IoT Knowledge Base
Learn the key concepts you need to know. Without the technical jargon.
IoT Reports & Guides
In-depth research, white-papers and guides from Pelion.
Blog Articles & News
The latest insights on industry trends, best practices, and Pelion announcements.
Events & Webinars
Upcoming events, online sessions, and expert-led webinars
About Us
Our mission, values, team, and the solutions we offer in the IoT space.
The Team
Meet our team behind Pelion's effortless connectivity.
Careers
Job opportunities, company culture, and the benefits of joining our team.
Sustainability
Our commitment to environmentally responsible practices.
The hype around global eSIM solutions for IoT use cases continues to grow. And there are a number of solutions out there for you to choose from. However, it's not quite as simple as it sounds. Different providers will have very different methods for providing a global eSIM service.
A global eSIM solution should offer the ability to switch between multiple network operators without requiring a physical SIM swap allowing simple and scalable global deployments on a single SKU. Pelion's preferred method of achieving this is via GSMA's accredited remote SIM provisioning (RSP) process (you can read about the spec over on GSMA's website). However, there are other ways to achieve similar benefits which we will also cover in this blog.
The three primary methods for this kind of single SIM global connectivity solution are:
GSMA accredited eSIM allowing the remote provisioning of any operator profiles OTA to an eUICC SIM
Multi-IMSI which allows multiple identities to be stored on a single eUICC providing the ability to switch between a pre-allocated set of operator networks
An eUICC SIM with a roaming profile only (this isn’t really eSIM at all but sometimes gets confused)
In our opinion only number 1 represents a true eSIM service that provides a properly future-proof and simple solution for build once, deploy anywhere global connectivity. This blog explains why.
The combination of this bootstrap which is then used to provision a better profile from a more local operator is what global eSIM looks like today. Whilst this "better profile" might not be a truly country specific local profile it will still provide better options than a single profile roaming SIM. For example, you might be deploying in France but the profile you provision will be from an Irish operator with great roaming coverage in France. It's still a good solution, just not perfect.
A common question that we get asked when discussing eSIM solutions with our customers is "can I have local eSIM profiles in every country?"
The short answer is no (not yet). But you can get quite close to it.
With the GSMA eSIM standard it is technically possible to provision a local operator profile to your SIM in any country in the world. However, practically speaking this is not what eSIM solutions look like today. You can still get global coverage on an eSIM, just how that is made possible can vary.
The primary reason you can't get local profiles in every country is that not all operators actually offer their profiles for use as part of an eSIM service with the ability to remotely provision them to any eUICC SIM. Even if they did, a provider of this kind of service would have to have dedicated agreements and technical integrations with each individual operator in every single country which is just not practical.
However, it is possible today to have multiple eSIM profiles across key regions internationally each with the ability to roam onto local networks, thereby offering something close to “local profiles in every country”.
For example, at Pelion we have multiple eSIM agreements with multiple operators across the world. All of these profiles have either roaming capabilities or broad international networks meaning that we can provide local network connectivity on a “semi-local” profile. This means if your deploying in, for example, North America and several countries in Europe, we can offer you a choice of North American operator profiles and a choice of European operator profiles. This gives you great coverage at a much better cost than a "global roaming" solution could.
The advantage of eSIM service based on GSMA’s standardised remote SIM provisioning (RSP) process is that we can remotely provision any eSIM profiles to any eUICC SIM at any time, and as we add new operator eSIM profiles to our catalogue (a process that is constantly happening) that new profile can then be made available to all our existing eSIM customers. The whole thing is standards based meaning greater interoperability, greater flexibility, and proper future-proofing of your deployments which the alternatives can't offer to the same degree.
It’s not standards-based, so different providers all have different ways of doing it which can create problems if you are working at a large scale across multiple providers. Not all multi-IMSI solutions have the ability to add/remove new connectivity offerings to that SIM over-the-air (OTA) and those that do can be much more complicated in practice than they may first appear. Whilst it can work, it’s certainly not as “elegant” as the GSMA-accredited methods. It is also likely to become less and less popular as the current GSMA RSP specs evolve to be even better suited to IoT use cases.
Overall, a multi-IMSI solution might end up just adding complexity to the process, requiring additional software on the device or SIM to manage the profile swaps, or being restricted to working with the 3-4 IMSIs already on the SIM.
The problem with a normal roaming SIM is that you are relying on the underlying operator maintaining their roaming agreements with all of their existing partners and you are also relying on the locations in which you need roaming coverage maintaining a roaming-friendly policy. This last point is definitely not guaranteed as evidenced by Turkey who recently ended all roaming access meaning any SIMs connecting to a local Turkish network but on a roaming SIM was permanently left without connectivity.
Roaming agreements also need to have IoT use cases pre-agreed between the various connectivity providers involved otherwise you can run into issues using roaming connectivity for a use case that doesn’t fall under the pre-agreed permissions. In this scenario, it’s entirely possible to end up in trouble.
If the SIM is an eUICC then technically it’s possible to provision a profile to it down the line even if it wasn’t deployed with all the infrastructure in place at the time but this is pretty impractical in reality. The whole point of eSIM is to add flexibility without adding too much complexity. Hence, it’s much better to just find a provider who already has all the supporting infrastructure in place and take advantage of their existing service.
Picking the right solution
The closing message would be that not all offerings branded as a "global IoT eSIM solutions" are the same and it is important to make sure you know what your priorities are before getting into an “eSIM” conversation. Think about things like device life span, likely deployment locations, device mobility, budgets etc. first. Once you are having conversations make sure you are absolutely clear what you are getting. You also need to be confident this solution is going to fit your requirements not just now, but over the lifespan of your device taking into account the possible risks presented by market dynamics changing.
Of course, it goes without saying if you want some advice about what solution we think best fits your application reach out to us or take a look at the various resources we have available here, on pelion.com
March 31, 2023 — 7 min read
The hype around global eSIM solutions for IoT use cases continues to grow. And there are a number of solutions out there for you to choose from. However, it's not quite as simple as it sounds. Different providers will have very different methods for providing a global eSIM service.
A global eSIM solution should offer the ability to switch between multiple network operators without requiring a physical SIM swap allowing simple and scalable global deployments on a single SKU. Pelion's preferred method of achieving this is via GSMA's accredited remote SIM provisioning (RSP) process (you can read about the spec over on GSMA's website). However, there are other ways to achieve similar benefits which we will also cover in this blog.
The three primary methods for this kind of single SIM global connectivity solution are:
GSMA accredited eSIM allowing the remote provisioning of any operator profiles OTA to an eUICC SIM
Multi-IMSI which allows multiple identities to be stored on a single eUICC providing the ability to switch between a pre-allocated set of operator networks
An eUICC SIM with a roaming profile only (this isn’t really eSIM at all but sometimes gets confused)
In our opinion only number 1 represents a true eSIM service that provides a properly future-proof and simple solution for build once, deploy anywhere global connectivity. This blog explains why.
The combination of this bootstrap which is then used to provision a better profile from a more local operator is what global eSIM looks like today. Whilst this "better profile" might not be a truly country specific local profile it will still provide better options than a single profile roaming SIM. For example, you might be deploying in France but the profile you provision will be from an Irish operator with great roaming coverage in France. It's still a good solution, just not perfect.
A common question that we get asked when discussing eSIM solutions with our customers is "can I have local eSIM profiles in every country?"
The short answer is no (not yet). But you can get quite close to it.
With the GSMA eSIM standard it is technically possible to provision a local operator profile to your SIM in any country in the world. However, practically speaking this is not what eSIM solutions look like today. You can still get global coverage on an eSIM, just how that is made possible can vary.
The primary reason you can't get local profiles in every country is that not all operators actually offer their profiles for use as part of an eSIM service with the ability to remotely provision them to any eUICC SIM. Even if they did, a provider of this kind of service would have to have dedicated agreements and technical integrations with each individual operator in every single country which is just not practical.
However, it is possible today to have multiple eSIM profiles across key regions internationally each with the ability to roam onto local networks, thereby offering something close to “local profiles in every country”.
For example, at Pelion we have multiple eSIM agreements with multiple operators across the world. All of these profiles have either roaming capabilities or broad international networks meaning that we can provide local network connectivity on a “semi-local” profile. This means if your deploying in, for example, North America and several countries in Europe, we can offer you a choice of North American operator profiles and a choice of European operator profiles. This gives you great coverage at a much better cost than a "global roaming" solution could.
The advantage of eSIM service based on GSMA’s standardised remote SIM provisioning (RSP) process is that we can remotely provision any eSIM profiles to any eUICC SIM at any time, and as we add new operator eSIM profiles to our catalogue (a process that is constantly happening) that new profile can then be made available to all our existing eSIM customers. The whole thing is standards based meaning greater interoperability, greater flexibility, and proper future-proofing of your deployments which the alternatives can't offer to the same degree.
It’s not standards-based, so different providers all have different ways of doing it which can create problems if you are working at a large scale across multiple providers. Not all multi-IMSI solutions have the ability to add/remove new connectivity offerings to that SIM over-the-air (OTA) and those that do can be much more complicated in practice than they may first appear. Whilst it can work, it’s certainly not as “elegant” as the GSMA-accredited methods. It is also likely to become less and less popular as the current GSMA RSP specs evolve to be even better suited to IoT use cases.
Overall, a multi-IMSI solution might end up just adding complexity to the process, requiring additional software on the device or SIM to manage the profile swaps, or being restricted to working with the 3-4 IMSIs already on the SIM.
The problem with a normal roaming SIM is that you are relying on the underlying operator maintaining their roaming agreements with all of their existing partners and you are also relying on the locations in which you need roaming coverage maintaining a roaming-friendly policy. This last point is definitely not guaranteed as evidenced by Turkey who recently ended all roaming access meaning any SIMs connecting to a local Turkish network but on a roaming SIM was permanently left without connectivity.
Roaming agreements also need to have IoT use cases pre-agreed between the various connectivity providers involved otherwise you can run into issues using roaming connectivity for a use case that doesn’t fall under the pre-agreed permissions. In this scenario, it’s entirely possible to end up in trouble.
If the SIM is an eUICC then technically it’s possible to provision a profile to it down the line even if it wasn’t deployed with all the infrastructure in place at the time but this is pretty impractical in reality. The whole point of eSIM is to add flexibility without adding too much complexity. Hence, it’s much better to just find a provider who already has all the supporting infrastructure in place and take advantage of their existing service.
Picking the right solution
The closing message would be that not all offerings branded as a "global IoT eSIM solutions" are the same and it is important to make sure you know what your priorities are before getting into an “eSIM” conversation. Think about things like device life span, likely deployment locations, device mobility, budgets etc. first. Once you are having conversations make sure you are absolutely clear what you are getting. You also need to be confident this solution is going to fit your requirements not just now, but over the lifespan of your device taking into account the possible risks presented by market dynamics changing.
Of course, it goes without saying if you want some advice about what solution we think best fits your application reach out to us or take a look at the various resources we have available here, on pelion.com