Feature: IOT
store-and-forward operations, critical when operating through a network of LEO (Low-Earth Orbit) satellites. From a satellite perspective, there is also the huge complexity created by having to manage the many different frequencies used on the ground by NB-IoT devices. Tis problem is rarely mentioned but is probably the biggest challenge to overcome, as the satellites will be much more complex and costly. Similarly, some system integrators
are turning to the LoRaWAN standard over satellite, for licensed or unlicensed spectrum. Even here there are obstacles to features like bi-directional communications or store-and-forward capabilities. Additionally, both 5G NB-IoT and LoRa over satellite have much more data overhead than an optimised proprietary protocol like Astrocast, resulting in much more energy consumed per byte sent. While these standards would theoretically simplify the deployment model, using non-optimised data protocols for the SatIoT component can be detrimental to IoT device performance – in effect destroying the IoT business case.
Optimised deployment Proprietary data protocols have been a core component of the SatIoT development model for good reason –
optimised deployments are cheaper, more reliable, better performing and of low power consumption, which can make or break an IoT deployment. Excessive power consumption significantly reduces battery life, leading to expensive battery/ device replacement, which is impossible for goods in transit and extremely challenging in remote locations. A device using a generic network standard for SatIoT will use up to ten times more power than a device using SatIoT with optimised data protocol and chipsets. Furthermore, it is not possible to simply add a SatIoT connection to an existing device, even using the same network standard such as LoRaWAN. Tis is not plug and play; devices will need a new antenna or RF front-end to connect to the satellite. Which, again, leads to better use of optimised data protocols and devices optimised for SatIoT. Tey must be small to fit all applications, with small, possibly flat antennas, robust enough to withstand years outside without needing replacement. Two-way communication is also important, providing remote device upgrades to further extend their life in the field.
An enabler The use of proprietary data protocols is not a barrier to deployment but an enabler. Systems integrators can create
solutions that use multiple networks to track items across the world. One recent deployment for shipping containers tracks them seamlessly between multiple different connectivity solutions, including Bluetooth, cellular, LoRaWAN and satellite, as required. Organisations can change the primary network at any time, ensuring the device connects to SatIoT rather than cellular service in high-cost areas. What’s important is to ensure the
deployment model supports rather than undermines the IoT business case: How often does the device need to communicate with the satellite? What is its power consumption? How long is its battery life? Is its antenna fit for purpose? Does it support bi-directional communication? These are key considerations that will affect the cost, viability and business benefits of SatIoT use – and optimal performance can only be achieved through dedicated, optimised data protocols. For now, full integration is the long-
term dream and, at some point over the next decade, standards will emerge. To maximise the power, potential and cost benefits of SatIoT today, using dedicated proprietary protocols will remain the best way to develop a robust, achievable business case and accelerate the deployment of IoT.
www.electronicsworld.co.uk March 2023 29
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44
