Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 18 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 19 of 91 The authors reserve the right to change specifications without notice. Note: If the network server has reached its maximum number of 1 retransmissions without receiving an acknowledgment, it will generally 2 consider the end-device as unreachable until it receives further 3 messages from the end-device. It is up to the network server to 4 retransmit the message once connectivity to the end-device in question 5 is regained or to forfeit that message and move on. 6 7 Note: The recommended data rate back-off strategy during re- 8 transmissions is described in Chapter 19.4 9 4.3.1.4 Frame pending bit (FPending in FCtrl, downlink only) 10 The frame pending bit (FPending) is only used in downlink communication, indicating that 11 the gateway has more data pending to be sent and therefore asking the end-device to open 12 another receive window as soon as possible by sending another uplink message. 13 The exact use of FPending bit is described in Chapter 19.3. 14 4.3.1.5 Frame counter (FCnt) 15 Each end-device has two frame counters to keep track of the number of data frames sent 16 uplink to the network server (FCntUp), incremented by the end-device and received by the 17 end-device downlink from the network server (FCntDown), which is incremented by the 18 network server. The network server tracks the uplink frame counter and generates the 19 downlink counter for each end-device. After a JoinReq – JoinAccept message exchange or 20 a reset for a personalized end-device, the frame counters on the end-device and the frame 21 counters on the network server for that end-device are reset to 0. Subsequently FCntUp and 22 FCntDown are incremented at the sender side by 1 for each new data frame sent in the 23 respective direction. At the receiver side, the corresponding counter is kept in sync with the 24 value received provided the value received has incremented compared to the current 25 counter value and is less than the value specified by MAX_FCNT_GAP 1 after considering 26 counter rollovers. If this difference is greater than the value of MAX_FCNT_GAP then too 27 many data frames have been lost then subsequent will be discarded. The FCnt is not 28 incremented in case of multiple transmissions of an unconfirmed frame (see NbTrans 29 parameter), or in the case of a confirmed frame that is not acknowledged. 30 The LoRaWAN allows the use of either 16-bits or 32-bits frame counters. The network side 31 needs to be informed out-of-band about the width of the frame counter implemented in a 32 given end-device. If a 16-bits frame counter is used, the FCnt field can be used directly as 33 the counter value, possibly extended by leading zero octets if required. If a 32-bits frame 34 counter is used, the FCnt field corresponds to the least-significant 16 bits of the 32-bits 35 frame counter (i.e., FCntUp for data frames sent uplink and FCntDown for data frames sent 36 downlink). 37 The end-device shall not reuse the same FCntUp value, except for retransmission, with the 38 same application and network session keys. 39 Note: Since the FCnt field carries only the least-significant 16 bits of 40 the 32-bits frame counter, the server must infer the 16 most-significant 41 bits of the frame counter from the observation of the traffic. 42 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.1