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

Glossary term · Security

MExE SIM

Mobile Execution Environment Subscriber Identity Module

Security →

MExE SIM is a (U)SIM application that stores a security certificate to enable the secure execution of MExE services and provide a trusted anchor for mobile application security.

Introduced
Rel-4
Where
Services
Specifications
1 specs
MExE SIM Description Purpose What changed Neighbours Specifications

Description

The MExE SIM is a specialised application residing on a (U)SIM card that is capable of storing a security certificate which can be accessed using standardised mechanisms. It forms part of the broader Mobile Execution Environment (MExE) framework defined by 3GPP, which was designed to provide a standardised execution environment for mobile applications and services on user equipment. The MExE SIM acts as a secure element within the UICC, leveraging the tamper-resistant properties of the smart card to protect cryptographic material and certificates from unauthorised access or modification.

Architecturally, the MExE SIM sits within the UICC alongside other SIM/USIM applications. It interfaces with the terminal through the standard ISO/IEC 7816 smart card interface and, in later implementations, through the USB or IP-based UICC-terminal interfaces. The security certificate stored on the MExE SIM can be used for authentication, digital signature generation, and secure key exchange. Standard mechanisms for accessing the certificate include the SIM Application Toolkit (SAT) and, in later releases, the Bearer Independent Protocol (BIP) and the Generic Bootstrapping Architecture (GBA).

The MExE SIM is closely tied to the MExE service architecture, which defines three classes of MExE devices: Class A (supporting both SAT and Java), Class B (supporting Java only), and Class C (supporting SAT only). The MExE SIM provides the security foundation for these devices by offering a trusted storage location for certificates that can be used to authenticate the subscriber to MExE service providers. This is particularly important for services that require a high level of trust, such as mobile banking, corporate email access, and secure VPN connectivity.

In operation, when a MExE application needs to perform a security-sensitive operation, it can request the MExE SIM to use the stored certificate. The SIM verifies the request against its security policy and, if authorised, performs the cryptographic operation internally without exposing the private key. This ensures that even if the terminal is compromised, the certificate remains protected. The standard mechanisms for accessing the certificate are defined in 3GPP TS 22.057 (MExE Stage 1) and TS 21.905 (Vocabulary).

The MExE SIM concept was introduced in Release 4 and has been maintained through Release 19, although its practical deployment has been limited by the rise of alternative secure elements such as the embedded UICC (eUICC) and the integrated secure element in modern smartphones. Nevertheless, it remains a foundational concept in 3GPP security architecture and is referenced in specifications related to UICC-based security services.

Purpose & Motivation

The MExE SIM was created to address the need for a trusted, tamper-resistant storage location for security certificates within the mobile execution environment. Before its introduction, mobile applications had to rely on the terminal's own storage for certificates, which was vulnerable to software attacks and lacked a hardware root of trust. The MExE SIM solves this by leveraging the UICC's secure element, which is physically protected and designed to resist tampering.

Historically, the MExE framework emerged in the early 2000s when mobile operators sought to standardise the execution of applications on mobile devices. The MExE SIM was part of this effort, providing a standardised way to store and access certificates that could be used across different device classes and manufacturers. This was particularly important for enabling interoperable security services such as operator-provided authentication and digital signatures.

The MExE SIM also addressed the problem of certificate portability. By storing the certificate on the SIM, users could move their security credentials between devices simply by moving the SIM card. This was a significant advantage in an era when device replacement was common and users expected their credentials to travel with them. Although the MExE SIM has been largely superseded by more modern secure element technologies, its design principles continue to influence 3GPP security specifications.

What changed in its specifications

The latest release-to-release comparison of specifications that define MExE SIM. 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 →

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.

Rel-4 Initial

Initial definition introduced as 'A SIM that is capable of storing a security certificate that is accessible using standard mechanisms.' This established the foundational concept of a SIM-based certificate store for MExE services.

Definition carried over unchanged from Rel-4, maintaining the same wording and scope.

Wording changed to 'A (U)SIM application that is capable of storing a security certificate that is accessible using standard mechanisms.' The key revision was the shift from 'A SIM' to 'A (U)SIM application', explicitly recognising that the MExE SIM is an application residing on either a SIM or USIM, and broadening the scope to include USIM-based implementations.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Definition carried over unchanged from Rel-6.

Defining Specifications

3GPP specifications that define or reference MExE SIM, 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