Gateway Roaming
- This topic has 2 replies, 3 voices, and was last updated 7 years, 11 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › Gateway Roaming
For LoRaWAN, anyone know how to allow for an end-device to be able to roam from gateway to gateway?
For Over-the-Air Activation, the end-device will have to go through a new join procedure when it enters the coverage of a different gateway. However, how will it know that it has entered the coverage of a new gateway? Is there a procedure for it to connect to the new gateway (such as a list of network names and keys to go through)? What happens if two gateways use the same network name and key?
Did you figure out if this is possible and how to allow devices to roam between conduits?
LoRaWAN does not have any built in specifications for roaming. You can do it at the application level on the node if you have ACKs enabled, but that does have all the downsides of ACKs.
If more than one gateway is required, the typical thing to do would be to use them in packet forwarder mode and use a cloud based network such as actility. You can also run your own join server on an internal network, but we do not have a reference implementation for this type of setup at this time.