3/4/11

A cable replacement technology Up to 3 Mb/s Range 10+ meters Single chip radio+baseband at low power & low price

Why not using WLANs? power cost Why not using IrDA? Line of sight Short distance range (1m)
3/4/11

Bluetooth has been named after a

Scandinavian king, who lived in the X century A.C., called Harald Bluetooth

Harald Bluetooth took over several tribes

which had different cultures and habits

The aim of the Bluetooth technology is to be

universal and suitable for any kind of environment

3/4/11

 February 1998: The Bluetooth SIG is formed promoter company groups: Ericsson, IBM, Intel, Nokia, Toshiba; 7,000 members as of 2007 May 1998: Public announcement of the Bluetooth SIG July 1999: 1.0A spec (>1,500 pages) is published December 1999: v. 1.0B is released (buggy) December 1999: The promoter group increases to 9 members 3Com, Lucent, Microsoft, Motorola June 2002: There are 1,900+ adopters
3/4/11

February 2001: Release of Bluetooth 1.1 including AFH and eSCO (high-quality audio) and correcting bugs from v.1.0B November 2004: Release of specification Bluetooth 2.0 with EDR (Enhanced Data Rate) March 28, 2007: Bluetooth 2.1 with EDR announced: lower power consumption and improved devices pairing. 2009: Bluetooth 3.0: enabled for support of WiFi transmissions too when data are too large (speed up to 24 Mbps in this case) 3/4/11

Task Group IEEE 802.15.1

Goal Developing a standard for short range wireless communication referred as WPAN, and based on the Bluetooth Specifications Facilitating coexistence of WPAN and WLAN.The coexistence model tries to quantify the mutual interference of the two Drafting and publishing a new standard for highrate (20Mbit/s or greater) WPANs Providing a standard for low data-rate wireless connectivity (LR-WPAN)
3/4/11

IEEE 802.15.2

IEEE 802.15.3 IEEE 802.15.4

 In March 2002, the IEEE 802.15.1 WG has released the first version of the standard for WPANs The two lower layers of the protocol stack (Physical and MAC layers) are based on the Bluetooth v1.x Specifications

3/4/11

3/4/11

Property

BT

Cable

3/4/11

Property
Application Type of devices Bandwidth Range Data rate Power Consumption Physical layer Type of use Cost

BT
Cable replacement technology Ideal for Cellular Phones ISM <10 meters Up to 3 Mbps Limited (60 mA) FHSS Very simple $10

IEEE 802.11g
Wireless version of Ethernet LAN Limited applicability for handheld devices ISM >100 meters 54 Mbps Expensive (300 mA) OFDM Complex $50
3/4/11

ISM bands 902 928 Mhz 2.4 2.4835 Ghz 5.725 5.785 Ghz
SHF
3GHz 10cm

o ra S/ W di FM

LF

MF
3MHz 100m

HF

VHF
30MHz 10m 300MHz 1m

TV dio TV ce llu la r
UHF

di

AM

ra

ra

EHF
30GHz 1cm 300GHz f 100mm

30kHz 300kHz 10km 1km

Propagation characteristics are different in each frequency band

(ISM: Industrial, Scientific and Medical)
3/4/11

33cm 26 Mhz

12cm 83.5 Mhz

5cm 125 Mhz

902 Mhz 928 Mhz Cordless phones Baby monitors

2.4 Ghz 2.4835 Ghz 802.11 Bluetooth Microwave oven

5.725 Ghz 5.785 Ghz

3/4/11

1Mhz . . . 12 3 79 83.5 Mhz

2.402 GHz + k MHz, k=1, , 79 (79 channels spaced by 1MHz) Modulations: GFSK (basic rate): 1 Mb/s /4-DQPSK (EDR): 2 Mb/s 8DPSK (EDR): 3 Mb/s transmit power: 0dBm (up to 20dBm with power control)
3/4/11

Dynamic reconfigurability for a very flexible system suited to many environments Piconet: all ad hoc networks with at most 8 simultaneously active devices 1 master: controls the channel access within the piconet and handles all the traffic within the piconet up to 7 slaves Scatternet: Many piconets coexisting in the same area (interconnected or not) Any device can be either a master or a slave in a piconet
3/4/11

3/4/11

3/4/11

Cordless headset mouse Keyboard Printer

To satellite, land line,

Data/voice access point

Cable replacement

Internet access

Personal ad hoc networking

3/4/11

User benefits Automatic synchronization of calendars, address books, business cards Push button synchronization Proximity operation
3/4/11

Cordless headset

User benefits Multiple device access Cordless phone benefits Hands free operation

3/4/11

Data Access Points Synchronization Headset Conference Table Cordless Computer Instant Postcard Computer Speakerphone ....
3/4/11

3/4/11

Bluetooth documentation is divided into two parts: The Specifications describe how the technology works (i.e., the Bluetooth protocol architecture) The Profiles describe how the technology is used (i.e., how different parts of the specification can be used to fulfill a desired function for a Bluetooth device)
3/4/11

3/4/11

noise, interference power

data signal

spectrum recovered data signal

cost

Goals high bandwidth conserve battery power cost < $10 robust system
3/4/11

 Power Classes: devices can be classified into 3 power classes Power Class 1: long range (~100m) devices, max output power = 20dBm Power Class 2: ordinary range devices (~10m), max output power = 4dBm Power Class 3: short range devices (~10cm), max output power = 0dBm Low Power Low voltage RF Standby modes (Sniff, Hold, Park)
3/4/11

noise, interference power

data signal

spectrum recovered data signal

cost

Goals high bandwidth conserve battery power cost < $10 robust system
3/4/11

Low Cost Single chip radio (minimize external components) Todays technology Time division duplex

3/4/11

noise, interference power

data signal

spectrum recovered data signal

cost

Goals high bandwidth conserve battery power cost < $10 robust system
3/4/11

Robust operation Frequency hopping: 1600 hops/sec Strong interference protection Fast ARQ Robust access code Forward header correction

3/4/11

3/4/11

10

Applications
IP

Audio

L2CAP LM

Baseband RF
3/4/11

Applications
IP

Co

Data
Audio L2CAP Link Mng

ntr ol

SDP

RFCOMM

Co

Data

ntr

ol

SDP

RFCOMM

Software HCI Single chip (RF, BB, LM, HCI) With RS-232, USB, or PC card interface

Baseband RF An application framework

A hardware/software/protocol description
3/4/11

Applications
IP

Audio

L2CAP LMP

Co

Data

ntr

ol

SDP

RFCOMM

Baseband RF

defines the requirements of the Bluetooth transceiver

3/4/11

11

 Idea

spread signal over all the available bandwidth originally designed to thwart jamming Frequency Hopping transmit over pseudo-random sequence of frequencies sender and receiver share: seed pseudo-random number generator
3/4/11

Uses an FHSS technique to minimize power waste and guarantee robustness to interference Bandwidth: 79 MHz divided into 79 frequency channels with width equal to 1 MHz In the U.S., hopping is performed over all the 79 channels In Europe (France and Spain), hopping initially used only 23 channels out of the 79 (channel limitation)
3/4/11

3/4/11

12

 Each BT device has a free-running clock that is the heart-beat of the tranceiver Slaves synchronize with the master by adding an offset to its native clock; offsets have to be updated regularly

3/4/11

Once created, each piconet uses its own frequency hopping sequence which is derived from the address of the master node Interference between neighboring piconets is reduced The hopping sequence is defined so that there is equal probability to hop on any of the available frequency channels (pseudo-random sequence) in the U.S.: channel hopping prob.=1/79 in Europe (old): channel hopping prob.= 1/23

3/4/11

Frequency hopping sequence can be modified due to

coexistence issues
Systems operating in the ISM bands and sharing the

same environment may interfere The closer the interfering transmitter to the receiver, the greater the throughput decrease (significant effects if receiver and interfering transmitter are within a distance of 4 m) Coexistence techniques aim at avoiding significant performance degradation of wireless technologies interfering with each other
3/4/11

13

3/4/11

offset

WLAN packet

366 s 625 s

802.15 packets colliding in time with the WLAN packet

3/4/11

