In the nRF Connect SDK v3.3.0 release notes, I noticed that the QoS Channel Survey feature has transitioned from experimental to supported (i.e., production-ready).
From what I understand, it can be enabled via the following Kconfig option:
github.com/.../Kconfig
For one of our client products based on the nRF52833 and using BLE Long Range (Coded PHY S=8), we expect operation in potentially congested RF environments. As such, this feature could be relevant for improving link robustness and channel utilization.
Each device is both central/peripheral. Each central connects to the same device using coded PHY.
Each device transmits two advertisements carrying the same payload:
- A legacy advertisement (on 1M PHY) with an associated scan response, to maintain compatibility with smartphones.
- An extended advertisement on the Coded PHY. Thanks to the increased payload capacity of extended advertising, the data typically placed in the legacy scan response is instead included directly within the extended advertising packet.
Could you clarify:
-
- Whether QoS Channel Survey is fully supported and stable when using Coded PHY (S=8)?
-
Is this feature intended for the central role, the peripheral role, or both? Could you please clarify how it works in detail?
- Any limitations or considerations when using it in long-range configurations?
- Recommended configuration or integration approach for this use case?
- Given that the device is battery-powered, what is the expected impact on power consumption when this feature is enabled?
- From an implementation perspective, is enabling
CONFIG_BT_CTLR_SDC_QOS_CHANNEL_SURVEY=ysufficient, or is additional application-level code required to start, manage, and process the survey data? - Is there a sample i can use as reference?
Thanks,
Alessandro