5

LoRaWAN has a feature called "macro-diversity", which allows more than one GW to demodulate the same uplink frame (UL). Multiple gateways receiving the same UL increases network resiliency and performance (in the face of changing/challenging RF conditions). Thanks to the LoRaWAN Passive Roaming feature, set of multiple GWs demodulating the UL can ...


4

Yes, firmware updates are a big issue with LPWAN networks, because they do not have the downlink capacity to do device-per-device full firmware updates as you can do using e.g.: Bluetooth or WiFi. However, there is a good solution for that leveraging the fact that (1) often new Fw updates are only patches and (2) many devices require the same update. The ...


3

You are right. Thingpark is doing much more than what a simple LNS is supposed to do. It is an advanced LPWAN connectivity platform including Network Server, Join Server, Reliable Multicast Server, Location Solver, Message Broker and many other components. It also provides connectivity for 3GPP devices (NB-IoT, LTE-CatM, etc.) But Thingpark is definitely not ...


3

LoRaWAN end devices have to cope with 2 different types of network connectivity issues: The device temporarily loses network connectivity. This can happen in the following example cases: There is no network coverage at the current location of a moving device There is a temporary network outage at the area of a fixed device. (e.g.: the LoRaWAN Gateway that ...


3

If you use only GPS geolocation or a local BLE location solver, then a cloud service is not required. However if you want to benefit from assisted-GPS, or WiFi geolocation, then the ThingPark Location Engine (cloud based) is required. The main benefit of Assisted-GPS is that the GPS chip will not need to wait to have acquired the full satellite information (...


3

Actually even in OTA (using Join) the LoRaWAN spec separates the network session key (used by the network server to verify checksums and potentially de-ambiguate colliding short DevAddr addresses into their unique devEUIs), and the payload encrypting session key (AppSKey). It is one of its key innovations compared to other MAC layers like 802.15.4. The trick ...


3

Indeed, having a Gateway-LNS backhaul with optimized signaling overhead is key for OPEX saving in case of cellular backhaul. It is even essential for backhaul connectivity over satellite. Actility's ThingPark LRR (LRR stands for Long Range Relay, which is the name of the packet forwarder in the ThingPark platform) has been designed to optimize GW-NS backhaul ...


3

Beyond the traffic generated by the devices of your network there are several other traffic components that generate load on the backhaul connectivity of your gateway. The complete list is the following: Device Traffic: Traffic generated by your network's LoRaWAN devices Traffic generated by foreign network's devices you have roaming agreement with Traffic ...


2

This will probably depend on the protocol used for the backhaul. I have never looked into the details, but I most definitely wouldn't be surprised if some were a lot chattier than others. Taking the example shown on the TTN website for a frame sent via the original Semtech UDP protocol which sends JSON-like data: { "rxpk": { "tmst":...


2

What is the impact of repeated transmissions on the capacity of the LoRaWAN Network? Intuitively, it would seem that repeat transmissions just load the network... and this is what will happen with a basic network server. However it is more subtle, because a high-end network server will optimize jointly power, channel diversity (repeat) and datarate. What you ...


2

We do have a set of REST APIs (named Dx-API) that will help you automate this type of mass-update tasks. From the ThingPark Enterprise UI, you can get access to the APIs from the "Help" menu. For your specific issue, these are the steps you need to follow: Obtain an authentication token (POST /oauth/token) using Dx-Admin API => https://...


1

There are several reasons that may cause a failed join procedure. The typical problems are the following:  The network server does not receive the Join Request because there are no LoRaWAN Gateways in the nighbourhood, or the gateway that is supposed to forward the message has no backhaul connection. The network server receives the Join Request but silently ...


1

Here is the detailed behavior for Abeeway brand trackers. Network timeout monitoring Not receiving any downlink communication from the network is a serious symptom. It can mean that the tracker became isolated from the network, in no longer active in this network, or potentially that the device LoRa radio (or the MCU driver for it) has become unstable. A ...


1

Funny how I had never seen that setting, I always though retransmits only occurred for confirmed packets. That's similar to the Sigfox strategy. Note how the wording is different between e.g. 1.0.3 and 1.1.0, though. Multiple shorter transmissions have several advantages: Each transmission occurs on a different channel If there's a downlink, retransmissions ...


1

LoRaWAN's ADR has a relative long convergence time, because the network server needs to collect data (SNR, packet error rate, etc.) from several uplink messages before it could calculate the ideal data rate and packet repetition parameters. For example: if a device sends UL messages in every 2 min and the NS needs 10 UL messages to calculate the packet error ...


Only top voted, non community-wiki answers of a minimum length are eligible