Description
SIM Application Toolkit (SAT) procedures define the standardized mechanism by which applications residing on the UICC (the smart card, commonly referred to as the SIM) can proactively send commands to the Mobile Equipment (ME), i.e., the mobile phone or modem. This is a significant departure from the traditional model where the ME is the master and the UICC is a passive slave that only responds to requests. With SAT, the UICC becomes an active entity capable of initiating actions, displaying menus, sending short messages, initiating calls, and interacting with the user through the ME's user interface.
The technical foundation of SAT procedures lies in the communication protocol between the ME and the UICC, as specified in the 3GPP 31.111 series (and historically GSM 11.14). The protocol defines a set of commands — known as proactive commands — that the UICC can send to the ME. These commands include DISPLAY TEXT, GET INPUT, SELECT ITEM, SEND SHORT MESSAGE, SET UP CALL, PROVIDE LOCAL INFORMATION, and many others. The ME executes these commands and returns a terminal response indicating success or failure, along with any requested data. This request-response exchange is governed by a set of procedures that ensure orderly execution, error handling, and compatibility between different UICC and ME implementations.
SAT procedures operate within the broader context of the UICC-ME interface, which is based on the ISO/IEC 7816 series of standards for smart card communication. The ME polls the UICC for proactive commands using the FETCH function, or the UICC indicates pending commands via status words. The ME must support a certain set of SAT capabilities, which are indicated in the TERMINAL PROFILE sent to the UICC during initialization. The UICC, in turn, provides its own profile in the SIM Application Toolkit Data (EFSAT) file, allowing both sides to negotiate which commands and features are supported. This negotiation is essential for backward compatibility and for ensuring that applications work across a wide range of devices.
SAT procedures enable a variety of value-added services. For example, a SIM-based application can present a menu to the user for selecting services, send an SMS to a service provider, initiate a voice call to a customer care center, or display information such as roaming charges. In machine-to-machine (M2M) and IoT contexts, SAT procedures allow the SIM to autonomously trigger actions, such as sending location updates or configuring the device. The procedures also support security features, including the ability to verify the user's identity via PIN entry and to manage access control to SIM applications.
The evolution of SAT procedures has been driven by the need to support increasingly sophisticated applications and to adapt to new network technologies. In later releases, the toolkit was extended to support USIM Application Toolkit (USAT) for 3G and beyond, adding features such as support for IP-based communication, enhanced security, and interaction with the ME's browser. The procedures continue to be maintained and updated in 3GPP specifications to ensure interoperability and to address new use cases, such as embedded SIM (eSIM) and remote SIM provisioning.
Purpose & Motivation
SIM Application Toolkit procedures were created to overcome the inherent limitation of the traditional SIM-ME relationship, where the SIM was a passive storage and security element that could only respond to commands from the ME. This limitation meant that any value-added service had to be implemented in the ME or in the network, leaving the SIM as a mere repository of subscriber credentials. Network operators wanted a way to deploy services directly on the SIM, independent of the handset manufacturer, to ensure consistent user experience and to reduce time-to-market for new offerings.
The introduction of SAT procedures in the late 1990s (standardized in GSM 11.14) provided a standardized mechanism for the SIM to become an active participant in service delivery. It allowed operators to embed applications on the SIM that could present menus, collect user input, send SMS, and initiate calls, all without requiring changes to the handset software. This was particularly important in a market where handsets were diverse and often closed to operator customization.
Over time, SAT procedures evolved into USAT to support 3G and LTE networks, adding capabilities such as IP communication and interaction with the ME's browser. The procedures also became foundational for M2M and IoT applications, where the SIM can autonomously manage connectivity and security. The ongoing relevance of SAT procedures demonstrates their success in solving the problem of operator-controlled service delivery at the SIM level.
What changed in its specifications
The latest release-to-release comparison of specifications that define SIM application toolkit procedures. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →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 SIM application toolkit procedures, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |