10.3 Contents of files at the GSM application level

11.113GPPRelease 1999Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) InterfaceTS

The EFs in the Dedicated File DFGSM contain network related information.

10.3.1 EFLP (Language preference)

This EF contains the codes for one or more languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. This information may be used by the ME for MMI purposes.

This information may also be used for the screening of Cell Broadcast messages in a preferred language, as follows. When the CB Message Identifier capability is both allocated and activated, the ME selects only those CB messages the language of which corresponds to an entry in this EF or in EFELP, whichever of these EFs is used (see subclause 11.2.1). The CB message language is defined by the Data Coding Scheme (DCS: see TS 23.038 [12]) 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 [12]) to the language coding as defined in ISO 639 [30] if it is necessary to check the language coding in EFELP.

Identifier: ‘6F05’

Structure: transparent

Mandatory

File size: 1‑n bytes

Update activity: low

Access Conditions:

READ ALW

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

1st language code (highest prior.)

M

1 byte

2

2nd language code

O

1 byte

n

nth language code (lowest prior.)

O

1 byte

Coding: according to language codings contained in the Data Coding Scheme (see TS 23.038 [12]).

Using the command GET RESPONSE, the ME can determine the size of the EF.

10.3.2 EFIMSI (IMSI)

This EF contains the International Mobile Subscriber Identity (IMSI).

Identifier: ‘6F07’

Structure: transparent

Mandatory

File size: 9 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE CHV1

Bytes

Description

M/O

Length

1

length of IMSI

M

1 byte

2 to 9

IMSI

M

8 bytes

– length of IMSI

Contents:

The length indicator refers to the number of significant bytes, not including this length byte, required for the IMSI.

Coding: according to TS 04.08 [15].

‑ IMSI

Contents:

International Mobile Subscriber Identity.

Coding:

This information element is of variable length. If a network operator chooses an IMSI of less than 15 digits, unused nibbles shall be set to ‘F’.

Byte 2:

b8

b7

b6

b5

b4

b3

b2

b1

1

0

0

Parity

LSB of Digit 1

:

:

MSB of Digit 1

For the parity bit, see TS 04.08 [15].

Byte 3:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 2

:

:

MSB of Digit 2

LSB of Digit 3

:

:

MSB of Digit 3

etc.

10.3.3 EFKc (Ciphering key Kc)

This EF contains the ciphering key Kc and the ciphering key sequence number n.

Identifier: ‘6F20’

Structure: transparent

Mandatory

File size: 9 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 8

Ciphering key Kc

M

8 bytes

9

Ciphering key sequence number n

M

1 byte

‑ Ciphering key Kc

Coding:

The least significant bit of Kc is the least significant bit of the eighth byte. The most significant bit of Kc is the most significant bit of the first byte.

‑ Ciphering key sequence number n

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

n

bits b4 to b8 are coded 0

NOTE: TS 04.08 [15] defines the value of n=111 as "key not available". Therefore the value ’07’ and not ‘FF’ should be present following the administrative phase.

10.3.4 EFPLMNsel (PLMN selector)

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

Identifier: ‘6F30’

Structure: transparent

Optional

File size: 3n (n ≥ 8) bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

1st PLMN (highest priority)

M

3 bytes

22 to 24

8th PLMN

M

3 bytes

25 to 27

9th PLMN

O

3 bytes

(3n‑2) to 3n

nth PLMN (lowest priority)

O

3 bytes

‑ PLMN

Contents:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 04.08 [15].

If storage for fewer than the maximum possible number n is required, the excess bytes shall be set to ‘FF’.

For instance, using 246 for the MCC and 81 for the MNC and if this is the first and only PLMN, the contents reads as follows:

Bytes 1‑3: ’42’ ‘F6′ ’18’

Bytes 4‑6: ‘FF’ ‘FF’ ‘FF’

etc.

10.3.5 EFHPPLMN (Higher Priority PLMN search period)

This EF contains the interval of time between searches for a higher priority PLMN (see TS 22.011 [5]).

Identifier: ‘6F31’

Structure: transparent

Mandatory

File size: 1 byte

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Time interval

M

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’: No higher priority PLMN search attempts

‑ ’01’: n minutes

‑ ’02’: 2n minutes

‑ : :

‑ ‘YZ’: (16Y+Z)n minutes (maximum value)

All other values shall be interpreted by the ME as a default period.

For specification of the integer timer interval n, the maximum value and the default period refer to TS 22.011 [5].

10.3.6 EFACMmax (ACM maximum value)

This EF contains the maximum value of the accumulated call meter. This EF shall always be allocated if EFACM is allocated.

Identifier: ‘6F37’

Structure: transparent

Optional

File size: 3 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1/CHV2

(fixed during administrative management)

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

Maximum value

M

3 bytes

‑ Maximum value

Contents:

maximum value of the Accumulated Call Meter (ACM)

Coding:

First byte:

b8

b7

b6

b5

b4

b3

b2

b1

223

222

221

220

219

218

217

216

Second byte:

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 SIM and transmitted over the SIM/ME interface as binary.

ACMmax is not valid, as defined in TS 22.024 [7], if it is coded ‘000000’.

10.3.7 EFSST (SIM service table)

This EF indicates which services are allocated, and whether, if allocated, the service is activated. If a service is not allocated or not activated in the SIM, the ME shall not select this service.

Identifier: ‘6F38’

Structure: transparent

Mandatory

File size: X bytes, X ≥ 2

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Services n°1 to n°4

M

1 byte

2

Services n°5 to n°8

M

1 byte

3

