Issue link: https://read.uberflip.com/i/1464686
LoRaWAN ® Multi-Package Access Protocol Specification TS007-1.0.0 ©2022 LoRa Alliance ® Page 6 of 15 The authors reserve the right to change specifications without notice. 3 Multi-Package Access Protocol 140 141 A command implemented by one of the packages running on the end-device MAY be 142 invoked by one of the following methods: 143 • Dedicated-package access 144 • Multi-package access 145 If implemented, the Multi-Package Access Protocol SHALL use FPort 225. 146 147 Other packages MAY use any FPort value from those not assigned by the LoRa Alliance ® , 148 excluding FPort 225, for dedicated-package access. Every package SHALL use a different 149 FPort number, and this FPort number SHALL NOT be used by the end-device's application. 150 3.1 Multi-Package Access 151 152 With multi-package access, the Application Server sends an applicative downlink to the end- 153 device on the multi-package FPort (225), with the following syntax. This method SHALL be 154 used on FPort 225 only. 155 156 PackageID 1 (opt) CommandID 1 Command1 Payload PackageID 2 (opt) CommandID 2 Command2 payload … Command Token Table 1: Multi-package access command format 157 The Command Token field is a 1-byte field with the following format: 158 159 Bits 7:2 1:0 Command Token Fields RFU Token Table 2: Command Token field format 160 The Command Token field SHALL be appended to all downlink command sets unless the 161 downlink only contains a MultiPackBufferReq command (Refer to section 4.4). The 162 Command Token field is used by the server to differentiate the end-device's answers to 163 different consecutive downlink commands. The end-device SHALL systematically append 164 the Command Token field into the uplink answer(s) to a multi-package server command. 165 166 The multi-package FPort MAY be used to access any package. A PackageID field is 167 used to differentiate among packages to which individual commands belong, that are sent 168 via multi-package access. 169 170 The first command (CommandID1) SHALL be prefixed with a PackageID field if the first 171 package identifier is different from 0 (multi-package access package). If the first package 172 identifier is 0, it SHALL NOT be prefixed with a PackageID field. 173 174 For the next commands, a PackageID field is REQUIRED when the command does not 175 belong to the same package as the preceding command. If several consecutive commands 176 belong to the same package, only the first command of the series SHALL be prefixed with a 177 PackageID field. The PackageID field SHALL NOT be used for the subsequent 178 commands. 179 180 PackageID field is a 1-byte field that has the following format: 181