From ccbbed037fc1c5389fba9aa6d7828a206b3952b1 Mon Sep 17 00:00:00 2001 From: Stefano Avallone Date: Wed, 8 Jun 2022 10:57:54 +0200 Subject: [PATCH] Update documentation --- CHANGES.md | 1 + RELEASE_NOTES.md | 2 ++ src/wifi/doc/source/wifi-design.rst | 17 ++++++++++++++--- 3 files changed, 17 insertions(+), 3 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index 270852aff..cb8d1e235 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -19,6 +19,7 @@ Changes from ns-3.36 to ns-3.37 ### New API * Added a new attribute **MaxTbPpduDelay** in HeConfiguration for configuring the maximum delay with which a TB PPDU can arrive at the AP after the first TB PPDU in order to be decoded properly. If the delay is higher than **MaxTbPpduDelay**, the TB PPDU is discarded and treated as interference. +* Added new attributes (**AccessReqInterval**, **AccessReqAc** and **DelayAccessReqUponAccess**) to the MultiUserScheduler to allow a wifi AP to coordinate UL MU transmissions even without DL traffic. ### Changes to existing API diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 0b1e1ea83..de838f364 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -16,11 +16,13 @@ Release 3-dev - (lr-wpan) !959 - Add PHY channel page support - (lr-wpan) Adds PAN descriptor, CommandPayload Header and Capability Field +- (wifi) !984 - MultiUserScheduler can request channel access periodically ### Bugs fixed - (wifi) Fix setting of stations' max supported channel width - (wifi) Fix setting TX power for HE TB PPDUs in case AP requested using the max TX power +- (wifi) #521 - UL OFDMA support Release 3.36.1 -------------- diff --git a/src/wifi/doc/source/wifi-design.rst b/src/wifi/doc/source/wifi-design.rst index 555134c86..7762d78a6 100644 --- a/src/wifi/doc/source/wifi-design.rst +++ b/src/wifi/doc/source/wifi-design.rst @@ -936,9 +936,20 @@ Multi-User Scheduler A new component, named **MultiUserScheduler**, is in charge of determining what frame exchange sequence the aggregated AP has to perform when gaining a TXOP (DL OFDMA, UL OFDMA or BSRP Trigger Frame), along with the information needed to perform the selected frame exchange sequence (e.g., -the set of PSDUs to send in case of DL OFDMA). ``MultiUserScheduler`` is an abstract base class. -Currently, the only available subclass is **RrMultiUserScheduler**. By default, no multi-user -scheduler is aggregated to an AP (hence, OFDMA is not enabled). +the set of PSDUs to send in case of DL OFDMA). A TXOP is gained (some time) after requesting +channel access, which is normally done by DCF/EDCA (Txop/QosTxop) if the device has frames to transmit. In order for an AP to coordinate UL MU transmissions even without DL traffic, the +duration of the access request interval can be set to a non-zero value through the +``AccessReqInterval`` attribute. The access request interval is the interval between two +consecutive requests for channel access made by the MultiUserScheduler; such requests are made +independently of the presence of frames in the queues of the AP. It is also possible to set the +Access Category for which the MultiUserScheduler makes requests for channel access (via the +``AccessReqAc`` attribute) and to choose whether the access request interval is measured starting +from the last time the MultiUserScheduler made a request for channel access or from the last time +channel access was obtained by DCF/EDCA (via the ``DelayAccessReqUponAccess`` attribute). + +``MultiUserScheduler`` is an abstract base class. Currently, the only available subclass is +**RrMultiUserScheduler**. By default, no multi-user scheduler is aggregated to an AP (hence, +OFDMA is not enabled). Round-robin Multi-User Scheduler ################################