Issue link: https://read.uberflip.com/i/1464683
LoRaWAN ® Fragmented Data Block Transport Specification TS004-2.0.0 ©2022 LoRa Alliance ® Page 15 of 32 The authors reserve the right to change specifications without notice. The end-device SHALL answer with a FragSessionSetupAns message with the following 418 payload: 419 420 Size (octets) 1 FragSessionSetupAns payload StatusBitMask Table 13: FragSessionSetupAns 421 Bits 7:6 5 4 3 2 1 0 Status BitMask Bits Frag Index RFU SessionCnt replay Wrong Descriptor FragIndex unsupported Not enough Memory FragAlgo unsupported Table 14: FragSessionSetupAns StatusBitMask format If any of the bits [0:4] is set to 1, the FragSessionSetupReq command was not accepted. 422 423 If a FragSessionSetupReq command with a FragIndex field corresponding to an already 424 existing fragmentation session is received and accepted, the current session SHALL be 425 stopped, and its context SHALL be cleared. The end-device SHALL set up a new session 426 with the parameters of the new FragSessionSetupReq command. 427 3.4 Fragmentation Session Delete Commands (FragSessionDeleteReq, 428 FragSessionDeleteAns) 429 430 These commands are used to delete a fragmentation session. The command payload is: 431 432 Size (octets) 1 Field Param Table 15: FragSessionDeleteReq Where: 433 Bits 7:2 1:0 Param bits RFU FragIndex Table 16: FragSessionDeleteReq Param bits The end-device SHALL respond to the FragSessionDeleteReq command with a 434 FragSessionDeleteAns command, which has the following payload: 435 436 Size (octets) 1 Field Status Table 17: FragSessionDeleteAns Where: 437 Bits 7:3 2 1:0 Status bits RFU Session does not exist FragIndex Table 18: FragSessionDeleteAns Status bits If bit 2 is set to 1, the FragSessionDeleteReq command was not accepted because the 438 fragmentation session corresponding to FragIndex did not exist in the end-device. 439