Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 79 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 80 of 91 The authors reserve the right to change specifications without notice. 18 Class C: Continuously listening end-device 1 The end-devices implanting the Class C option are used for applications that have sufficient 2 power available and thus do not need to minimize reception time. 3 Class C end-devices cannot implement Class B option. 4 The Class C end-device will listen with RX2 windows parameters as often as possible. The 5 end-device listens on RX2 when it is not either (a) sending or (b) receiving on RX1, 6 according to Class A definition. To do so, it will open a short window on RX2 parameters 7 between the end of the uplink transmission and the beginning of the RX1 reception window 8 and it will switch to RX2 reception parameters as soon as the RX1 reception window is 9 closed; the RX2 reception window will remain open until the end-device has to send another 10 message. 11 Note: There is not specific message for a node to tell the server that it 12 is a Class C node. It is up to the application on server side to know that 13 it manages Class C nodes based on the contract passed during the 14 join procedure. 15 18.1 Second receive window duration for Class C 16 Class C devices implement the same two receive windows as Class A devices, but they do 17 not close RX2 window until they need to send again. Therefore they may receive a downlink 18 in the RX2 window at nearly any time, including downlinks sent for the purpose of MAC 19 command or ACK transmission. A short listening window on RX2 frequency and data rate is 20 also opened between the end of the transmission and the beginning of the RX1 receive 21 window. 22 Transmit RX1 RX2 RX2 Transmit On Air Time RECEIVE_DELAY1 RECEIVE_DELAY2 Extends to next uplink 23 24 Figure 16: Class C end-device receive slot timing. 25 18.2 Class C Multicast downlinks 26 Similarly to Class B, Class C devices may receive multicast downlink frames. The multicast 27 address and associated network session key and application session key must come from 28 the application layer. The same limitations apply for Class C multicast downlink frames: 29 They are not allowed to carry MAC commands, neither in the FOpt field, nor in the 30 payload on port 0 because a multicast downlink does not have the same 31 authentication robustness as a unicast frame. 32 The ACK and ADRACKReq bits must be zero. The MType field must carry the value 33 for Unconfirmed Data Down. 34 The FPending bit indicates there is more multicast data to be sent. Given that a 35 Class C device keeps its receiver active most of the time, the FPending bit does not 36 trigger any specific behavior of the end-device. 37

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1