Coexistence mechanism in Bluetooth (part of the standard): limits interference on and from other devices Bluetooth devices carry out measurements in terms of SINR, BER, PER, over the frequency channels on which they hop A channel map indicates which RF channels are good (and shall be used) and which are bad (i.e., shall be unused) Slaves notify the master about their maps, and unused RF channels are re-mapped uniformly onto used RF channels (possibly, for each master-slave link)
3/4/11

14

Applications
IP

Audio

L2CAP LMP

Baseband RF
3/4/11

Point to point link master - slave relationship radios can function as masters or slaves Piconet master can connect to 7 slaves each piconet has max gross capacity of up to 3 Mbps hopping pattern is determined by the master

Co

Data

ntr

ol

SDP

RFCOMM

m s s s

3/4/11

Inquiry Inquiry Scan protocol to learn about the clock offset and device address of other nodes in proximity

3/4/11

15

 Page Page Scan protocol to establish links with nodes in proximity

Master Active Slave Parked Slave Standby

3/4/11

Bluetooth device address (BD_ADDR) 48 bit IEEE MAC address Active Member address (AM_ADDR) 3 bits active slave address all zeros: broadcast address Parked Member address (PM_ADDR) 8 bit parked slave address
3/4/11

A Hopping Sequence is used to select the next radio channel It is only related to masters hardware address The phase in the hopping sequence is determined by the masters BT clock Channel is temporally slotted (slot duration= 625 s) A packet is transmitted within a single radio channel
3/4/11

16

FH/TDD
f0 m f1 f2 f3 f4 f5

s1

s2 625s 1600 hops/s 366s tx/rx turn around time

3/4/11

Slaves can transmit only if polled by the master The packet header indicates the intended receipient Master always starts transmitting on even slots Slaves always start transmitting on odd slots

3/4/11

FH/TDD
f0 m f3 f4 f5

s1

s2 625s

Data rate depends on the packet type

3/4/11

17

 Synchronous Connection Oriented (SCO) Link

slot reservation at fixed intervals

Extended Synchronous Connection Oriented (eSCO) Link

SCO with configurable asymmetric data rate and retx

Asynchronous Connection-less (ACL) Link

Polling access method

SCO ACL

ACL SCO ACL

ACL

SCO ACL ACL

s1

s2

3/4/11

Point-to-point connection Two duplex slots are allocated periodically All packets are 1-slot long Packets are never retransmitted, but are protected by FEC

3/4/11

A master can support up to 3 SCO links with the

same slave or with different slaves

A slave can support up to 3 SCO links with the

same master and up to 2 SCO links if they originate from different piconets the SCO period TSCO and the SCO offset DSCO

The SCO link is established by the master sending Even if a slave fails in decoding the slave address in
the SCO packet header, it can access the channel in the following slot
3/4/11

18

Same as SCO but: configurable data rate: packet length & periodicity may be asymmetric limited retransmissions of lost or damaged packets inside a retransmission window (ritx must be done in the slots following the reserved ones) Packets may not be protected by FEC, but carry a CRC Packets may be more than 1 slot long (packet length and periodicity are fixed at the link connection establishment and remain unchanged)
3/4/11

Point-to-multipoint link between the master and the slaves within the piconet and point-to-point link between a slave and the master Can use all the slots not allocated to (e)SCO traffic ACL traffic is scheduled by the master Multi-slot packets can be used Packets can be retransmitted

3/4/11

Between a master and a slave one ACL link only

can exist

An ACL link is always established between a

master and a slave since it must be used to exchange LMP messages

If a slave fails in decoding the slave address in

the packet header, it cannot access the channel in the following slot
3/4/11

19

Control packets ID* Null Poll FHS

Data/voice/transparent data packets

Voice Transparent data Data

HV1 HV2 HV3 DV

EV3 EV4 EV5 x-EV5

x-EV3 DM1 DM3 DM5

x-DH1 x-DH3 x-DH5

combines voice and data (voice field+data field)

x = 2, 3: it indicates the used modulation (2=/ 4DQPSK; 3=8DPSK)

3/4/11

72 bits Access code

54 bits Header

0 - 2744 bits Payload

SCO traffic No CRC No retries FEC (optional)

eSCO

CRC

header
ARQ

dati

CRC

Retries FEC (optional)

FEC (optional)

3/4/11

