Issue link: https://read.uberflip.com/i/1464686
LoRaWAN ® Multi-Package Access Protocol Specification TS007-1.0.0 ©2022 LoRa Alliance ® Page 13 of 15 The authors reserve the right to change specifications without notice. payload size that can be transported is 10 bytes and the end-device received the request on FPort 225. CommandID Command payload 0x02 0x01 0x05 Table 16: MultiPackBufferReq command example The StartByte parameter is 1, StopByte is 5. Therefore, the end-device must respond with the following applicative payload sent on FPort 225: CommandID BaseByte Command payload Command Token 0x02 1 ANS[1..5] 0x02 Table 17: MultiPackBufferFrag example The length of the applicative payload is 8 bytes. The payload contains: • The command identifier (CommandID): 0x02, corresponding to MultiPackBufferFrag. • The BaseByte field, which is the index of the first byte being transmitted. • The ANS buffer content, starting at byte 1 (because StartByte==1) and stopping at byte 5. (Note: The byte numbering for the ANS buffer always starts at byte 0). 361 Example 2: The ANS buffer is still 13 bytes long. The maximum applicative payload size that can be transported is unchanged at 10 bytes, and the end-device received the request on FPort 225. CommandID Command payload 0x02 0x01 0x0C Table 18: MultiPackBufferReq command example The StartByte parameter is 1, StopByte is 12. Therefore, the end-device must respond with the following applicative payloads sent on FPort 225: CommandID BaseByte Command payload Command Token 0x02 1 ANS[1..7] 0x02 Table 19: MultiPackBufferFrag example (first message) CommandID BaseByte Command payload Command Token 0x02 8 ANS[8..12] 0x02 Table 20: MultiPackBufferFrag example (second message) The end-device automatically fragments the answer because it cannot fit in a single payload. The first fragment sent contains bytes ANS[1..7] because of the payload length limitation. This mechanism allows the server to request the retransmission of any portion of the ANS 362 buffer if the buffer could not be transmitted in a single uplink payload and a fragment has 363 been lost. 364