Document

LoRaWAN® Specification v1.0

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

Contents of this Issue

Navigation

Page 32 of 81

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

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0