BLUETOOTH CONCEPT
WHAT IS BLUETOOTH USED FOR ?
¾ Voice and data communication
¾ Cable replacement
¾ Personal Ad-hoc Networks and Access Point based networking
Bluetooth WAS NOT DESIGNED TO BE a WLAN (but it can be used as one) WHO IS BLUETOOTH ?
The Bluetooth Technology got it's name from the Viking King:
Harald Blaatand "Bluetooth" II King of Denmark 940-981
He preferred blueberries. That's why his teeth became blue most of the time.
One of his skills was getting people to talk to each other, and during his rule Denmark and Norway were christianized and united.
SPECIFICATIONS
Radio Band:
Bluetooth works in the so called ISM Band (Industrial, Scientific and Medical band) RF- Band: 2.400 - 2483 GHz, in USA, Europe and most other countries. This interferes with 802.11 WLANs (Wifi)
Channels: 23 or 78, depends on the local radio regulation authority. Each channel has a bandwidth of 1 MHz.
Frequency Hopping:
For each transmission of a packet, another radio channel is used. This is called frequency hopping and occurs approximately 1.600 times a second. Power classes:
1: 100mW 20dBm 100 m 2: 2,5 mW 4dBm 25 m 3: 1 mW 0dBm 10 m Data rate:
1 Mega Symbols per Second (MSPS), 720 Kbps Packet length:
max. 2871 Bit Security:
128 Bit key, PIN-Numbers, Pairing, Authentication
FRAME TRANSMISSION
Frames are transmitted in a frequency hopping system. This means that the radio channel is changed after one frame has been transmitted. Usually a frame transmission is not longer than 625 µs which is called a slot. However frames can last 1, 3 or 5 slots. If a frames is 3 or 5 slots, hopping into another channel occurs only after the transmission has finished. Changing the radio channel during a
transmission makes no sense.
Source: Bluetooth Spec. 1.1
FREQUENCE HOPPING
This is an example of frequence hopping scheme. At each slot (625 µs) a new channel is chosen for the transmission. When a frame is 3 or 5 slots long, the hopping is done after the transmission is completed.
The following diagram shows the possible usage of the 79 channels of two Piconets in the same area. It is very seldom that a channel is used by both Piconets at the same time. This diagram is a little bit idealistic, because the timing of the both Piconets is fully independent from each other. That's why the slots usually do not match exactly like it shows in the diagram.
Piconet 1 is red.
Piconet 2 is blue
It happens in Slot k+11 that the two Piconets share the same channel. The message transmitted will be lost of curse but at the next Slot both Piconets use different channels and can initiate a retransmission.
.
A hopping generator calculates the next channel for each transmission. The hopping generator uses a part of the device’ MAC address for initialization. That's why the hopping generator of each Bluetooth device starts with a different initialization value which will lead to a different hopping sequence.
When two or more Bluetooth devices wants to communicate with each other, they must use the same
Cha
nnel Slot
k k+1 k+2 k+3 k+4 k+5 k+6 k+7 k+8 k+9 k+10 k+11
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
:
:
67
68
69
70
71
72
73
74
75
76
77
78
79
this happen, the devices must be synchronized with each other. In Bluetooth networks, a so called Master synchronizes the other devices (called Slaves) to it’s own hopping generator. The master must send it’s own ID (part of the Mac address) and the current value of the hopping generator to the slaves.
The slaves re-initalizes their own hopping generator to get synchronized to the hopping sequence of the master.
When a Slave is synchronized to a Master, the Slave has become a member of the Master's Piconet!
M
S
S P
Sb M
S S
P S
Sb
PICONET - SCATTERNET
NETWORK ARCHITECTURE
The following diagram shows two independent Piconets. Each one has a master (M) and several slaves (S, Sb or P). The master controls the Piconet. A Bluetooth device can also have connections into several Piconets at the same time. This is called a Scatternet.
Each Piconet must have a master (M). The master can also be a slave in another Piconet at the same time.
Slaves can be active (S), standby (Sb) or parked (P). Active means the slave communicates with the master. Standby means the slave is in a power done mode and is not a member of the Piconet. Parked slave is a slave which is a member of the Piconet bus is in a power save state. It does not communicate but wakes up from time to time and listens the communication.
It is said, that up to 10 Piconets can share the same area without interfere each other too much.
Each Bluetooth device can become master or slave (symmetric).
PICONET
The master can connect to 7 simultaneous active or up to 255 parked slaves
M
S S
P S
Sb
sequence.
¾ For synchronization the master gives its device ID (=MAC address) and clock to the slaves.
¾ All devices in a Piconet hop together. They calculate the same hopping sequence from the moment;
they are synchronized to the masters hopping sequence.
¾ The hopping sequence is determined from the master's device ID (48 bit MAC address) and the
master's clock.
¾ Slaves in Sb mode are not joined to a Piconet means they are not synchronized to the masters
hopping sequence.
Slaves in P mode do not transmit data but stay synchronized with the master.
¾ M and S are addressed with Active Member Address (AMA, 3-bits).
¾ P are addresses with Parked Member Address (PMA, 8-bit).
SCATTERNET
Several Piconets in the same area can form a Scatternet. In a Scatter-net, a Slave can be connected to several Masters at the same time. Because each Piconet has its own hopping sequence, it happens very seldomely, that two or more Piconets use the same radio channel at the same time. In this case, the transmission will be corrupted, but just at the next packet, they should all use different channels to continue communication.
INQUIRE AND PAGE
INQUIRE
¾ Master wants to know about other devices in it's range.
¾ Master sends Inquire frames on different frequencies
in order to reach all other devices in it's range.
¾ Devices responds with Inquire Scan.
PAGE
¾ Master joins a slave into it's Piconet.
¾ The Master has to synchronize the slave to the frequency hopping scheme
of the Piconet
¾ To do so, the master sends it's device ID (MAC-Address) and clock to the slave.
¾ The slave can calculate the frequency hopping scheme out of the
masters ID and clock.
EXAMPLE: INQUIRING FOR DEVICES
The Master want to know which devices are in its range.
¾ Master (M) sends an Inquiry.
¾ Device C responds with it's ID (C) and clock (7:23).
¾ Master sends an Inquiry again.
¾ Device B responds with it's ID (B) and clock (3:01).
¾ Master sends an Inquiry again.
¾ Device A responds with it's ID (A) and clock (2:18).
¾ Master knows now the ID's and clocks of the devices in it's range
EXAMPLE: PAGE FOR DEVICES - C
The Master wants to join a Slave into its Piconet.
Master must know the ID and clock of the slave it wants to page, because it can calculate the current channel on which the slave listens.
M
B A ID m
ID a
ID b 1:37
3:01 2:18 ID c 7:23
ID b 3:01 ID a 2:18
C
ID c 7:23
¾ Master pages C with C's ID and clock.
¾ C responds to the master.
¾ Master sends it's ID (M) and clock (1:37) to C using a FHS packet.
¾ C reinitializes its hopping generator and is now synchronized to the Piconet of master M.
M
B A ID m
ID a
ID b 1:37
3:01 2:18 ID c 7:23
ID b 3:01 ID a 2:18
C ID c ID m
1:37
M
B A ID m
ID a
ID b 1:37
ID c 7.23 ID b 3.01 ID a 2:18
C ID c ID m
1:37
ID m
ID m 1:37
1:37
Master must know the ID and clock of the slave it wants to page, because it can calculate the current channel on which the slave listens.
¾ Master pages B with B's ID and clock.
¾ B responds to the master.
¾ Master sends it's ID and clock to B using a FHS packet.
¾ B is now synchronized to the Piconet of master M.
¾ Master pages A with A's ID and clock.
¾ A responds to the master.
¾ Master sends it's ID and clock to A using a FHS packet.
¾ A is now synchronized to the Piconet of Master M.
FRAME FORMAT
BASEBAND FRAME FORMAT
General format:
AM-Addr: Active member Address (3 Bit). When a device is joined to a Piconet (when it is pages) the Masters assigns an AM address to that device. The AM-Address 000 is reserved for the Master.
Type: (4 Bit) hold an packet type identifier. There exists 14 different packet types for Bluetooth transmission. They will be explained in the next chapter.
Flow: (1 Bit) This bit will be set when a device indicated that it is not able to receive due to buffer overrun.
ARQN & SEQN: (2 Bit) This bits are used for transmission error control. With this bits the devices signals, that a transmission before has been successful or not.
HEC: Header checksum
The Payload can be used for Baseband internal management or for data transmission. There exists two different kinds of data transmission: ACL and SCO. They will be discussed in the over next chapter.
AM Addr Type FLOW ARQN SEQN HEC
Access Code Header Payload
PAKET TYPES
Bluetooth Baseband communication uses 14 different packet types. The first three are use for Baseband specific activities, the others can be used for Bluetooth internal management as well as for data
communication of higher protocol layers. The packet sizes are limited to a maximum of 2871 Bits for a 5 slot packet.
PACKET TYPES
Source: Bluetooth Spec. 1.1
FHS:
Frequency Hopping Synchronization. This packet type is used, when a Frequency Hopping Synchronization occurs i.e. when a Master pages a Slave or a Slave answers for an Inquiry.
HV1 HV2 and HV3:
This packet types are used in SCO links only. They are used for voice transmission and do not have a CRC. SCO frames will never be retransmitted, when they got lost. This three packet types differ in the amount of bytes for payload. The maximal transmission speed for this packet type is 64 kb/s, sufficient for voice communication.
DV:
This packet type is used ins SCO links only. It has a Voice payload of 10 Bytes and an additional data payload of up to 9 Bytes. It will be used in case when in an voice communication additional data must be transmitted.
DM1, DM3 and DM5:
This packet types are used for ACL links. They are used for data transmission of higher layer protocols as well as local link management. The payload could be up to 17 Bytes (DM1), 121 Bytes (DM3) or 224 bytes (DM5)
DH1, DH3 and DH5:
This packet types are used also for ACL links only. Thy can transmit more payload with a higher rate. The payload could be up to 27 Bytes (DH1), 183 Bytes (DH3) or 339 Bytes (DH5)
AUX1:
This packet type is also used in ACL links only. It has a slower data rate and a maximum payload of 29 Bytes. The main difference to the other ACL packet types is, that AUX1 do not have a CRC. Retransmission of those packets will not be possible.
TYPE code
Slots Name Meaning
0000 1 NULL Null
0001 1 POLL Polling
0010 1 FHS Frequency Hopping Synchronization 0011 1 DM1 Data Medium Rate, Frame length 1 slot 0100 1 DH1 Data High Rate, frame length 1 slot 0101 1 HV1 High quality Voice, 10 bytes payload 0110 1 HV2 High quality Voice, 20 bytes payload 0111 1 HV3 High quality Voice, 30 bytes payload 1000 1 DV Data Voice, Voice and data payload
1001 1 AUX1
1010 3 DM3 Data Medium Rate, frame length 3 slots 1011 3 DH3 Data High Rate, frame length 3 slots 1100 3 Undefined
1101 3 Undefined
1110 5 DM5 Data Medium Rate, frame length 5 slots 1111 5 DH5 Data High Rate, frame length 5 slots
The following list shows the maximum data rate for the different packet types. This data rates are negotiated when a link has been established. A link can be established with a symmetric or a
asymmetric data rate. I.e. an asymmetric link can receive with a higher data rate that it can transmit.
This is something we can find in DSL connections also.
Source: Bluetooth Spec. 1.1
In SCO links, the Master has to poll the Slaves in fixed intervals so often, that they reach the desired data rate.
In ACL links the maximum rate depends also on the network load. When many Active Members want to transmit heavy load at the same time, the data rate will decrease.
Type Symmetric kb/s
Asymmetric kb/s forward reverse
HV1, HV2 HV3 64 - -
DV 64 + 57,6
DM1 108,8 108,8 108,8
DH1 172,8 172,8 172,8
DM3 258,1 387,2 54,4
DH3 390,4 585,6 86,4
DM5 286,7 477,8 36,3
DH5 433,9 723,2 57,6
AUX1 185,6 185,6 185,6
CONNECTION TYPES ACL / SCO
SCO Synchronous Connection-Oriented
The packet types HV1, HV2 HV3 and DV are used in SCO links. SCO links are used for transmission of real time traffic, because the bandwidth for a SCO link of 64 kb/s is guaranteed in a Piconet. The Master has to take care that a device in a SCO link is polled often enough to fulfill it's data rate.
Frames in an SCO link are not error checked. When they got lost or corrupted, there is no automatic correction of retransmission. Because SCO links are used for voice communication, it is not a big problem if they got lost.
ACL Asynchronous Connection-Less
The packet types DM x and DH x and AUX1 are used for ACL links. In ACL links the bandwidth is not guaranteed in a Piconet. But it is sure that a device can not use more than the maximum bandwidth allocated to the link.
When a link has to be established, it is negotiated whether a symmetric or asymmetric traffic load is used. In the symmetric link, the maximum data rate in each direction are the same. In asymmetric links, the data rates differ.
All packets in an ACL link are error checked (exception AUX1). I case they got corrupted or lost, a retransmission is initiated. The ARQN and SEQN bits in the frame header are used to indicate that the former transmission was successful or not.
PROTOCOL ARCHITECTURE
SOFTWARE ARCHITECTURE
The following diagram show the software architecture of the Bluetooth protocol stack. The blue line marks the border between hardware and software. The whole Baseband and parts of LMP are implemented in the Bluetooth Chipset. L2CAP and all higher protocols are usually implemented in Software. The connection between the Chipset and the host is done via a standardized interface called HCI (Host Controller Interface).
This diagram can not show all possible software stacks which are available now, because Bluetooth is fast growing with a lot of new inventions.
vCard/vCal
AT-
RFCOMM
SDP
Audio
L2CAP PPP
IP UDP/TCP
WAP
TCS-BIN OBEX
LMP Baseband
WAE
Host Controller Interface
Applications . . .
PROFILES AND DEPENDENCIES
BLUETOOTH PROFILES
Profiles are applications and/or services.
The following diagram shows a list of available profiles with the under laying protocol stacks.
PROTOCOL DEPENDENCIES
There are dependencies between the Profiles. If a Bluetooth device offers a spec. Profile, it must also offer the dependent.
GAP - GENERIC ACCESS PROFILE
SDAP - SERVICE DISCOVERY APPLICATION PROFILE CPP - CORDLESS TELEPHONY PROFILE &
INTERCOM PROFILE SPP - SERIAL PORT PROFILE HS - HEADSET PROFILE
DUN - DIAL-UP NETWORKING PROFILE FAX - FAX PROFILE
LAN - LAN ACCESS PROFILE
GOEP - GENERIC OBJECT EXCHANGE PROFILE OPP - OBJECT PUSH PROFILE
FTP - FILE TRANSFER PROFILE SYNC - SYNCHRONIZATION PROFILE
HCR - HARDCOPY CABLE REPLACEM HID - HUMAN INTERFACE DEVICE CIP - COMMON ISDN ACCESS PROFI PAN - PERSONAL AREA NETWORKIN HF - HANDS-FREE PROFILE
SIM - SIM ACCESS PROFILE
AVRCP - AUDIO/VIDEO REMOTE CON AUDIO/VIDEO DISTRIBUTION PROFIL BPP - BASIC PRINTING PROFILE BIP - BASIC IMAGING PROFILE
Example: If a device supports the FTP profile, it must also support the dependent GOEP, SPP and GAP profi offer functionality, which the FTP profile needs.
GAP AND SDAP
GENERIC ACCESS PROFILE (GAP)
The GAP has to introduce definitions, recommendations and common requirements related to modes and access procedures that are to be used by transport and application profiles.
To describe how devices are to behave in standby and connecting states in order to guarantee that links and channels always can be established between Bluetooth devices, and that multi-profile operation is possible.
Special focus is put on discovery, link establishment and security procedures.
To state requirements on user interface aspects, mainly coding schemes and names of procedures and parameters, that are needed to guarantee a satisfactory user experience.
SERVICE DISCOVERY APPLICATION PROFILE (SDAP)
The SDAP hat to collect the profiles from other devices within reach and stores them in a service database. This helps the Bluetooth user with identifying and using appropriate devices.
The SDAP has a lot of functions and messages go get the services and attributes about the supported profiles from the Bluetooth neighborhood
The SDAP uses the following Messages to recover its data.
• SDP_ErrorResponse
• SDP_ServiceSearchRequest
• SDP_ServiceSearchResponse
• SDP_ServiceAttributeRequest
• SDP_Service AttributeResponst
• SDP_ServiceSearchAttributeRequest
• SDP_ServiceSearchAttributeResponse
SPP, DUN, FAX AND HS
SERIAL PORT PROFILE (SPP)
The Serial Port Profile defines the protocols and procedures that shall be used by devices using
Bluetooth for RS232 (or similar) serial cable emulation. The scenario covered by this profile deals with legacy applications using Bluetooth as a cable replacement, through a virtual serial port abstraction (which in itself is operating system-dependent).
Application Serial port
emulation or other API RFCOMM
SDP
L2CAP
DIAL-UP NETWORKING PROFILE (DUN)
The Dial-up Networking Profile defines the
protocols and procedures that shall be used by devices implementing the usage model called ‘Internet Bridge’ (see Bluetooth SIG MRD).
The most common examples of such devices are modems and cellular phones.
The scenarios covered by this profile are the following:
Usage of a cellular phone or modem by a computer as a wireless modem for connecting to a dial-up internet access server, or using other dial-up services
Usage of a cellular phone or modem by a computer to receive data calls.
FAX PROFILE (FAX)
The Fax profile defines the protocols and procedures that shall be used by devices implementing the fax part of the usage model called ‘Data Access Points, Wide Area Networks’ (see Bluetooth SIG MRD).
A Bluetooth cellular phone or modem may be by a computer as a wireless fax modem to send or receive a fax message.
HEADSET PROFILE (HS)
This Headset profile defines the protocols and procedures that shall be used by devices implementing the usage model called ‘Ultimate Headset’.
The most common examples of such devices are headsets, personal computers, and cellular phones.
The headset can be wirelessly connected for the purposes of acting as the device’s audio input and output mechanism, providing full duplex audio. The headset increases the user’s mobility while maintaining call privacy.
Modem Emulation or Driver application AT-commands
RFCOMM RFCOMM
PPP SDP
L2CAP
Modem Emulation or Driver AT-commands
RFCOMM
SDP
L2CAP
AT-commands RFCOMM
SDP Audio
L2CAP
BASEBAND
GOEP, OPP, SYNCML, FTP, BIP AND BPP
GENERIC OBJECT EXCHANGE PROFILE (GOEP)
The Generic Object Exchange profile defines the protocols and procedures that shall be used by the applications providing the usage models which need the object exchange capabilities:
¾ Synchronization,
¾ File Transfer
¾ Object Push
¾ Printing
¾ Imaging
¾ and other models
The most common devices using these usage models can be notebook PCs, PDAs, smart phones, Cameras and mobile phones.
Application
RFCOMM OBEX
SDP
L2CAP
The Object Push profile defines the requirements for the protocols and procedures that shall be used by the applications providing the Object Push usage model.
This profile makes use of the Generic Object Exchange Profile (GOEP) to define the interoperability requirements for the protocols needed by applications. The most common devices using these usage models can be notebook PCs, PDAs, and mobile phones.
EXAMPLES
Usage of a Bluetooth device, e.g. a mobile phone to push an object to the inbox of another Bluetooth device. The object can for example be a business card or an appointment.
Usage of a Bluetooth device; e.g. a mobile phone to pull a business card from another Bluetooth device.
Usage of a Bluetooth device; e.g. a mobile phone to exchange business cards with another Bluetooth device. Exchange defined as a push of a business card followed by a pull of a business card.
SYNCHRONIZATION PROFILE (SYNCML)
The Synchronization profile defines the requirements for the protocols and procedures that shall be used by the applications providing the Synchronization usage model. This profile makes use of the Generic Object Exchange profile (GOEP) to define the interoperability requirements for the protocols needed by applications. The most common devices using these usage models might be notebook PCs, PDAs, and mobile phones. The scenarios covered by this profile are:
Usage of a mobile phone or PDA by a computer to exchange PIM (Personal Information Management) data, including a necessary log information to ensure that the data contained within their respective Object Stores is made identical. Types of the PIM data are, for example, phonebook and calendar items.
Use of a computer by a mobile phone or PDA to initiate the previous scenario (Sync Command Feature).
Use of a mobile phone or PDA by a computer to automatically start synchronization when a mobile phone or PDA enters the RF proximity of the computer
Object Push application OBEX
RFCOMM
SDP
L2CAP
FILE TRANSFER PROFILE (FTP)
The File Transfer profile defines the requirements for the protocols and procedures that shall be used by the applications providing the File Transfer usage model. This profile uses the Generic Object Exchange profile (GOEP) as a base profile to define the interoperability requirements for the protocols needed by the applications. The most common devices using these usage models can be (but are not limited to) PCs, notebooks, and PDAs. The scenarios covered by this profile are the following:
EXAMPLES:
Usage of a Bluetooth device (e.g. a notebook PC) to browse an object store (file system) of another Bluetooth device. Browsing involves viewing objects (files and folders) and navigating the folder hierarchy of another Bluetooth device. For example, one PC browsing the file system of another PC.
A second usage is to transfer objects (files and folders) between two Bluetooth devices. For example, copying files from one PC to another PC.
A third usage is for a Bluetooth device to manipulate objects (files and folders) on another Bluetooth device. This includes deleting objects, and creating new folders.
Synchronization application
OBEX RFCOMM
SDP
L2CAP IrMC
File Transfer application OBEX
RFCOMM
SDP
L2CAP
BASIC PRINTING PROFILE (BPP)
"Driverless Printing"
The Basic Printing Profile defines the requirements for the protocols and procedures that shall be used by applications providing the Basic Printing usage model.
This Profile makes use of the Generic Object Exchange Profile (GOEP).
The most common devices using these usage models are mobile devices such as mobile phones, pagers, and PDAs, although more complex devices are not excluded.
Usage models include printing of text emails, short messages, and formatted documents. Optional support for the printing of structured data objects such as vCard and vCalendar is also defined, as well as methods for negotiating the use of other formats supported by the printer.
Printing from sending devices such as laptops and desktop PCs, where printer specific drivers may be loaded, is defined in the Hardcopy Cable Replacement Profile
Printing application OBEX
RFCOMM
SDP
L2CAP
BASIC IMAGING PROFILE (BIP)
With this profile images from cameras can be transferred. The image is not manipulated in any way nor compressed or encoded. It is raw data material as it is stored on the cameras memory.
The following picture shows the example to transfer a image from a camera to a mobile phone for further sending.
Imaging application OBEX
RFCOMM
SDP
L2CAP
LAN AND PAN
LAN ACCESS PROFILE (LAN)
LAN Access using PPP over RFCOMM.
PPP provides authentication, encryption, data compression and multiprotocol facilities.
PPP over RFCOMM has been chosen as a means of providing LAN Access for Bluetooth devices because of the large installed base of devices equipped with PPP software.
PPP is capable of supporting various networking protocols (e.g. IP, IPX, etc.).
This profile does not deal with conferencing, LAN emulation, ad-hoc networking or any other means of providing LAN Access. These functions are, or may be, dealt with the PAN profile. The LAN Access profile defines how PPP networking is supported in the following situations.
¾ LAN Access for a single Bluetooth device.
¾ LAN Access for multiple Bluetooth devices.
¾ PC to PC (using PPP networking over serial cable emulation).
PERSONAL AREA NETWORKING PROFILE (PAN)
1. ACCESS POINT
Management Entitiy (ME)
ME
coordinates procedures during initialization, configuration and connection management:
¾
Link Establishment
¾ Single/Multi-user mode
When the NAP/GN is configured to allow multiple users, then the NAP/GN must be the master of the piconet. In this mode, the Management Entity on the NAP/GN shall ensure that the NAP/GN remains the master of the Bluetooth piconet.
2. ADHOC NETWORK
LAN Access application IP
RFCOMM
PPP SDP
L2CAP
CCP, CIP AND HCR
CORDLESS TELEPHONY PROFILE (CPP)
The Cordless Telephony profile defines the protocols and procedures that shall be used by devices implementing the use case called ‘3-in-1 phone’.
The ‘3-in-1 phone’ is a solution for providing an extra mode of operation to cellular phones, using Bluetooth as a short-range bearer for accessing fixed network telephony services via a base station.
However, the 3-in-1 phone use case can also be applied generally for wireless telephony in a residential or small office environment, for example for cordless-only telephony or cordless telephony services in a PC – hence the profile name Cordless Telephony’. This use case includes:
- making calls via the base station,
- making direct intercom calls between two terminals, and
- accessing supplementary services provided by the external network.
COMMON ISDN ACCESS PROFILE (CIP)
Define how applications shall access ISDN over Bluetooth;
llow wherever possible unrestricted access to services, data or signaling provided by ISDN;
nsure that legacy ISDN applications do continue to work without any modification inside that application itself;
Define how the ISDN access co-exists with Bluetooth Specifications and Profiles that possibly access ISDN in one way or other;
Show how ISDN over Bluetooth can co-exist with existing ISDN in one application.
This Profile strongly limits overlap with other Bluetooth Specifications or Profiles (e.g. DUN, UDI) and addresses interoperability issues in case of unavoidable overlaps.
CMG: CAPI Message Gateway. (CMG) is an optional, functional entity.
CMTP: CAPI Message Transport Protocol
HARDCOPY CABLE REPLACEMENT PROFILE (HCR)
The usage model includes printing and scanning any type of document. The data is rendered through the use of a driver on the client device.
The most common devices using these usage models are mobile laptops and desktop computers.
This profile does not include the printing of pure images such as those created by cameras and similar devices; this application is covered by the Still Image Profile. Driverless printing for mobile devices such as mobile phones, pagers, and PDAs is defined in the Basic Printing Profile.
has the following advantages over other more generic profiles:
It supports a 1284ID string, which is a transport-agnostic method for identifying a host driver; this allows the host to leverage existing solutions and extend them cleanly to include Bluetooth.
It provides a very lightweight flow control mechanism appropriate for the high data volume of printing and scanning.
It provides a method for simple asynchronous notifications.
It is connection-oriented; this should ensure more reliable behavior when a client moves out of range: a printer or scanner can recognize this and abort the current job, rather than losing data in the middle of a job.
At the same time, HCRP is expected to be relatively inexpensive to implement because:
It has a small list of relatively simple control commands.
It is implemented at a low level in the Bluetooth stack, avoiding the overhead of layers such as OBEX, RFCOMM, or PAN.
HID AND OTHERS
HUMAN INTERFACE DEVICE PROFILE (HID)
HANDS-FREE PROFILE (HF)
Audio Gateway (AG)
This is the device that is the gateway of the audio, both for input and output. Typical devices acting as Audio Gateways are cellular phones.
Hands-Free unit (HF)
This is the device acting as the Audio Gateway’s remote audio input and output mechanism. It also provides some remote control means.
SIM ACCESS PROFILE (SIM)
Access a SIM card via a Bluetooth link.
The profile enables the usage model "Personalizing the Car and its Devices" and similar usage models, Audio application
(Audio port emulation) Hands-Free ctrl
RFCOMM SDP
L2CAP
Audio application (Audio driver) Hands-Free ctrl
RFCOMM
SDP
L2CAP
which involve a Bluetooth enabled SIM card holder and a cellular phone.
For example, with this profile, the user can personalize his/her car-embedded phone with a SIM card in an external device, which is connected via a Bluetooth wireless link.
The external device can either be a simple SIM card holder or a portable phone, which is brought into the car.
The SIM Access Profile builds on the well-defined interface between the telephone and a SIM .
SIM application
RFCOMM
SDP
L2CAP SIM
AUDIO/VIDEO DISTRIBUTION PROFILE (AVDP)
Transport protocol for audio and/or video distribution connections and streaming of audio or video media over the Bluetooth air interface. Audio and video data streams require isochronious data transmission.
The transport mechanism are based on RTP.
Commands and responses for executing the stream set-up procedures are defined as Bluetooth specific.
AVDTP defines the binary transactions between Bluetooth devices for stream set-up and media streaming for audio and video using L2CAP.
A/V streaming and stream set-up signalling are transported via L2CAP packets.
A dedicated Protocol/Service Multiplexer (PSM) value is used to identify L2CAP packets that are intended for AVDTP.
AUDIO/VIDEO REMOTE CONTROL PROFILE (AVRCP)
The Audio/Video Remote Control Profile (AVRCP) defines the features and procedures required in order to ensure interoperability between Bluetooth devices with audio/video control functions in the Audio/Video distribution scenarios.
This profile specifies the scope of the AV/C Digital Interface Command Set (AV/C command set, defined by the 1394 Trade Association) to be applied, and it realizes simple implementation and easy operability.
In this profile, the controller translates the detected user action to the A/V control signal, and then transmits it to a remote Bluetooth device.
The functions available for a conventional infrared remote controller can be realized in this profile. The remote control described in this profile is designed specific to A/V control
Note that the Audio/Video Remote Control Profile does not handle the audio/video streaming.
Application
AVCTP
SDP
L2CAP AV Control
WIDCOMM
WIDCOMM, Inc offers a complete Bluetooth protocol stack for Windows platforms, which are adapted by many vendors:
Bluetooth Spec 1.1 compliant Windows protocol stack and profiles.
• Generic access profile Service discovery app profile
• Synchronization profile
• Object push profile
• Dial-up network profile Serial port profile
• Generic object exchange profile
• File transfer profile
• LAN access profile
Support for Windows 98 SE, Millennium Edition, 2000 and XP.
User Interface including Shell Extension, System Tray and Control Panel applications.
Extensive documentation that exposes and details Bluetooth wireless technology application programming interface (API).
Optional Test Spy test tool (trace, diagnostic and debug tools) to exercise the BTW communication software.
Sample application programs demonstrating Bluetooth out of the box connectivity.
No PAN Profile in current version
Audio Gateway
The Audio Gateway Application allows a remote Bluetooth device to use this computer’s microphone and speakers as the remote device’s audio input and output devices.
Bluetooth Serial Port
The Bluetooth Serial Port application allows this computer to establish a wireless serial connection with a remote Bluetooth device. The applications on both this computer and the remote device must be configured to send and receive data to and from the respective communications port (COM port) assigned to the Bluetooth serial port.
Dial-up Networking
The Bluetooth Dial-up Networking application allows this computer to use a modem that is physically connected to a remote device to access the Internet, log on to a remote network. After the Bluetooth dial-up networking connection is established it can be used the same way as any other networking connection.
Fax
The Bluetooth Fax service allows this computer to send a fax using a Fax/Modem that is physically connected to a remote device.
File Transfer
The Bluetooth File Transfer application allows this computer to perform file operations on the Bluetooth Exchange Folder (and the folders and files it contains) of a remote device.
Printer
The Bluetooth Printer application allows this computer to use a Bluetooth printer. Once a Bluetooth printer has been properly installed it can be used from this computer in the same way as any other printer would be.
Headset
The Headset application allows this computer to use a Bluetooth as the audio input and output device for this computer. Possible uses include:
¾ If this computer has on-board telephone hardware, a Bluetooth headset might be used as the audio
input/output device to make/receive telephone calls.
¾ If this computer has voice recognition capabilities, a Bluetooth headset might be used as the audio
input device.
¾ Any other scenario that requires audio input/output can potentially take advantage of a Bluetooth
headset to replace a hardwired microphone and/or speakers.
Network Access
The Bluetooth Network Access application makes it possible for this computer:
¾ To connect to a Local Area Network via a physical connection on a remote Bluetooth device.
¾ To connect to an ad hoc network provided by a remote Bluetooth device. The type of network
connection that is available is determined by the configuration of the remote Bluetooth device.
PIM Synchronization
The PIM Synchronization Application is used to synchronize the Personal Information Manager (PIM) database of this computer with the PIM database of a remote Bluetooth device.
PIM Item Transfer
The Bluetooth PIM Item Transfer application allows this computer to send and receive Personal Information Manager items to-and-from a remote Bluetooth device.
BLUETOOTH SERVICES
Audio Gateway
The Bluetooth Audio Gateway service allows this computer to use a remote Bluetooth device’s microphone and speakers as this computer’s input and output devices.
For example, if this computer has voice recognition capabilities, a Bluetooth headset might be used as the audio input device.
¾ The Bluetooth radio on both this computer and the remote device must support audio.
¾ The remote device handles both audio input and output for this computer; therefore, this computer
does not require a sound card, microphone, or speakers.
Bluetooth Serial Port
The Bluetooth Serial Port service allows a remote device to establish a wireless serial connection with this computer. The wireless serial connection may be used by applications as though a physical serial cable connected the devices. The connection must be initiated from the remote device by the Bluetooth Serial Port application.
Dial-up Networking Service
The Bluetooth Dial-up Networking service makes it possible for a remote Bluetooth device to use a modem that is physically connected to this computer. The remote device can then access the Internet or log on to a remote network.
Fax Service
The Fax service allows a remote Bluetooth device to send a Fax via a modem that is physically attached to this computer.
The File Transfer service allows this computer to perform file operations on the Bluetooth Exchange Folder (and the folders and files it contains) of a remote device.
Headset Service
The Bluetooth Headset Service allows this computer to provide audio input/output for remote Bluetooth devices. For example, if the remote device is a Bluetooth telephone, this computer’s microphone and speakers can be used as speakerphone input and output for that device.
¾ This computer must have a sound card, microphone, and speakers installed.
¾ The Bluetooth radio on both on this computer and the remote device must support audio.
Network Access
The Bluetooth Network Access service makes it possible for a remote Bluetooth device to use the Local Area Network connection that is physically attached to this computer.
After this computer has been configured to provide the Network Access service to other Bluetooth devices, it will not be able to use the Bluetooth Network Access service provided by another Bluetooth device without being re-configured. Put another way, this computer cannot be both a Bluetooth Network Access server and a Bluetooth Network Access client at the same time.
PIM Item Transfer
The PIM Item Transfer service allows Personal Information Manager items to be transferred between this computer and a remote Bluetooth device.
PIM Synchronization
The PIM Synchronization service can be used by a remote device to synchronize a Personal Information Manager (PIM) database with the PIM database of this computer.
SECURITY
AUTHENTICATION
Authentication is used to verify identity; it requires a passkey or link key from the remote device. When a remote device attempts access, a visual and/or audio warning notifies the local operator. If the
notification is ignored, access is denied after a preset timeout. When devices are “paired,” those devices automatically exchange a Link Key and Authentication is carried out without operator intervention.
AUTHORIZATION
Authorization is Yes-or-No security that requires operator intervention to avoid having the connection time out and fail.
BLUETOOTH DEVICE IDENTITY
Every Bluetooth device has a unique Bluetooth Device Address (BDA) assigned to it during the manufacturing process. This address cannot be changed by the end-user.
ENCRYPTION
Encrypting data translates it into an unreadable format using a secret key or password. Decrypting the data requires the same key or password that was used to encrypt it.
LINK KEY
A unique, internally generated, access code based on a passkey, the Bluetooth Device Address and an internally generated random number.. Link Keys are generated automatically when devices Pair.
After a link key is generated, manual entry of the passkey is not required.
PAIRING DEVICES
Pairing allows you to avoid entering access information each time a connection is attempted. Paired devices share a unique Link Key, which they exchange each time they connect.
PASSKEY
An alphanumeric string up to 16 characters in length. Passkeys are also called Personal Identification Numbers, or PIN codes. A passkey may be required if the Secure Connection option is enabled for a Bluetooth service or application.
SECURE CONNECTION
A passkey or link key is required each time a connection is attempted. All data exchanged over the Bluetooth connection is encrypted. Depending on other configuration options, authorization may also be required.
SECURITY REQUEST DIALOG BOX
A Bluetooth passkey request and/or Bluetooth Authorization request balloon may appear over the Windows system tray when a connection is attempted if Secure Connection is enabled.
MICROSOFT
BLUETOOTH SUPPORT BY MICROSOFT
Updated: Oct. 2004
Microsoft has created native support in the Microsoft® Windows® operating system for Bluetooth wireless technology. This support was developed from the ground up and is not based on existing software from other companies.
Microsoft supports the Bluetooth technology as a wireless bus, complementing USB and IEEE 1394.
The goal for Microsoft software support is for Windows to work with several types of devices that implement Bluetooth wireless technology, such as PC peripherals, PC companions, and devices bridged to network resources through a PC.
Windows XP Support. Microsoft has released Windows XP support for Bluetooth wireless
technology. This support is released through QFE 323183 and may be obtained by system and device manufacturers from Microsoft PSS. Support for Bluetooth wireless technology is available only for Windows XP Service Pack 2 (SP2) or later versions. The HID, HCRP, SPP, DUN and FAX profiles are implemented.
Hardware interfaces with the Windows implementation by following the H:2 (USB) HCI specification for Bluetooth wireless technology. A separate driver from the IHV is not required.
An RFCOMM-based API is available to enable ISVs and IHVs to add functionality to the core support provided by Microsoft.
Windows support for Bluetooth wireless technology is distributed under license agreement with Microsoft.
