This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
wiki:wiki3:whatsnew_3x [2020/10/07 16:56] tda |
wiki:wiki3:whatsnew_3x [2020/12/22 11:40] tda |
||
---|---|---|---|
Line 7: | Line 7: | ||
<code> | <code> | ||
+ | Main changes: | ||
- Improving Join procedure : | - Improving Join procedure : | ||
* Adding possibility to configure DevNonce feature (only applicable for OTAA devices) from dashboard and GMS API: activation/de-activation. | * Adding possibility to configure DevNonce feature (only applicable for OTAA devices) from dashboard and GMS API: activation/de-activation. | ||
Line 37: | Line 38: | ||
* Support of Wirnet iStation (with Embedded 3.2.x Software release). | * Support of Wirnet iStation (with Embedded 3.2.x Software release). | ||
* Support of Wirnet iFemtoCell-evolution (with Embedded 3.3.x Software release). | * Support of Wirnet iFemtoCell-evolution (with Embedded 3.3.x Software release). | ||
+ | - Management of 16-channels configuration: | ||
+ | * By default, only 8 channels are configured after CFList within the Join Accept. | ||
+ | * For regions with dynamic channels plans, the end-devices are now informed of the additional 8 channels by NewChannelReq dedicated MAC command(s) | ||
+ | - Timestamping for buffering feature : | ||
+ | * In case of network latency or backhaul disconnection, the message is delayed so the reception timestamps from gateway and WMC can be different. | ||
+ | * Separation between message receive timestamps from gateway and WMC. | ||
+ | * Parameter gwRecvTimeadded to figure out the gateway reception timestamp. | ||
+ | * Both timestamp values (gwRecvTime and recvTime) are displayed on dashboard and pushed to the end user in DataUpDto | ||
+ | - When immediate sending, RX window choice is no more based on the networkMaxDelays, current ping value is now used. | ||
+ | - Add possibility to filter on power-loss alarm. | ||
+ | - Improvement of downlink messages process: | ||
+ | * For classA & classC, downlinks are now sent to the gateways immediately after being provisioned by LNS in order to increase the chance to target the RX1 window. | ||
+ | - Improvement of RX1DROfsset management: | ||
+ | * RX1DROffset=0 (no offset applied on DR) is now used for JOIN Accept. | ||
+ | * RX1DROffset=n (if set) is only applied on subsequent downlinks. | ||
+ | |||
+ | Main restrictions: | ||
+ | Some residual cases of downlinks stucked in Class C. | ||
</code> | </code> | ||