Document

TS009-1.1.0 Certification Protocol

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

Contents of this Issue

Navigation

Page 9 of 25

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

Articles in this issue

view archives of Document - TS009-1.1.0 Certification Protocol