Elementary File

Description

An Elementary File (EF) is a basic, addressable data container residing within the file system of a UICC (Universal Integrated Circuit Card), which includes SIM, USIM, and ISIM applications. The UICC's file system is hierarchically organized, starting with a Master File (MF) as the root, under which are Dedicated Files (DFs) representing applications (like the GSM or USIM application), and within these DFs reside the Elementary Files. Each EF is identified by a unique file identifier (FID) and can be selected using standard ISO/IEC 7816-4 commands. EFs store a wide variety of data, structured as either transparent (a simple sequence of bytes), linear fixed (records of fixed length), cyclic (a fixed number of records where the oldest is overwritten), or BER-TLV (data objects encoded in Tag-Length-Value format).

How an EF works is central to the operation of the UICC. When the mobile device (ME) needs specific data, such as the IMSI for network registration or the authentication key (Ki) for security procedures, it sends a command (e.g., READ BINARY or READ RECORD) to the UICC, specifying the FID of the target EF. The UICC's operating system locates the file, performs any necessary access condition checks (e.g., verifying a PIN), and returns the requested data. For example, the EF_IMSI (file identifier '6F07') stores the International Mobile Subscriber Identity. The ME reads this file during initial registration to identify itself to the network. Similarly, EF_LOCI stores the Location Information, which is updated by the network to allow for efficient paging.

Key components of the EF concept include the file structure, the access conditions, and the associated metadata defined in the EF's header. The header specifies the file type, size, record length (if applicable), and access conditions (e.g., always allowed, PIN1 required, ADM required). EFs are the backbone for storing both mandatory network parameters (like EF_KC for ciphering key in GSM) and optional user data (like EF_PBR for phonebook references). Their role is to provide a standardized, secure, and persistent storage mechanism that is independent of the mobile device, enabling subscriber mobility and secure authentication across different handsets and networks.

Purpose & Motivation

The Elementary File exists to provide a standardized, secure, and organized method for storing critical subscriber and application data on the smart card used in mobile telecommunications (the UICC). It solves the problem of how to persistently manage a wide variety of data—from secret cryptographic keys to public phonebook entries—in a way that is accessible to the mobile equipment but protected from unauthorized access. The motivation for its creation dates back to the original GSM SIM specification, which needed a file system model derived from ISO smart card standards to replace the simple memory storage used in earlier cellular technologies.

The historical context is that prior to the standardized UICC file system, subscriber data and network parameters were often stored in proprietary formats on the mobile device itself, hindering interoperability and subscriber mobility. The introduction of the EF, along with the DF/MF hierarchy, created a universal 'data cabinet' where every piece of information had a known, standardized location and access method. This allowed any compliant mobile device to interact with any compliant SIM card, a cornerstone of GSM's global success. It addressed limitations by separating the subscriber's identity and service profile from the handset, enabling easy swapping of phones while retaining one's number and services, and by enforcing security through file-level access conditions, protecting sensitive data like authentication keys.

Key Features

• Defined by a unique 2-byte File Identifier (FID) and optional short file identifier
• Multiple structural types: Transparent, Linear Fixed, Linear Variable, Cyclic, BER-TLV
• Stores critical data: IMSI (EF_IMSI), authentication keys (EF_Ke/EF_Kc), phonebook (EF_ADN/EF_PBR), SMS (EF_SMS)
• Enforces access conditions (e.g., ALW, CHV, ADM) for security
• Selected via SELECT FILE command using FID or path
• Read/updated using READ/WRITE BINARY or READ/WRITE RECORD commands

Evolution Across Releases

Defining Specifications