4.4.3 Contents of files at the DF GSM-ACCESS level
(Files required for GSM Access)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
The Efs described in this clause are required for the USIM application to be able to access service through a GSM network.
The presence of this DF and thus the support of a GSM access is indicated in the ‘USIM Service Table’ as service no. ’27’ being available.
4.4.3.1 EFKc (GSM Ciphering key Kc)
If service n°27 is "available", this file shall be present.
This EF contains the ciphering key Kc and the ciphering key sequence number n for enciphering in a GSM access network.
|
Identifier: ‘4F20’ |
Structure: transparent |
Optional |
||||
|
SFI: ’01’ |
||||||
|
File size: 9 bytes |
Update activity: high |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE 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 24.008 [9] defines the value of n=111 as "key not available". Therefore the value ’07’ and not ‘FF’ should be present following the administrative phase.
4.4.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS)
If service n°27 is "available", this file shall be present.
This EF contains the ciphering key KcGPRS and the ciphering key sequence number n for GPRS (see TS 23.060 [7]).
|
Identifier: ‘4F52’ |
Structure: transparent |
Optional |
||||
|
SFI: ’02 |
||||||
|
File size: 9 bytes |
Update activity: high |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE 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 24.008 [9] defines the value of n=111 as "key not available". Therefore the value ’07’ and not ‘FF’ should be present following the administrative phase.
4.4.3.3 Void
4.4.3.4 EFCPBCCH (CPBCCH Information)
If service n°39 is "available", this file shall be present.
This EF contains information concerning the CPBCCH according to TS 44.018 [28].
CPBCCH storage may reduce the extent of a Mobile Station’s search of CPBCCH carriers when selecting a cell. The CPBCCH carrier lists shall be in accordance with the procedures specified TS 23.022 [29]. The MS stores CPBCCH information (from the System Information 19 message, Packet System Information 3, and Packet System Information 3 bis) on the USIM. The same CPBCCH carrier shall never occur twice in the list.
|
Identifier: ‘4F63’ |
Structure: transparent |
Optional |
||||
|
File size: 2n bytes |
Update activity: high |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE 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 45.005 [34].
– High/Low band indicator: If the ARFCN indicates possibly a channel in the DCS 1800 or a channel in the PCS 1900 band, if the bit is set to ‘1’ the channel is in the higher band (GSM 1900). If the bit is set to ‘0’, the lower band (GSM 1800) is indicated. If ARFCN indicates a unique channel, this indicator shall be set to ‘0’.
– Empty indicator: If this bit is set to ‘1’, no valid CPBCCH carrier is stored in this position. If the Empty Indicator is set to ‘1’, the content of the CPBCCH carrier field shall be ignored. The empty indicator shall also be used, and set to ‘1’, if storage of fewer than maximum number n, of CPBCCH carrier fields is required.
4.4.3.5 EFInvScan (Investigation Scan)
If service n°40 is "available", this file shall be present.
This EF contains two flags used to control the investigation scan for higher prioritized PLMNs not offering voice services.
|
Identifier: ‘4F64’ |
Structure: transparent |
Optional |
||||
|
File size: 1 byte |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Investigation scan flags |
M |
1 byte |
|||
‑ Investigation scan flags
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
In limited service mode |
|||||||||||||||||||
|
After successful PLMN selection |
|||||||||||||||||||
|
Bits b3 to b8 are coded RFU |
|||||||||||||||||||
A ‘1’ in a bit position indicates that the investigation scan shall be performed for the condition corresponding to that bit position and a ‘0’ that it shall not be performed.
If this elementary file is not present, no investigation scan shall be performed.