[Bluez-users] periodic inquiry mode.

Uichin (Eugene) Lee
2006-12-13T05:52:32Z

Hello,

I need some more helps/comments with periodic inquiry mode. As Marcel
told, I checked the D-Bus based API, which is assumed to be defined in
HCID. I mainly want to use this for P2P applications, i.e., for
content sharing/advertisement application, and thus minimizing peer
discovery latency (or, symmetric discovery latency) is the key issue.

It seems like the actual configuration in HCID is a bit absurd. It
uses inquiry window length of 8, and min and max were set to 16 and 24
respectively; i.e., by multiplying 1.28s, they are 20.48s and 30.72s.
We need to WAIT8*1.28=10.24s to get a response.

It seems like nobody has been working on optimizing the periodic
inquiry mode. I saw a number of papers, but they misunderstood the
units of various parameters, and thus proposed their own schemes,
which are yet another version of this "periodic inquiry mode." Some
analysis work simplified the mode too much, thus failing to reflect
the reality. (I tried, but it seems like it's non-trivial to exactly
model the overall system).

I'm actually working on optimizing the parameter configuration for
"symmetric" peer discovery. What I found is that unless we're using
Bluetooth v1.1, we need inquiry window size at most 2, and the min and
max are set to [0, 2*1.28] (assuming that inquiry scan is adjusted
accordingly). When I tested it with Bluetooth 2.0 (Broadcom chipset),
the latency was less than 3 seconds, which is a pretty well match with
simulation.

Any comments on this?

--
Uichin (Eugene) Lee
Ph.D. Student UCLA CS Dept.