When we started Beringar we spent a lot of time with clients in the health sector understanding their space utilisation needs. We discovered that to use IoT in the National Health Service in the UK we would have to find a way to get the data out without touching the buildings data infrastructure. So, no wired or Wi-fi connections were possible, partly due to data security concerns and partly due to spotty Wi-Fi that sometimes was there and worked and sometimes did not. A constraint was introduced to our way of working that we had to overcome.
As we have discovered, constraints are our friend. They force us to think of inventive ways to overcome them and usually lead to a better product in the end. This constraint led us to focus on LPWAN technologies as a potential data transmission solution (in turn leading to new constraints around data packet size) and to prototyping using LoRaWAN.
Why LoRaWAN? Well, it was a technology that we could find willing experts to help us with and had the benefit of flexibility compared to SigFox. We wanted to send data every minute and SigFox would not allow us to do that. LPWAN technology also had the benefit of great range and the ability to work from deep in the bowels of a building. Something that we knew that 3G or 4G would not be able to cope with from our initial tests. This choice meant we could get the data out of the building securely and reliably.
Making the choice to work with LoRaWAN meant that we needed to really focus on the data that was important and package it in a way that could let us fulfil the demand to count and position people in a building, report the environment and understand space utilisation. All in a few bytes transmitted once per minute. As I mentioned, constraints force creativity, so we found a way to package this information in a few different message types and stayed within the duty cycle limits for LoRaWAN. This choice reduced our data transmission, storage and management headache a lot.
The other benefit of LoRaWAN, as we have discovered, is the ability for us to be in control of the deployment. We choose how many gateways and when they will be installed. We manage the network and ensure that we deliver a high quality service. This is important in the overall end to end service we deliver to the customer. No waiting for a telco to roll out in that area and no service provider help desk to worry about if something is not right. This choice helped with speed to market and quality of service.
So LoRaWAN has challenges - its radio being the principle one. Doing large scale firmware updates is not trivial and we always have the issue of occasional dropped packets - but the pros outweigh the cons. It’s fast to deploy; you’re in control; it’s quite reliable; it has great range with low cost hardware and you can remain independent of the large carriers. There is a lot to like.
What do you use to get data out for your IoT deployment and what are the pros and cons?
Main image credit: Ryan Stefan via Unsplash