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

Glossary term · Security

ISIM

IMS Subscriber Identity Module

Security →

ISIM is an application on a UICC that securely stores a subscriber's IMS identity and credentials to enable authentication and access to services like VoLTE.

Introduced
Rel-5
Where
Services › IMS
Specifications
18 specs
Also in
Core Network, Security, User Equipment
ISIM Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The IMS Subscriber Identity Module (ISIM) is a specialized software application residing on a Universal Integrated Circuit Card (UICC), commonly known as a SIM card. It is distinct from the classic SIM application used for cellular network access (CS domain) and the USIM application for 3G/4G packet access (PS domain). The ISIM application is dedicated exclusively to the IP Multimedia Subsystem (IMS), which provides multimedia services like Voice over LTE (VoLTE), video calls, and instant messaging over the mobile packet core.

Architecturally, the ISIM contains a set of securely stored files and parameters essential for IMS registration and service invocation. The most critical data is the IMS Private User Identity (IMPI), a unique global identifier for the subscriber in the IMS realm (often formatted like a NAI, e.g., user@domain.com). It also stores the corresponding IMS Public User Identity (IMPU), which is the address used for communication (e.g., a SIP URI). Furthermore, the ISIM holds long-term authentication credentials: a shared secret key and the associated authentication algorithm parameters. These credentials are used in the IMS Authentication and Key Agreement (IMS AKA) procedure.

When a user wishes to access IMS services, the mobile device's IMS client reads the necessary identities from the ISIM. During registration, the device and the network perform the IMS AKA protocol. The device uses the secret key from the ISIM to compute a response to a challenge from the network. This process authenticates the subscriber to the IMS network and establishes secure session keys for protecting SIP signaling. The ISIM thus acts as the root-of-trust for IMS access, analogous to how USIM authenticates the user to the packet core network.

The ISIM application interoperates with other applications on the same UICC. A device may use the USIM for accessing the LTE/5G network (for bearer connectivity) and the ISIM simultaneously for accessing IMS services over that bearer. This separation allows for independent management of credentials and services. The ISIM's role is foundational for IMS security and service portability, as the subscriber's IMS identity and credentials are physically stored on a portable, tamper-resistant card.

Purpose & Motivation

The ISIM was created to provide a secure, portable, and standardized identity module specifically for the IMS, which is a service architecture separate from the traditional cellular access networks. Before ISIM, early IMS implementations often used soft credentials (username/password stored in the device) or attempted to derive IMS identities from cellular identities (like IMSI). These approaches had security weaknesses (soft credentials are vulnerable) or limitations in flexibility (tight coupling to cellular subscription).

A dedicated module was necessary because IMS authentication (IMS AKA) is different from the cellular network authentication (used by SIM/USIM). IMS uses SIP-based protocols and requires identities formatted as URIs or NAIs, not MSISDN or IMSI. The ISIM provides a secure hardware container for these new identity formats and the associated cryptographic keys, ensuring a high level of security equivalent to that of cellular access. It also enables service portability; a user can move their UICC to a new device and immediately have their IMS identity and services available.

Its introduction in Release 5 coincided with the initial standardization of IMS. It solved the problem of how to securely and manageably provision IMS subscriptions to end-users. By leveraging the existing UICC platform, it allowed operators to offer IMS services using a familiar, secure distribution mechanism (the SIM card). The ISIM established a clear separation of credentials, allowing a user to have independent subscriptions for cellular access and IMS services, even if provided by the same operator.

What changed in its specifications

The latest release-to-release comparison of specifications that define ISIM. 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 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

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

  • ISIM used together with USIM
    “If an ISIM is present on the UICC it shall be used to access the IMS.” TS 22.101
  • ISIM builds on UICC
    “The present document defines the IM Services Identity Module (ISIM) application. This application resides on the UICC, an IC card specified in TS 31.101 [3].” TS 31.103

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 13 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.

Rel-5 introduced

