Bluetooth profile

From Wikipedia, the free encyclopedia

You have new messages (last change).
This article or section does not adequately cite its references or sources.
Please help improve this article by adding citations to reliable sources. (help, get involved!)
Any unsourced material that has been or is likely to be challenged may be removed at any time.
This article has been tagged since September 2006.
The introduction of this article is vague or missing. To comply with Wikipedia's lead section guidelines, it should be improved.
Please discuss this issue on the talk page and read the lead section guide to make sure the introduction summarizes the article. This article has been tagged since February 2007.

A Bluetooth profile is a standardized interface between Bluetooth devices. In order to use Bluetooth, a device must be compatible with certain Bluetooth profiles. These define the possible applications.

Bluetooth profiles are general behaviors through which Bluetooth enabled devices communicate with other devices. Bluetooth technology defines a wide range of profiles that describe many different types of use cases. By following a guidance provided in Bluetooth specifications, developers can create applications to work with other devices also conforming to the Bluetooth specification.

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.

Contents

[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, and 2.0 mobile phones and portable media players natively support A2DP, and most newer Bluetooth 2.0 headphones support it as well.[2] Bluetooth headphones, especially the more advanced models, often come with a microphone and support for the Audio/Video Remote Control (AVRCP), Headset (HSP) and Handsfree (HFP) profiles.

A2DP[3] is designed to transfer a 2-channel stereo audio stream, like music from an MP3 player, to a headset or car radio. This profile relies on AVDTP and GAVDP. It includes mandatory support for low complexity Sub Band Codec (SBC) and supports optionally: MPEG-1,2 Audio, MPEG-2,4 AAC and ATRAC, and is extensible to support manufacturer-defined codecs. Most bluetooth stacks implement the SCMS-T copyright protection. In these cases it is not possible to connect the A2DP headphones for high quality audio. E.g. the Motorola HT820 can be used for high quality audio only with certain versions of the Toshiba bluetooth stack.

[edit] Operating Systems

  • Linux desktop distribution is still sketchy. There exists open source code Bluetooth-alsa Project that integrates with ALSA (Linux) to provide any media player that makes use of ALSA to transmit audio over A2DP.
  • Mac OS X v10.4, the current version of Apple's Mac OS X operating system, does not include support for A2DP; however, the developer preview release of Apple's forthcoming Mac OS X v10.5 does[4]
  • Palm OS A2DP support has been introduced in 2006 by Softick in Softick Audio Gateway shareware program.
  • Windows Mobile - used to be called Pocket PC - from version 5, based on Windows CE 5.0 kernel, fully supports A2DP if appropriate device is present (ie embedded in the PDA, phone etc).
  • Windows XP does not support A2DP out of the box, but newer Bluetooth USB dongles and built-in adapters include drivers with A2DP support. [2].
  • Windows Vista does not support A2DP out of the box[5], but does look for drivers for it, enabling hardware makers or third parties to provide drivers for A2DP without reworking the entire Bluetooth stack. Broadcomm's version 6 bluetooth driver provides such A2DP extension for Windows Vista, for all Broadcomm bluetooth hardware.

[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. The Generic Media Control Profile (GMCP) is proposed to be an open standard for transfer of media-content-related information using those extensions.

[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 Device Class according to the Specification version met, the Manufacturer, product and product version. This could be 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 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 ETSI 07.07, and 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, PCM 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 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 Parrot or 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, etc. It is designed to provide a low latency link, with low power requirements. Popular devices that feature support for this profile include: Logitech diNovo Media Desktop 2.0, Microsoft Optical Desktop Elite. 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 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) based profile, relying on SCO to carry the audio. It is proposed to allow voice calls between two Bluetooth capable handsets, over Bluetooth.

[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 TS07.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)

This mandatory profile is used to find out which profiles are offered by the Server device.

[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. And more info. click on SAG.

[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

[edit] References

  1. ^ Bluetooth SIG. Bluetooth.com Profiles Overview. bluetooth.com. Retrieved on September 27, 2006.
  2. ^ a b Robert Webbe. Advanced Audio Distribution Profile. robertwebbe.nl. Retrieved on November 8, 2006.
  3. ^ Bluetooth Tutorial - Profiles. palowireless Pty Ltd. Retrieved on January 5, 2007.
  4. ^ Mactasticsite. A2DP Finally in Leopard. mactasticsite.blogspot.com. Retrieved on September 19, 2006.
  5. ^ Vatsal Bhardwaj. On Windows Vista Bluetooth Advances In Windows Vista And Beyond. Microsoft. Retrieved on December 24, 2006.
Retrieved from "http://en.wikipedia.org../../../b/l/u/Bluetooth_profile.html"