From 54f71946463163b6101fdc6c2544107b40108770 Mon Sep 17 00:00:00 2001 From: "Rich.wu" Date: Sat, 30 Nov 2024 15:26:49 +0800 Subject: [PATCH 1/2] =?UTF-8?q?fix=20(net):=20=E4=BF=AE=E6=94=B9wiki?= =?UTF-8?q?=E4=B8=AD=EF=BC=8C=E4=B8=AD=E6=96=87=E7=89=88=E6=9C=AC=E5=85=B3?= =?UTF-8?q?=E4=BA=8Ersrq=E4=B8=8ESINR=E5=8D=95=E4=BD=8D=E9=94=99=E8=AF=AF?= =?UTF-8?q?=E7=9A=84=E6=83=85=E5=86=B5?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 固件版本: N/A 是否需要文案翻译: 否 --- docs/API_reference/en/iotlib/net.md | 4 ++-- docs/API_reference/zh/iotlib/net.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/API_reference/en/iotlib/net.md b/docs/API_reference/en/iotlib/net.md index 25cb353f..9eeff1e7 100644 --- a/docs/API_reference/en/iotlib/net.md +++ b/docs/API_reference/en/iotlib/net.md @@ -336,9 +336,9 @@ A tuple containing `(GW, LTE)` - Successful execution | --------- | ------------------------------------------------------------ | | `rssi` | Received Signal Strength Indicator. Range: -140 to -44 dBm. 99 indicates unknown or undetectable. | | `rsrp` | Reference Signal Receiving Power. Range: -140 to -44 dBm. 99 indicates unknown or undetectable. | -| `rsrq` | Reference Signal Receiving Quality. Range: -20 to -3 dBm. The higher the value, the better the reference signal received quality. 255 indicates unknown or undetectable. | +| `rsrq` | Reference Signal Receiving Quality. Range: -20 to -3 dB. The higher the value, the better the reference signal received quality. 255 indicates unknown or undetectable. | | `cqi` | Channel Quality Indication. 255 indicates unknown or undetectable. | -| `sinr` | Signal to interference plus Noise Ratio. Range: -10–40 dBm. 255 indicates unknown or undetectable. | +| `sinr` | Signal to interference plus Noise Ratio. Range: -10–40 dB. 255 indicates unknown or undetectable. | diff --git a/docs/API_reference/zh/iotlib/net.md b/docs/API_reference/zh/iotlib/net.md index fdd27ec5..34ae4604 100644 --- a/docs/API_reference/zh/iotlib/net.md +++ b/docs/API_reference/zh/iotlib/net.md @@ -325,9 +325,9 @@ net.getSignal([sinrEnable]) | ------ | ------------------------------------------------------------ | | `rssi` | 接收的信号强度，范围 -140 ~ -44 dBm，99表示未知或者无法检测到 | | `rsrp` | 下行参考信号的接收功率，范围 -140 ~ -44 dBm，99表示未知或者无法检测到 | -| `rsrq` | 下行特定小区参考信号的接收质量，范围 -20 ~ -3 dBm，值越大越好 ,255表示未知或者无法检测到 | +| `rsrq` | 下行特定小区参考信号的接收质量，范围 -20 ~ -3 dB，值越大越好 ,255表示未知或者无法检测到 | | `cqi` | 信道质量，255表示未知或者无法检测到 | -| `sinr` | 干扰信噪比，范围 -10 ~ 40 dBm，255表示未知或者无法检测到 | +| `sinr` | 干扰信噪比，范围 -10 ~ 40 dB，255表示未知或者无法检测到 | -- Gitee From 948d6e210744f32e10701edf4c96f4ce59d25017 Mon Sep 17 00:00:00 2001 From: "QUECTEL\\rich.wu" Date: Thu, 29 May 2025 11:32:49 +0800 Subject: [PATCH 2/2] =?UTF-8?q?fix=20(PSM):=20=E4=BF=AE=E6=94=B9wiki?= =?UTF-8?q?=E4=B8=AD=EF=BC=8C=E4=B8=AD=E6=96=87=E7=89=88=E6=9C=AC=E6=B7=BB?= =?UTF-8?q?=E5=8A=A0=E5=AF=B9=E5=A2=9E=E5=BC=BA=E5=9E=8B=E4=BC=91=E7=9C=A0?= =?UTF-8?q?=E7=9A=84=E8=A1=A5=E5=85=85=E8=AF=B4=E6=98=8E=EF=BC=9B=E8=8B=B1?= =?UTF-8?q?=E6=96=87=E7=89=88=E6=9C=AC=E5=88=A0=E9=99=A4=E5=A2=9E=E5=BC=BA?= =?UTF-8?q?=E5=9E=8B=E4=BC=91=E7=9C=A0=E7=9B=B8=E5=85=B3=E5=86=85=E5=AE=B9?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 固件版本: N/A 是否需要文案翻译: 否 --- docs/Application_guide/en/system/power-consumption.md | 10 ---------- docs/Application_guide/zh/system/power-consumption.md | 8 ++++++-- 2 files changed, 6 insertions(+), 12 deletions(-) diff --git a/docs/Application_guide/en/system/power-consumption.md b/docs/Application_guide/en/system/power-consumption.md index d109db1b..88666324 100644 --- a/docs/Application_guide/en/system/power-consumption.md +++ b/docs/Application_guide/en/system/power-consumption.md @@ -587,16 +587,6 @@ In the example below, PSM cannot be entered because the network environment does Similarly, check the above CP log items. The base station may issue timers with periods different from the set value, and the module will use the values issued by the base station as the actual values. ## Common Application Scenarios -### Sleep Solution for Intercoms - -RRC Fast Release: The network service of intercoms is not fixed and can be triggered randomly. Fast release of RRC ensures that RRC can be quickly released after each walkie-talkie session, allowing the module to enter sleep mode. - -In terms of business logic, try to unify the time periods of periodic tasks or make them multiples of a minimum period, and process as many periodic tasks as possible in a single wake-up session (e.g., heartbeat packets, LED breathing light, positioning, etc.). If the time periods of periodic tasks are not unified, the number of wake-ups will increase, and the proportion of sleep time within the same period will decrease. If wake-ups are too frequent, the module may not able to enter sleep. - -### Sleep Solution for Trackers - -RRC Fast Release: Trackers are location devices, and their positions are not fixed. They periodically perform location updates. Using RRC Fast Release can reduce the duration of RRC connections and thus reduce overall power consumption. - ### Sleep Solution for Meters and Door Contact Sensors PSM: Products such as meters and door contact sensors have long wake-up intervals and are generally not frequently moved. Real-time data is not required. PSM can be used in this scenario. If network connection is not available or the operator does not support PSM, a shutdown + RTC alarm solution can be used. diff --git a/docs/Application_guide/zh/system/power-consumption.md b/docs/Application_guide/zh/system/power-consumption.md index 46014c8c..d00e82e6 100644 --- a/docs/Application_guide/zh/system/power-consumption.md +++ b/docs/Application_guide/zh/system/power-consumption.md @@ -596,12 +596,16 @@ EC600U和BG95支持此引脚，上升沿触发，进入PSM时模组PMIC会默认 同样的，查看以上CPlog条目，基站下发的定时器周期可能不等于设置的值，且模组最终以基站下发的值为准。 ## 常见应用场景 -### 对讲机低功耗方案 +### 增强型休眠模式方案 -RRC快速释放：对讲机的网络业务是不固定的，随机触发的。快速释放RRC能够保证在任何一个随机时间点，都能在对讲后快速释放RRC，从而进入休眠。 +增强型休眠（RRC快速释放）：快速释放RRC能够保证在任何一个随机时间点，快速释放RRC，从而进入休眠。 业务上，将周期性任务的时间周期尽量统一，或均为某个最小周期的整数倍。在单次唤醒中处理尽量多的周期性任务（心跳包、呼吸灯、定位等）。若周期性任务时间不统一，唤醒次数会增加，同一周期内休眠的时间占比会下降。如果唤醒太频繁，甚至无法进入休眠。 +> 增强型休眠模式启用后，在用户发起数据交互时，会给基站产生额外的信令负担，所以可能存在终端被网络侧惩罚不能上线的情况，此功能默认处于关闭状态，客户在使用前需要自行对此风险进行评估。 +> +> 目前仅中国国内支持。 + ### tracker 低功耗方案 -- Gitee