From: bkil <bkil.hu+Aq@gmail.com>
To: chromatix99@gmail.com
Cc: bob.mcmahon@broadcom.com, bloat-announce@lists.bufferbloat.net,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net, dpreed@deepplum.com,
bloat@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] closing up my make-wifi-fast lab
Date: Thu, 30 Aug 2018 19:12:42 -0000 [thread overview]
Message-ID: <CAPuHQ=G-3-EgNFcpFkoEkUS0+ZyT-xjctw5wd=54JMB5orJ0KQ@mail.gmail.com> (raw)
In-Reply-To: <A2F03A04-E45A-42CB-8DE1-365BE75BF732@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]
Full-duplex still needs some work, but there is definite progress:
http://www.ti.rwth-aachen.de/~taghizadehmotlagh/FullDuplex_Survey.pdf
https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/TR-1.pdf
https://sing.stanford.edu/fullduplex/
https://spectrum.ieee.org/tech-talk/telecom/wireless/new-full-duplex-radio-chip-transmits-and-receives-wireless-signals-at-once
http://fullduplex.rice.edu/research/
On Mon, Aug 27, 2018 at 9:46 PM Jonathan Morton <chromatix99@gmail.com>
wrote:
> > On 27 Aug, 2018, at 10:11 pm, Bob McMahon <bob.mcmahon@broadcom.com>
> wrote:
> >
> > I guess my question is can a WiFi transmitting device rely on primarily
> energy detect and mostly ignore the EDCA probability game and rather search
> for (or predict) unused spectrum per a time interval such that its digital
> signal has enough power per its observed SNR? Then detect "collisions"
> (or, "superposition cases" per the RX not having sufficient SINR) via
> inserting silent gaps in its TX used to sample ED, i.e. run energy detect
> throughout the entire transmission? Or better, no silent gaps, rather
> detect if there is superimposed energy on it's own TX and predict a
> collision (i.e. RX probably couldn't decode its signal) occurred? If
> doable, this seems simpler than having to realize centralized (or even
> distributed) media access algorithms a la, TDM, EDCA with ED, token buses,
> token rings, etc. and not require media access coordination by things like
> APs.
>
> The software might be simpler, but the hardware would need to be
> overspecified to the point of making it unreasonably expensive for consumer
> devices.
>
> Radio hardware generally has a significant TX/RX turnaround time, required
> for the RX deafening circuits to disengage. Without those deafening
> circuits, the receivers would be damaged by the comparatively vast TX power
> in the antenna.
>
> So in practice, it's easier to measure SNR at the receiver, or indirectly
> by observing packet loss by dint of missing acknowledgements returned to
> the transmitter.
>
> - Jonathan Morton
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
[-- Attachment #2: Type: text/html, Size: 3290 bytes --]
next prev parent reply other threads:[~2018-08-30 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 12:26 [Cerowrt-devel] " David P. Reed
2018-08-27 6:00 ` [Cerowrt-devel] [Make-wifi-fast] " Bob McMahon
2018-08-27 6:26 ` Jonathan Morton
2018-08-27 7:06 ` Bob McMahon
2018-08-27 7:52 ` Jonathan Morton
2018-08-27 8:34 ` Bob McMahon
2018-08-27 19:11 ` Bob McMahon
2018-08-27 19:45 ` Jonathan Morton
2018-08-27 19:59 ` Bob McMahon
[not found] ` <alpine.DEB.2.02.1808271431590.2583@nftneq.ynat.uz>
2018-08-28 1:47 ` [Cerowrt-devel] [Bloat] " Bob McMahon
[not found] ` <alpine.DEB.2.02.1808271750490.2583@nftneq.ynat.uz>
2018-08-28 1:56 ` Bob McMahon
2018-08-30 19:12 ` bkil [this message]
2018-08-30 19:17 ` [Cerowrt-devel] " Bob McMahon
2018-08-30 20:36 ` bkil
2018-09-03 19:30 ` Bob McMahon
2018-08-27 7:24 ` [Cerowrt-devel] [Bloat] " Luca Muscariello
2018-08-27 7:39 ` Bob McMahon
2018-08-27 7:52 ` Luca Muscariello
2018-08-30 19:12 ` [Cerowrt-devel] " bkil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPuHQ=G-3-EgNFcpFkoEkUS0+ZyT-xjctw5wd=54JMB5orJ0KQ@mail.gmail.com' \
--to=bkil.hu+aq@gmail.com \
--cc=bloat-announce@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.mcmahon@broadcom.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dpreed@deepplum.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox