Description
Remote File Management (RFM) is a smart-card management capability defined by 3GPP that allows a network operator to read, update, create, and delete files on a UICC (the smart card hosting the USIM, ISIM, and other applications) without requiring the card to be physically present at an operator point of sale. It is closely related to Remote Applet Management (RAM) and is part of the broader Over-the-Air (OTA) management family. RFM is specified in TS 31.117, which defines the RFM procedures and the associated application, and in TS 33.812, which covers the security architecture for remote management of UICC applications.
Architecturally, RFM operates between an OTA server in the operator's network and an RFM application (or agent) on the UICC. The OTA server constructs RFM commands — essentially APDU-level file operations such as SELECT, READ, UPDATE, and file creation/deletion — and delivers them to the card over the air, typically via SMS, BIP (Bearer Independent Protocol), or an IP channel. The card-side RFM application receives the commands, validates them, and executes the file operations against the UICC file system. Responses are returned to the OTA server, giving the operator a reliable request/response mechanism for card management.
Security is a defining aspect of RFM. Because RFM commands can alter subscription parameters, security credentials, and application data, they must be strongly protected. TS 33.812 defines the security architecture, including the use of keys and certificates to authenticate the OTA server to the card and to protect the integrity and confidentiality of RFM commands. RFM commands are typically wrapped in a secure envelope using mechanisms such as the OTA security framework (based on the SCP80/SCP81 secure channel protocols) or the GlobalPlatform secure channel, depending on the deployment. The card verifies the command's integrity and authenticity before executing it, and may enforce access-control rules that restrict which files can be modified by which server.
RFM is used for a wide range of operational tasks: updating the IMSI or other subscription identifiers, provisioning new APNs, updating PLMN lists, changing roaming parameters, installing or updating applets and their associated files, and correcting misconfigured card data. It is especially important for M2M and IoT deployments, where SIMs may be embedded (eSIM/eUICC) or deployed in remote locations and cannot be physically replaced. In these environments, RFM provides the lifecycle management needed to keep subscription data current over the life of the device.
RFM was introduced in Release 8 and carried forward through Release 9. It remains relevant in Release 19, where remote management of UICC and eUICC profiles continues to be important for IoT and consumer eSIM. RFM is closely tied to the OTA platform and to the UICC's own security architecture, and it complements RAM (Remote Applet Management), which focuses on installing and managing applets rather than individual files.
Purpose & Motivation
RFM exists because UICCs are physically distributed across millions of devices and cannot be recalled or manually updated whenever subscription data or card contents need to change. Operators need a way to correct errors, update parameters, and provision new services remotely. Before standardized remote file management, such changes required physical card replacement or manual intervention, which was slow, costly, and impractical at scale — especially for M2M devices in the field.
RFM solves this by defining a standardized, secure protocol for file-level operations on the UICC over the air. It gives operators a reliable mechanism to read and modify card files, with strong authentication and integrity protection so that only authorized servers can make changes. This reduces operational cost, shortens time-to-market for new services, and enables remote troubleshooting.
The motivation has grown with eSIM and IoT. Embedded UICCs and remote devices make physical access impossible, so remote management becomes the only viable lifecycle tool. RFM, together with RAM and the broader OTA framework, provides the standardized foundation for managing card-based subscriptions throughout their lifetime.
What changed in its specifications
The latest release-to-release comparison of specifications that define RFM. Each summary describes the whole specification, not only this term.
Rel-19 added roaming value-added services with remote SIM provisioning security parameters, test message coding, and new terms. It also harmonized test case definitions across RATs by updating references, versions, identifiers, and applicable test sequences.
Full comparison in TS 31.117 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference RFM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 31.117 vj30 | USAT Tests for Non-Removable UICC | Rel-19 read |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 read |