 Hello everyone, I got an issue to unmute the mic. So thank you Steve, hi everyone. I'm pleased to be there with IOTrop today to give you a bit of a view of our STM32 wireless product and how we're working together with IOTrop myself and so also. So my name is Hakim Jafar. I'm the STM32 wireless MCU marketing director. So let me share my screen. Please let me know when the screen is correctly shared on the side. Yeah, you're up. Yeah. Let's go. So one word about the quick agenda that we'll see today. So one word, there will be one word about the partner program, one word about the global STM32 portfolio and then we go deeper into wireless product and then again deeper with the cellular solutions and the related ecosystem and then our partner IOTrop will take the lead for the second part of this webinar. About the partner program. So you have to know that STM32 and STM32 wireless product are teaming up with some partners in fact to offer you the best solution about software, hardware could be training as well. The way in fact, we are selecting our partner is very important. We select a partner because they offer reduced design cycle time solution, they enable a customer specific design or end to end solution and also because we wanna have a close collaboration in fact with our partners. And for instance, this is why we selected IOTrop for their solution, the quality, the obviousness of the solution. And of course with our partners, we are in fact sharing advanced technologies. This is just to give you another view about the IOTrop ST partner program. And now one word about the STM32. So it's a 30-bit MCU, you know that guys. What is important to keep in mind here is STM32 on top of being an MCU is going to add more wireless connectivity on the roadmap, more secure devices, you know, connected or not connected devices. Today's security is the key asset and we are also offering AI solutions. This is the global picture of our existing portfolio and it is split it over five sections of five series I would say, MP1, high performance MCU, mainstream MCU, ultra low power and the wireless one. And today the wireless MCUs are available in two flavor, STM32 WL and WB, all then being STM32 part of the entire ecosystem. Let's have a deeper look of what is an STM32 WB. It's just one slide to let you know this is a 2.4 Giga product. It supports the Bluetooth 5.2, ZB, which is now called CSA and CHIP, which is now called Matterer. So I'll give you the slide later on. You can click on all the links and you get much more detail on the product. For the WL, it's a long range product. L stands for long range. It's the world's first SOC supporting the Lora modulation but not only that supports as well as ZFox, wireless and views, MyOT and plenty of other. Here again, you'll get full links in fact to get a lot of information about those products. Now one word about the wireless roadmap. As we have seen today, we have 2.4 Giga, ZB. Our vision, our target is to go into cellular with STM32 W something, it's a bit of teasing and to go into ultra wide band with here again another series, how to do this? Today, okay, obviously we will focus on the cellular and how to extend quickly this roadmap and to execute. ST last summer has acquired a couple of companies for this. We have acquired Riot Micro, designing chips for LTM and NVIOT. We have acquired Somos Technology for Analog Frontend and PA. ST has acquired Biscount Company, working and developing ultra wide band solution and we have acquired Alquois Company developing BLE solution to reinforce and to increase our team in BLE. All those guys today are now part of ST. So ST has acquired the needed company and knowledge in fact to sustain our growth and our development about the existing solution because we worked with partners prior to go with acquisition. Here you can find a lot of STM32 solution existing out there bundled with Quectel Modem for instance. So you can see here you have an STM32L4 microcontroller board tied with Quectel Dotto board. You can get it in standalone. You have also a quick sequence, sorry, board. You have another board here named IoT node with plenty of technology here. And the latest one we launched is with our partner Murata. We launched a module, that tiny one here. This module contains the cellular in fact Modem which based on Altair 1250 and STM32L4 and an embedded scene from STM. So always included in this all-in-one module, right? I'll send you a slide you can go into detail. What you have to know is the board looks like this, right? It comes up with a multiple bounce antenna. There is a battery case underneath. There is a nodule jack to support voice over LT. It's super affordable. It's far below $100 and it's ready to use because when you open the box of this board you get 50 megabyte credit for free with our partner Truffaut. So for you guys, in order to make some trials and to test is the best out of the box experience. And then the board comes with a lot of features. So obviously the module, you have a micro-seam slot. If you want to go with a particular, in fact, MNO or on BNO, you have sensors, USB, user buttons. It's a real evaluation board to quickly helps you to develop and to play with this, right? Now to go deeper, we're now going to switch to the X-Cube sitting down our ecosystem. And now I give you the mic, SolarFo, your turn. If you want to take it to SolarFo, then yeah. Okay, thank you very much. I came for this introduction. Okay, so I will share my slide. Okay, so my name is SolarFo, I'm working for the microcontroller division in charge of the vertical application related to the integration of the cellular with the STM32. So for the today agenda, I'm going to talk about the STCeleral IT pillars, how we enable the cellular in the ST ecosystem. And I will talk about the product development process, how we make the cellular integration is very easy and to make a device with cellular. And I will talk about our core technology which is called the X-Cube cellular. And finally, I do kind of a short summary of our cellular IT solution and how it lets us help our end customer to make quickly a product, okay? So for the first, the STCeleral IT pillars. So basically, ST is providing the key components based on the STM32 to drive the cellular. So basically the idea was to develop a middleware which is called X-Cube cellular. It is part of the STM32-Cube expansion. So the goal of this middleware is to enable the cellular as simple as possible, meaning that we did provide internet connectivity without requiring the end customer or developer to even understand the cellular or to even understand the modem below. So basically it's provided only to provide internet connectivity for the cellular. So to make it running, we have developed the cellular key evaluation as presented by Hakim. So at the left, we have a bundle of discovery board with the STM32 and the modem module or you can buy the standalone module or you can use also the discovery board with the all-in-one module coming from Mirata. And then in the end to make the product that the customer can select easily, the solution based on the chipset component selecting the STM32, the modem and the SIM card or just to take the all-in-one module from Mirata as said by Hakim. So the second point is the second pillar is the global coverage. Why? Because I know for such IoT device let's say the customer can develop one in one time the product but it can be deployed worldwide. So the idea was that XCube cellular will support a different technology, KTM and BIUT, but also fall back to 2G. So then on top of this, we support also multiple vendors. So here we have the list, vector, sequence and Mirata using the modem from Sony. So it allows the customer let's say to evaluate quickly the solution with the selected modem but even later they can switch from one modem to another by keeping their own application and changed because the XCube cellular abstract that the modem actually. And then beyond the modem we, the kit we have a support a multi-SIM and the multi-INC and embedded SIM to provide a maximum flexibility for the connectivity. And to have out of the box connectivity we work with Trufen for let's say for their large coverage for the LTE low power cellular network. So now we have the internet connection. We have the components. So what is missing in the cloud? So basically we work with partner, especially with a company such as IoTrap. So for the lightweight machine to machine to provide the lightweight machine to machine client and the device because as you know, this technology is the most optimal for this kind of low power device. And then for sure we support as well the MQGT. So basically we support the Azure, AWS, Amazon free but we work as well with another live object such as a range live object. So basically we provide a complete solution with our partner. So now I'm going to talk about typical product development process. So basically what the end customer needs to do is to select the hardware development kit. So I give you here the example of the only one module with Murata. Then with this, the goal is to make a quick evaluation and to develop a prototype using the onboard peripherals. So for that, the customer just need to download the cube cellular middleware from the SC.com and they use the SM32 cube tools and the ecosystem to compile and to generate the binary and to program the image to the modem in an easy way. Then when everything is, let's say running properly, I mean the internet connection is working with the selected operator. So here with Trufun, when everything is working fine, then the customer just needs to integrate the cloud on top of the cube cellular. So the customer can use the SM32 cube expansion from partners and using additional software components as well. So basically the idea was that when it is fully operational, running with the cloud, with the sensors, then the customer can start to do it, building the actual hardware. So for that, okay, they have to select the component and for the device, but we provide also a bunch of documentation, schematic and the user manual to help the customer to design the final hardware. Okay, so now I'm going to talk about the core technology which is called X-Cube cellular. So basically each one in the microcontroller and it can be seen as a kind of abstraction layer of the modem. So as you can see here, we have the modem here. And as I said, we support a muti-seam. So we introduce a muti-placer here in order to enable different SIM interface here. So you can have the ST4 SIM embedded SIM, you can have the standard socket interface, but we can even support the SIM hosted by the SM32 if it is needed. So basically, natively, we support the muti-seam interface. So we have defined this estimate interface to abstract actually the hardware. And then X-Cube cellular when I manage the SMWORD signals to control the communication with the modem and to control the old GPIU. So the X-Cube cellular middleware, kind of a short presentation, provide the two simple APIs. One is for the control and the other one is for data. So for the control, we have a very simple functions to initialize, configure and to start a cellular service. And for the data plan, we provide a BSD socket, which is well known to create a socket connection to send an IP packet, TCP or UDP. So the X-Cube cellular will manage all ET command communication with the modem and they exchange the APGU messages with the ST4 SIM. Also, as I said, the X-Cube cellular is monitoring in all the SIM stages to support the remote SIM provisioning. On top of this, we provide additional library, which allows to leverage the embedded secure element in the ST4 SIM. So we support the PICA-CS11 library, which is a well-known library. When on interface, I would say, to enable the external secure element. So this library can be easily integrated in any, I know, cryptography library, or I can be TLS, SSL. So for that, then the next step, we just integrate the application on top of this. So it's to provide all library to make the internet connection supporting, let's say encrypted communication using this PICA-CS11 library. Okay. So just to summary, as you can see in this diagram, ST is providing the low level part here, the X-Cube cellular, with the needed component to make the connectivity and internet connection ready to use. So by this, the cellular really simplifies the cellular IT development. And then on top of this, as we provide a really well-known API to connect a cloud application, then it will be easy to integrate the cloud for any modem that has been chosen by the customer. So here, now we come up with our partner here, IOTrop team, to present their solution as a cloud client. Thanks a lot for listening. So I'll let you, Steven, hold them to the microphone. Okay. Yeah, and once again, thank you very much, both of you. I have with me here, Atomuzlati, CEO of IOTrop, and I'll let him begin by introducing the copy. Hello, everybody, I'm very happy to be here. So thank you, ST, for this great partnership. So we're going to go through what we have developed together, right, and combination of our ST micro or hardware and modem wireless capabilities, and including LiPo.com clients, so what we provide to this ecosystem for more efficiency in building efficient IoT applications. Let me introduce you with our company. Okay, so IOTrop is a company I created in 2016 from a former Intel executive. So we provide really this solution for massive IT deployments. That includes the security and device management of large fields of IT devices. Our vision is really to establish powerful tools in order to provide massive IT deployment to work toward customers. So we are strongly involved into our standardization bodies that includes OMA, but also Ipsil Alliance, IETF, and IOXT. But that's very important for us. So IOTrop vision is really centered on standards, right? So IOTrop is very involved into the IoT standardization bodies. We are a board member of the Open Mobile Alliance, so we gather all the big telcos that try to define the standard for security and device management on a worldwide perspective. So we have a strong influence there. We are literally driving those lightweight end-to-end specification on a worldwide perspective. And we contribute to a significant enhancement when it comes to reducing traffic, optimizing the footprint, and making sure we can make this lightweight end-to-end evolve towards embracing IoT challenges, especially for constrained devices. So as I mentioned, OVision is really centralized around three challenges that all face were industrial customers. So typically, security, inter-probability, device management, and those three things are intrinsically linked together because they are a critical consideration when envisioning massive IoT deployments. So let's take security, for example. That's almost the most important challenge to solve in IoT. Well, of course, the IoT use cases are often critical. Here, we talk about deploying meters that can manage your water, your electricity, your street lighting, so extremely critical use cases. And usually, the IoT devices is the most renewable point in the IoT value chain. So it's really critical to secure IoT devices end-to-end and be able to update the security, those parameters, throughout all the device lifecycle. And such practices are really now enforced by specific regulations. So we see regulation coming into Europe, but also in US that enforce to provide end-to-end security with siphoning with the management of the security from the lifetime of the devices. Also importantly is inter-probability, right? So it's really essential in the IoT from that time to device to the cloud, everything needs to be open, reusable. It's key to control your cost, right? You need to capitalize on open standard so that to make this inter-probability really happen. And that also prevents any vendor lock-in and make sure that providers can actually interact well together. And device management, that's the last challenge. It's really key. So typically, think about how you're going to onboard, configure your devices, change parameters, inject security keys, or even a virtual devices with new software without sending someone on the place, right? Because if you just send someone on the place just to change some parameters or the software, it means your ROI, your solution ROI may collapse. So it's very important to do those operation security but also remotely. Good. So this is Steven Lurio, I'm the marketing manager here at IOTrub. And it's a really interesting time to be in IoT. It's interesting to work with our customers. And there's kind of a growing awareness of how rapidly this market is evolving. And so some of the things that are happening is that its seller is maturing. So NBIOT is now becoming a viable option as well as LTAN. And so as people face this, they're looking for solutions. How can we build solutions for global markets that can use these new forms of connectivity and can get up to the cloud? And that's one of the reasons why Lightweight M2M is increasingly on people's radar and increasingly be considered strategic. And then once they look at that, then they start to take into these issues of time to market and qualitative issues and security and OPEX. And so today I was going to start by talking a little bit about some of how our customers are doing this in creating value. First thing I'd like to call out that most of our customers or many of our customers, I should say, use SD microelectronic solutions. So we're pretty familiar with the hardware. And basically what people are telling us in the market is they want more blocks, more standardized blocks so that they can focus more on the solution. And I call this Legos. But the language is very similar to what Salofa was talking about. These are modular pieces and they want, they're looking for abstraction. And then they can do this so that they can prototype very quickly. So let's look at the specific use cases here. So Alvaco is a customer of ours, they came to us and they're kind of very much a classic customer in the sense that they started by looking at proprietary approach to doing this. They figured out that Lightweight M2M made the most sense. And then from there, after using different implementations, realized that there was a qualitative aspect to the implementations. And so working with us, with the documentation, with the onboarding, literally they were able to cut down their time to getting something operational to a few hours, working with their code to a few hours, to prototyping in days to products in months. And that's really meaningful to them. And now they're at the point where they're coming out with more NBIOT products and they're actually having trouble keeping their current product in stock. So strategically Lightweight M2M make them to build a product and replicate, of course, their device portfolio and spread their product worldwide. It's very, very reasonable. Another customer we talk about is that we work with is EDMI. Of course they use ST microelectronics hardware as well. EDMI is really interesting. David Rowe heads up their efforts there and he is long in experience in smart water matering. And also he's used about every different LP1 connectivity out there, even having deployed some networks on his own. And he's very pro NBIOT for this market. It just makes a lot of sense. You don't have to operate this, you use whatever's there and it gives them access to global markets. It's also really interesting that very early on for the smart watering market in Australia, they settled on Lightweight M2M and then they did a very thorough market study. They followed up that market study. They identified us as a possible candidate after working with us. They just said, this is the way we wanna go. And because the infrastructure that we're using, they wanted to be confident that they were choosing the right strategy. And he has just flat-out said in a past webinar that it really just made the most sense to work with us. It's also interesting to look at this market in that it kind of gives insight to how Lightweight M2M and certain industries are developing and it's also happening regionally. And the next, I think it's by 2027, they're expecting 10 million smart water meters deployed in Australia and they have a real focus on OPEX and CAPEX and, you know, Australia is the driest continent slash country in the world with an inhabited country and COPDET. So water is very important to them. And then not only that, but the OPEX becomes critically important because they're looking at how can they use, these sensors and these, to collect and act upon data to improve their efficiency throughout their water network and beyond just billing and the initial things that they focused on early on. And then another thing we're kind of seeing in the marketplace as well is that security and firmware updates are a big driver. That's part of the issues with Australia and we're seeing that increasingly in the US as well as Europe and the UK where there's more and more regulation and more and more focus. And that's some issue with some other networks as well where you almost don't have the bandwidth really even to do a firmware update. So the key things driving here, the choices is performance. Can you imagine having a likelihood of implementation that can sustain being in place in a low power device for 15 years, right? So that Iowa can meet, right? So performance is very important because it is cost saving at the end. That's a good point. These smart water meters are battery operated and so optimization and using the very least amount of energy is just a critical importance. If you could add one year to your deployment lifespan that's almost like 10% or over 10% of your ROI. I'll let Atem talk about the next one. Yeah, so typically we are working with Traxins, the very innovative company in the logistic and transportation industry. So they have a solutions that attracts containers for freight trains and cargo. So you can know in real time what's the situation of your transported goods in terms of vibration shocks, temperature, humidity. You can even know whether someone has opened a container in an expected way. So this is the way those kind of industry are using open standards so that to replicate from the provider to another. You know, the big transporters here needs to comply, needs to be an inter-probable solutions on the market. So it's a very good example of how this industry leverages open standards so that to provide inter-probability within their subscribers, within their clients, but also making sure their providers can follow an open approach. So Traxins solution is pretty complex here. As you can see, they have multi-connectivity support. So they have the ability to transmit data on the hardware, on the cellular connection where, for example, the containers are offloading the data, but also when they are on board for several months within cargo. So here, they need to use the satellite connection with a lot of care because it's very costly effort. So only expected alerts need to be through and through the network. And in that case, LATWAT N2M provide them a dynamic way to manage those transmission policies. So it's very powerful for that. And you can change those policies over the year when the devices are on a cellular connectivity again. And just to add them's point, the logistics industry, there's an organization called the Digital Container Shipping Association which represents approximately 80% of the worldwide freight and container industry. And they're very quickly defining all the standards. And they see this as the key to unlocking efficiency and innovation in their marketplace. And so the market is really organizing around standards and even the data objects underneath. And so that aligns very well with something like LATWAT N2M. Right, another example we work with in the US, we work with ITRON on street lighting, but not only we work on the meter inside. So here, LATWAT N2M is a way also to enable an ecosystem, right? So ITRON has a lot of ambitions in the smart city. So they want to put in place an ecosystem of standardized infrastructure from device to clothes so that to onboard more device makers that will provide services at the end, right? So LATWAT N2M is very important for them. So historically, ITRON was building on preparatory technologies, right? So now they are part of the board of director of the UMA. So this is a strategic investment for them to capitalize on LATWAT N2M for their infrastructure and make sure they can control their OPEX, but also their construction of divided fabrics. So it's a very nice strategy to see how legacy very big players switch to open standards so that to open more opportunities. Just to touch on something that Atam said, when you look at something like street lighting, which is really a pillar of smart city, then what they want is they want to have a system in place for a smart city solution where they can manage all the different other objects, connected objects to do that and then share the data because of course the value is in there. And of course, they need to do that all securely. They need to be able to distribute keys. And also they need a mechanism for sharing the data securely, but also the way that respects people's privacy. So, and they want to enable their partners to innovate and come up with new devices and be able to support those devices very quickly. And so that's kind of the point about the ecosystem there. The last example we'll talk about, they're also using ST Microelectronics hardware is a partner of ours, Sentinel. And it's really interesting because this is kind of what's happening or the opportunity of this marketplace as we're seeing around NBIOT and lightweight end to end, which is these are just, there's a smaller organization and they were able to build this device really quickly. And so they looked at different approaches to doing this and then used Iowa and love the abstraction there and said it really simplified cellular development for them. So this is a small organization that's able to build a global solution. And so that's really important for them. And we think that's gonna bring an interesting dynamic to the market and unlock a lot of innovation, which will help adoption in the long run. So with that, we're gonna talk a little bit about why IOTRA. So, you know, a big part of what we do, you know, what we bring to the table, what we actually provide, it starts with our vision. And so I wanted to, you know, the things we've worked on since early on, our founders all worked with, early on with the Open Mobile Alliance on the DM. And so this was pre lightweight end to end. And this was really what unlocked the cell phone market and allowed this marketplace to boom. And this is a big part of what inspired our vision. Before that happened, the cell phone market was fragmented and it was harder to support this. And this all happened even pre lightweight M2M. And this work, working with them, defining the standards, having worked on different implementations of lightweight M2M and worked on our own, which we really defined for the marketplace. Now it's kind of brought us together to have a certain level of expertise and relevant, real IoT deployment experience. And of course, now we back that with some satisfied customers and the documentation. But if we were to provide kind of a graphic of what this vision looks like, this would be a visual representation of the vision. You know, our partner here today, SD Microelectronics, Salif was talking about modular and abstraction. And that's very much where we're working at getting to. So our vision for IoT is a little bit like plug and play IoT. We think people should be able to support any devices, different forms of connectivity very easily and then be able to tie into different security platforms or backends and support different clouds all very easily. And the whole point is easy, modular, reusable. And that's something, you know, what we're seeing also is people, they're like, oh, well, if I build with lightweight M2M on top of your thing, that's very strategic in the sense that I have some abstraction from my hyperscaler as well. And that's interesting to a certain extent. So this is kind of what we've been working on and now we're gonna dive in a little bit into depth of this. So a little bit, if we were to look at this at an architectural level, back to Salif's slide, we're sitting on the top here. And so what we provide is all the light blue here. And so these pieces are already built, they're standardized when we work with our customers, what we do is really increase their focus on the black part here. And what's interesting with lightweight M2M, lightweight M2M is not only do you have the services like, you know, firmware and security and managing connectivity with co-op, but you also have often the data models already defined both at a device management level but also an applicative at an applicative level. And that's a little bit different from a lot of device management approaches, which is that there's an application plane as well to help you manage that. But that's kind of the secret sauce which helps people focus on the application, focus on the solution and get these up and go in really quickly and have a good level of quality. So basically here we provide Iowa SDK for embedded devices. So we will go deeper into it to show you how it works. And we provide Alaska's device management platform that enables you to actually control all the operation you would expect for managing your device life cycle. Yeah, so, you know, again, just to compare this to how things were done, we're kind of transitioning in the market from M2M to real IoT. These devices are gonna be, you know, cloud connected devices and really focused on sharing data. And if we look back at the origins of our marketplace, it was really M2M and people were doing all this. If you talk with people like David Rowe or Eitron, they built everything that we see on the left and that's the hard part. So they had to build all these services each time and they really don't wanna do that. That doesn't really add any value there. And the other thing that what it does is it creates this ecosystem of siloed data, siloed solutions, everything siloed, siloed, siloed and it's really the opposite of where we need to get to to unlock adoption. And so that's what we're working on. And of course, now what we've done is we've built more pieces already pre-integrated into ST Microelectronics MCU32 line. So the idea is to get things going even faster than before, like I call these Legos. And, you know, and people are starting to figure this out. Gartner in 2020 said, you know, OEMs, if they're looking to do seller development, this is really something they should be considering. But so here, the key learning is, you know, concentrate on, you know, how is application, your devices, and then, you know, let us do the plumbing and leverage on expertise and library and performance so that, you know, to concentrate on what you need to do, right? Device management is a complex thing. Firmware is a complex thing. And all those things can be standardized and you can really fast on your time to market leveraging of the right implementation expertise. And it's kind of the same, it's the same thinking that would be behind, for example, choosing a cloud provider. No one builds their own cloud. The same thing with a web server. You download Apache and then you just build on top of Apache. So it's kind of the same logic. There's these building blocks and you just use the right building block. Let's go a little bit better and watch is Iowa, right? SDK. So Iowa is really the most complete and implementable implementation in the industry. It's extremely compact. It can run on any platform, even the lowest, the low power ones. So that's the reason why we choose ST Micro as a reference platform here internally because I mean, you can really use a low power and sustainable approach for customers leveraging on a very high quality hardware and tools. So it's very, very compact. As you can see, the footprint is the most competitive in the market. It has a very low RAM consumption and it can literally be fortunate in any hardware platform, either 30-bit, even 8-bit microcontrollers. It's portable on any operating system. So you can make it run on MbaOS or FreeRTOS or anything. So we have a lot of port available. It's very well documented, right? And its API is very easy to use. So you don't need to have any understanding of lightweight end-to-end or co-op standards or even know about detail and security to get started. The APIs are done in a way that in a couple of hours you have all your logic done and you can ship your product. So that's really very important to leverage on kind of software and expertise to go fast actually bidding your product. Yeah, and it's interesting. A lot of times when we work with people, they're looking at either other implementations or trying to do something on their own. And I think they really underestimate the complexity of what they're trying to do, building all this. We have a team of developers that have put in man years here. And so just talk about these different services and we're gonna dive in and show you some actual code examples here. From a connectivity standpoint, we've put lots of resources up on our website, but for something like NBIOT, co-op is the right approach. So from an energy standpoint, from an efficiency standpoint, from a scaling standpoint to the cloud, if you don't use the right connectivity approach, your solution is gonna be limited very quickly. And it's interesting because there's a lot of resources on the internet but people because it's a legacy approach still seem very focused on MQTT, but that's just not a viable approach here. The other thing is FOTA, of course there's regulatory and legislative issues here that FOTA is coming up on everyone's landscape and cellular is interesting in that it provides the bandwidth necessary to do that, which some of the other networks aren't able to do. And then the other thing that's interesting is how easy can you make it to do FOTA? And of course you also need to make your FOTA's mechanism secure. Many times these solutions are audited. And so when you work with us, you get a known security plane, the security risk plane of your FOTA is known out of the box, which is kind of nice. Speaking of security, lightweight MTM does some very interesting things. There's authentication, there's authorization, and then of course encryption of all your data. And we're kind of been working on the cutting edge of some of the security things. I don't know if you're familiar with it, but there's a thing called OSCAR, which is an encryption approach, encryption of standard that's very specific, a little bit like co-app for these LP1. And it does two things that's really interesting. It saves you energy, which can extend the lifespan of your devices, but it also actually improves the security as well. So it's very interesting. And then finally, this fourth pillar here, which is the data. So having these standardized data modules, for example, in an industry like water, you have 56 standard data modules, you just pull in your blocks, you've got your application, all your services are defined, all your data is defined. Next step. And so this literally just are all things that shorten the time to market. So here are some code examples, and I'll let Atom take it. Exactly. So IOR is already a full implementation that's coming along with all those features, like the template features, including like bootstrapping and data reporting, but also the folder and the security mechanisms, and all you need to actually manage your device life cycle easily, and compliant to the standard, of course. So here, as you can see, it's very easy to port IOR to any platform, any operating system. So you just have to rely on abstraction layers that here, for the case of STM32, are linked to the XCube cellular. So you have the abstraction on the modern side, so it can be very easy to actually bind those abstraction layers to an existing XCube cellular, but you can go otherwise, right? If you want, for example, to copure your exact modern implementation, in that case, you will implement the AT commands and the things that needs to be done, right? And the stack, I mean, will be operating seamlessly. So whatever your hardware platform is, the operating system here, so you just have a few implementation routines to overload. And the next thing, as you can see, it's also here, it's the way you set up your application logic when you call the stack. Actually, it's literally 10 lines of code to get started. You don't need to have any understanding of lightweight M2M. You just declare the data model you want to use, right? And typically you step into a stack and the stack shows to respond to any lightweight M2M server orders. So there are some callback mechanisms so that you can know whether a server triggers an operation. It's coming with a build system, so it's very integrable, very easy to use in your development environment. So it works out of the box without the knowledge of the specifications. And at least that's the same approach with firmware updates, very high level APIs. So as you can imagine, in lightweight M2M, there are two modes of pushing firmware updates, either pull or push, right? So we support both things. And typically here, this is very interesting API, very easy to use. So you have callbacks whenever software updates is triggered from the lightweight M2M server. And typically this is completely aligned with the specification of course, but also enforce the regulation that now are arising in UK, in the US and in Asia. So typically there is a question about that. So how we get started with this lightweight M2M Iowa assets, right? So we've pre-integrated Iowa with STM32, right? So how do you reuse that? So demos are already available for the cell one and cell two boards that Solo4 was talking about. So the one leveraging a QuakeTel model, but the new one leveraging now a Murata model. So the demo works seamlessly directly. Just go on our website, you have the link there, you click, you get the binaries, you get the instructions and typically you can get started. So you download the image into your STM32 board and you're ready to go. Then you go into our public lightweight M2M testing server, right? So that should check the operation of your board with reference lightweight M2M server. And you can do like manipulations, you know, trigger some resources. So everything will be seamlessly recognized and you can just be up and running. So of course, testing server is freely accessible publicly, but you can easily switch to Alaska production server in case you want to manage your fleets and get access to your data actually and do applications, web applications. So to summarize how to get started with our implementation. So either you get the full binaries, right? On the websites, right? So if it's not enough, you want to go a little bit beyond that and you want, for example, to implement your own application logic and want to go further for your device use case, well, you can get access to your Iowa evaluation source code that is accessible through GitHub. So Iowa eval SDK, it's an evaluation. It's not a fully disclosed, right? You have 1.0 capabilities, there are features that are disabled. So, but still it's good for you to compile, to see how it's going, build your application logic and get started. If it's not enough and you want to have the full featured Iowa SDK including the 1.1, the built-in of subjects and typically the firmware of the APIs. So please come back to us, to our sales to get a quotation for your use cases, right? So the way we sell the package here, we created special offer for STM32 ecosystem. So request your package, it's available until mid-July. So this package includes Iowa for STM32 and the bundles get you an access to full feature source code with the STM32 protein layers that includes the X-Cube cellular samples, examples and pre-porting layer we've done. You get 25 hours of integration guidance and support, right? So that your team can help you to actually work together on a device and a proof of concept. You have, of course, the API reference guide, sample codes, a full set of documentation that makes you start it very easily and develop your product easily and of course access to Lacto-Tentu and test server. And we also provide a bundle of production license for one of our produce queue. So there's a special offer, a 10% discount which we ordered by mid-July with this promo code. So to just take benefit of it, the promo is going to end mid-July once again. So I hope it was useful to you. Of course, if you wish to have Lacto-Tentu and supporting your product solutions, we're more than happy to talk to you and please get started. There is a bunch of free assets available for you and of course, if you want to go beyond, we're happy to provide you with more support. Good. Yeah, likewise, thank you very much. And with that, we're going to open it up, I guess, to the Q&A time. So if you have questions, please put them in the Q&A section. So the first question was, where can I download the binaries for evaluation? So I think we address that. The link will be in this. We'll send out an email to all the people who registered with the webinar and the link will be in the PDF. But it's also, I could maybe type it in there. Actually, it's already answered, sorry. So we can type it into the chat to everybody. The second question here, for very constrained sensor nodes, conserving battery power is very important. The sensor node is in sleep mode and only wakes up every, say, 15 minutes to send data. How does lightweight M2M support power save mode offered as part of NDAOT? The query for lightweight M2M server would need to be cued. Well, that's a very good question. Of course, I mean, when we work with EDMI and Traxense, of course, body power concerns are a strategic and critical for them. So there are many ways to solve that. You know, setting up accurately your device lifetime, so the lightweight M2M lifetime, making sure as well that your co-op implementation, I mean, cares about retransmission, acknowledgements. So there's a combination of several factors that makes you really save data traffic and the same way applies for the security, right? So typically, resuming a secure context can literally kill your device battery. So you need to have at least mechanisms like the connection ID that will, you know, especially optimize drastically the resuming of the secure context. So we have everything of this implemented in our iOS stack. And of course, we will be happy to, I mean, to work together in case you have more question about it. Yeah, and I think also that PSM also is on the network plane. PSM is on the network plane and lightweight M2M addresses these things on the applicative level. I think the thing is that when you're connecting up to your cloud servers, you wanna do that as efficiently as possible and make sure you're not reconnecting or losing anything in transmission. But yeah, I know these are important issues and kind of the part of the reason why we support our products because there's a lot of optimization that needs to be go into there to make sure it works as well. Sure, so there's not a single answer to the combination of factors that I would be happy to. Let's go. Yeah, exactly. Maybe I can add some comment as well on this one. Yes, please. Yeah, so regarding the PSM, for sure as you said, Steve, our XCube server is able to manage PSM of the modern meaning that when there is no communication over the cellular, then we are able to automatically configure the modem to push it to enter the PSM mode. So basically for sure it is fully supported. And from the network side, as you said, you know, the lightweight machine server because the modem is in the PSM mode, so it does not release any more any darling data from the cloud, right? So I assume that normally the lightweight machine to machine server should be able to queue all the requests from the external world, right? Yeah. Thank you. Yeah, so modem configuration can be triggered for lightweight M2M, you know, resource exposure, of course, but I mean, also they're in lightweight M2M 1.1, so 1.1 is very important because it has specific, you know, setting mechanisms to shorten, again, the traffic and the level of transmission. So typically here, for example, we have like data push at the initiative of the device rather than the way around. So typically here that those kind of mechanisms are expected by customers that especially want to control the way device will go to sleep and send data to the lightweight M2M servers. So there's a next question here. What levels of battery size and life can we expect from an application running on these platforms? So I know, depending on the market, so typical smart, I mean, typical battery-operated solutions are smart metering and they're looking for well over 10 years. And I think that's, if I understand correctly, that's on a couple of AA batteries or AA battery. Yeah, that's not an easy... But it's really gonna depend on the application, what you're doing, and then there's other factors like, you know, photo, how often do you send photo because photo is gonna use more energy. So there's a lot of moving factors there, but in general, people wanna push this to extreme and that's why they're looking at things like co-app and OSCORE and those are so critical, but also optimization. So you need to do security, but you need to make sure that the security is right size to the application. And this is where the quality of the lightweight M2M implementation matters, right? So how much you can tweak control, your retransmission, your acknowledgements, the way the secure context is resumed, the way the traffic is actually saved. So, and typically here with bad implementation, you can literally kill the battery life. So this is where you are as a strong advance compared to content. There's also a question about latency on the networks. So that's the problem, that's the rub there, which is, so you can expect latency on NBIOT networks for example, of I think tens of seconds in some cases and especially if for example, if a cell tower is under load and so that's the problem, which is you need a connectionless way to communicate with when you're building these solutions into the cloud. You can't establish and hold a connection and wait for all those transactions to happen. You're just gonna use too much energy. And so in doing that in a way that's efficient and secure and optimized from the device up to the cloud, kind of like the proper, there's only a chain is only strong as its weakest link. That's really the challenge and I think a lot of people underestimate at them. Yeah, so here within Iowa actually to solve those challenges, we have decided to implement our own co-op implementation. So that we can have control on the way retransmissions in the way timeouts, in the way optimization are handled, especially for NBIOT networks. And once again, the quality of the latter time implementation matters because here, this is typically the kind of issues that we help a customer with in shortening their product launch because if they use a bad implementation, they will face those issues and they will not be able to sustain their, their device on NBIOT network because of latency. Great, and it looks like in the chat panel, attempt to put in the link to the downloads, to the binaries, so you can get those and before you get the presentations as well. Please, if there's any more questions, we're gonna allow you in a few more seconds to type out your questions. Other than that, that's gonna wrap up the webinar. And of course, if you have any specific questions that you'd like to take offline, we're available to you. It looks like we've covered most everything. All right. Right, so Lotho, I came at, do you have anything else to add before we close this session? Yeah, I would like to take this opportunity to thank you, Hiotirok. Offering us the opportunity to do webinar together, to thank all the attendees. And again, to restate that ST, we really value the partnership with you guys and look forward to build a nice story together. Great. Thank you, Akim. We value the ST contributions here. So I really believe that the combination of our value additions, so STN32 and Iowa, it is a great for the industry to move forward to open standards. So thank you again. It was really a pleasure for us to have this session with you guys. Thank you for all the attendees. The nice questions. And I hope to hear you soon.