Skip to Content

Changes for page LoRaWAN Capacity

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

Summary

Details

Page properties
Content
... ... @@ -14,9 +14,9 @@
14 14  
15 15  LoRa transmission is a broadcast protocol. There is no fix connection between gateway and end node.
16 16  
17 -For uplink steam: Each End node will broadcast the uplink message and all-around gateways will get this message and forward to LoRaWAN Server.
17 +(% style="color:blue" %)**For uplink steam: **(%%) Each End node will broadcast the uplink message and all-around gateways will get this message and forward to LoRaWAN Server.
18 18  
19 -For Downlink Stream: Gateway will get instruction from LoRaWAN server and then broadcast this message to LoRaWAN End Node.
19 +(% style="color:blue" %)**For Downlink Stream:**(%%)  Gateway will get instruction from LoRaWAN server and then broadcast this message to LoRaWAN End Node.
20 20  
21 21  
22 22  
... ... @@ -30,6 +30,9 @@
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 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 +
34 +
35 +
33 33  * DownLink Traffic
34 34  ** 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.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  
41 41  A general LoRaWAN gateway such as LPS8N uses a multi-channel LoRaWAN Concentrator. which supports 10 rx channels and 1 tx channel.
42 42  
43 -* RX channel is used to received Uplink from Sensor. User can pre-set max 10 different frequencies on rx. For example, in EU868, 8 channels are use, they are as below:
46 +* **RX channel** is used to received Uplink from Sensor. User can pre-set max 10 different frequencies on rx. For example, in EU868, 8 channels are use, they are as below:
44 44  ** 868.1 - SF7BW125 to SF12BW125
45 45  ** 868.3 - SF7BW125 to SF12BW125 and SF7BW250
46 46  ** 868.5 - SF7BW125 to SF12BW125
... ... @@ -51,10 +51,9 @@
51 51  ** 867.9 - SF7BW125 to SF12BW125
52 52  ** 868.8 - FSK
53 53  
54 -
55 55  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).
56 56  
57 -* 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 +* **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.
58 58  
59 59  
60 60