Bluetooth profile

From Wikipedia, the free encyclopedia

To comply with Wikipedia's lead section guidelines, the introduction of this article may need to be rewritten. Please discuss this issue on the talk page and read the layout guide to make sure the section will be inclusive of all essential details. This article has been tagged since February 2007.

A Bluetooth profile is a wireless interface specification for Bluetooth-based communication between devices. In order to use Bluetooth technology, a device must be compatible with the subset of Bluetooth profiles necessary to use the desired services. A Bluetooth profile resides on top of the Bluetooth Core Specification and (optionally) additional protocols. While the profile may use certain features of the core specification, specific versions of profiles are rarely tied to specific versions of the core specification. For example, there are HFP 1.5 implementations using both Bluetooth 2.0 and Bluetooth 1.2 core specifications.

The way a device uses Bluetooth technology depends on its profile capabilities. The profiles provide standards which manufacturers follow to allow devices to use Bluetooth in the intended manner.

At a minimum, each profile specification contains information on the following topics:

• Dependencies on other profiles
• Suggested user interface formats
• Specific parts of the Bluetooth protocol stack used by the profile. To perform its task, each profile uses particular options and parameters at each layer of the stack. This may include an outline of the required service record, if appropriate.
  

This article summarizes the current definitions and possible applications of each profile.

Contents 1 List of profiles 1.1 Advanced Audio Distribution Profile (A2DP) 1.1.1 Operating systems 1.2 Audio/Video Remote Control Profile (AVRCP) 1.3 Basic Imaging Profile (BIP) 1.4 Basic Printing Profile (BPP) 1.5 Common ISDN Access Profile (CIP) 1.6 Cordless Telephony Profile (CTP) 1.7 Device ID Profile (DID) 1.8 Dial-up Networking Profile (DUN) 1.9 Fax Profile (FAX) 1.10 File Transfer Profile (FTP) 1.11 General Audio/Video Distribution Profile (GAVDP) 1.12 Generic Access Profile (GAP) 1.13 Generic Object Exchange Profile (GOEP) 1.14 Hard Copy Cable Replacement Profile (HCRP) 1.15 Hands-Free Profile (HFP) 1.16 Human Interface Device Profile (HID) 1.17 Headset Profile (HSP) 1.18 Intercom Profile (ICP) 1.19 LAN Access Profile (LAP) 1.20 Object Push Profile (OPP) 1.21 Personal Area Networking Profile (PAN) 1.22 Phone Book Access Profile (PBAP) 1.23 Serial Port Profile (SPP) 1.24 Service Discovery Application Profile (SDAP) 1.25 SIM Access Profile (SAP, SIM) 1.26 Synchronisation Profile (SYNCH) 1.27 Video Distribution Profile (VDP) 1.28 Wireless Application Protocol Bearer (WAPB) 2 Comments 3 See also 4 References

[edit] List of profiles

The following profiles are defined and adopted by the Bluetooth SIG:

[edit] Advanced Audio Distribution Profile (A2DP)

This profile defines how high quality audio (stereo or mono) can be streamed from one device to another over a Bluetooth connection.^[1] For example, music streamed from a mobile phone to a wireless headset.

A2DP was initially used in conjunction with an intermediate Bluetooth transceiver that connects to a standard output audio jack, encodes the incoming audio to a Bluetooth-friendly format, and sends the signal wirelessly to Bluetooth headphones that decode and play the audio. However, many Bluetooth 1.1, 1.2 mobile phones and portable media players do not natively support A2DP, while some newer Bluetooth 2.0 headphones do support it.

Bluetooth headphones, especially the more advanced models, often come with a microphone and support for the Headset (HSP), Hands-Free (HFP) and Audio/Video Remote Control (AVRCP) profiles.