Access Code (72 bits): Used for synchronization and to identify the piconet, or for inquiry and paging (see next) If the piconet cannot be identified by the receiver, the packet is discarded Header (54 bits): Encoded with a 1/3 FEC In ACL, if not correctly received, the packet is discarded Payload: For ACL and eSCO packets, its covered by a 16-bit CRC Payload header only for ACL: indicates how many bytes are transmitted
3/4/11

20

Three different access codes exist: Channel Access Code (CAC): identifies a piconet Inquiry Access Code (IAC): 64 possible access codes used in the inquiry procedure 1 General Inquiry Access Code (GIAC) 63 Dedicated Inquiry Access Codes (DIAC)

Device Access Code (DAC): used in paging

and response to paging

3/4/11

AM_ADDR: 3 bit active member address TYPE: 4-bit packet type (e.g., SCO, ACL, duration) FLOW: 1-bit flow control (=0 if rx buffer is full) ARQN: 1-bit ack indication SEQN: 1-bit sequence number (inverted at each packet tx so that 2 correct tx of the same packet can be distinguished) HEC: 8-bit header error check
3/4/11

72 bits 54 bits Access code Header Guard Sync

0 - 8216 bits Payload

Trailer

GFSK

DPSK

3/4/11

21

 Guard Time (5 s): Period between the end of the last GFSK symbol of the header and the start of the reference symbol of the synchronization sequence Sync (11 s): consists of a reference symbol (with arbitrary phase) followed by ten DPSK symbols. Trailer (2 symbols): 0/1 sequence used for extended DC compensation

3/4/11

HV (High quality Voice): Used for SCO links Bit-rate=64 Kbps 2 packets every Tsco slots are sent HV1: with 1/3 FEC; 6 packets every 6 slots (i.e., 2+2+2) HV2: with 2/3 FEC; 4 (2+2) packets in 6 slots, followed by (1+1) packets in 6 slots, and so on HV3: with no FEC; 2 packets every 6 slots
3/4/11

72 bits 54 bits Access code Header

240 bits 30 bytes Payload

= 366 bits

HV1 HV2 HV3

10 bytes 20 bytes

+ 1/3 FEC + 2/3 FEC

30 bytes

3.75ms (HV1) 2.5ms (HV2) 1.25ms (HV3)

3/4/11

22

 EV (Enhanced quality Voice): Used for eSCO links (voice or transparent data) Bit-rate >= 64 Kbps Each packet carries a 16-bit CRC code 2 packets every TeSCO slots are sent EV3: up to 30 bytes; cover 1 slot EV4: up to 120 bytes+2/3 FEC; cover 3 slots EV5: up to 180 bytes; cover 3 slots
3/4/11

Also available for eSCO under EDR: 2-EVx and 3-EVx packets whose payload is modulated by /4-DQPSK and 8DPSK Up to 540 bytes per packet for 3-EV5 packets

3/4/11

DH/M (Data High/Medium rate): Used for ACL links DM: with 2/3 FEC DH: no FEC Possible packet duration: 1, 3, 5 slots DM1, DM3, DM5 DH1, DH3, DH5
3/4/11

23

 Introduced by EDR Similar to DH packets but payload modulated by / 4-DQPSK and 8DPSK No FEC, only CRC-16 Possible packet duration: 1, 3, 5 slots 2-DH1, 2-DH3, 2-DH5 3-DH1, 3-DH3, 3-DH5 3-DH5: up to 1023 bytes per packet (including payload header)+ CRC

3/4/11

625 s
72 bits 54 bits Access Header code 240 bits

= 366 bits

30 bytes Payload Dir Size

17 17

Freq
1600/2

Max Rate
108.8 108.8

DM1
1 17 2 2/3 FEC 2

DH1 1
625 s

27 27

172.8 172.8

27

3/4/11

1875s
54 72 bits bits
Access code Header

1500 bits

= 1626 bits

187 bytes Payload Dir Size

121 17

Freq
1600/4

Max Rate
387.2 54.4

2/3 FEC 2

DM3

121

DH3 2
1875s

183 27

585.6 86.4

183

3/4/11

24

3125 s
54 72 bits bits
Access Header Code

2744 bits

= 2870 bits

343 bytes Payload Dir Size

224 17

Freq
1600/6

