Bluetooth Tutorial
Bluetooth Tutorial
Bluetooth Tutorial
Find
Bluetooth Resource Center Advanced search
Home
Bookshop
Market Research
Search Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Add a Link
Consulting
Database
Bluetooth Tutorial - Specifications
Bluetooth What is Bluetooth ? Well you can get lots of different definitions, but essentially
Antennas Bluetooth is the term used to describe the protocol of a short range (10 meter)
frequency-hopping radio link between devices. These devices are then termed
Articles
Bluetooth - enabled. Documentation on Bluetooth is split into two sections, the
Asia-Pacific
Bluetooth Specification and Bluetooth Profiles.
Audio
Books ● The Specification describes how the technology works (i.e the Bluetooth
Cathal's Corner protocol architecture),
Consultants ● The Profiles describe how the technology is used (i.e how different parts of
Design Tools the specification can be used to fulfil a desired function for a Bluetooth device)
Dev Tools
Downloads The Specification is examined first, then the Profiles.
Events
FAQ
Forums
Glossary Bluetooth Specification Protocol Stack:
InfoTooth
News
Products
Profiles
Research
Security
SIG
Shop
Subscribe
Technology
Testing
Training
Tutorial
WLANs & BT
What Is
Bluetooth?
Members
Member:
Password:
Login
Forgot your
Click on a section of the diagram* above, for a tutorial of its functions
password?
New Member
In more detail: Bluetooth is the name given to a new technology using short-
range radio links, intended to replace the cable(s) connecting portable and/or fixed
electronic devices. It is envisaged that it will allow for the replacement of the many
propriety cables that connect one device to another with one universal radio link. Its
key features are robustness, low complexity, low power and low cost. Designed to
operate in noisy frequency environments, the Bluetooth radio uses a fast
acknowledgement and frequency hopping scheme to make the link robust. Bluetooth
radio modules operate in the unlicensed ISM band at 2.4GHz, and avoid interference
from other signals by hopping to a new frequency after transmitting or receiving a
Have you packet. Compared with other systems in the same frequency band, the Bluetooth
visited our radio hops faster and uses shorter packets. The following pages give more detail
WAP about different sections of the protocol, note this tutorial is completely up to date with
Games the latest version of the bluetooth Specification (ver 1.1)
section yet?
1 Radio v1.1
2 Baseband v1.1
3 LMP v1.1
4 HCI v1.1
5 L2CAP v1.1
Logical Link Control and Adaptation
Protocol (L2CAP) supports higher
level protocol multiplexing, packet
segmentation and reassembly, and the
conveying of quality of service
information.
6 RFCOMM v1.1
7 SDP v1.1
Find
Wireless Resource Center Advanced search
October 2003
Members ● We've added a new section for EDGE (Enhanced Data for
Global Evolution) resources.
September 2003
Pages Served:
● Palowireless Wireless Update September 2003 Events,
Location-Based Services (LBS), Market Research, From The
2003: 3.6 million
Wireless Bookshop, Advertising and Sponsorship, Premium
2002: 3.27 million Membership, Recent Site News...
2001: 2.15 million
August 2003
July 2003
June 2003
● We've updated our news headlines feed. You'll find brief news
headlines in the right side of our news pages and other
selected sections.
May 2003
Find
Wireless Resource Center Advanced search
Forgot your
password?
New Member
Search for in
All Products Search Search tips
Search Amazon.com
Keywords:
Alexa Toolbar
Find
Wireless Resource Center Advanced search
Members
IEEE 802.11 IEEE 802.15 IEEE 802.16
Wireless LAN Wireless Wireless
technology. Personal Area Metropolitan Area
Member: Networking Networking (MAN)
(PAN) technology.
Password: technology.
Login
Forgot your
IrDA Java LBS
password?
Infrared Data Wireless Java Location Based
Association and J2ME. Services and Americas
New Member
standard. Location-Enabled
Business. GSM Americas
20 Nov 2003
Rio de Janeiro
OFDM Radar Satellite
Int'l Conference on
Orthogonal Radio Communications,
Pages Served: Computer Scienc
Frequency Detection And TV, Remote
2003: 3.6 million 15 Jan 2004
Division Ranging. sensing and other Honolulu, USA
2002: 3.27 million Multiplexing. related topics.
2001: 2.15 million
SMS, EMS, SyncML UMTS/3G Visit our
MMS Data Universal Mobile Wireless Events
Short, synchronization Telephony System page for full listings of
Enhanced & standard. and Third conferences, seminars
Multimedia Generation and trade shows.
Messaging Mobile.
Services.
WLL ** ZigBee
Wireless Specification
Local Loop. for untethered Have you visited our
devices. Wireless Bookshop
yet?
Members
Contact Us
Testimonials
What others
are saying palowireless and
about us. palowireless.com
are trademarks of
palowireless Pty
Ltd.
Find
Wireless Bookshop Advanced search
Home
The Wireless Bookshop What's Hot:
Bookshop
Market Research Welcome to the palowireless Wireless
Search Bookshop - an affilliate of Barnes & Noble.
Add a Link
Essential Guide to
We specialise in books on wireless RF and Wireless, Second
Consulting
Database
networking technologies and related Edition
subject such as security, games,
marketing, design, etc. Enjoy!
XHTML
Antennas ARRL Bluetooth
Recommended
Books on antennas Books on Books on GPS Land Navigation
and antenna American Radio Bluetooth
design. Relay League Short Range
topics. Radio.
Members Wireless Nation: The
Frenzied Launch of the
Cellular, 3G Games GPRS
Cellular Revolution in
3G, Cellular, TDMA, Game Design General America
CDMA, and other and Packet Radio
Member:
related topics. Implementation. Service
publications.
Password:
Dilbert and the Way
GPS GSM i-mode of the Weasel
Login Global Positioning Global System The best i-
System for Mobiles mode and
Forgot your publications. publications. cHTML books
Essential Guide to
password? and
Wireless
publications. Communications
New Member Applications
Java LBS mCommerce
The latest Wireless Location-Based The latest
Java & JM2E Services and mobile
publications. Location- commerce Bluetooth for Java
Enabled titles.
Business books
and
publications. Bluetooth 1.1: Connect
Without Cables, Second
Edition
Medical & .NET OFDM
Radiology The latest The latest
The latest mobile books and OFDM books
medical references and other OFDM Wireless LANs: A
applications, guides on the publications. Theoretical and Practical
radiology and .NET Guide
related topics. framework.
Wireless Messaging
Demystified: SMS,EMS,
MMS and Others
Wireless Java
Wireless Local XHTML Books For
Programming with J2ME
Loops Books on Dummies
The latest WLL eXtensible Ok, admit it -
books and related HyperText we've all
publications. Markup bought one of Creating Location
Language these Services for the
(XHTML) and sometime... Wireless Web
related topics.
Recommended:
Recommended
Reading * * Membership TCP/IP For Dummies
Some of the best is required for
reference books some
around on wireless sections.
topics. Internetworking with TCP/IP
Vol.1 : Principles, Protocols,
and Architecture
Resources:
J2ME: The Complete
Reference
Currency converter Subscribe * Newsletter
Click here for a Subscribe to Archive
handy conversion our Wireless past issues of
calculator for US$ Bookshop our Bookshop More wireless books...
or other prices. newsletter. Newsletter.
Other Goodies:
Dilbert
You don't have
to be an
engineer -
these are for
people in
cubicles
everywhere!
2004 Desk
Calendars
Got yours yet?
Check out our
favorites.
Featured
Section
Have you
visited our
featured
section for this
month?
November 2003
1 1 802.11 Wireless
Networks: The
Definitive Guide
As a network
administrator,
architect, or security
professional, you
need to understand
the capabilities,
limitations, and risks
associated with
integrating wireless
LAN technology into
your current
infrastructure. 802.11
Wireless Networks:
The Definitive Guide
provides all the
information
necessary to analyze
and deploy wireless
networks with
confidence.
Matthew S. Gast,
Mike Loukides
Format: Paperback,
464pp.
Publisher: O'Reilly &
Associates
Published: May 2002
There's a wireless
revolution underway!
With The Essential
Guide to RF and
Wireless, Second
Edition, you can help
drive that revolution,
even if you don't
have a technical
background. This
clear, concise, easy-
to-understand
briefing cuts through
the jargon to explain
how today's wireless
systems really work.
Fully updated to
Carl J. Weisman
Format: Paperback,
2nd ed., 332pp.
Publisher: Pearson
Education
Pubished: January
2002
3 - Wireless Hacks:
100 Industrial-
Strength Tips and
Techniques
Wireless Hacks
offers 100 industrial-
strength tips about
wireless networking,
contributed by
experts who apply
what they know in
the real world every
day. Each hack can
be read in just a few
minutes, but can
save you hours of
research. Written for
the intermediate to
advanced wireless
user, Wireless Hacks
is full of practical,
ingenious solutions
to real-world
networking situations
and problems.
Whether your
wireless network
needs to extend to
the edge of your
office or to the other
end of town, this
collection of
nonobvious, "from
the field" techniques
will show you how to
get the job done.
4 5 How Wireless
Works
Preston Gralla
Format: Paperback,
232pp.
Publisher: Que
Published: November
2001
5 6 Wi-Fi Handbook:
Building 802.11b
Wireless Networks
complexities of
building 802.11b
wireless networks in
your own world, this
is the book for you.
Franklin D. Ohrtman,
Konrad Roeder
Format: Paperback,
363pp
Publisher: McGraw-
Hill Companies
Published: April 2003
How the
convergence of
mobile
communications and
computing is driving
the next social
revolution-
transforming the
ways in which people
meet, mate, work,
buy, sell, govern, and
create.
Howard Rheingold
Format: Hardcover,
288pp.
Publisher: Perseus
Publishing
Published:
September 2002
7 2 Passport to World
Band Radio (2003)
This is a consumer's
guide to radio
receivers plus a
directory to
shortwave radio
broadcasting around
the world. . . . The
buyer's guide to
world-band radio
section rates
receivers and lists
them in various
categories (portables,
tabletop, and special
categories, including
a section on
antennas). . .
Lawrence Magne,
Tony Jones
Format: Paperback,
592pp.
Publisher:
International
Broadcasting
Services, Ltd.
Published: December
2002
8 9 Introduction to
Space-Time
Wireless
Communications
Arogyaswami
Paulraj, Dhananjay
Gore, Rohit Nabar
Format: Hardcover,
308pp
Publisher: Cambridge
University Press
Published: May 2003
9 - Wireless Sensor
Networks:
Architectures and
Protocols
Because they
provide practical
machine-to-machine
communication at a
very low cost, the
popularity of wireless
sensor networks is
expected to
skyrocket in the next
few years, duplicating
the recent explosion
of wireless LANs.
Wireless Sensor
Networks:
Architectures and
Protocols describes
how to build these
networks, from the
layers of the
communication
protocol through the
design of network
nodes. This overview
summarizes the
multiple applications
of wireless sensor
networks, then
discusses network
device design and
the requirements that
foster the successful
performance of these
applications...
Edgar H. Callaway
Format: Hardcover,
360pp
Publisher: CRC
Press
Published:
September 2003
10 - Real 802.11
Security: Wi-Fi
Protected Access
and 802.11i
Format: Paperback,
451pp
Publisher: Addison-
Wesley
Published: August
2003
Find
Advanced search
Wireless Market Research
Home
Wireless Market Research What's Hot:
Bookshop
Market Research Welcome to our guide to research and market reports for the wireless
Search industries.
Add a Link
2003 Wireless Markets
This online catalog of market research publications allows you to find,
Consulting
review, and purchase competitive intelligence quickly, easily, and
Database
securely.
Wireless Infrastructure
The catalog contains thousands of titles from hundreds of publishers. Market Strategies
Market
All prices are in US$ unless stated otherwise.
Research
Featured Wireless Java 2002
Search Tips
Contact Us about Custom Research.
Business Benefits
Members of VoiceXML
Featured Report
The global Wireless Market has undergone immense expansion in the Have you visited our
Bookshop yet?
last 25 years. While several factors are collectively responsible for this
growth, the convergence between the ‘'wired' and the 'wireless' is
arguably the most significant of them all. The progress that has been
seen in wireless and portable computing owes hugely to the blurring of
boundaries between the wireless, wireline and the Internet service
providers. 'Mobile wireless' thus is the latest buzzword that has caught
the attention of all concerned participants in the market.
Recommended Reading
E-Stats
Published: Quarterly
Published By: The Shosteck Group
****
This report looks at some of the key demographic and technology trends
that are resulting in new product opportunities, and then looks at some
****
Find
Wireless Resource Center Advanced search
Members
Next >
Pages Served:
Find
Consulting Services Advanced search
❍ Marketing Services
❍ Management Services
Login
Forgot your
password? About Palowireless Pty Ltd
Find
Wireless Resource Center Advanced search
Home
Wireless Database
Bookshop
Market Research Our detailed news and summary profiles for key
Search wireless products, applications, manufacturers and
Add a Link vendors.
Consulting
To access these pages you require Premium
Membership.
Contents
Member login
● Our A - Z of selected wireless vendors
User id: News, products and summaries for key wireless
companies from Agere to Zeevo.
❍ Bluetooth Modules
Our April 2002 roundup of selected
Bluetooth module suppliers.
❍ Headsets
A quick tour of the state-of-the-art for
Bluetooth headsets and related
components.
❍ Batteries
Our new (and still growing) roundup of
batteries for mobile applications.
Find
Bluetooth Resource Center Advanced search
Login between the ‘'wired' and the 'wireless' is arguably the most
significant of them all. The progress that has been seen in
Forgot your wireless and portable computing owes hugely to the
blurring of boundaries between the wireless, wireline and Top Bluetooth Sites
password?
the Internet service providers. 'Mobile wireless' thus is the
New Member latest buzzword that has caught the attention of all Thank you for your
concerned participants in the market. support in making us
one of the top Bluetooth
sites on the web!
Published: September 2003
Published By: RNCOS
Page Count: 50
****
See our Bluetooth Books section for all the latest titles.
Dean A. Gratton
Format: Hardcover, 569pp
Publisher: Pearson Education
Published: December 2002
Madhushee Gangali
Format: Paperback, 416pp.
Publisher: Premier Press
Published: September 2002
Find
Bluetooth Resource Center Advanced search
Bluetooth
Antennas
Articles
Asia-Pacific
Audio
Books
● Blue2Net (Sweden)
Cathal's Corner
Consultants
❍ Directional high-gain antenna omni-directional low-gain
Design Tools
antenna.
Dev Tools
Downloads
Events
FAQ
● Centurion
Forums
Glossary ❍ Bluetooth Antenna Products Internal and chip antennas.
InfoTooth
News
Products ● Ethertronics (USA)
Profiles
Research ❍ A variety of embedded antennas for cellphone
Security manufacturers and short range wireless Bluetooth and
Shop 802.11b antennas.
SIG
Subscribe
Technology ● Fractal Antenna Systems (USA)
Testing
Training ❍ Low-profile ComCyl antenna for the Bluetooth (2.4-
Tutorial GHz) and wireless local-area network (WLAN).
WLANs & BT
● Intenna (Sweden)
● Rainsun (USA)
● RangeStar (USA)
❍ Bluetooth Solutions
● SkyCross (USA/Japan)
❍ SkyCross provides antennas that will work in the ISM
● Yokowo (Japan)
❍ Ceramic antennas for personal communication.
Also see:
SAR
❍ MLA Antennas - Physically Small, Electrically Large
❍ Today's Wireless Antenna: More Efficient, Multiple
Frequencies
❍ Future Telematics Applications Rely on Wireless
Integration.
Find
Bluetooth Resource Center Advanced search
seeking to decide a
❍ Arca WaveCatcher
winner. This article
& WaveMaker
however explains the
❍ Catalyst BTAE
similarities and
❍ CATC Merlin
differences between
❍ CATC Merlin
Bluetooth & 802.11b
Mobile
on a broad level and
❍ CATC
tries to show that
BTTracer/Trainer
there is no serious
(NEW!)
competition between
❍ CETECOM BITE
the two. In fact both
❍ Frontline Test
have their own
Equipment
advantages and
SerialBlue and FTS
disadvantages, and
for Bluetooth
both technologies
❍ IVT BlueTester /
can complement
BlueAnalyzer
each other... more...
❍ Mobiwave /
Yokogawa BPA-
❍ Bluetooth Mobility D10
& Roaming ** ❍ Rohde & Schwarz
Two major current PTW 60
limitations of Bluetooth
are: that communication ❍ Tektronix BPA100
between devices must be ❍ Yokogawa BX1000
direct; and secondly that
they do not support the
movement of an active
terminal from one network
interface device to More Bluetooth
another. This article briefly
examines several Information
theoretical ways in which
these interpiconet issues ❍ Don't forget to take
could be handled and
developed.... more... a look at our
Bluetooth Tutorial
❍ Bluetooth Security - and FAQ!
Part 1 **
❍ Click here to
Nothing has caused
more concern and subscribe to our
confusion in free Bluetooth
Bluetooth than the email newsletter.
nature of Bluetooth
security
implementation. Submit An Article
From those who
insist that its security ❍ Click here or
is a disaster area,
contact us if you'd
prey to any half-
like to submit an
capable opportunist,
article.
to the contrary view
that’s its security is
second to none...
more...
❍ Bluetooth Security -
Part 2 **
Last month we
examined the lower
level of Bluetooth
security (Link Level
security). This month
we look at the
Security Mode 2 (
the service level
enforced security )
and a possible
implementation of it.
We also evaluate the
overall
merits/drawbacks of
Bluetooth in the
security arena....
more...
❍ Bluetooth Security -
Part 3 **
As shown in parts 1
& 2 of this article,
Bluetooth has a
comprehensive set
of security features,
at both upper and
lower levels.
However for all of it's
security features,
Bluetooth does have
some security
issues..... more...
Contributed Articles
❍ Northstream
Bluetooth
Opportunities and
Threats from a
Market Perspective
(9/01) (34Kb, PDF)
Usage models, The
business case of
short-range
networks, The
business case of
short-range networks
and Coexistence.
❍ MindBranch
Bluetooth: Value
Adds and
Opportunities
(8/01) (431Kb, PDF)
Uses of Bluetooth
Technology,
Competing Bluetooth
Technologies,
Devices: What does
the future hold? Are
Lap-Tops Leading
the Way?
Applications: How
much influence do
they really have?
Equipment: How will
Bluetooth effect
equipment
forecasts? Bluetooth
Opportunities, The
Value of Bluetooth.
❍ Marcin Michalak
Multimedia
Transmission in
Bluetooth-based
Networks (6/01)
(1143Kb, PDF)
Includes: - short
description of
Bluetooth and
multimedia
transmission
technologies, -
creation of the
testing environment, -
performance tests
and results of MPEG-
1, MPEG-4
(QuickTime) and
RealVideo
transmissions.
Find
Bluetooth Resource Center Advanced search
Bluetooth
Antennas
Articles
Asia-Pacific
Audio
Books
Cathal's Corner Featured Market Research
Consultants
Design Tools Recommended reports from reputable researchers.
Dev Tools
Downloads Asia Pacific Mobile Analyst
Events
FAQ Asia Pacific Mobile Analyst, an electronic newsletter
Forums from the publishers of ASIAcom, is your essential
Glossary fortnightly guide to the shifting power dynamic of Asian
InfoTooth next generation mobile development. From new pricing
News and tariffing requirements to mergers and consolidation,
Products every electronic issue includes the comprehensive
Profiles analysis and data necessary to compete. In addition,
Research Asia Pacific Mobile Analyst provides a consistent,
Security strategic assessment of regional developments across
Shop Asia within a global context, invaluable for European,
SIG US and ROW players looking to secure a global
Subscribe position.
Technology
Testing Type: Newsletter
Training Published: Fortnightly
Tutorial Published By: Baskerville
WLANs & BT
****
What Is
Bluetooth? Also Recommended:
Useful Links
Australia
● Ericsson Australia
● HCV
● IBM Australia
● Intel Australia
● Nokia
● Palowireless
● BluetoothInChina
● China WPAN
❍ WPAN News in China including Bluetooth, IEEE
● Ericsson China
● Telecom Asia
Japan
● Ericsson Japan
● Hitachi, Ltd
● Sony Japan
● Toshiba Japan
Korea
● Ericsson Korea
● Tricomtek
❍ Bluetooth and other Protocol Testing,
New Zealand
● Sony NZ
Singapore
Taiwan
● Alltek Taiwan
● Macronix Taiwan
Find
Wireless Resource Center Advanced search
Member:
Password:
Login
Forgot your
password?
New Member
Pages Served:
Find
Wireless Bookshop Advanced search
Wireless Java
Programming with J2ME
Creating Location
Bluetooth Profiles
Dean A. Gratton
Format: Hardcover, 550pp
Publisher: Pearson
Education
Published: December
2002
Mohammad Ilyas
Format: Hardcover
Madhushee Gangali
Format: Paperback,
416pp.
Publisher: Premier Press
Published: September
2002
Andreas Lerg
Format: Paperback,
160pp.
Publisher: Data Becker
Published: August 2002
For corporations
considering using
Bluetooth in offices, this
book details what
Bluetooth is capable of
and how it compares to
other wireless
technologies. For
companies developing
Bluetooth applications, it
● Implement “wireless
cable” for phones,
other handhelds,
and portables
● Build futuristic
Bluetooth apps—for
refrigerators that
update PDA
shopping lists, PDAs
that survey local
stores for the best
prices, and as many
others as you can
dream up
● Examine operational
characteristics in
detail
● Solve security
issues
● Get technical
insights on
Bluetooth's
coexistence with
other wireless
devices
● Find the facts you
want on packet
structure, paging,
host interfacing, and
designing and
testing the Bluetooth
module
● Probe the math
behind the
specifications for
further research
Robert Morrow
Format: Paperback,
567pp.
Publisher: McGraw-Hill
Professional
Published: May 2002
Gilster (Editor)
Format: Paperback,
384pp.
Publisher: Hungry Minds
Published: March 2002
The Bluetooth
specification has been
updated to deliver
dramatic improvements in
both reliability and
interoperability. Bluetooth
1.1: Connect Without
Cables, Second Edition
updates the industry's #1
Bluetooth guide to cover
these critical new
enhancements—and to
offer detailed guidance on
every aspect of Bluetooth
1.1 development.
Bluetooth security
and power
conservation
● New Bluetooth
profiles—including
the long-awaited
Personal Area
Networking profile!
Jennifer Bray,Charles
Sturman
Format: Hardcover, 2nd
ed., 622pp.
Publisher: Prentice Hall
PTR
Published: December
2001
Journal
Dreamtech
Format: Paperback,
552pp. & CD-ROM
Publisher: Wiley, John &
Sons, Inc
Published: November
2001
Bluetooth Application
Developer's Guide
Bluetooth Developer's
Guide to Embedded
Applications will provide
developers with an
advanced guide to the
wireless frequencies
governing the Bluetooth
protocol. This book will
give readers all of the
insight, tool, and
techniques necessary to
write embedded Bluetooth
applications. Written for
advanced programmers,
this book this book will be
invaluable for the
Bluetooth developer.
Publishing
Published: September
2001
Tom Siep
Format: Hardcover,
150pp.
Publisher: IEEE
STANDARD OFFICE
Published: November
2000
Discovering Bluetooth
Discovering Bluetooth
offers unparalleled insights
into this new wireless
technology, discusses its
many potential
applications, and shows
you how you can integrate
Bluetooth into your daily
routine.
Michael Miller
Format: Paperback,
304pp.
Publisher: Sybex,
Incorporated
Published: July 2001
Bluetooth Revealed
Develop state-of-the-art
wireless applications using
this detailed guide.
Transmit data over
wireless networks and
develop cutting-edge
applications with this
hands-on reference. This
in-depth guide fully
explains how wireless
technology works and
introduces the next
generation of applications
that allow for the
transmission of data
Gilbert Held
Format: Paperback
Publisher: McGraw-Hill
Professional Book Group
Published: December
2000
Wireless Personal
Communications :
Bluetooth and Other
Technologies
Wireless Personal
Communications:
Bluetooth Tutorial and
Other Technologies
presents a broad range of
topics in wireless
communications, including
perspectives from both
industry and academia.
This book serves as a
reflection of emerging
technologies in wireless
communications and
features papers from world-
renowned authors on the
subject. A new tutorial on
the emerging Bluetooth
technology is also
presented.
William H. Tranter
Format: Hardcover
Publisher: Kluwer
Academic Publishers
Published: December
2000
Find
Bluetooth Resource Center Advanced search
Home
Bookshop
CATHAL'S CORNER Cathal Mc Daid
Market Research
Search Welcome to Cathal's Corner - articles by Cathal Mc Daid covering a
Add a Link range of Bluetooth topics...
Consulting
Database
Future versions of Bluetooth - Bluetooth 1.2 & Bluetooth 2.0
Bluetooth Security
Find
Bluetooth Resource Center Advanced search
Bluetooth
Antennas
Articles
Asia-Pacific
Audio Primary
Organisation Overview
Books Location
Cathal's Corner
Wireless business and
Consultants
technology consultants.
Design Tools
Bluetooth, WAP, WLAN,
Dev Tools
Security, Java, location-
Downloads Palowireless Australia /
based services, technical,
Events Consulting Europe / USA
marketing and
FAQ
management services...
Forums
Click here to find out
Glossary
more.
InfoTooth
News Bluetooth Consultancy,
7layers Germany
Products Test Lab, BQB and more
Profiles
Research
Security
Shop
SIG
Bluetooth Global
Solutions. Testing,
CETECOM Germany
Approvals, Test Systems,
Development & Support.
ChipHelp is a provider of
Electronic Design
Services (chip & board
level), technical business
consulting, semiconductor
ChipHelp USA training courses and
technical recruiting
services. We offer
capabilities in Bluetooth
design, development and
integration services.
The Home of Bluetooth
and Embedded Systems
Solutions. Custom
Bluetooth-based wireless
application development.
Clarinox Australia
Embedded systems
solutions; software
design, hardware design
and device driver
development.
Offering the services for
your organization to learn
Code Blue more about Bluetooth
USA wireless technology and
Communications
help apply our expertise
to your products and
solutions.
Swedish Bluetooth
Combra AB Sweden hardware and software
consultants.
connectBlue specializes
in integrating Bluetooth
based communication
solutions in applications
and products for industrial
and commercial use.
connectBlue offers you a
connectBlue AB Sweden wide range of services all
depending on your needs
and requirements. The
services can range from
feasibility study to product
management both of
hardware and software
products.
Wireless software tools,
applications and
communication services
Cravewire USA
to assist and enhance the
use of Bluetooth enabled
devices.
Bluetooth design services
DCM Technologies USA
(USA / Japan / India)
eCom specialise in
providing expert solutions
in the Bluetooth, WAP,
eCom UK
Wireless, M-Commerce,
E-Commerce and related
fields.
ASIC design, RF
engineering, digital and
Electronic System analog design, DSP-
USA
Products (ESP) related development,
software and embedded
systems development.
LitePoint Wireless
System Design is a
Silicon Valley company
with a very experienced
and talented team of
LitePoint Wireless engineers from the
USA semiconductor and cell
System Design
phone industry. LitePoint
is your systems design
expert resource, offering
design consultancy
services to semiconductor
and systems companies.
L.S. Research has been a
leader in RF and wireless
design since 1980. With a
core compentency of
wireless product
development, L.S.
Research offers a broad
L.S. Research USA
range of services
including RF design,
antenna design, software
design, PCB layout,
prototyping, product
verification, and FCC
certification.
Specialists in mobile radio
communications design
for low cost and high
volume for systems such
as pcs, gsm, dcs, umts
and bluetooth transmitters
and receivers. Mentorport
offer design services to
Mentorport UK
the Clients requirements
from 1MHz to
10GHz,cellular
communications to
Nily Technologies is a
fabless company and
aiming to be a leading
supplier of RF GaAs and
Silicon Intellectual
Properties (IP) and RFIC
Design Services. Nily
technologies leverages
advanced design
Nily Technologies France
automation capabilities of
today modern simulation
and layout tools to
shorten your specific RF
circuit needs. IEEE
802.11a, HyperLAN II,
IEEE 802.11b, Bluetooth,
ISM radio system,
MMDS, MVDS
NT Communications
UK Consultancy services.
Ltd
Leading provider of
Open Interface USA Bluetooth technology for
the PC market.
Bluetooth design,
development and
Penell Denmark integration also within
HealthCare and Medical
Devices.
Proticom provides
consulting services to
help our clients develop
and implement successful
quality assurance efforts.
Proticom Proticom provides
advanced quality
solutions for emerging
technologies such as
Bluetooth, WAP, and
mobile applications.
RFI provides independant
compliance and
regulatory services for the
wireless communications
Radio Frequency industry. RFI is focusing
UK / USA on GSM, 3G, Bluetooth,
Investigation
WAP and Smartcard
technology. RFI will be
offering BQB, BQTF
services and consultancy
for Bluetooth products.
RTX Telecom is one of
the world's leading
independent suppliers of
Total Product
development Solutions,
focusing exclusively on
RTX Denmark
advanced wireless
communication standards
such as DECT, DPRS,
ISDN, WDCT, GSM,
CDMA, UMTS, and
Bluetooth.
A consulting company
that focuses on turnkey
solutions
Integrated Bluetooth
Product Development. A
privately held company
specialising in product
development using
Bluetooh components -
hardware and software.
We have in-depth
Spagat A/S Norway
knowledge of the
Bluetooth protocol stack
and various profiles with
experience on the
following platforms:
Windows 2000, Pocket
PC (Win CE) and Epoc
(Symbian).
ISDN and Bluetooth -
Products and Protocol-
Stollman Germany
Stacks. Custom
development services.
Bluetooth design,
Stonestreet One USA development and
integration services.
By developing innovative
applications for Bluetooth
In-Building Networks,
Strio provides retailers
Strio USA
with a suite of services,
creating wireless
communities inside brick
and mortar environments.
Custom Bluetooth
STS Netherlands
solutions.
An expanding
development company
specializing in integrating
Syncore communication solutions
Technologies AB Sweden based on Bluetooth
wireless technology in
applications and systems
for industrial or
commercial use.
Bluetooth and other
Protocol Testing, Korean
reseller of arca
Tricomtek Serialcatcher and
Korea
Wavecatcher. Developers
of short messaging
applications for 3G SMSC
and SMS platform.
Test Consultance BQB,
TÜV Rheinland/Berlin- BQTF, Worldwide
Germany
Brandenburg Regulary Type Approvals
etc.
Bluetooth Services Wipro
provides complete design
& implementation
services for Bluetooth for
Wipro mobile devices. Using the
India
Bluetooth core stack
developed in-house,
GR&D offers the time-to-
market advantage to the
customers.
Wireless Futures is a
consultancy operating in
the telecoms, wireless
and high technology
sectors. We are assisting
Wireless Futures UK
product manufacturers in
the development and test
of leading edge products
including GPRS,
Bluetooth and EMS.
Wireless Solutions for
Wireless Solutions Sweden
Bluetooth and WLAN
Find
Bluetooth Resource Center Advanced search
Bluetooth
Antennas
Articles
Asia-Pacific
Audio
Books
Cathal's Corner
Consultants
Design Tools ADS Bluetooth DesignGuide assists Bluetooth
Dev Tools developers with optimization and verification of
Downloads Bluetooth RF system designs. The ready-to-
Events Agilent
use Bluetooth reference transceiver model
FAQ with adjustable parameters comes as part of
Forums the DesignGuide.
Glossary
InfoTooth NC-Sim tool is a single kernel simulator that
News can verify both mixed-language and mixed-
Products signal designs. The Advanced Analysis
Profiles
Environment provides HDL analysis and linting
Cadence
Research
while Verifault provides accurate fault
Security
coverage. The IP model packager enables
secure distribution of HDL intellectual property
Shop
for system-on-a-chip design.
SIG
Find
Bluetooth Resource Center Advanced search
Subscribe Microelectronics)
Technology ❍ W7020 is a complete, low-power Bluetooth radio
● Alcatel
❍ An embedded stack Bluetooth solution for headset and
Login
● Alps Electric
❍ UGXZ Series modules
Forgot your
UGXZ1 Class 1 Module and the UGXZ2 Class 2 Modules
password? have dimensions of 10.0mm x 13.5mm x 2.0mm and
10.0mm x 10.0mm and 1.9mm respectively. Weighing
New Member
0.5g, they are also approximately 75% lighter than earlier
models.
● Atinav
❍ Atinav offers a fully developed Bluetooth Protocol Stack.
● Atmel Corporation
❍ Atmel Bluetooth
also provided.
● AU-System
❍ AU-system is a distributor for the Ericsson Bluetooth Host
stack.
● Axis Communication
❍ Bluetooth Protocol Stack for Linux available under the
● BlueMod
❍ Bluemod is a compact, powerful, fully compliant
● Bluelogic
❍ Qualified Bluetooth Protocol stack
● Bluesoft
❍ Bluesoft provides unique positioning platforms and
● BlueTags
❍ The BlueTags Development Kits will enable you to test
● BrightCom
❍ IntelliBLUE
❍ BIC2101
Bluetooth Serial Applications.
BIC2101 is an IntelliBLUE based IC device designed to
serve as a cost effective Bluetooth Application Processor
for serial type cable replacement applications. Interfaces
include UART (RS-232) and PCM.
❍ BIC2102
Bluetooth Serial/USB Applications.
BIC2102 is an IntelliBLUE based IC device designed to
serve as a cost effective Bluetooth Application Processor
for USB and serial cable replacement type of applications.
Interfaces include: USB with Host and Device operation
modes, UART (RS-232) and PCM/CVSD.
❍ BIC2104
Ultra low power Bluetooth Applications.
❍ BIC2201
Bluetooth Hi-Fi Audio Applications.
BIC2202 is an IntelliBLUE based IC device designed to
serve as a Bluetooth Application Processor for high-
quality audio applications. The IC includes engines for
MP3 and SBC streaming, handling reception and
decoding of audio signals. Interfaces include stereo
CODEC, PCM, CAN Bus and UART.
❍ BIC2301
Bluetooth LANB Access Point Applications.
BIC230x is an IntelliBLUE based IC device designed to
serve as a Bluetooth Application Processor for LAN
access point. The IC includes an integrated Ethernet
interface.
● Broadcom
❍ BCM2002
● BSQUARE
❍ Bluetooth Extension to WinDK.
● BTDesigner
❍ Web site dedicated to designers of Bluetooth products.
● Cadence Design
❍ IC and Software Design Services - also see Symbionics
❍ Bluecore
BlueCore is a single chip radio and baseband IC for
Bluetooth, 2.4GHz radios, implemented in CMOS
technology.
❍ Casira
Supporting development for host-side and embedded
Bluetooth systems (interfacing at RFCOMM, and/or using
BlueCore's on-chip RISC microcontroller).
❍ MicroSira
A platform for developing USB-connected host-side
software.
❍ CompactSira
● CC&C
❍ Bluetooth protocol stack
❍ Bluetooth Headset
● DCM Technologies
❍ Bluetooth Protocol Stack
● Ericsson
❍ Ericsson Bluetooth Development Kit (BDK)
Overview
● ETHERchip
❍ Internet applications System on Chip with built in access
● Extended Systems
❍ Bluetooth Embedded Protocols
● GCT Semiconductor
❍ Radio Transceiver
❍ Baseband Processor
The GDM1201 is one of several Bluetooth ICs offered in
the GCT Bluetooth product family. The GDM1201 is a
Bluetooth baseband IC implemented with CMOS
technology. Together with the GDM1000 radio transceiver
IC and an external flash memory, it provides a fully
compliant Bluetooth solution for data and voice
communications.
❍ Baseband Processor
GDM1202 consists of programmable seamless Bluetooth
RF interfaces such as BlueQ or BlueRF RXMODE2/3,
Bluetooth baseband and bit processor, GCT proprietary
96MIPS hybrid RISC/DSP embedded processor with 48bit
resolution, and UART/PCM/USB/DAC standard interfaces.
● Himico
❍ Bluetooth Components
● IAR
❍ Bluetooth Starter Kit
The Bluetooth Starter Kit is an evaluation and
development platform for the Bluetooth wireless
technology. This product includes all hardware and
software that is needed to set up a Bluetooth node for
wireless communication and get started with Bluetooth
development! The included software can be used for both
data and/or voice communications.
● Ibex Technologies
❍ Viking Bluetooth Protocol Stack.
● IBM
❍ BlueDrekar protocol driver is IBM's new middleware based
on Bluetooth specifications allowing Bluetooth wireless
devices to reliably communicate with each other.
● Impart Technology
❍ Impart Technology's Embedded Communication Platform
● Impulsesoft
❍ Impulsesoft's Bluetooth Audio Solutions
❍ iWISH
Impulsesoft's Wireless Stereo Headphones. Developed
using Bluetooth audio profiles, this ready-to-manufacture
reference design helps OEM customers bring CD-quality
stereo solutions to market quickly at a low cost.
❍ iWISA
Impulsesoft's Bluetooth Stereo Adapter reference design.
iWISA is a plug-in device for existing audio systems that
wirelessly transmits stereo quality audio to other wireless
devices like stereo headphone.
● Infineon Technologies
❍ Bluetooth system solution.
● InnoCOMM
❍ Single chip Bluetooth radio transceiver
● Innovent systems
❍ Bluetooth Single-Chip RF ICs
● Intel
❍ Flash Data Integrator Software
Intel's FDI software is a fully-tested, debugged and Intel-
supported data storage manager for use in real-time
embedded applications.
● Inventel
❍ BlueBird Evaluation/Development Kit
● Inventop
❍ BluePing Network SDK a software development kit that
● IVT Corporation
❍ IVT Bluelet™ Protocol Stack
● Mecel
❍ Mecel Bluetooth Software Development Kit (SDK)
● Microware
❍ Port of Extended Systems Bluetooth protocol stack for OS-
9.
● MindTree
❍ EtherMind is MindTree’s implementation of the Bluetooth
software protocol.
Modular and compact it has been designed to support
various applications including LAN access point, printers,
● Motorola
❍ BTPLATFORM Bluetooth Platform Solution
❍ Platform Chipset
■ MC71000 Bluetooth Baseband Controller IC
Transceiver
■ Optional MC13181 Wireless Power Management IC
● National Semiconductor
❍ Single-chip 2.4GHz Radio
● NewLogic Technologies
❍ The BOOST Core is a Bluetooth processor adapted for
● Nokia
❍ Nokia Bluetooth
● Oki
❍ Bluetooth Chipsets and SDK
■ LSI Products
■ RF LSI in CMOS
■ LSI and Module Data Sheets
■ System Development Kit, SDK
■ LSI Road Map
■ BT Modules
■ Module Data Sheets
■ Bluetooth™ is for this...
■ Brochure (650KB PDF)
● Open Interface
❍ BLUEmagic 3.0 embedded Bluetooth protocol stack The
● OpenCores.org
❍ Open source project for Bluetooth baseband controller
design.
● Parthus
❍ Parthus achieved an industry first with the successful
● Philips
❍ Philips Logic Products
❍ Philips Semiconductors
❍ TrueBlue RF Modules
Bluetooth TrueBlue radio modules enable customers to
enhance their products cost effectively with Bluetooth
technology. Fully tested, plug-n-play solutions, these radio
modules minimize design cost and are easy to integrate
into existing systems.
❍ Bandband Controllers
■ PCF26002 Bluetooth baseband processor
❍ Bluetooth RF ICs
● Rococo Software
❍ Impronto is a lightweight middleware platform that allows
● Rappore Technologies
● RF Micro Devices
❍ RF2968, a low-cost transceiver for Bluetooth applications.
❍ RF2172 Bluetooth PA
● RTX
❍ RTX IP, Protocol Stack, Baseband core
● Silicon Wave
❍ Silicon Wave is a leading provider of low-power, highly
licensing program.
❍ SIW1502
The SiW1502 Radio Modem IC combines low-cost, low-
power consumption with integrated RF logic and Bluetooth
protocol stack for a wide variety of Bluetooth applications.
The SiW1502 is a fully integrated 2.4 GHz radio
transceiver with a GFSK modem contained on a single
chip. Silicon Wave offers the SiW1502 as a stand alone IC
or, in tandem with the SiW1601 Link Controller IC and a
standard microprocessor, to complete a Bluetooth
wireless communications system.
❍ SIW1602
The SiW1602 Baseband Processor interfaces directly with
the SiW1502 Radio Modem IC and provides power
control, data packet processing, error-detection/correction
and other data processing functions. The SiW1602 also
contains a USB controller which provides an easy method
● Socket Communications
❍ Bluetooth Evaluation Program for Windows CE
● SourceForge.net
❍ AXIS OpenBT Stack An open source bluetooth stack for
● Spirea
❍ Spirea is a fabless semiconductor company in the
● STMicroelectronics
❍ ST Bluetooth Wireless Technology Solutions provides
● Stollman
❍ ISDN and Bluetooth - Products and Protocol-Stacks
❍ Products:
BlueTA+ Bluetooth - ISDN Gateway
BlueUSB+ Bluetooth USB adapter
BluePCMCIA+ Bluetooth PCMCIA adapter
BlueRS+ Bluetooth serial adapter for industrial
applications
❍ Protocol Stacks:
BlueCode+ (Bluetooth upper layer Stack)
BlueFace+ (API for Bluetooth aware applications)
● Stonestreet One
❍ Bluetooth Developer's Kit
● Synopsys
❍ DesignWare BlueIQ
● Texas Instruments
❍ BSN6030 ROM-based Bluetooth baseband controller
● Troy XCD
❍ WindStack a fully Bluetooth 1.1 qualified Bluetooth stack,
● TTPCom
❍ TTPCom offers Bluetooth technology for licence. There
● Vaishali Semiconductor
❍ Bluetooth Products
Applications
● VB8831DK2 Bluetooth Development Kit for Fully
● Wireless Futures
❍ BlueWAVE RS232 Modules - OEM Bluetooth enabling
solution.
● Wipro
❍ Bluetooth services
● Widcomm
❍ Blue-Connect Visor™ Bluetooth enabler
● Xemics
❍ Semiconductor solutions for Bluetooth targeting the
● Zucotto
❍ XJB 100 Bluetooth protocol stack written in Java.
Find
Wireless Resource Center Advanced search
Testing
Training Europe
Tutorials
Venture Capital
Hotels/
WLL Local Event Start Date Location
Flights
Loop
Open Mobile Alliance
Africa Plenary
Americas 9 Nov 2003 London, UK
Asia-Pacific Open Mobile
Europe Alliance Plenary
Middle-East
Mobile Internet
Mobile Internet
Members 2003 - Europe's
Largest & Most
Influential Mobile
Content & Services
Member: Event
The premier
Password: meeting place for
content and
application
Login
providers, mobile
operators and
Forgot your technical solution
password? providers, looking
to capitalise on the
New Member phenomenal
revenue potential of
content and
applications via the
mass-market media 20 Nov 2003 Paris, France
channels of mobile
devices.
Revenues with a
Creative Portfolio of
Content &
Applications
BILLING For
Content &
Commerce
Evaluating the
Billing Evolution for
New Services and
Content
Commercial Opportunities
for Short Range Wireless
Technologies
As mobile phone
technologies evolve
to provide
advanced, high
speed data
services, short
range wireless
technologies
become
increasingly useful
for distributing data
among mobile
phones, notebooks 14 Jan 2004 London, UK
and handheld
computers. The aim
of this conference
is to bring together
senior level
decision makers in
the telecoms &
technology industry
to learn how to
exploit he
commercial
opportunities in the
short-range
wireless technology
market.
OMA Technical
Plenary. These
events are only 25 Apr 2004 Munich, Germany
open to members
of the Open Mobile
Alliance.
Asia-Pacific
Hotels/
Event Start Date Location
Flights
Mobile operators in
their need to
increase revenue
streams through
value-added
services are
investing in location
technology to
reduce churn and
increase customer
loyalty. However, in
order to reach a
profitable mass- 24 Nov 2003 Hong Kong
market levels,
critical success
factors must be in
place before
operator LBS
deployments can
grow significantly.
What are the key
issues that need to
be addressed
before embarking
on this dynamic
new marketplace?
IBC
IBC
as new service
delivery platforms
and development
tools to speed
deployment.
IIR
Market Outlook,
Market Drivers, &
Potential Markets,
Business Issues,
Opportunities &
Revenue
Generating Models,
Structure of the
Value Chain, 15 Mar 2004 Seoul, Korea
Telematics
Technology &
Advancements,
Applications &
Services, Case
Studies & Lesson
Learned...
IBC
untethered
peripheral, control
and entertainment
devices.
Americas
Hotels/
Event Start Date Location
Flights
GSM Americas
GSM Americas is
the key mobile
event for the region
and with GSM set
to dominate
wireless access
across the
Americas, it is the 20 Nov 2003 Rio de Janeiro
annual meeting
place for all
operators from
IBC
CDMA Americas
Congress is the
definitive event for
North American
and Latin American
wireless industry
leaders. The event
features informative
keynote
presentations from
top industry
executives, up-to-
the-minute
technical
information on
CDMA2000
evolution, an
extensive exhibit 8 Dec 2003 Miama, FLA
hall, and the latest
next-generation
devices. In
addition, it features
reliable, market-
tested strategies for
realizing revenue, a
spotlight on recent
Latin American
success stories,
interactive
workshops, and the
9th Annual CDMA
Test Forum,
highlighting the
latest
developments in
network
optimization.
Bluetooth
Americas,
incorporating the
Bluetooth
Developers
Conference, is the
only official
Bluetooth event
held in the
9 Dec 2003 San Jose, CA
Americas. The
focus of this event
is broader to reflect
the growing
maturity of the
Bluetooth market,
the programme will
retain a detailed
technical level of
content.
Hawaii International
Conference on Computer
Science
OMA Technical
Plenary. These
events are only 1 Feb 2004 Los Angeles, CA
open to members
of the Open Mobile
Alliance.
peripheral, control
and entertainment
devices.
Middle-East/Africa
Hotels/
Event Start Date Location
Flights
SatCom Africa is
Africa's most
important annual
satellite
communications
event. This is the
Johannesburg,South
place where 17 Feb 2004
Africa
technology, the
know-how and the
ideas come
together to make
Africa's satellite
communications
work.
Find
Bluetooth Resource Center Advanced search
Home
Bookshop
Market Research
Search
Add a Link
Bluetooth FAQ and Knowledge Base
Consulting
Database
SDP
Message ACK/NACK
● RFCOMM DLCI & Server
Compared to GPS
● Bluetooth - an Inferior
● GFSK Modulation
Calculation LMP
● Exact Frequency Used
● Master LM Sniff
● EMC & Bluetooth
Security
● Round Computations in
Authentication Function
E1
● Security/Protection
Issues in Bluetooth
● Repeat Packet
Encryption
● Encryption Sample Data
Problem
Find
Bluetooth Resource Center Advanced search
Subscribe
Technology ● Regional Bluetooth User Groups:
❍ Boston area
Testing
Training ❍ India (primarily Bangalore)
WLANs & BT
● Ericsson Developers Zone
What Is ❍ WAP, Bluetooth, EPOC, SMS, GPRS and Mobile
Bluetooth? Positioning
New Member
Find
Advanced search
Bluetooth Resource Center
Consulting
Database
Bluetooth Glossary
Bluetooth The following is a list of most of the terms used in the Bluetooth technology, and serves as a
Antennas quick look-up guide. This glossary is partly based on the Glossary originally supplied in the Motorola
Articles Bluetooth website, my thanks to them. However this glossary contains much more lower layer
Asia-Pacific information, removes the reams of superfluous terms, and elaborates on many points. In effect it is
Audio a totally different list, and (I think) much better and clearer.
Books
Cathal's Corner
Consultants
Design Tools 2-in-1 Handset
Dev Tools The situation where a subscriber handset is acting as a remote handset to a base unit which
Downloads provides a network connection.
Events
FAQ 3G
Forums Third generation. Refers to the next generation of digital phone technology (such as UMTS).
Glossary Also see 3G Resource Center.
InfoTooth
News 802.11 WLAN
Products A Wireless Lan specification defined by the IEEE. Also see IEEE 802.11 Resource Center.
Profiles
Research
Access Code
Security
Each baseband packet starts with an Access code, which can be one of 3 types, CAC, DAC
SIG
& IAC. The CAC consists of a preamble, sync word and trailer, and its total length is 72 bits.
Shop
When used as a self-contained message without a packet header, the DAC and IAC do not
Subscribe
include the trailer bits and are of length 68 bits.
Technology
Testing
Training
Tutorial ACK
WLANs & BT Acknowledge.
What Is ACL
Bluetooth? Asynchronous Connectionless Link.One of the two types of data links defined for the
Bluetooth Systems, it is an asynchronous (packet-switched) connection between two devices
created on the LMP level. This type of link is used primarily to transmit ACL packet data. The
Member:
Active Mode
Password: In the active mode, the Bluetooth unit actively participates on the channel. The master
schedules the transmission based on traffic demands to and from the different slaves. In
Login
addition, it supports regular transmissions to keep slaves synchronised to the channel. Active
slaves listen in the master-to-slave slots for packets. If an active slave is not addressed, it
may sleep until the next new master transmission.
Forgot your
password?
AM_ADDR
New Member
Active Member Address. It is a 3 bit number.It is only valid as long as the slave is active on
the channel. It is also sometimes called the MAC address of a Bluetooth unit.
AP
Access Point.
AR_ADDR
Access Request Address. This is used by the parked slave to determine the slave-to-master
Have you half slot in the access window it is allowed to send access request messages in. It is only
visited our valid as long as the slave is parked and is not necessarily unique.
WAP
ARQN
Games
Automatic Repeat reQuest Number is used as a 1-bit acknowledge indication to inform the
section yet? source of a successful transfer of payload data with CRC.
authentication
The process of verifying 'who' is at the other end of the link. Authentication is performed for
devices. In Bluetooth, this is achieved by the authentication procedure based on the stored
link key or by pairing (entering a PIN).
authentication device
A device whose identity has been verified during the lifetime of the current link based on the
authentication procedure.
AUX
An ACL link packet type for data. An AUX1 packet resembles a DH1 packet except it has no
CRC code. As a result it can can carry up to 30 info bytes.
baseband
The baseband describes the specifications of the digital signal processing part of the
hardware -- the Bluetooth link controller, which carries out the baseband protocols and other
low-level link routines.
BB
Abbreviation of Baseband.
BD
Bluetooth device
BD_ADDR
Bluetooth Device Address. Each Bluetooth transceiver is allocated a unique 48-bit device
address. It is divided into a 24-bit LAP field, a 16-bit NAP field and a 8-bit UAP field.
BER
Bit Error Rate
Bluetooth
An open specification for wireless communication of data and voice. It is based on a low-cost
short-range radio link facilitating protected ad hoc connections for stationary and mobile
communication environments. Also see Bluetooth Resource Center.
Bluetooth clock
Every Bluetooth unit has an internal system clock which determines the timing and hopping
of the transceiver. It is never adjusted or turned off. It can be implemented as a 28-bit
counter, with the LSB ticking in units of 312.5us, giving a clock rate of 3.2kHz.
BT
Bluetooth (unofficial short form).
business card
The electronic date equivalent to a printed business card. This electronic version of the
business card is treated like a file and can be exchanged between Bluetooth devices.
CAC
Channel Access Code
CDMA
Code Division Multiple Access. CDMA is a digital cellular communications technology. Each
call has a individual code to identify the call. Multiple calls can be grouped together on a
single frequency. CDMA uses spread-spectrum techniques for handling radio
communications. CDMA is an improvement on AMPS and TDMA cellular service. Also see
CDMA Resource Center.
channel
A logical connection on the L2CAP level between two devices serving a single application or
higher layer protocol.
This is a pseudo-random sequence of 79 (23 for the 23MHz system) frequencies, The
frequency is calculated using the BD_ADDR of the master of the piconet. The phase in the
sequence is derived from an estimate of the master's clock. The channel hopping sequence
has a very long period length, does not show repetitive patterns over a short time interval,
but which distributes the hop frequencies equally over the 79 (23 for the 23MHz system) MHz
during a short time interval .See also Frequency sequence.
Circuit Switched
The application of a network where a dedicated line is used to transmit information. Only one
user may employ the resources of the line at a time.
CL
Connectionless.
class of device
See Bluetooth device class. Also abbreviated as CoD.
CLK
Clock, typically the master device clock which defines the timing used in the piconet.
CLKE
Clock Estimate, a slave's estimate of the master's clock, used to synchronise the slave
device to the master.
CLKN
Clock Native, the clock of the current Bluetooth Device
CO
Connection-oriented.
CoD
Class of Device.
connectable device
A Bluetooth device in range that will respond to a page message and set up a connection
CP
Capability Provider. A Capability Provider is a module within the local device that provides a
service to other modules. Protocol stack modules (RFCOMM, L2CAP) are Capability
Providers. So are "application interface modules" such as OBEX and ESC-AT. In fact, any
module that registers a port that other modules can connect to is a Capability Provider.
CRC
Cyclic Redundancy Check. This is a 16-bit code added to the packet to determine whether
the payload is correct or not. CRC data payloads can be carried only be DM, DH or DV
packets. The CRC code is generated by the CRC-CCITT polynomial 0x11021 (hex).
CTP
Cordless Telephone Profile.
CVSD
Continuous Variable Slope Delta Modulation.
DAC
Device Access Code. It is used during page, page scan and page response substates. It is a
code derived from the unit's BD_ADDR.
DCI
Default Check Initialisation. Within Bluetooth , the DCI is defined to be 0x00 (hexadecimal).
DCID
Destination Channel Identifier, used as the device local end point for an L2CAP transmission.
It represents the channel endpoint on the device receiving the message. It is a device local
name only. See also SCID.
destination
The Bluetooth device receiving an action from another Bluetooth device. The device sending
the action is called the source. The destination is typically part of an established link, though
not always ( such as in inquiry / page procedures).
Device Discovery
The mechanism to request and receive the Bluetooth address, clock, class of device, used
page scan
, and names of devices.
device name
See Bluetooth device name.
DH
Data-High Rate. An ACL link data packet type for high rate data. DH1 packets are similar to
DM1 packets, except the info in the payload is not FEC encoded. This means the DH1
packet can carry up to 28 info bytes and covers a single time slot. The DH3 is the same
except it can cover up to 3 time slots and contain up to 185 info bytes. The DH5 packet is the
same again except it can cover up to 5 time slots and contains up to 341 info bytes See also
Bluetooth packet types.
DIAC
Dedicated Inquiry Access Code, used when you wish to inquire for certain, specific types of
devices.
discoverable device
A Bluetooth device in range that will respond to an inquiry message
DLCI
Data Link Connection Identifier. This is a 6-bit value representing an ongoing connection
between a client and a server application. It is used in the RFCOMM layer.
DM
Data - Medium Rate. An ACL link data packet type for medium rate data. DM1 packets carry
information data only, contining a 16-bit CRC code and up to 18 info bytes. They are
encoded using 2/3 FEC and the packet can cover up to a single time slot. DM3 packets are
the same except they can cover up to 3 time slots, and can carry up to 123 info bytes. DM5
packets are the same again except they can cover up to 5 time slots and can hold up to 226
info bytes. See also Bluetooth packet types.
DSR
Data Set Ready. A device sets an RS-232 DSR signal when it is ready to accept data.
DT
Data Terminal.
DV
Data Voice. A SCO link data packet type for data and voice.It is divided into a voice field of
80 bits and a data field of 150 bits. The voice field is not covered by FEC, but the data field is
covered by 2/3 FEC. The voice and data fields are treated completely separate. The voice
field is handled like normal SCO data and is never retransmitted; that is, the voice field is
always new. The data field is checked for errors and is retransmitted if necessary. See also
Bluetooth packet types.
ETSI
European Telecommunications Standards Institute.
FEC
Forward Error Correction. The purpose of the FEC scheme on the data payload is to reduce
the number of retransmissions. Within Bluetooth , there are 2 versions of this, 1/3 FEC and
2/3 FEC. 1/3 FEC is a simple 3-times repetition of each info bit. 2/3 FEC is a (15,10)
shortened Hamming code.
FH
Frequency Hopping.
FHS
Frequency Hopping Synchronization. This a special control packet revealing, among other
things, the BD_ADDR and the clock of the source device. It contains 144 info bits and a 16-
bit CRC code. The payload is coded with a rate 2/3 FEC which brings the total payload
length to 240 bits. The FHS packet covers a single time slot. See also Bluetooth packet
types.
FIFO
First In, First Out.
The individual hopping sequences include the page sequence and the page response
sequence, these are used in the page procedure. Used in the inquiry procedure are the
inquiry sequence and the inquiry response sequence. Finally the main hopping
sequence used in the bluetooth system is the channel hopping sequence
GAP
Generic Access Profile. This profile describes the mechanism by which one device discovers
and accesses another device when they do not share a common application.
GFSK
Gaussian Frequency Shift Keying. This is the modulation used in the radio layer of the
Bluetooth system.
GIAC
General Inquire Access Code. The default inquiry code which is used to discover all devices
in range.
GM
Group Management.
GOEP
Generic Object Exchange Profile.
GSM
Global System for Mobile communications. GSM is a digital cellular communications
technology that is available in Europe and the US. GSM offers multiple services for the
subscriber such as short message service.
GW
Gateway. A Bluetooth enabled basestation which is connected to an external network.
HCI
Host Controller Interface. An (application-optional) layer which provides a command interface
to the LMP and Baseband layers.
headset
A microphone and earpiece used to conduct conversations. Headsets can be connected
directly to a cellular device or remotely using Bluetooth communications technology.
HEC
Header-Error-Check. An 8-bit word normally generated by using the UAP of the master
device. There are 2 exceptions: in the case of FHS packets using the master page response,
the slave UAP is used and for FHS packets sent in inquiry response the DCI value is used.
hold mode
Devices synchronised to a piconet can enter power-saving modes in which device activity is
lowered. The master unit can put slave units into HOLD mode, where only an internal timer is
running. Slave units can also demand to be put into HOLD mode. Data transfer restarts
instantly when units transition out of HOLD mode. It has an intermediate duty cycle (medium
power efficient ) of the 3 power saving modes (sniff, hold & park).
HS
Headset.
HV
High quality Voice. A SCO link voice packet. HV1 packets carry 10 info bytes, which are
protected by 1/3 FEC. HV2 packets carry 20 info bytes, and are protected by 2/3 FEC. HV3
packets carry 30 info bytes, and not protected by FEC. HV packets do not have a CRC or
payload header.See also Bluetooth packet types.
IAC
Inquiry Access Code. Used in inquiry procedures, can be one of 2 types: Dedicated IAC, for
specific devices, or Generic IAC for all devices.
ID packet
A 68-bit packet used in paging , inquiry and response routines. It is essentially the device
access code (DAC) or inquiry access code (IAC). See also Bluetooth packet types.
Idle mode
A device is in idle mode when it has no established links to other devices. In this mode, the
device may discover other devices. In general, a device sends inquiry codes (GIAC, DIAC to
other devices. Any device that allows inquiries will respond with information. The devices
may then decide to form a link.
IEEE
Institute of Electronic and Electrical Engineering.
Inquiry Procedure
The inquiry procedure enables a device to discover which devices are in range, and
determine the addresses and clocks for the devices. The inquiry procedure involve a unit (the
source)sending out inquiry packets (inquiry state) and then receiving the inquiry reply .The
unit that receives the inquiry packets (the destination), will hopefully be in the inquiry scan
state to receive the inquiry packets. The destination will then enter the inquiry response
state and send an inquiry reply to the source. After the inquiry procedure has completed, a
connection can be established using the paging procedure.
Inquiry State
When a device wishes to discover new devices , it enters the inquiry state, where it
broadcasts inquiry packets (ID packets), containing the IAC, to all devices in range. It will
send these using the inquiry hopping sequence. The device in the Inquiry state can also
receive inquiry replies (FHS packets), however it will not acknowledge these packets.
ISM
Industrial, Scientific, Medical.
ITU
International Telecommunication Union. http://www.ituaj.jp/index-e.html
known device
A device for which at least the BD_ADDR is stored.
L2CAP
Logical Link Controller and Adaptation Protocol. This protocol supports higher level protocol
multiplexing, packet segmentation and reassembly, and the conveying of quality of service
information.
L_CH
Logical Channel.
LAN
Local Area Network.
LAP
LAN Access Point.
LAP
Lower Address Portion. A 24-bit section of the BD_ADDR.See also NAP & UAP.
LC
Link Controller. The Link Controller manages the link to the other Bluetooth devices. It is the
low-level baseband protocol handler.
LC Channel
Link Control control channel. One of the 5 logical channels defined for the bluetooth system.
It is mapped onto the packet header. It control low level link control info. The LC is carried in
every packet except the ID packet which has no packet header.
LFSR
Linear Feedback Shift Register. Used in bluetooth to generate the HEC and CRC.
link key
The authentication key used to establish a link between devices. See also bonding.
LM
Link Manager. The Link Manager software entity carries out link setup, authentication, link
configuration, and other protocols.
LM Channel
Link Manager control channel. One of the 5 logical channels defined for the bluetooth
system. It carries control info exchanged between the link managers of the master and the
slave(s). It can be carried by either the SCO or ACL link.
LMP
Link Manager Protocol. The LMP is used for link setup and control. The LMP PDU signals
are interpreted and filtered out by the Link Manager on the receiving side and are not
propagated to higher layers.
LMP-authentication
An LMP level procedure for verifying the identity of a remote device. The procedure is based
on a challenge-response mechanism using a random number, a secret key and the
BD_ADDR of the non-initiating device. The secret key used can be a previously exchanged
link key or an initialization key created based on a PIN (as used when pairing).
LMP-pairing
A LMP procedure that authenticates two devices based on a PIN and subsequently creates a
common link key that can be used as a basis for a trusted relationship or a (single) secure
connection. The procedure consists of the steps:
1: creation of an initialization key (based on a random number and a PIN),
2: LMP-authentication based on the initialisation key and
3: creation of a common link key.
Logical Channel
There are 5 logical channels defined for the Bluetooth system. The LC & LM control
channels, and the UA, UI & US user channels.The LC channel is carried in the packet
header, all other channels are carried in the packet payload. See the individual sections for
more details.
LSB
Least Significant Bit.
MAC Address
3-bit address to distinguish between units participating in the piconet. Within Bluetooth, this is
the AM_ADDR .
MAN
Metropolitan Area Network.
master device
A device that initiates an action or requests a service on a piconet. Also the device in a
piconet whose clock and hopping sequence are used to synchronize all other devices in the
piconet.See also LocDev.
MS
Mobile Station. A generic term for the mobile device in question (GSM phone, Bluetooth
device etc).
MSB
Most Significant Bit.
MSC
Message Sequence Chart.
MT
Mobile Terminal, same as Mobile Station.
MUX
Multiplexing Sublayer. A sublayer of the L2CAP layer.
Name Discovery
The mechanism to request and receive a device name.
NAP
Non-significant Address Portion. A 16-bit section of the BD_ADDR. See also LAP & UAP.
non-connectable device
A device that does not responds to paging is said to be in non-connectable mode. The
opposite of a non-connectable device is a connectable device.
non-discoverable device
A device that cannot respond to an inquiry is said to be in non-discoverable mode. The
device will not enter the inquiry response state in this mode.
NULL packet
A 126-bit packet consisting of the CAC and packet header only. It is used to return link
information to the source. The NULL packet does not have to be acknowledged .See also
Bluetooth packet types.
OBEX
Object EXchange Protocol.
Packet Format
Each packet consists of 3 entities, the access code, the packet header and the payload.
Their are a number of different packet types.
Packet Header
The header contains link control info and consists of 6 fields: AM_ADDR : active member
address, TYPE : type code , FLOW : flow control, ARQN : acknowledge indication, SEQN :
sequence number & HEC : header error check. The total size of the header is 54-bits.
Packet Switched
A network that routes data packets based on an address contained in the data packet is said
to be a packet switched network. Multiple data packets can share the same network
resources.
Packet type
13 different packet types are defined for the baseband layer of the Bluetooth system. All
higher layers use these packets to compose higher level PDU's. The packets are ID, NULL,
POLL, FHS , DM1 ; these packets are defined for both SCO and ACL links. DH1, AUX1,
DM3, DH3, DM5, DH5 are defined for ACL links only. HV1, HV2, HV3 , DV are defined for
SCO links only
master and slave use different rules to obtain the same sequence. See also Frequency
sequence.
Step 2:When the source has received the second reply (Page Slave Response State:
Step2), it knows that the destination device has received the FHS packet the source sent in
Step 1. The source is now the master of the destination (the slave).
Step 2:Once the destination device has received the FHS packet from the source ,(Page
Master Response State: Step 1), the destination will send a reply to the source (an ID
packet containing the destination DAC).
Step 3: The destination will switch to the source's channel params. The destination is now
the slave of the source (the master).
Page State
A mode that a device enters when searching for other devices. The device sends out a page
packet (ID packet), using the page hopping sequence, to notify other devices that it wants to
know about the other devices and/or their services.
Paging Procedure
With the paging procedure, an actual connection can be established. The paging procedure
typically follows the inquiry procedure. Only the Bluetooth device address is required to set
up a connection. Knowledge about the clock (clock estimate) will accelerate the setup
procedure. A unit that establishes a connection will carry out a page procedure and will
automatically be the master of the connection. The procedure occurs as follows:
1: A device (the source) pages another device (the destination ) : Page state
3: The destination sends a reply to the source. : Slave Response state: Step 1
4: The source sends an FHS packet to the destination : Master Response state: Step 1
5: The destination sends it's second reply to the source. : Slave Response state : Step 2
6: The destination & source then switch to the source channel parameters :Master
Response state: Step 2 & Slave Response state: Step 3
pairable mode
A device that accepts pairing, is said to be in pairable mode. The opposite of pairing mode is
non-pairable mode.
pairing
The creation and exchange of a link key between two devices. The devices use the link key
for future authentication when exchanging information.
park mode
In the PARK mode, a device is still synchronized to the piconet but does not participate in the
traffic. Parked devices have given up their MAC (AM_ADDR) address and occasional listen
to the traffic of the master to re-synchronize and check on broadcast messages. It has the
lowest duty cycle (power efficiency) of all 3 power saving modes (sniff, hold & park).
payload format
Each packet payload can have one of 2 possible fields, the data field (ACL) or the voice field
(SCO). The different packets, depending on whether they are ACL or SCO packets can only
have one of these fields. The one exception is the DV packets which have both. The voice
field has a fixed length field, with no payload header. The data field consists of 3 segments: a
payload header, a payload body and a CRC code (with the exception of the AUX1 packet).
PCM
Pulse Coded Modulation.
PDU
Protocol Data Unit. (i.e., a message.)
Physical link
A synchronized Bluetooth baseband-compliant RF hopping sequence. It is a baseband level
association between two devices established using paging. A physical link comprises a
sequence of transmission slots on a physical channel alternating between master and slave
transmission slots.
Piconet
A collection of devices connected via Bluetooth technology in an ad hoc fashion. A piconet
starts with two connected devices, such as a portable PC and cellular phone, and may grow
to eight connected devices. All Bluetooth devices are peer units and have identical
implementations. However, when establishing a piconet, one unit will act as a master and the
other(s) as slave(s) for the duration of the piconet connection. All devices have the same
physical channel defined by the master device parameters (clock and BD_ADDR).
PIN
Personal Identification Number. The Bluetooth PIN is used to authenticate two devices that
have not previously exchanged link key. By exchanging a PIN, the devices create a trusted
relationship. The PIN is used in the pairing procedure to generate the initial link that is used
for further identification.
PIN(BB)
The PIN used on the baseband level. The PIN(BB) is used by the baseband mechanism for
calculating the initialization key during the pairing procedure. (128 bits)
PIN(UI)
The PIN used on the user interface level. The PIN(UI) is the character representation of the
PIN that is entered on the UI level.
PM_ADDR
Parked Member Address. It is a 8-bit member (master-local) address that separates the
parked slaves.The PM_ADDR is only valid as long as the slave is parked.
POLL packet
Similar to the NULL packet, except it requires a confirmation from the destination. Upon
reception of a POLL packet the slave must respond with a packet. See also Bluetooth packet
types
PPP
Point to Point Protocol.
PRBS
Pseudorandom Bit Sequence.
Profile
A description of the operation of a device or application.
PSTN
Public Switched Telephone Network. The general phone network.
QoS
Quality of Service.
Radio
The Radio layer of the Bluetooth system, the lowest defined layer. It details the requirements
needed for a Bluetooth device transceiver to operate in the Bluetooth radio band . 2 different
ranges have been defined for the radio layer, a 23MHz range and a 79MHz range , both are
in the 2.4GHz ISM band. The 23MHz range is only used in certain countries (such as Spain,
France) , that have national limitations on the amount of frequencies available. Different hop
systems are used for both.
RF
Radio Frequency.
RFCOMM
Serial Cable Emulation Protocol based on ETSI TS 07.10.
RS-232
A serial communications interface. Serial communication standards are defined by the
Electronic Industries Association (EIA).
RSSI
Received Signal Strength Indication. An optional part of the radio layer, used to determine
the link quality and thus whether to increase broadcast power.
RTX Timer
The Response Timeout eXpired timer used in the L2CAP layer to terminate the channel
when the remote endpoint is unresponsive to signalling requests. It is started when a
signalling request is sent to a remote device.
RX
Receiver.
S
Short for Slave. See slave device.
SAP
Service Access Points.
SAR
Segmentation and Reassembly. A sublayer of the L2CAP layer.
Scatternet
Multiple independent and non-synchronized piconets form a scatternet.
SCO
Synchronous Connection Oriented link. One of the 2 bluetooth data link types defined.A
synchronous (circuit-switched) connection for reserved bandwidth communications, e.g.
voice, between two devices created on the LMP level by reserving slots periodically on a
physical channel. This type of link is used primarily to transport SCO packets (voice data).
SCO packets do not include a CRC and are never retransmitted. It primarily supports time-
bounded information like voice. (Master to single slave.) SCO links can be established only
after an ACL link has first been established. See also ACL.
SCID
Source Channel Identifier. Used in the L2CAP layer to indicate the channel endpoint on the
device sending the L2CAP message. It is a device local name only. See also DCID.
SDAP
Service Discovery Application Profile.
SDDB
Service Discovery Database.
SDP
Service Discovery Protocol. It is a Bluetooth defined protocol for provided for or available
through a Bluetooth device. Essentially provides a means for applications to discover which
services are available and to determine the characteristics of those available services.
SDP client
The SDP client may retrieve information from a service record maintained by the SDP server
by issuing an SDP request.
SDP server
The SDP server maintains a list of service records that describe the characteristics of
services associated with the server.
SDP Session
The exchange of information between an SDP client and an SDP server. The exchange of
information is referred to as an SDP transaction.
SDP Transaction
The exchange of an SDP request from an SDP client to an SDP server, and the
corresponding SDP response from an SDP server back to the SDP client.
Security Mode 1
A device will not initiate any security. A non-secure mode.
Security Mode 2
A device does not initiate security procedures before channel establishment on L2CAP level
This mode allows different and flexible access policies for applications, especially running
applications with different security requirements in parallel. A service level enforced security
mode.
Security Mode 3
A device initiates security procedures before the link setup on LMP level is completed. A link
level enforced security mode.
SEQN
Sequential Numbering scheme. It provides a sequential numbering scheme to order the data
packet stream.
Serial Interface
An interface to provide serial communications. service This term refers to a service that one
device provides for others. Examples are printers, PIM. synchronization servers, modems (or
modem emulators).
Service Attribute
Service Discovery
See SDP.
Service Class
Each service is an instance of a service class. The service class definition provides the
definitions of all attributes contained in service records that represent the instances of that
class.
Service Layer
The group of protocols that provides services to the application layer and the driver layer in a
Bluetooth device.
Service Record
A service record contains all of the information about a service that is maintained by an SDP
server.
SIG
Special Interest Group. The Bluetooth SIG is located at www.bluetooth.com.
slave device
A device in a piconet that is not the master.There can be many slaves per piconet.
sniff mode
Devices synchronized to a piconet can enter power-saving modes in which device activity is
lowered. In the SNIFF mode, a slave device listens to the piconet at reduced rate, thus
reducing its duty cycle. The SNIFF interval is programmable and depends on the application.
It has the highest duty cycle (least power efficient ) of all 3 power saving modes (sniff, hold &
park).
source
The Bluetooth device initiating an action to another Bluetooth device. The device receiving
the action is called the destination. The source is typically part of an established link, though
not always ( such as in inquiry / page procedures).
SR
Scan Repetition. A mode used in the baseband layer to determine how long the device will
continue to scan for a page response
TCP/IP
Transport Control Protocol/Internet Protocol.
TCS
Telephone Control protocol Specification.
TCS-AT
A set of AT-commands by which a mobile phone and modem can be controlled in the
multiple usage models. In BT, AT-commands are based on ITU-T recommendation v.250
and ETS 300 916(GSM 07.07). In addition, the commands used for fax services are specified
by the implementation. TCS-AT will also be used for dial-up networking and headset profiles.
TCS Binary
Bluetooth Telephony Control protocol Specification using bit-Oriented protocol. It is also
referred to as the TCS-BIN system. TCS-BIN will be used for cordless telephony profiles.
TDD
Time Division Duplex
TGAP
Timer used in the General Access Profile (GAP).
time slot
A single time slot in the Bluetooth system lasts 625us. It can be though of as the time it takes
to send one packet from one Bluetooth device to another
TTP
Tiny Transport Protocol between OBEX and UDP [TBD].
TX
Transmit.
UA Channel
User Asynchronous data channel. One of the 5 logical channels defined for the bluetooth
system. The UA channel carries L2CAP transparent asynchronous user data. It is normally
carried in the ACL link.
UAP
Upper Address Portion. A 8-bit section of the BD_ADDR. See also LAP & NAP.
UART
Universal Asynchronous Receiver Transmitter. A device which converts parallel data into
serial data for transmission, or it converts serial data into parallel data for receiving data.
UC
User Control.
UDP/IP
User Datagram Protocol/Internet Protocol.
UI Channel
User Isochronous data channel. One of the 5 logical channels defined for the bluetooth
system. The UI channel carries L2CAP transparent isochronous user data. It is normally
carried in the ACL link. It is supported by timing start packets at higher levels
UMTS
Universal Mobile Telecommunications System. Also see 3G Resource Center.
US Channel
User Synchronous data channel. One of the 5 logical channels defined for the bluetooth
system. The UI channel carries transparent synchronous user data. It is carried in the SCO
link only.
UUID
Universal Unique Identifier. Used in the SDP layer.
WAN
Wide Area Network.
WLAN
Wireless Local Area Network. Also see IEEE 802.11 Resource Center.
Find
Bluetooth Resource Center Advanced search
What Is
Bluetooth?
Members
Have you visited our Bluetooth Articles section yet?
Have you visited
Current topics: our Wireless
Member: Bookshop yet?
● CATHAL'S CORNER: Future versions of Bluetooth - Bluetooth
Password:
1.2 & Bluetooth 2.0 The recent release of cores based on
preliminary Bluetooth 1.2 and speculation on the abilities of Top Bluetooth Sites
Bluetooth 2.0, means that far-sighted developers should not
Login
stand still in approaching Bluetooth optimisations. This article Thank you for your
explains the features on a broad level of Bluetooth 1.2 and support in making us
Forgot your examines the reports on Bluetooth 2.0. more... one of the top Bluetooth
sites on the web!
password?
● Bluetooth Additional Profiles - Overview
New Member
Currently in the final stages of evaluation and approval, the
Bluetooth SIG is in the process of releasing 12 new profiles.
In conjunction with this, palowireless has also published on- CATHAL'S CORNER
line new tutorials to these profiles. However, with the
proliferation of profiles and acronyms it is sometimes hard to This month's topic:
see what these profiles are designed to do. As an entry-level
introduction, this article gives a very brief outline of these new Future versions of
profiles and what roles they will allow Bluetooth units to fill. Bluetooth - Bluetooth
more... 1.2 & Bluetooth 2.0
Have you
● Bluetooth and IEEE 802.11b
visited our
WAP Although aimed at different markets and roles, there has long
been speculation about the effects 802.11b (also called Wi-Fi,
Games
IEEE 802.11, Wireless LAN etc.) and Bluetooth have on each
section yet? other, not just technical interference, but also whether they
are in competition with each other commercially. Often these
are simplistic press reports attempting to compare the two
and seeking to decide a winner. This article however explains
the similarities and differences between Bluetooth & 802.11b
on a broad level and tries to show that there is no serious
competition between the two. In fact both have their own
advantages and disadvantages, and both technologies can
complement each other. more...
Find
Bluetooth Resource Center Advanced search
Subscribe
Technology
Bluetooth News and Articles Recent Bluetooth
Headlines
Testing
Training 2003
PRWeb XEMICS Looking
Tutorial
● Bluetooth SIG Bluetooth Core to Expand Presence in
WLANs & BT
Specification Version 1.2 (11/03) India through Aarjay
The Bluetooth SIG announces the XEMICS has appointed
What Is Aarjay International Pvt.
availability of the Bluetooth Core
Bluetooth? Specification Version 1.2. It has Ltd. as Indian distributor
been delivered as announced in the for their complete range of
Fall of 2003, tested and is market ultra low power
ready. The newest Core semiconductors for
Specification introduces many new Wireless, Sensing, GPS
Members innovative features that required and Bluetooth? systems.
countless hours of work and [PRWEB Oct 28, 2003]
compromise. Features like Adaptive
Frequency Hopping have not only Computerworld A touch
Member: made the technology better, but of gray in Bluetooth's
promote good citizenship in the silver lining
Password:
unlicensed spectrum for other
Bluetooth, the short-range
technologies.
wireless technology, is
showing signs of technical
Login ● Ericsson Ericsson awarded improvements and growing
Bluetooth license agreement by adoption, but it faces new
Forgot your Winbond (11/03) Ericsson challenges from other
password? Technology Licensing today wireless technologies.
announced a licensing agreement
New Member with Winbond, a leading Computerworld A touch
semiconductor manufacturer from of gray in Bluetooth's
Taiwan. The license agreement silver lining
covers the Ericsson Core Bluetooth
Bluetooth, the short-range
Radios KE-1 and KD-1. The license
wireless technology, is
agreement enables Winbond to
showing signs of technical
design and manufacture complete
improvements and growing
Bluetooth solutions together with a
adoption, but it faces new
proprietary baseband. Winbond can
challenges from other
tailor Ericsson's solutions for all of
wireless technologies.
the major Bluetooth applications
such as human interface devices,
headsets and mobile phones. allNetDevices Intel
Purchases Bluetooth, Wi-
● Silicon Wave Silicon Wave and RF Fi Developer
Earlier News
Find
Bluetooth Resource Center Advanced search
Subscribe
Technology
Testing
Training
Tutorial
WLANs & BT
What Is
Bluetooth?
Members
Member:
Password:
Bluetooth Products and Solutions - announced
Login
These are announced Bluetooth products and solutions
Forgot your which may not yet be qualified. See below for qualified
password? products.
Developers of Bluetooth-based
wireless communication solutions
Airlogic Co Ltd including Bluetooth USB IP Share,
USB Dongle & Flash Memory, USB
Serial Adapter and Bluetooth USB
Headset.
Air2Net Bluetooth solutions PC
AmbiCom Card, CompactFlash Card, USB
Adapter, Home Gateway.
Bluetooth products providing users
with a complete end-to-end wireless
solution. From PC Cards to CF
AnyCom
Cards to Palm Pilot Sleeves, the
world's first Printer Module and an
up coming Access Point.
The Axis 9010 is a wireless access
Axis Communications point based on the Bluetooth
specification, supporting both voice
and data.
Hardware and software solutions for
networking within the Bluetooth
Blue2Net
standard, providing a complete
family of services and products.
Wireless Remote Access Platform is
an integrated hardware and software
solution. It combines standard
Networking and Internet
technologies and the Bluetooth
wireless technology in a turn-key
platform enabling remote access to
devices and systems. WRAP
products can intelligently and
BlueGiga
independently run all needed
protocols and application software
without the need for a host
processor. It is designed to
significantly lower the investment
Bluetooth PC-Card
Bluetooth Printer Adaptor
NEC Corporation
(11/00)
Nokia LRB-1 Components (12/00)
Siemens Bluetooth Radio
Siemens
SurfBlue Bluetooth Software
Stack
Find
Bluetooth Resource Center Advanced search
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Bluetooth Tutorial - Profiles
Consulting The profiles have been developed in order to describe how implementations of
Database user models are to be accomplished. The user models describe a number of user
scenarios where Bluetooth performs the radio transmission. A profile can be
described as a vertical slice through the protocol stack. It defines options in each
protocol that are mandatory for the profile. It also defines parameter ranges for
Bluetooth each protocol. The profile concept is used to decrease the risk of interoperability
Antennas problems between different manufacturers' products.
Articles
Asia-Pacific Note: A number of additional Bluetooth profiles are currently in the final stages
Audio of development. To stay up to date check this page regularly or subscribe to our
Bluetooth Newsletter.
Books
Cathal's Corner
Consultants Bluetooth Profile Dependencies:
Design Tools
Dev Tools
Downloads
Events
FAQ
Forums
Glossary
InfoTooth
News
Products
Profiles
Research
Security
SIG
Shop
Subscribe
Technology
Testing
Training
Tutorial
WLANs & BT
What Is
Bluetooth?
Members
Member:
Password:
Login
Forgot your
password?
New Member Click on a section of the diagram* above, for a tutorial of its functions
The Bluetooth profile structure and the dependencies of the profiles are
depicted above. A profile is dependent upon another profile if it re-uses parts of
that profile, by implicitly or explicitly referencing it. Dependency is illustrated in the
figure: a profile has dependencies on the profile(s) in which it is contained –
directly and indirectly. For example, the Object Push profile is dependent on
Generic Object Exchange, Serial Port, and Generic Access profiles.
Service Discovery
K2 SDAP 1.1
Application Profile
Cordless Telephony
K3 CTP 1.1
Profile
K4 IP 1.1 Intercom Profile
K5 SPP 1.1 Serial Port Profile
K6 HS 1.1 Headset Profile
K7 DNP 1.1 Dial-up Networking Profile
K8 FP 1.1 Fax Profile
LAN (Local Area Network)
K9 LAP 1.1
Access Profile
Generic Object Exchange
K10 GOEP 1.1
Profile
K11 OPP 1.1 Object Push Profile
K12 FTP 1.1 File Transfer Profile
K13 SP 1.1 Synchronization Profile
Extended Service
Available Now ESDP 0.95a Discovery Profile (for
Universal Plug and Play)
Premium Advanced Audio
A2DP 0.95b
Access * Distribution Profile
Premium Audio Video Remote
AVRCP 0.95b
Access * Control Profile
Premium
BIP 1.0 Basic Imaging Profile
Access *
Premium
BPP 0.95a Basic Printing Profile
Access *
Premium Common ISDN Access
CIP 1.0
Access * Profile
Note: Check out the information available in our Bluetooth Articles and
Documentation page, for overviews and details on the different layers.
ss
Bluetooth IN: & All Products
1 2 3 4 5 6 7 8 9 10 next>>
Find
Wireless Resource Center Advanced search
Member:
Password:
Login
Forgot your
password?
New Member
Useful Time
Zone Links
NSW, Australia
China
Denmark
Finland
India
Ireland
Korea
Japan
Malaysia
Sweden
UK
USA East
USA West
Find
Bluetooth Resource Center Advanced search
Bluetooth
Antennas ● www.bluetooth.com/ The Bluetooth public web site (and old
Articles members area < Aug 2000)
Asia-Pacific ❍ Bluetooth SIG
Audio
❍ Press Releases
Books
Cathal's Corner
● www.bluetooth.org Members Area
Consultants
❍ Stay tuned for more links and news soon!
Design Tools
Dev Tools
Downloads
Events
FAQ Useful Links to SIG Promoters
Forums
Glossary
InfoTooth
News 3Com (COMS)
Products
Profiles
Research
Security
Shop
SIG
Forgot your
password?
New Member
Find
Advanced search
Bluetooth Resource Center
[ Also see: Shop for GPS products Shop for WLAN products ]
Home
Bookshop
Market Research
Search
Add a Link
Shop Online For Bluetooth Products
Consulting
Database Looking for a Bluetooth headset or a card for a PC or
notebook? Then look no further!
What Is
Bluetooth?
Members
Member:
Password:
Login
Forgot your
password?
New Member
Find
Wireless Resource Center Advanced search
Members
Member:
Password:
Login
Forgot your
password?
New Member
Pages Served:
Find
Bluetooth Resource Center Advanced search
FAQ
Forums Technical Articles:
Glossary
InfoTooth ● African Cellular
News ❍ Preventing Bluetooth Interference
Products
Profiles ● BTDesigner
Research
❍ Bluetooth Technology, Applications and Compatibility
Security
(Word Doc, 800kb)
Shop
SIG What is Bluetooth? Is it the technology? Is it the
(PDF)
Member: ● CETECOM
❍ Bluetooth Type Approval Site is a web site developed
Specification
❍ Bluetooth – Wireless Local Access
● Counterpoint Systems
❍ IrDA versus Bluetooth: A Complementary Comparison
● DevX
❍ Make Bluetooth Work for You (4/03) Build a Sample
Chat Application Learn how to write applications that
● EE Times
❍ Piecing Together the Bluetooth/Mobile Phone Puzzle
● Ericsson
❍ Bluetooth Pages
● Extended Systems
❍ Synchronization in Bluetooth (PDF)
● ExtremeTech
❍ Bluetooth Real World (7/02) Right now in order to get
● Intel
❍ Bluetooth Architecture Overview
❍ Architectural Overview of Intel's Bluetooth Software
Stack
❍ Integrating Bluetooth Technology into Mobile Products
● ISPWorld
❍ Breaking The 2.4 GHz Traffic Jam ...the IEEE formed a
● Marcin Michalak
● Microsoft
❍ Bluetooth information about Bluetooth and Windows®
operating systems
❍ Windows CE Features for Platform Developers
● Motorola
❍ Motorola Bluetooth
❍ Bluetooth Glossary
● RFGlobalNet
❍ Building a Bluetooth Radio
■ Process technology
■ Performance
■ Technological Issues
● Sun
❍ JSR-000082 Java APIs for Bluetooth
The specification will standardize a set of Java APIs to
allow these Java-enabled devices to integrate into a
Bluetooth environment.
● WLAN Association
❍ Reliability of IEEE 802.11 Hi Rate DSSS WLANs in a
● ZDNet
❍ Bluetooth versus WLANs If asked to construct a
Find
Bluetooth Resource Center Advanced search
What Is
Bluetooth?
RF Testing
comms.
Download BlueHoc
2026A/B MultiSource Generator with
Bluetooth test capability.
Multi-Source Signal Generator for
Bluetooth. For critical Bluetooth
interoperability testing, the 2026B with
Bluetooth Option 117 is more cost
IFR effective than buying two or three
separate signal sources. The 2026B
multi-source generator with Bluetooth
allows the user to simultaneously
generate two Bluetooth modulated
carriers and one GSM carrier in a
single instrument.
IVT interoperability and conformance
testers.
Bluetooth services
Testhouse and Certification center.
Bluetooth Services: Testing,Blue Unit
Tester, Protocol/Profile Tester,
Validation AB
Bluetooth qualification and
Interoperability testing services
Bluetooth Pre-Qualification testing.
Interesting Articles:
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Bluetooth Radio
Consulting The Bluetooth Radio (layer) is the lowest defined layer of the Bluetooth specification. It defines the
Database requirements of the Bluetooth transceiver device operating in the 2.4GHz ISM band.
For more details : Download the Radio Specification from the SIG website, or visit the Documents
Page.
Bluetooth
Antennas Table Of Contents
Articles
Asia-Pacific Frequency Bands and
Audio 1.1
Channel Arrangement
Books
Cathal's Corner 1.2 Transmitter Characteristics
Consultants 1.3 Receiver Characteristics
Design Tools
Dev Tools
Downloads
Events 1.1 Frequency Bands and Channel Arrangement
FAQ
Forums The Bluetooth radio accomplishes spectrum spreading by frequency hopping in 79 hops
Glossary displaced by 1 MHz, starting at 2.402GHz and finishing at 2.480GHz. In a few countries (i.e France)
InfoTooth this frequency band range is (temporarily) reduced, and a 23-hop system is used. In order to comply
News with out of band regulations in each country. In both systems a guard band is used at the lower and
Products upper band edge
Profiles
Research
Security
SIG 1.2 Transmitter Characteristics
Shop
Power Classes: Each device is classified into 3 power classes, Power Class 1, 2 & 3.
Subscribe
Technology
● Power Class 1: is designed for long range (~100m) devices, with a max output power of 20
Testing
dBm,
Training ● Power Class 2: for ordinary range devices (~10m) devices, with a max output power of 4 dBm,
Tutorial ● Power Class 3: for short range devices (~10cm) devices, with a max output power of 0 dBm.
WLANs & BT
The Bluetooth radio interface is based on a nominal antenna power of 0dBm. Each device can
What Is optionally vary its transmitted power.Equipment with power control capability optimizes the output
Bluetooth? power in a link with LMP commands (see Link Manager Protocol). It is done by measuring RSSI and
report back if the power should be increased or decreased.
Modulation Characteristics: The Bluetooth radio module uses GFSK (Gaussian Frequency Shift
Members Keying) where a binary one is represented by a positive frequency deviation and a binary zero by a
negative frequency deviation. BT is set to 0.5 and the modulation index must be between 0.28 and
0.35.
Member: Spurious Emissions: The spurious emission, in-band and out-of-band, is measured with a
frequency hopping transmitter hopping on a single frequency; this means that the synthesizer must
Password: change frequency between receive slot and transmit slot, but always returns to the same transmit
frequency.
Login
Radio Frequency Tolerance: The transmitted initial center frequency accuracy must be ±75 kHz
from Fc. The initial frequency accuracy is defined as being the frequency accuracy before any
Forgot your
information is transmitted. Note that the frequency drift requirement is not included in the ±75 kHz.
password?
New Member
1.3 Receiver Characteristics
Sensitivity Level: The receiver must have a sensitivity level for which the bit error rate (BER)
0.1% is met. For Bluetooth this means an actual sensitivity level of -70dBm or better.
Interference Performance: The interference performance on Co-channel and adjacent 1 MHz and
2 MHz are measured with the wanted signal 10 dB over the reference sensitivity level. On all other
frequencies the wanted signal shall be 3 dB over the reference sensitivity level.
Have you
visited our Out-of-Band blocking: The Out of band blocking is measured with the wanted signal 3 dB over
WAP the reference sensitivity level. The interfering signal shall be a continuous wave signal. The BER
Games shall be less than or equal to 0.1%.
section yet?
Intermodulation Characteristics: The reference sensitivity performance, BER = 0.1%, shall be
met under the following conditions.
● The wanted signal at frequency f 0 with a power level 6 dB over the reference sensitivity level.
● A static sine wave signal at f 1 with a power level of –39 dBm
● A Bluetooth modulated signal at f 2 with a power level of -39 dBm
Such that f 0 =2f 1 -f 2 and |f 2 -f 1| =n*1 MHz, where n can be 3, 4, or 5. The system must fulfil
one of the three alternatives.
Maximum Usable Level: The maximum usable input level the receiver shall operate at shall be
better than –20 dBm. The BER shall be less or equal to 0,1% at –20* dBm input power.
RSSI: Receiver Signal Strength Indicator (Optional): A transceiver that wishes to take part in a
power-controlled link must be able to measure its own receiver signal strength and determine if the
transmitter on the other side of the link should increase or decrease its output power level. A
Receiver Signal Strength Indicator (RSSI) makes this possible. The way the power control is
specified is to have a golden receive power range. This golden receive power is defined as a
range with a lower and higher threshold levelsand a high limit. The lower threshold level
corresponds to a received power between -56 dBm and 6 dB above the actual sensitivity of the
receiver. The upper threshold level is 20 dB above the lower threshold level to an accuracy of +/- 6
dB. The instructions to alter the TX power are carried in the LMP link
Note , the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual Bluetooth
Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Bluetooth Baseband
Consulting
Database The Baseband is the physical layer of the Bluetooth. It manages physical channels and links
apart from other services like error correction, data whitening, hop selection and Bluetooth security.
The Baseband layer lies on top of the Bluetooth radio layer in the bluetooth stack. The baseband
protocol is implemented as a Link Controller , which works with the link manager for carrying out
Bluetooth link level routines like link connection and power control. The baseband also manages
Antennas asynchronous and synchronous links, handles packets and does paging and inquiry to access and
Articles inquire Bluetooth devices in the area. The baseband transceiver applies a time-division duplex
(TDD) scheme. (alternate transmit and receive). Therefore apart from different hopping frequency
Asia-Pacific
(frequency division), the time is also slotted.
Audio
Books
Cathal's Corner
Consultants For more details : Download the Baseband Specification from the SIG website, or visit the
Design Tools Documents Page.
Dev Tools
Downloads Table Of Contents
Events
FAQ Physical
Forums 2.1
Characteristics
Glossary
InfoTooth 2.1.1 Physical Channel
News 2.1.2 Physical Links
Products 2.1.3 Logical Channels
Profiles
2.1.4 Device Addressing
Research
Security 2.2 Packets
SIG 2.2.1 Packet Types
Shop
2.2.2 Packet Format
Subscribe
Technology Channel
2.3
Testing Control
Training 2.3.1 Controller States
Tutorial
2.3.1 Connection Setup
WLANs & BT
2.3.2 Connection Modes
What Is 2.3.4 Scatternet
Bluetooth?
Other
Members
2.4 Baseband
Functions
2.4.1 Error Correction
Member:
2.4.2 Flow Control
Password:
Login
2.1 Physical Characteristics
Forgot your 2.1.1 Physical Channel
password?
Bluetooth operates in the 2.4 GHz ISM band. In the US and Europe, a band of 83.5 MHz width is
New Member
available; in this band, 79 RF channels spaced 1 MHz apart are defined. In France, a smaller band
is available; in this band, 23 RF channels spaced 1 MHz apart are defined.
The channel is divided into time slots, each 625 us in length. The time slots are numbered
according to the Bluetooth clock of the piconet master.
A TDD scheme is used where master and slave alternatively transmit. The master shall start its
transmission in even-numbered time slots only, and the slave shall start its transmission in odd-
numbered time slots only. The packet start shall be aligned with the slot start.
The Baseband handles two types of links : SCO (Synchronous Connection-Oriented) and ACL
(Asynchronous Connection-Less) link. The SCO link is a symmetric point-to-point link between a
master and a single slave in the piconet. The master maintains the SCO link by using reserved slots
at regular intervals (circuit switched type). The SCO link mainly carries voice information. The
master can support up to three simultaneous SCO links while slaves can support two or three SCO
links. SCO packets are never retransmitted. SCO packets are used for 64 kB/s speech
transmission.
The ACL link is a point-to-multipoint link between the master and all the slaves participating on
the piconet. In the slots not reserved for the SCO links, the master can establish an ACL link on a
per-slot basis to any slave, including the slave already engaged in an SCO link (packet switched
type). Only a single ACL link can exist. For most ACL packets, packet retransmission is applied.
Bluetooth has five logical channels which can be used to transfer different types of information.
LC (Control Channel) and LM (Link Manager) channels are used in the link level while UA, UI and
US channels are used to carry asynchronous, isosynchronous and synchronous user information.
2.2 Packets
13 different packet types are defined for the baseband layer of the Bluetooth system. All higher
layers use these packets to compose higher level PDU's. The packets are ID, NULL, POLL, FHS ,
DM1 ; these packets are defined for both SCO and ACL links. DH1, AUX1, DM3, DH3, DM5, DH5
are defined for ACL links only. HV1, HV2, HV3 , DV are defined for SCO links only.
Each packet consists of 3 entities, the access code (68/72 bits), the header (54 bits) , and the
payload (0-2745 bits).
● Access Code: Access code are used for timing synchronization, offset compensation, paging
and inquiry. There are three different types of Access code: Channel Access Code (CAC),
Device Access Code (DAC) and Inquiry Access Code (IAC). The channel access code
identifies a unique piconet while the DAC is used for paging and its responses. IAC is used for
inquiry purpose.
● Header:The header contains information for packet acknowledgement, packet numbering for
out-of-order packet reordering, flow control, slave address and error check for header.
● Payload: The packet payload can contain either voice field, data field or both. It it has a data
field, the payload will also contain a payload header.
Bluetooth controller operates in two major states: Standby and Connection . There are seven
substates which are used to add slaves or make connections in the piconet. These are page, page
scan, inquiry, inquiry scan, master response, slave response and inquiry response .
The Standby state is the default low power state in the Bluetooth unit. Only the native clock is
running and there is no interaction with any device whatsoever. In the Connection state, the master
and slave can exchange packet , using the channel (master) access code and the master Bluetooth
clock. The hopping scheme used is the channel hopping scheme.The other states (page, inquiry etc
are described below)
Normally, a connection between two devices occur in the following fashion: If nothing is known
about a remote device, both the inquiry(1) and page(2) procedure have to be followed. If some
details are known about a remote device, only the paging procedure (2) is needed
Step 1:
The inquiry procedure enables a device to discover which devices are in range, and
determine the addresses and clocks for the devices.
The inquiry procedure involve a unit (the source) sending out inquiry packets (inquiry
1.1:
state) and then receiving the inquiry reply
The unit that receives the inquiry packets (the destination), will hopefully be in the
1.2:
inquiry scan state to receive the inquiry packets.
The destination will then enter the inquiry response state and send an inquiry reply to
1.3:
the source.
After the inquiry procedure has completed, a connection can be established using the paging
procedure.
Step 2:
With the paging procedure, an actual connection can be established. The paging procedure
typically follows the inquiry procedure. Only the Bluetooth device address is required to set up
a connection. Knowledge about the clock (clock estimate) will accelerate the setup procedure.
A unit that establishes a connection will carry out a page procedure and will automatically be
the master of the connection. The procedure occurs as follows:
The Connection state starts with a POLL packet sent by the master to verify that slave has
switched to the master's timing and channel frequency hopping. The slave can respond with any
type of packet.
A Bluetooth device in the Connection state can be in any of the four following modes: Active,
Hold, Sniff and Park mode.
● Active Mode: In the active mode, the Bluetooth unit actively participates on the channel. The
master schedules the transmission based on traffic demands to and from the different slaves.
In addition, it supports regular transmissions to keep slaves synchronized to the channel.
Active slaves listen in the master-to-slave slots for packets. If an active slave is not
addressed, it may sleep until the next new master transmission.
● Sniff Mode: Devices synchronized to a piconet can enter power-saving modes in which
device activity is lowered. In the SNIFF mode, a slave device listens to the piconet at reduced
rate, thus reducing its duty cycle. The SNIFF interval is programmable and depends on the
application. It has the highest duty cycle (least power efficient ) of all 3 power saving modes
(sniff, hold & park).
● Hold Mode: Devices synchronized to a piconet can enter power-saving modes in which
device activity is lowered. The master unit can put slave units into HOLD mode, where only an
internal timer is running. Slave units can also demand to be put into HOLD mode. Data
transfer restarts instantly when units transition out of HOLD mode. It has an intermediate duty
cycle (medium power efficient ) of the 3 power saving modes (sniff, hold & park).
● Park Mode: In the PARK mode, a device is still synchronized to the piconet but does not
participate in the traffic. Parked devices have given up their MAC (AM_ADDR) address and
occasional listen to the traffic of the master to re-synchronize and check on broadcast
messages. It has the lowest duty cycle (power efficiency) of all 3 power saving modes (sniff,
hold & park).
2.3.4 Scatternet
Multiple piconets may cover the same area. Since each piconet has a different master, the
piconets hop independently, each with their own channel hopping sequence and phase as
determined by the respective master. In addition, the packets carried on the channels are preceded
by different channel access codes as determined by the master device addresses. As more
piconets are added, the probability of collisions increases; a graceful degradation of performance
results as is common in frequency-hopping spread spectrum systems.
If multiple piconets cover the same area, a unit can participate in two or more overlaying piconets
by applying time multiplexing. To participate on the proper channel, it should use the associated
master device address and proper clock offset to obtain the correct phase. A Bluetooth unit can act
as a slave in several piconets, but only as a master in a single piconet. A group of piconets in which
connections consists between different piconets is called a scatternet.
Sometimes an existing master or slave may wish to swap roles (i.e a master-slave switch) , this
can take place in two steps:
1. First a TDD switch of the considered master and slave, followed by a piconet switch of the
both participants.
2. Then, if so desired, other slaves of the old piconet can be transferred to the new piconet.
When a unit have acknowledged the reception of the FHS packet, this unit uses the new piconet
parameters defined by the new master and the piconet switch is completed.
There are three kinds of error correction schemes used in the baseband protocol: 1/3 rate FEC,
2/3 rate FEC and ARQ scheme.
● In 1/3 rate FEC every bit is repeated three times for redundancy,
● In 2/3 rate FEC a generator polynomial is used to encode 10 bit code to a 15 bit code,
● In the ARQ scheme , DM, DH and the data field of DV packets are retransmitted till an
acknowledgement is received (or timeout is exceeded). Bluetooth uses fast, unnumbered
acknowledgement in which it uses positive and negative acknowledgements by setting
appropriate ARQN values. If the timeout value is exceeded, Bluetooth flushes the packet and
proceeds with the next.
The Baseband protocol recommends using FIFO queues in ACL and SCO links for transmission
and receive. The Link Manager fills these queues and link controller empties the queues
automatically.
If these RX FIFO queues are full, flow control is used to avoid dropped packets and congestion. If
data cannot be received, a stop indication is transmitted inserted by the Link Controller of the
receiver into the header of the return packet. When the transmitter receives the stop indication, it
freezes its FIFO queues. If receiver is ready it sends a go packet which resumes the flow again.
2.4.3 Synchronization
The Bluetooth transceiver uses a time-division duplex (TDD) scheme ,meaning that it alternately
transmits and receives in a synchronous manner. The average timing of master packet transmission
should not drift faster than 20 ppm relative to the ideal slot timing of 625 us. Jitter from average
timing should be less than 1 microsecond.
The piconet is synchronized by the system clock of the master.To transmit on the piconet channel
you need 3 pieces of information, The (channel) hopping sequence, the phase of the sequence, and
the CAC to place on the packets
Channel Hopping The Bluetooth Device Address (BD_ADDR) of the master is used to
1
Sequence derive this frequency hopping sequence.
The system clock of the master determines the phase in the
2 Phase
hopping sequence.
This is derived from the Bluetooth Device Address (BD_ADDR) of
3 Channel Access Code
the master.
The slaves adapt their native clocks with a timing offset in order to match the master clock, giving
then an estimated clock value. The offset is zero for the master as it's native clock is the master
clock. The Bluetooth clocks should have the LSB ticking in units of 312.5us, giving a clock rate of
3.2kHz.
A 20us uncertainty window is allowed around the exact receive time in order for the access
correlator for the receiver to search for the correct channel access code and get synchronized with
the transmitter. When a slave returns from the hold mode, it can correlate over a bigger uncertainty
window till they don't overlap slots. A parked slave periodically wakes up to listen to beacons from
the master and re-synchronizes its clock offset.
At the link layer, security is maintained by authentication of the peers and encryption of the
information. For this basic security we need a public address which is unique for each device
(BD_ADDR), two secret keys (authentication keys and encryption key) and a random number
generator. First a device does the authentication by issuing a challenge and the other device has to
then send a response to that challenge which is based on the challenge, it's BD_ADDR and a link
key shared between them. After authentication, encryption may be used to communicate. See our
Bluetooth Security page and Bluetooth article(s) for more details
Note , the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual
Bluetooth Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Link Manager Protocol (LMP)
Consulting
Database
The Link Manager carries out link setup, authentication, link configuration and other protocols. It
discovers other remote LM’s and communicates with them via the Link Manager Protocol (LMP). To
perform its service provider role, the LM uses the services of the underlying Link Controller (LC).
Bluetooth
Antennas The Link Manager Protocol essentially consists of a number of PDU (protocol Data Units), which
Articles are sent from one device to another, determined by the AM_ADDR in the packet header. LM PDUs
Asia-Pacific are always sent as single-slot packets and the payload header is therefore one byte.
Audio
Books DM1 packets are used to transport LM PDUs except if an SCO link is present using HV1 packets
and length of content is less than 9 bytes. In this case DV packets are used.
Cathal's Corner
Consultants
The following is a brief list of the types of PDU's available and their function/operation. These
Design Tools PDU are either Mandatory : M (must be supported), or Optional : O ( optionally supported)
Dev Tools
Downloads For more details : Download the LMP Specification from the SIG website, or visit the
Events Documents Page.
FAQ
Forums
Glossary
InfoTooth Table Of Contents
News
Products 3.1 LMP PDUs
Profiles
3.1.1 General Response
Research
Security 3.1.2 Authentication
SIG 3.1.3 Pairing
Shop
3.1.4 Change Link Key
Subscribe
Technology 3.1.5 Change the Current Link Key
Testing 3.1.6 Encryption
Training 3.1.7 Slot Offset Request
Tutorial
WLANs & BT 3.1.8 Clock Offset Request
3.1.9 Timing Accuracy Information Request
What Is 3.1.10 LMP Version
Bluetooth?
3.1.11 Supported Features
3.1.12 Switch of Master-Slave Role
Member:
3.1.16 Sniff Mode
3.1.17 Park Mode
Password:
3.1.18 Power Control
3.1.19 Channel Quality-Driven Change
Login
3.1.20 Quality of Service
Forgot your 3.1.21 SCO Links
password?
3.1.22 Control of Multi-Slot Packets
New Member 3.1.23 Paging Scheme
3.1.24 Link Supervision
3.1.25 Connection Establishment
3.1.26 Test Mode
3.1.27 Error Handling
These PDU's are used as response messages to other PDU's in a number of different
procedures, containing the opcode of the message that is being responded to.
3.1.2 Authentication
3.1.3 Pairing
When two devices do not have a common link key an initialization key (K init ) is created based
on a PIN and a random number. When both devices have calculated K init the link key is created,
and finally a mutual authentication is made. The pairing procedure starts with a device sending
LMP_in_rand; this device is referred to as "initiating LM" or "initiator" in. The other device is referred
to as "responding LM" or "responder".
(M) LMP_comb_key
If the link key is derived from combination keys and the current link is the semi-permanent link
key, the link key can be changed. If the link key is a unit key, the units must go through the pairing
procedure in order to change the link key. The contents of LMP_comb_key is protected by a bitwise
XOR with the current link key.
The current link key can be a semi-permanent link key or a temporary link key key. It can be
changed temporarily, but the change is only valid for the session. Changing to a temporary link key
is necessary if the piconet is to support encrypted broadcast.
3.1.6 Encryption
If at least one authentication has been performed encryption may be used. If the master wants all
slaves in the piconet to use the same encryption parameters it must issue a temporary key (K
master ) and make this key the current link key for all slaves in the piconet before encryption is
started. This is necessary if broadcast packets should be encrypted.
When a slave receives the FHS packet, the difference is computed between its own clock and the
master’s clock included in the payload of the FHS packet. The clock offset is also updated each time
a packet is received from the master. The master can request this clock offset anytime during the
connection. By saving this clock offset the master knows on what RF channel the slave wakes up to
PAGE SCAN after it has left the piconet. This can be used to speed up the paging time the next
time the same device is paged.
(O) LMP_slot_offset
With LMP_slot_offset the information about the difference between the slot boundaries in different
piconets is transmitted. This PDU carries the parameters slot offset and BD_ADDR. The slot offset
is the subtraction of time in us of the start of the master’s TX slot in the piconet where the PDU is
transmitted from the time in us of the start of the master’s TX slot in the piconet where the
BD_ADDR device is master modulo 1250.
. Before doing a master-slave switch, this PDU shall be transmitted from the device that becomes
master in the switch procedure. The PDU can also be useful in inter-piconet communications.
LMP supports requests for the timing accuracy. This information can be used to minimize the
scan window for a given hold time when returning from hold and to extend the maximum hold time.
It can also be used to minimize the scan window when scanning for the sniff mode slots or the park
mode beacon packets. The timing accuracy parameters returned are the long term drift measured in
ppm and the long term jitter measured in µs of the clock used during hold, sniff and park mode.
These parameters are fixed for a certain device and must be identical when requested several
times.
The LMP layer supports requests for the version of the LM protocol. The requested device will
send a response with three parameters: VersNr, CompId and Sub-VersNr. VersNr specifies the
version of the Bluetooth LMP specification that the device supports. CompId is used to track
possible problems with the lower Bluetooth layers. All companies that create a unique
implementation of the Link Manager shall have their own CompId. The same company is also
responsible for the administration and maintenance of the SubVersNr. It is recommended that each
company has a unique SubVersNr for each RF/BB/LM implementation.
The Bluetooth radio and link controller may support only a subset of the packet types and
features described in Baseband Specification and Radio Specification. A device may not send any
packets other than ID, FHS, NULL, POLL, DM1 or DH1 before it is aware of the supported features
of the other device. After the features request has been carried out, the intersection of the supported
packet types for both sides may also be transmitted. Whenever a request is issued, it must be
compatible with the supported features of the other device. For instance, when establishing an SCO
link the initiator may not propose to use HV3 packets if that packet type is not supported by the
other device.
Since the paging device always becomes the master of the piconet, a switch of the master-slave
role is sometimes needed. Suppose device A is slave and device B is master. The device that
initiates the switch finalises the transmission of the current L2CAP message and then sends
LMP_switch_req. Note: in a slave initiated master-slave switch the slave (A) will first send
LMP_slot_offset, then LMP_switch. In a master initiated master-slave switch, the master (B) will first
send LMP_switch, before receiving LMP_slot_offset from the slave (A). If the switch is accepted, the
other device finalises the transmission of the current L2CAP message and then responds with
LMP_accepted. The switch procedure then takes place, and afterwards device A is master and
device B is slave.
LMP supports name request to another Bluetooth device. The name is a user-friendly name
associated with the Bluetooth device and consists of a maximum of 248 bytes coded according to
the UTF-8 standard. The name is fragmented over one or more DM1 packets.
3.1.14 Detach
(M) LMP_detach
The connection between two Bluetooth devices can be closed anytime by the master or the slave.
A reason parameter is included in the message to inform the other party of why the connection is
closed.
The ACL link of a connection between two Bluetooth devices can be placed in hold mode for a
specified hold time. During this time no ACL packets will be transmitted from the master. The hold
mode is typically entered when there is no need to send data for a relatively long time. The
transceiver can then be turned off in order to save power. But the hold mode can also be used if a
device wants to discover or be discovered by other Bluetooth devices, or wants to join other
piconets. What a device actually does during the hold time is not controlled by the hold message,
but it is up to each device to decide.
To enter sniff mode, master and slave negotiate a sniff interval T sniff and a sniff offset, D sniff ,
which specifies the timing of the sniff slots. The offset determines the time of the first sniff slot; after
that the sniff slots follows periodically with the sniff interval T sniff . When the link is in sniff mode the
master can only start a transmission in the sniff slot. Two parameters control the listening activity in
the slave. The sniff attempt parameter determines for how many slots the slave must listen,
beginning at the sniff slot, even if it does not receive a packet with its own AM address. The sniff
timeout parameter determines for how many additional slots the slave must listen if it continues to
receive only packets with its own AM address.
If a slave does not need to participate in the channel, but still should be FH-synchronized, it can
be placed in park mode. In this mode the device gives up its AM_ADDR but still re-synchronizes to
the channel by waking up at the beacon instants separated by the beacon interval. The beacon
interval, a beacon offset and a flag indicating how the first beacon instant is calculated determine
the first beacon instant. After this the beacon instants follow periodically at the predetermined
beacon interval. At the beacon instant the parked slave can be activated again by the master, the
master can change the park mode parameters, transmit broadcast information or let the parked
slaves request access to the channel.
All PDUs sent from the master to the parked slaves are broadcast. These PDUs are the only
PDUs that can be sent to a slave in park mode and the only PDUs that can be broadcast. When a
slave is placed in park mode it is assigned a unique PM_ADDR, which can be used by the master to
unpark that slave.
If the RSSI value differs too much from the preferred value of a Bluetooth device, it can request
an increase or a decrease of the other device’s TX power. Upon receipt of this message, the output
power is increased or decreased one step. At the master side the TX power is completely
independent for different slaves; a request from one slave can only effect the master’s TX power for
that same slave.The power adjustment requests can be made at anytime following a successful
baseband paging procedure. If a device does not support power control requests this is indicated in
the supported features list.
The data throughput for a given packet type depends on the quality of the RF channel. Quality
measurements in the receiver of one device can be used to dynamically control the packet type
transmitted from the remote device for optimization of the data throughput. If a device A wants the
remote device B to have this control it sends LMP_auto_rate once. The device B can then send
back LMP_preferred_rate to device A whenever it wishes to change the packet type that A
transmits.
This PDU has a parameter which determines the preferred coding (with or without 2/3FEC) and
the preferred size (in slots) of the packets. Device A is not required to change to the packet type
specified by this parameter and may never send a packet that is larger than the maximum allowed
number of slots even if the preferred size is greater than this value.
The LM provides Quality of Service capabilities. A poll interval, which is defined as the maximum
time between subsequent transmissions from the master to a particular slave, is used to support
bandwidth allocation and latency control. In addition, master and slave negotiate the number of
repetitions for broadcast packets (NBC).
When a connection has been established between two Bluetooth devices the connection consists
of an ACL link. One or more SCO links can then be established. The SCO link reserves slots
separated by the SCO interval, T sco . The first slot reserved for the SCO link is defined by T sco
and the SCO delay, D sco . After that the SCO slots follows periodically with the SCO interval. Each
SCO link is distinguished from all other SCO links by an SCO handle.
The number of slots used by a device can be limited. A device allows the remote device to use a
maximal number of slots by sending the PDU LMP_max_slot providing max slots as parameter.
Each device can request to use a maximal number of slots by sending the PDU LMP_max_slot_req
providing max slots as parameter. After a new connection, as a result of page, page scan, master-
slave switch or unpark, the default value is 1 slot. Two PDUs are used for the control of multi-slot
packets.These PDUs can be sent at anytime after connection setup is completed.
In addition to the mandatory paging scheme, the Bluetooth system defines optional paging
schemes. LMP provides a means to negotiate the paging scheme, which is to be used the next time
a unit is paged.
(M) LMP_supervision_timeout
Each Bluetooth link has a timer that is used for link supervision. This timer is used to detect link
loss caused by devices moving out of range, a device’s power-down, or other similar failure cases.
An LMP procedure is used to set the value of the supervision timeout.
When the paging device wishes to create a connection involving layers above LM, it sends
LMP_host_connection_req. When the other side receives this message, the host is informed about
the incoming connection. The remote device can accept or reject the connection request by sending
LMP_accepted or LMP_not_accepted.
LMP has PDUs to support different Bluetooth test modes, which are used for certification and
compliance testing of the Bluetooth radio and baseband.
(M) LMP_not_accepted
If the Link Manager receives a PDU with unrecognised opcode, it responds with
LMP_not_accepted with the reason code unknown LMP PDU. The opcode parameter that is echoed
back is the unrecognised opcode. If the Link Manager receives a PDU with invalid parameters, it
responds with LMP_not_accepted with the reason code invalid LMP parameters. If the maximum
response time is exceeded or if a link loss is detected the party that waits for the response shall
conclude that the procedure has terminated unsuccessfully.
Erroneous LMP messages can be caused by errors on the channel or systematic errors at the
transmit side. To detect the latter case, the LM should monitor the number of erroneous messages
and disconnect if it exceeds a threshold, which is implementation-dependent.
Note , the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual
Bluetooth Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Host Controller Interface (HCI)
Consulting The HCI provides a command interface to the baseband controller and link manager, and access
Database to hardware status and control registers. Essentially this interface provides a uniform method of
accessing the Bluetooth baseband capabilities.The HCI exists across 3 sections, the Host -
Transport Layer - Host Controller. Each of the sections has a different role to play in the HCI
system.
Bluetooth
Antennas For more details : Download the HCI Specification from the SIG website, or visit the
Articles Documents Page.
Asia-Pacific
Audio
Books
Cathal's Corner Table Of Contents
Consultants
Design Tools HCI
Dev Tools 4.1 Functional
Downloads Entities
Events 4.1.1 HCI Firmware
FAQ
Forums 4.1.2 HCI Driver
Glossary 4.1.3 Host Controller Transport Layer
InfoTooth HCI
News 4.2
Commands
Products
4.2.1 HCI-Specific Information Exchange
Profiles
Research 4.2.2 Link Policy Commands
Security 4.2.3 Host Controller & Baseband Commands
SIG
4.2.4 Informational Parameters
Shop
Subscribe 4.2.5 Status Parameters
Technology 4.2.6 Testing Commands
Testing HCI Events/
Training Error
Tutorial 4.3 Codes/
WLANs & BT Flow
Control
What Is
Bluetooth? 4.3.1 Flow Control
4.3.1 HCI Events
New Member
4.1 HCI Functional Entities
Have you
visited our
WAP
Games
section yet?
HCI Firmware , is located on the Host Controller , (e.g. the actual Bluetooth hardware device).
The HCI firmware implements the HCI Commands for the Bluetooth hardware by accessing
baseband commands, link manager commands, hardware status registers, control registers, and
event registers. The term Host Controller means the HCI-enabled Bluetooth device
HCI Driver , which is located on the Host (e.g. software entity). The Host will receive
asynchronous notifications of HCI events, HCI events are used for notifying the Host when
something occurs. When the Host discovers that an event has occurred it will then parse the
received event packet to determine which event occurred. The term Host means the HCI-enabled
Software Unit.
The HCI Driver and Firmware communicate via the Host Controller Transport Layer , i.e. a
definition of the several layers that may exist between the HCI driver on the host system and the
HCI firmware in the Bluetooth hardware. These intermediate layers, the Host Controller Transport
Layer, should provide the ability to transfer data without intimate knowledge of the data being
transferred. Several different Host Controller Layers can be used, of which 3 have been defined
initially for Bluetooth : USB , UART and RS232. The Host should receive asynchronous notifications
of HCI events independent of which Host Controller Transport Layer is used.
The HCI provides a uniform command method of accessing the Bluetooth hardware capabilities.
The HCI Link commands provide the Host with the ability to control the link layer connections to
other Bluetooth devices. These commands typically involve the Link Manager (LM) to exchange
LMP commands with remote Bluetooth devices. The HCI Policy commands are used to affect the
behaviour of the local and remote LM. These Policy commands provide the Host with methods of
influencing how the LM manages the piconet. The Host Controller and Baseband commands,
Informational commands , and Status commands provide the Host access to various registers in the
Host Controller.
The Host Controller Transport Layer provides transparent exchange of HCI-specific information.
These transporting mechanisms provide the ability for the Host to send HCI commands, ACL data,
and SCO data to the Host Controller. These transport mechanisms also provide the ability for the
Host to receive HCI events, ACL data, and SCO data from the Host Controller. Since the Host
Controller Transport Layer provides transparent exchange of HCI-specific information, the HCI
specification specifies the format of the commands, events, and data exchange between the Host
and the Host Controller.
The Link Control commands allow the Host Controller to control connections to other Bluetooth
devices. When the Link Control commands are used, the Link Manager (LM) controls how the
Bluetooth piconets and scatternets are established and maintained. These commands instruct the
LM to create and modify link layer connections with Bluetooth remote devices, perform Inquiries of
other Bluetooth devices in range, and other LMP commands.
The Link Policy Commands provide methods for the Host to affect how the Link Manager
manages the piconet. When Link Policy Commands are used, the LM still controls how Bluetooth
piconets and scatternets are established and maintained, depending on adjustable policy
parameters. These policy commands modify the Link Manager behaviour that can result in changes
to the link layer connections with Bluetooth remote devices.
The Host Controller & Baseband Commands provide access and control to various capabilities of
the Bluetooth hardware. These parameters provide control of Bluetooth devices and of the
capabilities of the Host Controller, Link Manager, and Baseband. The host device can use these
commands to modify the behaviour of the local device.
The Informational Parameters are fixed by the manufacturer of the Bluetooth hardware. These
parameters provide information about the Bluetooth device and the capabilities of the Host
Controller, Link Manager, and Baseband. The host device cannot modify any of these parameters.
The Host Controller modifies all status parameters. These parameters provide information about
the current state of the Host Controller, Link Manager, and Baseband. The host device cannot
modify any of these parameters other than to reset certain specific parameters.
The Testing commands are used to provide the ability to test various functionality's of the
Bluetooth hardware. These commands provide the ability to arrange various conditions for testing.
Flow control is used in the direction from the Host to the Host Controller to avoid filling up the
Host Controller data buffers with ACL data destined for a remote device (connection handle) that is
not responding. It is the Host that manages the data buffers of the Host Controller.
A number of different events are defined for the HCI layer. The events provide a method to return
parameters and data associated for each event. 32 HCI different events have been implemented so
far, they range from Inquiry Complete Event to Page Scan Repetition Mode Change Event. See the
main HCI specs for mode details.
A large number of error codes have been defined for the HCI layer. When a command fails, Error
codes are returned to indicate the reason for the error. 35 HCI error codes have so far been defined,
from Unknown HCI Command to LMP PDU Not Allowed.See the main HCI specs for mode details.
The objective of the HCI UART Transport Layer is to make it possible to use the Bluetooth HCI
over a serial interface between two UARTs on the same PCB. The HCI UART Transport Layer
assumes that the UART communication is free from line errors. Event and data packets flow
through this layer, but the layer does not decode them.
The objective of the HCI RS232 Transport Layer is to make it possible to use the Bluetooth HCI
over one physical RS232 interface between the Bluetooth Host and the Bluetooth Host Controller.
Event and data packets flow through this layer, but the layer does not decode them.
The objective of the Universal Serial Bus (USB) Transport Layer is to the use a USB hardware
interface for Bluetooth hardware (which can be embodied in one of two ways: as a USB dongle, or
integrated onto the motherboard of a notebook PC). A class code will be used that is specific to all
USB Bluetooth devices. This will allow the proper driver stack to load, regardless of which vendor
built the device. It also allows HCI commands to be differentiated from USB commands across the
control endpoint.
Note, the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual
Bluetooth Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Logical Link Control and Adaptation Protocol
Consulting
Database
The Logical Link Control and Adaptation Layer Protocol (L2CAP) is layered over the Baseband
Protocol and resides in the data link layer. L2CAP provides connection-oriented and connectionless
data services to upper layer protocols with protocol multiplexing capability, segmentation and
Bluetooth reassembly operation, and group abstractions. L2CAP permits higher level protocols and
Antennas applications to transmit and receive L2CAP data packets up to 64 kilobytes in length.
Articles
Asia-Pacific Two link types are supported for the Baseband layer : Synchronous Connection-Oriented (SCO)
Audio links and Asynchronous Connection-Less (ACL) links. SCO links support real-time voice traffic using
reserved bandwidth. ACL links support best effort traffic. The L2CAP Specification is defined for
Books
only ACL links and no support for SCO links is planned.
Cathal's Corner
Consultants For more details : Download the L2CAP Specification from the SIG website, or visit the
Design Tools Documents Page
Dev Tools
Downloads
Events
FAQ Table Of Contents
Forums
Glossary
L2CAP
InfoTooth
5.1 Functional
News
Requirements
Products
Profiles 5.1.1 Protocol Multiplexing
Research 5.1.2 Segmentation & Reassembly
Security 5.1.3 Quality of Service
SIG
Shop 5.1.4 Groups
Subscribe L2CAP
Technology 5.2 General
Testing Operation
Training 5.2.2 Channel Identifiers
Tutorial
5.2.3 Operation between Devices
WLANs & BT
5.2.4 Operation between Layers
What Is 5.2.5 Segmentation & Reassembly
Bluetooth?
L2CAP State
5.3
Machine
L2CAP must support protocol multiplexing because the Baseband Protocol does not support any
’type’ field identifying the higher layer protocol being multiplexed above it. L2CAP must be able to
distinguish between upper layer protocols such as the Service Discovery Protocol , RFCOMM , and
Telephony Control .
Have you
visited our 5.1.2 Segmentation & Reassembly
WAP
Games Compared to other wired physical media, the data packets defined by the Baseband Protocol are
section yet? limited in size. Exporting a maximum transmission unit (MTU) associated with the largest Baseband
payload (341 bytes for DH5 packets) limits the efficient use of bandwidth for higher layer protocols
that are designed to use larger packets. Large L2CAP packets must be segmented into multiple
smaller Baseband packets prior to their transmission over the air. Similarly, multiple received
Baseband packets may be reassembled into a single larger L2CAP packet following a simple
integrity check. The Segmentation and Reassembly (SAR) functionality is absolutely necessary to
support protocols using packets larger than those supported by the Baseband.
The L2CAP connection establishment process allows the exchange of information regarding the
quality of service (QoS) expected between two Bluetooth units. Each L2CAP implementation must
monitor the resources used by the protocol and ensure that QoS contracts are honoured.
5.1.4 Groups
Many protocols include the concept of a group of addresses. The Baseband Protocol supports
the concept of a piconet, a group of devices synchronously hopping together using the same clock.
The L2CAP group abstraction permits implementations to efficiently map protocol groups on to
piconets. Without a group abstraction, higher level protocols would need to be exposed to the
Baseband Protocol and Link Manager functionality in order to manage groups efficiently.
The L2CAP layer is based around the concept of ’channels’. Each one of the end-points of an
L2CAP channel is referred to by a channel identifier.
Channel identifiers (CIDs) are local names representing a logical channel end-point on the
device. Implementations are free to manage the CIDs in a manner best suited for that particular
implementation, with the provision that the same CID is not reused as a local L2CAP channel
endpoint for multiple simultaneous L2CAP channels between a local device and some remote
device.
CID assignment is relative to a particular device and a device can assign CIDs independently
from other devices (with the exception of certain reserved CIDs , such as the signalling channel).
Thus, even if the same CID value has been assigned to (remote) channel endpoints by several
remote devices connected to a single local device, the local device can still uniquely associate each
remote CID with a different device.
The connection-oriented data channels represent a connection between two devices, where a
CID identifies each endpoint of the channel. The connectionless channels restrict data flow to a
single direction. These channels are used to support a channel ’group’ where the CID on the source
represents one or more remote devices. There are also a number of CIDs reserved for special
purposes. The signalling channel is one example of a reserved channel. This channel is used to
create and establish connection-oriented data channels and to negotiate changes in the
characteristics of these channels. Support for a signalling channel within an L2CAP entity is
mandatory. Another CID is reserved for all incoming connectionless data traffic.
● L2CAP implementations must transfer data between higher layer protocols and the lower
layer protocol.
● Each implementation must also support a set of signalling commands for use between L2CAP
implementations.
● L2CAP implementations should also be prepared to accept certain types of events from lower
layers and generate events to upper layers. How these events are passed between layers is
an implementation-dependent process.
Segmentation and reassembly (SAR) operations are used to improve efficiency by supporting a
maximum transmission unit (MTU) size larger than the largest Baseband packet. This reduces
overhead by spreading the network and transport packets used by higher layer protocols over
several Baseband packets. All L2CAP packets may be segmented for transfer over Baseband
packets. The protocol does not perform any segmentation and reassembly operations but the
packet format supports adaptation to smaller physical frame sizes.
An L2CAP implementation exposes the outgoing (i.e., the remote host’s receiving) MTU and
segments higher layer packets into ’chunks’ that can be passed to the Link Manager via the Host
Controller Interface (HCI), whenever one exists. On the receiving side, an L2CAP implementation
receives ’chunks’ from the HCI and reassembles those chunks into L2CAP packets using
information provided through the HCI and from the packet header.
This section describes the L2CAP connection-oriented channel state machine. The section
defines the states, the events causing state transitions, and the actions to be performed in response
to events. This state machine is only pertinent to bi-directional CIDs and is not representative of the
signalling channel or the uni-directional channel.
*Diagram Source: Courtesy of Bluetooth SIG, L2CAP Specs, Fig 3.1 , p 258
The figure* above illustrates the events and actions performed by an implementation of the
L2CAP layer. Client and Server simply represent the initiator of the request and the acceptor of the
request respectively. An application-level Client would both initiate and accept requests. The
naming convention is as follows.
● The interface between two layers (vertical interface) uses the prefix of the lower layer offering
the service to the higher layer, e.g., L2CA.
● The interface between two entities of the same layer (horizontal interface) uses the prefix of
the protocol (adding a P to the layer identification), e.g., L2CAP.
● Events coming from above (starting above) are called Requests (Req) and the corresponding
replies are called Confirms (Cfm).
● Events coming from below (starting below) are called Indications (Ind) and the corresponding
replies are called Responses (Rsp).
● Responses requiring further processing are called Pending (Pnd). The notation for Confirms
and Responses assumes positive replies. Negative replies are denoted by a ’Neg’ suffix such
as L2CAP_ConnectCfmNeg.
5.4.2 Signalling
Various signalling commands can be passed between two L2CAP entities on remote devices. All
signalling commands are sent to CID 0x0001 (the signalling channel). The L2CAP implementation
must be able to determine the Bluetooth address (BD_ADDR) of the device that sent the
commands. Multiple commands may be sent in a single (L2CAP) packet and packets are sent to
CID 0x0001. MTU Commands take the form of Requests and Responses. For a complete list see
the L2CAP specs.
Options are a mechanism to extend the ability to negotiate different connection requirements.
Options are transmitted in the form of information elements comprised an option type, an option
length, and one or more option data fields.
Several services are offered by L2CAP in terms of service primitives and parameters. The service
interface is required for testing. They include primitives to :
Note , the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual Bluetooth
Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
RFCOMM Protocol
Consulting
Database
The RFCOMM protocol provides emulation of serial ports over the L2CAP protocol. The protocol
is based on the ETSI standard TS 07.10. Only a subset of the TS 07.10 standard is used, and some
adaptations of the protocol are specified in the Bluetooth RFCOMM specification.
Bluetooth
Antennas For more details: Download the RFCOMM Specification from the SIG website, or visit the
Articles Documents Page.
Asia-Pacific
Audio
Books
Cathal's Corner RFCOMM
Consultants 6.1
Overview/Service
Design Tools
6.1.1 Device Types
Dev Tools
Downloads 6.1.2 Control Signals
Events 6.1.3 Null Modem Emulation
FAQ 6.1.4 Multiple Emulated Serial Ports
Forums
TS 07.10
Glossary
InfoTooth 6.2 Adaptations for
RFCOMM
News
Products 6.2.1 Media Adaption
Profiles TS 07.10 Multiplexer Startup & Closedown
Research 6.2.2
Procedure
Security
6.2.3 DLCI Allocation with RFCOMM Server Channels
SIG
Shop 6.2.4 Multiplexer Control Commands
Subscribe Flow Control
Technology 6.3
Methods Used
Testing
6.3.1 L2CAP Flow Control
Training
Tutorial 6.3.2 Wired Serial Port Flow Control
WLANs & BT 6.3.3 RFCOMM Flow Control
6.3.4 Port Emulation Entity : Serial Flow Control
What Is
Bluetooth? 6.3.5 Credit Based Flow Control
Other Entity
6.4
Interaction
Member:
6.4.4 Low Power Modes
Password:
Login
6.1 RFCOMM Overview/Service
RFCOMM is a simple transport protocol, which provides emulation of RS232 serial ports over the
Forgot your
L2CAP protocol.The protocol is based on the ETSI standard TS 07.10. Only a subset of the TS
password?
07.10 standard is used and an RFCOMM - specific extension is added, in the form of a mandatory
credit based flow control scheme.
New Member
The RFCOMM protocol supports up to 60 simultaneous connections between two BT devices.
The number of connections that can be used simultaneously in a BT device is implementation-
specific. For the purposes of RFCOMM, a complete communication path involves two applications
running on different devices (the communication endpoints) with a communication segment between
them.
The information transferred between two RFCOMM entities has been defined to support both type
1 and type 2 devices. Some information is only needed by type 2 devices while other information is
intended to be used by both. In the protocol, no distinction is made between type 1 and type 2.
Since the device is not aware of the type of the other device in the communication path, each must
pass on all available information specified by the protocol.
RFCOMM emulates the 9 circuits of an RS-232 interface. The circuits are listed below.
RFCOMM is based on TS 07.10. When it comes to transfer of the states of the non-data circuits,
TS 07.10 does not distinguish between DTE and DCE devices. The RS-232 control signals are sent
as a number of DTE/DCE independent signals.
The way in which TS 07.10 transfers the RS-232 control signals creates an implicit null modem
when two devices of the same kind are connected together. No single null-modem cable wiring
scheme works in all cases; however the null modem scheme provided in RFCOMM should work in
most cases.
Two BT devices using RFCOMM in their communication may open multiple emulated serial ports.
RFCOMM supports up to 60 open emulated ports; however the number of ports that can be used in
a device is implementation-specific. A Data Link Connection Identifier (DLCI) identifies an
ongoing connection between a client and a server application. The DLCI is represented by 6 bits,
but its usable value range is 2…61. The DLCI is unique within one RFCOMM session between two
devices.
To account for the fact that both client and server applications may reside on both sides of an
RFCOMM session, with clients on either side making connections independent of each other, the
DLCI value space is divided between the two communicating devices using the concept of
RFCOMM server channels.
If a BT device supports multiple emulated serial ports and the connections are allowed to have
endpoints in different BT devices, then the RFCOMM entity must be able to run multiple TS 07.10
multiplexer sessions. Note that each multiplexer session is using its own L2CAP channel ID (CID).
The ability to run multiple sessions of the TS 07.10 multiplexer is optional for RFCOMM.
The opening flag and the closing flags in the 07.10 basic option frame are not used in RFCOMM,
instead it is only the fields contained between the flags that are exchanged between the L2CAP
layer and RFCOMM layer. There is always exactly one RFCOMM frame contained in each L2CAP
frame.
The start-up and closedown procedures as specified in section 5.7 in TS 07.10 are not supported.
At any time, there must be at most one RFCOMM session between any pair of devices. When
establishing a new DLC, the initiating entity must check if there already exists an RFCOMM session
with the remote device, and if so, establish the new DLC on that. A session is identified by the
Bluetooth BD_ADDR of the two endpoints.
Step 1:
Startup Procedure: The device opening up the first emulated serial port connection between
two devices is responsible for first establishing the multiplexer control channel. This involves
the following steps, after which DLCs for user data traffic can be established:
1: Establish an L2CAP channel to the peer RFCOMM entity, using L2CAP service primitives
2: Start the RFCOMM multiplexer by sending SABM command on DLCI 0, and await UA
response from peer entity.
Step 2:
Closedown Procedure: The device closing the last connection (DLC) on a particular session
is responsible for closing the multiplexer by closing the corresponding L2CAP channel.
Closing the multiplexer by first sending a DISC command frame on DLCI 0 is optional, but it is
mandatory to respond correctly to a DISC (with UA response).
Step 3:
Link Loss Handling: If an L2CAP link loss notification is received, the local RFCOMM entity
is responsible for sending a connection loss notification to the port emulation/proxy entity for
each active DLC. Then all resources associated with the RFCOMM session should be freed.
To account for the fact that both client and server applications may reside on both sides of an
RFCOMM session, with clients on either side making connections independent of each other, the
DLCI value space is divided between the two communicating devices using the concept of
RFCOMM server channels and a direction bit. The RFCOMM server channel number is a subset of
the bits in the DLCI part of the address field in the TS 07.10 frame.
Server applications registering with an RFCOMM service interface are assigned a Server
Channel number in the range 1…30. For an RFCOMM session, the initiating device is given the
direction bit D=1 (and conversely, D=0 in the other device). When establishing a new data link
connection on an existing RFCOMM session, the direction bit is used in conjunction with the Server
Channel to determine the DLCI to use to connect to a specific application. This DLCI is thereafter
used for all packets in both directions between the endpoints.
An RFCOMM entity making a new DLC on an existing session forms the DLCI by combining the
Server Channel for the application on the other device, and the inverse of its own direction bit for the
session.
Note that in TS 07.10, some Multiplexer Control commands pertaining to specific DLCIs may be
exchanged on the control channel (DLCI 0) before the corresponding DLC has been established.
Wired ports commonly use flow control such as RTS/CTS to control communications. On the
other hand, the flow control between RFCOMM and the lower layer L2CAP depends on the service
interface supported by the implementation. In addition RFCOMM has its own flow control
mechanisms. The following describes the different flow control mechanisms.
L2CAP relies on the flow control mechanism provided by the Link Manager layer in the baseband.
The flow control mechanism between the L2CAP and RFCOMM layers is implementation specific.
These methods may be used by both sides of a wired link, or may be used only in one direction.
● The RFCOMM protocol contains flow control commands that operate on the aggregate data
flow between two RFCOMM entities; i.e. all DLCIs are affected.
● The Modem Status command is the flow control mechanism that operates on individual
DLCI.
On Type 1 devices some port drivers (Port Emulation Entities plus RFCOMM) will need to provide
flow control services as specified by the API they are emulating. An application may request a
particular flow control mechanism like XON/XOFF or RTS/CTS and expect the port driver to handle
the flow control.
On type 2 devices the port driver may need to perform flow control on the non-RFCOMM part of
the communication path; i.e. the physical RS-232 port. This flow control is specified via the control
parameters sent by the peer RFCOMM entity (usually a type 1 device). The description of flow
control in this section is for port drivers on type 1 devices.
Since RFCOMM already has its own flow control mechanism, the port driver does not need to
perform flow control using the methods requested by the application. In the ideal case, the
application sets a flow control mechanism and assumes that the COMM system will handle the
details. The port driver could then simply ignore the request and rely on RFCOMM’s flow control.
The application is able to send and receive data, and does not know or care that the port driver did
not perform flow control using the mechanism requested. However, in the real world some
problems arise :
● The RFCOMM-based port driver is running on top of a packet-based protocol where data may
be buffered somewhere in the communication path. Thus, the port driver cannot perform flow
control with the same precision as in the wired case.
● The application may decide to apply the flow control mechanism itself in addition to
requesting flow control from the port driver.
These problems suggest that the port driver must do some additional work to perform flow
control emulation properly. Here are the basic rules for flow control emulation.
● The port driver will not solely rely on the mechanism requested by the application but use a
combination of flow control mechanisms.
● The port driver must be aware of the flow control mechanisms requested by the
application and behave like the wired case when it sees changes on the non-data circuits
(hardware flow control) or flow control characters in the incoming data (software flow control).
For example, if XOFF and XON characters would have been stripped in the wired case they
must be stripped by the RFCOMM based port driver.
● If the application sets a flow control mechanism via the port driver interface and then proceeds
to invoke the mechanism on its own, the port driver must behave in a manner similar to that of
the wired case (e.g. If XOFF and XON characters would have been passed through to the
wire in the wired case the port driver must also pass these characters).
This is a mandatory feature that did not exist in RFCOMM in Bluetooth specifications 1.0B and
earlier. Therefore, its use is subject to negotiation before the first DLC establishment.
Implementations conforming to this specification must support it, and must try to use it when
connecting to other devices.
The credit based flow control feature provides flow control on a per - DLC basis. When used, both
devices involved in a RFCOMM session will know, for each DLC, how many RFCOMM frames the
other device is able to accept before it buffers fill up for that DLC. A sending entity may send as
many frames on a DLC as it has credits; if the credit count reaches zero, the sender must stop and
wait for further credits from the peer. It is always allowed to send frames containing no user data
(length field = 0) when credit based flow control is in use. This mechanism operates independently
for each DLC, and for each direction. It does not apply to DLCI 0 or to non-UIH frames.
This section defines how the RFCOMM protocol should be used to emulate serial ports.
Type 1 devices are communication endpoints such as computers and printers.Type 2 devices are
part of a communication segment; e.g. modems.
● Port Emulation Entity : The port emulation entity maps a system specific communication
interface (API) to the RFCOMM services.
● Port Proxy Entity : The port proxy entity relays data from RFCOMM to an external RS-232
interface linked to a DCE. The communications parameters of the RS-232 interface are set
according to received RPN commands,
Registration of individual applications or services, along with the information needed to reach
those (i.e. the RFCOMM Server Channel) is the responsibility of each application respectively (or
possibly a Bluetooth configuration application acting on behalf of legacy applications not directly
aware of Bluetooth).
6.4.3 Reliability
RFCOMM uses the services of L2CAP to establish L2CAP channels to RFCOMM entities on
other devices. An L2CAP channel is used for the RFCOMM/TS 07.10 multiplexer session.
Some frame types (SABM and DISC) as well as UIH frames with multiplexer control commands
sent on DLCI 0 always require a response from the remote entity, so they are acknowledged on the
RFCOMM level (but not retransmitted in the absence of acknowledgement ). Data frames do not
require any response in the RFCOMM protocol, and are thus unacknowledged.
Therefore, RFCOMM must require L2CAP to provide channels with maximum reliability, to ensure
that all frames are delivered in order, and without duplicates. Should an L2CAP channel fail to
provide this, RFCOMM will expect a link loss notification, which should be handled by RFCOMM.
If all L2CAP channels towards a certain device are idle for a certain amount of time, a decision
may be made to put that device in a low power mode i.e hold, sniff or park mode. This will be done
without any interference from RFCOMM. RFCOMM can state its latency requirements to L2CAP.
This information may be used by lower layers to decide which low power mode(s) to use.
The RFCOMM protocol as such does not suffer from latency delays incurred by low power
modes, and consequentially, this specification does not state any maximum latency requirement on
RFCOMM’s behalf. Latency sensitivity inherently depends on application requirements, which
suggests that an RFCOMM service interface implementation could include a way for applications to
state latency requirements, to be aggregated and conveyed to L2CAP by the RFCOMM
implementation. (That is if such procedures make sense for a particular platform.)
Note, the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual
Bluetooth Specification.
Find
Advanced search
Bluetooth Resource Center
Home
Bookshop
Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles
Market Research
Search
Add a Link
Service Discovery Protocol (SDP)
Consulting The service discovery protocol (SDP) provides a means for applications to discover which
Database services are available and to determine the characteristics of those available services.
A specific Service Discovery protocol is needed in the Bluetooth environment, as the set of
services that are available changes dynamically based on the RF proximity of devices in motion,
Bluetooth qualitatively different from service discovery in traditional network-based environments. The service
Antennas discovery protocol defined in the Bluetooth specification is intended to address the unique
Articles characteristics of the Bluetooth environment.
Asia-Pacific
Audio For more details : Download the SDP Specification from the SIG website, or visit the
Books Documents Page.
Cathal's Corner
Consultants Table Of Contents
Design Tools
Dev Tools SDP Protocol
7.1
Downloads Setup
Events 7.1.1 Overview
FAQ
7.1.2 PDU Format
Forums
Glossary 7.1.3 Partial Responses and Continuation State
InfoTooth 7.1.4 Error Handling
News
7.2 SDP Services
Products
Profiles 7.2.1 Service Record
Research 7.2.2 Service Attribute
Security 7.2.3 Service Class
SIG
Service
Shop 7.3
Discovery
Subscribe
Technology 7.3.1 Searching for Services
Testing 7.3.2 Browsing for Services
Training
Data
Tutorial 7.4
Representation
WLANs & BT
7.4.1 Data Element header field
What Is 7.4.2 Data Element data field
Bluetooth?
Service
Members
7.5 Discovery
Background info
7.5.1 Service Discovery
Member:
7.5.2 Bluetooth Service Discovery
Password:
Login
SDP uses a request/response model where each transaction consists of one request protocol
data unit (PDU) and one response PDU. In the case where SDP is used with the Bluetooth L2CAP
transport protocol, only one SDP request PDU per connection to a given SDP server may be
Have you outstanding at a given instant. In other words, a client must receive a response to each request
visited our before issuing another request on the same L2CAP connection. Limiting SDP to sending one
WAP unacknowledged request PDU provides a simple form of flow control.
Games
section yet?
*Diagram Source: Courtesy of Bluetooth SIG, SDP Specs, Fig 2.1 , p 330
Every SDP PDU consists of a PDU header followed by PDU-specific parameters. The header
contains three fields:
● PDU ID field identifies the type of PDU. I.e. its meaning and the specific parameters.
● TransactionID field uniquely identifies request PDUs and is used to match response PDUs to
request PDUs.
● ParameterLength field specifies the length (in bytes) of all parameters contained in the PDU.
Some SDP requests may require responses that are larger than can fit in a single response PDU.
In this case, the SDP server will generate a partial response along with a continuation state
parameter. The continuation state parameter can be supplied by the client in a subsequent request
to retrieve the next portion of the complete response.
Each transaction consists of a request and a response PDU. Generally, each type of request
PDU has a corresponding type of response PDU. However, if the server determines that a request
is improperly formatted or for any reason the server cannot respond with the appropriate PDU type,
it will respond with an error PDU (SDP_ErrorResponse) .
The following section describe how the individual characteristics (services) of the different
devices are stored.
A service is any entity that can provide information, perform an action, or control a resource on
behalf of another entity. A service may be implemented as software, hardware, or a combination of
hardware and software. All of the information about a service that is maintained by an SDP server is
contained within a single service record. The service record consists entirely of a list of service
attributes.
Each service attribute describes a single characteristic of a service. Some examples of service
attributes are ServiceClassIDList & ProviderName . Some attribute definitions are common to all
service records , but service providers can also define their own service attributes.
● An attribute ID is a 16-bit unsigned integer that distinguishes each service attribute from
other service attributes within a service record. The attribute ID also identifies the semantics
of the associated attribute value.
● The attribute value is a variable length field whose meaning is determined by the attribute ID
associated with it and by the service class of the service record in which the attribute is
contained. In the Service Discovery Protocol, an attribute value is represented as a data
element. See the section 'Data Representation' below for more information.
Each service is an instance of a service class. The service class definition provides the definitions
of all attributes contained in service records that represent instances of that class. Each attribute
definition specifies the numeric value of the attribute ID, the intended use of the attribute value, and
the format of the attribute value. A service record contains attributes that are specific to a service
class as well as universal attributes that are common to all services.
Each service class is assigned a unique identifier ,this service class identifier is contained in the
attribute value for the ServiceClassIDList attribute, and is represented as a UUID. A UUID is a
universally unique identifier that is guaranteed to be unique across all space and all time. UUIDs
can be independently created in a distributed fashion. No central registry of assigned UUIDs is
required. A UUID is a 128-bit value.
The whole point of the SDP is to allow bluetooth devices to discover what other bluetooth devices
can offer (what services). SDP allows this in various means. Searching means looking for specific
service, while Browsing means looking to see what services are actually being offered.
The Service Search transaction allows a client to retrieve the service record handles for particular
service records based on the values of attributes contained within those service records.
The capability search for service records based on the values of arbitrary attributes is not
provided. Rather, the capability is provided to search only for attributes whose values are
Universally Unique Identifiers (UUIDs). Important attributes of services that can be used to search
for a service are represented as UUIDs. Service search pattern are used to locate the desired
service. A service search pattern is a list of UUIDs (service attributes) used to locate matching
service records.
This process of looking for any offered services is termed browsing. In SDP, the mechanism for
browsing for services is based on an attribute shared by all service classes. This attribute is called
the BrowseGroupList attribute. The value of this attribute contains a list of UUIDs. Each UUID
represents a browse group with which a service may be associated for the purpose of browsing.
When a client desires to browse an SDP server’s services, it creates a service search pattern
containing the UUID that represents the root browse group. All services that may be browsed at the
top level are made members of the root browse group by having the root browse group’s UUID as a
value within the BrowseGroupList attribute.
data element. A data element is a typed data representation. It consists of two fields: a header field
and a data field.
The header field is composed of 2 parts, a Type Descriptor and a Size Descriptor.
● Type Descriptor: A data element type is represented as a 5-bit type descriptor. The type
descriptor is contained in the most significant (high-order) 5 bits of the first byte of the data
element header.
● Size Descriptor: The data element size descriptor is represented as a 3-bit size index
followed by 0, 8, 16, or 32 bits. The size index is contained in the least significant (low-order)
3 bits of the first byte of the data element header.
The data is a sequence of bytes whose length is specified in the size descriptor and whose
meaning is (partially) specified by the type descriptor.
As computing continues to move to a network-centric model, finding and making use of services
that may be available in the network becomes increasingly important. Services can include common
ones such as printing, paging, FAX-ing, and so on, as well as various kinds of information access
such as telecon-ferencing, network bridges and access points, eCommerce facilities, and so on —
most any kind of service that a server or service provider might offer. In addition to the need for a
standard way of discovering available services, there are other considerations: getting access to the
services (finding and obtaining the protocols, access methods, "drivers" and other code necessary
to utilize the service), controlling access to the services, advertising the services, choos-ing among
competing services, billing for services, and so on. This problem is widely recognized; many
companies, standards bodies and consortia are addressing it at various levels in various ways.
Service Location Protocol (SLP), JiniTM, and Salutation TM, to name just a few, all address some
aspect of service discovery.
The Bluetooth Service Discovery Protocol (SDP) addresses service discovery spe-cifically for the
Bluetooth environment. It is optimized for the highly dynamic nature of Bluetooth communications.
SDP focuses primarily on discovering services available from or through Bluetooth devices. SDP
does not define methods for accessing services; once services are discovered with SDP, they can
be accessed in various ways, depending upon the service. This might include the use of other
service discovery and access mechanisms such as those mentioned above; SDP provides a means
for other protocols to be used along with SDP in those environments where this can be beneficial.
While SDP can coexist with other service discovery protocols, it does not require them. In Bluetooth
environments, services can be discovered using SDP and can be accessed using other protocols
defined by Bluetooth.
Note , the above text contains excerpts from the Bluetooth SIG's Specification, as well as various
interpretations of the Specs. For complete details of the various sections, consult the actual
Bluetooth Specification.
Find
Bluetooth Resource Center Advanced search
Home
Bookshop
Market Research
Search
Add a Link What Is Bluetooth?
Consulting
Database Well it isn't some
strange form of tooth
decay as you might
initially imagine.
Bluetooth Bluetooth is the name
of a new technology
Antennas
that is now becoming
Articles
commercially
Asia-Pacific available. It promises
Audio to change significantly
Books the way we use
Cathal's Corner machines.
Consultants
Design Tools
Dev Tools
Downloads
Events
FAQ 1 Take a look around
Forums
Glossary Look around you at the
moment, you have your keyboard
InfoTooth
connected to the computer, as well
News
as a printer, mouse, monitor and
Products so on. What (literally) joins all of
Profiles these together?, they are
Research connected by cables. Cables have
Security become the bane of many offices,
Find
Bluetooth Resource Center Advanced search
Subscribe
Besser Associates Bluetooth: An
Technology
Introduction
Testing
Training
Tutorial This two-day course introduces
WLANs & BT and analyzes the Bluetooth radio
system. Bluetooth signal
propagation, modulation, packet
What Is
structure, and error control are
Bluetooth?
examined.
Bluetooth University
Members
Bluetooth University is offering
an extensive, international
training program during the
Member: second half of 2001 which will
give you deep knowledge about
Password: how to use Bluetooth in products
and applications. Bluetooth
University, a part of connectBlue.
Login
Includes:
What is the fastest way to the
national and international
markets?
Testing Requirements in the
most important Marketplaces.
Short Introduction to the
Bluetooth Technology
connectBlue
Bluetooth in Control
Enea
Bluetooth Architecture
Malmö, Linköping.
Ericsson
Bluetooth Academy - Boosting
Product Development
Various
locations
ETS
● Understanding Bluetooth -
2 days
● Implementing Wireless
Networks using Bluetooth -
2 days
Extended Systems
Overview of Bluetooth
A fast-track
introduction to
Bluetooth
technology,
standards and the
latest Bluetooth
developments.
Understanding Bluetooth
Technology
A fast-track coverage
of Bluetooth
technology, including
Bluetooth operation,
testing and
troubleshooting.
NetConsulate
Rococo Software
Sigma
TechOnLine University
Understanding Wireless
Communications, Software
Defined Radio and other free
courses & lectures available on-
line.
TPG Training
1.Introducing Bluetooth
2.Bluetooth in the Wireless Data
Arena
3.Hopping and timing details
4.Error control and logical
channels
5.Audio Processing
6.Bluetooth Security
7.Bluetooth Operating Modes
8.Bluetooth Protocols
9.Bluetooth Application Support
10.Bluetooth Application Profiles
11.Bluetooth Modules
12.Using Bluetooth
E-Mail: [email protected]
Find
Wireless Resource Center Advanced search
Existing User?
Please enter your user name and password in the boxes below.
palowireless
Click here if you've forgotten your user id or password and would like
About Us
About Site us to e-mail it to you.
FAQ
Feedback
Link To Us Your user name:
I've forgotten my user id or
Suggest
Testimonials password!
What's New Your password:
Member:
To use this facility your web browser must have cookies enabled.
Password:
Inactive sessions expire after 20 minutes.
Login
Forgot your
password?
New Member
Pages Served:
Find
Wireless Resource Center Advanced search
palowireless
About Us
About Site
FAQ
Feedback
Link To Us
Suggest
Testimonials
What's New
Members
Member:
Password:
Login
Forgot your
password?
New Member
Pages Served:
Find
Wireless Resource Center Advanced search
Member:
Password:
Login
Forgot your
password?
New Member
Pages Served:
Find
Advanced search
WAP Resource Center
*****
Have you
Physics for Game Developers
visited our Interesting Articles
MMS
Colliding billiard balls. Missile
Games Wired Mobile Gamers Need Better Devices (10/02) Mobile
●
trajectories. Cornering dynamics in
or Java gaming stands poised to become a billion-dollar business - speeding cars. By applying the
Games but not on today's cell phones, a Sony executive told an laws of physics, you can
sections audience at the Cellular Telecommunications and Internet realistically model nearly
yet? Association show. Despite the proliferation of cell phones everything in games that bounces
this year, none of the handsets is good enough for serious around, flies, rolls, slides, or isn't
gamers, said John Smedley, chief operations officer for sitting still, to create compelling,
Sony Online Entertainment. But that doesn't mean that cell- believable content for computer
phone service providers can't and shouldn't bank on games, simulations, and
games. There are dozens of games written in J2ME that animation.
are available.
Useful Links
agotchi
A virtual pet - hours of fun. Cheat
codes for secret access - and
wap.agotchi.net
much more.