LoRaWAN
®
Relay Technical Recommendations
TR016-1.0.0
©2026 LoRa Alliance
®
Page 11 of 20
The authors reserve the right to change
specifications without notice.
• keep the WOR protocol activated and 275
• proceed to the JOINED_WOR_ACTIVATED case (see section 276
4.2) 277
o Else, if a valid Join-Accept is received on RXR: 278
▪ keep the WOR protocol activated and 279
▪ prefix every subsequent uplink frame with a WOR-Uplink and proceed 280
to the JOINED_WOR_ACTIVATED case (see section 4.2) 281
o Else, if no Join-Accept is received after N2 attempts: 282
▪ deactivate WOR and 283
▪ start over the DEVICE_NOT_JOINED state machine described in this 284
section. 285
286
Notes: 287
• Recommended settings for N1 and N2: 288
o For dynamic channel plan regions (EU868, AS923, KR920, RU864, IN865 289
etc.): N1=8 and N2=12 290
o For fixed channel plan regions (US915, AU915 etc.): N1=18 and N2=27. 291
• The LinkCheckReq command is useful to avoid deactivating the WOR protocol too 292
quickly, given the variability of the RF propagation conditions due to fading and 293
shadowing effects. 294
• The condition associated to N2 is useful for the end-device battery, to avoid sending 295
WOR-Join-Request permanently if there is no LoRaWAN network at all. 296
297
This state machine is illustrated by Figure 5: 298
