Issue link: https://read.uberflip.com/i/1539840
Developing LoRaWAN Devices Technical Recommendation TR007-1.1 ©2021-2025 LoRa Alliance ® Page 7 of 28 The authors reserve the right to change documents without notice. 3 Provisioning 173 LoRaWAN end-devices, both Over-the-Air-Activation (OTAA) and Activation-By- 174 Personalization (ABP), need to be properly provisioned for operation on a LoRaWAN 175 compliant network. OTAA devices are provisioned with a DevEUI, JoinEUI, and one or more 176 root keys. ABP devices are provisioned with a DevEUI, DevAddr, and one-time session keys. 177 All end-devices are identified through the DevEUI (device-EUI). All end-devices are also 178 provisioned with a shared secret (or secrets), which are used to authenticate and encrypt 179 frames to and from the network. 180 3.1 Extended-Unique-Identifier (EUI) 181 LoRaWAN uses EUIs to identify various elements of the network architecture. End-devices 182 are identified by a DevEUI and Join Servers (JS) are identified by a JoinEUI. The EUIs in 183 LoRaWAN specifications are always EUI-64 (64-bit EUIs). Other architectural elements may 184 use EUIs as identifiers in the future. 185 An EUI is a globally unique identifier, allocated from a pool of EUIs owned by the organization 186 that has been allocated them by the Institute of Electrical and Electronics Engineers (IEEE). 187 The Organizationally-Unique-Identifier (OUI) forms the most significant 24 bits of the EUI for 188 MAC Address Block Large (MA-L) address blocks. MAC Address Block Medium (MA-M) and 189 MAC Address Block Small (MA-S) address blocks are based on a 36-bit OUI-36. The IEEE is 190 the Registration Authority that assigns the OUI or OUI-36 and the relevant MA-L, MA-M, or 191 MA-S address blocks to an organization. EUIs SHALL be globally unique. 192 Vendors purchase OUIs from the IEEE and then allocate their DevEUI and JoinEUI 193 addresses from the range of addresses that the OUI defines. Vendors can choose whether to 194 keep their company name and address confidential (for an added, annual fee). 195 The consequence of a vendor incorrectly allocating DevEUIs or JoinEUIs (either by not 196 owning an OUI block or improperly allocating it), is that they may collide with EUIs created by 197 the true owner of the OUI block. This can lead to one or both devices failing to properly operate 198 on LoRaWAN networks (this is true for both public and private networks). For this reason, 199 implementors SHALL refrain from using OUIs that they are not entitled to (including random 200 OUIs or other vendors' OUIs), when creating DevEUIs and JoinEUIs. 201 The DevEUI assigned to a LoRaWAN end-device SHALL be immutable, i.e., it should not be 202 possible to change the DevEUI of an end-device. 203 3.2 Device Address (DevAddr) 204 The DevAddr is a short-form address used to aid in the identification of an end-device. It is 205 allocated by the network operator and consists of NWK-ID (network ID derived from NetID) 206 and Host-ID (in the same manner as IP addresses). The DevAddr is 32-bits wide and is not 207 guaranteed to be unique. The NetID is allocated by the LoRa Alliance to member companies 208 in good standing that request one. If the operator does not have a NetID allocated by the LoRa 209 Alliance, they SHALL use NetID 0 or 1, the private NetIDs. 210