TS 31.103 first defines the ISIM application on the UICC for access to IMS services, and TS 33.203 and TS 24.229 first specify its role in IMS authentication and identity storage.

  • “The present document defines the IM Services Identity Module (ISIM) application.” TS 31.103 v5.14.0
  • “The present document defines the ISIM application for access to IMS services.” TS 31.103 v5.14.0
  • “If there is an ISIM and a USIM application on a UICC, then the ISIM application shall always be used for IMS authentication” TS 24.229 v5.26.0
Rel-6 specification text

The ISIM application's specification gained GBA_U key storage and NAF derivation procedures, an ISIM service table, and IMS AKA authentication handling, while TS 24.229 now requires ISIM use for IMS authentication when present.

  • “The ISIM performs Ks_ext_NAF and Ks_int_NAF derivation as defined in TS 33.220 [25] using the key material from the previous GBA_U bootstrapping procedure” TS 31.103 v6.14.0
  • “The ISIM application shall always be used for IMS authentication, if it is present, as described in 3GPP TS 33.203 [19].” TS 24.229 v6.30.0
  • “This EF indicates which optional services are available. If a service is not indicated as available in the ISIM, the ME shall not select this service.” TS 31.103 v6.14.0
Rel-7 specification text

TS 31.103 added ISIM support for local key establishment (Ks_local derivation, storage, availability check, status words) and corrected the ISIM file structure; TS 24.229 added ISIM refresh handling.

  • “the ISIM stores Ks_local and associated parameters Terminal_ID, Terminal_appli_ID, UICC_appli_ID, RANDx and the Ks_local Counter Limit.” TS 31.103 v7.7.0
  • “The ISIM uses the NAF_ID to identify the Ks_int_NAF associated to the NAF Key Centre.” TS 31.103 v7.7.0
  • “The first public user identity in the list stored in the ISIM is used in emergency registration requests.” TS 24.229 v7.34.0
Rel-8 specification text

ISIM requirements changed: TS 31.103 gained corrected SMS storage procedures for the ISIM, and TS 33.203 added the ISIM/ISIM application distinction and revised rules for ISIM use in IMS authentication.

  • “Correction of SMS storage procedures for ISIM” TS 31.103 v8.6.0
  • “If there is an ISIM application and a USIM application on a UICC, then the ISIM application shall always be used for IMS authentication.” TS 33.203 v8.8.0
  • “In this case the ME shall store in the ISIM the TS‑Service‑Centre‑Address and the TPDU in bytes 2 to 176 without modification” TS 31.103 v8.6.0
Rel-9 1 CR

TS 24.229 reworks how the UE uses ISIM versus USIM/IMC for IMS authentication and identity provisioning, and TS 31.124 adds ISIM-related conformance tests.

Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.

  • “The ISIM shall always be used for authentication to the IM CN subsystem, if it is present, as described in 3GPP TS 33.203 [19].” TS 24.229 v9.31.0
  • “In case the UE contains neither an ISIM nor a USIM, but IMC is present the UE shall use preconfigured parameters in the IMC” TS 24.229 v9.31.0
  • Introduction ISIM related SMS-PP Data Download tests TS 31.124CR0243
Rel-10 1 CR

ISIM gained Communication Control for IMS by ISIM and an IARI list (EFUICCIARI), and the UE registration procedure now uses the IARI list from the ISIM.

  • “The procedures and commands for Communication Control for IMS by ISIM are the same as Communication Control for IMS by USIM” TS 31.103 v10.3.0
  • Introduction of the IARI list in the ISIM TS 31.103CR2
  • “the EFUICCIARI changes in either the USIM or the ISIM, the UE shall perform the user-initiated reregistration procedure” TS 24.229 v10.29.0
Rel-12 1 CR

ISIM handling was extended: 33.203 added a note distinguishing ISIM from the ISIM application, and a WebRTC option for a dedicated ISIM application; 31.103 corrected ISIM SMS storage procedures.

  • “It is optional to have in the UICC an ISIM application that would be dedicated to WebRTC usage” TS 33.203 v12.9.0
  • Support for toolkit initiated GBA bootstrap using refresh on ISIM TS 31.111CR0427