A2DP is designed to transfer a uni-directional 2-channel stereo audio stream, like music from an MP3 player, to a headset or car radio.^[2] This profile relies on AVDTP and GAVDP. It includes mandatory support for the low complexity SBC codec and supports optionally: MPEG-1, MPEG-2, MPEG-4, AAC, and ATRAC, and is extensible to support manufacturer-defined codecs. Most bluetooth stacks implement the SCMS-T digital rights management (DRM) scheme. In these cases it is not possible to connect the A2DP headphones for high quality audio.

[edit] Operating systems

• Linux: Initial A2DP support was added to BlueZ in version 3.15. The instructions to set up A2DP can be found in BlueZ Wiki.
• Mac OS X: As of version 10.5, Mac OS X includes native support for A2DP on Bluetooth-equipped Macs.^[3] Version 10.4 does not support A2DP, but can be hacked to enable limited functionality.^[4] A2DP support for Mac OS X is also presented by Softick with Softick Audio Gateway for Mac OS X. The iPhone variant of OS X provides no A2DP support.
• Palm OS: A2DP support was introduced in 2006 by Softick with their Softick Audio Gateway shareware program.
• Symbian Series60: Devices running Series60 3rd Edition FP1 (S60v3.1/Symbian 9.1) and newer support A2DP ^[5]
• Motorola P2K: Motorola L9 running on P2K supports A2DP Profile.
• UIQ: UIQ 3.0 (Symbian 9.1) and newer support A2DP.^[5]
• Windows Mobile (previously Pocket PC): Version 5.0 and newer (with AKU 2.0), thus far based on the Windows CE 5.0 kernel, fully support A2DP if an appropriate device is present.
• Windows XP: Does not natively support A2DP, but newer Bluetooth USB dongles and built-in adapters include drivers with A2DP support.^[6]
• Windows Vista: Supports A2DP after installing an April 2007 update to the Bluetooth stack, which enables A2DP for supported dongles.^[7] No update has been made available through Microsoft as of Feb 13,2008 though a Widcomm update may be available to some.
• BlackBerry: Supports A2DP in Operating System 4.2.

[edit] Audio/Video Remote Control Profile (AVRCP)

This profile is designed to provide a standard interface to control TVs, Hi-fi equipment, etc. to allow a single remote control (or other device) to control all of the A/V equipment to which a user has access. It may be used in concert with A2DP or VDP.

It has the possibility for vendor-dependent extensions. Additionally, with the version 1.3 release of the specification, there is now capability to transmit information on the status of the music source, including information on the track itself (artist, track name, etc).

[edit] Basic Imaging Profile (BIP)

This profile is designed for sending images between devices and includes the ability to resize, and convert images to make them suitable for the receiving device. It may be broken down into smaller pieces:

Image Push 

Allows the sending of images from a device the user controls.

Image Pull 

Allows the browsing and retrieval of images from a remote device.

Advanced Image Printing 

print images with advanced options using the DPOF format developed by Canon, Kodak, Fujifilm, and Matsushita

Automatic Archive 

Allows the automatic backup of all the new images from a target device. For example, a laptop could download all of the new pictures from a camera whenever it is within range.

Remote Camera 

Allows the initiator to remotely use a digital camera. For example, a user could place a camera on a tripod for a group photo, use their phone handset to check that everyone is in frame, and activate the shutter with the user in the photo.

Remote Display 

Allows the initiator to push images to be displayed on another device. For example, a user could give a presentation by sending the slides to a video projector.

[edit] Basic Printing Profile (BPP)

This allows devices to send text, e-mails, vCards, or other items to printers based on print jobs. It differs from HCRP in that it needs no printer-specific drivers. This makes it more suitable for embedded devices such as mobile phones and digital cameras which cannot easily be updated with drivers dependent upon printer vendors.

[edit] Common ISDN Access Profile (CIP)

This provides unrestricted access to the services, data and signalling that ISDN offers.

[edit] Cordless Telephony Profile (CTP)

This is designed for cordless phones to work using Bluetooth. It is hoped that mobile phones could use a Bluetooth CTP gateway connected to a landline when within the home, and the mobile phone network when out of range. It is central to the Bluetooth SIG's '3-in-1 phone' use case.

