Issue link: https://read.uberflip.com/i/1428356
LoRaWAN Fragmented Data Block Transport v1.0.0 Specification ©2018 LoRa Alliance™ Page 10 of 30 The authors reserve the right to change specifications without notice. 254 3.3 FragSessionDeleteReq & Ans 255 This message is used to delete a fragmentation session. A fragmentation session MUST be 256 deleted before its index (FragIndex) can be reused for another one. The command payload 257 is: 258 259 260 261 Table 8: FragSessionDeleteReq 262 Where: 263 Bits 7:2 1:0 Param bits RFU FragIndex Table 9: FragSessionDeleteReq Param bits 264 265 The end-device answers with FragSessionDeleteAns with payload: 266 267 268 269 Table 10: FragSessionDeleteAns 270 Where: 271 Bits 7:3 2 1:0 Status bits RFU Session does not exist FragIndex Table 11: FragSessionDeleteAns Status bits 272 If the bit 2 is set to 1 the FragSessionDeleteReq command was not accepted because the 273 fragmentation session corresponding to FragIndex did not exist in the end-device. 274 3.4 Downlink Data Fragment message 275 This message can be received by the end-device in a multicast or unicast downlink frame. 276 This message is used to carry a data block fragment. 277 The payload content is: 278 279 Size (bytes) Index&N 0:MaxAppPl-3 Payload 2 Table 12: Downlink Data Fragment payload 280 281 Index&N Fields FragIndex N Size (bits) 2bits 14bits Table 13: Downlink Data Fragment Index&N field 282 Field Param Size (bytes) 1 Field Status Size (bytes) 1