# Mobility in LoRaWAN **URL:** \ **Category:** TTN Network and Services\ **Created:** [October 29, 2018, 4:21pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226 "2018-10-29T16:21:53Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [October 29, 2018, 4:21pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/1 "2018-10-29T16:21:53Z")
In many IoT applications, mobility is a major parameter to consider. For example, in healthcare, monitor patient, tracking objects, etc. Is LoRaWAN technology applicable for such applications? Do LoRaWAN supports movement of the node between different Gateways? ---
**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\ **Post date:** [October 29, 2018, 4:23pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/2 "2018-10-29T16:23:34Z")
nodes don’t ‘connect’ to [gateways](https://www.thethingsnetwork.org/docs/gateways/) like wifi So yes… you can move around and gateways in reach will receive and forward the node’s signal… the network backend decides which gateway will answer (when neccesary) ---
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [October 29, 2018, 4:36pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/3 "2018-10-29T16:36:38Z")
In LoRaWAN we have uplink which is the message sent from device to Application server, and downlink which is the message send from Application server to device. How Network server can detects the place of this device during mobility? ---
**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\ **Post date:** [October 29, 2018, 4:44pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/4 "2018-10-29T16:44:48Z")
strongest signal and time of arrival ---
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [October 29, 2018, 4:46pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/5 "2018-10-29T16:46:34Z")
Thank you, so this depend on the next uplink received. ---
**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\ **Post date:** [October 29, 2018, 4:53pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/6 "2018-10-29T16:53:15Z")
uhhh I don’t follow you 🕶 ---
**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\ **Post date:** [October 29, 2018, 5:41pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/7 "2018-10-29T17:41:11Z")
> [@WaelAyoub](#): > > Thank you, so this depend on the next uplink received. LoRaWAN Class A only allows for downlinks after an uplink. For Class B and C another mechanism will be required to select the best gateway. It will be interesting to see how this is/will be implemented in networks supporting Class B and C. ---
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [October 29, 2018, 6:13pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/8 "2018-10-29T18:13:16Z")
> [@kersing](#): > > e best gateway. It w This means that only classes B and C support mobility? Or did each class support mobility using a different mechanism? Does mobility between different network servers support LoRaWAN? Example: If a device of class A, B or C leaves the gateway coverage belonging to the network server X, to an area covered by gateways belonging to the network server Y. Does LoRaWAN support roaming between different network servers? If so, what is the communication mechanism used by this device to get a connection? ---
**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\ **Post date:** [October 29, 2018, 6:41pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/9 "2018-10-29T18:41:10Z")
No. Class A supports mobility. Class B and C will have more issues with mobility. I suggest you read up on the LoRaWAN 1.1 standard. Also check the TTN YouTube channel, specifically watch [https://m.youtube.com/watch?v=ewsXKc3bk1U](https://m.youtube.com/watch?v=ewsXKc3bk1U) ---
**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\ **Post date:** [October 29, 2018, 6:52pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/10 "2018-10-29T18:52:50Z")
> [@kersing](#): > > Class A supports mobility. …because the downlink will happen 1 second (RX1) or 2 seconds (RX2) after an uplink, and in such a short time a device should not move out of reach of the gateway(s) that received the uplink. ---
**Author:** ![WA4OSH](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/wa4osh/32/27554_2.png) [@WA4OSH](https://www.thethingsnetwork.org/forum/u/WA4OSH)\ **Post date:** [October 30, 2018, 9:49am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/11 "2018-10-30T09:49:30Z")
Yes, With LoraWAN, end-devices “join” with the server and not with the gateway. The end-device can be heard by several gateways and that data will be passed on to the server. In Wi-Fi, the mobile station authenticates and associates with one access point at a time. ---
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [November 15, 2018, 2:16pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/12 "2018-11-15T14:16:43Z")
Thank you for your response. Message drop occurs on Gateway or Network server? Example: Case of an End-Device corresponds to Network operator X, and due to the movement, GWs of Network operator Y receives the message. Consider no roaming, are the GWs check for the End-Device identity and drop. Or GWs just forward the message and at Network Server and check on identity is done and the message is dropped? ---
**Author:** ![ThejAravindan](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/t/e19adc/32.png) [@ThejAravindan](https://www.thethingsnetwork.org/forum/u/ThejAravindan)\ **Post date:** [December 20, 2018, 8:27am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/13 "2018-12-20T08:27:06Z")
Usually the network servers are the one that drop the packets, But gateways can also be configured to drop pckets that do not belong to the network. ---
**Author:** ![WaelAyoub](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/97f17d/32.png) [@WaelAyoub](https://www.thethingsnetwork.org/forum/u/WaelAyoub)\ **Post date:** [December 21, 2018, 8:44am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/15 "2018-12-21T08:44:00Z")
Thanks for your clarification. LoRaWAN v1.1 supports two types of roaming, passive and handover. In the case of passive roaming, the LoRaWAN device can move between two or more network operators. This movement is transparent to the LoRaWAN device. Therefore, even if the device is outside the coverage of the home network operator, the device will be able to send the data and the new operator of the network will send the data to the home NS of the device. Of course, the two network operators are in a collaboration between them. In the case of passive roaming, the new NS will function as a gateway for the home NS. In the LoRaWAN device, the device can request an acknowledgment for each uplink. In case this acknowledgment is not received, the device will repeat the uplink. My question: In the case of passive roaming, which server (Home NS or visited NS) returns an acknowledgment (ACK) for the ED upon receiving the uplink ? Or is the ACK returned by GW correspond for the visited NS directly to ED? ---
**Author:** ![keevvee](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/keevvee/32/20484_2.png) [@keevvee](https://www.thethingsnetwork.org/forum/u/keevvee)\ **Post date:** [May 7, 2019, 5:48am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/16 "2019-05-07T05:48:50Z")
Hello. I found this topic relevant for my application. How the LoRaWAN will work if the ‘Thing’ move from one country to another, most likely changing the operator as well? As far as I can see there is no global roaming manifest for the LoRaWAN members. Could someone point me to a proper documentation on this? There are reasons why I look into LoRa rather than Sigfox and cellular. Thanks in advance. ---
**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\ **Post date:** [May 7, 2019, 6:37am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/17 "2019-05-07T06:37:09Z")
see discussion here > [@Different LoRa Servers](https://www.thethingsnetwork.org/forum/t/different-lora-servers/13237/16): > > Thankyou. Just trying to understand this better in light of [this discussion](https://www.thethingsnetwork.org/forum/t/how-can-an-operational-node-be-triggered-to-join-a-different-network/1106/4) on switching between networks. Is the device address autogenerated once for the device, or regenerated each time the device “joins” the network? Do I understand correctly that if I have a device with the same DevEui, AppEui and AppKey registered with another network, and with TTN, both using OTAA: On startup, it will randomly “join” one of the two networks (probably the one with the best reception). While connected t… important is, that the country you enter with your mobile device, has the same **[frequency-plan](https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html)** used in your device, if not, it won’t be heared by the local TTN gateways. [![](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/2/e/2eec5dd7910f10e5b13da374bda20d858262f18d.jpeg "Deployment Scenarios with The Things Enterprise Stack") ](https://www.youtube.com/watch?v=qw3Plxja1Qo) ---
**Author:** ![UdLoRa](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/udlora/32/45330_2.png) [@UdLoRa](https://www.thethingsnetwork.org/forum/u/UdLoRa)\ **Post date:** [May 7, 2019, 7:07am UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/18 "2019-05-07T07:07:48Z")
> [@keevvee](#): > > How the LoRaWAN will work if the ‘Thing’ move from one country to another, most likely changing the operator as well? Differently from cellular networks, it is not obvious that networks are country-specific. If you are on TTN, it is just matter of [having gateways around you](https://www.thethingsnetwork.org/map) (and, as pointed out by BoRRoZ, with the same frequency plan). If you are on a private network, there is some possibility of roaming, in the future, through [PacketBroker](https://www.packetbroker.org). ---
**Author:** ![keevvee](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/keevvee/32/20484_2.png) [@keevvee](https://www.thethingsnetwork.org/forum/u/keevvee)\ **Post date:** [May 7, 2019, 3:48pm UTC](https://www.thethingsnetwork.org/forum/t/mobility-in-lorawan/19226/19 "2019-05-07T15:48:53Z")
Thanks for a quick reply. Will look into this.