Skip to Content

Changes for page LoRaWAN Capacity

Last modified by Xiaoling on 2023/04/14 11:38
From version 6.1
edited by Edwin Chen
on 2022/08/22 21:40
Change comment: There is no comment for this version
To version 5.3
edited by Xiaoling
on 2022/08/09 15:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -25,7 +25,7 @@
25 25  
26 26  If we consider using LHT65N as an example to calculate the traffic, we can get a rough idea for how many messages are there:
27 27  
28 -* **Uplink Traffic:**
28 +* Uplink Traffic:
29 29  ** 1~~ several messages for OTAA Join Request. ~/~/ Once the Device joins successful, there is no such traffic.
30 30  ** 1 message to uplink sensor value / every 20 minutes ~/~/ Default uplink interval is 20 minutes for LHT65N. In case user set LHT65N to work in Confirmed Uplink Mode, each uplink might uplink up to 3~~8 messages if the sensor doesn't get any ACK from Server
31 31  ** up to several messages per day.
... ... @@ -32,10 +32,11 @@
32 32  ** So every day, LHT65N might send an average 100 or less messages. Every uplink message last between 200ms to 1 second and they are in different frequencies point ( For example, 868.1Mhz, 868.3Mhz)
33 33  
34 34  
35 -* **DownLink Traffic:**
35 +* DownLink Traffic
36 36  ** several per day for each sensor, Unless end-node sends CONFIRMED UPLINK, in this case, each uplink message will require one downlink message from the server.
37 37  
38 38  
39 +
39 39  == 1.3  Capacity for Gateway ==
40 40  
41 41  
... ... @@ -52,18 +52,18 @@
52 52  ** 867.9 - SF7BW125 to SF12BW125
53 53  ** 868.8 - FSK
54 54  
55 -
56 56  When two sensors send uplink in different frequencies, for example, 868.1 nad 868.3. both packets can arrive at the gateway, and the gateway will forward to LoRaWAN Server. Normally, we can consider the gateway support 8 packets per second ( The packets are of different frequencies).
57 57  
58 58  * **TX channel frequency** is flexible and defined by each downstream from LoRaWAN Server. Please notice when the gateway is in TX mode, RX won't be able to receive packets. So If there are too many downstream in the network. RX capacity will be highly effected.
59 59  
60 60  
61 +
61 61  == 1.4  Conclusion ==
62 62  
63 63  
64 64  When we check the capacity for the LoRaWAN network, we need to check how the sensor work. We can't simply say how many nodes the gateway can support because nodes' uplink frequency is very important.
65 65  
66 -(% class="mark" %)In a network with low transmission frequency end node, for example, several hundred LHT65N, transmit every 20 minutes.  can be easily supported by a LoRaWAN gateway.
67 +In a network with low transmission frequency end node, for example, several hundred LHT65N, transmit every 20 minutes.  can be easily supported by the gateway.
67 67  
68 68  but for a high-frequency application, for example, a tracker sends a message every 3 second, you wil then see packet loss for dozens of units.
69 69