From: Ricky Soh <rickysoh@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Bluetooth headset enquiries
Date: Thu, 30 Sep 2004 14:38:02 +0800 [thread overview]
Message-ID: <db972f43040929233863680ff2@mail.gmail.com> (raw)
Dear all,
I would like to clear some doubts about the Bluetooth headset profile.
Please assist in anyway possible.
1. After both the headset and AG (Audio Gateway) are paired, if there
are no need for active communication, the headset will go into PARK
mode but stay in sync with the AG. At this point, is there any
transmission between the devices, or is the headset just purely
listening to the master (AG) for the clock sequence? What is the
rate/frequency that the master sent a signal to the headset to
indicate its clock and frequency sequence at this time?
2. What is the encryption key for SCO packets? Is it the same Kc
derived from the E0 cipher scheme used in encrypting the data files in
data transmission? I heard that different security modes will result
in different Kc length, do you have any details on this and what is
the length of the key?
3. For FHSS in bluetooth, there are 13 different packet types. Which
part of the packet is frequency hopping sequence information attached
to? Is it the access codes, the header or the payload? What is the bit
of this information? Do the slave derive that sequence based on the
data (Master's BD_ADDR and clock) exchanged or the slave gets the
sequence directly from the Master?
Sorry for the lengthy email. Please help if possible. Thanks
Sincerely
Ricky
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2004-09-30 6:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=db972f43040929233863680ff2@mail.gmail.com \
--to=rickysoh@gmail.com \
--cc=bluez-users@lists.sourceforge.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