Academy for LoRaWAN®

All end devices must persist these parameters during a reset of the device, as well as when the device suffers a power loss.

Required Persistent Values for OTAA Devcies

In the event of a reset or power loss, the following values must persist, so that the end devices will not re-initiate a Join procedure:

• DevEUI
• JoinEUI 
• Root Keys (AppKey/NwkKey)
• DevNonce (The DevNonce is implemented as a counter from LW1.0.4; the last value used SHALL be persisted to ensure no previous values are re-used.)
• JoinNonce  (This must be validated against reuse by the end device. If the join server supports incrementing JoinNonce values, the last value should be persisted for validation.  If the join server does not support incrementing JoinNonce values, the end device must persist a reasonable number of most- recently-seen values.)
• SessionKeys
• Frame Counters (both uplink and downlink)
• Channel List (frequencies and enabled channels)
• Data rate
• TXPower
• NbTrans
• MaxDutyCycle
• RX2Frequency
• RX1DROffset
• RX2DataRate
• RXTimingDelay
• MaxEIRP
• DownlinkDwellTime
• UplinkDwellTime

Required Persistent Values for ABP Devcies

In the event of a reset or loss of power, the following values must be persisted so that an ABP end device can return to the network connection session where it left off before the loss of power:

• DevEUI
• DevAddr
• SessionKeys
• Frame Counters (both uplink and downlink)
• Channel List (frequencies and enabled channels)
• Data rate
• TXPower
• NbTrans
• MaxDutyCycle
• RX2Frequency
• RX1DROffset
• RX2DataRate
• RXTimingDelay
• MaxEIRP
• DownlinkDwellTime
• UplinkDwellTime