F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update documentation

Browse Source
This commit is contained in:
Stefano Avallone
2022-06-08 10:57:54 +02:00
committed by Stefano Avallone
parent a301750492
commit ccbbed037f
3 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGES.md
View File

@@ -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

2
RELEASE_NOTES.md
View File

@@ -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
--------------

17
src/wifi/doc/source/wifi-design.rst
View File

@@ -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
################################