The primary purpose of Firmware-Over-The-Air (FOTA) Applications is to update firmware in IoT and Automotive devices, that are installed in remote locations or on a field.
This demo video starts by introducing you to the architecture of the system that facilitates FOTA update.
There are four primary components in the FOTA Architecture:
- Client app server – Firmware files and device properties are uploaded through the user interface of the client app server.
- FOTA server – The work order is created and moved to the FOTA server.
- BLOB Storage – This is a highly scalable file storage service that facilitates thousands of concurrent download requests from different devices.
- Devices – These should be connected to the internet and have the ability to make API calls. Each device checks for updates from the FOTA server during the first reboot of the day.
Subsequently, the workflow of the system is explained. The steps involved in the FOTA update process are as follows:
- When new firmware image is available, the admin user uploads the firmware to BLOB storage through client app server.
- BLOB storage creates a url for the file, and this is stored in the FOTA server.
- During boot-up, the field deployed devices check for new firmware availability by making API calls to the FOTA server.
- If new firmware is available, the FOTA server responds with the url.
- The device then starts downloading the firmware from BLOB storage.
- Once the firmware starts updating the devices, the status is reported to the FOTA server.
- When the update is completed by all devices, the status can be viewed in the client app server in the form of bar charts.
This is followed by an insightful demo of how the application works in real-time.
How is scalability the USP of our FOTA Solution? What are the business use-cases of our FOTA Solution?
You will find all the answers in this demo!
