The Impact of iSIM and Satellite Technology on IoT

We’re gonna be talking about ISIM and satellite technology. But before we get into the webinar, first, this is brought to you by Mouser Electronics, and some of the hardware we’re talking about will be available through Mouser. Thank you for joining us for the Let’s Talk IoT Devices series. This is the impact of ISIM and satellite technology on IoT, and we’re here with our partner, Murata. We’re gonna be talking about ISIM applications, an evaluation kit that gets you started. We’ll be talking about NTN satellite, what that means for IoT, building applications and some actual next steps, and the actual action items that you’ll wanna take followed by the q and a. I’m your host, Ryan Carlson, the technology evangelist for the Americas here at Soracom, and from Murata. Hi. My name is Shohei, Shohei Kawanaka. I’m a senior product manager. I’m based in Germany. Nice to meet you, everyone. And as an overview for Soracom, Soracom is a global cellular mobile virtual network operator that is solely focused on IoT. The company started in two thousand fifteen and now has customers with deployments that measure in the millions of devices all over the world. We’ve got over a hundred and eighty countries with over four hundred twenty of the major carriers, which puts multi carrier in all of the regions around the globe. The company exists to make it easier to put devices into the world, to deploy them into remote and urban locations, whether it’s using blended radio networks, cellular, Sigfox, LoRaWAN, Wi Fi, and now, NTN satellite, and all wrapping it up with secure networking requirements. The company has its own core cellular network, which allows it to have a lot of control, which we’ll get into some of those pieces and why r and d teams love using Soracom to build their IoT products and pushing the envelope on new technologies. And over to Murata. Let me quickly share the Murata overview. There are weird, electrical component manufacturer that we have a bunch of the product portfolio. That, mainly the passive component like a capacitor, the EMI filters. But we also have connectivity module. This is the, also the main point today. The, the, our company was established in nineteen forty four, in Japan. The, our net sales is, over twelve billion US dollars. We have a number of subsidiaries, in the worldwide. And, we have also the, more than seven thousand employees globally. I was gonna say one of the things that, we appreciate at Soracom is how Murata is focused on communication infrastructure, edge based computing, and mobility. And so you’re really pushing into territories of bringing technology into new new applications, new solutions. And so it’s very exciting to see how partnering with a company like Murata is allowing us to bring, technologies like NTN or ISIM into the world. Let me re-emphasize one point about Murata. We always bring the, smallest components to the market and especially the communication perspective. So that’s why we have, the very good collaborations with the Soracom, for a long time. So one of the things that we will be discussing is the ISIM EVK. It’s a Murata type one SC board, and that’s something that we also are having available at, Mouser. So let’s imagine that we could build very small tracking or asset tracking and monitoring devices that could go on, let’s say, a piece of equipment that is going into the mining fields. It starts in the garage, and it connects to a strong cellular signal back at home base. And as that device is traveling, it’s sending megabytes, maybe even gigabytes worth of video data, telemetry, machine performance, equipment safety, providing a whole series of different types of sensors and data. But then that device moves out of the cellular range and moves further into the mining fields, and it switches over to NTN satellite. And rather than sending all of the telemetry information, it’s still sending the information of where that device is in the world. It can send critical or emergency related notifications. So the any sort of, overrides or overheating or breakdowns will still be reported well before a human even has to pull out a sat phone or a radio and call back. And so these are things that can happen when you have this next generation of technology we’ll be talking about. It’s not just iSIM. ISIM has a lot of value, but now that we’re getting into this world of small, multi spectrum communications, let’s go ahead and explore what that looks like and why. But first, we’re gonna wanna talk about iSIM. So it is a subscriber identity module, the same thing that you’d be putting inside your cell phone, but much smaller. In fact, since about ninety six, the form factor has been shrinking all the way down to today, where you went from an eSIM, the embedded SIM, which comes on reels. Many products are now being built with these. iPhones have made them widely popular largely because this technology is pushing the ability for people to put different cellular profiles on these different types of devices on this equipment. But now we have the integrated SIM, which is going right onto a system on a chip. It’s also significantly reducing the amount of energy that is being consumed by having this smaller piece of equipment. We’ll get into some of those reasons. One of the things from add on to assumed is the idea that SIMs were those add on modules, came on USB. It came on as another board that you’d put on another board to moving on to where it’s been soldered onto the board. And now we just know that connectivity is what is gonna be required for most products being put out into the field. And so those are being integrated into the module itself. And so this impacts the engineering requirements by a number of different ways. The big one is reducing the footprint and lower power consumption. So with a smaller size, this means longer battery life. This means a higher durability as well due to vibration tolerance or wider temperature operating ranges. The other piece is the idea of security. These chips can’t even be removed and replaced. It is now built right into the module itself. This also means one less part, so reducing your bill of materials. And then there’s no SIMs to swap. There’s nothing that needs to be changed, and it’s one less thing to lose on that bill of materials or one less logistic for a distributor or a channel partner to to manage. So when we’re talking about size, we want to talk more about the idea of that impact it has on the layout of a board. So imagine for a moment the number of boards that will have a standard SIM card slot or even an eSIM, this does result in fewer components, fewer solder joints, one less SKU, and also just one less opportunity for an error to occur. The applications themselves, we looked at a wide spectrum of some of the most common IoT areas, and cost, runtime, and reliability are always going to be a factor. But in particular, we know that as you’re looking into mobile metering and wearables, can just reduce the layout constraints. The size is going to be important. This also does reduce cost, which because you’re going to have so many more, right? We’re we’re looking at far more asset trackers or smart meters or wearables than we would connected cars, for example. But when we look on the other end of the spectrum, when we’re not looking at battery operated devices, that an idea of environmental resilience, of putting devices into into more challenging situations with heat, cold, electronic interference by reducing those components just again one less opportunity to impact the connectivity profile of a particular piece of equipment. So when we’re looking at evaluating and implementing ISIMS, right out of the box, the Soracom EVK, it’s gonna have the ability for you to use a physical SIM card if you want to, if you’re trying to check a particular carrier profile. But it does come with ISIM built right into the Type one SC module. You’re going to also see that there is, subscription containers and an ability to handle some of the device credential management with a product like this. And so, for example, the EVK, it’ll have a fully integrated modem hardware, so you don’t need an SDK. You can choose your own development environment, and it’s gonna allow you to do everything you need with all of the common AT commands right through the command line interface. And all of that documentation will be available as far as how you can change it over to, only send a particular data over cellular and the rest might go over another connectivity profile like Wi Fi. It’s gonna give you a whole wide variety of different choices, especially when we’re talking about NTN and cellular connectivity profiles. The process is actually very simple to sign up. So you’re going to receive your package inside. It’s going to have all of the circuit boards. It’s going to have all of the connectors. It’s going to have, documentation inside. Registration is very simple with Soracom. You sign up your free operator ID. You put in your ICC ID that’s right on the packaging, and that’s it. It it will register everything, and you can go ahead and, you’ll start with the global plan is what it starts with. The reality is is that hardware engineers consistently tell us over and over again how much they love working with Soracom for their projects. They get to have one provider, and that same provider is gonna give them cellular and NTN. It’s gonna just be one single SIM that gets them any of the carriers in all of the regions in which they’re trying to deploy for testing, for pilots, or even full production. It’s one invoice that they get for the department, and it’s one development effort overall. Shohei, tell me a little bit more about your thoughts on this. Yes. Exactly. Murata also contributes the hardware engineer in terms of the development side. The Cellular and NTN connectivity enabled by Qualcomm and Murata together. Because Murata also provide, type one SC module, enabling the terrestrial network and non-terrestrial network together. Moreover, the iSIM is also integrated into Murata module. So combination between Soracom and, Murata, that’s gonna be kind of the total solution to, engineer. Absolutely. We look forward to seeing what people are able to create with the EVK and what we’ve, jointly put together out into the world. The thing that I’d like to point out is the subscription containers for profile switching will manage multiple subscriptions, which could be multiple plans with different region profiles, with even some of them being, specific local profiles. So if you’re looking to deploy to Brazil or you’re looking to deploy in particular parts of Europe or the United States, Canada, or, APAC, wherever it is that you’re looking to go, you have the ability to mix and match. And then the SIM OS itself will look at making the switching occur. So you don’t have to have a human in the loop telling your device to switch carriers. The logic is going to be automatic, which allows for an automatic failover. Your radio or your device can have the commands built right in to make switches when you have a signal drop. And this is how you have failover occur between cellular and something like NTN satellite. All of that logic gets to be built in onboard on the device, and so no human needs to send the command to tell it to switch. Because I’ll tell you right now, the one thing you don’t want is when a device loses connectivity, that’s when you wanna switch carriers. And so we’re allowing devices to be intelligent enough to switch carriers on their own without requiring an external force. So one of the common challenges that we have when you’re making IoT devices is it’s around certificate loading and device authentication. So, typically, if you’re a user, you’re going to register your device through a service. It’s going to go through, it’s going to give you credentials and your configuration profile, and then it copies those credentials down to the device itself, and then the device gets to handshake and authenticate and connect with the cloud service. That’s just one user. When you’re manufacturing multiple devices, the steps are lengthy and costly. First, you’re going to register your user and the devices, and you’re going to get a whole slew of these keys. So if you’re fabricating a hundred thousand devices, you’re going to get a hundred thousand keys. You’re gonna have to bring them to your contract manufacturer and securely copy them over in the manufacturing process using a an HSM, a hardware security module, which has its own costs and logistics and oversight, and then embedding them into each individual device during the manufacturing process. So just like serializing a device, you’re putting the unique keys for each one of your devices, which means they’re each maintaining their own version of their software. Then you get to authenticate and connect as they’re brought online. So this is a batch operation before the service that has to happen. There’s been instances in which there could be a credentials breach, and then it’s also just cost and lead time in the manufacturing process. Now there are a number of initiatives today through standards that are looking to change this, but Soracom now for several years has allowed for a process that eliminates the need altogether, having each individual device loaded with its own bootstrapped credentials. You can manufacture a hundred thousand of the exact same device, and they’ll handle the handshake on its own. So a device will initiate a connection in the field. You can grab one of a hundred thousand devices off the shelf, plug it in, turn it on, and it initiates the connection. Soracom will register the device with your own cloud service. The cloud service then issues the credentials, and then it passes those credentials down the device. Now it’s using the unique SIM. So that ISIM, ESIM, or regular SIM has its own, encryption module built right into the SIM itself. So we’re using that unique fingerprint to identify that device in the field and securely move those credentials and even storing them on the SIM itself or on another location within that device. And so this is something that will save a ton of time, and it eliminates a lot of headaches for contract manufacturing. Let’s talk about NTN satellite. This is a non terrestrial network. Couple of things. We’ve heard the names Iridium. We see it in the movies when they’re pulling out all of the sat phones. We’ve heard of Starlink and all of those constellation satellites that are ringing around the globe. So when you’re looking up into the stars and you see a whole ring of lights, it’s probably Starlink, zipping around. There’s also Skylo, which is a company that’s out there. They use geosynchronous Earth orbit satellites. What does this mean? Geosynchronous is gonna have three stationary satellites that are providing coverage to a vast majority of the surfaces of the Earth, and at any given point, they’re providing a fair amount of coverage. Whereas the low Earth orbit, like, the Starlink devices are gonna be moving fairly quickly around their coverage areas, and the difference is is that you need over two hundred satellites. In fact, it’s many, many, many hundreds of satellites to provide the targeted coverage. It does have a much lower latency, and the speeds are almost like a slow broadband. You can actually do some pretty impressive stuff with the low Earth orbit. But when you’re talking about IoT, you may not need that. This is gonna have blanket coverage. It is a higher latency, and the speeds are gonna be measured instead of in megabytes, it’s gonna be measured in kilobytes. We’ll get into what that means for devices momentarily. Let’s talk about the actual NTN technology and some of the scenarios that we’ve been building around. So the big one is gonna be NTN backhaul. This is where you’ve got devices that are into far off remote locations, like maritime is a big one, in which you’re getting all of your mission critical data, and you’re pulling it up through low Earth orbit. So this is where these star links come into, great effect for moving a fair amount of data. Cruise ships will be using something similar to this, and it’s gonna be going from the satellite to the terrestrial networks on land. Then you’ve got air to ground where you’re gonna have planes that are actually in communication with both both ground and air. And this is how you’re getting your inflight infotainment, is you’re gonna be getting any of these updates or how you’re gonna send text message to loved mon loved ones when you’re in the plane is by maintaining this duality between air to ground communications. And what we’re talking about today is the the non terrestrial network applications for IoT in remote locations, whether it’s tracking navigation, communications, emergency, or monitoring. These are the types of applications that are gonna need small bits of data, but it’s important that you’re actually getting it rather than not having it at all. This is something that was a great discussion when we were talking to Murata about NTN, was it’s not just about where you need data, but when you need your data. And so you’re gonna have primary connectivity where there’s no terrestrial coverage or when you’ve got gaps in terrestrial coverage. But then backup connectivity or that failover scenario is when there’s a loss of terrestrial coverage. So whether it’s wildfires, hurricanes, tsunamis, whatever it might be, there are times in which you need this. You’ll notice that some of the latest generation iPhones now give you the option of doing emergency calling over satellite. And that is because the same radio that facilitates cellular communication can now facilitate non terrestrial networks. So some of these use cases that we’re looking at as we get into the, the mix of satellite and cellular is you’re going to go from the logistics to recreation wearables all the way to remote control in some of these livestock and agriculture scenarios, where we can get into some other use cases. But, it seems that safety seems to be one of the big ones in which you’re looking at that failover scenario, or some sort of like workplace safety, site safety, or even things like public safety. Shohei, in your inquiries that you get from people that are looking to build applications, what types of trends are you seeing for people that are looking to explore this technology? Obviously, the emergency call is the one of the main application. Moreover, we we got so many inquiries from the device maker or the system integrator for sport. For example, like, the when the bicycle is going to the countryside, also the mountain, the hiking, etc. Coverage is not, enough, in the such, area. In this case, the NTN, can really help for the, such emergency call. I’d imagine four races you’d want to know at all times where your athletes are both for safety, but then also just to make sure they’re not taking a shortcut, right, for some of those extreme cross country sporting events. No. That’s great. I didn’t think about that. And then are these applications looking at a hundred percent NTN, or are they looking at using both? The the point is the both. The, the NTN could be really the secondary network as a backup. Even the automotive application, like, fleet management and the truck, application. They they continuously send the data via conventional cellular technology like a 4G, 5G. But, while the, the accident is happened, unfortunately, main battery might be broken, but a backup battery is, containing in the, system, and the dot can transmit the data via NTN. Interesting. This is responding to something in an emergency situation, which is less about cost, and it’s more about the need to get the information out. This still does come down to to cost given that up until release seventeen of 3GPP, we’ve been having to build in dual radios, dual antennas, all for a we might use it someday type situation. Yes. So the currently, the, NTN is, a very narrow band. But, I I expect the the in the future, the that’s gonna be the more extended, like the SMS communication, voice communication, data streaming, their satellite communication at the end. But right now, the emergency use case But let’s get into the the meat of building applications that leverage NTN. The reason why we’re even having this conversation is because of the 3GPP Release seventeen. It is the standards that all of the manufacturers and the providers around the world agree on, and this standards body is pushing the technology forward. And so we’re we’ve now got integrated non terrestrial networks, and this means the same antenna, the same module, the same radio will all allow for integrated support for cellular networks and non terrestrial. The Release seventeen is also looking at enhanced IoT support. This is all about trying to move packets quicker and faster with less latency. Then we’ve got additional technical changes that have made it so it eliminates some of the errors. We’ve got improved spectrum. We’ve got advanced mobility management for moving between both of them, and that’s the protocols that handles the handover between one network to another, similar to the air to ground scenario. We’ve got use cases for maritime and aviation that have been driving the release seventeen, and specifically because you’ve got the, like, ships going in and out of port. And so you need to have that hand off back and forth and using the most cost effective means of communicating. And the other is just some global coverage for five g devices, within release seventeen. So, this is all great news, but what does this mean for you and your next steps? This is permission to continue moving forward knowing that the standards are in place, and it’s only going to keep getting better as continuous releases are put out. With the iSIM EVK that we worked with on Murata is the satellite NB IoT enablement. And so it was in twenty twenty four, back in July, We announced our partnership with Skylo. And so that’s where Soracom and Skylo will be Skylo will be providing their services through Soracom, and you’re able to have a single plan, a single invoice, and a single rate card that is going to handle all of your processing. So, you’re not having to work through multiple vendors, and then Soracom will handle all of the data routing for your transactions. So, this is where you can use cloud services to optimize the data as well. And so, when you’re thinking about getting your product that’s gonna be out in the field and you’re trying to connect it to the cloud, you can then use your cellular and your satellite data. It’s gonna go to Soracom’s unified endpoint, and it would so you have the opportunity to then natively communicate with AWS, Azure, Google Cloud, or like a public endpoint or even a private endpoint of your own through a direct fiber channel. So this means you have the opportunity to communicate from a remote location without ever touching the public internet, which is great for utilities and other areas in which the data that you’re handling is sensitive. When you’re developing the products that you’re going to be leveraging satellite and cellular, Very important to look at the lightweight protocols that are available to you. The standard IoT device that we would deploy in our home typically is going to be using HTTPS, and it’s going to be using an encryption header called TLS. Now we’ve got HTTP, TCP, and even UDP. Now what you’re looking at on this chart this is from a blog post with a we’ve got the link below and that is all about how to reduce the overhead of the protocols you’re using. And this is important when we’re talking about being paying for not just megabytes, but now paying per kilobyte if your products are using satellite. So you can go from almost eleven thousand bytes down to fifteen hundred just by eliminating some of the encryption aspects of the packets and leveraging the encrypted nature of satellite and cellular networks that are natively encrypted. Now, this is using Soracom. We have a service that’s called Beam, and it allows for a protocol translation so the devices can use these low data optimized languages, and it will turn them into HTTPS, MQTTs, and allow you to communicate with the cloud platforms. The thing is you cannot send data to a cloud platform from an IoT device unless you’re using that TLS encrypted handshake. And so it’s the thing that allows us to verify you are the device who you say you are, and this is for security reasons. And so Soracom, by handling all of the data in the middle, allows us to leverage the code at the device level, and then turn it into human readable. Here’s an example to help bring this home. If you’re in a low data mode, you’ve got a device that is going to be crop health monitoring, forestry wildlife alerts, seismic event detection, or even bulk water levels for livestock out in the heart of Texas, where you’re thousands of miles from the closest cellular tower, you’re gonna look at what we’ve got here is that this is three different sensing points. And so we’ve got a device that communicates to the cellular network and then the cellular network to the cloud. This diagram is just showing how back and forth your device is going to have to communicate. It says hello, it gets a handshake back, it says here’s my credentials and my keys, and here’s the sensor data, and it moves back and forth until it’s acknowledged at the end. And what we’re looking at is, yeah, two thousand two hundred and forty four bytes over cellular. So if you wanted to go and have your device communicate over HTTP and then have a service like Beam turn it into that secure element, what we’ve done now is on the left hand side between IoT device and the cellular network, that’s what you pay for from a data perspective. Between the cellular network and Soracom and then Soracom Beam to the cloud, that’s all in the cloud. That’s all transactions that are occurring. So right here, you’ve had an eighty two percent reduction in the amount of data that you were having to pay for over cellular by offloading that encryption into the cloud. And so this push the it it pushes that back and forth transmission off the cellular network and lets the secure cloud service handle all of that back and forth and add the encryption that the cloud provider requires. Now we’re going to go one step further. You can go to UDP, which is a binary language that’s not human readable. And so what you do is you would offload that. And so in this particular case, we’re looking at satellite, where you’re being being charged per kilobyte, not per megabyte. And we’re looking at a ninety two percent reduction. So that single packet of binary data is sent to Soracom Beam. It’s translated then into JSON and HTTPS, which developers are probably going to want to see. Uses less battery, less processor, less data overhead. And if we were deploying a hundred devices into the field and just for easy math’s sake, we’re being charged ten cents per kilobyte, and those sensors were transmitting hourly, if it’s the difference per year of paying sixteen thousand seven hundred dollars versus one hundred and thirty dollars just for the data portion of that connectivity plan. So I’m I’m trying to, you know, trying to make this one a little bit more striking close to home and and put it down to dollars and cents. And so NTN is if it’s going to be a failover connection for your devices, you’re going to want to plan for low data modes. Just like our cell phones get ten percent and it says, do you want to save some battery power? In this particular case, a graceful failover to satellite data will require some thoughtful consideration. And this means, like that mining truck scenario, as soon as you leave cellular cellular range and move into satellite range for data, you stop sending all of the telemetry and the video, and it’s gonna store and forward until it gets back into another another connectivity zone. And then on satellite, it’s just gonna be mission critical updates, or might just might just be lat/long and a heartbeat. But that’s the thing you’re going to want to be thinking about when you’re developing these applications if it’s going to be taking advantage of both types of connectivity. One of the ways that prototypes can run amok is when you’re when you’re not planning for something like that, but you could be setting automated notifications that allow you to take action during testing to keep a device from using too much data. So, for example, in Soracom, we’ve got our our event handler. Our support team says it’s their number one most favorite tool because it allows people from day one to just set rules and notify them of when they’re reaching a certain data use threshold to keep their bill from running up thousands of dollars of just running junk data or, dare we say, testing NTN satellite where you’re going from being charged per megabyte to per kilobyte and saving someone’s job. Well, maybe that’s a little extreme, but who knows? You can you can set up the event handler to notify you, and even when you reach a certain threshold to just pause that device so it can’t use any more data. So I recommend when you if you’re gonna get one of the NTN, EVK modules, that you go ahead and when you register it, go to event handler, and go ahead and get that set up right away. And there’s some setup guides that can walk you through what that looks like. Very simple to do. Let’s talk about your next steps. When it comes to the ISIM EVK and the NTN satellite, you’re gonna one register your device, and you can buy them at Mouser. So, you can go to the link provided here. We’ll also be providing in the materials after the fact. Go to Mouser and type in Soracom ISIM and you’ll find our EVK. It’s got all the library of all of the documentation. It’s gonna have everything you need to buy it and purchase it. And then you can go to Murata, the my. Murata dot com, and you can go ahead and get your free account. And you’re gonna have access to a lot of additional evaluation guide documentation. So, Shohei, what are some of the things that people are gonna want to be prepared for when they are they’ve signed up for their account. Is there anything in particular that you recommend as part of this getting set up process for an evaluation? Yeah. Thank you for asking. The the initially, once the customer registered my Murata, then the, the agent downloads the EVK manual and startup, guide. That would be the, the, the first point the, the customer can look up. Then the, once the customer want to, evaluate the, especially the NTN, then the, we will provide the additional documentation a kind of manual. That documentation will be uploaded on the mymurata dot com, the signal writer. Still in a work in progress, but the we can take action accordingly. You’re saying if if some certain documentation isn’t isn’t ready for a hundred percent publishing, you may be able to arrange a early release copy? That’s right. Yeah. So you’ve got your documentation, all that information. There is something that you’d mentioned in one of our earlier meetings, and you said go outside. Give me a few more words about that. Yes. The this is a very important point. You know, the customer came registered mymurata dot com to get a bunch of documentation. But the most important things for the NTN testing, I strongly suggest go outside to see the open sky. The, the two for the NTN communication. The unfortunately, NTN, doesn’t work inside the laboratory, which, the all customers should go outside. At least the antenna should go outside to see the open sky. This is the most important to succeed with the NTN test. I think this is one of those cautionary tales, but there have been so many projects that I’ve even been involved in in which part of the testing process was to not fully go through all of the motions. Like, if this is a product for use in the wilderness, actually, not just go into the parking lot, but go into the wilderness and see how tree cover, how humidity or cloud cover or different types of environmental conditions might change the responsiveness, the latency, the power draw, whatever it might be. And so this is great. This is great, simple advice and a good reminder for everyone So go outside and use your product where your users would use this product to verify it’s meeting all of your specific needs. Awesome. If there’s additional information that you’re looking to learn or if you’d like to learn more about IoT devices technology that’s up and coming, go ahead and sign up for the webinar series, with Soracom. We won’t spam you. We’re not gonna assume that you’re a sales lead. We’re just gonna let you know when new education is offered, when there’s episodes of a particular podcast interview that you might be interested in, and we’d love the opportunity to connect. Now if you would like to actually speak with someone, go ahead to soracom dot I o forward slash contact, and we’d be happy to reach out to you and get the conversation going and see what we can do to help with your testing and evaluation. But not only that, but what your deployment might look like. So most of our customers all have their own custom pricing package put together all based off of what they’re anticipating for their deployment, what types of numbers they’re looking at. So if you’ve got any of that information, we can make sure that something lines up well with your business model. So thank you for attending today’s webinar, and we’re looking forward to addressing some of the questions that we’ve got in the chat. And so we’re gonna move on to q and a. There were some actually really great questions that we’ve got so far, and there’s two of them I wanted to to comment on. The first one is, out to Harold, about the, SGP thirty two. And one, we’re all eager for mass adoption of SGP thirty two for that IT standard for moving profiles around. Following it very closely, it is not yet, fully yeah. It’s not finalized. So it’s in preview. And as Shohei said or Shohei said, the end goal for, the ISIM is to support the latest IoT standard. We look to both eSIM and ISIM, those ones we have to put them in, they will be following that type of standard. So as far as the ability to, I can’t answer the question as far as from the, the process of if something were to update or change in SGP thirty two between now and whenever it’s fully adopted or mass adopted, I don’t know if that’s something that’s can be pushed down at that time. We’ve been doing testing at Soracom with those standards and, it’s really cool. So having built devices myself and had to move profiles around, it’s gonna be a game changer. And then just one other thing too, this goes out to Gabriel. I don’t disagree with you at all as far as having to trust Soracom’s Beam endpoint, if you’re sending data. So if you’re sending identifiable personal health information or any sort of secure or industry regulated data? Absolutely not. You’d wanna have to fully use an end to end encryption model. But if it’s soil moisture sensor or some sort of, like, an alert of some kind, it’s just all about what’s the risk tolerance for that type of data. But the the cellular network itself is encrypted. And then when we set up things like a virtual private gateway, which is actually your own instance, this is your traffic. It’s not something that Soracom can snoop. So it is, it’s like setting up your own virtual private cloud out, out on the web. There are ways of mitigating and addressing security needs, but you’re not wrong. The best way if you do protect the data is to have complete end to end encryption, but you won’t be able to do NTN satellite. NTN requires a UDP, if you’re looking at something like geosynchronous. So it’s the latency on that handshake back and forth is just too much to to work off of. See what other questions we can have. There is a question about the EVK, Murata EVK for the MDM testing. The I need to check actually, the we Murata need to check the the version of the EVK you have. The if it is NTN enabling version or not, but always a new EVK is recommended for the NTN test. As far as the maximum payload, I believe it’s two fifty bytes for the maximum payload over NTN. So we’re not pushing. Faster in the video. That’s for sure. Two fifty six. Yeah. Yeah. The it’s depends on the network connection network circumstance, but, around two fifty byte, including any I IP overhead or so closer to the two hundred thirty bytes or just the payload. So it’s really narrow band, but, yes, this is the fact. Around two hundred thirty to two hundred fifty byte. And this and there was a question around older Murata EVKs. Could you answer that one, Shohei? Yeah. Yeah. I think I I already answered that. All older version. Yeah. The new version is recommended. I mean It’s it it depends how old it is. So when you buy you bought the Murata EVK, it’s it really depends. So the new one is the for sure. Perfect. But, if you have a concern, please contact our sales or distributor contact. We got any other questions out there? Go ahead and throw them out on the chat. The direct port? Does it mean the port in the EVK? What is the direct port? Oh, so the every collection and also the, IP debugging, it can be done in your time for by using the direct. I think it it it it the right answer you expected? Okay. Cool. And it looks like we I I did learn something today. I don’t think Liz is on anymore, but, Iridium has sixty six satellites all cross linked. And so more efficient than the, the constellation, the Starlink ones. But either way, those are the low earth orbit. Those are get some pretty sweet feeds, but you pay for it. It’s not my soil moisture sensor doesn’t necessarily need to be, have the ability to do Xbox gaming or watch Netflix. The reason we assume they announced the release that the news that that they will also enter the NTN market. So now later, they are also a part of the cellular NTN. Any other questions? I’m curious. Did was there anything in particular that as you were watching, was there anything that surprised you or was there information that was I’m always curious to know what it is that people that are interested in this topic, where is it that they where are they surprised by things or new information that they come across? The okay. Maybe I will add some comment about SGP thirty two supports more. The type one SC, they support the today’s webinar’s main topic is a type one SC, which support both iSIM and NTN. Type one SC supports SGP thirty two with external eSIM perfectly. The the question is the iSIM plus NTN. The this gonna be support, with the new Murata module. It’s called the type two g d. It will be launched, this year, middle of this year. It supports ISIM plus SGP thirty two point. And that assumes that the three GPP standards are finalized by them? Yeah. Very recently. Yes. Yeah. Okay. Looks like there’s a question about Yeah. Any if there is update needed to fire on satellite. The the it’s very fundamentally the GNSS location is required for NTN because the, the device need to know the exact satellite location. So GNSS is a mandatory feature for the NTN communication. But the Murata type one c also has the GNSS feature as an option. You can utilize either the GNSS inside of type one c or you can put the external GNSS chip or GNSS module beside this module to get exact GNSS location. But you don’t need to get the satellite location, every time, at least to attach the network, at the beginning, to attach the network, you need the GNSS location. Thanks, Harold. Harold. Yeah. This is correct. The the type one is they also support, this o three bar. Two hundred fifty five, two hundred fifty six, and twenty three. Twenty three and, two hundred fifty five is, for mostly the North America. Correct. And the latest question is the latency things. The practically, the latency at the sub second, some seconds. The the some sometimes three seconds, sometimes ten seconds, roughly, because GEO is very far from Earth. Alright. If you’ve got any additional questions or if you’d like to learn more, we’d be happy to talk to you. Until then, thank you all for tuning in to the latest Let’s Talk IoT devices about ISIM and NTN. And if there’s additional details that you’d love to learn more about or if there’s content you think that we should be, like, talk IoT devices and we’re not covering them, let us know, and we’d love to dig in and see if there’s, more opportunities to share wealth of knowledge that we have at our disposal between our companies. So thank you so much, and until next time. Thank you.