alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2025-08-07 20:00:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'docs/fix_some_coexist_doc_issue' into 'master'

Browse Source 
docs(coex): update rf coexistence documents

See merge request espressif/esp-idf!36974
This commit is contained in:
Wang Meng Yang
2025-02-25 19:33:14 +08:00
parent d7222cc89e 9f0c8e7bfc
commit 909d81283d
2 changed files with 132 additions and 120 deletions
Download Patch File Download Diff File Expand all files Collapse all files

126
docs/en/api-guides/coexist.rst
View File

@@ -16,32 +16,32 @@ Supported Coexistence Scenario for {IDF_TARGET_NAME}
.. table:: Supported Features of Wi-Fi and BLE Coexistence
+-------+--------+-----------+-----+------------+-----------+----------+
| |BLE |
+ +-----+------------+-----------+----------+
| |Scan |Advertising |Connecting |Connected |
+-------+--------+-----------+-----+------------+-----------+----------+
| Wi-Fi |STA |Scan |Y |Y |Y |Y |
+ + +-----------+-----+------------+-----------+----------+
| | |Connecting |Y |Y |Y |Y |
+ + +-----------+-----+------------+-----------+----------+
| | |Connected |Y |Y |Y |Y |
+ +--------+-----------+-----+------------+-----------+----------+
| |SOFTAP |TX Beacon |Y |Y |Y |Y |
+ + +-----------+-----+------------+-----------+----------+
| | |Connecting |C1 |C1 |C1 |C1 |
+ + +-----------+-----+------------+-----------+----------+
| | |Connected |C1 |C1 |C1 |C1 |
+ +--------+-----------+-----+------------+-----------+----------+
| |Sniffer |RX |C1 |C1 |C1 |C1 |
+ +--------+-----------+-----+------------+-----------+----------+
| |ESP-NOW |RX |S |S |S |S |
+ + +-----------+-----+------------+-----------+----------+
| | |TX |Y |Y |Y |Y |
+-------+--------+-----------+-----+------------+-----------+----------+
+-------+--------+-----------+-----+------------+----------+
| |BLE |
+ +-----+------------+----------+
| |Scan |Advertising |Connected |
+-------+--------+-----------+-----+------------+----------+
| Wi-Fi |STA |Scan |Y |Y |Y |
+ + +-----------+-----+------------+----------+
| | |Connecting |Y |Y |Y |
+ + +-----------+-----+------------+----------+
| | |Connected |Y |Y |Y |
+ +--------+-----------+-----+------------+----------+
| |SOFTAP |TX Beacon |Y |Y |Y |
+ + +-----------+-----+------------+----------+
| | |Connecting |C1 |C1 |C1 |
+ + +-----------+-----+------------+----------+
| | |Connected |C1 |C1 |C1 |
+ +--------+-----------+-----+------------+----------+
| |Sniffer |RX |C1 |C1 |C1 |
+ +--------+-----------+-----+------------+----------+
| |ESP-NOW |RX |S |S |S |
+ + +-----------+-----+------------+----------+
| | |TX |Y |Y |Y |
+-------+--------+-----------+-----+------------+----------+
.. only:: esp32
.. only:: SOC_WIFI_SUPPORTED and SOC_BT_CLASSIC_SUPPORTED
.. table:: Supported Features of Wi-Fi and Classic Bluetooth (BT) Coexistence
@@ -97,24 +97,26 @@ Supported Coexistence Scenario for {IDF_TARGET_NAME}
.. table:: Supported Features of IEEE 802.15.4 (Thread / Zigbee) and BLE Coexistence
+-----------------+-------------+-----+------------+-----------+----------+
| |BLE |
+ +-----+------------+-----------+----------+
| |Scan |Advertising |Connecting |Connected |
+-----------------+-------------+-----+------------+-----------+----------+
| Thread / Zigbee |Scan |X |Y |Y |Y |
+ +-------------+-----+------------+-----------+----------+
| |Router |X |Y |Y |Y |
+ +-------------+-----+------------+-----------+----------+
| |End Device |C1 |Y |Y |Y |
+-----------------+-------------+-----+------------+-----------+----------+
+-----------------+-------------+-----+------------+----------+
| |BLE |
+ +-----+------------+----------+
| |Scan |Advertising |Connected |
+-----------------+-------------+-----+------------+----------+
| Thread / Zigbee |Scan |X |Y |Y |
+ +-------------+-----+------------+----------+
| |Router |X |Y |Y |
+ +-------------+-----+------------+----------+
| |End Device |C1 |Y |Y |
+-----------------+-------------+-----+------------+----------+
.. note::
- Y: supported and the performance is stable
- C1: supported but the performance is unstable
- X: not supported
- S: supported and the performance is stable in STA mode, otherwise not supported
.. list::
- Y: supported and the performance is stable
- C1: supported but the performance is unstable
- X: not supported
:SOC_WIFI_SUPPORTED: - S: supported and the performance is stable in STA mode, otherwise not supported
.. only:: SOC_IEEE802154_SUPPORTED
@@ -168,44 +170,48 @@ The RF resource allocation mechanism is based on priority. As shown below, Wi-Fi
Coexistence Policy
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Coexistence Period and Time Slice
""""""""""""""""""""""""""""""""""""""""
.. only:: SOC_WIFI_SUPPORTED and SOC_BT_SUPPORTED
.. only:: esp32
Coexistence Period and Time Slice
""""""""""""""""""""""""""""""""""""""""
Wi-Fi, BT, and BLE have their fixed time slice to use the RF. A coexistence period is divided into 3 time slices in the order of Wi-Fi, BT, and BLE. In the Wi-Fi slice, Wi-Fi's request to the coexistence arbitration module will have higher priority. Similarly, BT/BLE can enjoy higher priority at their own time slices. The duration of the coexistence period and the proportion of each time slice are divided into four categories according to the Wi-Fi status:
.. only:: SOC_BLE_SUPPORTED and SOC_BT_CLASSIC_SUPPORTED
Wi-Fi, BT, and BLE have their fixed time slice to use the RF. A coexistence period is divided into 3 time slices in the order of Wi-Fi, BT, and BLE. In the Wi-Fi slice, Wi-Fi's request to the coexistence arbitration module will have higher priority. Similarly, BT/BLE can enjoy higher priority at their own time slices. The duration of the coexistence period and the proportion of each time slice are divided into four categories according to the Wi-Fi status:
.. only:: SOC_WIFI_SUPPORTED and SOC_BLE_SUPPORTED and not esp32
.. only:: not SOC_BT_CLASSIC_SUPPORTED
Wi-Fi and BLE have their fixed time slice to use the RF. In the Wi-Fi time slice, Wi-Fi will send a higher priority request to the coexistence arbitration module. Similarly, BLE can enjoy higher priority at their own time slice. The duration of the coexistence period and the proportion of each time slice are divided into four categories according to the Wi-Fi status:
Wi-Fi and BLE have their fixed time slice to use the RF. In the Wi-Fi time slice, Wi-Fi will send a higher priority request to the coexistence arbitration module. Similarly, BLE can enjoy higher priority at their own time slice. The duration of the coexistence period and the proportion of each time slice are divided into four categories according to the Wi-Fi status:
.. list::
.. list::
:esp32: 1) IDLE status: the coexistence of BT and BLE is controlled by Bluetooth module.
:SOC_WIFI_SUPPORTED and SOC_BLE_SUPPORTED and not esp32: 1) IDLE status: RF module is controlled by Bluetooth module.
#) CONNECTED status: the coexistence period starts at the Target Beacon Transmission Time (TBTT) and is more than 100 ms.
#) SCAN status: Wi-Fi slice and coexistence period are longer than in the CONNECTED status. To ensure Bluetooth performance, the Bluetooth time slice will also be adjusted accordingly.
#) CONNECTING status: Wi-Fi slice is longer than in the CONNECTED status. To ensure Bluetooth performance, the Bluetooth time slice will also be adjusted accordingly.
:SOC_BLE_SUPPORTED and SOC_BT_CLASSIC_SUPPORTED: 1) IDLE status: the coexistence of BT and BLE is controlled by Bluetooth module.
:not SOC_BT_CLASSIC_SUPPORTED: 1) IDLE status: RF module is controlled by Bluetooth module.
#) CONNECTED status: the coexistence period starts at the Target Beacon Transmission Time (TBTT) and is more than 100 ms.
#) SCAN status: Wi-Fi slice and coexistence period are longer than in the CONNECTED status. To ensure Bluetooth performance, the Bluetooth time slice will also be adjusted accordingly.
#) CONNECTING status: Wi-Fi slice is longer than in the CONNECTED status. To ensure Bluetooth performance, the Bluetooth time slice will also be adjusted accordingly.
According to the coexistence logic, different coexistence periods and time slice strategies will be selected based on the Wi-Fi and Bluetooth usage scenarios. A Coexistence policy corresponding to a certain usage scenarios is called a "coexistence scheme". For example, the scenario of Wi-Fi CONNECTED and BLE CONNECTED has a corresponding coexistence scheme. In this scheme, the time slices of Wi-Fi and BLE in a coexistence period each account for 50%. The time allocation is shown in the following figure:
According to the coexistence logic, different coexistence periods and time slice strategies will be selected based on the Wi-Fi and Bluetooth usage scenarios. A Coexistence policy corresponding to a certain usage scenarios is called a "coexistence scheme". For example, the scenario of Wi-Fi CONNECTED and BLE CONNECTED has a corresponding coexistence scheme. In this scheme, the time slices of Wi-Fi and BLE in a coexistence period each account for 50%. The time allocation is shown in the following figure:
.. figure:: ../../_static/coexist_wifi_connected_and_ble_connected_time_slice.png
:align: center
:alt: Time Slice Under the Status of Wi-Fi CONNECTED and BLE CONNECTED
:figclass: align-center
.. figure:: ../../_static/coexist_wifi_connected_and_ble_connected_time_slice.png
:align: center
:alt: Time Slice Under the Status of Wi-Fi CONNECTED and BLE CONNECTED
:figclass: align-center
Time Slice Under the Status of Wi-Fi CONNECTED and BLE CONNECTED
Time Slice Under the Status of Wi-Fi CONNECTED and BLE CONNECTED
.. only:: SOC_IEEE802154_SUPPORTED
The IEEE 802.15.4 module requests RF resources based on pre-assigned priorities. Normal receive operations are assigned the lowest priority, meaning Wi-Fi and BLE will take over the RF whenever needed, while 802.15.4 can only receive during the remaining time. Other 802.15.4 operations, such as transmitting or receiving ACKs and transmitting or receiving at given time, are assigned higher priorities. However, their access to RF ultimately depends on the priorities of Wi-Fi and BLE operations at that moment.
Dynamic Priority
""""""""""""""""""""""""""""
.. only:: SOC_WIFI_SUPPORTED and SOC_BT_SUPPORTED
The coexistence module assigns varying priorities to different statuses of each module, and these priorities are dynamic. For example, in every N BLE Advertising events, there is always one event with high priority. If a high-priority BLE Advertising event occurs within the Wi-Fi time slice, the right to use the RF may be preempted by BLE.
Dynamic Priority
""""""""""""""""""""""""""""
The coexistence module assigns varying priorities to different statuses of each module, and these priorities are dynamic. For example, in every N BLE Advertising events, there is always one event with high priority. If a high-priority BLE Advertising event occurs within the Wi-Fi time slice, the right to use the RF may be preempted by BLE.
.. only:: SOC_WIFI_SUPPORTED