Document

LoRaWAN® Specification v1.0

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

Contents of this Issue

Navigation

Page 18 of 81

LoRaWAN Specification ©2015 LoRa™ Alliance Page 19 of 82 The authors reserve the right to change specifications without notice. messages from the end-device. It is up to the network server to 1 retransmit the message once connectivity to the end-device in question 2 is regained or to forfeit that message and move on. 3 4 Note: The recommended data rate back-off strategy during re- 5 transmissions is described in Chapter 18.4 6 4.3.1.4 Frame pending bit (FPending in FCtrl, downlink only) 7 The frame pending bit (FPending) is only used in downlink communication, indicating that 8 the gateway has more data pending to be sent and therefore asking the end-device to open 9 another receive window as soon as possible by sending another uplink message. 10 The exact use of FPending bit is described in Chapter 18.3. 11 4.3.1.5 Frame counter (FCnt) 12 Each end-device has two frame counters to keep track of the number of data frames sent 13 uplink to the network server (FCntUp), incremented by the end-device and received by the 14 end-device downlink from the network server (FCntDown), which is incremented by the 15 network server. The network server tracks the uplink frame counter and generates the 16 downlink counter for each end-device. After a join accept, the frame counters on the end- 17 device and the frame counters on the network server for that end-device are reset to 0. 18 Subsequently FCntUp and FCntDown are incremented at the sender side by 1 for each data 19 frame sent in the respective direction. At the receiver side, the corresponding counter is 20 kept in sync with the value received provided the value received has incremented compared 21 to the current counter value and is less than the value specified by MAX_FCNT_GAP 1 after 22 considering counter rollovers. If this difference is greater than the value of MAX_FCNY_GAP 23 then too many data frames have been lost then subsequent will be discarded. 24 The LoRaWAN allows the use of either 16-bits or 32-bits frame counters. The network side 25 needs to be informed out-of-band about the width of the frame counter implemented in a 26 given end-device. If a 16-bits frame counter is used, the FCnt field can be used directly as 27 the counter value, possibly extended by leading zero octets if required. If a 32-bits frame 28 counter is used, the FCnt field corresponds to the least-significant 16 bits of the 32-bits 29 frame counter (i.e., FCntUp for data frames sent uplink and FCntDown for data frames sent 30 downlink). 31 The end-device shall not reuse the same FCntUp value, except for retransmission, with the 32 same application and network session keys. 33 Note: Since the FCnt field carries only the least-significant 16 bits of 34 the 32-bits frame counter, the server must infer the 16 most-significant 35 bits of the frame counter from the observation of the traffic. 36 4.3.1.6 Frame options (FOptsLen in FCtrl, FOpts) 37 The frame-options length field (FOptsLen) in FCtrl byte denotes the actual length of the 38 frame options field (FOpts) included in the frame. 39 1 Actual value for MAX_FCNT_GAP, RECEIVE_DELAY1 and RECEIVE_DELAY2 can be found at 7.1.7 for EU863-870 or 7.2.7 for US902-928.

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0