Issue link: https://read.uberflip.com/i/1428305
TR005 LoRaWAN® Device Identification QR Codes ©2020 LoRa Alliance® Page 8 of 16 The authors reserve the right to change specifications without notice. Schema ID Description D0 Device Schema Version 0 – the schema described in this document 173 Table 2 – Schema IDs 174 175 4.2.2 JoinEUI 176 177 JoinEUI is the initial JoinEUI value used by the device after shipment (in case the device 178 uses multiple JoinEUIs) that identifies the JS uniquely in the LoRaWAN® Backend 179 Interfaces 1.0 Specification. 180 181 The JoinEUI, formerly AppEUI, value uses a hexadecimal representation resulting in 16 182 characters. 183 4.2.3 DevEUI 184 185 IEEE allocates an Organization Unique Identifier and identifier range to the manufacturer of 186 the subsystem running the LoRaWAN® stack (please refer to IEEE Registration 187 Authority). 188 DevEUI consist of 8 bytes and is described in the LoRaWAN® Link-layer Specification [LW]. 189 190 The DevEUI value uses a hexadecimal representation resulting in 16 characters. 191 4.2.4 ProfileID 192 193 The profile identifier encodes a Vendor Identifier and a Vendor Profile Identifier as a 194 hexadecimal representation resulting in 8 characters. 195 196 ProfileID VendorID VendorProfileID Size (Bytes) 2 2 197 Table 3 – Product ID 198 199 VendorID is assigned by the LoRa Alliance [VID]. The VendorID, 0xFFFF, is to be utilized 200 prior to commercial production of a device. 201 202 VendorProfileID is assigned by the device manufacturer for commercial products. Because 203 the ProfileID may be used as an index on a Device Profile database or payload decoding 204 database, the manufacturer SHALL use a distinct VendorProfileID for devices with different 205 Device Profiles [BE] or payload encodings. 206 4.2.5 Optional Extensions 207 4.2.5.1 Checksum 208 209