Document

LoRaWAN® Specification v1.0.1

Issue link: https://read.uberflip.com/i/1428386

Contents of this Issue

Navigation

Page 58 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 59 of 91 The authors reserve the right to change specifications without notice. 8 Retransmissions back-off 1 2 Uplink frames that: 3 Require an acknowledgement or an anwser by the network or an application 4 server, and are retransmitted by the device if the acknowledgement or answer is not 5 received. 6 and 7 can be triggered by an external event causing synchronization across a large 8 (>100) number of devices (power outage, radio jamming, network outage, 9 earthquake…) 10 can trigger a catastrophic, self-persisting, radio network overload situation. 11 12 Note: An example of such uplink frame is typically the JoinRequest if 13 the implementation of a group of end-devices decides to reset the 14 MAC layer in the case of a network outage. 15 The whole group of end-device will start broadcasting JoinRequest 16 uplinks and will only stops when receiving a JoinResponse from the 17 network. 18 19 20 For those frame retransmissions, the interval between the end of the RX2 slot and the next 21 uplink retransmission shall be random and follow a different sequence for every device (For 22 example using a pseudo-random generator seeded with the device's address) .The 23 transmission duty-cycle of such message shall respect the local regulation and the following 24 limits, whichever is more constraining: 25 26 Aggregated during the first hour following power-up or reset T0=0 Transmit time < 8.7Sec per 24h 27

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1