Document

TS009-1.2.1 Certification Protocol

Issue link: https://read.uberflip.com/i/1527095

Contents of this Issue

Navigation

Page 9 of 26

LoRaWAN ® Certification Protocol Specification TS009-1.2.1 ©2024 LoRa Alliance ® Page 10 of 27 The authors reserve the right to change specifications without notice. 4 End-Device Certification Description 252 4.1 Overview 253 Every LoRaWAN end-device SHALL implement this applicative protocol specification in its 254 application layer. This allows the LCTT to fully validate compliance of the end-device's 255 LoRaWAN MAC layer implementation. 256 257 The FPort value of 224 is dedicated to the LoRaWAN MAC layer certification protocol. 258 259 The DUT SHALL return to its normal application behavior via a command disabling 260 certification FPort 224 processing. Additionally, the DUT SHALL be reset with a dedicated 261 command, returning to a join state from which it can then establish a new session. 262 263 All defined test commands SHALL be sent by the TCL to the DUT using FPort 224 when 264 the end-device is in its normal operation. The DUT SHOULD execute the given command as 265 soon as possible. 266 4.1.1 Over-The-Air Activated DUT 267 268 If the DUT uses OTAA, when the DUT is first powered up, it SHOULD join the network by 269 issuing a Join-Request. The TCL will respond with a Join-Accept. As a best practice of the 270 certification process, upon receipt of the Join-Accept frame, the DUT SHOULD send a 271 (possibly empty) uplink frame. The TCL is then able to send certification test commands on 272 FPort 224, if enabled. 273 4.1.2 Activated by Personalization DUT 274 275 A personalized DUT is one that comes with session keys pre-programmed. The 276 personalization information SHALL be supplied to the ATH. When the DUT is first powered 277 on, it SHOULD send an uplink frame. The TCL is then able to send certification test 278 commands on FPort 224, if enabled. 279 4.2 Certification Commands 280 4.2.1 Downlink Counter 281 282 The DUT creates a 16-bit unsigned counter (called RxAppCnt) that is incremented each time 283 the DUT receives an applicative downlink frame (FPort > 0). An empty downlink frame with 284 a FCtrl ACK bit set SHALL be considered as an applicative downlink. 285 The RxAppCnt counter SHALL be initialized to 0 when the DUT is reset or each time the 286 TCL sends a DownlinkCntRstReq command on FPort 224. 287 4.2.2 Beacon Counter 288 289 The DUT creates a 16-bit unsigned counter (called BeaconCnt) that is incremented each 290 time the DUT receives a Class B beacon. 291

Articles in this issue

view archives of Document - TS009-1.2.1 Certification Protocol