4.2.47 EFEST (Enabled Services Table)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
If service n° 2, 6, 34 or 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 n1 to n8 |
M |
1 byte |
|||
|
2 |
Services n9 to n16 |
O |
1 byte |
|||
|
etc. |
||||||
|
X |
Services n(8X-7) to n(8X) |
O |
1 byte |
|||
|
‑Services |
||
|
Contents: |
Service n°1: |
Fixed Dialling Numbers (FDN) |
|
Service n°2: |
Barred Dialling Numbers (BDN) |
|
|
Service n°3: |
APN Control List (ACL) |
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then the EF shall also contain all bytes before that byte. Other services are possible in the future. The coding falls under the responsibility of the 3GPP.
Coding:
– 1 bit is used to code each service:
– bit = 1: service activated;
– bit = 0: service deactivated.
– Unused bits shall be set to ‘0’.
A service which is listed in this table is enabled if it is indicated as available in the USIM Service Table (UST) and indicated as activated in the Enabled Services Tables (EST) otherwise this service is, either not available or disabled.
First byte:
|
b8 |
b7 |
b6 |
B5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
Service n°1 |
|||||||||||||||||||
|
Service n°2 |
|||||||||||||||||||
|
Service n°3 |
|||||||||||||||||||
|
Service n°4 |
|||||||||||||||||||
|
Service n°5 |
|||||||||||||||||||
|
Service n°6 |
|||||||||||||||||||
|
Service n°7 |
|||||||||||||||||||
|
Service n°8 |
|||||||||||||||||||
etc.