Hi Xavier,
To complement the information from Eros, the Modem firmware upgrade process (FOTA) generally works in the IoT cellular ecosystem:
1. The modem manufacturer (e.g., Sequans) creates and signs the firmware update
Sequans is responsible for developing, testing, and cryptographically signing the modem firmware. We make the firmware available, but do not automatically push it to devices in the field.
2. The device maker or IoT platform decides when and whether to update
Typically, it’s the responsibility of the device manufacturer (the company integrating the Sequans module) or their chosen device‑management platform to initiate the firmware update.
They decide:
if the new firmware contains needed updates for the deployed devices
which devices should receive it
when the update should be triggered
the conditions (battery level, network availability, business logic)
3. How the update is delivered depends on the chosen FOTA mechanism
Sequans modules support:
FOTA managed by an IoT platform or the device maker
Operator-driven FOTA in some cases, but only if the operator and module vendor have set up a managed update program together
Application-controlled FOTA, where the host MCU downloads the package and instructs the modem to update
In practice:
Sequans provides the firmware.
The operator may host or distribute it, but only in specific operator-managed programs.
The device maker or IoT solution provider is almost always the one who initiates and controls the update to their deployed devices.
So unlike laptops or smartphones, where updates are pushed regularly and automatically, IoT modem FOTA is usually controlled by the device manufacturer or the cloud/device‑management platform, not by Sequans directly.
One last point: FOTA in IoT has an impact both on the device and on operating costs, since each update session consumes power (which matters for battery‑powered devices) and uses data from the cellular plan.
I hope this clarifies the picture for you.