[edit] Device ID Profile (DID)

This profile allows a device to be identified above and beyond the limitations of the Device Class already available in Bluetooth. It enables identification of the manufacturer, product id, product version, and the version of the Device ID specification version being met. It is useful in allowing a PC to identify a connecting device and download appropriate drivers. It enables similar applications to those the Plug-and-play specification allows.

[edit] Dial-up Networking Profile (DUN)

This profile provides a standard to access the Internet and other dial-up services over Bluetooth. The most common scenario is accessing the Internet from a laptop by dialing up on a mobile phone, wirelessly. It is based on Serial Port Profile (SPP), and provides for relatively easy conversion of existing products, through the many features that it has in common with the existing wired serial protocols for the same task. These include the AT command set specified in European Telecommunications Standards Institute (ETSI) 07.07, and Point-to-Point Protocol (PPP).

[edit] Fax Profile (FAX)

This profile is intended to provide a well defined interface between a mobile phone or fixed-line phone and a PC with Fax software installed. Support must be provided for ITU T.31 and / or ITU T.32 AT command sets as defined by ITU-T. Data and voice calls are not covered by this profile.

[edit] File Transfer Profile (FTP)

Provides access to the file system on another device. This includes support for getting folder listings, changing to different folders, getting files, putting files and deleting files. It uses OBEX as a transport and is based on GOEP.

[edit] General Audio/Video Distribution Profile (GAVDP)

Provides the basis for A2DP, and VDP.

[edit] Generic Access Profile (GAP)

Provides the basis for all other profiles.

[edit] Generic Object Exchange Profile (GOEP)

Provides a basis for other data profiles. Based on OBEX.

[edit] Hard Copy Cable Replacement Profile (HCRP)

This provides a simple wireless alternative to a cable connection between a device and a printer. Unfortunately it does not set a standard regarding the actual communications to the printer, so drivers are required specific to the printer model or range. This makes this profile less useful for embedded devices such as digital cameras and palmtops, as updating drivers can be problematic.

[edit] Hands-Free Profile (HFP)

This is commonly used to allow car hands-free kits to communicate with mobile phones in the car. It uses SCO (see Synchronous Connection Oriented link) to carry a mono, Continuously variable slope delta modulation or Pulse-code modulation with logarithmic a-law or μ-law quantization audio channel. Currently in version 1.5. In 2002 Audi, with the Audi A8, was the first motor vehicle manufacturer to install Bluetooth technology in a car, enabling the passenger to use a wireless in-car phone. The following year DaimlerChrysler and Acura introduced Bluetooth technology integration with the audio system as a standard feature in the third generation Acura TL in a system dubbed HandsFree Link (HFL). Later, BMW added it as an option on its 1 Series, 3 Series, 5 Series, 7 Series and X5 vehicles. Since then, other manufacturers have followed suit, with many vehicles, including the Toyota Prius (Since 2004), 2007 Toyota Camry, 2007 Infiniti G35, and the Lexus LS 430 (Since 2004). The Bluetooth car kits allow users with Bluetooth-equipped cell phones to make use of some of the phone's features, such as making calls, while the phone itself can be left in a suitcase or in the boot/trunk, for instance. Companies like Nokia, Johnson Controls, RAYTEL, Parrot and Motorola manufacture Bluetooth hands-free car kits for well-known brand car manufacturers.

[edit] Human Interface Device Profile (HID)

Provides support for devices such as mice, joysticks, keyboards, as well as sometimes providing support for simple buttons and indicators on other types of devices. It is designed to provide a low latency link, with low power requirements.

Bluetooth HID is a lightweight wrapper of the Human Interface Device protocol defined for USB. The use of the HID protocol simplifies host implementation (ex: support by Operating Systems) by enabling the re-use of some of the existing support for USB HID to also support Bluetooth HID.

Popular devices that feature support for this profile include: Logitech diNovo Media Desktop 2.0, Microsoft Optical Desktop Elite for Bluetooth. PlayStation 3 controllers and Wii Remotes also use BT HID.

