Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 17 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 18 of 91 The authors reserve the right to change specifications without notice. resets the ADR_ACK_CNT counter. The downlink ACK bit does not need to be set as any 1 response during the receive slot of the end-device indicates that the gateway has still 2 received the uplinks from this device. If no reply is received within the next 3 ADR_ACK_DELAY uplinks (i.e., after a total of ADR_ACK_LIMIT + ADR_ACK_DELAY), the 4 end-device may try to regain connectivity by switching to the next lower data rate that 5 provides a longer radio range. The end-device will further lower its data rate step by step 6 every time ADR_ACK_DELAY is reached. The ADRACKReq shall not be set if the device 7 uses its lowest available data rate because in that case no action can be taken to improve 8 the link range. 9 Note: Not requesting an immediate response to an ADR 10 acknowledgement request provides flexibility to the network to 11 optimally schedule its downlinks. 12 13 Note: In uplink transmissions the ADRACKReq bit is set if 14 ADR_ACK_CNT >= ADR_ACK_LIMIT and the current data-rate is 15 greater than the device defined minimum data rate, it is cleared in 16 other conditions. 17 4.3.1.2 Message acknowledge bit and acknowledgement procedure (ACK in FCtrl) 18 When receiving a confirmed data message, the receiver shall respond with a data frame that 19 has the acknowledgment bit (ACK) set. If the sender is an end-device, the network will send 20 the acknowledgement using one of the receive windows opened by the end-device after the 21 send operation. If the sender is a gateway, the end-device transmits an acknowledgment at 22 its own discretion. 23 Acknowledgements are only sent in response to the latest message received and are never 24 retransmitted. 25 26 Note: To allow the end-devices to be as simple as possible and have 27 as few states as possible it may transmit an explicit (possibly empty) 28 acknowledgement data message immediately after the reception of a 29 data message requiring a confirmation. Alternatively the end-device 30 may defer the transmission of an acknowledgement to piggyback it 31 with its next data message. 32 4.3.1.3 Retransmission procedure 33 The number of retransmissions (and their timing) for the same message where an 34 acknowledgment is requested but not received is at the discretion of the end device and 35 may be different for each end-device. 36 Note: Some example timing diagrams of the acknowledge mechanism 37 are given in Chapter 19. 38 39 Note: If an end-device has reached its maximum number of 40 retransmissions without receiving an acknowledgment, it can try to re- 41 gain connectivity by moving to a lower data rate with longer reach. It is 42 up to the end-device to retransmit the message again or to forfeit that 43 message and move on. 44 45

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1