Skip to Content

Changes for page LoRaWAN Capacity

Last modified by Xiaoling on 2023/04/14 11:38
From version 5.2
edited by Xiaoling
on 2022/07/13 11:19
Change comment: There is no comment for this version
To version 5.4
edited by Xiaoling
on 2022/08/09 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
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.
... ... @@ -33,7 +33,7 @@
33 33  
34 34  
35 35  
36 -* DownLink Traffic
36 +* **DownLink Traffic:**
37 37  ** 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.
38 38  
39 39  
... ... @@ -54,6 +54,8 @@
54 54  ** 867.9 - SF7BW125 to SF12BW125
55 55  ** 868.8 - FSK
56 56  
57 +
58 +
57 57  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).
58 58  
59 59  * **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.