You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NS should persistently queue ApplicationUp per application, while it is not available.
Why do we need this?
For the AS to recover from missed upstream events, including join-accepts with new session information, uplink messages as well as downlink queue invalidations with the new FCntDown to use in LoRaWAN 1.0.x.
What is already there? What do you see now?
NS drops upstream messages.
What is missing? What do you want to see?
A persistent queue per application UID. Once any AS instance links an application with the UID, NS flushes the queue to AS before it sends normal messages.
How do you propose to implement this?
Persistent queue in NS.
Can you do this yourself and submit a Pull Request?
Can review
The text was updated successfully, but these errors were encountered:
Summary:
Replaces #439
NS should persistently queue ApplicationUp per application, while it is not available.
Why do we need this?
For the AS to recover from missed upstream events, including join-accepts with new session information, uplink messages as well as downlink queue invalidations with the new
FCntDown
to use in LoRaWAN 1.0.x.What is already there? What do you see now?
NS drops upstream messages.
What is missing? What do you want to see?
A persistent queue per application UID. Once any AS instance links an application with the UID, NS flushes the queue to AS before it sends normal messages.
How do you propose to implement this?
Persistent queue in NS.
Can you do this yourself and submit a Pull Request?
Can review
The text was updated successfully, but these errors were encountered: