Issue link: https://read.uberflip.com/i/1428305
TR005 LoRaWAN® Device Identification QR Codes ©2020 LoRa Alliance® Page 9 of 16 The authors reserve the right to change specifications without notice. The Checksum is used to validate the data integrity. Even though QR codes have their own 210 built-in integrity checks, this explicit checksum is useful when the content of the QR code is 211 presented as plain text. Checksum is generated using the CRC-16-MODBUS [CRC] of the 212 full QR content except the Checksum field itself, and presented in hexadecimal format 213 without the leading "0x". 214 4.2.5.2 OwnerToken 215 The OwnerToken is used to prove the ownership of the end-device (as identified by its 216 DevEUI) to a system that allows the device owner to create and modify settings associated 217 with the end-device. For example: Registering the end-device on the home NS and setting 218 the home NS of the end-device on the JS. 219 It is RECOMMENDED that OwnerToken is not used for retrieving any confidential 220 information related to the end-device. Using it for such purposes requires the OwnerToken 221 to be protected at the same level as the AppKey/NwkKey. 222 The OwnerToken SHALL be protected against unauthorized access on the end-device until 223 it is used by the legitimate owner of the device (e.g., not accessible until the end-device is 224 unpacked). 225 How the OwnerToken is generated, delivered to the systems verifying its value, and whether 226 it is a one-time-use value are outside the scope of this document. See Appendix A for an 227 example. 228 4.2.5.3 SerNum 229 230 The SerNum, serial number, is a unique identifier assigned during the product manufacturing 231 process. The SerNum does not need to be strictly a number and may contain any 232 characters, with the exception of the ":" from the available alphabet indicated in Section 5.1 233 of this document. 234 4.2.5.4 Proprietary 235 236 Tag content can be extended using proprietary schemes, using any characters, with the 237 exception of the ":" from the available alphabet indicated in Section 5.1 of this document. 238 239 The ProfileID field may be used to determine the interpretation of the proprietary extensions 240 and SerNum field. 241 242