Issue link: https://read.uberflip.com/i/1534635
LoRaWAN® End-Device and Network Server Interoperability Test Plan • LNS-A is configured with either an inbuilt JS-A and/or AS-A or LNS-A is connected to an independent JS-A 222 and/or AS-A. 223 • JS-A is operational and ready to accept Join Requests from DEV-A via LNS-A. 224 • AS-A is operational and ready to receive messages LNS-A. 225 • Monitoring tools are available to capture logs. 226 3.2 Test Cases 227 3.2.1 Activation by Personalisation test 228 This section defines the Activation by Personalisation (ABP) test scenarios. These tests must be executed only if the 229 device is an ABP device. When an ABP device is restarted, it is confirmed that the End-Device sends an uplink on 230 restart, is assigned a valid DevAddr, is allocated a random and unique NwkSKey, is allocated a 128-bit AppKey per 231 application and preserves all its RF settings. 232 3.2.1.1 Test Steps 233 Scenario: Verify Reset parameters of the device for ABP Given DEV-A supports Activation by Personalisation And DEV-A is reset When the operator triggers DEV-A to restart (CAP.1.4) Then DEV-A must send an uplink (EVT.1.4) And LNS-A must validate that DEV-A is assigned the DevAddr correctly where DevAddr = NetID + NwkAddr And LNS-A must validate that DEV-A is allocated a random and unique NwkSKey And LNS-A must validate that DEV-A is allocated a 128-bit AppKey per application And (for LW1.0.4+ devices only) DEV-A must preserve all RF settings (RF channel, frame counters) 3.2.2 Over The Air Activation- Join-Rejoin Process 234 This section defines the Join and Rejoin test scenarios for all network elements. These tests are executed only when 235 the End-Device supports Over the Air Activation. The following scenarios are confirmed: 236 1. After the End-Device is reset, on triggered to send an uplink, the End-Device sends a Join-Request, the LNS 237 responds with a Join-Accept, the End-Device is assigned a valid DevAddr and the End-Device sends an uplink using 238 only the Default channels. 239 2. When the End-Device is triggered to Re-join, the re-join must be successful. Apart from the checks mentioned 240 above, it is also confirmed that they End-Device communicates on the new channels with the CFList, sends the correct 241 MIC checksum for uplinks, properly uses the DLSettings and RxDelay defined in the Join-Accept. 242 3. When RxDrOffset, Rx2Datarate, RxDelay is set in Join-Accept, the End-Device connects successfully and sends 243 uplinks to the LNS. It is also confirmed that the Duty cycle restrictions are met. 244 3.2.2.1 Test Steps 245 Scenario: Verify Join Procedure Given the Prerequisites are met And DEV-A is configured to use OTAA And DEV-A is reset When the operator triggers an uplink on DEV-A (CAP.1.1) Then ©2025 LoRa Alliance ® Page 9 of 18 The authors reserve the right to change specifications without notice.