Services n°9 to n°12

O

1 byte

4

Services n°13 to n°16

O

1 byte

5

Services n°17 to n°20

O

1 byte

6

Services n°21 to n°24

O

1 byte

7

Services n°25 to n°28

O

1 byte

8

Services n°29 to n°32

O

1 byte

etc.

X

Services (4X‑3) to (4X)

O

1 byte

‑Services

Contents:

Service n°1 :

CHV1 disable function

Service n°2 :

Abbreviated Dialling Numbers (ADN)

Service n°3 :

Fixed Dialling Numbers (FDN)

Service n°4 :

Short Message Storage (SMS)

Service n°5 :

Advice of Charge (AoC)

Service n°6 :

Capability Configuration Parameters (CCP)

Service n°7 :

PLMN selector

Service n°8 :

RFU

Service n°9 :

MSISDN

Service n°10:

Extension1

Service n°11:

Extension2

Service n°12:

SMS Parameters

Service n°13:

Last Number Dialled (LND)

Service n°14:

Cell Broadcast Message Identifier

Service n°15:

Group Identifier Level 1

Service n°16:

Group Identifier Level 2

Service n°17:

Service Provider Name

Service n°18:

Service Dialling Numbers (SDN)

Service n°19:

Extension3

Service n°20:

RFU

Service n°21:

VGCS Group Identifier List (EFVGCS and EFVGCSS)

Service n°22:

VBS Group Identifier List (EFVBS and EFVBSS)

Service n°23:

enhanced Multi‑Level Precedence and Pre‑emption Service

Service n°24:

Automatic Answer for eMLPP

Service n°25:

Data download via SMS‑CB

Service n°26:

Data download via SMS‑PP

Service n°27:

Menu selection

Service n°28:

Call control

Service n°29:

Proactive SIM

Service n°30:

Cell Broadcast Message Identifier Ranges

Service n°31:

Barred Dialling Numbers (BDN)

Service n°32:

Extension4

Service n°33:

De‑personalization Control Keys

Service n°34:

Co‑operative Network List

Service n°35:

Short Message Status Reports

Service n°36:

Network’s indication of alerting in the MS

Service n°37:

Mobile Originated Short Message control by SIM

Service n°38:

GPRS

Service n°39:

Image (IMG)

Service n°40:

SoLSA (Support of Local Service Area)

Service n°41:

USSD string data object supported in Call Control

Service n°42:

RUN AT COMMAND command

Service n43:

User controlled PLMN Selector with Access Technology

Service n 44:

Operator controlled PLMN Selector with Access Technology

Service n 45

HPLMN Selector with Access Technology

Service n 46:

CPBCCH Information

Service n 47:

Investigation Scan

Service n°48:

Extended Capability Configuration Parameters

Service n°49:

MExE

Service n°50

Reserved and shall be ignored

For a phase 2 SIM, the EF shall contain at least two bytes which correspond to the Phase 1 services. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF. The coding falls under the responsibility of ETSI.

NOTE 1: Service N°8 was used in Phase 1 for Called Party Subaddress. To prevent any risk of incompatibility Service N°8 should not be reallocated.

NOTE 2: As the BDN service relies on the Call Control feature, service n°31 (BDN) should only be allocated and activated if service n°28 (Call control) is allocated and activated.

Coding:

2 bits are used to code each service:

first bit = 1: service allocated

first bit = 0: service not allocated

where the first bit is b1, b3, b5 or b7;

second bit = 1: service activated

second bit = 0: service not activated

where the second bit is b2, b4, b6 or b8.

Service allocated means that the SIM has the capability to support the service. Service activated means that the service is available for the card holder (only valid if the service is allocated).

The following codings are possible:

‑ first bit = 0: service not allocated, second bit has no meaning;

‑ first bit = 1 and second bit = 0: service allocated but not activated;

‑ first bit = 1 and second bit = 1: service allocated and activated.

The bits for services not yet defined shall be set to RFU. For coding of RFU see subclause 9.3.

First byte:

b8

b7

b6

b5

b4

b3

b2

b1

Service n°1

Service n°2

Service n°3

Service n°4

Second byte:

b8

b7

b6

b5

b4

b3

b2

b1

Service n°5

Service n°6

Service n°7

Service n°8

etc.

The following example of coding for the first byte means that service n°1 "CHV1‑Disabling" is allocated but not activated:

b8

b7

b6

b5

b4

b3

b2

b1

X

X

X

X

X

X

0

1

If the SIM supports the FDN feature (FDN allocated and activated) a special mechanism shall exist in the SIM which invalidates both EFIMSI and EFLOCI once during each GSM session. This mechanism shall be invoked by the SIM automatically if FDN is enabled. This invalidation shall occur at least before the next command following selection of either EF. FDN is enabled when the ADN is invalidated or not activated.

If the SIM supports the BDN feature (BDN allocated and activated) a special mechanism shall exist in the SIM which invalidates both EFIMSI and EFLOCI once during each GSM session and which forbids the REHABILITATE command to rehabilitate both EFIMSI and EFLOCI until the PROFILE DOWNLOAD procedure is performed indicating that the ME supports the "Call control by SIM" facility. This mechanism shall be invoked by the SIM automatically if BDN is enabled. The invalidation of EFIMSI and EFLOCI shall occur at least before the next command following selection of either EF. BDN is enabled when the EFBDN is not invalidated.

10.3.8 EFACM (Accumulated call meter)

This EF contains the total number of units for both the current call and the preceding calls.

