What is multi-IMSI? Identities on one SIM

Several identities, one subscription at a time

A multi-IMSI SIM holds several IMSIs and an application that chooses which one to present. The device attaches to the network with one identity at a time. When the SIM switches, the network authenticates the new IMSI and the subscription behind it applies. That is the whole trick: the card does not move, but the identity the network sees does.

The commercial arrangement behind each IMSI is separate, and there are two common cases. A sponsor IMSI from another country reaches the local network as a roamer, under a roaming agreement the provider already holds. Or the provider holds a local range wholesale from an operator in the market; the network then sees a local subscriber. In that second case, the end customer's contract, the registration of the line and the permanent-roaming position are still separate questions. Neither case turns the card into a local subscription for the customer by itself. Registration, admission and roaming rules still apply to the device and to the traffic.

How selection works in public terms

The SIM application chooses the identity. The policy can follow the country, the visited network or a rule the provider loads onto the card. A switch can start when the device detects a new network, when a timer expires or when the platform sends a command. The device then detaches, re-registers with the new IMSI and rebuilds its data session.

The details differ by provider. The number of identities, the selection order, the time to switch, the fallback when no identity is valid and the way a switch is triggered are not standardized as one service. Multi-IMSI is a SIM application behavior, not a single 3GPP specification. Ask for the market list, the selection policy and the test evidence rather than assuming the label means a specific capability.

Local-looking is not the same as local

An IMSI whose country and network codes fit the market looks local to the network: it is a local subscriber, not a roamer. That still does not make it a local subscription for the end customer. The provider may hold the range wholesale from a local operator, and the customer's contract, the line registration and the permanent-roaming position remain separate questions. A sponsor IMSI from another country is the other common model: the network authenticates it as a roamer under a roaming agreement. The table below separates the local-range case from a local subscription.

What it does not solve

It does not remove registration, identity checks or admission rules. A local-looking IMSI does not exempt a device from line registration, and it does not make a foreign entity local. It does not create coverage: if the destination operator does not run the band or the network, the identity does not help. It does not create the roaming or wholesale agreement behind the identity, because that commercial relationship still has to exist. And it does not solve permanent roaming, because a subscription that stays in one country too long can attract scrutiny whatever identity it presents.

It also does not change the MSISDN by itself. The IMSI identifies the subscription and the MSISDN is the diallable number. A switch can come with a new number, an existing number or no number at all, depending on the arrangement. If the application depends on a stable number for replies, ask how the number is managed across switches.

How long a switch takes

A switch is a re-registration, not a settings change. The device detaches, the SIM presents the next identity, the network authenticates it and the data session is rebuilt. That can take seconds or longer, depending on the network and the device. A failed switch can leave the device without a usable identity until the next attempt or a fallback.

Design for the gap. If the application cannot tolerate a re-registration, buffer the data and retry when the session returns. Log the identity in use and the time of the switch, so a support ticket can tell which subscription was active. Test the switch on the real device and firmware, including a failed switch and a fallback.