Issue link: https://read.uberflip.com/i/1428305
TR005 LoRaWAN® Device Identification QR Codes ©2020 LoRa Alliance® Page 6 of 16 The authors reserve the right to change specifications without notice. 3 Background 113 114 LoRaWAN devices are generally manufactured in bulk and personalized with their unique 115 DevEUI, JoinEUI, security key(s) and DevAddr (in the case of ABP devices), at the time of 116 manufacturing. 117 118 In order for devices to be accepted by the network, relevant device information must be 119 shared with each network element prior to device activation. This process is called 120 provisioning. 121 122 The process of associating an owner and verifying permission to use a network is called 123 onboarding. During the onboarding process a generic provisioned device is associated with 124 its owner and, optionally, meta-data that eases the management or use of the device. These 125 devices may be offboarded when a user no longer desires to be responsible for the device. 126 127 Device attributes directly or indirectly identified by the QR code SHALL be valid when the 128 device is put to use for the first time. Please note that they MAY change throughout the 129 lifecycle of the device, e.g., by changing the JoinEUI over-the-air or using FUOTA to 130 upgrade the firmware and the Device Profile. Addressing issues that may arise from such a 131 change is outside the scope of this document. 132 133