Max Rate
477.8 36.3

DM5 2 DH5 2
3125 s

224

2/3 FEC 2

339 27

723.2 57.6

339
625 s

3/4/11

3125 s
54 72 bits bits +8216 bits

Access Header 16 s + 1025 bytes + 6 bits Code

Payload

Dir

Size
1021 27

Freq

Peak Rate
2178.1 57.6

3-DH5

1021
625 s

3125 s

3/4/11

3/4/11

25

 SCO and eSCO traffic always have priority due to delay requirements ACL link: a round-robin scheduling has been proposed by Ericsson
Not the most efficient solution in the case of asymmetric traffic For asymmetric traffic, its better to transmit to the same slave (or let the slave transmit) for a longer time DH/M-3 and DH/M-5 packets can be used to reduce the overhead
3/4/11

Stop-and-Wait Applied to x-EV and x-DM/H packets only If the master is receiving, it can send the ACK in the slot next to the received packet even if the master transmission is toward a different slave (fast Stop&Wait) the time latency is reduced in this case the ACK is sent by setting the ARQN bit to 1
3/4/11

POLL: CAC+Header only, used by the master to poll a slave which must respond. Not a part of the ARQ scheme NULL: CAC+Header only, used to return information to the source such as ARQN and FLOW ID: consists of the DAC or IAC (68 bits), used in inquiry, paging and response routines FHS: control packet revealing the senders address and clock (144 bits+16-bit CRC)
3/4/11

26

 Used to discover other devices and exchange

synchronization information (HW address and clock) This allows two nodes to agree on a common channelhopping sequence (for paging): Address used to select the sequence
Clock used to select the sequence phase

Asymmetric procedure Listener and sender hop using the same sequence but the sender hops faster than the listener
3/4/11

The interval between two consecutive inquiry procedures is a random variable so that synchronization between two or more entities performing the procedure is avoided Typically, the sender repeats the procedure for about 10 s every minute The sender stops repeating the procedure when it has contacted a sufficient number of nodes
3/4/11

The sender uses a known-to-all inquiry hopping sequence and IAC The sender can specify the class of devices to contact by using a dedicated instead of a general inquiry access code

3/4/11

27

The sender: Keeps transmitting the IAC on different frequencies Every 1.25ms transmits on two hops and listens whether there is a response from neighboring units
f(k) f(k+1) f(k) f(k+1) f(k+2) f(k+3)

625 s
3/4/11

The sequence comprises 32 frequency hops: It is divided into 2 sub-sequencies of 16 hops, each lasting 10 ms (625 s16=10 ms) The single sub-sequence is repeated 256 times, i.e., for 2.56 s To discover neighbors, 4 trains of sub-sequences have to be transmitted Inquiry may have to last 10.24 s (42.56=10.24) It may finish earlier if many responses have been collected
3/4/11

A listener, i.e., a unit that wants to be discovered, periodically enters the inquiry scan state and listens to one frequency only for a while When it detects an inquiry message, it has the option to not reply If it replies, it uses a FHS packet with the same access code and the common sequence, called inquiry response Interval between two consecutive inquiry scans equal to 2.56 s. Each time the unit listens to a different frequency for 10 ms
3/4/11

28

 Listeners: when more than one listener is present, their replies may collide to avoid collisions, listeners defer their replies until expiration of a random back-off timer the FHS packet is retransmitted at other times and frequencies as long as the master is probing with inquiry messages
3/4/11

Sender: collects device address and clock offset from the listeners this information is subsequently used to page the selected listener

3/4/11

inquiring unit

f(k)

f(k+1)

f(k)

625 s

ID
inquiry responding unit

ID FHS

625 s

Received packet
3/4/11

29

IDa

IDd

A
INQ

IDb

IDc

B,C,D are in Inquire Scan

3/4/11

IDb

IDa

IDd

A
FHS IDb

IDc

B,C,D are in Inquire Scan

3/4/11

IDb

IDa

IDd FHS

IDb

B
FHS

IDc

C and D respond simultaneously: their FHSs are lost

3/4/11

30

IDb

IDa

IDd

A
INQ

IDb

IDc

A issues an inquiry again

3/4/11

IDb IDc

IDa

IDd

