Issue link: https://read.uberflip.com/i/1428386
LoRaWAN Specification ©2016 LoRa™ Alliance Page 83 of 91 The authors reserve the right to change specifications without notice. 1 Figure 18: Downlink timing diagram for confirmed data messages 2 The frame exchange is initiated by the end-device transmitting an "unconfirmed" application 3 payload or any other frame on channel A. The network uses the downlink receive window to 4 transmit a "confirmed" data frame towards the end-device on the same channel A. Upon 5 reception of this data frame requiring an acknowledgement, the end-device transmits a 6 frame with the ACK bit set at its own discretion. This frame might also contain piggybacked 7 data or MAC commands as its payload. This ACK uplink is treated like any standard uplink, 8 and as such is transmitted on a random channel that might be different from channel A. 9 Note: To allow the end-devices to be as simple as possible and have 10 keep as few states as possible it may transmit an explicit (possibly 11 empty) acknowledgement data message immediately after the 12 reception of a data message requiring an acknowledgment. 13 Alternatively the end-device may defer the transmission of an 14 acknowledgement to piggyback it with its next data message. 15 19.3 Downlink Timing for Frame-Pending Messages 16 The next diagram illustrates the use of the frame pending (FPending) bit on a downlink. 17 The FPending bit can only be set on a downlink frame and informs the end-device that the 18 network has several frames pending for him; the bit is ignored for all uplink frames. 19 If a frame with the FPending bit set requires an acknowledgement, the end-device shall do 20 so as described before. If no acknowledgment is required, the end-device may send an 21 empty data message to open additional receive windows at its own discretion, or wait until it 22 has some data to transmit itself and open receive windows as usual. 23 Note: The FPending bit is independent to the acknowledgment 24 scheme. 25 26 Figure 19: Downlink timing diagram for frame-pending messages, example 1 27 gateway End-point Unconfirmed data {Cu} Confirmed Data {Cd} ok ok Receive slots ok ACK {Cu+1} gateway End-point Data uplink {cu} Confirmed Data0+F_P {cd} ACK {cu+1} Confirmed Data1 {cd+1} ACK {cu+2} ok ok ok (*) F_P means 'frame pending' bit set Receive slots