Rel-13 2 CRs

Rel-13 extends ISIM with MCPTT procedures, URI support for the SMS indicator, and support for Enhanced IMS Call Control, plus a corrected ISIM service number for MCPTT.

  • “The MCPTT related procedures by ISIM are the same as MCPTT related procedures by USIM defined in 3GPP TS 31.102 [2].” TS 31.103 v13.2.0
  • Support of Enhanced IMS Call Control by ISIM TS 31.103CR2
  • URI support for SMS indicator in ISIM TS 31.103CR1
Rel-14 specification text

TS 31.103 gained new ISIM Service Table requirements for services 17, 18 and 19, and TS 24.229 added notes on precedence between USIM and ISIM files.

  • “Requirement: service n°17 is "available" in the ISIM Service Table.” TS 31.103 v14.6.0
  • “Requirement: service n°19 is "available" in the ISIM Service Table.” TS 31.103 v14.6.0
  • “NOTE: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B].” TS 24.229 v14.21.0
Rel-15 2 CRs

ISIM specification extended for Mission Critical Services: MCS-related procedures by ISIM are aligned with USIM, and a configuration data update to ISIM was added; default ISIM EF_AD values corrected.

  • “The MCS related procedures by ISIM are the same as MCS related procedures by USIM defined in 3GPP TS 31.102 [2].” TS 31.103 v15.6.0
  • Mission Critical Services configuration data update to ISIM TS 31.103CR2
  • Correction of EF_AD in the default ISIM values TS 31.124CR0528
Rel-16 1 CR

Default ISIM values for an NG-RAN ISIM-UICC were defined in the 31.124 test specification, adding ISIM-related test configuration.

  • “Definition of default ISIM values of NG-RAN ISIM-UICC” TS 31.124 v16.14.0
  • Definition of default ISIM values of NG-RAN ISIM-UICC TS 31.124CR0691
Rel-18 1 CR

The ISIM application gained new elementary files: an IMS Data Channel configuration EF (later updated) and an Access Control EF for GBA_U_APIs.

  • “Add EF of IMS Data Channel configuration to the ISIM” TS 31.103 v18.3.0
  • “Add EF of Access Control to GBA_U_APIs for the ISIM” TS 31.103 v18.3.0
  • Update EF of IMS Data Channel configuration on the ISIM TS 31.103CR2
Rel-19 specification text

TS 31.124 gained test specifications covering ISIM, including default ISIM values for E-UTRAN/EPC and NG-RAN ISIM-UICC and ISIM initialisation procedures.

  • “The E-UTRAN/EPC ISIM-UICC shall contain a USIM as defined in clause 27.22.2B.1 and an ISIM as defined in clause 27.22.2C.3.” TS 31.124 v19.0.0
  • “The NG-RAN ISIM-UICC shall contain an ISIM for IMS access. The values defined in 27.22.2C.3 shall be used.” TS 31.124 v19.0.0
  • “ME activates the required bearer, discoveres P-CSCF and registers with the values from the ISIM to IMS services” TS 31.124 v19.0.0

Defining Specifications

3GPP specifications that define or reference ISIM, 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
TR 22.944 vj00 UE Functionality Split Scenarios and Requirements Rel-19 read
TR 22.980 vj00 Network Composition Feasibility Study Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.167 vj10 3GPP IMS Management Object Rel-19 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 31.103 vj10 IM Services Identity Module Specification Rel-19 read
TS 31.829 vd00 ISIM-ME Interface Conformance Requirements Rel-13 read
TR 31.901 ve00 USIM/ISIM/USAT Feature Review Study Rel-14 read
TS 32.181 vj00 User Data Convergence Management Framework Rel-19 read
TS 32.182 vj00 UDC Common Baseline Information Model (CBIM) Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.141 vj00 Security for Presence Service (Ut reference point) Rel-19 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read
TS 33.812 v920 M2M Remote Subscription Management Security Rel-9 read
TS 33.978 v800 Early IMS Security Interim Solution Rel-8 read