IDb

B
FHS

IDc

C responds with an FHS

3/4/11

IDb IDc IDd IDb

IDa

IDd FHS

IDc

A issues an inquiry again and D responds

3/4/11

31

 Used to establish connections and define roles

Steps similar to Inquiry, BUT Paging message is unicast to a selected listener (ID packet uses the DAC) listener does not need to back-off The sender has also an estimate of the listeners clock it is enabled to communicate with the listener almost istantaneously
3/4/11

Several paging schemes can be applied

Mandatory paging scheme: supported by all units; used when 2 units meet for the first time and when paging directly follows the inquiry procedure Once connected, 2 units may agree on an optional paging/scanning scheme to be used next time it is needed
3/4/11

The paging unit: Knows the address (DAC) of the unit to page (X) Derives the hopping frequency to be used for paging from Xs address However, usually the pager and X are not perfectly sync. Thus, the pager does not know exactly: when X will listen to the channel on which frequency (i.e., Xs phase)
3/4/11

32

 The paging sequence is 32-hop long and is divided into two sub-sequences of 16 hops each (in U.S.) The paging unit periodically repeats the paging sequence

3/4/11

The paging unit: keeps transmitting Xs access code on different frequencies every 1.25 ms transmits on two hops and listens whether there is a response from X
f(k) f(k+1) f(k+2) f(k+3)

625 s
3/4/11

There isnt a paging channel

X has to periodically listen to the channel to detect whether there is a paging message for itself

X listens to the channel to detect whether the access code derived from its own address is being transmitted X scans the channel at least every 1.28 s (R1 mode) or 2.56 s (R2 mode), and each time listens to a different frequency for 10 ms
3/4/11

33

 When X receives the paging msg, it replies back with an ID packet using a sequence called paging response, derived from its address The pager replies by sending its own address and clock information (FHS packet) and using the same hopping frequency and access code employed by X X sends an acknowledgment with the same hopping frequency and access code After that, the paging unit (i.e., the master) starts the data exchange by using the hopping sequence of the piconet, derived by its own address and clock
3/4/11

paging unit

f(k)

f(k+1)

f(k)

f(k+1)

f(k+1)

625 s

ID
paged unit

ID ID

FHS

message exchange follows ID after a poll +null

625 s

Received packet
3/4/11

Upon receiving a response for the paging

message, the sender becomes the master and the listener the slave of a newly formed piconet Both nodes switch to the piconet channelhopping sequence

3/4/11

34

IDc

IDa

IDc

IDc

A knows Cs ID and has an idea of its clock

3/4/11

IDc

IDa

IDc

IDc

3/4/11

IDc

IDa

IDa

IDc

A replies with its ID and clock (FHS packet)

3/4/11

35

IDc

IDa

IDc

IDc

IDa

3/4/11

IDc

IDa

IDc

IDa

Then, A connects as a master to C

3/4/11

Typically, masters have a much higher computational and communication load, thus experiencing higher energy consumption than slaves do Master and slave can switch role within the piconet through an appropriate procedure

3/4/11

36

Cordless headset Cordless headset

mouse

Cordless headset

3/4/11

3/4/11

A slave can belong to two or more piconets, but cannot communicate with more than one at the same time It must use time multiplexing by being in suspend (i.e., hold, park, or sniff mode) in a piconet and active in another A slave can leave its current piconet (after informing its current master about the duration of the leave) and join another piconet

3/4/11

37

3/4/11

A master in one piconet can also act as a slave in another piconet (but not as a master) How to schedule presence in two piconets? Forwarding delay? Missed traffic?

3/4/11

Device 1

Device 2

Baseband Physical

Baseband

FH/TDD physical layer Various types of links (SCO, eSCO, and ACL) Multiple packet types (multiple data rates with and without FEC) Device inquiry and paging Scatternet
3/4/11

38

Applications
IP

Setup and management of Baseband connections

ol

SDP

RFCOMM

Audio

L2CAP LMP
LMP

Baseband RF
3/4/11

Attach and detach slaves Master-slave switch Establishing ACL and SCO links Handling of low power modes ( Sniff, Hold, Park)
Paging @ Baseband

m
Master

LMP Accepted
3/4/11

