Issue link: https://read.uberflip.com/i/1428383
LoRaWAN 1.0.3 Specification ©2018 LoRa™ Alliance Page 33 of 72 The authors reserve the right to change specifications without notice. 6 End-Device Activation 906 To participate in a LoRaWAN network, each end-device has to be personalized and activated. 907 Activation of an end-device can be achieved in two ways, either via Over-The-Air Activation 908 (OTAA) when an end-device is deployed or reset, or via Activation By Personalization 909 (ABP) in which the two steps of end-device personalization and activation are done as one 910 step. 911 6.1 Data Stored in the End-device after Activation 912 After activation, the following information is stored in the end-device: a device address 913 (DevAddr), an application identifier (AppEUI), a network session key (NwkSKey), and an 914 application session key (AppSKey). 915 6.1.1 End-device address (DevAddr) 916 The DevAddr consists of 32 bits identifies the end-device within the current network. Its format 917 is as follows: 918 Bit# [31..25] [24..0] DevAddr bits NwkID NwkAddr The most significant 7 bits are used as network identifier (NwkID) to separate addresses of 919 territorially overlapping networks of different network operators and to remedy roaming issues. 920 The least significant 25 bits, the network address (NwkAddr) of the end-device, can be 921 arbitrarily assigned by the network manager. 922 6.1.2 Application identifier (AppEUI) 923 The AppEUI is a global application ID in IEEE EUI64 address space that uniquely identifies 924 the entity able to process the JoinReq frame. 925 The AppEUI is stored in the end-device before the activation procedure is executed. 926 6.1.3 Network session key (NwkSKey) 927 The NwkSKey is a network session key specific for the end-device. It is used by both the 928 network server and the end-device to calculate and verify the MIC (message integrity code) 929 of all data messages to ensure data integrity. It is further used to encrypt and decrypt the 930 payload field of a MAC-only data messages. 931 6.1.4 Application session key (AppSKey) 932 The AppSKey is an application session key specific for the end-device. It is used by both 933 the application server and the end-device to encrypt and decrypt the payload field of 934 application-specific data messages. Application payloads are end-to-end encrypted between 935 the end-device and the application server, but they are not integrity protected. That means, a 936 network server may be able to alter the content of the data messages in transit. Network 937 servers are considered as trusted, but applications wishing to implement end-to-end 938 confidentiality and integrity protection are recommended to use additional end-to-end 939 security solutions, which are beyond the scope of this specification. 940 941