1. What is the proposal?
Non-AP STA indicates its preferred count for sending unsolicited unavailability indications (or BSRP-NTB) to AP in UHR OMP Request (enable/update)
AP may use this value in it's algorithm to set/update the MaxStandaloneDUOBSRP in DUO Parameters field.
2. How does it help AP?
Robust Configuration: AP already must implement an algorithm to determine a suitable value of MaxStandaloneDUOBSRP . Input from non-AP STAs can provide a more complete picture on what is actually required out there before AP determines the value.
User Experience for Residential APs : It can provide the user a much better user experience by catering to the diverse needs of the user as typically a residential AP is likely to service smart home appliances , smartphones , XR devices , wearables and so on. Each of them very diverse- for example:
if AP sets a value that is too small for an XR device , it could have adverse effect on the overall performance of the system. (By not utilizing the benefit of unsolicited unavailabilty information from let's say an XR device, the AP may end up trying to schedule the XR device during its unavailability duration (even ICF is missed ), when in fact it could schedule another device instead)
Enterprise AP: The major issue being discussed from AP perspective seems to be about the load on enterprise APs if all STAs use high value. However the current proposal is only discussing about indicating a preference by non-AP STA which the AP may utilize to set the actual value it wants all the non-AP STAs to use in its BSS. It still does not restrict the AP from setting a common value which can be low or high as deemed fit on the basis of load on the network.
3. How does it help Non-AP STA?
Non-AP STAs are diverse and each has a different need.
A smartphone or XR device that optimizes user experience from throughput, latency and reliability perspective would prefer a larger value of unsolicited unavailability information compared to a home appliance, IoT or wearable.
Sending a preference via UHR OMP Request during enable or update procedure, provides a window for the non- AP STA to indicate its preference to the AP.
Further with some devices indicating low value and some indicating a high value, the AP which has the visibility of such values, can chose a more suitable value for the stations preferring a higher value.
When the station faces any interruptions like low battery, thermal issues or some other errors, the non-AP STA can indicate to AP that it now prefers a lower value. (A station that reduces its transmissions saves on battery, can help reduce thermal issues by reducing unwanted Tx )
Overall system can be enhanced this way if non-AP STA can indicate it's preference to AP and AP makes an informed decision
|