Detach: The connection between 2 units can be closed anytime either 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 A Reset procedure occurs in the case of an abrupt link failure
3/4/11

Slave

Co

Data

Piconet Management Link Configuration Security

ntr

LMP_host_conn_req

39

 The pager becomes the master, but a switch between slave and master may occur if both agree on it First, a TDD switch is performed between the old and the new master A piconet switch for all the piconet participants follows

3/4/11

The piconet switch is done with one piconet participant at a time: The new master sends a time allignment command and an FHS packet and waits for an ack (ID packet) from the slave From then on, that slave uses the new master parameters for its communications Information on the piconet participants may be transfered from the old to the new master
3/4/11

Standby: The node is not connected to anyone through a traffic link However it listens to the channel checking every 1.28 s (or 2.56 s) over 32 frequency hops if there are msgs from a master sent to itself Page/Inquiry-scan Connected: The node is connected to another node through a traffic link
3/4/11

40

detach/reset

standby

unconnected state, only the native clock is running @ the LPO

page

page scan

inquiry scan

inquiry

master response

slave response

inquiry response

connetd

3/4/11

connecting states (7)

inquiry standby

low-power states active states

sniff

page connetd 2ms hold

2ms active park

3/4/11

The node transmits and/or receives traffic

3/4/11

41

 Defined for slaves only, the slave listens for Dsniff slots every Tsniff and for a Nsniff attempt number of times The master issues a sniff command indicating the Tsniff period, the Dsniff, and Nsniff The slave remains synchronized to the piconet and maintains its MAC address Listens to the channel while consuming little energy The master can force the slave into sniff mode; both the slave and the master can request to put the connection in sniff mode or to move back to active mode
3/4/11

Sniff offset Sniff slots Slave Sniff period Master

Traffic reduced to periodic sniff slots

3/4/11

Master and slave agree on the hold time duration. Both of them can request hold mode Tx/rx in one piconet/inquiry/paging/scanning and in hold state in the other ACL link can be put in hold mode also to save energy (if so, the unit in hold turns off its receiver) Maintains its MAC address Returning from hold, it must listen for the master and resync its clock offset
3/4/11

42

Hold offset Slave

Hold duration Master

3/4/11

The master can force a slave in park mode; either the slave or the master can require to put the connection in park mode The master can force the park mode to one slave at a time The node does not participate in piconet activity and does not have a MAC address (PM_ADDR for the unpark master initiated procedure, AR_ADDR for the unpark slave initiated-procedure)
3/4/11

Remains synchronized to the piconet waking up periodically to listen to the beacons from the master Returning from park, it must listen for the master and resync its clock offset A slave can send an unpark request in a proper halfslot after a broadcast packet sent by the master to poll parked slaves. The slave can unpark when it receives an ack by the master

3/4/11

43

Slave

Beacon instant
Master

Beacon interval

Power saving + keep more than 7 slaves in a piconet Give up active member address, yet maintain synchronization Communication via broadcast LMP messages
3/4/11

Low power consumption* Standby current < 0.3 mA 3 months Voice mode 8-30 mA 75 hours Data mode average 5 mA (0.3-30 mA, 20 kbit/s, 25%) 120 hours Low Power Architecture Programmable data length (else radio sleeps) Hold and Park modes 60 A Devices connected but not participating Device can participate within 2 ms
*Estimates calculated with 0.6 Ah battery
3/4/11

Applications
IP

Setup and management of Baseband connections

ol

SDP

RFCOMM

Audio

L2CAP LMP
LMP

Baseband RF
3/4/11

Co

Data

Piconet Management Link Configuration Security

ntr

44

 Quality of service
Polling interval for ACL traffic Packet type negotiation (multi-slot packets) Broadcast repetition

Power control

Paging @ Baseband

Master

LMP_quality_of_se rvice

LMP_not_Accepted

3/4/11

Mandatory for class 1 devices and optional otherwise In practice, most devices are class 2 and most
support power control

A device can send increase or decrease link manager

commands to another device based on the RSSI

The specification defines a 20dB golden window with

the lower limit at least 6dB above the receiver sensitivity. If the RSSI falls within this window, no power adjustment is requested
3/4/11

Applications
IP

Setup and management of Baseband connections

