 Welcome again here on day two of the Embedded World 2023. And thanks for joining us here at the Exhibitors Forum. Our next topic is matter, the promise of seamless device interoperability. And our speaker today is Paolo Scaniofi from STM Microelectronics. Enjoy. Yeah. Good morning, everyone. The sort name is Scanifio, indeed. And today I'm here to give you an overview about matter, because in 30 minutes it will be very difficult to give you the taste. But the aim of the presentation is to give you some seeds, some information, and some input about the standard. Before to start, I want to share with you an experience that I did exactly yesterday that gave me a better view about matter. Yesterday, I think, like the most of you, I landed in the Moonee Airport. And I needed to rent a car to come here. And when I go into the car, my phone was completely discharged. And so I took my USB connector. I connected to the car. And after, I think, five seconds on the display, it appears a message, OK, do you want to enable Apple CarPlay? Oh, cool. Yes, sure. Sure that I want. A few steps after, I did add my screen that I'm happy to have on my car. Everything was mine, my icons, my setup, my agenda for the telephone. And I said, oh, cool. That's the aim. My user experience at that time has been fantastic, OK? Seamless usage, two steps, everything went fine since the beginning. And this is exactly where matter want to bring the IoT connected devices. Because so far, let me skip the agenda. We will talk about the agenda. So far, the IoT connected devices has been a huge market. And so far, if we see, if we have a look about the CHR that are indicators of the growth from 22 to 27, we can see that if we took a couple of technologies, Bluetooth Low Energy and 802.15.4 as a marker or indicators about IoT connected devices, we can see that there is a growth, OK? But it's also true that so far, IoT connected devices, the mass deployment of that has been slowed down because of many factors. And what are those many factors? I think that you can share with me your common experience, OK? In your house, you have perhaps Google or Mochita, someone Alexa. Others can have Apple, OK? And then you have your wife that is Google, your son that is Samsung, OK? All those main brands did a good, very good job to create ecosystem infrastructure to secure and to create a very good user experience. But indeed, they are still bubbles, OK? Each one is doing what they want. There is not a common way to interact. And then if you have, I don't know, just to say two names, Alexa and Google in your house, they don't talk. They can stay, but they don't talk. And sometimes if you say Alexa or you can call Alexa Google, he said, no, I'm not Google, I'm Alexa, OK? And here, if we talk about the big names, the giant names, but if we talk instead of the IoT mass and cheap devices that we have out there, we can understand that you give to those devices your credential for the Wi-Fi, but who grants you that those are secure enough to protect your house? I don't know. They have my credential. And if they start doing something, you know that the latest attack to your houses is made no more on the routers that are now protected, but from the small devices, like connected cameras, connected switches, because on that, so far, there were not the idea to make them so secure, so protected, and so on. And then, come on, you open your smartphone, you have the application to the gate door opener, the application for this, the application for that. OK, the user experience for guys that are technical is good, but my wife say, OK, Paolo, please manage the device yourself because I cannot understand too many, too many stuff, OK? So those problems that are listed here, so huge complexity, there are many. And for sure, there are kind of, say, users that are not able to work around and to try to find the solution. They are not. It does not work in a minute. Oh, OK, put. Vast it immediately. Various ecosystem, as we said, and then the lack of security, OK, overall, OK? I don't want to say all, but overall is a lack of security. And so the market was strongly asking for a simplification, OK, to improve the IoT adoption. OK, CSA, the Connectivity Standard Alliance, comes, understood the problem, OK? We have to remember that they were already in this philosophy with ZigBee and with other protocol, but they understood that a step farther in needed to be done. And in fact, they unraveled all these problems that we discussed, and they come with something, OK? We deem to simplify, to create an open context, meaning something that everyone can adopt, OK? To promote, again, this open standard and to enable all the objects, IoT connected, to be secured, connected through an open standard. And this, as a name, is Matter, OK? So Matter is meant to create a seamless and super user-friendly installation, super secure environment so that you don't have to go to the shop and say, OK, I do have these at home. So what I have to buy, this is compatible? No, it's Matter. Whatever is your system at home, you buy it, and you install in few steps, OK? So what is Matter? Matter is an application layer, no more than that, OK? It's an application software running or relying on top of standard layers that are well-known to the market that are basically IPv6-based, OK? So it uses IPv6. Why IPv6? Easy, thousands or millions of addresses, worldwide addressable, OK? It's well-proven, and it is available on two or three main channels, Wi-Fi, OK? Thread that is able, it is a narrow-band 2.5 gigahertz protocol that is able to transport IPv6, and then, of course, also Ethernet, the standard cable, OK? So please remember this stratification or these layers because it matters, because it gives you a real idea. So also, when we will talk about the certification, you will understand the kind of certification that you have to achieve in order to have your product ready matter. The context. The context is basically smart home and smart building, OK? So let's talk about the smart home. We know very well. I don't have a three-floor house, but OK? If you have a good for you. But the idea is very simple. You have this guy that is a border router, OK? It is connected to your access point through Ethernet or through Wi-Fi, OK? And what this is, a main task, is to create a thread network in your house. Thread is a mesh network, 2.4 gigahertz IPv6, as I said before. And the good is that, OK, even if you have a three-floor house, because of the mesh, if the border router is not able to reach directly one device, the mesh is self-adapting in order to route everything to the border router. And then you have the smartphone. In this case, that's a smartphone, but it's not limited to the smartphone. This is the controller of your network. We will see right after some other possibilities. The smartphone is used for two tasks, basically. The first one is to allow or to easy the enrollment. You buy a new device. You want to put it home. And you need a way to say to your network, OK, this is a new device. And this is typically done with the smartphone thanks to the Bluetooth low energy. We will come in a minute. And then when the new device is enrolled, is onboarded on your network, OK, you may want to light on the lights and to do additional stuff, OK? So this is the way with which you embark and you control your network. Some terminologies, OK? As I said before, the controllers. Controllers is the equipment meant to control the network. I give you the example of the smartphone because it's the easy one. But it could be something else, your home assistant, or perhaps also your thermostat. The test, it is matter-ready. And it is also a controller or any kind of display with which you can control your network. In your matter network, you can have many controllers, OK? Your wife may want it to have its one, your son, so also. OK, that's all. And then the targets. The targets are basically a cluster. And this is coming directly from ZB concept. Those are kind of equipments that have a common profile. And so you have those targets that you can control. In addition to that, those are still targets that belong on a different, let's say, subgroup. We do have the access points or the border router and the bridges. I will give you basic information about both in a minute. So if we come back to your network, OK? This is a little bit more complex, OK? Believe me, then you can see right after. You have your router. This is your access point, OK? It must be IPv6. Otherwise, the game does not work, OK? Your access point. And then you have your border router, OK? The border router, as I said, is meant to establish the threat network. And then you have your threat network with many devices, OK? Then you have controllers, OK? Many, many smartphones, many and equipments, OK? The transportation layers that you have here can be Wi-Fi, as I said. So your network could be Wi-Fi, only Wi-Fi without the thread, or Wi-Fi and thread, or only one of those, OK? But at least one of them you must have, or Ethernet in addition to that. As I said at the beginning, Bluetooth or energy, in this case, is used, but it's used only for the commissioning. After the commissioning, Bluetooth goes deep. But there is a complexity from a technical point of view because there is a moment on which Bluetooth through energy and thread, or Bluetooth through energy and Wi-Fi, must work together at the same time. And this creates from a technical point of view some headache, some troubles, OK? What matter add, because this is more or less, OK, where is the new, OK? What matter added is the security at each stage of the process, OK? Starting from the enrollment. Basically, a new device, first of all, it must be matter certified. Otherwise, OK, you cannot use. Full stop. Also, the enrollment, meaning before you deploy the credential of your Wi-Fi or the keys or the master key of your thread network are deployed to the device, must be verified as a genuine system. Otherwise, the system is not getting any data that is super sensible for you. If you deploy your Wi-Fi keys, you open your network, OK? When the new device that have been defined as genuine, good, certified, and so it is deployed with the Wi-Fi credential, for instance, joined to the network, each single byte here is encrypted with the most secure encryption that we have nowadays, OK? So the aim of this is that your network is secure, your data are really secure. OK, this is a good point. But what if you already have deployed on your house a lighting system? So you already spent a lot of money. And so what? Now that the matter comes, so you have asked everything, and OK, no. CSA did a good job here because they also foreseen the possibility to add bridges, OK? Bridges are bridges, OK? Are the guys that are simply, let me switch, that this is nice, are simply translate, the matter word into something else, OK? So you have your lighting bulb system that is ZigBee, that is SubGiga, that is, I don't know, you invented it because your company has a super know-how on SubGiga super secure system, OK? No problem. You can translate the two words. This guy, what have to do is to take your private network or the existing network that you have, and he has to translate the profile, the cluster, OK? The information that is transferring. And that's all, OK? Of course, in this case, the complexity is a little bit higher, and we will see in a second. But this is absolutely feasible and stated on the matter specification. And this is great because, as I said, the thread is 2.4 gigahertz, good. But we know that 2.4 gigahertz could have some issues in range. So you can bridge with SubGiga, why not, OK? And have your system. How this technology or these requirements translates on devices, OK? You remember the first slide that I said, please remember? We have the matter layer. Then we have TCP, UDP, IPv6. And then you could have thread, Bluetooth or energy, perhaps also Wi-Fi all together. And then on top of that, you may want to do your application, right? Otherwise, it's useless. And so the stratification of the software is huge, OK? This is not meant for super tiny or super constrain devices. But we will see in a moment, you have still the possibility to use standard wireless MCUs with some special requirements. But those are standard, OK? So for the end devices that could be TV, TV, HVAC controls, or whatever, you can use a standard wireless MCUs. Or you can use a standard wireless MCUs as a co-processor, OK? Because perhaps your system has a super cool graphic display, 10-inch, OK? So a wireless MCU is not meant for that, OK? So you can keep an MCU high performance with graphic support and then use a standard wireless MCUs as co-processor. While Fourier Assets Point bridges, border routers, and bridges, in this case, they need to do something more, OK? The computational power they need is a little bit higher, because typically they are translating the Ethernet IPv6 to, if it is a bridge to something else, to ZigBee, OK? So typically, it is used a wireless MCU as a co-processor for an MPU or a high performance MCU. And we will see our development, OK? Certifications. Again, remember this stratification that I said, Bluetooth or energy, thread, Wi-Fi, and then matter. All of those must be certified, OK? And before to go to the CSA and say, OK, guys, I'm in you. I want to certify matter by product, you have to demonstrate that you have the, if it is Bluetooth, you have this SIG certification. If it is thread, you have the need to be thread group certified. If it is Wi-Fi, you need to be Wi-Fi aligned and certified. And then you go with those certifications to the CSA and say, OK, I'm already, the transport layers are certified. Please certify my matter application, OK? It's many steps, OK? That's the message. As I said, you must to be certified. Otherwise, the party does not start. For the time being, you must to go to accredited laboratories, OK, so you cannot inherit in any meaning for a new device. You cannot inherit any previous certification, also coming from the Silicon vendor, OK? And as I said, each layer must be certified. So what are the challenges as of today? Again, the memory footprint as of today is 900K flash for a single instance of matter, 900K byte, OK, flash. And then if you want and you must have OTA, you have to double. And then you have also your application on top of it, OK, I don't know how much is your application. So it's not meant for tiny devices. You need thread and Bluetooth through energy concurrent. Just to say that Bluetooth through energy is not mandatory. If your equipment has the possibility to enter by a meaning of display or keyboard or something else, the passcode, OK? So it's not mandatory if you have another meaning to provide a declaration. As of today, the ecosystem from the CSA is only Linux, OK? And this is, OK, could be a trouble, a deck, something more. And then how CSA gives you the right to put on the field a new device. The rights are coming from the DAC. And the DAC is a certificate that is the result of your certification process. This certificate is signed by a route of trust, OK, for which you need the pie that is a key. And these must be deployed into your device. So each device must be provisioned by at least the DAC, additional keys. You need to ask to the CSA your vendor ID. You need to have your vendor ID and product ID. And there are additional, it is called data factory, something like that, that describes your product, OK? All of those must be deployed in each device during your building, OK? And again, to reinforce the message, everything must be certified. OK, how we at SD support this business, OK? Or this opportunity? With two main, let's say, macro blocks. STN32, I think, I hope that you know, our STN32 MCUs that could be used for bridges, for access point, or even DMPUs, OK? With the STN32 WB wireless series, that is what you need to go wireless. And then thanks to the ecosystem, the STN32 cube ecosystem that provides you all the need, the software, the software, the tools, the debug, and so on, OK? Everything stated here, a part of the MCU that you have to pay, is free of charge. A quick snapshot about the STN32 WB series. When you see W after the STN32, it means wireless, OK? So why the STN32 WB? Because it's a dual core, Cortex-M4 and Cortex-M0, because we don't know how much is complex to your application. Remember, matter is an application layer, OK? So what we do is to load these stacks, Bluetooth or energy, and thread on the Cortex-M0 plus. And this is a black box, this goes, OK? You cannot touch, you cannot influence or corrupt the protocols. And then you have the Cortex-M4, where you run the matter and your application. One megaflash, 256K byte of RAM. I forgot to say that the RAM needed by matter is about 200K, OK? So you still have some freedom, more or less, OK? WB is good because it's multi-protocol. Also, it is able to run in concurrency, matter, and thread, or ZIGB and Bluetooth, pardon, Bluetooth through energy, and thread, and or Bluetooth through energy, and ZIGB, simultaneously, OK? It's a one-stop shop because we do provide all the ecosystem needed for you, starting from the graphical configuration of the hardware at the check of if your hardware and your peripherals are good, up to the tools to certify or to verify the radio frequency. So everything is inside this main box. And then there is a large portfolio, OK? Large portfolio that includes module. So on our booth, and I invited you to reach us, on our booth you will see a matter running on the SOC and on the modules also, OK? Why the modules? The modules are very cool because it has 72 GPIOs, OK? So you can make your application. It has one Mac flash, and in addition to that, it does support the execution in place thanks to the code SPI. So you can enlarge the flash as much as you want. And then 10 years longevity commitment. This is a legal commitment. Every year, we renew these 10 years, longevity commitment, so you can count on these devices at least for the next 10 years. If we don't renew the program, it means that you have nine years in front of you, OK? Super cool. And let me add a very important point, ST invested a lot on capacity for wireless products and for other products, OK, now are serious. So zero problem of deliveries, zero problem of capacity. We are coming all from a very good moment. OK, let me skip rapidly these, but the SDK that we do provide are available both for Linux and Windows. So we do a step forward versus what as you say did so far. So we do provide the Linux and Windows environment. We do provide the XCube matter. This is an SDK. This is an add-on. Why an add-on and not integrated on our environment? Because these is STM32 agnostic. You can load the XCube matter onto an MCU or a wireless MCU in order to build your application, OK? So it's agnostic for that. And then we do have also a GitHub hotspot. I will give you all the references right after in which we provide, let's say, unofficial releases, OK? And so far, because we are still in the process to finalize our releases, all the deliverables are in GitHub hotspot. GitHub hotspot, OK? Let me skip here. So the demo that you can enjoy at our booth where there are experts on the topic that can answer to all your questions and where I think that you can also get some evaluation board for free. OK. In terms of this is the block diagram of the application, OK? So you have your controller, the smartphone. You have the gateway. And in this case, we will see is an MPU with the STM32WB as a radio coprocessor. And then you have the matter device that instead is fully running on the model that is this guy in the corner over there. If we translate in, let's say, a better block diagram, I like this one, OK? So what you can see, OK, here, you can control your network through two devices. In this case, I think that you have recognized this is a Google Nest or your mobile phone, OK? Those are Wi-Fi connected to the gateway, OK? Or the border router. The border router is a standard MPU, OK, connected with the WB as a radio coprocessor. And this creates the thread network, OK, with which the end devices are connected. The demo is a light bulb, so you will see giant bulbs. And the idea is to de-merge, to switch on and off. This is a cluster for the light bulb. Funny story is that we are running a matter on the evaluation board, the nuclear. This is the easiest one without any additional stuffs around or on the discovery that is based on the model. The model, again, is this guy over there. It's 11 by 7 with integrated antenna, OK? The matter bridge. We do have also the matter bridge, OK? But we don't have here today because of the space on the booth. The matter bridge is easy, OK? It is based on STN32-H7, OK? H7 is in high performance. It's a Cortex-M7 550MHz, OK, with a lot of power computation. It is used the STN32-WB as a radio coprocessor, and it translates matter to ZigBee. And this is all the riverables that you can download and test by yourself today, not tomorrow. OK, take a ways, guys. Sorry, I go a little bit longer, but three main takeaways for you today, and then we are done. So we really, we strongly believe in matter, OK? There are still some question marks about the size, about the challenges, but the bases are very good, OK? So we really believe that matter is the base for a massive IoT adoption, OK? We at ST, we are fully committed on matter. We are also on the board of directors, and we are ready to follow as we do now and the future the new releases, OK? And we do support on all our series, from MCU and MQ. And finally, you're welcome to join us to have a talk with our expert. I will be also there. They can really go into the details, OK, if you have any additional question. I'm sorry for the question. I think that we don't have time, but really, if you want to join, please join us at the all for A. And here are some QR codes where you can get access to the deliverables ready today. So thank you very much, and see you at our booth.