Issue link: https://read.uberflip.com/i/1428356
LoRaWAN Fragmented Data Block Transport v1.0.0 Specification ©2018 LoRa Alliance™ Page 12 of 30 The authors reserve the right to change specifications without notice. 318 The end-devices respond with a FragSessionStatusAns message. The message payload 319 is: 320 321 Size (bytes) 2 1 1 FragParam Payload Received&index MissingFrag Status Table 17: FragSessionStatusAns 322 Where: 323 324 bits 15:14 13:0 Received&index field FragIndex NbFragReceived Table 18: FragSessionStatusAns Received&index field 325 bits 7:1 0 Status field RFU Not enough matrix memory. The defragmentation process was aborted because the number of missing fragments was greater than the available memory matrix storage capacity Table 19: FragSessionStatusAns Status field 326 327 Used by the fragmentation receiver to report its defragmentation status for the fragmentation 328 session FragIndex. 329 330 NbFragReceived is the total number of fragments received for this fragmentation session 331 since the session was created. 332 333 MissingFrag is the number of independent coded fragments still required before being able 334 to reconstruct the data block. In the case where the block was already successfully 335 reassembled this field SHOULD be 0. If more than 255 fragments are missing, then 336 MissingFrag SHALL be set to 255. 337 338 339 As described in the "FragSessionStatusReq" command, the receivers MUST respond with 340 a pseudo-random delay as specified by the BlockAckDelay field of the 341 FragSessionSetupReq command. 342