Document

LoRa Alliance 5177 Brandin Court, Fremont, CA 94538 USA LoRaWAN 1.0.4 End Device Certification Page 165 of 173 Requirements for All Regions Version 1.4 Copyright © 2021 LoRa Alliance, Inc. All rights reserved. www.lora-alliance.org 4. Test Case Mapping with LoRaWAN Specification [1] 1370 The following table provides the section mapping between the LoRaWAN Specification [1] and this 1371 Certification Specification document 1372 LoRaWAN Spec [1] section This document section Description 3.3 2.5.11 Receive Windows 4 0 2.4.1 and 2.4.2 MAC Packet Formats 5.1 2.5.7 LinkCheck 5.2 2.5.8 LinkADR 5.3 0 DutyCycle 5.4 2.5.4 RXParamSetup 5.5 2.5.1 DevStatus 5.6 2.5.2 and 2.5.3 NewChannel and DlChannel 5.7 2.5.5 RXTimingSetup 5.8 2.5.6 TXParamSetup 5.9 2.5.10 DeviceTime 6.2 2.2 Over the air Activation 6.3 2.3 Activation by Personalization Table 5 LoRaWAN Spec vs Certification Spec mapping 1373 1374 5. Retransmission back-off tests for power-up or reset of 1375 device – for OTAA device only 1376 Note: A 64-channel gateway is required for running the Back-off tests for Fixed channel devices. 1377 Dynamic channel devices may use an 8-channel or 16-channel gateway. 1378 1379 Manually reset the DUT. DUT starts the Join procedure. 1380 1381 TCL ignores the Join-Requests from the DUT. 1382 1383 For the first one-hour, DUT sends Join-Requests such that the aggregated Transmit time of all uplinks 1384 < 36s per hour. 1385 For the next 10 hours, DUT sends Join-Requests such that the aggregated Transmit time of all uplinks 1386 < 36s per 10 hours. 1387 For the next 24 hours, DUT sends Join-Requests such that the aggregated Transmit time of all uplinks 1388 < 8.7s per 24 hours. 1389 1390 1391 Note: The DUT must not reset itself during this period, unless the DUT ensures that it still complies 1392 with the above-mentioned transmission timing after reset. 1393 1394 5.1. Test Procedure Frame Sequence Chart 1395 1396

• Cover