Changes for page Cellular network connection details and tips
Last modified by Kilight Cao on 2024/12/31 16:38
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -482,44 +482,37 @@ 482 482 483 483 = 7. How to reduce data traffic = 484 484 485 -== 7.1 How thegatewaywill consumedata traffic==485 +== 7.1 Reduce Status Uplink Interval == 486 486 487 -Below list the place where the data traffic will use. 488 488 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) 488 +**The gateways will use the data traffic below two places.** 494 494 495 -=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server === 496 496 497 - Whengatewayconnect to LoRaWANserverviaLoRaWAN protocol,besidesthe sensor datauplink/downlink.gateway will still need to:491 +~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink. 498 498 499 -* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below 500 -* 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. 493 +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. 501 501 502 502 [[image:image-20220527155108-13.png]] 503 503 504 504 505 -=== 7.1.2 System Keep Alive data === 506 506 507 - SystemKeepAliveData isused tocheckgateway-network statusandfix possibleissue.Gateway will check every15 secondsand generatetraffic.499 +2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s. 508 508 509 - Baseon15secondspercheck,the data traffic isabout 2M data traffic per day.Users can adjust**KeepaliveInterval**as below.501 +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. 510 510 511 -[[image:image-20220527155 229-15.png||height="511" width="986"]]503 +[[image:image-20220527155358-16.png]] 512 512 505 +System General interface 513 513 514 -=== 7.1.3 Auto update === 515 515 516 - Gateway will check for update every day for new configureor software. User can disablethem by below method.508 +[[image:image-20220527155229-15.png]] 517 517 510 +Keepalive script interval time settings 518 518 519 -=== 7.1.4 Filter unwanted packets === 520 520 521 - Whengatewayconnect to LoRaWAN server via LoRaWAN protocol, Gateway will by default get everypossible LoRaWAN packets and forward to LoRaWAN server. If there are sensors from othersin the same area, such sensor data will alsobe forward to LoRaWAN server ( they will be ignore by the server). This also consume data.513 +== 7.2 Filter unwanted packets == 522 522 515 + 523 523 See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]] 524 524 525 525