full duplex RF communication is HARD, and completely incompatible with existing stuff. Full duplex also doesn't really help when the problem is more than two stations communicating. And with the mu-mimo mode of operation where the AP is transmitting to multiple receivers at once, 'full duplex' between all the stations is orders of magnatude harder.

The biggest problem with the latest standards is that the per transmit overhead is not shrinking at all. Even as the data bitrates skyrocket, the management bitrates, quiet time requirements, etc remain static.

There would actually be far more benefits from scrapping these timings and re-setting them to match current high-speed capabilities than in going to full-duplex with the current timings in place. Unfortuantly, unless the new systems are on a newly opened frequency band, legacy requirements (existing networks continuing to operate, not just legacy equipment talking to new networks) make this hard. The fact that Wifi networks are not on a dedicated, regulated band and are instead in the 'free for all' bands means that it's not even possible to outlaw old stuff to make room for new stuff.

David Lang


On Sat, 10 Oct 2015, Simon Barber wrote:

The next generation of WiFi is likely to include full duplex - it's about the only physical layer thing left!

Simon

On 10/10/2015 4:12 PM, Jonathan Morton wrote:
On 11 Oct, 2015, at 02:06, Dave Taht <[email protected]> wrote:

I would certainly have preferred a wifi world that instead of all
stations and APs highly contending for bursty access to a single
320mhz channel, we had 160 dedicated, low latency, 5mhz channels, but
that is not what the IEEE has handed us.
Dual radios would be a useful compromise - one 20-40 MHz channel to the AP, one from it. Stations would still need to negotiate for the channel in the uplink direction, but the AP would be able to transmit on the downlink more freely.

_______________________________________________
aqm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/aqm

Reply via email to