Issue link: https://read.uberflip.com/i/1539840
Developing LoRaWAN Devices Technical Recommendation TR007-1.1 ©2021-2025 LoRa Alliance ® Page 21 of 28 The authors reserve the right to change documents without notice. 3 Minimize end-device power consumption 667 ADR controls the channel plan, data rate, transmit power, and number of retransmissions used 668 by the end-device. These attributes are dynamically adapted as the network observes 669 changes in the RF conditions and gateway configurations supporting the end-device. 670 In all cases, the network is in the best position to determine the optimum ADR configurations 671 for the end-device as it enjoys a network-wide view, where the device has no visibility outside 672 of its own behavior. This is true even for mobile devices. 673 4.15.2 Recommended Practice 674 ADR SHOULD be fully supported and enabled by default. The end-device owner SHOULD 675 coordinate with the network operator to define a device management schema (i.e., profile) that 676 optimizes its connectivity. This is particularly true for end-devices with special considerations 677 (mobile, nomadic, or other widely varying RF conditions). 678 4.16 ADR Back-Off 679 4.16.1 Description 680 The LoRaWAN Link Layer specification describes the mechanism by which ADR-controlled 681 end-devices restore connectivity by executing a stepwise algorithm that restores maximum 682 transmit power, gradually decreases data rate, and ultimately re-enables all default channels. 683 The pace of this back-off is controlled by a pair of parameters: ADR_ACK_LIMIT and 684 ADR_ACK_DELAY. By default, ADR_ACK_LIMIT is 64 uplink messages without a Class A 685 downlink and ADR_ACK_DELAY is 32 uplink messages without a Class A downlink. 686 4.16.2 Recommended Practice 687 End-devices SHOULD implement ADR and the ADR back-off algorithm with the default values 688 of ADR_ACK_LIMIT and ADR_ACK_DELAY, defined in [RP002]. If the end-device 689 implements values other than the default for ADR_ACK_LIMIT and ADR_ACK_DELAY, the 690 end-device SHALL communicate these values to the network operator out-of-band, during the 691 provisioning process. 692 4.17 Duty Cycle Limitations 693 4.17.1 Description 694 The LoRaWAN Link Layer specification defines some duty cycle limitations and controls over 695 the end-device to improve network optimization, however, regulatory regions around the world 696 may enforce specific duty cycle limitations in addition to those specified by LoRaWAN. These 697 limitations may be different by frequency band, channel bandwidth, or transmit power. Duty 698 cycle limitations may apply to the gateway as well as the end-device, which may impact the 699 network's ability to send downlinks in response to requests from the end-device. 700