Description
MUSIM (Multi-Universal Subscriber Identity Module) is a 3GPP service feature that allows a single User Equipment (UE) to manage multiple active Universal Subscriber Identity Module (USIM) profiles concurrently. Architecturally, it involves enhancements across the UE, the Radio Access Network (RAN), and the Core Network (CN) to support the independent operation and resource management for each subscription. The UE must possess the hardware and software capability to host multiple USIM applications and maintain separate protocol stacks, including distinct Radio Resource Control (RRC) states and Non-Access Stratum (NAS) contexts, for each active profile. The network, including the gNB in 5G NR or eNB in LTE, must be aware of the MUSIM capability to efficiently schedule paging and manage UE activity states, as the device may be temporarily unreachable on one subscription while actively communicating on another.
From an operational perspective, MUSIM enables a UE to be simultaneously registered on one or more Public Land Mobile Networks (PLMNs) using different subscriber identities. Each USIM profile has its own International Mobile Subscriber Identity (IMSI), security credentials, and subscription parameters. The UE and network coordinate through specific RRC and NAS procedures to indicate MUSIM capability and negotiate parameters like paging cycles and discontinuous reception (DRX) configurations tailored for multi-SIM operation. This coordination is essential to prevent service disruption, as the UE's radio transceiver can typically only serve one subscription's active data session or call at a time, requiring time-sharing or suspension mechanisms.
The primary role of MUSIM in the network is to facilitate advanced user services without requiring multiple physical devices. It impacts mobility management, as location updates and tracking area management must be handled per subscription. It also influences connection management, with the UE potentially establishing and maintaining multiple Protocol Data Unit (PDU) Sessions or Packet Data Network (PDN) Connections across its profiles. For the core network, each subscription is treated as a separate user with its own authentication, session management, and policy control, even though they originate from the same physical device. This separation ensures billing, security, and service differentiation remain intact for each profile, making MUSIM a foundational enabler for converged personal and enterprise communication services.
Purpose & Motivation
MUSIM was created to address the growing user and market demand for a single mobile device to seamlessly support multiple active network subscriptions. Historically, dual-SIM devices often used a 'Dual-SIM Dual-Standby' (DSDS) approach, where only one SIM could be active in a call or data session at a time, with the other being unreachable. This limitation was problematic for users needing constant availability on both numbers, such as for separate personal and work lives. The evolution towards 'Dual-SIM Dual-Active' (DSDA) hardware posed new challenges for network efficiency and UE power consumption, necessitating standardized network support to manage the radio resource conflicts and signaling overhead intelligently.
The technical motivation for standardizing MUSIM in 3GPP Release 17 was to define a unified, network-aware framework that goes beyond proprietary handset implementations. Previous non-standardized implementations could lead to inefficient network behavior, such as excessive paging attempts when a UE is busy on another subscription, wasting radio resources and battery life. By introducing MUSIM, 3GPP enables the UE to explicitly inform the network of its multi-SIM capability and patterns, allowing the network to optimize paging strategies, mobility procedures, and connection release timers. This cooperation improves overall system capacity, reduces signaling congestion, and enhances the user experience by providing more reliable simultaneous service across subscriptions.
Furthermore, MUSIM supports emerging service paradigms like network slicing, where different subscriptions might be associated with different network slices (e.g., one for enhanced Mobile Broadband and another for a dedicated IoT service). It also caters to the subscription flexibility required for IoT devices that may need to switch between operator profiles for coverage or cost reasons. By standardizing MUSIM, 3GPP provides a future-proof foundation for devices that must juggle multiple identities, whether for consumer convenience, enterprise device management, or innovative IoT deployments, ensuring interoperability and efficient network operation across vendors and operators.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (117 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, 3GPP introduced foundational requirements and use cases for the MUSIM function, establishing support for User Equipment with multiple active USIMs registered simultaneously. The release defined key UE capabilities, such as single or dual Rx/Tx configurations, and specified that the MUSIM UE must allow user-configurable service prioritization between USIMs to manage paging and mobile-terminated services. It also mandated that one operator cannot restrict the use of another operator's USIM within the same device.
- Addition of an SPID value for vehicle UE subscriber TS 36.300CR1212
- RAN sharing with multiple Cell ID broadcast TS 36.300CR1239
- Corrections to multiple SPS configurations after sTTI and HRLLC merge TS 36.331CR3676
- Support of multiple UL SPS configurations and configuration of repetition TS 36.331CR3707
- RAN sharing with multiple Cell ID broadcast TS 37.340CR0140
- Corrections on Multi-Radio dual connectivity TS 38.300CR0137
+ 13 more changes
In Release 16, the MUSIM function introduced foundational service requirements to formally support UEs with multiple simultaneously registered USIMs from the same or different operators. It defined key UE capabilities, such as single or dual receive chains, which determine how the UE can monitor paging and handle mobile-terminated services for different USIMs. The release also specified that the system must allow user-configurable service prioritization between USIMs and prevent one operator from restricting the use of another operator's USIM.
- Signalling UE capability Identity TS 36.300CR1294
- NRIIOT Higher Layer Multi-Connectivity TS 38.300CR0253
- Correction to DL Multi-TB scheduling in NB-IoT TS 36.331CR4734
- Description of Multi-TRP operation TS 38.300CR0300
- Clarification on no support of CA, DC or multi-TRP with DAPS TS 38.300CR0307
- Updated description of multi-TRP TS 38.300CR0359
+ 9 more changes
In Release 17, 3GPP formally introduced the MUSIM function, defining requirements for a UE to support multiple USIMs registered simultaneously. This included specifying how a MUSIM UE, based on user-configured service priorities, decides whether to monitor paging from another registered USIM while actively engaged in a communication session. The release also added NR RRC support for MUSIM and provided corrections and clarifications, such as on paging reception and the 'Separate Devices' requirement, building upon initial LTE support.
- Running CR to 36300 for Multi-USIM devices support TS 36.300CR1355
- Introduction of MUSIM for LTE TS 36.331CR4769
- Introduction of further multi-RAT dual-connectivity enhancements TS 36.331CR4774
- Introduction of further multi-RAT dual-connectivity enhancements TS 37.340CR0309
- Running CR to 38300 for Multi-USIM devices support TS 38.300CR0422
- Introduction of NR RRC support for MUSIM TS 38.331CR2919
+ 20 more changes
In Release 18, the new MUSIM enhancements introduced the ability for a UE to express its preference for multi-receive (multi-Rx) operation to the network and defined mechanisms for paging cause forwarding to assist the UE in managing services between multiple active USIMs. These additions build upon the foundational use cases to provide more sophisticated support for user-configured service prioritization, particularly for mobile-terminated services. The specifications were also updated with corrections and clarifications for multi-carrier operation and UE capability restrictions related to these MUSIM functions.
- Introduction on UE preference for multi-Rx operation in UAI TS 38.300CR0731
- Introduction of NR MUSIM enhancements in TS 38.300 TS 38.300CR0741
- Introduction of Multi-carier enhancements TS 38.300CR0769
- Correction to 38.300 for multi-cell scheduling TS 38.300CR0832
- MUSIM paging cause forwarding [MUSIMpagingCause] TS 38.306CR0978
- Introduction of UE preference for multi-Rx operation in UAI TS 38.331CR4380
+ 38 more changes
In Release 19, the MUSIM function was refined with specific stage 2 corrections and clarifications. This included converting an editor's note into a formal note within the stage 2 description of MUSIM and making corrections related to SI reception by a remote UE for multi-path scenarios. These updates provided clearer technical specifications for handling multiple active USIMs.
- Introduction of Multi-path Relay Enhancement [N3C_M_Relay] TS 38.300CR0991
- Stage 2 CR for Rel-19 Multi-carrier enhancements TS 38.300CR1005
- Introduction of NR sidelink multi-hop U2N Relay TS 38.300CR1028
- Recovery of N3mb path failure for unicast transport of multicast session TS 38.300CR1032
- Introduction of Multi-path Relay Enhancement [N3C_M_Relay] TS 38.306CR1296
- Introduction of Multi-path Relay Enhancement [N3C_M_Relay] TS 38.331CR5373
+ 7 more changes
Explore further
Broader topics and technologies where MUSIM plays a role.
Defining Specifications
3GPP specifications that define or reference MUSIM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.834 vh20 | Study on Support for Multi-USIM Devices | Rel-17 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 37.340 vj00 | Multi-Connectivity Operation Overview | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |