Running Azure Sphere OS version 20.12 Update 1 on Avnet MT3620 module.
When connected stably to an AP the Sphere OS periodically performs WiFi background scanning without properly informing the AP that it is going off channel.
This means the AP will continue sending frames to the Sphere OS even though it is no longer on the same channel.
Per the 802.11 specification the Sphere OS must use the Power Management bit of the Null Data Frame to indicate that is is going offline temporarily for background scanning so that the AP will buffer frames until the Sphere OS comes back online to the AP's channel.
The Sphere OS does not appear to ever set the Power Management bit.
Problems:
The Sphere OS does not adhere to the 802.11 specification because the connected AP is not properly informed when WiFi background scanning occurs. The Sphere OS should send an 802.11 Null Data Frame with the Power Management bit set before changing channels to background scan. Upon returning to the AP channel the Sphere OS should send another Null Data Frame with the Power Management bit cleared. The Sphere OS does not appear to ever set the Power Management bit.
The Sphere Application must be allowed to programmatically enable and disable WiFi background scanning (both broadcast and directed) when connected to an AP to minimize unscheduled communication interruptions and latency, and reduce unnecessary background transmissions.
What additional information can I provide to aid in the resolution of these problems?