[edit] Headset Profile (HSP)

This is the most commonly used profile, providing support for the popular Bluetooth Headsets to be used with mobile phones. It relies on SCO for audio encoded in 64 kbit/s CVSD or PCM and a subset of AT commands from GSM 07.07 for minimal controls including the ability to ring, answer a call, hang up and adjust the volume.

[edit] Intercom Profile (ICP)

This is often referred to as the walkie-talkie profile. It is another TCS (Telephone Control protocol Specification)^[8] based profile, relying on SCO to carry the audio. It is proposed to allow voice calls between two Bluetooth capable handsets, over Bluetooth.

[edit] LAN Access Profile (LAP)

LAN Access profile makes it possible for a Bluetooth device to access LAN, WAN or Internet via another device that has a physical connection to the network. It uses PPP over RFCOMM to establish connections. LAP also allows the device to join an ad-hoc Bluetooth network.

The LAN Access Profile has been replaced by PAN profile in the Bluetooth specification.

[edit] Object Push Profile (OPP)

A basic profile for sending "objects" such as pictures, virtual business cards, or appointment details. It is called push because the transfers are always instigated by the sender (client), not the receiver (server).

OPP uses the APIs of OBEX profile and the OBEX operations which are used in OPP are connect, disconnect, put, get and abort. By using these APIs the OPP layer will reside over OBEX and hence following the specifications of Bluetooth stack.

[edit] Personal Area Networking Profile (PAN)

This profile is intended to allow the use of Bluetooth Network Encapsulation Protocol on Layer 3 protocols for transport over a Bluetooth link.

[edit] Phone Book Access Profile (PBAP)

This profile allows exchange of Phone Book Objects between devices. It is likely to be used between a car kit and a mobile phone to allow the car kit to display the name of the incoming caller.

[edit] Serial Port Profile (SPP)

This profile is based on the ETSI TS 07.10 specification and uses the RFCOMM protocol. It emulates a serial cable to provide a simply implemented wireless replacement for existing RS-232 based serial communications applications, including familiar control signals. It provides the basis for DUN, FAX, HSP and AVRCP profiles.

[edit] Service Discovery Application Profile (SDAP)

SDAP describes how an application should use SDP to discover services on a remote device. SDAP requires that any application be able to find out what services are available on any Bluetooth enabled device it connects to.

[edit] SIM Access Profile (SAP, SIM)

This allows devices such as car phones with built in GSM transceivers to connect to a SIM card in a phone with Bluetooth, so the car phone itself doesn't require a separate SIM card.

[edit] Synchronisation Profile (SYNCH)

This profile allows synchronisation of Personal Information Manager (PIM) items. As this profile originated as part of the infrared specifications but has been adopted by the Bluetooth SIG to form part of the main Bluetooth specification, it is also commonly referred to as IrMC Synchronization.

[edit] Video Distribution Profile (VDP)

This profile allows the transport of a video stream. It could be used for streaming a recorded video from a PC media center to a portable player, or from a digital video camera to a TV. Support for H.263 baseline is mandatory. Support for MPEG-4 Visual Simple Profile, H.263 profiles 3 and 8 are optionally supported, and covered in the specification.

[edit] Wireless Application Protocol Bearer (WAPB)

This is a profile for carrying Wireless Application Protocol, (WAP) over Point-to-Point Protocol over Bluetooth.

[edit] Comments

These profiles are still not finalised, but are currently proposed within the Bluetooth SIG:

• Unrestricted Digital Information (UDI)
• Extended Service discovery profile (ESDP)
• Video Conferencing Profile (VCP) : This profile is to be compatible with 3G-324M, and support videoconferencing over a 3G high-speed connection.
• Message Access Profile (MAP)

Compatibility of products with profiles can be verified on the Bluetooth Qualification Program website.

[edit] See also

• Bluetooth
• Bluetooth protocols

[edit] References