Document

ERRATA_L2_1_0_4_D2D

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

Contents of this Issue

Navigation

Page 2 of 2

ERRATA Allow Downlink TransmissionsThe LoRa Alliance © 2021 3 Analogously, a first downlink with FCntDown=0 sent by a Network Server to an ABP or an OTAA end-device after a successful Join procedure SHALL be accepted by the end-device, provided the MIC field is valid. Frame counters are 32 bits wide. The FCnt field SHALL correspond to the least-significant 16 bits of the 32-bit frame counter (i.e., FCntUp for data frames sent uplink and FCntDown for data frames sent downlink). The end-device SHALL NOT reuse the same FCntUp value with the same application or network session keys, except for retransmission. The end-device SHALL NOT process any retransmission of the same downlink frame. Subsequent retransmissions SHALL be ignored without being processed. ************************ Start of proposed change for 9.3 ************************* 9.3 Downlink Ping Frames A downlink ping frame uses the same format as a Class A downlink frame but might follow a different channel frequency or data rate plan. Frames can be unicast or multicast. Unicast frames are sent to a single end-device, whereas multicast frames are sent to multiple end-devices. All end-devices of a multicast group SHALL share the same multicast address and associated encryption keys. A Class B-capable end- device SHALL support at least one multicast group and an end-device SHALL NOT transmit using a multicast address. ************************* End of proposed change for 9.3 ****************************

Articles in this issue

view archives of Document - ERRATA_L2_1_0_4_D2D