How to Replace Permanent Roaming in Global IoT

Permanent roaming restrictions strand IoT devices. Here is how local IMSI, multi-IMSI and eUICC provisioning replace it, and how to move a live fleet.

Permanent roaming worked until regulators and host operators started pushing back. Here is what replaces it, and how to move a live fleet without a site visit.

Permanent roaming is when a device sits on a foreign network indefinitely and never returns to its home network. Several regulators restrict it, and the list shifts as national rules are revised. Let us look at what you should use instead is a local IMSI, a multi-IMSI SIM, or a remotely provisioned eUICC profile, so the device holds a local identity in the market where it operates rather than a foreign one.

 

 

Why permanent roaming became a problem

Roaming was designed for people. A phone crosses a border, registers on a visited network, and goes home a week later. Settlement between operators assumes that pattern. An IoT device breaks it. A meter installed in one country stays there for ten years. A tracker shipped abroad never comes back.

 

Regulators noticed. Permanent roaming moves traffic and revenue outside the country while putting devices on the national network with no local accountability. Lawful intercept, number portability, emergency service obligations and tax all assume a local subscriber. A permanently roaming SIM sits outside that.

 

Host operators noticed too. A visited network carrying thousands of foreign IoT SIMs earns wholesale roaming rates and gains nothing else. Some throttle. Some deregister. Some set a hard time limit measured in days.

 

 

What breaks, and when

Deregistration arrives without warning. A device that has run for eight months drops off and will not re-attach. Field teams find working hardware with no network. Diagnosis takes weeks, because the SIM looks healthy in every dashboard that reports from the home network outward.

 

Partial service is worse. Data sessions attach and then fail on throughput. SMS stops while data continues. The device reports itself as connected and delivers nothing.

 

Then there is the commercial version. A regulator opens an enquiry, your operator withdraws roaming in that market at 30 days notice, and your fleet is stranded while your replacement plan starts from zero.

 

 

The three alternatives, and where each fits

A local IMSI means your SIM carries a subscriber identity issued by an operator in the country of deployment. The device is a local subscriber, not a visitor, and the regulatory exposure goes away. The trade-off is commercial, because someone has to hold an agreement in every market you ship to.

 

Multi-IMSI puts several subscriber identities on one SIM and selects the right one for the market the device lands in. Switching happens over the air, with no hands on the device. This suits a fleet shipped to many countries from one part number.

 

eUICC remote provisioning replaces the profile itself, so a device shipped with a bootstrap profile receives a local operator profile after installation. GSMA SGP.32 defines this for IoT devices with no user interface and constrained connectivity.

 

Most fleets end up running more than one. Multi-IMSI handles the markets you already sell into. eUICC handles the markets you have not entered yet.

 

 

How to plan the replacement

Start with a country list, not a technology list. Write down every market where devices are installed today and every market in the next two years of your roadmap. For each one, record the current network, the current identity, and whether that identity is local or roaming.

 

Then check the hardware. eUICC needs an eUICC-capable SIM or an embedded MFF2 module. A device shipped with a plain 4FF SIM will not accept a remote profile. If the fleet is already installed and the SIM is not eUICC-capable, multi-IMSI on the existing form factor is the route that avoids a site visit.

 

Then check what you will see afterwards. Profile switching you are unable to observe is a new blind spot. You want to know which identity each device is using, when it last switched, and why.

 

 

Where IXT fits

IXT runs a dedicated mobile core built for IoT from the ground up, rather than a virtualised platform on shared infrastructure. That gives IXT direct control over routing, policy and identity. IXT supports local IMSI options in key markets to reduce permanent roaming risk, across 600+ mobile networks in 190+ countries.

 

The IXT CMP shows every SIM in real time: status, usage, location and session logs. Many platforms report on a 24 to 48 hour delay. When a profile switch fails in a market you entered last month, a two-day-old dashboard will not tell you.