If service No. 8 is "available", this file shall be present.
This EF is located within the USIM application. The outgoing call information can be linked to the phone book stored under DFTELECOM or to the local phone book within the USIM. The EFOCI contains the information related to outgoing calls.
The time of the call and duration of the call are stored in this EF. It may also contain associated alpha identifier. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM ADF level. The structure of this file is cyclic, so the contents shall be updated only after a call is disconnected.
If the dialled phone number matches a number stored in the phone book the outgoing call information might be linked to the corresponding information in the phone book. The dialled number may match with a hidden entry in the phone book. If the dialled number matches a hidden entry in the phone book the link is established but the information related to the phone book entry is not displayed by the ME, if the hidden code has not been verified. The ME shall not perform hidden code verification at this point.
Optionally, the ME may store the link to phone book entry in the file, so that it does not need to look again for a match in the phone book when it reuses the entry. But the ME will have to check that the outgoing call number still exists in the linked phone book entry, as the link might be broken (entry modified). When not used by the ME or no link to the phone book has been found, this field shall be set to 'FFFFFF'.
Coding scheme is according to EFICI.
Structure of EFOCI
If service No. 9 is "available", this file shall be present.
This EF contains the accumulated incoming call timer duration value for the current call and previous calls. The EF is USIM specific and resides within the USIM application.
This file should have only one entry.
Structure of EFICT
Identifier: '6F82'
Structure: cyclic
Optional
Record length: 3 bytes
Update activity: high
Access Conditions:
READ
PIN
UPDATE
PIN/PIN2 (fixed during administrative management)
INCREASE
PIN
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to 3
Accumulated call timer value
M
3 bytes
Coding:
Accumulated call timer value is indicated by second.
Byte 1:
If service No. 8 is "available", this file shall be present.
This EF contains the accumulated outgoing call timer duration value for the current call and previous calls. The EF is USIM specific and resides within the USIM application. The contents of this EF shall be updated only after a call is disconnected. The coding of this EF is the same as EFICT.
This file should have only one entry.
Structure of EFOCT
If service No. 14 is "available", this file shall be present.
This EF contains parameters of required network and bearer capabilities and terminal configurations associated with a call established using a fixed dialling number, a barred dialling number, an MSISDN, a service dialling number, an incoming call, an outgoing call or an MBDN. It is referred by EFFDN, EFBDN, EFMSISDN, EFSDN, EFICI, EFOCI, EFMBDN and EFCFIS at USIM ADF level.
Identifier: '6F4F'
Structure: linear fixed
Optional
SFI: '16'
Record length: X bytes, X≥15
Update activity: low
Access Conditions:
READ
PIN
UPDATE
PIN
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to X
Bearer capability information element
M
X bytes
Bearer capability information elements
Contents and Coding:
see TS 24.008. The Information Element Identity (IEI) shall be excluded, i.e. the first byte of the EFCCP2 record shall be Length of the bearer capability contents.
If service No. 24 is "available", this file shall be present.
This EF contains information about priority levels and fast call set-up conditions for the enhanced Multi Level Precedence and Pre-emption service that can be used by the subscriber.
Identifier: '6FB5'
Structure: transparent
Optional
File size: 2 bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
ADM
DEACTIVATE
ADM
ACTIVATE
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
0
priority level 4
priority level 3
priority level 2
priority level 1
priority level 0
priority level B
priority level A
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
0
fast call set-up condition for priority level 4
fast call set-up condition for priority level 3
fast call set-up condition for priority level 2
fast call set-up condition for priority level 1
fast call set-up condition for priority level 0
fast call set-up condition for priority level B
fast call set-up condition for priority level A
EXAMPLE 2:
If fast call set-up is allowed for priority levels 0, and 1, then byte 2 of EFeMLPP is coded '0C'.
If service No. 25 is "available", this file shall be present.
This EF contains those priority levels (of the Multi Level Precedence and Pre-emption service) for which the ME shall answer automatically to incoming calls.
Identifier: '6FB6'
Structure: transparent
Optional
File size: 1 byte
Update activity: low
Access Conditions:
READ
PIN
UPDATE
PIN
DEACTIVATE
ADM
ACTIVATE
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
0
Automatic answer priority for priority level 4
Automatic answer priority for priority level 3
Automatic answer priority for priority level 2
Automatic answer priority for priority level 1
Automatic answer priority for priority level 0
Automatic answer priority for priority level B
Automatic answer priority for priority level A
EXAMPLE:
If automatic answer is allowed for incoming calls with priority levels A, 0 and 1, then EFAaeM is coded '0D'.
This EF contains the hidden key that has to be verified by the ME in order to display the phone book entries that are marked as hidden. The hidden key can consist of 4 to 8 digits.
Identifier: '6FC3'
Structure: transparent
Optional
File size: 4 bytes
Update activity: low
Access Conditions:
READ
PIN
UPDATE
PIN
DEACTIVATE
ADM
ACTIVATE
ADM
Bytes
Description
M/O
Length
1 to 4
Hidden Key
M
4 bytes
Hidden Key
Coding:
the hidden key is coded on 4 bytes using BCD coding. The minimum number of digits is 4. Unused digits are padded with 'F'.
