Professional Documents
Culture Documents
S
S S P THE PROTOCOL STACK
The protocols of the bluetooth stack can be divided
into four different categories:
Figure 2. A Scatternet comprising two Piconets.
BLUETOOTH CORE PROTOCOLS
3 bit active device address. Inactive slaves in uncon-
nected modes may continue to reside within the BaseBand
piconet. The baseband and the Link control layers enable the
A master is the only one that may initiate a bluetooth physical RF link between bluetooth devices to form a
communication link. However, once a link is estab- piconet. Both circuit and packet switching is used.
lished, the slave may request a master/slave switch to They provide two kinds of physical links using the
become the master. Slaves are not allowed to talk to baseband packets. Synchronous connection oriented
each other directly. All communication occurs within (SCO) and Asynchronous connectionless (ACL). ACL
the slave and the master. Slaves within a piconet must packets are used for data only, while the SCO packets
also synchronize their internal clocks and frequency may contain audio only or a combination of audio and
hops with that of the master. Each piconet uses a dif- data.
ferent frequency hopping sequence. Radio devices
used Time Division Multiplexing (TDM). A master The Link Manager Protocol
device in a piconet transmits on even numbered slots The link manager protocol is responsible for the link
and the slaves may transmit on odd numbered slots. setup between bluetooth units. This protocol layer
Multiple piconets with overlapping coverage areas caters to issues of security like authentication, encryp-
form a scatternet. Each piconet may have only one tion by generating, exchanging and checking the link
master, but slaves may participate in different piconets and encryption keys. It also deals with control and
vCARD / WAE
vCAL
AT TCS SDP
OBEX WAP Commands
TCP/UDP/IP
PPP
RFCOMM
L2CAP AUDIO
HOST CONTROLLER
INTERFACE (HCI)
LINK MANAGER
PROTOCOL
BLUETOOTH BASEBAND
BLUETOOTH RF
}
APPLICATION
SOFTWARE
TCP/IP HID RFCOMM
OL
TR
DATA
N
CO
L2CAP HCI
AUDIO
}
HARDWARE
LINK MANAGER
BASEBAND
BLUETOOTH RF
RFCOMM
Connecting States Page
Inquiry
The RFCOMM protocol is the basis for the cable
replacement usage of bluetooth. It is a simple transport
Data
protocol with additional provisions for emulating the 9
Active States Connected
transfer circuits of RS-232 serial ports over L2CAP part of the
bluetooth protocol stack. This is based in the ETSI
standard TS 07.10 and supports a large base of lega-
Low Power States Parked Hold Sniff
cy applications that use serial communication. It pro-
vides a reliable data stream, multiple concurrent con-
nections, flow control and serial cable line settings.
Figure 5. The Baseband State Machine.
Telephony Control Protocol
Logical Link Control and Adaptation Specification (TCS Binary)
Layer (L2CAP) The TCS binary protocol defines the call control sig-
The bluetooth logical link control and adaptation layer naling for the establishment of speech and data calls
supports higher level multiplexing, segmentation and between bluetooth devices. It is based on the ITU-T
reassembly of packets, and Quality of Service (QoS) Q.931 recommendation. It is a bit oriented protocol
communication and Groups. This layer does not pro- and also provides group management.
vide any reliability and uses the baseband ARQ to
The Host Controller Interface (HCI)
ensure reliability. Channel identifiers are used to label
each connection end point. The HCI provides a command interface to the base-
band controller, link manager and access to the hard- tocol features supporting a usage model. These pro-
ware status and control registers. The interface pro- files are the basis for interoperability and bluetooth
vides a uniform method of accessing the bluetooth logo requirements. Each bluetooth device supports
baseband capabilities. The Host control transport layer one or more profiles. There are four generic profiles
abstracts away transport dependencies and provides that are used by the different usage model based pro-
a common device driver interface to various interfaces. files. These are serial port profile, generic access pro-
Three interfaces are defined in the core specification: file, Service discovery application profile and generic
USB, RS-232, and UART. object exchange profile.
Specification and Description Language (SDL) is an
ADOPTED PROTOCOLS object-oriented, formal language defined by ITU-T as
recommendation Z.100. The language is intended for
PPP, TCP/IP specification of complex, event driven real-time, and
interactive applications involving concurrent activities
PPP, TCP, UDP and IP are standard Internet protocols that communicate using discrete signals.
defined by IETF. These are used as the lower layer pro-
tocols of the WAP stack.
BLUETOOTH PACKET FORMATS
OBEX BASEBAND
OBEX is a session protocol defined by IrDA. This pro-
Access code Packet header Payload
tocol is also utilized by bluetooth thus enabling the
72 bits 54 bits 0-2754 bits
possibility for application to use either the bluetooth
radio or IrDA technologies.
L2CAP
WAP/WAE
Bluetooth may be used as a bearer technology for Connection Oriented
transporting between a WAP client and a nearby WAP
Length DCID Payload
server. WAP operates on top of the bluetooth stack
16 bits 16 bits 0-65535 bits
using PPP and the TCP/IP protocol suite.