Document

LoRaWAN® Specification v1.0.1

Issue link: https://read.uberflip.com/i/1428386

Contents of this Issue

Navigation

Page 29 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 30 of 91 The authors reserve the right to change specifications without notice. 6 End-Device Activation 1 To participate in a LoRaWAN network, each end-device has to be personalized and 2 activated. 3 Activation of an end-device can be achieved in two ways, either via Over-The-Air 4 Activation (OTAA) when an end-device is deployed or reset, or via Activation By 5 Personalization (ABP) in which the two steps of end-device personalization and activation 6 are done as one step. 7 6.1 Data Stored in the End-device after Activation 8 After activation, the following information is stored in the end-device: a device address 9 (DevAddr), an application identifier (AppEUI), a network session key (NwkSKey), and an 10 application session key (AppSKey). 11 6.1.1 End-device address (DevAddr) 12 The DevAddr consists of 32 bits identifies the end-device within the current network. Its 13 format is as follows: 14 Bit# [31..25] [24..0] DevAddr bits NwkID NwkAddr The most significant 7 bits are used as network identifier (NwkID) to separate addresses of 15 territorially overlapping networks of different network operators and to remedy roaming 16 issues. The least significant 25 bits, the network address (NwkAddr) of the end-device, can 17 be arbitrarily assigned by the network manager. 18 6.1.2 Application identifier (AppEUI) 19 The AppEUI is a global application ID in IEEE EUI64 address space that uniquely identifies 20 the application provider (i.e., owner) of the end-device. 21 The AppEUI is stored in the end-device before the activation procedure is executed. 22 6.1.3 Network session key (NwkSKey) 23 The NwkSKey is a network session key specific for the end-device. It is used by both the 24 network server and the end-device to calculate and verify the MIC (message integrity code) 25 of all data messages to ensure data integrity. It is further used to encrypt and decrypt the 26 payload field of a MAC-only data messages. 27 6.1.4 Application session key (AppSKey) 28 The AppSKey is an application session key specific for the end-device. It is used by both 29 the application server and the end-device to encrypt and decrypt the payload field of 30 application-specific data messages. It is also used to calculate and verify an application- 31 level MIC that may be included in the payload of application-specific data messages. 32 6.2 Over-the-Air Activation 33 For over-the-air activation, end-devices must follow a join procedure prior to participating in 34 data exchanges with the network server. An end-device has to go through a new join 35 procedure every time it has lost the session context information. 36

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1