Historic archive of defunct list mab-wifi@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Björn Smedman" <bjorn@openias.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: mab-wifi@lists.bufferbloat.net
Subject: Re: [mab-wifi] Initial algorithm simulation results
Date: Fri, 21 Apr 2017 00:16:08 +0200	[thread overview]
Message-ID: <CAGp19xe8agzFMkW76F9ruqVsOxheSs2BdLg-xXZnRpFFGjtyEg@mail.gmail.com> (raw)
In-Reply-To: <CAGp19xf7B0QA+Js6fWV2CN_=-2L9N2rVC-p=ph6kBWUu=LsbXg@mail.gmail.com>

On Sun, Mar 26, 2017 at 10:07 PM, Björn Smedman <bjorn@openias.org> wrote:
> On Sun, Mar 12, 2017 at 8:35 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Björn Smedman <bjorn@openias.org> writes:
>>> I had a quick look at your pybandits code and the attached graph. Some
>>> quick questions: What are your thoughts regarding
>>> dependencies/covariances between "arms"? Will we be able to estimate
>>> those from the data Thomas is collecting?
>>
>> Yeah, hopefully Thomas' data set will allow us to build some assumptions
>> on relations between arms (and check those put forward in prior work). I
>> have also been meaning to go digging for similar WiFi measurement
>> studies in the literature; surely there is bound to be something that
>> evaluates the same kinds of things we are interested in? Are you aware
>> of any?
>
> No I'm not. And a quick google search (for "802.11 conditional
> probability of packet loss") turns up very little. I guess this is
> unfortunate on the one hand, and an opportunity on the other. :P

I was researching something called Mixture of Multivariate Bernoulli
(MMB) models the other day and came across an interesting paper titled
"M&M: Multi-level Markov Model for Wireless Link Simulations" [1].
They model a wireless link (in their case 802.15.4) using Hidden
Markov Models (HMM) for longer term variability, and MMBs for the
short-term variability / uncertainty.

I'm not sure it's discussed in the paper, but one very interesting
aspect of MMBs is that they can model correlation between "arms", and
they allow very efficient computation of conditional distributions
(i.e. answering questions like "if MCS-13 just failed, twice, what is
the probability that MCS-15 will succeed?").

One interesting thought that pops up in this context is that Minstrel
actually fits quite beautifully into an MMB framework. As I understand
Minstrel:

1. For every time slot (of 100 ms or so) we estimate a multivariate
Bernoulli distribution (i.e. the packet success probability) over the
different "arms".

2. We assume that the distribution over the next time slot will be an
"exponentially weighted average" of those estimated over previous time
slots.

3. For (most) transmissions in the next time slot we "pull the arm"
with the highest expected payoff, based on the "weighted average"
distribution computed in 2 above.

Seen in an MMB light I guess the main problems with Minstrel are then
more "implementation issues": (a) the "weighted average" of a number
of multivariate Bernoulli distributions (as computed in 2 above) is
not a multivariate Bernoulli distribution itself, it's an MMB(!); and
(b) when deciding which "arm to pull next" the question is not which
arm had the highest expected payoff when the time slot started, it's
what arm has the highest expected payoff given the result of all the
pulling we've been doing so far in the time slot(!). Adding Bayesian
uncertainty and Thompson sampling to that should not be too hard...

Cheers,

Björn

1. http://andes.ucmerced.edu/papers/Kamthe09b.pdf

      parent reply	other threads:[~2017-04-20 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 12:43 Toke Høiland-Jørgensen
     [not found] ` <CAGp19xdZtvDXXNuo7g8tU52-pPWSL0k4QT8Z8-px3OcACU_Qyw@mail.gmail.com>
2017-03-12 19:35   ` Toke Høiland-Jørgensen
     [not found]     ` <CAGp19xf7B0QA+Js6fWV2CN_=-2L9N2rVC-p=ph6kBWUu=LsbXg@mail.gmail.com>
2017-04-20 22:16       ` Björn Smedman [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGp19xe8agzFMkW76F9ruqVsOxheSs2BdLg-xXZnRpFFGjtyEg@mail.gmail.com \
    --to=bjorn@openias.org \
    --cc=mab-wifi@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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