Document

TS004-2.0.0 Fragmented Data Block Transport

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

Contents of this Issue

Navigation

Page 9 of 31

LoRaWAN ® Fragmented Data Block Transport Specification TS004-2.0.0 ©2022 LoRa Alliance ® Page 10 of 32 The authors reserve the right to change specifications without notice. 3.1 Package Version Commands (PackageVersionReq, 225 PackageVersionAns) 226 227 The PackageVersionReq command has no payload. 228 229 The end-device SHALL answer this command with a PackageVersionAns command with 230 the following payload: 231 232 Size (octets) 1 1 Field PackageIdentifier PackageVersion Table 3: PackageVersionAns PackageIdentifier uniquely identifies the package. 233 234 PackageVersion corresponds to the version of the package specification implemented 235 by the end-device. 236 3.2 Fragmentation Session Status Commands (FragSessionStatusReq, 237 FragSessionStatusAns) 238 239 These commands can be transmitted by the server in a unicast or multicast downlink frame. 240 241 Size (octets) 1 Payload FragStatusReqParam Table 4: FragSessionStatusReq Where: 242 243 Bits 7:3 2:1 0 FragStatusReqParam Field RFU FragIndex Participants Table 5: FragSessionStatusReq FragStatusReqParam format FragSessionStatusReq is used by the fragmentation server to request receiver end- 244 devices to report their current defragmentation status. 245 246 The receivers (in the case of multicast) SHOULD NOT answer this request all at the same 247 time because this would potentially generate a lot of collisions. The receivers SHALL 248 randomly spread their responses as specified by the BlockAckDelay field of the 249 FragSessionSetupReq command. 250 251 The Participants bit signals when all fragmentation receivers SHALL answer or when 252 only the ones still missing fragments SHALL answer: 253 • If the Participants bit value is 0, only the receivers that are still missing 254 fragments SHALL answer the request. 255 • If the Participants bit value is 1, all receivers SHALL answer, even those who 256 already successfully reconstructed the data block. 257 The end-devices SHALL respond with a FragSessionStatusAns message. The message 258 payload is: 259

Articles in this issue

view archives of Document - TS004-2.0.0 Fragmented Data Block Transport