 Hello everyone. My name is Marc Avieux. We are CES here. I'm IoT marketing manager. I'm going to talk about the partnership we have between ST, a semiconductor company and the operators. These operators are Verizon and AT&T and are developing LT, CATAM network and NBIOT layer-on that are very adequate with the ST product portfolio. We're talking about microcontroller and sensors and we are talking about low bitrate, long-range battery and low power devices. So the first one I want to present is the Verizon one and the value we wanted to present in this development kit in this product kit are our free nature. The first one we want that to be an IoT enabler meaning a lot of sensors, a lot of capabilities, even more than we can normally use in one use case, but providing a lot of options for the customers. The second one is the sensor to the cloud experience. It's important that we do not stop just to send data out, but we also try to present those data so the customer can make use and very easily manipulate those death kits and gain on time to market because this is at the end what we are looking for. And the most important thing that we wanted to have is to simplify the cellular experience. It's not easy. There's some stuff that are not easy to manage and we are presenting a great tool to ease and to again accelerate this time to market for all of you that are developing products. On the side, certification is important and we have been some good steps to help on that side as well. So first of all, the hardware. The hardware we have we are working on with an IoT discovery kit that is based on all the development kit that I'm going to present today. And this board is it's a concentration of technology. Basically, it's a loaded of feature of sensors with accelerometer, gyro, magnometer, humidity, temperature, pressure, time of flight for proximity sensors and also a couple of microphones there. It is all articulated around an STM-32 that is STM-32 L4. It is in the middle here. And it's also getting a lot of local connectivity. I'm talking about NFC, BLE, sub-gigards and obviously the Wi-Fi will be replaced by the LTE, CATM and NBIUT. And for that we have done an extension and here's a modem that ST has developed. For Verizon, we are also able to provide the SIM card because we have the product for the right profile for Verizon as well. I'm going to present you the software side of the XCube cellular that is a package that is published on the ST network. So it is running on the STM-32 and the big value of that package is that it is including a cellular driver. The value of that is that it is isolating the application from the complexity of the modem. Meaning what? Meaning that all the APIs that you have that are presented to the application are ultra simple, super simple. You connect, you send data, you receive data. You don't even know that you are on a cellular network. So this is an application that is an HTTP client that is going to present to a dashboard later on on the cloud. And basically the cellular driver is going to do all the work of setting up the communication, managing the communication, even managing the errors because again we are on a cellular so we can be moving and losing signal. So it's very important to do all of this. And it's going to send the right 80 commands to the modem and we're talking about the module that is a certified module on the Verizon network. Basically this is what the rendering is that you have here on the board. You are able to see all the various sensors and to see them moving around, temperature, humidity, pressure. But you are able also to control back and LED. So showing a back and forth communication with the board. The second application I wanted to show and the DevKit that I wanted to show is the Amazon FreeR task. And actually it's a little bit closer to the product because the cloud solution is no more an HTTP example. It's really something much more real. This is basically a AWS core from Amazon. So Amazon has created what they call Amazon FreeR task that is basically a distribution for microcontrollers. And what we have done is that we have inserted in the distribution the cellular driver middleware. Again all the value that I was presenting before applied to this solution I'm going to probably do a little bit more detail right after. And it is generating the right ET commands for the model. So if you look at the cellular driver, all the values and a little bit more detail than that. So first of all you don't need to be an expert to develop applications for cellular anymore, right? This is going to help you in a big way. It's going to present a simple application, a BSD-like API for the application level. It's also going to present the AL for an abstraction layer for the ET command. And why is this important is that because you want maybe change the modem and use another modem that fits better your business model. So for that it's a very simple file to change inside the code. And you're able to control and change to a different language of ET commands. Because unfortunately all the module makers, even the chip makers of cellular radio do not have the exactly same ET commands. But they are commonly you know having the same language roughly but with different syntax. So we are able to adapt to those syntax inside the middleware. So that's pretty important. Error management again they're important at the device level, at the network level as well. Then certification. We have added certification features inside the middleware. And why? Because some features are not supported inside the module. And I expected the application to do that. So typically for Verizon we had to insert the DSMA, TSA, TS34 and 35 that are a mechanism to manage when there are errors on the network. So every device do not overload the network at the same time. So kill the network. So this is our protection that Verizon requires for the certification that are not supported by the module maker that we have to do. So just to help again the developer to go faster to market. And also what is important is that this dev kit from Verizon is distributed by Arrow. So you have an Arrow landing page and you have also a Verizon landing page on which also that kit is detailed and you're able to acquire the solution. So what is important as well is that the modem used in the Verizon dev kit is QuakeTail BG96 and is able to feature LT, KTM, NBIOT and 2G fallback. So basically we have tested this device on real NBIOT networks so we know it works. And Verizon is going to deploy later on is their NBIOT network. So this kit is going to be ready in future proof for when this network will be up and running after deployment. So let's talk about the AT&T network now. This is a network that is LT, KTM today, deployed nationwide in US. They have done a very nice job of presenting the AT IoT starter kit in a box like this with the ST solution and this has been created with Avnet as a main partner. So Avnet is manufacturing the modem here that's a shield on top of the IoT discovery kit. ST is presenting all the code that is on the STM32. So this solution is basically presenting data from the sensor to the cloud and the cloud is an AT&T flow that is going to store and get all the raw data and from that you can connect to AWS, Azure and others from cloud to cloud. This is their way of working with the ecosystem. So I hope those desk kits are going to be very helpful for you for your different applications and we thank you very much for your attention.