If service
No. 6 is
"available", this file shall be present.
This EF contains Barred Dialling Numbers (BDN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging. As the BDN service relies on the Call Control feature, BDN shall only be available if Call Control is available. If this file is present in the USIM, the Enabled Services Table (
EFEST) shall also be present.
Identifier: '6F4D' | Structure: linear fixed | Optional |
Record length: X+15 bytes | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | PIN2 |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 to X | Alpha Identifier | O | X bytes |
X+1 | Length of BCD number/SSC contents | M | 1 byte |
X+2 | TON and NPI | M | 1 byte |
X+3 to X+12 | Dialling Number/SSC String | M | 10 bytes |
X+13 | Capability/Configuration2 Record Identifier | M | 1 byte |
X+14 | Extension4 Record Identifier | M | 1 byte |
X+15 | Comparison Method Pointer | M | 1 byte |
For contents and coding of all data items, except for the Comparison Method Pointer, see the respective data items of
EFADN, with the exception that extension records are stored in the
EFEXT4 and capability/configuration parameters are stored in
EFCCP2. The Comparison Method Pointer refers to a record number in
EFCMI.
If service
No. 7 is
"available", this file shall be present.
This EF contains extension data of a BDN/SSC.
Identifier: '6F55' | Structure: linear fixed | Optional |
Record length: 13 bytes | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | PIN2 |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 | Record type | M | 1 byte |
2 to 12 | Extension data | M | 11 bytes |
13 | Identifier | M | 1 byte |
For contents and coding see
clause 4.4.2.4 EFEXT1.
If service
No. 6 is
"available", this file shall be present.
This EF contains the list of Comparison Method Identifiers and alpha-tagging associated with BDN entries (see
EFBDN).
Identifier: '6F58' | Structure: linear fixed | Optional |
Record length: X+1 bytes | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | ADM |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 to X | Alpha Identifier | M | X bytes |
X+1 | Comparison Method Identifier | M | 1 byte |
Contents:
Alpha-tagging of the associated Comparison Method Identifier.
Coding:
Same as the alpha identifier in
EFADN.
Comparison Method Identifier
Contents:
This byte describes the comparison method which is associated with a BDN record. Its interpretation is not specified but it shall be defined by the card issuers implementing the BDN feature on their USIMs.
Coding:
Binary; values from 0 to 255 are allowed.
The default coding 255 is reserved for empty field.
If service
No. 2,
No. 6,
No. 34 or
No. 35 is
"available" (as indicated in the USIM Service Table), this file shall be present.
This EF indicates which services are enabled. If a service is not indicated as enabled in this table, the ME shall not select the service.
Identifier: '6F56' | Structure: transparent | Optional |
SFI: '05' | |
File size: X bytes, (X ≥ 1) | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | PIN2 |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 | Services No. 1 to No. 8 | M | 1 byte |
2 | Services No. 9 to No. 16 | O | 1 byte |
etc. | | | |
X | Services No. (8X-7) to No. (8X) | O | 1 byte |
Contents
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then the EF shall also contain all bytes before that byte. Other services are possible in the future. The coding falls under the responsibility of the 3GPP.
Coding:
-
1 bit is used to code each service:
-
bit = 1: service activated;
-
bit = 0: service deactivated.
-
Unused bits shall be set to '0'.
A service which is listed in this table is enabled if it is indicated as available in the USIM Service Table (UST) and indicated as activated in the Enabled Services Tables (EST) otherwise this service is, either not available or disabled.
First byte:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
Service No. 8 |
Service No. 7 |
Service No. 6 |
Service No. 5 |
Service No. 4 |
Service No. 3 |
Service No. 2 |
Service No. 1 |
etc.
If service
No. 35 is
"available", this file shall be present.
This EF contains the list of allowed APNs (Access Point Names) or DNNs. If this file is present in the USIM, the Enabled Services Table (
EFEST) shall also be present.
Identifier: '6F57' | Structure: transparent | Optional |
File size: X bytes (X>1) | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | PIN2 |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 | Number of APNs/DNNs | M | 1 byte |
2 to X | APN/DNN TLVs | M | X-1 byte |
For contents and coding of APN/DNN-TLV values see
TS 23.003. The tag value of the APN/DNN-TLV shall be
'DD'.
"Network provided APN/DNN" is coded with a TLV object of length zero.
If service
No. 36 is
"available", this file shall be present.
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 | PIN |
UPDATE | PIN |
DEACTIVATE | ADM |
ACTIVATE | 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 bytes shall be coded 'FFFFFFFF'.
If service
No. 37 is
"available", this file shall be present.
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, (n ≥ 1) | Update activity: low |
Access Conditions:
READ | PIN |
UPDATE | ADM |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 to 6 | Element 1 of co-operative net list | M | 6 bytes |
… | | | |
6n-5 to 6n | Element n of co-operative net list | O | 6 bytes |
Co-operative Network List
Contents:
PLMN network subset, service provider ID and corporate ID of co-operative networks.
Coding:
For each 6 byte list element.
Bytes 1 to 3: PLMN (MCC + MNC): according to
TS 24.008.
Byte 4:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
MS bit of network subset digit 2 |
|
|
LS bit of network subset digit 2 |
MS bit of network subset digit 1 |
|
|
LS bit of network subset digit 1 |
Byte 5:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
MS bit of service provider digit 2 |
|
|
LS bit of service provider digit 2 |
MS bit of service provider digit 1 |
|
|
LS bit of service provider digit 1 |
Byte 6:
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
MS bit of corporate digit 2 |
|
|
LS bit of corporate digit 2 |
MS bit of corporate digit 1 |
|
|
LS bit of corporate digit 1 |
-
Empty fields shall be coded with 'FF'.
-
The end of the list is delimited by the first MCC field coded 'FFF'.
This EF contains the values of STARTCS and STARTPS of the bearers that were protected by the keys in
EFKeys or
EFKeysPS at release of the last CS or PS RRC connection. These values are used to control the lifetime of the keys (see
TS 33.102).
Identifier: '6F5B' | Structure: transparent | Mandatory |
SFI: '0F' | |
File size: 6 bytes | Update activity: high |
Access Conditions:
READ | PIN |
UPDATE | PIN |
DEACTIVATE | ADM |
ACTIVATE | ADM |
|
Bytes |
Description |
M/O |
Length |
1 to 3 | STARTCS | M | 3 bytes |
4 to 6 | STARTPS | M | 3 bytes |
Contents:
Initialisation value for Hyperframe number - CS domain.
Coding:
The LSB of STARTCS is stored in bit 1 of byte 3. Unused nibbles are set to 'F'.
Contents:
Initialisation value for Hyperframe number - PS domain.
Coding: