Document

TS001-1.0.4 LoRaWAN® L2 1.0.4 Specification

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

Contents of this Issue

Navigation

Page 86 of 89

LoRaWAN ® L2 1.0.4 Specification © 2020 LoRa Alliance ® Page 87 of 90 The authors reserve the right to change specifications without notice. Require the support of at least one multicast group 2625 Define interpretation of Fpending in Class B downlinks for unicast and multicast 2626 PingSlotInfoAns is defined 2627 Beacon Frame formats defined for Spreading Factors SF8 to SF12 2628 Beacon transmission randomization for loosely synched gateways 2629 Add a time precision field Prec to the Beacon to describe the precision of the source 2630 gateway's timing and a description was added for its use 2631 Defined the Lat / Lng fields for the GPS coordinate fields of the beacon 2632 Clarified the downlink route update requirements on cell change 2633 Clarify priority of Class A downlinks over Class C downlinks 2634 Clarify unicast and multicast RXC parameters and logical model 2635 Update all of the Informative Examples 2636 MAC commands from the Network may only be sent on Class A downlinks. Note that 2637 regular uplink traffic is expected in class B & C. 2638 Added a minimum power control range 2639 For Class B and Class C confirmed downlinks, ACKs shall not occur after a timeout. 2640 Enforcing duty cycle limit after each uplink frame with Toff 2641 Modify PingSlotChannelReq acknowledge mechanism (repeated in all uplinks, until 2642 next class A downlink, f.k.a. sticky answer) 2643 After confirmed Class A downlink, NS shall wait for an uplink before sending a Class B 2644 or Class C confirmed DL. 2645 Recommend to send as soon as possible RxParamSetupAns (class C-enabled), and 2646 PingSlotChannelAns. 2647 2648 2649

Articles in this issue

view archives of Document - TS001-1.0.4 LoRaWAN® L2 1.0.4 Specification