<div dir="ltr"><h3 style="box-sizing:content-box;line-height:1.1;color:rgb(51,51,51);margin:0px 0px 6px;font-size:14px;padding:0px"><span style="font-weight:normal">Hi Jonathan,</span></h3><h3 style="box-sizing:content-box;line-height:1.1;color:rgb(51,51,51);margin:0px 0px 6px;font-size:14px;padding:0px"><span style="font-weight:normal"><br>I think in 802.11ax the AP can schedule STAs to some extent so it looks like that technique is coming soon. It is a bw tradeoff per the RUs per user.</span><br><br></h3><h3 style="box-sizing:content-box;line-height:1.1;color:rgb(51,51,51);margin:0px 0px 6px;font-size:14px;padding:0px">Multi-User Uplink Operation</h3><p style="box-sizing:content-box;margin:0px 0px 6px;padding:0px;line-height:1.25;color:rgb(51,51,51);font-size:12px">To coordinate uplink MU-MIMO or uplink OFDMA transmissions the AP sends a trigger frame to all users. This frame indicates the number of spatial streams and/or the OFDMA allocations (frequency and RU sizes) of each user. It also contains power control information, such that individual users can increase or reduce their transmitted power, in an effort to equalize the power that the AP receives from all uplink users and improve reception of frames from nodes farther away. The AP also instructs all users when to start and stop transmitting. As Figure 10depicts, the AP sends a multi-user uplink trigger frame that indicates to all users the exact moment at which they all start transmitting, and the exact duration of their frame, to ensure that they all finish transmitting simultaneously as well. Once the AP receives the frames from all users, it sends them back a block ACK to finish the operation.</p><p style="box-sizing:content-box;margin:0px 0px 6px;padding:0px;line-height:1.25;color:rgb(51,51,51);font-size:12px;text-align:center"><img width="710" alt="" height="198" src="http://www.ni.com/cms/images/devzone/tut/figure_10_uplink_20160517152439.png" style="box-sizing: content-box; border: none; vertical-align: middle; margin-bottom: 6px;"></p><p style="box-sizing:content-box;margin:0px 0px 6px;padding:0px;line-height:1.25;color:rgb(51,51,51);font-size:12px"> </p><div style="box-sizing:content-box;margin:0px auto;padding:0px;color:rgb(51,51,51);font-size:12px;width:585.594px"><p align="center" style="box-sizing:content-box;margin:0px;padding:0px;line-height:1.25;text-align:center"><em style="box-sizing:content-box"><span style="box-sizing:content-box;font-weight:700">Figure 10.</span> Coordinating uplink multi-user operation</em></p><p align="center" style="box-sizing:content-box;margin:0px;padding:0px;line-height:1.25;text-align:center"><br></p><p align="center" style="box-sizing:content-box;margin:0px;padding:0px;line-height:1.25;text-align:center"><br></p></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 27, 2018 at 12:52 AM Jonathan Morton <<a href="mailto:chromatix99@gmail.com">chromatix99@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> On 27 Aug, 2018, at 10:06 am, Bob McMahon <<a href="mailto:bob.mcmahon@broadcom.com" target="_blank">bob.mcmahon@broadcom.com</a>> wrote:<br>
> <br>
> How can a centralized device predict the many "end stations'" network demand in its time scheduling?<br>
<br>
DOCSIS does it by initially giving stations a tiny window into which to send requests for time, which are granted by the head-end. This introduces some latency. Further requests for time can be appended to a real transmission, which helps efficiency slightly.<br>
<br>
Developing from that model, an AP might initially divide time evenly between stations, allowing them to send single large packets or several small packets without an explicit request for time - this is good for latency. Along with that packet, the station could indicate to the AP that it has a queue of packets waiting, and the AP would take that into account when producing its next schedule. It would also take into account its own queue.<br>
<br>
It may be possible to combine TDM with orthogonal coding. Here the AP monitors the received signal strength of its stations, and instructs them to change power so as to minimise the difference between them. This maximises the SNR for each, should two transmit simultaneously. The tradeoff, of course, is that orthogonal coding permits a reduction in waiting to transmit, but requires a reduction in data rate during the transmission. I'm sure other people have better data on that than I do.<br>
<br>
- Jonathan Morton<br>
<br>
</blockquote></div>