NOTE: The information may be used to provide an indication to the user for advice or as a basis for the calculation of the monetary cost of calls (see TS 22.086 [9]).

Identifier: ‘6F39’

Structure: cyclic

Optional

Record length: 3 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1/CHV2

(fixed during administrative management)

INCREASE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

Accumulated count of units

M

3 bytes

‑ Accumulated count of units

Contents: value of the ACM

Coding: see the coding of EFACMmax

10.3.9 EFGID1 (Group Identifier Level 1)

This EF contains identifiers for particular SIM‑ME associations. It can be used to identify a group of SIMs for a particular application.

Identifier: ‘6F3E’

Structure: transparent

Optional

File size: 1 to n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to n

SIM group identifier(s)

O

n bytes

10.3.10 EFGID2 (Group Identifier Level 2)

This EF contains identifiers for particular SIM‑ME associations. It can be used to identify a group of SIMs for a particular application.

Identifier: ‘6F3F’

Structure: transparent

Optional

File size: 1 to n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to n

SIM group identifier(s)

O

n bytes

NOTE: The structure of EFGID1 and EFGID2 are identical. They are provided to allow the network operator to enforce different levels of security dependant on application.

10.3.11 EFSPN (Service Provider Name)

This EF contains the service provider name and appropriate requirements for the display by the ME.

Identifier: ‘6F46’

Structure: transparent

Optional

File Size: 17 bytes

Update activity: low

Access Conditions:

READ ALWAYS

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Display Condition

M

1 byte

2 to 17

Service Provider Name

M

16 bytes

‑ Display Condition

Contents: display condition for the service provider name in respect to the registered PLMN (see TS 02.07 [3]).

Coding: see below

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

b1=0: display of registered PLMN not required

b1=1: display of registered PLMN required

RFU (see subclause 9.3)

‑ Service Provider Name

Contents: service provider string to be displayed

Coding: the string shall use either

– the SMS default 7‑bit coded alphabet as defined in TS 23.038 [12] 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 annex B.

10.3.12 EFPUCT (Price per unit and currency table)

This EF contains the Price per Unit and Currency Table (PUCT). The PUCT is Advice of Charge related information which may be used by the ME in conjunction with EFACM to compute the cost of calls in the currency chosen by the subscriber, as specified in TS 22.024 [7]. This EF shall always be allocated if EFACM is allocated.

Identifier: ‘6F41’

Structure: transparent

Optional

File size: 5 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1/CHV2

(fixed during administrative management)

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

Currency code

M

3 bytes

4 to 5

Price per unit

M

2 bytes

‑ Currency code

Contents:

the alpha‑identifier of the currency code.

Coding:

bytes 1, 2 and 3 are the respective first, second and third character of the alpha identifier. This alpha‑tagging shall use the SMS default 7‑bit coded alphabet as defined in TS 23.038 [12] with bit 8 set to 0.

‑ Price per unit

Contents:

price per unit expressed in the currency coded by bytes 1‑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‑3. Bits b5 to b8 of byte 5 are the decimal logarithm of the multiplicative factor represented by the absolute value of its decimal logarithm (EX) and the sign of EX, which is coded 0 for a positive sign and 1 for a negative sign.

Byte 4:

b8

b7

b6

b5

b4

b3

b2

b1

211

210

29

28

27

26

25

24

of EPPU

Byte 5:

b8

b7

b6

b5

b4

b3

b2

b1

23

22

21

20

of EPPU

Sign of EX

20 of Abs(EX)

21 of Abs(EX)

22 of Abs(EX)

The computation of the price per unit value is made by the ME in compliance with TS 22.024 [7] by the following formula:

price per unit = EPPU * 10EX.

The price has to be understood as expressed in the coded currency.

10.3.13 EFCBMI (Cell broadcast message identifier selection)

This EF contains the Message Identifier Parameters which specify the type of content of the cell broadcast messages that the subscriber wishes the MS to accept.

Any number of CB Message Identifier Parameters may be stored in the SIM. No order of priority is applicable.

Identifier: ‘6F45’

Structure: transparent

Optional

File size: 2n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 2

CB Message Identifier 1

O

2 bytes

3 to 4

CB Message Identifier 2

O

2 bytes

2n‑1 to 2n

CB Message Identifier n

O

2 bytes

‑ Cell Broadcast Message Identifier

Coding:

as in TS 23.041, "Message Format on BTS‑MS Interface ‑ Message Identifier".

Values listed show the types of message which shall be accepted by the MS.

Unused entries shall be set to ‘FF FF’.

10.3.14 EFBCCH (Broadcast control channels)

This EF contains information concerning the BCCH according to TS 04.08 [15].

BCCH storage may reduce the extent of a Mobile Station’s search of BCCH carriers when selecting a cell. The BCCH carrier lists in an MS shall be in accordance with the procedures specified in TS 04.08 [15]. The MS shall only store BCCH information from the System Information 2 message and not the 2bis extension message.

Identifier: ‘6F74’

Structure: transparent

Mandatory

File size: 16 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 16

BCCH information

M

16 bytes

‑ BCCH information

Coding:

The information is coded as octets 2‑17 of the "neighbour cells description information element" in TS 04.08 [15].

10.3.15 EFACC (Access control class)

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

Identifier: ‘6F78’

Structure: transparent

Mandatory

File size: 2 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 2

Access control classes

M

2 bytes

‑ Access control classes

Coding:

Each ACC is coded on one bit. An ACC is "allocated" if the corresponding bit is set to 1 and "not allocated" if this bit is set to 0. Bit b3 of byte 1 is set to 0.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

15

14

13

