Document

TS004-2.0.0 Fragmented Data Block Transport

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

Contents of this Issue

Navigation

Page 8 of 31

LoRaWAN ® Fragmented Data Block Transport Specification TS004-2.0.0 ©2022 LoRa Alliance ® Page 9 of 32 The authors reserve the right to change specifications without notice. The following table summarizes the list of fragmented data block transport package 220 messages: 221 222 CID Command name Transmitted by Multicast (M) / Unicast (U) Short Description End- device App Server 0x00 PackageVersionReq x U Used by the Application Server to request the package version implemented by the end- device 0x00 PackageVersionAns x U Conveys the answer to PackageVersionReq 0x01 FragSessionStatusReq x U/M Asks an end-device or a group of end-devices to send the status of a fragmentation session 0x01 FragSessionStatusAns x U Conveys the answer to the FragSessionStatusReq request 0x02 FragSessionSetupReq x U Defines a fragmentation session 0x02 FragSessionSetupAns x U Conveys the answer to FragSessionSetupReq 0x03 FragSessionDeleteReq x U Used to delete a fragmentation session 0x03 FragSessionDeleteAns x U Conveys the answer to FragSessionDeleteReq 0x04 FragDataBlockReceivedReq x U Used by the end-device to signal the fragmentation server that a data block has been completely received 0x04 FragDataBlockReceivedAns x U Conveys the answer to FragDataBlockReceivedReq 0x08 DataFragment x U/M Carries a fragment of a data block Table 2: Summary of fragmented data block transport package messages The messages marked "U/M" can be received using a unicast or multicast address. All other 223 messages are exchanged only using the unicast end-device address. 224

Articles in this issue

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