Issue link: https://read.uberflip.com/i/1545681
LoRaWAN ® Device Identification QR Codes for Automated Onboarding Specification TS018- 1.0.0 ©2026 LoRa Alliance ® Page 9 of 17 The authors reserve the right to change specifications without notice. 4.2.5 Optional Extensions 227 4.2.5.1 Checksum 228 229 The Checksum is used to validate the data integrity. Even though QR codes have their own 230 built-in integrity checks, this explicit checksum is useful when the content of the QR code is 231 presented as plain text. 232 233 Checksum is generated using the CRC-16-MODBUS [CRC] of the full QR content except the 234 Checksum field itself, the preceding ":" that is used to separate the Checksum value from the 235 preceding value is excluded as well, and presented in hexadecimal format without the leading 236 "0x". Leading 0 (zero) values MAY be omitted (e.g., "FE6" can be used instead of "0FE6"). 237 4.2.5.2 OwnerToken 238 239 The OwnerToken is used to prove the ownership of the end-device (as identified by its 240 DevEUI) to a system that allows the device owner to create and modify settings associated 241 with the end-device. For example: Registering the end-device on the home NS and setting the 242 home NS of the end-device on the JS. 243 244 It is RECOMMENDED that OwnerToken is not used for retrieving any confidential information 245 related to the end-device. Using it for such purposes requires the OwnerToken to be protected 246 at the same level as the LoRaWAN® root keys [TS001]. 247 248 The OwnerToken SHALL use any characters from the character set defined in Section 4.1 of 249 this document. 250 251 The OwnerToken SHALL be protected against unauthorized access on the end-device until it 252 is used by the legitimate owner of the device (e.g., not accessible until the end-device is 253 unpacked). 254 255 How the OwnerToken is generated, delivered to the systems verifying its value, and whether 256 it is a one-time-use value are outside the scope of this document. See also Appendix A. 257 Example Generation and Use of OwnerToken. 258 4.2.5.3 SerNum 259 260 The SerNum, serial number, is a unique identifier assigned during the product manufacturing 261 process. The SerNum does not need to be strictly a number, it SHALL use any characters 262 from the character set defined in Section 4.1 of this document. 263 4.2.5.4 DevProfileServer 264 265 The DevProfileServer is the hostname and (optionally) the port number [RFC3986] of the 266 Device Profile Server (DPS) that is used by the home Network Server (hNS) for retrieving the 267 Device Profile [TS014] of the end-device (e.g., "EXAMPLE.ORG", 268 "EXAMPLE.ORG%3A444"). 269 270 When the port number is provided, it SHALL be delineated from the hostname by a "%3A" 271 (ASCII code of ":"). "%3A" SHALL NOT be used if a port number is not provided. 272