Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

USAT

Universal Subscriber Identity Module Application Toolkit

Services →

USAT is a standardized execution environment and API within a UICC/USIM that securely runs operator-provisioned applications to enable value-added services like SIM menus and secure authentication.

Introduced
R99
Where
Services › IMS
Specifications
15 specs
Also in
User Equipment
USAT Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Universal Subscriber Identity Module Application Toolkit (USAT) is a comprehensive framework, standardized by 3GPP and ETSI, that turns a traditional SIM card into a secure, programmable platform capable of hosting and executing applications. It is essentially the application layer that runs on top of the underlying UICC (Universal Integrated Circuit Card) hardware and USIM (Universal Subscriber Identity Module) logical structure. USAT defines a set of commands, procedures, and an execution environment that allows applets—small applications written in Java Card or Native code—to interact with the mobile device (the Terminal Equipment or ME) and, through it, with the mobile network and external services. The architecture is based on a proactive model: the USAT application on the UICC can send "Proactive Commands" to the ME. These commands instruct the ME to perform actions such as displaying text menus, playing tones, setting up calls, sending Short Message Service (SMS) messages, or providing location information. The ME executes the command and sends a "Terminal Response" back to the UICC with the result. This interaction is managed through the ETSI-defined "AT" command interface. Key components include the USAT Interpreter for processing commands, the File System for storing applets and data, and the Security Domain for managing cryptographic keys and secure channel protocols like OTA (Over-The-Air) for remote application management. USAT enables services like SIM Toolkit (STK) menus for banking or info services, OTA provisioning of device settings (e.g., internet access points), and is the foundation for more advanced secure elements used in mobile financial services (e.g., NFC payments via SIM). It provides a trusted, tamper-resistant environment isolated from the phone's main operating system, which is crucial for security-sensitive operations.

Purpose & Motivation

USAT was developed to unlock the potential of the SIM card beyond its original purpose of subscriber authentication and storage of network parameters. In the early days of GSM, the SIM was a relatively static component. USAT, evolving from the earlier SIM Application Toolkit (SAT), was created to provide a standardized, vendor-independent platform for mobile network operators to deploy and manage value-added services directly from the secure SIM card. This solved several problems: it gave operators control over service delivery independent of handset manufacturers, provided a ubiquitous secure execution environment across all compliant phones, and enabled services that required a high level of trust, such as mobile banking. Before USAT, introducing new features often required handset firmware updates or proprietary solutions, which were slow and fragmented. USAT established a universal ecosystem where operators could write an application once and deploy it OTA to millions of subscribers' SIMs, knowing it would work on any compliant device. This motivated the creation of a wide range of services, from simple info menus to complex payment and identity applications, establishing the SIM as a key platform for mobile commerce and secure services in the 2G/3G/4G eras, a role that continues to evolve with embedded SIM (eSIM) and IoT applications.

What changed in its specifications

The latest release-to-release comparison of specifications that define USAT. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 22.038Rel-4 → Rel-5

Rel-5 added USAT definitions, proactive key press indication, ISIM reference, and removed network-specific bearer and communication control restrictions.

Full comparison in TS 22.038 →

Technology family

Subscriber identity modules · User Equipment › SIM/USIM

  1. Phase 1 IC card SIM, ID-1 SIM, Plug-in SIM, SIM
  2. R96 proactive SIM, SAT
  3. R99 UICC, USAT, USIM
  4. Rel-5 ISIM
  5. Rel-17 MUSIM

Also in this family (introduction release not pinned to a single defining specification): eSIM, eUICC

  • USAT succeeds SAT
    “This is because of backward compatibility with SAT: several options existed in SAT for a given facility, and they are mandatory in USAT when this facility is supported.” TS 31.111

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 16 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

USAT is specified for the first time in R99: TS 22.038 gives the stage-one service requirements and TS 31.111 defines the USAT commands, procedures and profile download mechanism.

  • “SAT/USAT provides a standardised execution environment for applications stored on the (U)SIM card and the ability to utilize certain functions” TS 22.038 v3.4.0
  • “USAT is a set of commands and procedures for use during the network operation phase of 3G” TS 31.111 v3.14.0
  • “USAT: set of applications and related procedures that may be used during a 3G session.” TS 31.111 v3.14.0
Rel-4 specification text

USAT requirements and procedures were specified: the security requirement on the SAT/USAT environment, USAT-specific proactive commands, error causes, optional ME support, and Bearer Independent Protocol annexes for local links.

  • “In addition to the proactive commands listed in ETSI TS 102 223 [32], an UICC supporting USAT can issue the following proactive commands:” TS 31.111 v4.17.0
  • “The support of USAT implies the support of CAT (ETSI TS 102 223 [32]).” TS 31.111 v4.17.0
  • “The enhancement of the (U)SIM card by SAT/USAT shall not reduce nor endanger the current security.” TS 22.038 v4.3.0
Rel-5 specification text

Rel-5 first specifies the USAT Interpreter byte codes (TS 31.113) and protocol (TS 31.114), and restates USAT requirements for a UICC-based execution environment in TS 22.038.

  • “The present document specifies the byte codes that are recognised by an USAT Interpreter.” TS 31.113 v5.6.0
  • “The present document specifies the transmission protocol to be used to communicate with the USAT Interpreter” TS 31.114 v5.3.0
  • “USAT provides a standardised execution environment for applications stored on the UICCand the ability to utilize certain functions of the supporting mobile equipment.” TS 22.038 v5.4.0
Rel-6 specification text