12

11

10

09

08

Number of the ACC (except for bit b3)

Byte 2:

b8

b7

b6

b5

b4

b3

b2

b1

07

06

05

04

03

02

01

00

Number of the ACC

10.3.16 EFFPLMN (Forbidden PLMNs)

This EF contains the coding for four Forbidden PLMNs (FPLMN). It is read by the ME as part of the SIM initialization procedure and indicates PLMNs which the MS shall not automatically attempt to access.

A PLMN is written to the EF if a network rejects a Location Update with the cause "PLMN not allowed". The ME shall manage the list as follows.

When four FPLMNs are held in the EF, and rejection of a further PLMN is received by the ME from the network, the ME shall modify the EF using the UPDATE command. This new PLMN shall be stored in the fourth position, and the existing list "shifted" causing the previous contents of the first position to be lost.

When less than four FPLMNs exist in the EF, storage of an additional FPLMN shall not cause any existing FPLMN to be lost.

Dependent upon procedures used to manage storage and deletion of FPLMNs in the EF, it is possible, when less than four FPLMNs exist in the EF, for ‘FFFFFF’ to occur in any position. The ME shall analyse all the EF for FPLMNs in any position, and not regard ‘FFFFFF’ as a termination of valid data.

Identifier: ‘6F7B’

Structure: transparent

Mandatory

File size: 12 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

PLMN 1

M

3 bytes

4 to 6

PLMN 2

M

3 bytes

7 to 9

PLMN 3

M

3 bytes

10 to 12

PLMN 4

M

3 bytes

‑ PLMN

Contents:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 04.08 [15].

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‑9: ’42’ ‘F6′ ’18’

If storage for fewer than 4 PLMNs is required, the unused bytes shall be set to ‘FF’.

10.3.17 EFLOCI (Location information)

This EF contains the following Location Information:

‑ Temporary Mobile Subscriber Identity (TMSI);

‑ Location Area Information (LAI);

‑ TMSI TIME;

‑ Location update status.

See clause 11.1.2 for special requirements when updating EFLOCI.

Identifier: ‘6F7E’

Structure: transparent

Mandatory

File size: 11 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE CHV1

Bytes

Description

M/O

Length

1 to 4

TMSI

M

4 bytes

5 to 9

LAI

M

5 bytes

10

TMSI TIME

M

1 byte

11

Location update status

M

1 byte

‑ TMSI

Contents: Temporary Mobile Subscriber Identity

Coding: according to TS 04.08 [15].

Byte 1: first byte of TMSI

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ LAI

Contents: Location Area Information

Coding: according to TS 04.08 [15].

Byte 5: first byte of LAI

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ TMSI TIME

Contents: Current value of Periodic Location Updating Timer (T3212).

This byte is used by Phase 1 MEs, but it shall not be used by Phase 2 MEs.

‑ Location update status

Contents: status of location update according to TS 04.08 [15].

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 subclause 9.3).

10.3.18 EFAD (Administrative data)

This EF contains information concerning the mode of operation according to the type of SIM, such as normal (to be used by PLMN subscribers for GSM operations), type approval (to allow specific use of the ME during type approval procedures of e.g. the radio equipment), cell testing (to allow testing of a cell before commercial use of this cell), manufacturer specific (to allow the ME manufacturer to perform specific proprietary auto‑test in its ME during e.g. maintenance phases).

It also provides an indication of whether some ME features should be activated during normal operation as well as information about the length of the MNC, which is part of the International Mobile Subscriber Identity (IMSI).

Identifier: ‘6FAD’

Structure: transparent

Mandatory

File size: 3+X bytes

Update activity: low

Access Conditions:

READ ALW

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

MS operation mode

M

1 byte

2 to 3

Additional information

M

2 bytes

4

length of MNC in the IMSI

O

1 byte

5 to 3+X

RFU

O

(X-1) bytes

NOTE: If X=0 no optional field is present;
If X=1 byte 4 is present but no RFU field is present;
When the RFU field is present (X ≥2) then byte 4 shall be present.

‑ MS operation mode

Contents: mode of operation for the MS

Coding:

Initial value

‑ normal operation ’00’

‑ type approval operations ’80’

‑ normal operation + specific facilities ’01’

‑ type approval operations + specific facilities ’81’

‑ maintenance (off line) ’02’

‑ cell test operation ’04’

‑ Additional information

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

Byte 3:

b8

b7

b6

b5

b4

b3

b2

b1

b1=0: OFM to be disabled by the ME

b1=1: OFM to be activated by the ME

RFU

The OFM bit is used to control the Ciphering Indicator as specified in TS 02.07 [3]

‑ ME manufacturer specific information (if b2=1 in byte 1).

  • 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 subclause 9.3).

10.3.19 EFPhase (Phase identification)

This EF contains information concerning the phase of the SIM.

Identifier: ‘6FAE’

Structure: transparent

Mandatory

File size: 1 byte

Update activity: low

Access Conditions:

READ ALW

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

SIM Phase

M

1 byte

‑ SIM Phase

Coding:

’00’: phase 1

’02’: phase 2

’03’: phase 2 and PROFILE DOWNLOAD required (see TS 11.14 [27]).

All other codings are reserved for specification by ETSI TC SMG. Codings ’04’ to ‘0F’ indicate that the SIM supports, as a minimum, the mandatory requirements defined in this specification.

This phase identification does not preclude a SIM to support some features of a phase later than the one indicated in EFPhase. For example : if EFPhase is coded ’00’, it may be assumed by the ME that some Phase 2 or Phase 2+ features are supported by this SIM; if EFPhase is coded ’02’ or ’03’, it may be assumed by the ME that some Phase 2+ features are supported by this SIM.

