Document

LoRaWAN® Specification v1.0

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

Contents of this Issue

Navigation

Page 60 of 81

LoRaWAN Specification ©2015 LoRa™ Alliance Page 61 of 82 The authors reserve the right to change specifications without notice. The server needs to be aware of the end-device ping slot periodicity or expected data rate 1 else Class B downlinks will not happen successfully. For that purpose the PingSlotInfoReq 2 MAC command must be acknowledged with a PingSlotInfoAns before the device can 3 switch from class A to Class B. To change its ping slot scheduling or data rate a device 4 should first revert to Class A , send the new parameters through a PingSlotInfoReq 5 command and get an acknowledge from the server through a PinSlotInfoAns . It can then 6 switch back to Class B with the new parameters. 7 This command can be concatenated with any other MAC command in the FHDRFOpt field 8 as described in the Class A specification frame format. 9 14.2 BeaconFreqReq 10 This command is sent by the server to the end-device to modify the frequency on which this 11 end-device expects the beacon. 12 13 Octets 3 PingSlotChannelReqPay load Frequency 14 The Frequency coding is identical to the NewChannelReq MAC command defined in the 15 Class A. 16 Frequency is a 24bits unsigned integer. The actual beacon channel frequency in Hz is 100 17 x frequ. This allows defining the beacon channel anywhere between 100 MHz to 1.67 GHz 18 by 100 Hz step. The end-device has to check that the frequency is actually allowed by its 19 radio hardware and return an error otherwise. 20 A valid non-zero Frequency will force the device to listen to the beacon on a fixed frequency 21 channel even if the default behavior specifies a frequency hopping beacon (i.e US ISM 22 band). 23 A value of 0 instructs the end-device to use the default beacon frequency plan as defined in 24 the ―Beacon physical layer‖ section. Where applicable the device resumes frequency 25 hopping beacon search. 26 14.3 PingSlotChannelReq 27 This command is sent by the server to the end-device to modify the frequency on which this 28 end-device expects the downlink pings. 29 30 Octets 3 1 PingSlotChannelReq Payload Frequency DrRange 31 The Frequency coding is identical to the NewChannelReq MAC command defined in the 32 Class A. 33 Frequency is a 24bits unsigned integer. The actual ping channel frequency in Hz is 100 x 34 frequ. This allows defining the ping channel anywhere between 100MHz to 1.67GHz by 35 100Hz step. The end-device has to check that the frequency is actually allowed by its radio 36 hardware and return an error otherwise. 37 A value of 0 instructs the end-device to use the default frequency plan. 38

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0