Document

TS003-2.0.0 Application Layer Clock Synchronization

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

Contents of this Issue

Navigation

Page 9 of 12

LoRaWAN ® Application Layer Clock Synchronization Specification TS003-2.0.0 ©2022 LoRa Alliance ® Page 10 of 13 The authors reserve the right to change specifications without notice. 313 The end-device SHALL respond with the DeviceAppTimePeriodicityAns message 314 containing the following payload: 315 316 Size (octets) 1 4 Field Status DeviceTime Table 10: DeviceAppTimePeriodicityAns 317 Where: 318 Bits 7:1 0 Status Fields RFU NotSupported Table 11: DeviceAppTimePeriodicityAns Status format 319 The NotSupported bit SHALL be set to 1 if the end-device's application does not accept 320 a periodicity set by the Application Server and manages the clock synchronization process 321 and periodicity itself. 322 323 The DeviceTime definition is identical to the definition of the DeviceTime field of the 324 AppTimeReq command in section 3.2. 325 3.4 Force Device Resynchronization Command 326 (ForceDeviceResyncCmd) 327 328 The ForceDeviceResyncCmd message is transmitted by the Application Server to the end- 329 device to trigger a clock resynchronization. 330 Example: A condition that may trigger this transmission is the 331 McClassCSessionAns message (described in the LoRaWAN Remote 332 Multicast Setup Specification [TS005]) sent by the end-device in 333 response to a Class C setup command from the Application Server. If 334 the server detects that the end-device's clock is not well synchronized, 335 it should force the end-device to re-synchronize its clock; otherwise the 336 end-device will miss the multicast slot. 337 338 The ForceDeviceResyncCmd command has a single octet payload: 339 340 Size (octets) 1 Field ForceConf Table 12: ForceDeviceResyncCmd 341 Where: 342 Bits 7:3 2:0 ForceConf Fields RFU NbTransmissions Table 13: ForceConf format 343 There is no answer message to this command. The end-device SHALL respond by sending 344 up-to NbTransmissions AppTimeReq messages with the AnsRequired bit set to 0. 345 The end-device SHALL stop re-transmissions of the AppTimeReq if a valid AppTimeAns is 346 received. If the NbTransmissions field is 0, the command SHALL be silently discarded. 347 The delay between consecutive transmissions of the AppTimeReq is application specific. 348

Articles in this issue

view archives of Document - TS003-2.0.0 Application Layer Clock Synchronization