Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 64 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 65 of 91 The authors reserve the right to change specifications without notice. 12 Downlink Ping frame format (Class B option) 1 12.1 Physical frame format 2 A downlink Ping uses the same format as a Class A downlink frame but might follow a 3 different channel frequency plan. 4 12.2 Unicast & Multicast MAC messages 5 Messages can be "unicast" or "multicast". Unicast messages are sent to a single end-device 6 and multicast messages are sent to multiple end-devices. All devices of a multicast group 7 must share the same multicast address and associated encryption keys. The LoRaWAN 8 Class B specification does not specify means to remotely setup such a multicast group or 9 securely distribute the required multicast key material. This must either be performed during 10 the node personalization or through the application layer. 11 12.2.1 Unicast MAC message format 12 The MAC payload of a unicast downlink Ping uses the format defined in the Class A 13 specification. It is processed by the end-device in exactly the same way. The same frame 14 counter is used and incremented whether the downlink uses a Class B ping slot or a Class A 15 "piggy-back" slot. 16 12.2.2 Multicast MAC message format 17 The Multicast frames share most of the unicast frame format with a few exceptions: 18 They are not allowed to carry MAC commands, neither in the FOpt field, nor in the 19 payload on port 0 because a multicast downlink does not have the same 20 authentication robustness as a unicast frame. 21 The ACK and ADRACKReq bits must be zero. The MType field must carry the value 22 for Unconfirmed Data Down. 23 The FPending bit indicates there is more multicast data to be sent. If it is set the 24 next multicast receive slot will carry a data frame. If it is not set the next slot may or 25 may not carry data. This bit can be used by end-devices to evaluate priorities for 26 conflicting reception slots. 27 28

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1