Bluetooth
Baseband (BB) Part B Version 1.0B
During our creation, modeling and validation of this protocol,
we discovered problems and holes, which we fixed based on our
understanding. Below is a list of those assumptions.
- The current model has four (4) timer errors that are caused
by interaction. No solution has been decided on yet. An example
of one of the timer problems is for the Tinquiryscan, which is
required every so often. What happens when the BB is in a state
like Page Scan when this timer expires? What should be done?
--Should it save the event and try act on it when current procedures
are complete?
--Should it act on the event then and interrupt the current procedure?
--Should this even happen?
--Something else?
- Currently the model only models a single device's protocol.
- Due to the lack of easily defined interfaces between BB and its
other processes (i.e. RF, LMP, L2CAP, and audio), it was necessary
to define signals of our own.
- Due to the very nature of the BB protocol much of it is
implementation dependent, which makes writing an SDL just an
exercise and not a standard.
Project Contact
For inquiries regarding this project, contact
David Cypher
|