Issue link: https://read.uberflip.com/i/1428308
TR007 Developing LoRaWAN® Devices © 2021 LoRa Alliance® Page 22 of 26 The authors reserve the right to change specifications without notice. ADR controls the channel plan, data rate, transmit power and number of retransmissions 684 used by the end-device. These attributes are dynamically adapted as the network observes 685 changes in the RF conditions and gateway configurations supporting the end-device. 686 In all cases, the network is in the best position to determine the optimum ADR configurations 687 for the end-device as it enjoys a network-wide view, where the device has no visibility 688 outside of its own behavior. This is true even for mobile devices. 689 3.15.2 Recommended Practice 690 ADR (Adaptive Data Rate) SHOULD be fully supported and enabled by default. The end- 691 device owner SHOULD coordinate with the network operator to define a device management 692 schema (i.e. profile) which optimizes its connectivity. This is particularly true for end-devices 693 with special considerations (mobile, nomadic, or other widely varying RF conditions). 694 3.16 ADR Back Off 695 3.16.1 Description 696 [TS001] described the mechanism by which ADR controlled end-devices restore connectivity 697 by executing a stepwise algorithm that restores maximum transmit power, gradually 698 decreases data rate and ultimately re-enables all default channels. The pace of this back off 699 is controlled by a pair of parameters: ADR_ACK_LIMIT and ADR_ACK_DELAY. By default, 700 ADR_ACK_LIMIT is 64 uplink messages without a Class A downlink and ADR_ACK_DELAY 701 is 32 uplink messages without a Class A downlink. 702 3.16.2 Recommended Practice 703 End-devices SHOULD implement ADR and the ADR back off algorithm with the default 704 values of ADR_ACK_LIMIT and ADR_ACK_DELAY, defined in [RP002]. If the end-device 705 implements values other than the default for ADR_ACK_LIMIT and ADR_ACK_DELAY, the 706 end-device SHALL communicate these values to the network operator out of band, during 707 the provisioning process. 708 3.17 Duty Cycle Limitations 709 3.17.1 Description 710 [TS001] defines some duty cycle limitations and controls over the end-device to improve 711 network optimization, however, regulatory regions around the world may enforce specific 712 duty cycle limitations in addition to those specified by LoRaWAN®. These limitations may 713 be different by frequency band, channel bandwidth or transmit power. Duty cycle limitations 714 may apply to the gateway as well as the end-device, which may impact the network's ability 715 to send downlinks in response to requests from the end-device. 716 3.17.2 Recommended Practice 717 The end-device SHALL respect the lower of the two duty cycle limitations (LoRaWAN or 718 Regulatory). Most often, a LoRaWAN network will not set a duty cycle limitation, and the 719 end-device SHALL respect the regulatory duty cycle limitations 720