14.1 PingSlotInfoReq

  1. With the PingSlotInfoReq command an end-device informs the server of its unicast ping
  2. slot periodicity and expected data rate. This command must only be used to inform the
  3. server of the parameters of a UNICAST ping slot. A multicast slot is entirely defined by the
  4. application and should not use this command.

10

Size (bytes) 1
PingSlotInfoReq Payload Periodicity & data rate

11

Bit# 7 [6:4] [3:0]
Periodicity & data rate RFU Periodicity Data rate
  1. The Periodicity subfield is an unsigned 3 bits integer encoding the ping slot period currently
  2. used by the end-device using the following equation.

14 in seconds

  1. Periodicity = 0 means that the end-device opens a ping slot every second
  2. Periodicity = 7 , every 128 seconds which is the maximum ping period supported by
  3. the LoRaWAN Class B specification.
  4. The Data rate subfield encodes the data rate at which the end-device expects any ping. This
  5. uses the same encoding scheme that the LinkAdrReq command described in the Class A
  6. specification.

©2016 LoRa™ Alliance Page 47 of 70

The authors reserve the right to change specifications without notice.

LoRaWAN Specification

  1. The server needs to be aware of the end-device ping slot periodicity or expected data rate
  2. else Class B downlinks will not happen successfully. For that purpose the PingSlotInfoReq
  3. MAC command must be acknowledged with a PingSlotInfoAns before the device can
  4. switch from class A to Class B. To change its ping slot scheduling or data rate a device

5 should first revert to Class A , send the new parameters through a PingSlotInfoReq

  1. command and get an acknowledge from the server through a PinSlotInfoAns . It can then
  2. switch back to Class B with the new parameters.
  3. This command can be concatenated with any other MAC command in the FHDRFOpt field
  4. as described in the Class A specification frame format.

results matching ""

    No results matching ""