However, the services n°3 (FDN) and/or n°5 (AoC) shall only be allocated and activated in SIMs of phase 2 or later with EFPhase being coded ’02’ or greater. Similarly, service n°31 (BDN) shall only be allocated and activated in SIMs with EFPhase being coded ’03’ or greater.

If EFPhase is coded ’03’ or greater, an ME supporting SIM Application Toolkit shall perform the PROFILE DOWNLOAD procedure, as defined in TS 11.14 [27].

10.3.20 EFVGCS (Voice Group Call Service)

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

Identifier: ‘6FB1’

Structure: transparent

Optional

File size: 4n bytes (n <= 50)

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 4

Group ID 1

M

4 bytes

5 to 8

Group ID 2

O

4 bytes

:

:

:

:

(4n‑3) to 4n

Group ID n

O

4 bytes

‑ Group ID

Contents: VGCS Group ID, according to TS 23.003 [10]

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. If a VGCS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to ‘F’. VGCS Group ID Digit 1 is the most significant digit of the Group ID.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 1 of Group ID 1

:

:

MSB of Digit 1 of Group ID 1

LSB of Digit 2 of Group ID 1

:

:

MSB of Digit 2 of Group ID 1

Byte 2:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 3 of Group ID 1

:

:

MSB of Digit 3 of Group ID 1

LSB of Digit 4 of Group ID 1

:

:

MSB of Digit 4 of Group ID 1

Byte 3:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 5 of Group ID 1

:

:

MSB of Digit 5 of Group ID 1

LSB of Digit 6 of Group ID 1

:

:

MSB of Digit 6 of Group ID 1

Byte 4:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 7 of Group ID 1

:

:

MSB of Digit 7 of Group ID 1

LSB of Digit 8 of Group ID 1

:

:

MSB of Digit 8 of Group ID 1

:

: etc……..

Byte (4n-3) to 4n:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 7 of Group ID n

:

:

MSB of Digit 7 of Group ID n

LSB of Digit 8 of Group ID n

:

:

MSB of Digit 8 of Group ID n

If storage for fewer than the maximum possible number n of VGCS Group IDs, is required, the excess bytes shall be set to ‘FF’.

10.3.21 EFVGCSS (Voice Group Call Service Status)

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

Identifier: ‘6FB2’

Structure: transparent

Optional

File size: 7 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 7

Activation/Deactivation Flags

M

7 bytes

‑ Activation/Deactivation Flags

Contents: Activation/Deactivation Flags of the appropriate Group IDs

Coding:

bit = 0 means ‑ Group ID deactivated

bit = 1 means ‑ Group ID activated

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

Group ID 1

:

:

:

:

:

:

Group ID 8

etc : : : : : : : :

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

10.3.22 EFVBS (Voice Broadcast Service)

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

Identifier: ‘6FB3’

Structure: transparent

Optional

File size: 4n bytes (n <= 50)

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 4

Group ID 1

M

4 bytes

5 to 2

Group ID 2

O

4 bytes

:

:

:

:

(4n‑3) to 4n

Group ID n

O

4 bytes

‑ Group ID

Contents: VBS Group ID, according to TS 23.003 [10]

Coding:

The VBS Group ID is of a variable length with a maximum length of 8 digits. Each VBS Group ID is coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code. If a VBS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to ‘F’. VBS Group ID Digit 1 is the most significant digit of the Group ID.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 1 of Group ID 1

:

:

MSB of Digit 1 of Group ID 1

LSB of Digit 2 of Group ID 1

:

:

MSB of Digit 2 of Group ID 1

Byte 2:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 3 of Group ID 1

:

:

MSB of Digit 3 of Group ID 1

LSB of Digit 4 of Group ID 1

:

:

MSB of Digit 4 of Group ID 1

Byte 3:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 5 of Group ID 1

:

:

MSB of Digit 5 of Group ID 1

LSB of Digit 6 of Group ID 1

:

:

MSB of Digit 6 of Group ID 1

Byte 4:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 7 of Group ID 1

:

:

MSB of Digit 7 of Group ID 1

LSB of Digit 8 of Group ID 1

:

:

MSB of Digit 8 of Group ID 1

:

: etc……..

Byte (4n-3) to 4n:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 7 of Group ID n

:

:

MSB of Digit 7 of Group ID n

LSB of Digit 8 of Group ID n

:

:

MSB of Digit 8 of Group ID n

If storage for fewer than the maximum possible number n of VBS Group IDs, is required, the excess bytes shall be set to ‘FF’.

10.3.23 EFVBSS (Voice Broadcast Service Status)

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’

Structure: transparent

Optional

File size: 7 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 7

Activation/Deactivation Flags

M

7 bytes

‑ Activation/Deactivation Flags

Contents: Activation/Deactivation Flags of the appropriate Group IDs

Coding:

see coding of EFVGCS

10.3.24 EFeMLPP (enhanced Multi Level Pre-emption and Priority)

This EF contains information about priority levels and fast call set‑up conditions for the enhanced Multi Level Pre-emption and Priority service that which can be used by the subscriber.

Identifier: ‘6FB5’

Structure: transparent

Optional

File size: 2 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Priority levels

M

1 byte

2

Fast call set‑up conditions

M

1 byte

‑ Priority levels

Contents: The eMLPP priority levels subscribed to.

