Bluetooth Protocol Stack

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

Bluetooth Protocol stack

Fig: Bluetooth protocol stack

1. As Fig shows, the Bluetooth specification already comprises many protocols and
components.

2. The Bluetooth protocol stack can be divided into a core specification


(Bluetooth, 2001a), which describes the protocols from physical layer to the data
link control together with management functions, and profile specifications
(Bluetooth, 2001b). The latter describes many protocols and functions needed to
adapt the wireless Bluetooth technology to legacy and new applications.
3. The core protocols of Bluetooth comprise the following elements:

Radio: Specification of the air interface, i.e., frequencies, modulation, and


transmit power.

Baseband: Description of basic connection establishment, packet formats, timing,


and basic QoS parameters.

Link manager protocol: Link set-up and management between devices including
security functions and parameter negotiation.

Logical link control and adaptation protocol(L2CAP): Adaptation of higher


layers to the baseband (connectionless and connection-oriented services).

Service discovery protocol: Device discovery in close proximity plus querying of


service characteristics.

4. On top of L2CAP is the cable replacement protocol RFCOMM that emulates a


serial line interface following the EIA-232 (formerly RS-232) standards.
RFCOMM supports multiple serial ports over a single physical channel.

5. The telephony control protocol specification – binary (TCS BIN) describes a


bit-oriented protocol that defines call control signaling for the establishment of
voice and data calls between Bluetooth devices. It also describes mobility and
group management functions.

6. The host controller interface (HCI) between the baseband and L2CAP provides
a command interface to the baseband controller and link manager, and access to
the hardware status and control registers. The HCI can be seen as the hardware/
software boundary.

7. Many protocols have been adopted in the Bluetooth standard. Classical Internet
applications can still use the standard TCP/IP stack running over PPP or use the
more efficient Bluetooth network encapsulation protocol (BNEP).

8. Telephony applications can use the AT modem commands as if they were using
a standard modem. Calendar and business card objects (vCalen dar/ vCard) can be
exchanged using the object exchange protocol (OBEX) as common with IrDA
interfaces.
9. A real difference to other protocol stacks is the support of audio . Audio
applications may directly use the baseband layer after encoding the audio signals.

You might also like