diff --git a/docs/Application_guide/en/network-comm/nic/cellular/application.md b/docs/Application_guide/en/network-comm/nic/cellular/application.md index 783d22c6f15228765cf6323dbb0213b45a0ec98c..dc0b3df4b1750c8b397deca48b84bf84073f63f8 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/application.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/application.md @@ -2,6 +2,18 @@ This document will provide detailed instructions on how to configure and use NICs for network communication in different scenarios, as well as provide sample code for reference. +Users can refer to the following table to choose and view the configuration method for the corresponding scenario: + +| Corresponding scenario | Reference section | +| ------------------------------------------------------------ | ------------------------------------------------------------ | +| The SIM card can access the Internet without configuring an APN. Users only need to determine that the module has successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network. | [Automatically Activate One NIC at Startup Without Configuring APN](./application.html#Automatically Activate One NIC at Startup Without Configuring APN) | +| The SIM card needs to be configured with APN before it can access the Internet. Users only need to determine that the module is successfully connected to the Internet and directly use socket/mqtt/http to directly access the public network or a private network. | [Automatically Activate One NIC at Startup and Configure APN](./application.html#Automatically Activate One NIC at Startup and Configure APN) | +| The SIM card needs to be configured with APN before it can access the Internet. For user business, it is necessary to automatically activate multiple network cards after the module is powered on. For example, one network card is used to access a public network, and another network card is used to access a private network. | [Automatically Activate Multiple NICs at Startup and Configure APN](./application.html#Automatically Activate Multiple NICs at Startup and Configure APN) | +| The SIM card needs to be configured with an APN before it can access the Internet. Users do not want the module to automatically activate the network card when it is powered on. Instead, they want the user to actively activate a certain network card when needed, and then deactivate the network card after the network service is completed. | [Manually Activate One NIC](./application.html#Manually Activate One NIC) | +| The SIM card needs to be configured with APN before it can access the Internet. For user business, the module needs to activate multiple network cards. For example, one network card is used to access a public network, and another network card is used to access a private network. And users hope that they can control the activation of multiple network cards when needed, instead of having the module automatically complete it when it is powered on. | [Manually Activate Multiple NICs](./application.html#Manually Activate Multiple NICs) | + + + ## Automatically Activate One NIC at Startup Without Configuring APN This scenario refers to the situation where the module has not configured any APN for any NIC and automatically activates one NIC at startup. There are two situations as follows. @@ -61,6 +73,8 @@ if __name__ == '__main__': main() ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_default_nic_no_apn.py) + In this scenario, you do not configure any APN for the cellular NIC, but the module can still communicate normally after startup. However, there is a major issue: you may find that the application program written according to the above example can run normally in some places but fail in others, especially in countries or regions outside China. The specific manifestation is that the return value of the `checkNet.waitNetworkReady()` is not `(3,1)`. The module fails to register on the network due to the lack of APN configuration. Whether the cellular NIC can be successfully activated when no APN is configured depends on whether the automatic APN correction feature of the current base station is enabled. The automatic APN correction feature means that when the UE attaches to the network, if you do not configure an APN for the cellular NIC or configure an incorrect APN, the base station will automatically send a correct APN to the device and allow the UE to attach successfully. @@ -158,6 +172,8 @@ if __name__ == '__main__': ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_default_nic_set_apn.py) + ## Automatically Activate Multiple NICs at Startup and Configure APN @@ -325,6 +341,8 @@ if __name__ == '__main__': main() ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_multiple_nic_set_apn.py) + @@ -458,6 +476,10 @@ if __name__ == '__main__': main() ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_manually_activate_one_nic_set_apn.py) + + + ## Manually Activate Multiple NICs The scenario is similar to that of "Automatically Activate Multiple NICs at Startup and Configure APN". The only difference is that you need to disable the automatic activation at startup, and then manually activate the NICs when needed. @@ -642,6 +664,8 @@ if __name__ == '__main__': main() ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_manually_activate_multiple_nic_set_apn.py) + ## Configure DNS Server Address diff --git a/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md b/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md index 17afccd9fa65c253287e9c6cd7f8f46e087734a7..4d0a45ac85c52c07571fdc8d079b83738feada98 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/common-concepts.md @@ -10,6 +10,20 @@ For users, many types of external networks can be accessed, such as [Internet](h All operators use specific APNs (Access Point Names), which are usually pre-configured on your SIM card, but you may need to adjust them manually if necessary. +For APN configuration interface description, please refer to the following sections: + +[APN configuration interface description](https://python.quectel.com/doc/API_reference/en/iotlib/dataCall.html#APN-Configuration-and-Retrieval) + +APN configuration example: + +* [Automatically Activate One NIC at Startup and Configure APN](https://python.quectel.com/doc/Application_guide/en/network-comm/nic/cellular/application.html#Automatically-Activate-One-NIC-at-Startup-and-Configure-APN) + +* [Automatically Activate Multiple NICs at Startup and Configure APN](https://python.quectel.com/doc/Application_guide/en/network-comm/nic/cellular/application.html#Automatically-Activate-Multiple-NICs-at-Startup-and-Configure-APN) + +* [Manually Activate One NIC](https://python.quectel.com/doc/Application_guide/en/network-comm/nic/cellular/application.html#Manually-Activate-One-NIC) + +* [Manually Activate Multiple NICs](https://python.quectel.com/doc/Application_guide/en/network-comm/nic/cellular/application.html#Manually-Activate-Multiple-NICs) + ### Confirm Which APN to Use All operators have their own APNs. Generally, for regular SIM cards (also known as public network cards), their APNs are publicly available and can be found online or by contacting the corresponding operator. However, for IoT SIM cards or other specialized network cards, you need to contact the corresponding operator to confirm which APN to use. @@ -96,7 +110,7 @@ When measuring signal strength and signal quality, high signal strength values o ### RSSI -RSSI (Received Signal Strength Indicator) refers to the total power (in dBm) of all received signals, including pilot signals, data signals, neighboring interference signals, and background noise signals. The parameter range of RSSI varies in different network modes, but a larger value indicates better signal strength. +[RSSI](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Received Signal Strength Indicator) refers to the total power (in dBm) of all received signals, including pilot signals, data signals, neighboring interference signals, and background noise signals. The parameter range of RSSI varies in different network modes, but a larger value indicates better signal strength. RSSI is usually a relative value, and its measurement is highly dependent on the receiving device. Therefore, the measurement standards for RSSI may not be completely uniform for different devices. The RSSI measurement standards provided below are for reference only: @@ -114,8 +128,7 @@ RSSI is usually a relative value, and its measurement is highly dependent on the ### CSQ -CSQ (Carrier Signal Quality) refers to the signal strength, used to indicate RSSI level. Range: 0 – 3. Larger values indicate better signal strength. If the CSQ value is less than 6, the terminal may have difficulty establishing network communication. There is a corresponding relationship between CSQ and RSSI: - +[CSQ](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#%3Ccode%3Enet.csqQueryPoll%3C/code%3E) (Carrier Signal Quality) refers to the signal strength, used to indicate RSSI level. Range: 0 – 3. Larger values indicate better signal strength. If the CSQ value is less than 6, the terminal may have difficulty establishing network communication. There is a corresponding relationship between CSQ and RSSI: $$ CSQ = (RSSI + 113) / 2 $$ @@ -132,7 +145,7 @@ $$ ### RSRP -RSRP (Reference Signal Received Power) refers to the received power of reference signals. It is the average power of the signals received on all REs (resource elements) carrying reference signals in a symbol. It reflects the path loss intensity in the current channel and is used for cell coverage measurements, cell selection, and re-selection. Range: -140 dBm to -44 dBm. Larger values indicate better signal strength. +[RSRP](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Reference Signal Received Power) refers to the received power of reference signals. It is the average power of the signals received on all REs (resource elements) carrying reference signals in a symbol. It reflects the path loss intensity in the current channel and is used for cell coverage measurements, cell selection, and re-selection. Range: -140 dBm to -44 dBm. Larger values indicate better signal strength. Please note that RSRP is a concept introduced in LTE, so it is used to measure LTE network signal strength, equivalent to RSCP in WCDMA networks. The following RSRP standards are for reference only: @@ -149,7 +162,7 @@ Please note that RSRP is a concept introduced in LTE, so it is used to measure L ### RSRQ -RSRQ (Reference Signal Received Quality) refers to the quality of the received reference signals. It reflects the signal-to-noise ratio and interference levels of the current channel. Range: -20 dB to -3 dB. Larger values indicate better signal strength. RSRQ is a concept introduced in LTE, so it is used to measure LTE network signal strength +[RSRQ](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Reference Signal Received Quality) refers to the quality of the received reference signals. It reflects the signal-to-noise ratio and interference levels of the current channel. Range: -20 dB to -3 dB. Larger values indicate better signal strength. RSRQ is a concept introduced in LTE, so it is used to measure LTE network signal strength RSRQ is the ratio of RSRP to RSSI, but adjusted by a coefficient since their measurements may be based on different bandwidths, i.e. RSRQ = N*RSRP/RSSI. @@ -164,7 +177,7 @@ The following RSRQ standards are for reference only: ### RSCP -RSCP (Receive Signal Code Power) refers to the received power of the code signals. It is a concept in UMTS networks and represents the power measured on a specific physical channel by the receiver. It is used as an indication of signal strength, handover criteria, and path loss calculation in downlink power control. Range: -120 dBm to -25 dBm. Larger values indicate better signal strength. +[RSCP](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Receive Signal Code Power) refers to the received power of the code signals. It is a concept in UMTS networks and represents the power measured on a specific physical channel by the receiver. It is used as an indication of signal strength, handover criteria, and path loss calculation in downlink power control. Range: -120 dBm to -25 dBm. Larger values indicate better signal strength. The following RSCP standards are for reference only: @@ -180,7 +193,7 @@ The following RSCP standards are for reference only: ### SINR -SINR (Signal to Interference plus Noise Ratio) refers to the ratio of the received useful signal strength to the received interference signal strength. It is an important parameter for measuring signal quality in mobile network communication. Range: 0 dB to 40 dB. +[SINR](https://python.quectel.com/doc/API_reference/en/iotlib/net.html#Get-Detailed-Signal-Strength) (Signal to Interference plus Noise Ratio) refers to the ratio of the received useful signal strength to the received interference signal strength. It is an important parameter for measuring signal quality in mobile network communication. Range: 0 dB to 40 dB. The following SINR standards are for reference only: diff --git a/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md b/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md index 50c76b14c7ee0d144aecf227bdbedcc956c7c196..973f45a13862524e7a1c692dd0480ad53cf7c500 100644 --- a/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md +++ b/docs/Application_guide/en/network-comm/nic/cellular/exception-handling.md @@ -232,6 +232,8 @@ if __name__ == '__main__': main() ``` +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_network_exception_handle_set_apn.py) + #### No Network Coverage from SIM Card Operator @@ -504,4 +506,6 @@ def main(): if __name__ == '__main__': main() -``` \ No newline at end of file +``` + +The above sample code download link:[Download](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_network_exception_handle.py) \ No newline at end of file diff --git a/docs/Application_guide/en/network-comm/sim/README.md b/docs/Application_guide/en/network-comm/sim/README.md index fde0bab4ff0d225f13189ac170b93e1f0f0c77f4..111d2fadc290cdcb1c8eb155fa44fb390dec92dc 100644 --- a/docs/Application_guide/en/network-comm/sim/README.md +++ b/docs/Application_guide/en/network-comm/sim/README.md @@ -50,8 +50,8 @@ It is important to note that the use of vSIM requires support from network opera All QuecPython modules support card SIMs, and some platforms' modules support eSIMs with customized versions. QuecPython does not support vSIM. Currently, the platforms that support customized eSIMs are as follows: -| Platform | Supported Module Models | -| ------------- | ------------------------------- | -| Quectel 8910 | EC200U/EC600U/EG912U/EG915U series | -| Quectel ASR1803S | EC200A series | -| Qualcomm | BG95M1/BG95M3/BG95M8 | \ No newline at end of file +| Supported Module Models | +| ------------------------------- | +| EC200U/EC600U/EG912U/EG915U series | +| EC200A series | +| BG95M1/BG95M3/BG95M8 | \ No newline at end of file diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/application.md b/docs/Application_guide/zh/network-comm/nic/cellular/application.md index 29ddd7c91d3ec48ef01a0ef4d4a9f710de781055..39dee54bfebbb6043d235959225d5b5d1016ef00 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/application.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/application.md @@ -2,6 +2,16 @@ 本文将根据用户的不同场景需求，来详细说明如何配置，以及在对应场景下，如何使用网卡进行网络通信，并给出示例代码供用户参考。 +用户可参考如下场景来选择查看对应场景的配置： + +| 应用场景 | 参考章节 | +| ------------------------------------------------------------ | ------------------------------------------------------------ | +| SIM卡无需配置APN就可以上网，用户只需要判断模组联网成功后，直接使用socket/mqtt/http等直接访问公共网络。 | [开机自动激活一路网卡且没有配置APN](./application.html#开机自动激活一路网卡且没有配置APN) | +| SIM卡需要配置APN才可以上网，用户只需要判断模组联网成功后，直接使用socket/mqtt/http等直接访问公共网络或者某个专用网络。 | [开机自动激活一路网卡且配置APN](./application.html#开机自动激活一路网卡且配置APN) | +| SIM卡需要配置APN才可以上网，用户业务上需要模组开机后自动激活多路网卡，比如一路用来访问公共网络，另一路用来访问某个专用网络。 | [开机自动激活多路网卡且配置APN](./application.html#开机自动激活多路网卡且配置APN) | +| SIM卡需要配置APN才可以上网，用户不希望模组开机就自动激活网卡，而是希望在需要的时候，由用户主动激活某一路网卡，然后在网络业务完成后再对网卡进行去激活。 | [手动激活一路网卡](./application.html#手动激活一路网卡) | +| SIM卡需要配置APN才可以上网，用户不希望模组开机就自动激活多路网卡，而是希望在需要的时候，由用户主动激活多路网卡，比如一路用来访问公共网络，另一路用来访问某个专用网络，然后在网络业务完成后再对网卡进行去激活。 | [手动激活多路网卡](./application.html#手动激活多路网卡) | + ## 开机自动激活一路网卡且没有配置APN @@ -63,7 +73,7 @@ if __name__ == '__main__': main() ``` - +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_default_nic_no_apn.py) 这种场景下，用户没有为任何一路蜂窝无线网卡配置过APN，模组开机后也能正常进行网络通信。但是会存在一个很大的问题：用户很可能会发现，按照上述示例编写的应用程序，在有的地方可以正常运行，有的地方不能正常运行，尤其是在中国以外的其他国家，大概率不能正常运行，具体表现就是`checkNet.waitNetworkReady`方法返回值不是`(3,1)`。原因是因为没有配置APN导致模组网络注册失败。 @@ -162,6 +172,8 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_default_nic_set_apn.py) + ## 开机自动激活多路网卡且配置APN @@ -331,6 +343,8 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_activate_multiple_nic_set_apn.py) + ## 手动激活一路网卡 @@ -463,6 +477,8 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_manually_activate_one_nic_set_apn.py) + ## 手动激活多路网卡 @@ -652,6 +668,8 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_socket_manually_activate_multiple_nic_set_apn.py) + ## 配置DNS服务器地址 diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/common-concepts.md b/docs/Application_guide/zh/network-comm/nic/cellular/common-concepts.md index 56dcaf5efea41e12facb28e8bce69175ed408118..c95797fe7ef872407fb5a8fae93c73a7b41da950 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/common-concepts.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/common-concepts.md @@ -10,6 +10,16 @@ APN（Access Point Name，接入点名称）指一种网络接入技术，是终 所有运营商都使用特定的APN（Access Point Name，接入点名称）。这通常是您的SIM卡预先配置的，但必要时，您需手动进行调整。 +关于APN的配置接口说明，可以参考QuecPython官方网站Wiki说明的[APN配置与获取功能](https://python.quectel.com/doc/API_reference/zh/iotlib/dataCall.html#APN%E9%85%8D%E7%BD%AE%E4%B8%8E%E8%8E%B7%E5%8F%96%E5%8A%9F%E8%83%BD)部分，具体的配置使用示例，可以参考如下几个部分： + +* [开机自动激活一路网卡且配置APN](./application.html#开机自动激活一路网卡且没有配置APN) + +* [开机自动激活多路网卡且配置APN](./application.html#开机自动激活多路网卡且配置APN) + +* [手动激活一路网卡](./application.html#手动激活一路网卡) + +* [手动激活多路网卡](./application.html#手动激活多路网卡) + ### 确认用什么APN 所有运营商都有自己的APN，一般普通的SIM卡（也叫公网卡），其APN都是公开的，可以在网络上查询到，或者直接联系对应运营商咨询。而对于物联网卡或者其他一些专网卡，需要用户联系对应运营商去确认应该使用什么APN。 @@ -95,7 +105,7 @@ MCC（Mobile Country Code）和 MNC（Mobile Network Code）是在移动通信 ### RSSI -RSSI（Received Signal Strength Indicator）指接收的所有信号的总功率（单位dBm），包括导频信号、数据信号、邻区干扰信号和底噪信号等。RSSI的参数范围在不同的网络制式中有所不同，但是值越大，表示信号强度越好。 +[RSSI](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96%E8%AF%A6%E7%BB%86%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)（Received Signal Strength Indicator）指接收的所有信号的总功率（单位dBm），包括导频信号、数据信号、邻区干扰信号和底噪信号等。RSSI的参数范围在不同的网络制式中有所不同，但是值越大，表示信号强度越好。 RSSI通常是一个相对值，它的测量和接收设备有很大的关系。因此对于不同设备，其RSSI的衡量标准并不是完全统一的，因此下面我们提供的RSSI衡量标准仅作为一个参考： @@ -109,11 +119,13 @@ RSSI通常是一个相对值，它的测量和接收设备有很大的关系。 | -80 <= RSSI < -70 | 好 | 信号很好，适合高清视频、实时语音等应用。 | | RSSI > -70 | 非常好 | 信号非常好，适合高速数据传输和对网络质量要求较高的应用场景。 | +一般RSSI的值小于-90dBm，说明网络信号比较差了，模组可能就无法进行正常的网络通信。 +
### CSQ -CSQ表示信号强度，是用来指示RSSI强度的参数，取值范围是0~31，数值越大表示信号强度越好。若CSQ值小于6，终端基本无法进行网络通信。CSQ和RSSI之间是有对应关系的，其对应关系如下： +[CSQ](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96CSQ%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)表示信号强度，是用来指示RSSI强度的参数，取值范围是0~31，数值越大表示信号强度越好。若CSQ值小于6，终端基本无法进行网络通信。CSQ和RSSI之间是有对应关系的，其对应关系如下： $$ CSQ=(RSSI+113)/2 $$ @@ -131,7 +143,7 @@ $$ ### RSRP -RSRP（Reference Signal Received Power）指参考信号接收功率。是在某个符号内承载参考信号的所有RE(资源粒子)上接收到的信号功率的平均值。反应的是当前信道的路径损耗强度，用于小区覆盖的测量和小区的选择以及重选。RSRP的取值范围是-140dBm ~ -44dBm，值越大越好。 +[RSRP](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96%E8%AF%A6%E7%BB%86%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)（Reference Signal Received Power）指参考信号接收功率。是在某个符号内承载参考信号的所有RE(资源粒子)上接收到的信号功率的平均值。反应的是当前信道的路径损耗强度，用于小区覆盖的测量和小区的选择以及重选。RSRP的取值范围是-140dBm ~ -44dBm，值越大越好。 需要注意的是，RSRP是在LTE中才引入的概念，也就是说RSRP是用来衡量LTE网络信号强度的参数。相当于WCDMA网络中的RSCP参数。下面提供的RSRP参数衡量标准仅作为一个参考： @@ -150,7 +162,7 @@ RSRP（Reference Signal Received Power）指参考信号接收功率。是在某 ### RSRQ -RSRQ（Reference Signal Received Quality）指参考信号接收质量。表示当前信道质量的信噪比和干扰水平。其取值范围是-20 dB ~ -3 dB，值越大越好。RSRQ是在LTE中才引入的概念，也就是说RSRQ是用来衡量LTE网络信号强度的参数。 +[RSRQ](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96%E8%AF%A6%E7%BB%86%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)（Reference Signal Received Quality）指参考信号接收质量。表示当前信道质量的信噪比和干扰水平。其取值范围是-20 dB ~ -3 dB，值越大越好。RSRQ是在LTE中才引入的概念，也就是说RSRQ是用来衡量LTE网络信号强度的参数。 RSRQ是RSRP和RSSI的比值，但是因为两者测量所基于的带宽可能不同，会用一个系数来调整，即 RSRQ = N*RSRP/RSSI。 @@ -169,7 +181,7 @@ RSRQ是RSRP和RSSI的比值，但是因为两者测量所基于的带宽可能 ### RSCP -RSCP（Receive Signal CodePower）指接收信号码功率。它是UMTS网络系统中的概念，表示接收器在特定物理信道上测量的功率。它在下行链路功率控制中用作信号强度的指示、切换标准以及计算路径损耗。RSCP的取值范围通常在-120 dBm到-25 dBm之间。 +[RSCP](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96%E8%AF%A6%E7%BB%86%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)（Receive Signal CodePower）指接收信号码功率。它是UMTS网络系统中的概念，表示接收器在特定物理信道上测量的功率。它在下行链路功率控制中用作信号强度的指示、切换标准以及计算路径损耗。RSCP的取值范围通常在-120 dBm到-25 dBm之间。 下面提供的RSCP参数衡量标准仅作为一个参考： @@ -185,7 +197,7 @@ RSCP（Receive Signal CodePower）指接收信号码功率。它是UMTS网络系 ### SINR -SINR（Signal to Interference plus Noise Ratio）指信号与干扰加噪声比，即接收到的有用信号的强度和接收到的干扰信号强度的比值。它是用来表示移动网络通信中信号质量的重要参数。SINR的单位是dB，范围一般是-10dB到40dB。 +[SINR](https://python.quectel.com/doc/API_reference/zh/iotlib/net.html#%E8%8E%B7%E5%8F%96%E8%AF%A6%E7%BB%86%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6)（Signal to Interference plus Noise Ratio）指信号与干扰加噪声比，即接收到的有用信号的强度和接收到的干扰信号强度的比值。它是用来表示移动网络通信中信号质量的重要参数。SINR的单位是dB，范围一般是-10dB到40dB。 下面提供的SINR参数衡量标准仅作为一个参考： diff --git a/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md b/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md index 7f3e56e21653d5b4c6d0a30fae115df5eb314bf5..e182ac0c1b64a1f1375dd0240c47b29e66b8fac8 100644 --- a/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md +++ b/docs/Application_guide/zh/network-comm/nic/cellular/exception-handling.md @@ -236,6 +236,8 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_network_exception_handle_set_apn.py) + #### 无SIM卡所属运营商的网络覆盖 @@ -510,3 +512,4 @@ if __name__ == '__main__': main() ``` +上述示例代码下载链接：[示例下载](https://github.com/QuecPython/examples/blob/main/network-comm/nic/cellular/example_network_exception_handle.py) \ No newline at end of file diff --git a/docs/Application_guide/zh/network-comm/sim/README.md b/docs/Application_guide/zh/network-comm/sim/README.md index 7b4a69c33098cda923353a6a8451ce2f972b6f10..513f1c19cbc96db2b631c50770896a1374634c33 100644 --- a/docs/Application_guide/zh/network-comm/sim/README.md +++ b/docs/Application_guide/zh/network-comm/sim/README.md @@ -60,9 +60,9 @@ vSIM，全称为Virtual SIM，即虚拟SIM卡。它的核心思想是把物理SI QuecPython所有模组都支持卡片式SIM卡，部分平台的模组支持eSIM，但是需要定制版本才能支持，QuecPython不支持vSIM。目前，支持定制eSIM的平台如下： -| 平台 | 支持定制eSIM的模组型号 | -| ------------ | ------------------------------- | -| 展锐8910平台 | EC200U/EC600U/EG912U/EG915U系列 | -| ASR1803S平台 | EC200A系列 | -| 高通平台 | BG95M1/BG95M3/BG95M8 | +| 支持定制eSIM的模组型号 | +| ------------------------------- | +| EC200U/EC600U/EG912U/EG915U系列 | +| EC200A系列 | +| BG95M1/BG95M3/BG95M8 |