FAQ

5177 Brandi n Court, Frem ont, CA94538 | Tel : +1 51 0 -4 9 2 -4044 | Fax : +1 510 -4 9 2 -4001 | www.l o ra -al l i anc e.org FUOTA FAQ No. All FUOTA WG specifications are independent and can be used for other purposes. For example, the Application Layer Clock Synchronization protocol can be used to set the correct clock time into end- devices, independent of a firmware upgrade. You can also use a combination of specifications, like Remote Multicast Setup and Fragmented Data Block Transport, to send any large file to a fleet of end-devices. 5. Is there an open-source implementation of FUOTA specifications? Yes, the LoRaMac-node project, for example, proposes an implementation of the FUOTA building block specifications on the end-device side. 6. What is the maximum size of a firmware update? There is no strict limitation on the firmware size that the FUOTA protocols can transport. The Fragmented Data Block Transport protocol has been designed for data blocks of a few hundred kilobytes. Missing fragment reconstruction becomes more complex when the data block size increases. The actual limit will mostly depend on the capabilities of the end-device, in terms of memory for storage and reconstruction, and on the network capacity to broadcast large amounts of data over the air. There are techniques to lighten broadcasted data size. Refer to question 29, How can I improe the efficiency of FUOTA? for more information. 7. I heard LoRaWAN payload sizes are limited. How can I send a large file to my end-device? Yes, LoRaWAN payload sizes are limited, depending on the region of the world and on the selected data rate. However, the FUOTA WG specification Fragmented Data Block Transport describes a fragmentation protocol to split a larger data block into fragments. 8. How do FUOTA protocols handle packet loss? When broadcasting a firmware update to many end-devices, it is not efficient nor recommended to ask each end-device if it has received all of the fragments. The FUOTA WG specification

• Cover