Coding: Each eMLPP priority level is coded on one bit. Priority levels subscribed to have their corresponding bits set to 1. Priority levels not subscribed to have their corresponding bits set to 0. Bit b8 is reserved and set to 0.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

priority level A

priority level B

priority level 0

priority level 1

priority level 2

priority level 3

priority level 4

0

NOTE: Priority levels A and B can not be subscribed to (see TS 22.067 [42] for details).

EXAMPLE 1: If priority levels 0, 1 and 2 are subscribed to, EFeMLPP shall be coded ‘1C’.

‑ Fast call set‑up conditions

Contents: For each eMLPP priority level, the capability to use a fast call set‑up procedure.

Coding: Each eMLPP priority level is coded on one bit. Priority levels for which fast call set‑up is allowed have their corresponding bits set to 1. Priority levels for which fast call set‑up is not allowed have their corresponding bits set to 0. Bit b8 is reserved and set to 0.

Byte 2: fast call set-up condition for:

b8

b7

b6

b5

b4

b3

b2

b1

fast call set-up condition for priority level A

`

fast call set-up condition for priority level B

fast call set-up condition for priority level 0

fast call set-up condition for priority level 1

fast call set-up condition for priority level 2

fast call set-up condition for priority level 3

fast call set-up condition for priority level 4

0

EXAMPLE 2: If fast call set‑up is allowed for priority levels 0 and 1, then byte 2 of EFeMLPP is coded ‘0C’.

10.3.25 EFAAeM (Automatic Answer for eMLPP Service)

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

Identifier: ‘6FB6’

Structure: transparent

Optional

File size: 1 byte

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Automatic answer priority levels

M

1 byte

‑ Automatic answer priority levels

Contents:

For each eMLPP priority level, the capability for the mobile station to answer automatically to incoming calls (with the corresponding eMLPP priority level).

Coding:

Each eMLPP priority level is coded on one bit. Priority levels allowing an automatic answer from the mobile station have their corresponding bits set to 1. Priority levels not allowing an automatic answer from the mobile station have their corresponding bits set to 0. Bit b8 is reserved and set to 0.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

Automatic answer priority for priority level A

Automatic answer priority for priority level B

Automatic answer priority for priority level 0

Automatic answer priority for priority level 1

Automatic answer priority for priority level 2

Automatic answer priority for priority level 3

Automatic answer priority for priority level 4

0

EXAMPLE: If automatic answer is allowed for incoming calls with priority levels A, 0 and 1, then EFAAeMLPP is coded ‘0D’.

10.3.26 EFCBMID (Cell Broadcast Message Identifier for Data Download)

This EF contains the message identifier parameters which specify the type of content of the cell broadcast messages which are to be passed to the SIM.

Any number of CB message identifier parameters may be stored in the SIM. No order of priority is applicable.

Identifier: ‘6F48’

Structure: transparent

Optional

File size: 2n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 2

CB Message Identifier 1

O

2 bytes

3 to 4

CB Message Identifier 2

O

2 bytes

2n‑1 to 2n

CB Message Identifier n

O

2 bytes

‑ Cell Broadcast Message Identifier

Coding:

as in TS 23.041 [14]. Values listed show the identifiers of messages which shall be accepted by the MS to be passed to the SIM.

Unused entries shall be set to ‘FF FF’.

10.3.27 EFECC (Emergency Call Codes)

This EF contains up to 5 emergency call codes.

Identifier: ‘6FB7’

Structure: transparent

Optional

File size: 3n (n  5) bytes

Update activity: low

Access Conditions:

READ ALW

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

Emergency Call Code 1

O

3 bytes

4 to 6

Emergency Call Code 2

O

3 bytes

(3n‑2) to 3n

Emergency Call Code n

O

3 bytes

‑ 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 that 6 digits is chosen, then the unused nibbles shall be set to ‘F’.

Byte 1:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 1

:

:

MSB of Digit 1

LSB of Digit 2

:

:

MSB of Digit 2

Byte 2:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 3

:

:

MSB of Digit 3

LSB of Digit 4

:

:

MSB of Digit 4

Byte 3:

b8

b7

b6

b5

b4

b3

b2

b1

LSB of Digit 5

:

:

MSB of Digit 5

LSB of Digit 6

:

:

MSB of Digit 6

10.3.28 EFCBMIR (Cell broadcast message identifier range selection)

This EF contains ranges of cell broadcast message identifiers that the subscriber wishes the MS to accept.

Any number of CB Message Identifier Parameter ranges may be stored in the SIM. No order of priority is applicable.

Identifier: ‘6F50’

Structure: transparent

Optional

File size: 4n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 4

CB Message Identifier Range 1

O

4 bytes

5 to 8

CB Message Identifier Range 2

O

4 bytes

(4n‑3) to 4n

CB Message Identifier Range n

O

4 bytes

‑ 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 [14] "Message Format on BTS‑MS Interface ‑ Message Identifier". Values listed show the ranges of messages which shall be accepted by the MS.

Unused entries shall be set to ‘FF FF FF FF’.

10.3.29 EFDCK De-personalization Control Keys

This EF provides storage for the de‑personalization control keys associated with the OTA de‑personalization cycle of TS 22.022.

Identifier: ‘6F2C’

Structure: transparent

Optional

File size: 16 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 4

8 digits of network de‑personalization control key

M

4 bytes

5 to 8

8 digits of network subset de‑personalization control key

M

4 bytes

9 to 12

8 digits of service provider de‑personalization control key

M

4 bytes

13 to 16

8 digits of corporate de‑personalization control key

M

4 bytes

Empty control key records shall be coded ‘FFFFFFFF’.

10.3.30 EFCNL (Co-operative Network List)

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

Identifier: ‘6F32’

Structure: transparent

Optional

File size: 6n bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 6

Element 1 of co-operative net list

O

6 bytes

6n‑5 to 6n

Element n of co-operative net list

O

6 bytes

‑ Co-operative Network List

Contents:

PLMN network subset, service provider ID and corporate ID of co-operative networks.

Coding:

For each 6 byte list element

Byte 1 to 3 : PLMN (MCC + MNC) : according to TS 04.08 [15].

Byte 4:

b8

b7

b6

b5

b4

b3

b2

b1

LS bit of network subset digit 1

:

:

MS bit of network subset digit 1

LS bit of network subset digit 2

:

:

MS bit of network subset digit 2

Byte 5:

b8

b7

b6

b5

b4

b3

b2

b1

LS bit of service provider digit 1

:

:

MS bit of service provider digit 1

LS bit of service provider digit 2

:

:

MS bit of service provider digit 2

Byte 6:

b8

b7

b6

b5

b4

b3

b2

b1

LS bit of corporate digit 1

:

:

MS bit of corporate digit 1

LS bit of corporate digit 2

:

:

MS bit of corporate digit 2

Empty fields shall be coded with ‘FF’.

The end of the list is delimited by the first MCC field coded ‘FFF’.

10.3.31 EFNIA (Network’s Indication of Alerting)

This EF contains categories and associated text related to the Network’s indication of alerting in the MS service defined in TS 02.07 [3].

Identifier: ‘6F51’

Structure: linear fixed

Optional

Record length : X+1 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Alerting category

M

1 byte

2 to X+1

Informative text

M

X bytes

‑ Alerting category

Contents:

category of alerting for terminating traffic.

Coding:

according to TS 04.08 [15]. 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 (subclause 10.5.1). The maximum number of characters for this informative text is indicated in TS 02.07 [3].

10.3.32 EFKcGPRS (GPRS Ciphering key KcGPRS)

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

Identifier: ‘6F52’

Structure: transparent

Optional

File size: 9 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 8

Ciphering key KcGPRS

M

8 bytes

9

Ciphering key sequence number n for GPRS

M

1 byte

‑ Ciphering key KcGPRS

Coding:

The least significant bit of KcGPRS is the least significant bit of the eighth byte. The most significant bit of KcGPRS is the most significant bit of the first byte.

‑ Ciphering key sequence number n for GPRS

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

n

bits b4 to b8 are coded 0

NOTE: TS 04.08 [15] defines the value of n=111 as "key not available". Therefore the value ’07’ and not ‘FF’ should be present following the administrative phase.

10.3.33 EFLOCIGPRS (GPRS location information)

This EF contains the following Location Information:

‑ Packet Temporary Mobile Subscriber Identity (P-TMSI);

‑ Packet Temporary Mobile Subscriber Identity signature value (P-TMSI signature value);

‑ Routing Area Information (RAI);

‑ Routing Area update status.

Identifier: ‘6F53’

Structure: transparent

Optional

File size: 14 bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 4

P-TMSI

M

4 bytes

5 to 7

P-TMSI signature value

M

3 bytes

8 to 13

RAI

M

6 bytes

14

Routing Area update status

M

1 byte

‑ P-TMSI

Contents: Packet Temporary Mobile Subscriber Identity

Coding: according to TS 04.08 [15].

Byte 1: first byte of P-TMSI

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ P-TMSI signature value

Contents: Packet Temporary Mobile Subscriber Identity signature value

Coding: according to TS 04.08 [15].

Byte 5: first byte of P-TMSI signature value

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ RAI

Contents: Routing Area Information

Coding: according to TS 04.08 [15].

Byte 8: first byte of RAI

b8

b7

b6

b5

b4

b3

b2

b1

MSB

‑ Routing area update status

Contents: status of routing area update according to TS 04.08 [15].

Coding:

Byte 14:

Bits: b3 b2 b1

0 0 0 : updated

0 0 1 : not updated

0 1 0 : PLMN not allowed

0 1 1 : Routing Area not allowed

1 1 1 : reserved

Bits b4 to b8 are RFU (see subclause 9.3).

10.3.34 EFSUME (SetUpMenu Elements)

This EF contains Simple TLVs related to the menu title to be used by a SIM card supporting the SIM API when issuing a SET UP MENU proactive command.

Identifier: ‘6F54’

Structure: transparent

Optional

File size: X+Y bytes

Update activity: low

Access Conditions:

READ ADM

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 – X

Title Alpha Identifier

M

X bytes

1+X to X+Y

Title Icon Identifier

O

Y bytes

– Title Alpha Identifier

Contents:

this field contains the Alpha Identifier Simple TLV defining the menu title text.

Coding:

according to TS 11.14 [27].

‑ Title Icon Identifier

Contents:

this field contains the Icon Identifier Simple TLV defining the menu title icon.

Coding:

according to GSM 11.14 [27].
If not present the field shall be set to ‘FF’.

Unused bytes of this file shall be set to ‘FF’.

10.3.35 EFPLMNwAcT (User controlled PLMN Selector with Access Technology)

This EF contains coding for n PLMNs, where n is at least eight. This information, determined by the user, defines the preferred PLMNs of the user in priority order. The EF also contains the Access Technologies for each PLMN in this list. (see TS 23.122 [51]).

Identifier:’6F60′

Structure: transparent

Optional

File size: 5n (n  8) bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

1st PLMN (highest priority)

M

3 bytes

4 to 5

1st PLMN Access Technology Identifier

M

2 bytes

6 to 8

2nd PLMN

M

3 bytes

9 to 10

2nd PLMN Access Technology Identifier

M

2 bytes

:

:

36 to 38

8th PLMN

M

3 bytes

39 to 40

8th PLMN Access Technology Identifier

M

2 bytes

41 to 43

9th PLMN

O

3 bytes

44 to 45

9th PLMN Access Technology Identifier

O

2 bytes

:

:

(5n-4) to (5n‑2)

Nth PLMN (lowest priority)

O

3 bytes

(5n-1) to 5n

Nth PLMN Access Technology Identifier

O

2 bytes

‑ PLMN

Contents:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 24.008 [47].

‑ Access Technologies

Contents: The Access Technologies of a PLMN that the MS will assume when searching for a listed PLMN.

Coding:

– 2 bytes are used to select the access technology where the meaning of each bit is as follows:

– bit = 1: access technology selected;

– bit = 0: access technology not selected.

Byte 5n-1:

b8

b7

b6

b5

b4

b3

b2

b1

RFU

RFU

RFU

RFU

RFU

RFU

RFU

Reserved (see 3G TS 31.102 [52])

Byte 5n:

b8

b7

b6

b5

b4

b3

b2

b1

RFU

RFU

RFU

RFU

RFU

RFU

GSM COMPACT

GSM

The RFU bits are coded with ‘0’ in the bit positions.

10.3.36 EFOPLMNwAcT (Operator controlled PLMN Selector with Access Technology)

This EF contains coding for n PLMNs, where n is at least eight. This information, determined by the operator, defines the preferred PLMNs of the operator in priority order. The EF also contains the Access Technologies for each PLMN in this list (see TS 23.122 [51]).

Identifier: ‘6F61’

Structure: transparent

Optional

File size: 5n (n  8) bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

1st PLMN (highest priority)

M

3 bytes

4 to 5

1st PLMN Access Technology Identifier

M

2 bytes

:

:

36 to 38

8th PLMN

M

3 bytes

39 to 40

8th PLMN Access Technology Identifier

M

2 bytes

41 to 43

9th PLMN

O

3 bytes

44 to 45

9th PLMN Access Technology Identifier

O

2 bytes

:

:

(5n-4) to (5n‑2)

Nth PLMN (lowest priority)

O

3 bytes

(5n-1) to 5n

Nth PLMN Access Technology Identifier

O

2 bytes

‑ PLMN

Contents:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 24.008 [47].

‑ Access Technologies

Contents: The Access Technologies of a PLMN that the MS will assume when searching for a listed PLMN.

Coding: See EFPLMNwAcT for coding.

10.3.37 EFHPLMNwAcT (HPLMN Selector with Access Technology)

The HPLMN Selector with access technology data field shall contain the HPLMN code, or codes together with the respective access technology in priority order (see TS 23.122 [51]).

Identifier: ‘6F62’

Structure: transparent

Optional

File size: 5n (n ≥ 1) bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 3

1st PLMN (highest priority)

M

3 bytes

4 to 5

1st PLMN Access Technology Identifier

M

2 bytes

6 to 8

2nd PLMN

O

3 bytes

9 to 10

2nd PLMN Access Technology Identifier

O

2 bytes

:

:

(5n-4) to (5n‑2)

Nth PLMN (lowest priority)

O

3 bytes

(5n-1) to 5n

Nth PLMN Access Technology Identifier

O

2 bytes

‑ PLMN

Contents:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).

Coding:

according to TS 24.008 [47].

‑ Access Technology

Contents: The Access Technology of the HPLMN that the MS 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.

10.3.38 EFCPBCCH (CPBCCH Information)

This EF contains information concerning the CPBCCH according to TS 04.18 [48] and TS 03.22 [45].

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 in TS 04.18 [48], TS 04.60 [49] and TS 03.22 [45]. The MS stores CPBCCH information from the System Information 19 message, Packet System Information 3, and Packet System Information 3 bis on the SIM. The same CPBCCH carrier shall never occur twice in the list.

Identifier: ‘6F63’

Structure: transparent

Optional

File size: 2n bytes

Update activity: high

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to 2

Element 1 of CPBCCH carrier list

M

2 bytes

2n-1 to 2n

Element n of CPBCCH carrier list

M

2 bytes

‑ Element in CPBCCH carrier list

Coding:

Byte 1: first byte of CPBCCH carrier list element

b8

b7

b6

b5

b4

b3

b2

b1

LSB of ARFCN

:

:

:

:

:

:

:

Byte 2: second byte of CPBCCH carrier list element

b8

b7

b6

b5

b4

b3

b2

b1

:

MSB of ARFCN

High/Low band indicator

bits b4 to b7 are RFU

Empty indicator

– ARFCN (10 bits) as defined in TS 05.05 [46].

– 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’, 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 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.

10.3.39 EFInvScan (Investigation Scan)

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

Identifier: ‘6F64’

Structure: transparent

Optional

File size: 1 byte

Update activity: low

Access Conditions:

READ CHV1

UPDATE ADM

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1

Investigation scan flags

M

1 bytes

‑ Investigation scan flags

Coding:

b8

b7

b6

b5

b4

b3

b2

b1

In limited service mode

After successful PLMN selection

Bits b3 to b8 are coded RFU

A ‘1’ in a bit position indicates that the investigation scan shall be performed for the condition corresponding to that bit position and a ‘0’ that it shall not be performed.

If this elementary file is not present, no investigation scan shall be performed.

10.3.40 Void