4.2.33 EF_ICI (Incoming Call Information)

31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS

If service n°9 is "available", this file shall be present.

This EF is located within the USIM application. The incoming call information can be linked to the phone book stored under DF_TELECOM or to the local phone book within the USIM. The EF_ICI contains the information related to incoming calls.

The time of the call and duration of the call are stored in this EF. This EF can also contain associated alpha identifier that may be supplied with the incoming call. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM ADF level. The structure of this EF is cyclic, so the contents shall be updated only after a call is disconnected.

If CLI is supported and the incoming phone number matches a number stored in the phone book the incoming call information is linked to the corresponding information in the phone book. If the incoming call matches an entry but is indicated as hidden in the phone book the link is established but the information is not displayed by the ME if the code for the secret entry has not been verified. The ME shall not ask for the secret code to be entered 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 incoming call number still exits 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’.

The first byte of this link is used to identify clearly the phone book location either global (i.e. under DF_TELECOM) or local (i.e. USIM specific). To allow the reuse of the referring mechanism in further implementation of the phonebook under discussion, this byte can be used to indicate those.

For the current version of the phone book, the phone book entry is identified as follows:

– the record number in the EF_PBR which indicates the EF_ADN containing the entry;

– the record number inside the indicated EF_ADN.

The structure of EF_ICI is shown below. Coding scheme is according to EF_ADN

Structure of EF_ICI

Identifier: ‘6F80’		Structure: Cyclic			Optional
SFI: ’14’
Record length: X+28 bytes			Update activity: high
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM
Bytes	Description			M/O		Length
1 to X	Alpha Identifier			O		X bytes
X+1	Length of BCD number contents			M		1 byte
X+2	TON and NPI			M		1 byte
X+3 to X+12	Incoming Call Number			M		10 bytes
X+13	Capability/Configuration2 Record Identifier			M		1 byte
X+14	Extension5 Record Identifier			M		1 byte
X+15 to X+21	Incoming call date and time (see detail 1)			M		7 bytes
X+22 to X+24	Incoming call duration (see detail 2)			M		3 bytes
X+25	Incoming call status (see detail 3)			M		1 byte
X+26 to X+28	Link to phone book entry (see detail 4)			M		3 bytes

NOTE: When the contents except incoming call status are invalid, they are filled with ‘FF’.

Detail 1 Coding of date and time.

Content:
the date and time are defined by the ME.

Coding:
it is according to the extended BCD coding from Byte1 to Byte 7. The first 3 bytes show year, month and day (yy.mm.dd). The next 3 bytes show hour, minute and second (hh.mm.ss). The last Byte 7 is Time Zone. The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. Bit 4 in Byte 7 represents the algebraic sign of this difference (0: positive, 1: negative). If the terminal does not support the Time Zone, Byte 7 shall be "FF". Byte X+15: Year.

B8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit year

MSB of first digit year

LSB of second digit year

MSB of second digit year

Byte X+16: Month

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit month

MSB of first digit month

LSB of second digit month

MSB of second digit month

Byte X+17: Day

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit day

MSB of first digit day

LSB of second digit day

MSB of second digit day

Byte X+18: Hour

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit hour

MSB of first digit hour

LSB of second digit hour

MSB of second digit hour

Byte X+19: Minute

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit minute

MSB of first digit minute

LSB of second digit minute

MSB of second digit minute

Byte X+20: Second

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit second

MSB of first digit second

LSB of second digit second

MSB of second digit second

Byte X+21: Time Zone

b8

b7

b6

b5

b4

b3

b2

b1

LSB of first digit indicates by quarters an hour

MSB of first digit indicates by quarters an hour

the algebraic sign (0: positive, 1: negative)

LSB of second digit indicates by quarters an hour

MSB of second digit indicates by quarters an hour

Detail 2 Coding of call duration.

Call duration is indicated by second.

Byte X+22:

		b8		b7		b6		b5		b4		b3		b2		b1
		223		222		221		220		219		218		217		216

Byte X+23:

		b8		b7		b6		b5		b4		b3		b2		b1
		215		214		213		212		211		210		29		28

Byte X+24:

		b8		b7		b6		b5		b4		b3		b2		b1
		27		26		25		24		23		22		21		20

For instance, ’00’ ’00’ ’30’ represents 25+24.

Detail 3 Coding of Call status.

Byte X+25:

b8

b7

b6

b5

b4

b3

b2

b1

Answered=’0’/ Not Answered=’1′

RFU

Detail 4 Link to phone book entry

For the current implementation of the phone book the following coding applies:

Phone book reference.

Byte X+26:

b8

b7

b6

b5

b4

b3

b2

b1

0 Global Phone Book (DFTELECOM) 1 Local Phone Book (USIM Specific)

RFU

EF_PBR record number:

– Byte X+27: Hexadecimal value.

EF_ADN record number:

– Byte X+28: Hexadecimal value.