12 October 2021
What does eSIM mean for the IoT industry?
IoT Leaders with Nick Earle, CEO of Eseye and Francis D’Souza, VP Strategy & Products – IoT at Thales
12 October 2021
IoT Leaders with Nick Earle, CEO of Eseye and Francis D’Souza, VP Strategy & Products – IoT at Thales
The era of eSIM technology is here.
eSIM provides resilient connectivity alongside resilient IoT device security — and it does it while keeping total costs low for device makers.
In this episode, Nick interviews Francis D’Souza, VP Strategy & Products – IoT at Thales, about the benefits and use cases of eSIM technology.
Join us as we discuss:
Join us on the IoT Leaders Podcast and share your stories about IoT, digital transformation and innovation with host, Nick Earle.Contact us
You’re listening to IoT Leaders, a podcast from Eseye that shares real IoT stories from the field about digital transformation swings and misses, lessons learned and innovation strategies that work. In each episode, you’ll hear our conversations with top digitization leaders on how IoT is changing the world for the better. Let IoT Leaders be your guide to IoT, digital transformation and innovation. Let’s get into the show.
Nick Earle (00:36):
Welcome to the IoT leader’s podcast with me, your host, Nick Earle, the CEO of IoT company Eseye. This is the podcast. As many of you will know, certainly if you’ve been listening, watching previous episodes where we attempt to demystify different aspects of IoT because we know it’s a very complicated world. And in this episode, I’m delighted to welcome our guest from Thales, which is Francis D’Souza. And Francis is the Head of Strategy for Thales Worldwide. Francis, welcome to the IoT Leaders podcast.
Francis D’Souza (01:09):
Thanks, Nick. Thanks for having me, glad to be here.
Nick Earle (01:12):
Francis, you’ve got a global remit and you’re based in Paris. Maybe just for any of our viewers and listeners who are not fully familiar with Thales and perhaps the tie-up with Gemalto. Maybe you could explain briefly, to begin with, Thales and then what your role entails before we get into the subject of this podcast, which is all going to be around what’s happening in eSIMs and how it works and how we believe it’s going to change the industry.
Francis D’Souza (01:40):
Absolutely, so Thales is a company that is present in different sectors, but all linked with the need to actually have to build, let’s say, resident systems. The sectors are aerospace, defense and digital security and cybersecurity. Within this, what Thales does is, establishes the world of trust. I’d like to focus on the digital and digital security and cybersecurity part of Thales because you’d required it with Gemalto. Gemalto was acquired by Thales, and Gemalto is really the pillar around which the digital and cybersecurity business is being built off. And it works in different sectors. There’s a whole building trust in cybersecurity for mobile operators, for banks and financial systems, for enterprises, for government and public sector and for IoT. And specifically within the IoT part I head up the strategy and products for the IoT unit, where what Thales does is brings first of all, the most resilient cellular connectivity solutions to connect IoT devices.
Francis D’Souza (02:45):
In addition to that, what Thales brings in addition to the cellular modules that are used to connect devices, the eSIMs and the really advanced technology around eSIM that make for extremely resilient connectivity services, as well as from a TCO perspective, helping keep total cost of ownership for IoT device makers, service providers under control, thanks to eSIM technology. All of this underlined with cybersecurity, because this is essential for all of our businesses today and particularly for IoT, where if you don’t have security by design right at the start on your IoT device or IoT system, you are potentially exposed to a lot of, lets bad actors in the chain. And Thales brings these cybersecurity solutions on top of the cellular module and connectivity and the eSIM services for the IoT.
Nick Earle (03:36):
Okay, great. Thank you for that. Now there was a lot in there, but there was one bit in the middle that was specifically going to double click on and you mentioned the world of eSIM.
Nick Earle (03:46):
So let me just sort of lay out the big picture, at least from my perspective as I see it. And then you can jump in as to what Thales are doing in this area. Broadly, for the last 20, 30 years, we’ve talked about it on previous podcasts, for the last 20, 30 years, arguably since cell phones first came out, there hasn’t been so much an eSIM. There has been a proprietary SIM. Over 800 mobile network operators in the world, they all have their own IMSI, international mobile subscriber identity. The way they go to market is their IMSI is loaded into their SIM.
Nick Earle (04:17):
When you contract, particularly from a cellular consumer voice perspective, which is where it was for the first 30 years; you contract with the mobile operator, you got their SIM. And then that SIM is always connected to the operator and then the operators are creating global reach with roaming. And so you have a lot of roaming agreements between operators and many to many type situation. And that really has been the case pretty much right from the beginning of cellular.
Nick Earle (04:41):
But that is now changing and the whole eSIM, which refers to not embedded as such, but the ability to actually have a operator agnostic SIM, where you can, and I use it analogy of sort of like the way the Kindle works or some of these ones where the device will pull down the right IMSI based on it’s requirements at that time, or an intermediate, like an MVNO will load IMSI based on the requirements at that time. In other words, it seems to me like it’s a pretty fundamental point in the maturity of the mobile network operator, where we’re going in from a world dominated by proprietary SIMs, to this emerging world with eSIMs, which is essentially a generic SIM that can be loaded with IMSIs over the air. Have I broadly laid the table right on the landscape?
Francis D’Souza (05:36):
You have. Though I must point out about the word proprietary, because a lot of the Telco industry would come back with a hammer on the word proprietary for the SIM itself, because the SIM itself is completely standardized.
Nick Earle (05:50):
SIM is standardized, yeah.
Francis D’Souza (05:50):
But what it builds on the stack. Yes. I mean, it’s kind of a SIM issued by an operator.
Nick Earle (05:57):
Francis D’Souza (05:58):
The eSIM like you currently pointed out, is the ability to have at any stage where the hardware is standardized, but the subscription of an operator could be changed during the life cycle. Now specifically point of view of an IoT device make of IoT service provider. Why is this capability useful? And probably even more than consumer devices. The first thing, as an IoT device maker, as an IoT service provider, you’re probably building devices to ship around the world. A smart meter manufacturer builds us a line of devices to go around the world. You might use different operators in different countries. You might not know about it until you’re shipping the device or at the point of installation. How do you manage that?
Francis D’Souza (06:40):
If you got to have a different SIM per operator per country, it explodes the number of SKUs and variants, stock keeping units, increases your cost of production. This is one point, how do you manage device variety when you’re shipping all across the world.
Francis D’Souza (06:54):
Second point, especially for devices that are using cellular networks, but tend to be fixed. Let’s say smart meters or alarm panels. They’re fixed locations in the home. In this case, literally the network has to come to the device. The device cannot go to the network, like in a car you don’t have network, you drive a few meters, you might actually get a network. In this case, the device is fixed. How do you actually … How does the technician acquire the right, the operator that’s present at that point in time that the meter’s installed.
Francis D’Souza (07:25):
If you’ve got eSIM capability, it’s literally like you catch out and you pull the network down into the meter. This is the second point; smart installation of the operator based on the conditions at the point of insulation.
Francis D’Souza (07:38):
The third point is fallback. During the life of any device network, conditions change. Say an operator’s base station goes down and suddenly a device is out of coverage. How do you manage situations like this? How do you have backup operators to be able to give you the resonance that you, as a service provider, are providing your customers? That’s the third one.
Francis D’Souza (07:59):
And the fourth one is in-life change. For example, you have contractual, and this is typical of IoT devices. They might tend to have a long lifetime, 10, 15 years. Smart meters are a very long time. But your telco contracts might be five, six years. And at the end of it, you might have another contract. Either, it’s because your original telco has done the sunset of the network or you wish to change, or the MNA and things like that, merchant acquisition between telcos.
Francis D’Souza (08:26):
How do you update the subscriptions on those devices at the end of the contractual period? And this capability of being able to remotely, digitally be able to change the operator on your device, really helps bring cost-saving and bring the capability at the time of variant and device management of variants, management of getting the right network at the point of installation of device, ability to have resilience and fall back in case of loss of primary connectivity, and ability to be able to contractually change operators over the year without sending someone without, doing a truck roll, should you wish to do it. And this is the eSIM capability that’s now on the market; that’s standardized, that’s rolled out, that’s implemented. That’s really starting to make a difference in IoT.
Nick Earle (09:16):
You’ve made as a company, made a pretty significant announcement in this field. And in fact, one of the first movers in that respect. Maybe you can just recap the announcement you’ve made as to how those benefits are clearly needed, especially with large multi-region or even global deployments, the fallback to the bootstraps that you’re referring to, the ability to switch. That is interesting that you said the ability to pull rather than push. All of these things are really important characteristics of the solution. Maybe, can you just recap the announcement you’ve made and sort of talk through it at a high level about how the new solution works?
Francis D’Souza (09:52):
Absolutely. And I think I’ll probably start off with the journey. I’m going to take you on a bit of imagination, mind space. Project yourself. So, literally you’ve got your IoT device. It’s got no subscription in it. It’s got a SIM hardware, let’s call it, but it’s literally an empty shell.
Nick Earle (10:11):
Francis D’Souza (10:12):
At the time of manufacturing the device, you don’t know where it’s going to go. You don’t know which network, where is that particular device going to go? You don’t know. All you have … But you do know that out of the, let’s say 100,000 devices, you’re going to ship, you’re probably going to have 40,000 land Australia; 30,000 land in Japan, 10,000 in the US, say for example.
Francis D’Souza (10:33):
You also have various telco contracts in different parts of the word. All you do is, even before you ship your devices, you go to a portal and you set your provisioning rules. It could be as simple as, if a device shows up in this country, use this telco. If a device, for example shows up in a country where I have two telco contracts, let’s say smart metering, typical, because you need two local contacts for the coverage. But in these conditions use telco A, in these conditions use telco B. And you just set up these provisioning groups.
Francis D’Souza (11:06):
You just set them up on a platform. And you ship your devices. When your devices power on the first time, using the bootstrap they actually hit your server. They say, “Where should I get my subscription from?” And the server redirects it to that operator based on the provisioning group, where the device presents an activation code; again part of the standards, and download the subscription. And all this process starting from an empty shell, you’ve done your provisioning rules, waking up, hitting the servers, saying where do I get my subscription from? And downloading it from the corresponding MNO. Happens in the time that’s way shorter than my explanation out there.
Francis D’Souza (11:49):
And this is something we’ve actually brought to the market. It relies on standardized infrastructure that telcos around the world have put in place to deal with consumer devices like the iPhone, and some of the other eSIM based devices. And we’ve literally made the cellular module and the eSIM act like these devices. Using existing infrastructure in place around the world to be able to implement this capability for IoT. And that’s quite a breakthrough because it addresses most of the pinpoints that IoT device makers and IoT service providers have when rolling out and making their projects a success.
Nick Earle (12:31):
And just to go a little bit deeper. I mentioned the Kindle, as an example of that existing technology, but I think I’m right in saying is what’s called the SM-DP+ technology.
Francis D’Souza (12:42):
Nick Earle (12:42):
And that’s where it is a pull rather than a push.
Francis D’Souza (12:46):
Nick Earle (12:47):
The differences today in IoT, a lot of the technology involves in, you sense of condition and you push an IMSI OTA. But this would be a pull so the device says, I now need, based on the rules I need…
Francis D’Souza (12:59):
Nick Earle (13:01):
And it goes, and it pulls from the ISMI.
Francis D’Souza (13:06):
Yeah, that’s a fundamental difference. And the ability of doing it as a pull rather than the push, is that you do things based on real actual network conditions, real life conditions. It’s not based on theoretical stuff where a server is pushing based on assumptions. It’s actual real time conditions where the device sends it back to the server and says “tell me, where should I get my subscription from?”
Nick Earle (13:32):
And I think that one of the things that you will provide, and we’ll get into who this is for in a minute, but let’s say for an MVNO or someone who is using this to offer a global capability, you’ll provide them with network information, which could be, as you said, for fixed devices; which networks are available in that exact location, perhaps latency or whatever. You’ll provide network mobile…
Francis D’Souza (13:59):
Nick Earle (14:00):
…information, which they will then write their rules around, which will determine when the pull happens of the IMSI.
Francis D’Souza (14:10):
Absolutely. All of these, let’s say parameters, would be passed on either automated or via APIs. And then they could be using by a different provisioning rule engine to decide about making the subscription download.
Nick Earle (14:26):
What about the pricing? What about data pricing? I understand how the technology will work.
Francis D’Souza (14:31):
Nick Earle (14:33):
And the MNOs. I mean, you have tremendous reach into the world’s MNOs. Many of them are customers of yours, especially through the Gemalto side of this. I guess it uses the Gemalto SM-SR technology.
Francis D’Souza (14:46):
Nick Earle (14:47):
Yeah, SM-DP+, excuse me, technology. But what about the billing and the data pricing? Who determines the pricing for the data? Is that based on a contract between the CSP or MVNO?
Francis D’Souza (15:00):
Sure. Absolutely. Where Thales comes in is Thales is literally providing the plumbing between the different parts of the ecosystem.
Nick Earle (15:11):
Francis D’Souza (15:11):
Thales doesn’t get into the contractual relationships between the OEMs and the MNOs or the MVNOs, or between the IoT service provider. Let’s say the one that’s buying the devices, and the MNOs and MVNOs.
Francis D’Souza (15:23):
Thales is the enabler. And the IoT device maker, or the IoT service provider has commercial relationships and agreements with people like yourselves, like Eseye with the other telcos. And uses those commercial relationships to set up the provision groups.
Francis D’Souza (15:41):
Thales doesn’t get into that part. Where Thales does is providing the infrastructure to the MNOs and the MVNOs, the SM-DP+ to be able to bring this capability. And most of the MNOs and MNVOs around the world are equipped with the capability. And Thales provides the cellular module with the eSIMs that go into the IoT devices, as well as the backend platform that does the plumbing between the device, between the SM-DP+ has all the subscriptions downloading into devices. And makes it available, Thales makes it available as a very simple commercial model. You have the hardware on the device, an eSIM, that goes along with the cellular module. You have one price there. And then you have a transaction fee for every subscription that you download into the device.
Nick Earle (16:29):
Okay. And who’s the primary customer? It seems like there could be multiple different types of customers for these…
Francis D’Souza (16:35):
Nick Earle (16:36):
…solutions. Sort of by category can you…
Francis D’Souza (16:39):
Absolutely. The customer for which this is, let’s say the easiest utility from an implementation point of view, it’s easiest is an IoT device makeup also bringing its own connectivity.
Nick Earle (16:53):
Francis D’Souza (16:53):
Because you have IoT devices makers, just make the hardware and then sell it on to someone else who puts together the solution. Now IoT device maker, that’s also bringing in the connectivity.
Nick Earle (17:02):
Francis D’Souza (17:03):
The package is the device plus the connectivity, is ideal for this. And it could actually even be, you have many customers. For example, e-bike manufacturers. When e-bike manufacturers, they build a device, they also provide the connectivity because that’s part of the service. That’s the sweet spot for this. You might even have, and you might be surprised to know, in some of, for example, in the smart metering world, the commercial contracts are changing.
Francis D’Souza (17:31):
They move from a hardware model to sell smart meter to the utility. And then the utility buys a connectivity, to a model where the smart meter manufacturer sells metering as a service. In which case a smart manufacturer sells an SLA, and then does all the negotiations and chooses the best connectivity.
Nick Earle (17:53):
Francis D’Souza (17:53):
That’s another typical one. Then there’s a model that’s a bit hybrid. And let’s take the smart metering example, where the smart meter manufacturer will ship the smart meters, but the utility would buy the connectivity.
Nick Earle (18:07):
Francis D’Souza (18:07):
The problem is not going away if it’s utility buying the connectivity of the smart meter manufacturer, buying the connectivity. You still have the same problems that the smart meter needs to get the best network, et cetera. In which case the hardware so to speak, is bought by the smart meter manufacturer. And the service to download the subscription is bought by the utility.
Francis D’Souza (18:26):
Those are typically the two kinds of models that exist. And of course, for the infrastructure itself, the SM-DP+ that’s on the telco side, that’s something that Thales sells to the MNOs or the MVNOs directly.
Nick Earle (18:39):
Yeah. Okay. I got it. I think one of the other areas you touched on in your initial overview was security. Would you say that, we all know how big a concern security is and in fact continues to be, and is actually getting more and more important because of the threat, the expanding edge we talked about on previous podcasts here but does this solution make things easier to implement a security policy, for any of the customers that you’ve been referring to?
Francis D’Souza (19:08):
Absolutely. I’ll come back to that in a second, because one of the things about security is there needs to be a concept of security by design. If you don’t build in security from the start, you can’t retrofit. And this is easier said than done, because every device is unique, every environment is unique. The principles of security are quite simple. Putting that into practice is harder.
Francis D’Souza (19:31):
Within the GSMA, there’s a new initiative that’s launched called IoT SAFE, where is SIM is used as kind of a root of trust, and as a base to start to secure the device.
Nick Earle (19:45):
Francis D’Souza (19:46):
And that SIM could actually be the same eSIM that we’ve just spoken about earlier, to download the subscription of the MNO, the telco that you selected. That SIM could also be used as a root of trust, and as the trust anchor in the device for the security of the device itself.
Francis D’Souza (20:04):
Moving forward, what’s going to happen is there’s going to be massive deployment of eSIMs and eSIM technology. In parallel, there’s a parallel track within the GSMA to standardize security via this IoT SAFE initiative. And that capability could reside within the same eSIM we spoke about. Your SIM now becomes your way of acquiring and managing extremely resilient connectivity, and your way of acquiring and managing extremely resilient IoT device security.
Nick Earle (20:34):
And one of the reasons that I asked you that is just to actually touch on something that we as Eseye offer, because I think security is, as we both know, a large complex area. And there are many components. And one of them is the issue of policy, anomaly detection, behavior, and deployment of policy to the agent. In other words, when do you, how do you spot infringement? When do you change the security certificates inside the SIM? One of the things that we have done is a relationship with the agentless security company called Armis. That was a subject of a previous podcast. Now, I think this fits in with what you’ve just said, because my own view of, as per my opening comments, my own view of what’s going to happen as a result of this change of what I call the, I won’t use the P word that you told me not to use, but let’s say to a generic SIM, is that you’re going to see more adoption.
Nick Earle (21:25):
And clearly that’s one of the commercial reasons you’ve done it. It’s one of the reasons we’re in business. You see more adoption because as you rightly said at the beginning, people have held back, particularly, you know we mentioned the 50 billion things that are going to be connected by 2020, we got to 11 billion. It’s the classic pareto. It’s the 80% of things that are owned by 20% of the companies that didn’t really go to full deployment.
Nick Earle (21:47):
And they’re the big multi-region global deals because people want global, the big brands, they want global solutions. And if they were going to have to change the SIMs all the time and change the back ends and their APIs and the support infrastructures, it’s too complicated. The ROI wasn’t there. But the moment you introduce this they’ll say, “Oh, then I can have a global eSIM. And then, based on where the device lights up, I can actually have the pull technology to pull the right IMSI at times.”
Nick Earle (22:16):
You have to assume that one of the effects of this will be an increase in adoption. Now, looking at it from the completely, and that’s the glass half full perspective, looking at the glass half empty perspective, you say well then if IoT security cellular devices is a problem, then as the number of cellular devices increase, then the security threat perimeter, if you like increases.
Nick Earle (22:38):
Back to what we’ve done with Armis. Armis, in case people haven’t heard the Armis episode, but they do agentless security. They are a California based company leader and by far the best in the agentless security for IoT devices, what they say is that you can never keep pace with the bullets bouncing down the stairs. You can never actually put a security piece of an agent security like Symantec do on every device, because the number of devices is growing exponentially.
Nick Earle (23:03):
You have to almost like use radar; my words, not theirs; sense what’s out there. And then you have a CMDB configuration management database. Is it behaving properly? Oh, that one’s not behaving properly. Take a look at it. My policy is, if it’s not behaving properly, quarantine it, inspect. Find out what’s wrong. And then if need be change its security certificates. That would fit into the safe eSIM thing that you’re talking about.
Nick Earle (23:27):
The challenge for both of us is that the IoT devices that are behind MNO firewalls, aren’t visible to enterprises, because they’re one step removed. Because they’re behind the MNO. As your technology enables more MNOs to basically be switched in and out of devices, cause that’s essentially what it does, then those devices arguably become even more invisible. So, what we’ve done, I think is a very important piece of the jigsaw here,
Nick Earle (23:56):
Is here at Eseye, we run all of our platform, connectivity management platform, over a private network, things like our own MPLS network. By connecting our MPLS network to Armis’s cloud solution, which is connected to the enterprise’s MPLS network, essentially you have a single MPLS connectivity to every device, independent of which MNO it’s using at any one time. Suddenly you’ve solved a very important problem.
Nick Earle (24:26):
You’ve extended the perimeter of your enterprise. You’ve extended the perimeter of your enterprise network to IoT devices, that themselves can be on potentially hundreds of MNOs. At which point you can then set policy centrally and have it deployed to the true edge, which is the IoT edge.
Francis D’Souza (24:47):
Nick Earle (24:50):
I believe that that’s going to be really important as companies like your own enable much greater adoption across many more MNOs. That’s the glass half full. The glass half empty is people would say, “Oh, what’s that going to do with my security?” It’s going to make problems worse.
Nick Earle (25:07):
Therefore, you have to have governance, policy compliance, quality of service. It’s almost as Armis described it to me, or someone described it to me is, it’s almost like every IoT device is if it’s connected via an ethernet cable into a Cisco router. But the idea of extending visibility policy control to the edge of the network. And I think that’s going to be really important. Because you literally cannot put agent software on all these devices, because they’re all made by different manufacturers. A lot of them are sealed. They have pretty poor security.
Nick Earle (25:42):
And I think it probably also solves the concern for the device manufacturers, doesn’t it? Because they are also worried that any security problem often reflects on the device manufacturer.
Francis D’Souza (25:54):
Yeah, absolutely. In fact, what you described, the complementary efforts, because with things like IoT SAFE and trust anchor and security by design, it’s let’s say hygiene factor. It needs to be done. But security by design doesn’t mean fire and forget. Because security is always a moving target and hackers are always moving really fast.
Francis D’Souza (26:20):
And what you described of having the ability to constantly scan the behavior of devices and based on the analytics to be able to detect any device or devices that are behaving abnormally, flag it, set policies; is an essential component. Because again, remember these are long life devices. You might have the security by design and you will have your security policies that are set at the time the device is introduced into the market. Which may not be good enough, five, six years down the line. Which is where the ability, besides the good practice of having the ability to update and patch devices in a secure way, the ability to detect this behavior using something like the system you described from Armis, is essential.
Francis D’Souza (27:07):
Besides the fact that for many enterprises, if there has not been IoT devices that have been designed with security by design principles, you at least cover for that possibility by having such a kind of solution.
Francis D’Souza (27:19):
These solutions, during let’s say time of device design and implementation and the other one constantly during the life cycle of a device, are essential and complimentary to each other. I think that makes for a very good compliment.
Nick Earle (27:37):
Okay. I think I got a good understanding an overview of it. You’ve announced it recently. Where are you in terms of the project? Are you in the early adopters phase? I guess you’ve got the MNOs, as you pointed out, the mobile network operators already have most of them, I guess.
Francis D’Souza (27:53):
Nick Earle (27:54):
They have SM-DP+. It’s not like they have to, they already have it because of the consumer devices used to pull technology.
Francis D’Souza (28:01):
Nick Earle (28:02):
You’re in the process of just rolling out the program now, and signing of the program?
Francis D’Souza (28:06):
Absolutely. We’ve got our first devices shipping and we went through the classic, we tested the concept, minimum viable proposition and product ties, and rolling out in mass. Fact for some pretty big roll outs on, I can mention one example, because that’s public, besides there’s the lots of others, which are a bit under the hood right now. But there’s a very big smart metering rollout that’s happening using this technology up in Scandinavia.
Francis D’Souza (28:32):
And really segments like smart metering really need this technology as well. Because for example, in Scandinavia, you might not have the best coverage all over the country, like in every country. So you need to have this, whereas the smart meter’s fixed at the location, on the wall. The meter with the non-smart meter, at the location where the non-smart meter was fixed.
Francis D’Souza (28:53):
Rather than have technician go out, trying to figure out the best network, the antennas and everything, this intelligence is built in. And then the eSIM downloads the subscription that’s needed at that point of time.
Francis D’Souza (29:04):
This is commercialized, rolling out on Cat M networks, on LTE Cat 1 networks, on LTE Cat, NB IoT networks as well. It’s been tested, works brilliantly on Cat NB networks as well. This is very, very much production grid rolling out, in implementation, in deployments and on the testing beyond the ones that are in deployment, under the testing with a host of customers.
Francis D’Souza (29:32):
And at the same time, there are many MNOs and MVNOs also onboarding into the platform so that as they sign up contracts on their side with device makers, device makers could also use this capability.
Nick Earle (29:43):
Okay great. So, Francis, if any of our listeners are wanting to get in touch with you to find out more, how would they do that?
Francis D’Souza (29:51):
Well, you can use my Francis@Thalesgroup.com email ID. But besides that, at any point in time, you could just go to the Thales website, thalesgroup.com/IoT. Just fill up a form request and get in touch with us. Or, I mean, we’ve been doing, especially on this topic of what we call the IoT eSIM, you put in a search for IoT eSIM on LinkedIn. You’ll have plenty of stuff that pops up. You’ll have me in and lot of different videos. Connect with me on LinkedIn, and we can take it from there.
Nick Earle (30:21):
And I’ve been on there and I’ve seen there’s is quite a few explanation videos…
Francis D’Souza (30:25):
Nick Earle (30:25):
…and white paper and you can do your research.
Francis D’Souza (30:28):
Nick Earle (30:28):
Great. Well, I think that’s probably a good overview for people and hopefully people do visit the website and find out more. Why don’t we leave it there. Thank you very much for appearing on this episode of IoT Leaders podcast. This is exactly what we wanted to do when we designed this series, is really shine a light on how to navigate through a lot of the complexities of IoT. And certainly this area of being able to get large global deployments, to be able to simplify the deployment and to actually have a choice, agnostic choice across different operators is something that many of our previous speakers have spoken about. I’m sure it will be successful.
Nick Earle (31:07):
I’d like to finish by again thanking Francis D’Souza from Thales, and thank you for listening. We’ll be doing all our IoT Leaders podcasts. If you do need to get in touch with me, I’m Nick Earle, CEO of Eseye. You can find me on LinkedIn, but also that we have our email address as well, which is IoTleaders@eseye.com. Thanks for listening. And we look forward to talking to you all at the next episode. Thanks again for tuning in. Bye-bye.
Thanks for tuning in to IoT Leaders, a podcast brought to you by Eseye. Our team delivers innovative global IoT cellular connectivity solutions that just work, helping our customers deploy differentiated experiences and disrupt their markets. Learn more at eseye.com.
You’ve been listening to IoT Leaders featuring digitisation leadership on the front lines of IoT. Our vision for this podcast is to be your guide to IoT and digital disruption, helping you to plot the right route to success. We hope today’s lessons, stories, strategies, and insights have changed your vision of IoT. Let us know how we’re doing by subscribing, rating, reviewing and recommending us. Thanks for listening. Until next time.
Build the IoT estate that meets your needs now – and ten years from now. It’s why global leaders trust Eseye.