Issue link: https://read.uberflip.com/i/1428395
LoRaWAN ® L2 1.0.4 Specification © 2020 LoRa Alliance ® Page 76 of 90 The authors reserve the right to change specifications without notice. Note: The purpose of this timeout is for the Network Server to know how 2296 long to wait for a response from the end-device, before it transmits 2297 another Class C confirmed downlink. This ensures that the Network 2298 Server can process responses without any ambiguity: there may be only 2299 a single confirmed Class C downlink pending an acknowledgement. 2300 2301 The uplink frame sent in response MAY be sent up to NbTrans times, but no retransmission 2302 SHALL occur after the timeout period. It is RECOMMENDED that the end-device transmits 2303 each copy of the uplink frame at a random time within CLASS_C_RESP_TIMEOUT. 2304 As this adds a timing requirement compared to responding to Class A downlinks, the end- 2305 device may not send an uplink frame within the timeout, for instance if it has a duty cycle 2306 limitation. When such an uplink frame is not sent, the end-device SHALL act as if the uplink 2307 frame with the ACK bit set was sent. 2308 After sending a Class C confirmed downlink, a network server SHALL NOT send any other 2309 confirmed downlink to the end-device until this timeout expires or an uplink frame is received 2310 from that end-device. 2311 After sending a Class A confirmed downlink, a network server SHALL NOT send any other 2312 confirmed downlink to the end-device until an uplink frame is received from that end-device. 2313 2314 Note: Class C downlink frames of type Unconfirmed Data may be sent 2315 without a minimum delay between them. 2316 2317 2318 2319 Figure 6: Class C end-device reception slot timing 2320 2321 2322 2323 Note: As defined in Section 3, the end-device does not open RX2 if a 2324 downlink is received in RX1. In that case, the end-device opens a 2325 continuous RXC receive window at the end of the demodulation of the 2326 RX1 downlink that extends until the next uplink. 2327 2328