USAT Interpreter error and exception handling was specified (e.g. 'Syntax error', 'Type mismatch', 'Jump to undefined'), and USAT gained MMS presentation and management capabilities and data exchange capability wording.

  • “If TLVs are expected by the USAT Interpreter and are missing the execution result of the byte code shall be "Syntax error"” TS 31.113 v6.3.0
  • “The USAT shall be able to request the ME to present to the user a Multimedia Message” TS 22.038 v6.5.0
  • “In case of error generated by the plug-in execution, the USAT interpreter shall execute the "Error during plug-in execution" exception case” TS 31.113 v6.3.0
Rel-7 specification text

USAT specifications were extended in Rel-7: the USAT Interpreter gained defined behaviours (page rendering, events, terminal response handling) and USAT bearer and ME interaction requirements were added.

  • “the USAT Interpreter shall extract the General Result byte from the Result TLV of the Terminal Response structure” TS 31.113 v7.0.0
  • “The ME supporting bearer independent protocol shall provide to the USIM a common interface for any type of data bearer.” TS 22.038 v7.5.0
  • “Details about how this mechanism is used for USAT are defined in TS 102 223 [32] clause 6.1.” TS 31.111 v7.17.0
Rel-8 1 CR

USAT gained support for EPS (BIP, Provide Local Information, Call control) and a new mode of operation for reduced-capability terminals, with USAT requirements extended to 3G/LTE.

  • Support of EPS in USAT: BIP, Provide Local Information, Call control TS 31.111CR201
  • “Annex P (normative): Support of USAT by Terminals with reduced feature capabilities.” TS 31.111 v8.15.0
  • “USAT is a set of commands and procedures for use during the network operation phase of 3G/LTE” TS 31.111 v8.15.0
Rel-9 specification text

The mandatory support for Home eNodeB name in USAT was removed, changing the capability requirements of USAT.

Rel-10 1 CR

USAT gained new requirements in Rel-10: USAT over the AT interface with default routing rules, multiple entities providing USAT facilities, and corrections to IMS-related USAT commands.

  • “In addition to the mechanism defined in ETSI TS 102 223 [32], the MT shall route USAT commands as follows:” TS 31.111 v10.17.0
  • “4.17 USAT over the AT interface” TS 31.111 v10.17.0
  • Removal of the mandatory Home eNodeB name support in USAT TS 31.111CR0296
Rel-11 specification text

A NOTE stating the preferred way for a USAT application to indicate a Data Download error, using status code '62 XX' or '63 XX', was removed from the specification.

  • “The preferred way for a USAT application to indicate a Data Download error is by using the specific code '62 XX' or '63 XX'” TS 31.111 v11.14.0
Rel-12 1 CR

USAT URI support was clarified regarding interactions with FDN_URI and BDN_URI, and default routing for USAT over the AT interface was corrected.

  • “URI support by USAT clarification on the interactions with FDN_URI and BDN_URI” TS 31.111 v12.12.0
  • Essential correction to default routing for USAT over AT interface references TS 31.111CR0388
Rel-13 2 CRs

Rel-13 added USAT features: WLAN bearer alignment of USAT and URI support for USAT SMS-related features, listed as ME functions with optional support.

  • WLAN Bearer alignment of USAT TS 31.111CR0424
  • URI support by USAT SMS related features TS 31.111CR0434
  • “Support of USAT is optional for Mobile Equipment.” TS 31.111 v13.8.0
Rel-14 1 CR

USAT gained support for URI handling within its SMS-PP Download feature in Rel-14, as an added capability of the toolkit.

Rel-16 2 CRs

Rel-16 corrected 5G USAT test cases and updated the USAT applicability table in the 31.124 conformance test specification.

  • Corrections to 5G USAT test cases TS 31.124CR0598
  • Update of the USAT applicability table TS 31.124CR0622
Rel-17 1 CR

USAT in Rel-17 gained new requirements: the ME stores SOR-CMCI received in the USAT REFRESH command, and REFRESH rules apply for new EFs changed via USAT, plus Satellite E-UTRAN support.

  • “The ME shall store the SOR-CMCI received in the USAT REFRESH command accordingly to TS 23.122 [7].” TS 31.111 v17.14.0
  • Satellite E-UTRAN in USAT TS 31.111CR0771
  • “When an EFDRI is changed in the USIM via Data Download or a USAT application and a REFRESH command is issued” TS 31.111 v17.14.0
Rel-18 1 CR

USAT gained support for multiple LSEs on a UICC, with proactive sessions run per selected LSE in parallel, and USAT REFRESH was extended for updating the SENSE operator threshold.

  • “If a UICC supports multiple LSEs as defined in TS 31.101 [13], USAT can separately be used for each LSE.” TS 31.111 v18.12.0
  • Adding USAT REFRESH for updating operator threshold for SENSE TS 23.122CR1073
Rel-19 1 CR

Files used for USAT application testing were updated in the test specification to cover USAT up to Rel-19.

  • Update of files to support USAT application testing up to Rel-19 TS 31.124CR0852

Defining Specifications

3GPP specifications that define or reference USAT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.038 vj00 USIM Application Toolkit (USAT) Stage 1 Rel-19 read
TS 22.112 v800 USAT Interpreter for Secure Narrowband Channel Rel-8 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 27.007 vk00 AT Command Interface for Mobile Terminals Rel-20 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.111 vj40 3GPP TS 31111 vj40: USIM Application Toolkit Rel-19 read
TS 31.112 v800 USAT Interpreter System Architecture and Functionality Rel-8 read
TS 31.113 v800 USAT Interpreter Byte Codes Specification Rel-8 read
TS 31.114 v800 USAT Interpreter Transmission Protocol Rel-8 read
TS 31.117 vj30 USAT Tests for Non-Removable UICC Rel-19 read
TR 31.901 ve00 USIM/ISIM/USAT Feature Review Study Rel-14 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read