ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: sandeep suresh <sandeep.suresh@yahoo.co.in>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Bonjour mDNS broacast can be lost during BT-WLAN coexistence schemes?
Date: Sun, 27 Mar 2016 16:43:29 +0000 (UTC)	[thread overview]
Message-ID: <1860079637.618245.1459097009016.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: 1860079637.618245.1459097009016.JavaMail.yahoo.ref@mail.yahoo.com

Dear Experts,
WiFi-BT Coexistence:
To let wireless LAN systems coexist with Bluetooth system, a hardware Packet Traffic Arbiter (PTA) scheme is used. Here PTA is based on 2-wire coexistence , BT_ACTIVE and WL_ACTIVE. When BT wants to use the medium, it will assert the BT_ACTIVE line, during which WLAN cannot perform any transactions. When WLAN is in client mode, during this assertion period waiting for a packet from WLAN router (AP) to be received , WLAN packet will be lost !!! Let us call this window during which WiFi being stomped ?by BT as stomping window. WLAN device in client mode considered here is based on AR9287 chipset and let us call this as Apple accessory?
Bonjour discovery:Apple devices connect to the same WiFi router to which the Apple accessory is also connected. Apple device is also connected in WiFi client mode. ?In order to determine other clients (Apple compatible) in the same network, it performs Bonjour discovery which is based on mDNS broadcast.
Concern/Query:-?The mDNS query is a broadcast query received from Apple device and sent by the WiFi AP to the WiFi network (to which the apple accessory is also connected) only once. The period of reception of this broadcast query can coincide with the stomping window. Hence the broadcast query can be lost by Apple accessory. This might result in discovery, pair verify (later) from apple devices to fail. Apple devices implement a back-off strategy and as per this the next discovery will be after 10s of minutes. During this long period the WiFi client based apple accessory will be offline!!!!?
Is the understanding and concern correct? If so, how can this be solved via ath9k drivers and/or settings in WiFi AP?
Regards
Sandeep
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160327/eb6300be/attachment.htm 

       reply	other threads:[~2016-03-27 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1860079637.618245.1459097009016.JavaMail.yahoo.ref@mail.yahoo.com>
2016-03-27 16:43 ` sandeep suresh [this message]
2016-03-27 22:43   ` [ath9k-devel] Bonjour mDNS broacast can be lost during BT-WLAN coexistence schemes? Adrian Chadd
2016-03-27 23:27     ` Dave Taht
2016-03-29  4:22     ` sandeep suresh
2016-03-29  8:24       ` [ath9k-devel] Fw: " sandeep suresh
2016-03-29 20:29       ` [ath9k-devel] " Adrian Chadd
2016-03-30  1:40         ` sandeep suresh
2016-03-30 20:02           ` Adrian Chadd
2016-03-31  1:33             ` sandeep suresh
2016-03-31 22:04               ` Adrian Chadd
2016-04-01  1:32                 ` sandeep suresh
2016-04-01 20:28                   ` Adrian Chadd
2016-04-02  2:52                     ` sandeep suresh
2016-04-05  4:33                       ` sandeep

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=1860079637.618245.1459097009016.JavaMail.yahoo@mail.yahoo.com \
    --to=sandeep.suresh@yahoo.co.in \
    --cc=ath9k-devel@lists.ath9k.org \
    /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;
as well as URLs for NNTP newsgroup(s).