ol

SDP

RFCOMM

Audio

L2CAP LMP
LMP

Baseband RF
3/4/11

Co

Data

Piconet Management Link Configuration Security

ntr

Slave

45

Goals: Authenticated access

Only accept connections from trusted devices

Constraints: Processing & memory limitations (e.g., $10 headsets)

Paging @ Baseband
LMP_host_conn_req LMP Accepted

Privacy of communication Prevent eavesdropping

Master

Security procedure LMP_setup_complete LMP_setup_complete

3/4/11

It is a mandatory feature Authentication is based on a challenge/response mechanism using a link key (128 bit shared secret between two devices) How can link keys be distributed securely?

Verifier

Challenge (RN) response accepted

Link key

Link key

Claimant

3/4/11

Pairing is a process of establishing a trusted secret channel between two devices (construction of initialization symmetric key Kinit) Kinit is used for initial authentication and then to distribute link keys

PIN

Verifier

+ address Random number Kinit

Random number challenge response accepted

Claimant

PIN

+ address Random number Kinit

PIN=Common

PIN entered in 3/4/11 both the devices

Slave

46

 It is optional An encryption key (configurable key length 8 128 bits, derived from the link key) and the encryption algorithm are needed
Encryption mode? Key size? Start encryption Encrypted traffic Stop encryption
3/4/11

Applications
IP

ntr ol Co

SDP

RFCOMM

Data
Audio L2CAP LMP

Logical Link Control and Adaptation Protocol L2CAP provides:

Protocol multiplexing Segmentation and reassembly Quality of service negotiation
3/4/11

Baseband RF

Goals Hides peculiarities of lower layer protocols from the upper layers thus providing great flexibility in supporting higher layer protocols

Provides services to ACL traffic links

3/4/11

47

IP

RFCOMM

IP

RFCOMM

Multiplexing demultiplexing reliable, flow controlled in-sequence, asynchronous link with unlikely duplication

Baseband

Baseband pckt size is very small (17min, 339 max) cmp to HL pckts No protocol-ID field in the baseband header
3/4/11

IP

RFCOMM

IP

RFCOMM

reliable, in-sequence, flow controlled, ACL link with unlikely duplication

Desired features: Protocol multiplexing Segmentation and reassembly

3/4/11

Length IP header

Payload

Baseband packets start of L2CAP

L 2 C A P
CRC

CRC

CRC continuation of L2CAP

continuation of L2CAP

MTU (Maximum Transmission Unit): Max L2CAP PDU payload that a local device can accept min MTU = 48 B; max MTU = 65535 B default MTU = 672 B
3/4/11

48

Applications
IP

Audio

L2CAP Link Mng

Baseband RF
3/4/11

Establish L2CAP connection to remote device Query for services search for specific class of service, or browse for services Retrieve attributes that detail how to connect to the service Establish a separate (non-SDP) connection to use the service
3/4/11

Applications
IP

Co

Data
Audio L2CAP LM

ntr

ol

SDP

RFCOMM

Serial Port emulation on top of a packet oriented link Similar to HDLC For supporting legacy applications
3/4/11

Baseband RF

Co

Data

ntr

ol

SDP

RFCOMM

49

RFCOMM

RFCOMM

L2CAP

L2CAP

Functions:
framing: assemble bit stream into bytes and, subsequently, into packets transport: in-sequence, reliable delivery of serial stream control signals: emulate RTS, CTS,

Options at the TX
1. collect MTU bytes @ L2CAP and then send 2. wait until a timeout 3. send whatever is available

3/4/11

A. Tanenbaum, Computer networks, 4th ed., Prentice-Hall, 2002. J. Haartsen, The Bluetooth Radio System, IEEE Personal Comm. Magazine, Feb. 2000. B.A. Miller and B. Bisdikian, Bluetooth Revealed, Prentice Hall, 2nd Ed., 2002. B. Chatschik, An Overview of the Bluetooth Wireless Technology, IEEE Communications Magazine, Vol. 39, Dec. 2001. J. Haartsen, Paving the way for personal area network standards: An overview of the IEEE P802.15 Working Group for wireless personal area networks, IEEE Personal Comm. Magazine, March 2000.
3/4/11

50