For the second year I had the chance to introduce the IoT and LPWAN networks to a group of 150 students in computer engineering school. This year we add a longer time to detail a bit the Sigfox and LoRaWan solution and I’ve added a part on the IoT security.
I’ve tried to propose a different point of view on security aspect, not based on fear but practical things to do and a larger contextual aspect. I’ll try to make video on this specific topic on my Youtube (where you can find in french most of the content of these slides).
So … here are the slides, for my students who joined or not the conferences, and for those who would like to join this course.
This model is standard for LoRaWan ecosystem running on private network as on public network. For Sigfox it has always been possible to expend the network but it was a little bit complex because you had to rent the basestation from Sigfox and the basestation itself was an operator equipment: something made for being installed on a roof, not in your office.
New episode of my LPWAn post series, this time, about the network architecture and the role of the network kernel.
The network architecture is different than a classical IP communication from client to server: the LPWAn architecture is based on a kernel network allowing the protocol transformation from the Sigfox / LoRaWan world to the IP-Internet world.
In the LPWAn protocol the addressing is limited to one device address only to reduce the frame size and as a consequence all the frame have to be captured by a central system: the network kernel. It will route the message correctly to the end user application based on device association made on registration.
This post is related to a french video (as usual) and detailed in the following part of this post.
The Things Network (TTN) is a global LoRaWan public network kernel based on crowd-source infrastructure. This initiative sounds really interesting in my point of view because it breaks one of the main LoRaWan issues : the country based operators organization.
Related to this good point, the negative point is the current area covered by a such network limited to the contributor localization, generally in the main cities.
That said, I’m convinced : when you want to create a private LoRaWan network you have to manage a network kernel managing gateways, device authorizations… You can do it yourself, you can pay someone to do it for you or, eventually, you can lever TTN for this use. As a counterpart you will extend the network and offer this benefit to any around. That way it makes sense and gives large opportunities to the networks and it’s private users.
Long introduction for a technical topic … How to join this network once you have a Kerlink LoRa Iot station available ? Continue reading →
Episode 3 & 4 of my Youtube series about LPWAN is about antennas for LPWAN and impact on object design. The episode 4 go deeper on the way to improve radio performance by tuning and adapting antennas with matching circuit.
As usual, this series of post are summarizing in English the content of my French video on youtube.