Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 32 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 33 of 91 The authors reserve the right to change specifications without notice. Note: The network server uses an AES decrypt operation in ECB 1 mode to encrypt the join-accept message so that the end-device can 2 use an AES encrypt operation to decrypt the message. This way an 3 end-device only has to implement AES encrypt but not AES decrypt. 4 5 Note: Establishing these two session keys allows for a federated 6 network server infrastructure in which network operators are not able 7 to eavesdrop on application data. In such a setting, the application 8 provider must support the network operator in the process of an end- 9 device actually joining the network and establishing the NwkSKey for 10 the end-device. At the same time the application provider commits to 11 the network operator that it will take the charges for any traffic incurred 12 by the end-device and retains full control over the AppSKey used for 13 protecting its application data. 14 The format of the NetID is as follows: The seven LSB of the NetID are called NwkID and 15 match the seven MSB of the short address of an end-device as described before. 16 Neighboring or overlapping networks must have different NwkIDs. The remaining 17 MSB 17 can be freely chosen by the network operator. 18 The DLsettings field contains the downlink configuration: 19 20 Bits 7 6:4 3:0 DLsettings RFU RX1DRoffset RX2 Data rate 21 The RX1DRoffset field sets the offset between the uplink data rate and the downlink data 22 rate used to communicate with the end-device on the first reception slot (RX1). By default 23 this offset is 0.. The offset is used to take into account maximum power density constraints 24 for base stations in some regions and to balance the uplink and downlink radio link margins. 25 The actual relationship between the uplink and downlink data rate is region specific and 26 detailed in the "Physical Layer" section 27 The delay RxDelay follows the same convention as the Delay field in the 28 RXTimingSetupReq command. 29 6.3 Activation by Personalization 30 Under certain circumstances, end-devices can be activated by personalization. Activation by 31 personalization directly ties an end-device to a specific network by-passing the join request 32 - join accept procedure. 33 Activating an end-device by personalization means that the DevAddr and the two session 34 keys NwkSKey and AppSKey are directly stored into the end-device instead of the DevEUI, 35 AppEUI and the AppKey. The end-device is equipped with the required information for 36 participating in a specific LoRa network when started. 37 Each device should have a unique set of NwkSKey and AppSKey. Compromising the keys 38 of one device shouldn't compromise the security of the communications of other devices. 39 The process to build those keys should be such that the keys cannot be derived in any way 40 from publicly available information (like the node address for example). 41

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1