TSG-Terminals Working Group 3 (USIM) meeting #3	TSGT3#3(99)075
Helsinki 16th - 18th March, 1999	

Agenda item:	7

Source:	Nippon Ericsson, Mitsubishi Electric (ARIB), NTT DoCoMo

Title:		Proposed new EF structures to support the storage of call detail information

___________________________________________________________________________

1.	Introduction
In the second WG3 meeting in Munich, the requirement for the storage of call detail information in T3#2(99)036[1] was agreed and added into 3GPP 21.11 (T3#2(99)064[2]). This document proposes new EF structure to support the storage of call details listed in chapter 9.3 on 3GPP 21.11[2], except of the accumulated charge.

2.	Proposals

2.1	EF (Mobile Terminated Calls)
This EF contains mobile terminated call's log which has Calling party number and/or the respective supplementary service control strings (SSC), date and time, calling party’s name, status of call, time duration and charge. In addition it contains identifiers of associated network/bearer capabilities.

Identifier: '6F##	Structure: cyclic	Optional	
Record length: X+28 bytes	Update activity: low	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1
	INCREASE	NEVER
	INVALIDATE	ADM
	REHABILITATE	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/Configuration Identifier	M	1 byte	
X+14	Extension1 Record Identifier	M	1 byte	
X+15 to X+21	Date and time	M	7 bytes	
X+22	Status of call	M	1 byte	
X+23 to X+25	Time duration	M	3 bytes	
X+26 to X+28	Charge information	M	3 bytes	

- Alpha Identifier:
Alpha Identifier is Calling party's name of the associated calling party's number.

This Alpha Identifier shall use either the SMS 7 bit coded alphabet, or one of the UCS2 coded options as defined in Annex. B on GSM 11.11. 

NOTE: This field is encoded in the same way as the Alpha Identifier of the EF(ADN).

- Length of BCD Number/SSC contents:
This byte gives the number of bytes of actual BCD number/SSC information.

NOTE: This field is encoded in the same way as the Length of BCD umber/SSC contents of the EF(ADN).

- TON and NPI:
This is value for Type of number (TON) and numbering plan identification (NPI).

If the Dialling Number/SSC String does not contain a dialling number, e.g. a control string deactivating a service, the TON/NPI byte shall be set to 'FF' by the ME.

NOTE: This field is encoded in the same way as the TON and NPI of the EF(ADN).

- Dialing Number/SSC String:
Dialling number is calling party’s telephone number. Up to 20 digits of the telephone number  and/or SSC information shall be stored in this data item.

If the telephone number or SSC is longer than 20 digits, the first 20 digits are stored in this data item and the remainder is stored in an associated record in the EF(EXT1). The record is identified by the Extension1 Record Identifier. If the telephone number/SSC require less than 20 digits, excess nibbles at the end of the data item shall be set to 'F'. Where individual dialled numbers, in one or more records, of less than 20 digits share a common appended digit string the first digits are stored in this data item and the common digits stored in an associated record in the EF(EXT1). The record is identified by the Extension 1 Record Identifier. Excess nibbles at the end of the data item shall be set to 'F'.

NOTE: This field is encoded in the same way as the Dialling Number/SSC String of the EF(ADN).

- Capability/Configuration Identifier:
This is capability/configuration identification byte. This byte identifies the number of a record in the EF(CCP) containing associated capability/configuration parameters required for the call. The use of this byte is optional. If it is not used it shall be set to 'FF'.

NOTE: This field is encoded in the same way as the Capability/Configuration Identifier of the EF(ADN).

‑ Extension1 Record Identifier:
This is extension1 record identification byte. This byte identifies the number of a record in the EF(EXT1) containing an associated called party subaddress or additional data. The use of this byte is optional. If it is not used it shall be set to 'FF'.

NOTE: This field is encoded in the same way as the Extension1 Record Identifier of the EF(ADN).

- Date and Time
This is value of Date and time when the call is happening. Date and time field is given in semi‑octet representation, and represents the local time in the following way:

	Year:	Month:	Day:	Hour:	Minute:	Second:	Time Zone	
Digits:
(Semi‑octets)	2	2	2	2	2	2	2	

The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. In the first of the two semi‑octets, the first bit represents the algebraic sign of this difference (0 : positive, 1:negative).

This date item is encoded in the same way as the TP-Service-Centre-Time-Stamp in GSM 03.40.

