Document

TR007 Developing LoRaWAN Devices - v1.1.0

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

Contents of this Issue

Navigation

Page 19 of 27

Developing LoRaWAN Devices Technical Recommendation TR007-1.1 ©2021-2025 LoRa Alliance ® Page 20 of 28 The authors reserve the right to change documents without notice. 4.14 ABP REQUIRED Persistent Values 631 4.14.1 Description 632 End-devices operating in ABP mode are REQUIRED to persist several values to remain 633 compliant with the LoRaWAN Link Layer specification and ensure that they remain in contact 634 with the network. 635 4.14.2 Recommended Practice 636 All ABP end-devices SHALL persist the following values through a reset or loss of power: 637 • DevEUI 638 • DevAddr 639 • SessionKeys 640 • Frame counters (both uplink and downlink) 641 End-devices that do not support ResetInd SHALL persist the additional values through a reset 642 or loss of power: 643 • Channel List (frequencies and enabled channels) 644 • Data rate 645 • TxPower 646 • NbTrans 647 • MaxDutyCycle 648 • RX2Frequency 649 • RX1DROffset 650 • RX2DataRate 651 • RXTimingDelay 652 • MaxEIRP 653 • DownlinkDwellTime 654 • UplinkDwellTime 655 If an end-device is operating with Class B enabled, the following additional values SHALL be 656 persisted through a reset or loss of power: 657 • PingSlotPeriodicity 658 • BeaconFrequency 659 • PingSlotFrequency 660 • PingSlotDataRate 661 4.15 Adaptive Data Rate Support 662 4.15.1 Description 663 ADR is used by the Network Server to optimize the configuration of the end-device to: 664 1 Maximize connectivity 665 2 Minimize airtime 666

Articles in this issue

view archives of Document - TR007 Developing LoRaWAN Devices - v1.1.0