Issue link: https://read.uberflip.com/i/1546053
LoRaWAN ® Relay Technical Recommendations TR016-1.0.0 ©2026 LoRa Alliance ® Page 9 of 20 The authors reserve the right to change specifications without notice. 201 Figure 4: Battery life Simulation – LoRaWAN® Relay 202 203 204 3.3 Relay Traffic Constraints 205 The capacity of a Relay to handle end-device traffic is inherently constrained by both the Relay 206 protocol and the physical limitations of the relay equipment. These constraints include, but are 207 not limited to: 208 • Battery capacity and power availability 209 • Limited backhaul connectivity due to duty-cycle restrictions and low capacity 210 Network operators and implementers SHOULD account for these limitations when determining 211 the number of end-devices that can be supported by each Relay, ensuring alignment with the 212 traffic profile of the connected end-devices. 213 Failure to adhere to this recommendation MAY result in suboptimal network performance, 214 increased power consumption, or connectivity failures, affecting both the Relay and 215 associated end-devices. 216 217 3.4 End-Device Compliance and Relay mode 218 End-devices that intend to connect to the network via a Relay SHALL fully implement 219 LoRaWAN® Technical Specification [TS011], including the Wake-On-Radio (WOR) 220 mechanism. The WOR exchange preceding a LoRaWAN® uplink SHOULD be carefully 221 managed to minimize its impact on end-device battery life and to prevent excessive network 222 traffic. In general, when an end-device is not connected to a Relay it SHOULD NOT use the 223 WOR mechanism before each Uplink (see section 4 for more details). 224 225 3.5 Class Consideration 226 Relay functionality described in this TR is restricted to Class A end-devices. End-devices 227 operating through a Relay SHALL comply with Class A specifications, ensuring compatibility 228 with the LoRaWAN® network requirements for relay-based communication. 229 230