Expert insight : Top 3 Questions People Ask Our Deputy CTO, Julien Catalano
1 – Are Firmware Updates Over the Air (FUOTA) Limited on a LoRaWAN Network?
In theory, LoRaWAN networks can support the distribution of large firmware updates through FUOTA (Firmware Update Over the Air). The firmware is divided into small fragments that are progressively transmitted to multiple connected devices simultaneously using multicast communication, before being reassembled and installed on each device.
In practice, however, it is advisable to keep update sizes as small as possible. LoRaWAN was designed to transmit small amounts of data while consuming very little energy. The larger the firmware file, the longer the update process takes, increasing the load on both network resources and device batteries.
There are also regional regulatory constraints to consider. In Europe, for example, IoT networks operate under strict regulations. Devices cannot transmit continuously because of duty-cycle limitations, and transmission frequencies are shared between end devices and gateways in a half-duplex environment. These restrictions must be taken into account when planning large-scale firmware updates.
Another important aspect is the lost-fragment recovery mechanism defined in the LoRa Alliance FUOTA specifications. This feature prevents the need to retransmit an entire firmware image when data is lost during transmission. However, it requires memory resources proportional to the firmware size.
As a result, the LoRaWAN firmware update protocol was designed for constrained devices, meaning equipment with limited resources and firmware sizes typically measured in a few hundred kilobytes. These update profiles are generally the most suitable for LoRaWAN IoT deployments.
Ultimately, the challenge is not the maximum firmware size itself, but the ability to deploy updates without affecting network performance or device autonomy. With proper planning, FUOTA remains an essential tool for maintaining and evolving connected devices. It is also a critical enabler for compliance with emerging cybersecurity regulations such as the Cyber Resilience Act (CRA).
Learn more about the latest FUOTA technical recommendations from the LoRa Alliance:
2 – What Are the Next Technical Developments Planned by the LoRa Alliance Technical Committee?
Several major developments are currently underway within the LoRa Alliance.
The first major advancement concerns satellite-enabled LoRaWAN.
The objective is to adapt the protocol for satellite communications and extend connectivity on a global scale. This evolution will make it possible to connect devices in areas where terrestrial infrastructure is unavailable or difficult to deploy, such as remote regions and maritime environments.
Another key topic is Mobile Readout for smart metering applications.
This approach enables the collection of metering data without relying on a fixed LoRaWAN network. For example, a gateway installed in a service vehicle can retrieve data from water or gas meters while driving through city streets. This model opens new opportunities for low-density deployments or areas where permanent coverage is not required.
A significant update to the LoRaWAN specification is also being prepared.
This new version aims to strengthen security, simplify certain protocol mechanisms, and improve interoperability between devices. The goal is to make deployments even smoother, delivering a more user-friendly and streamlined plug-and-play experience for customers and system integrators.
These developments are highly anticipated across the ecosystem because they will make LoRaWAN networks easier to deploy, more secure, and capable of supporting an even wider range of applications.
The LoRa Alliance welcomes new members throughout the year. It is a unique forum for collaboration and innovation, bringing together industry-leading experts who are shaping the future of LoRaWAN. If this journey interests you, I would be delighted to discuss it with you via LinkedIn.
3 – Why Isn’t the Track Value Solution Designed to Provide My Railcar’s Position Every Five Minutes?
First, it is important to understand that Track Value was not designed as a real-time tracking solution. Instead, it is a monitoring and event-management platform.
Its primary objective is to deliver high-value operational information, such as anomalies, incidents, unexpected stops, or significant asset status changes.
This approach is built on three key principles:
-
A Business Value-Driven Approach
In rail freight operations, receiving a railcar’s position every five minutes rarely provides additional actionable insights. The objective is not to collect as much data as possible, but to obtain relevant information at the right moment.
Frequent transmissions generate larger volumes of data that must be stored, processed, and analyzed, without necessarily creating operational value. With Track Value, communications are triggered by meaningful events, enabling operators to focus their attention on situations that genuinely require action.
-
A Design Optimized for Long Battery Life
Devices installed on railcars must operate autonomously for several years without maintenance intervention. This is why the Track Value architecture was specifically designed to minimize energy consumption.
Depending on operating conditions, the Mobile Hub can achieve a battery life of up to six years. Such autonomy would be significantly reduced if the device were required to transmit its position every five minutes. This is therefore a deliberate technological choice aimed at ensuring controlled operating costs and maximum equipment availability in the field.
-
Satellite Connectivity Designed for Global Asset Tracking
Track Value relies on the Kinéis satellite network, which is based on a constellation of Low Earth Orbit (LEO) satellites. Unlike terrestrial networks or continuous communication solutions, this type of infrastructure operates using intermittent connectivity. Satellites regularly pass over monitored assets, enabling data exchanges at each pass.
This characteristic provides a major advantage. On one hand, it enables truly global coverage, including remote locations where terrestrial networks are unavailable. On the other hand, it offers an extremely efficient infrastructure for asset monitoring applications, where event reporting and alert generation are often far more valuable than continuous real-time tracking.