Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Edwin

Content

...	...	@@ -215,7 +215,6 @@
215	215	Once the Ethernet of the Wi-Fi network is unavailable where the gateway network will switch to a Cell network from Ethernet or Wi-Fi.
216	216
217	217
218		-
219	219	**Enable Cellular and connect Ethernet at the same time**
220	220
221	221	ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
...	...	@@ -483,37 +483,45 @@
483	483
484	484	= 7. How to reduce data traffic =
485	485
486		-== 7.1 Reduce Status Uplink Interval ==
	485	+== 7.1 How the gateway will consume data traffic ==
487	487
	487	+Below list the place where the data traffic will use.
488	488
489		-**The gateways will use the data traffic below two places.**
	489	+* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
	490	+* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
	491	+* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
	492	+* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
	493	+* Auto update ( Software auto update, can be disabled)
490	490
491	491
492		-~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.
	496	+(% class="wikigeneratedid" %)
	497	+=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
493	493
494		-For this case, by default, the gateway will uplink self-status to the LoRaWAN server per the 30s. the users can adjust the interval time.
	499	+When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
495	495
	501	+* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
	502	+* Check LoRaWAN server status every 5 seconds to see if there is valid downlink command to sensors. We don't provide WEB UI option to modify this time, because the modify of this settings will lead to fail on OTAA Join and Downlink commands.
	503	+
496	496	[[image:image-20220527155108-13.png]]
497	497
498	498
	507	+=== 7.1.2 System Keep Alive data ===
499	499
500		-2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.
	509	+System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
501	501
502		-For this case, We have monitored the loss of data traffic, which is the loss of 2M data traffic per day. the users can adjust the interval time following screenshots.
	511	+Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
503	503
504		-[[image:image-20220527155358-16.png]]
	513	+[[image:image-20220527155229-15.png]]
505	505
506		-System General interface
507	507
	516	+=== 7.1.3 Auto update ===
508	508
509		-[[image:image-20220527155229-15.png]]
	518	+Gateway will check for update every day for new configure or software. User can disable them by below method.
510	510
511		-Keepalive script interval time settings
512	512
	521	+=== 7.1.4 Filter unwanted packets ===
513	513
514		-== 7.2 Filter unwanted packets ==
515	515
516		-
517	517	See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
518	518
519	519