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 This case shows that the duration of a FUOTA session, for the first three scenarios, is a handful of minutes, and that battery usage is kept low (< 0.1%). The scenario on the last line highlights that Class C Multicast in a duty cycle-restricted region, where only 10% of the time can be used to broadcast, may be inefficient for large file transfer; end-devices would have to listen for an entire hour while only receiving actual data for a few minutes. This is a waste of energy and radio bandwidth. For such cases, Class B might be more suitable. Class B, single ping slot per beacon period The second use case is LoRaWAN Multicast Class B with a single fragment per beacon period. FIRMWARE NAME REGION SETTINGS TIME ELAPSED ACTIVE TIME POWER 90K US915-DR10 17h 10m 7m 00s 0.583mAh (<0.1%) 120K US915-DR10 22h 53m 9m 20s 0.777mAh (~0.1%) 90K EU868-DR4 17h 10m 6m 50s 0.570mAh (<0.1%) 120K EU868-DR4 22h 53m 9m 07s 0.760mAh (~0.1%) In this use case, the duration (time elapsed) of a FUOTA session is much longer. It takes almost a day to broadcast the firmware. But the active time that end-devices are in reception mode stays low, as they are only listening for one ping slot per beacon period, which is one fragment every 128s. In addition, end-devices also listen to the beacon itself, which explains the longer active time as compared to Class C. The power budget is similar to Class C, except for the scenario on the last line, where it stays much lower, due to the avoidance of activating listening mode for no reason. Class B, Maximum ping slots per beacon period The third use case is LoRaWAN Multicast Class B with a maximum number of fragments per beacon period. The number of fragments depends on the duty cycle restrictions. FIRMWARE NAME REGION SETTINGS # BEACON PERIOD TIME ELAPSED ACTIVE TIME POWER 90K US915-DR10 4 8m 32s 4m 50s 0.403mAh (<0.1%) 120K US915-DR10 6 12m 48s 7m 15s 0.604mAh (~0.1%) 90K EU868-DR4 31 1h 06m 5m 50s 0.487mAh (<0.1%) 120K EU868-DR4 41 1h 27m 7m 43s 0.644mAh (~0.1%) In EU868-DR4 region settings, due to duty cycle restrictions, only 16 ping slots per beacon period are allowed to be used for the given fragments. This lengthens the time elapsed but only slightly affects the total active time, and therefore the power consumption necessary to receive the file. The power budget stays around 0.1% of the chosen battery capacity.

• Cover