File Control Parameters

Description

File Control Parameters are a critical component of the UICC (Universal Integrated Circuit Card) and USIM (Universal Subscriber Identity Module) architecture, defined within the framework of the USIM Application Toolkit (USAT). They are metadata associated with every file (both Elementary Files, EFs, and Dedicated Files, DFs) residing on the UICC's file system. These parameters are stored within the file's header or a dedicated administrative file and are read by the terminal (mobile equipment) to understand how to interact with a specific file correctly and securely. The parameters define the file's fundamental characteristics and the rules for accessing its content.

The structure and encoding of FCP are standardized, primarily in 3GPP TS 31.102, which details the USIM characteristics. When a terminal selects a file on the UICC, it receives the File Control Parameters in a response. These parameters include the file size (indicating the number of bytes), the file identifier (a unique 2-byte address), the file's lifecycle status (e.g., created, initialized, operational, terminated), and crucially, the security attributes. The security attributes define the access conditions for various operations like reading, updating, increasing, or invalidating the file. These conditions can be 'always', 'never', or require a specific security context such as successful PIN (CHV) verification, administrative keys (ADM), or never allowing access.

Furthermore, FCP can specify the file's structure, such as whether it is a linear fixed, linear variable, cyclic, or transparent file. For structured files, additional parameters like record length or the number of records are included. The role of FCP is foundational; they act as the rulebook that governs all file system interactions on the smart card. Without correctly interpreting FCP, a terminal could not read subscriber identity (IMSI), network authentication keys (Ki), phonebook entries, or SMS storage. They enforce the security model, preventing unauthorized access to sensitive data and ensuring the integrity of the UICC's file system, which is a trusted environment in the mobile network ecosystem.

Purpose & Motivation

The purpose of File Control Parameters is to provide a standardized, secure, and flexible mechanism for managing the hierarchical file system on a UICC smart card. Before such standardization, proprietary methods for file management led to interoperability issues between different card manufacturers and mobile equipment. The FCP framework solves this by defining a universal set of metadata that any compliant terminal can interpret, enabling seamless interaction with USIMs from any vendor.

Their creation was motivated by the need for a robust security and access control model on the subscriber identity module. The SIM/USIM card stores highly sensitive information, including the subscriber's unique identity (IMSI), long-term authentication key (Ki), and personal data. FCP enforces mandatory access control, ensuring that critical files cannot be read or modified without the proper authentication (e.g., PIN verification). This protects the subscriber from identity theft and the network from fraudulent access. Furthermore, as the USIM evolved from a simple authentication token to a platform for multiple applications (USAT), the FCP system provided the necessary structure to manage a complex, multi-application file system with varying security requirements for different files and applications.

Key Features

• Defines mandatory access conditions for file operations (READ, UPDATE, INVALIDATE, REHABILITATE).
• Specifies file structure type (transparent, linear fixed, cyclic, etc.) and associated size parameters.
• Indicates the file's lifecycle state (e.g., created, initialized, operational).
• Contains the unique file identifier used for file selection commands.
• May include security attributes referencing specific PINs or administrative keys.
• Provides a standardized template (BER-TLV encoded) for interoperable file management.

Evolution Across Releases

Defining Specifications