Byte X+15 (The year field):
b8	b7	b6	b5	b4	b3	b2	b1		

									LSB of Digit 1	
									   :	
									   :	
									MSB of Digit 1	
									LSB of Digit 2	
									   :	
									   :	
									MSB of Digit 2	

Etc.

- Status of call
This is the status of call when incoming call happened. (i.e. answered or missed)

Byte X+22:
b8	b7	b6	b5	b4	b3	b2	b1		

									Answered	
									Not Answered	
									Reserved	
									Reserved	
									Reserved	
									Reserved	
									Reserved	
									Reserved	

- Time duration 
This is the value of the time duration for the call. It is possible to store up to 24 bit seconds (approximately 4660 hours).

Byte X+23:
b8	b7	b6	b5	b4	b3	b2	b1		

									216	
									217	
									218	
									219	
									220	
									221	
									222	
									223	

Byte X+24:
b8	b7	b6	b5	b4	b3	b2	b1		

									28	
									29	
									210	
									211	
									212	
									213	
									214	
									215	

Byte X+25:
b8	b7	b6	b5	b4	b3	b2	b1		

									20	
									21	
									22	
									23	
									24	
									25	
									26	
									27	

For instance, '00' 00' '30' represents 25+24 .(48 seconds)

- Charge information
This data item is the number of units for the call.

Byte X+26:
b8	b7	b6	b5	b4	b3	b2	b1		

									216	
									217	
									218	
									219	
									220	
									221	
									222	
									223	

Byte X+27:
b8	b7	b6	b5	b4	b3	b2	b1		

									28	
									29	
									210	
									211	
									212	
									213	
									214	
									215	

Byte X+28:
b8	b7	b6	b5	b4	b3	b2	b1		

									20	
									21	
									22	
									23	
									24	
									25	
									26	
									27	

NOTE: This field is encoded in the same way as the EF(ACMmax).

2.2	EF (Mobile Originated Calls)
This EF contains mobile originated call's logs which has Calling party number and/or the respective supplementary service control strings (SSC), date and time, calling party’s name, time duration and charge. In addition it contains identifiers of associated network/bearer capabilities.

Identifier: '6F##	Structure: cyclic	Optional	
Record length: X+27 bytes	Update activity: low	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1
	INCREASE	NEVER
	INVALIDATE	ADM
	REHABILITATE	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/Configuration Identifier	M	1 byte	
X+14	Extension1 Record Identifier	M	1 byte	
X+15 to X+21	Date and time	M	7 bytes	
X+22 to X+24	Time duration	M	3 bytes	
X+25 to X+27	Charge information	M	3 bytes	

NOTE: See chapter 2.1 in this documentation in detail.

2.3	EF (Accumulated time duration of the preceding calls for Originated Calls)
This EF contains the total time duration for both the current call and the preceding calls.

Identifier: '6F##'	Structure: transparent	Optional	
File size: 3 bytes	Update activity: high	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1/CHV2
		(fixed during administrative management)

	INVALIDATE	ADM
	REHABILITATE	ADM
	
Bytes	Description	M/O	Length	
1 – 3	Accumulated time duration	M	3 bytes	

‑ Accumulated time duration
This data item is the total number of seconds for both the current call and the preceding calls for originated calls. It shall store up to 24 bit seconds (approximately 4660 hours).

NOTE: This is the same data format as the time duration of the EF (Mobile terminated call) which is proposed in chapter 2.1 of this documentation.

2.4	EF (Accumulated time duration of the preceding calls for Terminated Calls)
This EF contains the total time duration for both the current call and the preceding calls.

Identifier: '6F##'	Structure: transparent	Optional	
File size: 3 bytes	Update activity: high	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1/CHV2
		(fixed during administrative management)
INVALIDATE	ADM
	REHABILITATE	ADM
	
Bytes	Description	M/O	Length	
1 – 3	Accumulated time duration	M	3 bytes	

‑ Accumulated time duration
This data item is the total number of seconds for both the current call and the preceding calls for terminated calls. It shall store up to 24 bit seconds (approximately 4660 hours).

NOTE: This is the same data format as the time duration of the EF (Mobile terminated call) which is proposed in chapter 2.1 of this documentation.

3.	References
[1] T3#2(99)036: Proposed texts for Stage 1 (requirements) (source: Nippon Ericsson)
[2] T3#2(99)064: 21.11 version 1.2.0 "USIM and UICC requirements for 3G systems (source: TSG-T3)
[3] GSM 03.40: Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)
[4] GSM 11.11: Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module -Mobile Equipment (SIM - ME) interface