Issue link: https://read.uberflip.com/i/1539840
Developing LoRaWAN Devices Technical Recommendation TR007-1.1 ©2021-2025 LoRa Alliance ® Page 19 of 28 The authors reserve the right to change documents without notice. 4.12 Frame Counters Incremented Only With Frame Transmission 599 4.12.1 Description 600 The frame counter is used for both security (for MIC generation/validation and 601 encryption/decryption), and detection of lost frames. By only incrementing the frame counter 602 after transmission, end-devices, Application Servers, and Network Servers can reliably use 603 the frame counter to detect lost frames. In turn, this information could influence RF 604 configuration to optimize communication reliability and efficiency. 605 4.12.2 Recommended Practice 606 End-devices, Application Servers, and Network Servers SHALL only increment (by one) frame 607 counters after a message transmission has been attempted. 608 4.13 OTAA REQUIRED Persistent Values 609 4.13.1 Description 610 End-devices operating in OTAA mode are REQUIRED to persist several values to remain 611 compliant with the LoRaWAN Link Layer specification. 612 4.13.2 Recommended Practice 613 For end-devices that will initiate a Join Procedure following a reset or loss of power, the 614 following values SHALL be persisted. End-devices that will NOT initiate a Join Procedure 615 following a reset or loss of power SHALL persist these values as well as those described for 616 ABP end-devices: 617 • DevEUI 618 • JoinEUI 619 • Root keys (AppKey/NwkKey) 620 • DevNonce 621 The DevNonce SHALL be implemented as a counter, the last value used SHALL be 622 persisted to ensure no previous values are reused. 623 • JoinNonce 624 The JoinNonce needs to be validated against reuse by the end-device. If the JS 625 supports incrementing JoinNonce values, as recommended in [TR001-1.0.0], a last 626 value SHALL be persisted for validation. If the JS does not support incrementing 627 JoinNonce values, the end-device SHOULD persist a reasonable number of most 628 recently seen values. 629 In LoRaWAN 1.0.4+, DevNonce SHALL be implemented as a counter. 630