10 Contents of the Elementary Files
21.1113GPPRelease 17TSUSIM and IC card requirements
10.1 USIM information storage requirements
The USIM shall contain information elements for 3G network operations. The USIM may contain information elements related to the subscriber, 3G services and home environment or service provider related information.
The UICC shall provide storage capability for the following:
– UICC related information:
– IC card identification: a number uniquely identifying the UICC and the card issuer;
– Preferred language(s);
– Directory of applications.
– USIM related information:
– Administrative information: indicates mode of operation of the USIM, e.g. normal, type approval;
– USIM service table: indicates which optional services are provided by the USIM;
– IMSI;
– Language indication;
– Location information;
– Cipher key (Kc) and cipher key sequence number;
– Access control class(es);
– Forbidden PLMNs;
– Ciphering Key for GPRS;
– GPRS location information;
– Cell Broadcast related information;
– Emergency call codes;
– Phone numbers (ADN, FDN, SDN);
– Short messages and related parameters;
– Capability and Configuration parameters;
– Higher Priority PLMN search period;
– list of carrier frequencies to be used for cell selection.
– Information accessible to the USIM and other applications:
– ADN.
In addition, the USIM shall manage and provide storage for the following information in accordance with the security requirements of clause 5:
– PIN;
– PIN enabled/disabled indicator;
– PIN error counter;
– Unblock PIN;
– Unblock PIN error counter;
– Data integrity keys;
– Subscriber authentication keys.
10.2 Phone Book
A Phone Book entry consists of a record in an ADN file and, optionally, additional records which are placed in different EFs. In the latter case, a mechanism shall be defined to link all records in the same Phone Book entry. These features shall be supported by the ME while their support by the UICC is optional.
10.2.1 Support of two name fields per entry
The support of two name fields per entry shall be specified to allow, for example, for two different representations of the same name (for example, in Japanese characters and in Latin characters).
10.2.2 Support of multiple phone numbers per entry
The support of multiple phone numbers per entry shall be specified, for example, office, home, fax, mobile or pager. In addition to that, information for identifying those attributes are needed.
10.2.3 Support of email address
The support of email addresses linked to Phone Book entries shall be specified. In addition to that, information for identifying these addresses is needed.
10.2.4 Support of user definable groupings
The specification shall support the grouping of Phone Book entries into groups defined by the user, for example, business and private.
10.2.5 Support of hidden entries
The specification shall support means of marking Phone Book entries as "hidden".
10.2.6 Number of entries
The specification shall support storage of at least 500 entries.
10.2.7 Void
10.3 Storage of call details
The specification shall support provision of storage for call detail information. The call detail information consists of the following attributes:
– mobile terminated calls:
calling party number, date and time, calling party’s name and status of call (i.e. answered or missed), duration;
– mobile originated calls:
called party number, date and time, called party’s name and duration;
– accumulated duration of preceding calls, separately for mobile originated and mobile terminated calls.
Call detail attributes are optional. A value to mark them as "undefined" shall be available.
NOTE 1: The calling/called party’s name may be available from the Phone Book.