Document

LoRaWAN® Specification v1.0

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

Contents of this Issue

Navigation

Page 58 of 81

LoRaWAN Specification ©2015 LoRa™ Alliance Page 59 of 82 The authors reserve the right to change specifications without notice. 13.2 Slot randomization 1 To avoid systematic collisions or over-hearing problems the slot index is randomized and 2 changed at every beacon period. 3 The following parameters are used: 4 5 DevAddr Device 32 bit network unicast or multicast address pingNb Number of ping slots per beacon period. This must be a power of 2 integer: pingNb = 2 k where 1 <= k <=7 pingPeriod Period of the device receiver wake-up expressed in number of slots: pingPeriod = 2 12 / pingNb pingOffset Randomized offset computed at each beacon period start. Values can range from 0 to (pingPeriod-1) beaconTime The time carried in the field BCNPayload.Time of the immediately preceding beacon frame slotLen Length of a unit ping slot = 30 ms 6 At each beacon period the end-device and the server compute a new pseudo-random offset 7 to align the reception slots. An AES encryption with a fixed key of all zeros is used to 8 randomize: 9 Key = 16 x 0x00 10 Rand = aes128_encrypt(Key, beaconTime | DevAddr | pad16) 11 pingOffset = (Rand[0] + Rand[1]x 256) modulo pingPeriod 12 The slots used for this beacon period will be: 13 pingOffset + N x pingPeriod with N=[0:pingNb-1] 14 The node therefore opens receive slots starting at : 15 First slot Beacon_reserved + pingOffset x slotLen Slot 2 Beacon_reserved + (pingOffset + pingPeriod) x slotLen Slot 3 Beacon_reserved + (pingOffset + 2 x pingPeriod) x slotLen … … If the end-device serves simultaneously a unicast and one or more multicast slots this 16 computation is performed multiple times at the beginning of a new beacon period. Once for 17 the unicast address (the node network address) and once for each multicast group address. 18 In the case where a multicast ping slot and a unicast ping slot collide and cannot be served 19 by the end-device receiver then the end-device should preferentially listen to the multicast 20 slot. If there is a collision between multicast reception slots the FPending bit of the previous 21 multicast frame can be used to set a preference. 22 The randomization scheme prevents a systematic collision between unicast and multicast 23 slots. If collisions happen during a beacon period then it is unlikely to occur again during the 24 next beacon period. 25

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0