Hi everyone, welcome to today's destination Lorawan webcast. We are going to go ahead and get started in just a few moments here. Thank you for joining. Alright, hi everyone, we do want to go ahead and kick off on time here, so let's go ahead and get started with today's destination Lorawan webcast called ensuring device success with Lorawan certification. Thank you for joining. Before we dive in, there are a few housekeeping notes to share with you at the bottom of your screen you will see a bar of application engagement tools to help guide your experience. You can also move around and resize the different tools on the screen as you need. If you notice the slides or video is behind, simply pressing F5 on your computer will refresh your screen and help you catch up. Most importantly, you can see the Q&A box below the slides we are going to have a live Q&A session at the end of today's webcast with the panelists, so please be submitting your questions throughout the webcast into that box labeled Q&A. Lastly, an Ondemand version of this webcast will be available within 24 hours, and you can access it using the same link you used to join the webcast today. Lastly, before we jump in special thank you as always to our destination Lorawan sponsors who helped make these web casts possible. Thank you to machine QA Comcast company as the destination Lorawan gold sponsor and thank you to our two silver sponsors, Birds and Charter Communications. Now let's get into the great content we have for you today. It is my pleasure to welcome our two panelists, Derek Hunt, from the Laura Alliance and Mark Roberts from 11X. 11X is a Laura Alliance member and we are grateful for their participation and leadership of today's webcast. And Mark will be joined alongside Derek Hunt, the Laura Alliances director of certification. And now I will hand it over to you, Derek, to interview, to introduce yourself and get this webcast started. OK, thank you very much, Megan. It's great to be here and have the chance to talk about the certification. So my name is Derek Hunt and I am the chair of the Certification Committee. Really, there's a few things we want to try and cover today, and one of the points I wanted to start with was. We've done a survey recently to try and get people's view on certification and what's stopping them and what's helping them. And there were a couple of points that came out of it that were slightly concerning, so I wanted to also make sure that we can address some of those questions that have come up on it and there was one in particular that I wanted to highlight here, which is a comment from one of our Members which basically said certification is not needed as we using. The Laura chipset from Semtech. Well, clearly that's just the RF side of it and the Lorawan side and the certification side is very important to our devices and needs to be done on top of whatever testing is done on the pure RF side and the other comment that came out was just about the regulatory requirements so that within the Lorawan we do lots to adapt the use of the Lorawan in that sub one giga Hertz space wherever in the ISN band you're using it in the world. So we try and make sure and we do everything to make sure that the Lorawan complies with the regulatory, but that still doesn't mean you don't have to go through that regulatory approval process yourself. So really, what I want to cover is is sort of a bit more detail about what certification does cover some of the benefits that it will bring with you, and then will also be a section where we talk about and Mark will join us in a bit to talk about the real life scalability issues with these devices and some of the things that he's seen whilst trying to get devices up and running. And then we'll come back to myself and I'll go through what the alliance is doing to try and help with that process. So if I really starts with the benefits, why is Laura Alliance and why is the Lorawan certification so important really? It's to give everyone the confidence and reliability that the devices will work as intended. There's lots of cases where that doesn't happen and Mark will go through quite a few of those, but the other thing that is clear is if you can find a fault or an issue earlier on in it, it's far easier to fix than it is later on in the life cycle of your device. And also if you have the marketing approval with the Lorawan certified logo, it has that ability to use better promote your device. And really, the final thing is poor devices caused performance issues which actually has a huge impact not just on the operational side of it, but potentially the cost of returning ones. So the certification program is available to all lower alliance members and there is a category separately for certification affiliate. So if I go in through what is a certification about? Well, the key thing really is this assurance assures that the Laurel and protocol is there too, and one of the key things that we find is it makes it and ensures that it will work under any operator condition. We've seen lots of instances in the past where devices tested on one network and then goes to a different network because they use slightly different parameters, or it's a different set of configurations. It doesn't work that way and causes problems so. The lower line certification program goes through all the different parameters and make sure that it can work under any network condition, and it also gives us the reliability, so it guarantees to adhere to the law under standards and we do everything we can to certify the device in a normal operating environment, so there's no extra wires or connections you need to it. It's basically as your device is going out the door and the key thing really is to find those issues before you get into production. So it saves helps save time as well because we do it. It's one day testing at the certification test labs. Unlike a lot of the telecoms products which are usually weeks or months and then we use an automatic automatic test system to maximize the coverage within that time frame. So really, the cost saving benefits is it reduces your design rework cycle and helps keep the maintenance costs load though, and we have worldwide testing solutions and I'll talk a little bit about some of those so that you can know exactly where to go. What we've also implemented is a separate RF testing and I'll talk a little bit about that and what it covers, but that's really to help when you're deploying a device to know what performance you're going to get out of it, and it makes it quicker for you to deploy your network. And the final one security is a big issue for all of us. So we test and we guarantee that everything in the Lorawan from a security point of view is covered by that certification program. So just going limited detail on how it works, you see from the picture in front of you, we have the device under test the tut, which is really your device you're trying to certify. It runs the Lorawan protocol stack and it's connected to a gateway and this is a standard off the shelf gateway. Again, everything's been done to keep the price and the cost of certification as low as possible, so it uses a standard off the shelf gateway and then it connects up to a control layer. I'm not control. There is over the LCT and I'll talk a little bit about that later, or it's a defined and determined one that the authorized test houses have put together. But basically, when you were going through certification, it supports all of the different modes of operation. As I've talked about. So whether it's over the air activation or activation by personalization. And really, the IT does it in another quick chamber so you have the advantage to guarantee the rate, and that's for a couple of reasons. One, it gives you the repeat ability because there's no other outside traffic to do it, but also one of the tests that we do is actually to test the packet error rate. So we want to make sure it's the devices performance that you're measuring, not whatever background noise or interference causes a problem for the device and the whole process sends and receives over 2000 messages. So in terms of authorized test houses, we have six orthros test houses. They have locations all over the world. The key thing with that is it's trying to ensure that if you have a device that you want to be tested, it can be tested as locally as possible to you. And because the ISMA band is different in all parts of the world, the certification itself is against the different regional parameters, so it's trying to make sure that you can test their instance in North America against Europe, or you can test in Asia against Europe or North America, so the test houses also have the ability not only to test locally in their region, but they can test for the region that it's going to be deployed to. And in terms of you as device manufacturers, they only cost you pay for certification. Is the fee you pay to the authorized test House unlike a lot of other alliances, the law reliance does not take any cost for issuing certificates or giving you certification from it, so that is free to all our members. So finally just quick run through. Once the device has been certified. We then publicize it and promote it and we for those people who have seen we have a showcase on the Lure Alliance website where we go through and highlight all of the certified products. What you can also do on this website is then search for the different region of Lorawan that you want it to go for and also the different regional parameters that you want it to do as well as there's a feature in here as well now where you can look at it and. And filter it by the RF performance that you need for the device. So all of those things are here on the showcase. The link is on here, but it'll be in the slide set when we follow afterwards. Sorry, that was my quick introduction to the certification. If you got questions and and you went there, to which you want answering, please submit them while we go through. But now I will hand over to Mark Roberts, who can go through some of the real life issues that they've seen during that process. Thank you Derek. I would like to introduce myself. I'm Mark Roberts from 11X. I joined the company about a year ago to start his center of excellence and in the Center of Excellence we offer specialized engineering services around Lorawan and especially some best practices testing that we've found useful as a network operator and what we will talk about today. So I think everybody recognizes the benefits of Laura when it it really has unlimited potential in 11X. Is case we started to create a Canada Wide network about five years ago, and after determining that Lorawan would be the best overall solution for low bandwidth, low power IoT solutions, and I say that. With most of our engineers coming from a cellular background, so initially 11X tried to deploy with cellular IO T and ended up moving towards. Towards Lorawan for our Canada network. But more land solutions. Significant fill a significant gap in the market, but only if the solutions work flawless. Leanne. Scale into mass. Mass deployments. And so that brings us to. One of the problems in the industry today. You know many devices failed to deliver on the promise of Lorawan. Yeah, we found in field deployments that we've encountered many issues that limit scalability and scalability issues include things like basic device functionality, the performance, the interoperability. The reliability and robustness of devices we've seen problems that range from drastically lower than expected. Battery life to basic stability issues. Connectivity issues, inadequate security, you know, and many of these issues turn up in device deployments and. Aren't practical to test at the certification stage. So in our first suite of testing, some of the common problems we encountered in the field. We found that no device passed all of the tests that we did and no test was passed by all devices. So clearly we have a device quality problem and network operators must do their own testing. Qualification of devices for field deployment today. So going through some of the issues, I would say the number one issue that we encountered was device documentation documentation. We typically found that only about 40% of the information required to execute our tests was provided by the device maker. And when you contact the device manufacturer, often they providing complete feedback an I think this can be traced to the fact that in many cases they are subject matter experts in their sensor and their sensor technology. But they've used modules or or. Contract services to get their Lorawan so they don't have a complete understanding of it themselves sometimes. Device provisioning was difficult. You know, in a typical North America requirement, like setting a subband was not always supported by the device in a reasonable or convenient fashion. Security is still very loose. We see devices coming with blank keys or simple formulas for their key creation. The mechanisms that makers have today for key distribution is very poor. And when they do use QR codes, there's inconsistent use of QR codes across the industry. No Derek in the next part of the presentation will be talking about how to address some of these issues and and in this first case the Lorawan certified supplementary information that they have in place. For EU network operators, that's a very important initiative that I think needs to be. Realized in North America as well. Another big issue, and what represents the biggest part of our suite of tests is connectivity corner cases. No Derek mentioned in his introduction there that Lorawan certification testing is is necessarily limited to a reasonable time frame. You have to keep this certification process economical so that it can be widely adopted, but some connectivity issues appear only in long duration testing. Yeah, you know and some questions you might ask is what happens when a device loses downlink. So we do a five day test for that. How many uplinks are actually performed each day? That's a 48 hour test. How well does the device follow the the retransmission backup guidelines for joining? That's a 36 hour test and they have announced repetition is many, many power cycles of the device and 20 join requests each time. Does the device work properly on all the data rates that they claim support? So to give you some anecdotes on these, in the case of loss of downlink, we've typically saw a failing device transition overtime down to data Rate 0, but then they go silent. They don't try to rejoin again, and so that device can be lossed. If you if you have a remote gateway, I would ensure that you don't get it. Repair in time. You could lose large swaths of devices that you would have to then roll a truck and re. We can figure it, get onto the network again. The number of uplinks you know there's an unpredictable number of uplinks by many devices and. That becomes a scalability issue in mass deployment, so we like to see a very predictable number of uplinks typically. Pending retransmission back off that joint Test. You know, a lot of devices don't follow the time on air specifications, and it's not until like the 11 hour mark that we see them start to fail. And diverge from the requirements and also when devices are joining. You really need to thoroughly check whether they're using all of the channels and check that they use the lowest data rate to join and and some devices never use the 500 kilohertz channel, for example, so. That is all issues that we can countered in the field. Yo dude, definite repetition. If you see a device fail in that area, it's probably traceable to the same Laura stack and the same MCU combination where you know for whatever reason, the pseudorandom number generator wasn't good, and and so we do see a number of devices in the field today that have. Darkness, repetition. In the trial. Strange join behavior. What I mean by that is there are a number of devices out there that will join the network. And then remember those settings forever, even if they're powered off. So this could be an issue. I mean, they become like an AVP device that this could be an issue if you reconfigure network and you expect the device to rejoin and get a new network address for instance. So so some unexpected behavior there. Now another big issue for I think everybody in the industry is the battery life. It's one of the biggest offers that Lorawan has is really long battery life. It's very reasonable to expect. To achieve the battery shelf life of the battery in deploying devices that have power fishing sensors having to go out in the field and replace batteries could destroy the economics of a mass deployment. And devices unfortunately fall short of their claims in the area of power power consumption. So we feel that with manufacturers, many manufacturers are are quite optimistic about their battery life may be choosing a best case scenario, but when you look at a practical mass deployment you have to allow for devices being somewhat removed from the gateway and so you need to pick typical worst case. And use a fairly low data rate, have a reasonable activity level from the device, and so we've incorporated all of these things into our battery life. Estimate testing that we do, and we've lately integrated the Nordic Power Profiler 2 into our test setup and we found that with its 100 kilohertz sample rate, averaging those. Data points in real time. He was excellent amount of detail to debug problems with the device and also gives a very good battery life estimation. Finally. There's issues with network interoperability and this is becoming a lot more important as the details of roaming and broker systems are worked out. Bottom line is, you know LNS is or it's a top line in this slide elements are not standardized or certified, and there's a lot of subtle differences between Lorawan network servers due to the interpretation of the specs or the philosophy of the network server creator. Network servers are slow to change and and often they haven't adopted the newer features in the standard that resolve legacy issues. A couple anecdotes in this area. You know our own network server. Is story wise that we use and in the early days of the standard there was some? Interpretation required by the device when they received multiple Mac commands in a single packet, so typically would be like 80 R link commands and so or be wise had to restrict the use of ADR link commands so that you wouldn't put the device in the situation where it executes the link commands in the wrong order and then ends up ignoring. Commands because it would shut off. Some bands like all the subbands and disconnect the device from the network or. Alternatively, it might actually go ahead and and execute the commands in the order that it feels is right and then and then disable end up disabling the device from the network. Now that is subsequently been improved, or. Worked around in the latest versions of realize you. They they put the ATR link commands in in a specific order so that they there's no chance of misinterpretation, and they tend to want to see you turn on new sub plans first before you turn off any subjects, so that resolves that issue. Another network server we've seen. Some issues with his is chirps that so we used chip stack internally a lot in our testing and. 11 X 10s with our meter interface you know we want to run in confirmed packet mode. It turned out to be the most efficient way to run that kind of device and chirp stack. Interprets the re acknowledgement of confirmed packets. As. You know a possible attack vector for denial of service attack, so somebody could replay the confirmed packet. And use that as a way to deny service by getting re acknowledged those packets, Sauternes sectors won't issue re acknowledgements and if you are a device that runs in. Confirm mode, that could be a serious problem, because if you're out on the fringe of the network and you lose one ACK packet, then you're kind of forced to go into a mode where you try to replay or get that packet Re acknowledged up to 8 times, and that's that's a drain on your battery and your overall system, especially period, mass, mass, deployment of sensors. So finally, you know, as I said at the Sept. 11X has this center of excellence, which offers a number of specialized engineering services and importantly some some best practices. Testing and what made this possible is Semtex open source open hardware project. They call the conformance test bench budget. So we've taken that an we've customized it in an extended it. With our own test suite and using that setup, we have the option of internal or external gateways. So we have integrated chirps back on the Raspberry Pi that's part of that setup. The CTB becomes a man in the middle, so it's very flexible to let us inject commands. To the device for advanced testing and. When with this suite of tests on the CTB platform, there kind of a fleet of devices that you saw in an earlier picture. We've started to bring something like a carrier acceptance test program to Lorawan that that you might be familiar with from the cellular world. So I'll pass it back to Derek. OK, thank you very much Mark. So what I wanted to do really was just trying to go through some of the issues that marks raising and we have seen those issues as well and trying to look at what is the alliance doing to help and what can we do from the certification to help that process. So really, I'll just run through a few of the initiatives that are going through, and some of them you may have heard of. Some are just literally coming out over the next few months, so I'll talk about the LCT. Mark talked a little bit about the back of text mechanism, so there's a change to what we're planning on doing for that, and we're implementing that fairly soon, then also talk about some of the other things that operators have seen in terms of the performance of the device, the RF performance. But then also want to talk a lot of work that we've done with the European operators really to try and address a lot of the issues that mark seeing in North America and also going to talk about this extra information that's needed by the device users to affectively set it up. So if I start with the Lorawan certification test tool and I was asked from when I first started this certification program and we first started rolling it out probably 4-5 years ago now to have some sort of ability for device manufacturers to test their device prior to going to certification. So we've really been designed from the ground up to allow that feature, and what we've done is we've kept it in step with the certification program so it tests. All the features and functions of the lower end protocol very much as you would do when you're testing your device at an authorized test house. But it also is capable of running at your own facility, so you don't have to take it anywhere. You don't have to do it. You can set it up in your own lab in your own office and actually run through it. So this gives you the time and money saving by allowing you to fully test your device prior to going to a test house. But more importantly, it accelerates the process that it takes you to get through from 'cause what you really want to do is get your device to mass deployment. And the tool itself is available for both 1.02 and 1.04. A little bit about how it works and what you can see is the setup here is very sort of similar to what I described earlier we've certification. We have our device under test. Again, we use a standard local gateway. And then the LCT tool itself is downloaded to you via a PC and it runs on a PC and that PC really has a mini network server built into it, and the test control layer. And what it allows you to do is have two modes of operation. So we have a mode in it which we call pre certification and this will automatically run through all of the tests that are needed when you go through certification. There is a slight difference in the to keep the cost of this deployment down locally. We're expecting that most people would just implement it with affectively, an 8 channel gateway. But obviously for testing for North America or for Europe now you know I need a 16 or 64 channel gateway so. It has all the tests that it can do with that limitation. And in the final mode it has, which is the one really most the device manufacturer found useful. Is this debug mode. So if you run through a certification test and you find it failing, you can stop the test. You can rerun that specific bit of the test, you can put it in a loop to allow you to just repeatedly run that particular bit that was failing to help you diagnose what the issue is. And the way it's set up is it provides you all the logs in the data so you can see every message that's been transferred, sent and received by the device. And there's also the ability if you want to do other things to your device, it can send and receive Mac commands from it, so it gets the responses back from it. So you can set it up in a particular manner that you want to do, and this tool is available to all lower alliance members. It's part of your membership benefits, and you get that to run an on your local PC so it really is a local way of testing it. To all of their lifecycle of your device. And the next thing I wanted to talk about was, and as Mark mentioned, we've had an issues raised with what we've sort of locally turned zombie devices, and these are ones that sit out in the network and are just continually sending join requests. And as Mark says, that test is a 36 hour test to run, so clearly it's not feasible to include it within the certification test. The cost of running that unauthorized test house would just become too prohibitive to do. So we're just introducing and will be rolled out in the next month or so. Is a test mode in the LCT that actually allows you to run this test before the device is certified, and then once you've got the results out of it, you'll send those results with it with the device you want to be tested to the test house and it will be included as part of that certification process. So with this we now have the ability to run some of those longer tests that Mark was referring to. And we can also use is looking forward to say, well, are there other tests that we could look into putting into this? But certainly this will become part of the certification process within the next three months. So the other thing that's really critical for a device is the RF performance of it, and you can see from this if you want to get the best performance out of your device, it really isn't. It is critical that it has a good RF performance, but the trouble is a lot of our devices, they are really ones that can either be mounted on a desk or put on a wall, or put in a certain configuration or orientation. And what really being useful? And this is what was really requested by the operators that we worked with is not just to have what the output power of the devices, but to do a 360 degree scan of it so that when you see the test results from this, not only can you find out what its maximum power is, but you have the ability to be able to say. Well, OK, I'm going to Mount this on a wall. This is the area that will be facing my gateway. This is the RF performance I expect to get from that. So the measurement it does is looking at the transmitted power and said it scans it over 360 degree ratio to find the different points of it and it is captures all of those in the test report. What do then also does is say OK, well transmission is one thing, an effective radiated power is 1. But what about its sensitivity? How good is it receiving? So what it will do is it will pick the area where you had the most stable position of the device and now actually use. TLC TT or a test tool to send packets down to the device and slowly reduce the power coming out from the gateway until we get to the point where we have a 10% packet error rate on the device. So that gives you then a really good view of the sensitivity of the device as well, and those measurements are the ones that the operators in particular have requested us to do. So we have created a best practice document on how to measure this so that all devices are measured in the same way, and more importantly, you can compare one device with another. Not to the RF performance and the other thing. And Mark mentioned a little bit about this earlier. I just wanted to talk about. We've done a lot of work with the European operators who've been seeing exactly the same sort of issues that Mark was talking about. A different network service behaving slightly differently. Different parameters set up, and the device will work with one set of parameters and and not with another. So what we've worked with them is to create additional tests that have gone into and for Europe they've gone into. The 1.02 Certification requirements specification, but all those additional tests have been included in the 1.04, so they become relevant for everywhere. All the regions and that is a list. Then of all the additional tests that the operators had seen that they were needing to do to try and find and resolve the issues. Similar to what Mark was referring to. So we've enhanced incorporated those into the certification test and so now what, Dan? The operators are asking us to do and are asking of their device manufacturers is to come back and say Yep, it's been certified against over the 1.02 latest version or against 1.04. The other thing that they're saying is critical to them is this RF performance test, and again, if you have a badly performing device, it has a real impact on your network. You may need twice as many gateways if if the device doesn't provide the power output that you're expecting, or it may be running all the time at a very slow data rate. And in which case it will impact the battery life. So again, this is critical for them, and they insisted that it's all done before they'll go into mass deployments. And then the other thing, and I'll just mention this on the next slide briefly, is this information that's required by operators to set their device up. It always seems a real shame to me. You've done all the hard work to produce your device and you've got it out there and you've got it marketed, but you don't allow the operators all the information that they actually need, and I'll just on the next slide. I'll run through some of the things that we've incorporated into that to try and make sure we get it. So really, the benefit. And this was the real main benefit from. The European ones is device manufactured prior to this were going to the different operators. They had their device passed by one acceptance test and then it failed on another one so they were always having to go back and rework it. With this they can go through the certification and then it's accepted by the operators. So there's a considerable time and effort saved in there so really sort of simplifies and speeds up the selection and this is what we want to try and roll out. An intention is to roll this out now as well for North America and other parts of the world. So what I spend and just go through really is what is this additional information? What is the important things that are needed by an operator or a user of a device to try and make sure that they have all of the information in one place? So sort of fits into four main categories. The first thing is just the generic sales information and again, it's amazing how many devices are out there, but you don't really know who to contact, who to get hold of. So this is a questionnaire that's been designed by the European operators and incorporated into the lower Alliance certification program where we collect all of the information that they need in order to deploy their devices. It then goes on to the device itself and it talks about the daily UI range and the power schemes used, and again different versions of these devices, whether they pick one regional parameters or another have slightly different power scheme. So this captures what you've implemented for your device. And then the final one is all the information is about the game, the antenna 110 are you meant to use with it. So again, this is a little bit more information and then the final one really is the battery consumption estimates that measure the RRP and the sensitivity figures for it. So really with that that approach allows them to have all the information they need to set it up onto their network, and those input information as well is also stored on the showcase. So when you click into a device, not only can you see the certification certificates for it, but you can get to this information sheet which gives you all of their extra information. So really, finally, just to come back to this. This is really why you certify your device, and again, it's the confidence, reliability, reduced support, cost marketing, and the other thing that I wanted to bring out at this point is. We've heard it time and time again. Operators are prepared to spend more for a device that has proven reliability, so you can try and keep the cost down as much as possible. But if you run into issues or problems then. The operators are soon going to know that, and in most cases they are prepared to pay a premium for devices that they have confidence with that are capable of running it. That really goes to everything. I wanted to discuss about that. Couple last things then just really talking about. For more information on the Lore Alliance and membership and to become part of the ecosystem you can download the membership information that's in the resource box on the console, and you can also reach out to the email address is on there to get any questions you have answered about it. And the final one is. This is part of their long series that we're doing about Laurel and destinations. They'll be having new content every week throughout the next few months, so please check the destination Lorawan website and engagement Hub to try and see. And the final thing is we will record this session today and within 24 hours we will put it onto a demand for replying back and you can follow the same link that you saw today to get access to it. So at this point I will hand over and will will start. This sort of submitted questions and answers boxes and we had some great questions in and what I want you to do really is just hold on a few minutes just a minute or so while we collate all those questions and then starting thoroughly the question and answer section. So hi, thank you all. For those of you ring. So we're now moving into the question and answer section again. Thank you for all the questions that been submitted. If you have anymore, please do submit them by the Q&A box. So what I'll do now, we start running through those questions that we've received. I'll try and cover most of them in the order that we have. If I can see a couple that look like their combined, I'll try and talk to them as well and also get Mark to answer them where appropriate. So, so on the first questions when really about this T device, the IQ Lorawan asking about certification, as far as I'm aware, that's part of the STM 32 WLES series which has had substantial certification testing done on it, so I'm not sure specifically the IQ, but certainly STR heavily involved in the certification program and I would expect that to be dealt with. So next question is, what's the typical test cost time charged by the 80 H is? Does it greatly vary by region? So one of the things that we tried to do is keep the time that it takes to actually certified device down to the minimum Ann, and although we don't as an alliance don't have direct control of the cost. What we do have is the ability to control the time of it. So we have made it to the point where all the devices will be certified within a certain period of time and that's very slightly by region by region. But again, if you go into the Lore Alliance website and look at the 88 Test Houses Betina certification one. We give you an example of what the typical times would be for you to get your device certified, and there may be some regional variation, mainly because obviously hourly rates change from one region to another, so we try and identify things by the time, but then not specifically go into the price because we are controlling the time of the device. So. Next question was. On what is the addition? Why not add additional multi Day testing to the LCT and thank you for Carla. This came in when the first section was on and hopefully we've been in and talked about that now that says you'll see TT now because it's available to all our members. It gives you that ability to actually run those tests now as a stand alone device before it. So what we are implementing is that back off test where. Before you send your device to certification, you will run that 36 hour back off test at your own facility and then when she actually had that test results, you will forward that along with your device to the Authorized Test House. When it goes through certification and what we're expecting is that now that everyone has the access to the LCT overtime, there could be other things that we can look at doing and saying OK, what other testing should we be asking people to do and to pick up some remarks points that could be? Other things in there as well that we actually need to try and make sure we can capture into that, but I think the LCT is the platform that allows us to do that. So thank you for that question. The next little bit more detail just about RF testing. When using one of the Semtex chips combined with one another's, is it possible to get the device to do continuously enabled, receive and transmit the different channels? Clearly some of that would need to be a dedicated firmware on the device, but once you have the device talking at the Laura, one side of it, and by using the LC TT there is a test mode or manual mode in the LC TT which will allow you to. Send commands down to your device to enable or disable particular channels, so it may not be able to be done directly during the development testing, but certainly once your device is there an operating against the law when side of it, the LC TT has the ability to really go in and control and set up in the end device. So just moving on another question then. Thank you for this one. This what sort of loss rate should we expect? So typically the Lorawan works over and I ** bands which has lots of other devices in it. I think typically we would expect that you should be able to cope and you should be able to design your network to a sort of up to a 90% packet success rate or a 10% error rate loss when we actually do the certification part. We tested the devices ability in a quiet environment so we guarantee and we ensure as part of certification, but. There is no more than a 5% packet loss on the end of ice, so typically you should be expecting worst case to see something in the region of five or 10%. But again, the protocols are built into the lore around to allow you to automatically re transmit messages and things and use the confirmed and unconfirmed message saying that. A good way of counteracting anything and the other thing, obviously, is if you send one message in. My only have a 90% if you send the same message twice, you get a 99% chance of success rate, so that repetition again is built into the spec, and if you need to in certain circumstances, you can enable that function automatically. I'm to have another question which is how long does it take to run a full test suite using the best practice testing and mark if you want to have a go at that one please. Oh yes, So what we use is kind of a fleet of low cost. Testbench is based on the Simtek. CTB project and So what we typically have done is ask the vendor to provide three samples of their sensor. And then running in parallel on multiple CTS, some of which are RF chambers. Others are have the power measurement hooked up. We can complete our our complete suite of tests in about 2 weeks of elapsed time by kind of compressing it down. So even though we're doing many multi day tests taking advantage of running some things in parallel, we can. We can get a device tested in and reported in 10. And working days. OK, thank you for that. So carry on with a few more of the questions so. Are there any Bible off the shelf local Lorawan gateways that can be easily connected to the LCTT so the one that we are currently recommending is the Semtech pico cell? Is a little USB connection that fits into your PC and it really is the best low cost device that's available for the regions around the world and and again if you look at the Handbook for the LCT, there's instructions on there and it points you to various places where you can obtain it from and it's available by most of the stock is still. We also provide the setup for it so that you can have an easy connection to the LCTT. The reality is the LCT should work with any gateway, but obviously each gateway has its own slight differentiating, so we have tested and proved it with the pico cell gateway, but it is possible if you're a little bit on your own, but it is possible to get it set up with almost any other gateway, and I think we've had various people now around the world using it with different gateways, but the one we're recommending and the one we provide all setup information for is for Matt Pico cell. So thank you. Another good question says what about test? Run with duty cycle on and off. So part of the certification program obviously and obviously duty cycle is for the dynamic channel plans. Whilst we're actually doing the testing and specially when we do the packet error rate testing and things like that we do go in and turn the duty cycle off basically to allow us to get the test time so it's always a compromise between getting the test time down to. Three or so hours. If you can imagine when we're testing the data rates, for instance, we're sending 60 messages for each of the different data rates on each of their receive channels, so there's a lot of messages that get sent backwards and forwards, and if we were limited by the duty cycle, that would take that test time from 3 hours to probably near a 10 to 15 hours. So we tend to run some of the tests with duty cycle disabled, but in general, and especially at 1.04, we've tried to use the device now. As much as possible in its normal operating mode, and only when there's a specific test that might be an issue from a timing point of view, would we actually go in and through certification application, turn off the duty cycle. The next question is, is it possible to obtain certification for only the antenna in Lorawan and so as a stand alone it's not possible to certify it or test it, but obviously once it's connected to a device and it could be any type of device that accepts an external antenna and what is available then is the RF measurement the end device measurement facility and that defines that set of measurements and it provides that 360 degree scan so? Although you can't test the antenna on it in isolation by attaching it to an end device and then you can actually use the end device and run through the testing mode with that so that you can actually see what the performance is. Obviously, at that point you could switch out different antennas as well, so you could be clear what's the impact of the antenna as opposed to just the end device itself. But as you know, the radiated pattern is more specifically there to test the antenna. So a lot of the end device RF testing is specifically aimed at testing the antenna on the device, whether it be. Drippy and internal one. So next we're following question about antenna patterns. Even if it's internal to know what orientation the devices when it's placed. So yeah, this is one of the things that we added, again specifically when we're working with the operators, because the antenna does have a significant impact on the range of the device, and once you once you impact the Ranger, then impacting the data rate that the device is able to do so it's not much good having a device if it works. Absolutely perfectly on your bench and actually you're going to war Mount it because then its transmission mode will be in a completely different orientation and that was really the aim of doing the RF performance testing to make sure that we cover and we capture all of the its abilities in all directions so that one of the things, particularly operators look at is when they look at the 3D scan, they actually check how it's going to be mounted. Where it's going to be mounted so that they can actually make sure that the output power that is giving is based on the orientation they're actually going to install it in. The next question is, where can I get an LC TT on the market so I'm not sure if you're a lower alliance member, but if you are, it's free and available to all lower alliance members. It is a benefit that we have said for the lower alliance and what we can do is if you remember then please come back to us and I can tell you exactly the links where to get it from. But affectively you would just download the software package from. The Lore Alliance install it onto a local PC which could then run as the LCT and then effectively go through a process where you. Extract the license file which you send to the Lore Alliance so that we can then send you back and basically enable that license on that PC. Unable to run that LCT so it's not available outside of the alliance, it is only available to law Alliance members. I know we see there's two ways of getting that. Then if you are a Member, fine, you're welcome to it, and it's part of the benefit. If not, there is the process called the certification affiliate, which will allow you to go in and and become a certification affiliate which is not signing up to the full terms and conditions of the lower alliance, but will separately give you their access to the LCT. If you're interested in that, please follow up with again with us and. The addresses are on the slide set as well. So next question, this is a good one. Thank you. So what are the best practices for testing lower devices in field conditions? I think there's a little bit in that. Of it. There's a lot of work that's sort of been done, and that's a lot of reasons why the RF testing is so important for it. Obviously, the conditions that we know different buildings have different absorption rates and things like that. So what we would actually suggest is that you actually do just a trial of where you want to it, put the device, and it's a combination really of where is the device going to be located? Is it indoors? Is it outdoors? How far away is it that you're expecting the? Device to be from the from the gateway, and this is one of the things that again of the RF testing that we've put into place is. We quote what the having measured it. We actually say then what is the expected? Or what is the likely output power that you're going to get from this device and that has the biggest impact into then. What is the range that it will be able to reach and how far will it be able to go so? And the best one really is. Look at the situation and it's fine. Where the gateways are workout what devices where they need to be inside a building or not? And so next one is using a lower end set radio module automatically certifies the whole device so. And what we've implemented IS certification by similarity program, and I didn't really talk about it on the slides, but we have. If you already use a certified module and the main thing is that that includes the Laurel and protocol stack, then you can implement that onto your own device. And with that you can then apply for certification by similarity, which means you don't need to send your device in, you fill out a self declaration form from it, you submit the information and it goes just through. The authorized test ask for them to check it, but if they are then happy with it, they pass it on to us and then we can issue you a certificate or to say it's past the certification test based on that certification by similarity. But the key thing is if you meet the criteria for that and using a certified device is one of them, it will go through and won't need to be separately tested. I'm trying to think if there's any others to pick out. There's quite a few questions in here. Carry on for a couple more minutes, but I think I know. We then need to pull a halt at some time. So one question, I think covered something similar to the House. Do you intend to include a standard generic gateway, yuniel CTT? And that's partly what we've tried to say would be the picocell gateway from that. So the next question is we have an LCT dongle that ones on 868. Do we need to buy additional dongles for other frequencies as well? Particularly looking at a S923, so AS923 works in the 920 mark. The reality is the dongle and specially I know that the. Pico cell from that will actually work at those other frequencies is a matter of reconfiguring it, and because we're only doing LC T testing, you're going to be quite close to the device, so there is a good chance that the same gateway will work. But obviously you need to be aware that depending on where you are, you have to transmit legally within your band, so if you're trying to use it, a band that's not part of your country or your region, then you need to put it into some sort of Faraday cage. So I'm conscious we're coming up to time and I think we're probably a minute or so over now, so I'll call a halt on these. Thank you all for those who have submitted the questions. Those that I haven't been able to answer to, we will go through and separately respond to and make sure everyone gets an answer for that. So with that thank you all for attending and thank you all for the brilliant questions that have come in and we will come back to you with the answers specifically for those that haven't been able to do. So thank you all very much and hope to see you again soon. _1619172983271

The LoRaWAN® certification program provides assurance to end customers that their application-specific end devices will operate on any LoRaWAN network, making it crucial for the successful deployment of IoT applications.

The LoRaWAN certification program has been thoughtfully setup and designed to include the right tools to achieve these goals, while also saving your company time and money throughout the certification process.

In this webcast, expert panelists will give an overview of the key benefits of LoRaWAN certification, expert tips to consider when testing LoRaWAN devices, and how to ensure device performance beyond certification and through deployment. Panelists will cover key topics such as:

Additionally, LoRa Alliance member company eleven-x will introduce its LoRaWAN Centre of Excellence (CoE), a testing facility designed to deliver cost-effective and timely results for device makers and system integrators. The CoE has already executed testing on a number of devices covering key device factors such as battery life and RF performance, as well as interoperability with different network servers.

Drawing on a variety of real-life examples, this presentation is sure to provide device manufacturers and system integrators the insight and direction to successfully move through the certification process and network qualification in order to ensure rapid and successful deployments, from pilot to large-scale.