In My Bluetooth Application, Chapter 1, we introduced the conceptual nature of a Bluetooth Profile and how it relates to the Bluetooth protocol stack. This described how each profile facilitated the underlying protocol to ultimately achieve an end-user experience. It also introduced the importance of establishing a common set of parameters and user interface characteristics to ensure interoperability with all manufacturers’ devices.
The Bluetooth Special Interest Group (SIG) openly welcomes all member [1] companies to contribute to the growth of new profiles, adopting new usage models and increasing the Bluetooth application potential. Typical facets to creating a new profile must combine interoperability features, where integration of a common set of parameters and a clear definition of structured procedures provide a holistic user experience.
It is envisaged that the next release from the Bluetooth SIG shall combine new profiles that are being currently architected. In Section 15.3, Profiles and New Protocols Under Development, we provide a list of profiles that are in the process of reaching maturity in development, where they are expected to be in the next release.
Any member company can contribute to the new definition of a profile, which must adhere to the interoperability requirements defined by the Bluetooth SIG. A more formal process will be made available on their web site, [2] where member companies can choose to submit profile suggestions and documentation online. During profile development, revisions of related documentation are incremented to reflect the significant changes in devel opment and the approval from the Bluetooth Architecture Review Board (BARB). As such, Table 15-1 clarifies the time at which membership companies can become privy to the evolution of such documentation.
In the following section, we clarify the formal processes involved in establishing a working group where new specifications and subsequently new profiles can be architected.
Any member (adopter, associates or promoter) of the SIG can submit to the BARB that they wish to create a new working group to undertake the creation of a new profile. Clear objectives and usage models must be identified accompanied with any overlaps of other profiles. It is suggested that the submission should also be supported by a number of companies wishing to adopt the same profile.
The BARB will make a decision based upon the information submitted and, upon successful acceptance, will initially create a study group. It is here that the members involved elect a chair and sufficient interest must be sustained within the group or the BARB will suspend its activities. Within the study group the members must then set out their charter or objectives.
The study group will also undertake an analysis of the market acceptance and the range of usage models that can be expected from it. A profile plan [3] is established outlining the evolution and market analysis. With identifiable project deliverables and project planning a working group can then be formally created with the approval of the BARB to undertake the effort required.
Table 15-1. The evolution of a protocol and profile are mapped directly on phases of release, where working groups are privy to early revisions. Higher revisions of the documents are made available to the member company audience.
|
VERSION |
DESCRIPTION |
|---|---|
|
V0.5 |
A number of internal working group changes are made from its initial draft of v0.1 to the final adopted release of v0.5. Prior to its submission to the adopter and associates, it is passed onto the BARB for approval. All early revisions are released internally within the working group for review. |
|
V0.5 and above |
The new profile or protocol undergoes the natural evolution process and is generally released when there are significant changes made; adopters and associates will have access to these further revisions. |
|
V1.0 |
Further revisions and additions are made to the existing architecture before again meeting with BARB for its approval and subsequent release for incorporation into the Bluetooth Specification. |
This section describes in full all of the profiles and protocols that are still under development; some of which have already been adopted by the SIG. It is expected, as they reach maturity, [4] that they will be incorporated into the Specification of the Bluetooth System.
Table 15-2. The introduction of these new profiles is expected in the new release of the Specification of the Bluetooth System.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Advanced Audio Distribution Profile (A2DP) |
This new addition to the profile suite prescribes how Bluetooth-enabled devices support distribution of high quality audio. It outlines a set of new protocols and procedures that enable advanced audio capabilities for a range of Bluetooth-enabled products. |
|
Audio/Video Remote Control Profile (AVRCP) |
This profile defines a new set of protocols and user features for the adoption of remote control functionality within Bluetooth-enabled devices. It also outlines, as with any other profile, how such devices should interoperate. |
|
Generic Audio/Video Distribution Profile (GAVDP) |
The GAVDP forms a small part of the comprehensive introduction of the range of audio/video-related services. This profile specifically addresses the necessary requirements to achieve streaming channels for audio and video distribution. |
|
Video Conferencing Profile (VCP) |
In this last set of audio/video-related profiles, the video conferencing profiles provides a set of protocols and procedures that are required to enable the support of this feature. |
Table 15-3. The set of new Audio/Video-related protocols.
|
PROTOCOL |
DESCRIPTION |
|---|---|
|
Audio/Video Control Transport Protocol (or AVCTP) |
To achieve the functionally prescribed in the audio/video-related profiles, this protocol is specifically used to address the transportation of command and response messages in compliant Bluetooth-enabled devices. |
|
Audio/Video Distribution Transport Protocol (or AVDTP) |
This protocol further defines procedures for the establishment, initial negotiation and transmission methods for audio/video-enabled devices. |
Table 15-4. The Basic Printing, Imaging and Hardcopy Cable Replacement Profiles.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Basic Printing Profile (BPP) |
This profile establishes the fundamental requirements to enable basic printing, outlining a common set of protocols and procedures. It is primarily aimed, although not limited, to mobile devices, such as mobile phones and PDAs, where more larger and static devices may use the Hardcopy Cable Replacement Profile. We discuss this profile in The Basic Printing and Basic Imaging Profiles: An Overview, Chapter 19. |
|
Basic Imaging Profile (BIP) |
This profile outlines the requirements necessary to enable the imaging usage model. It manages a series of procedures which, in turn, negotiate the size and encoding of the image-related data to be exchanged. We discuss this profile in The Basic Printing and Basic Imaging Profiles: An Overview, Chapter 19. |
|
Hardcopy Cable Replacement Profile (HCRP) |
This profile prescribes the capabilities of Bluetooth-enabled devices that support the HCRP. Specific usage models can be extended to printing and scanning of documents. The printing of images would be managed by the capabilities offered to us by the Basic Imaging Profile. |
Table 15-5. The set of car profiles.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Car Hands-Free Profile (HFP) |
A set of protocols and procedures outline the capabilities that are offered to us though the HFP. It outlines the ability to operate a hands-free phone device within a vehicle environment that has a hands-free unit, where connection establishment is achieved through Bluetooth wireless means. We discuss this profile in The Car Profiles: An Overview, Chapter 17. |
|
Car Phone Access Profile (PAP) |
In this suite of car-specific capability, the PAP provides a set of protocols and procedures that allow the remote operation of a phone using an in-car device, which may include a cordless handset, hands-free units and car-embedded mobile phones. We discuss this profile in The Car Profiles: An Overview, Chapter 17. |
|
Car SIM Access Profile (SAP) |
This final suite of profiles provides the diversity required to enable users to make use of SIM-specific information which, in turn, allows the user to make use of the in-car embedded phone. We discuss this profile in The Car Profiles: An Overview, Chapter 17. |
Table 15-6. The set of Extended Service Discovery Profiles.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Extended Service Discovery Profiles for Universal Plug and Play (ESDP for UPnP) |
This profile is considered to be an enhancement to the existing Service Discovery Protocol. It describes how support should be provided in Bluetooth-enabled devices that use UPnP. This support manifests itself through the SDP and embodies other protocols such as L2CAP and IP. We discuss this profile in ESDP: An Overview, Chapter 18. |
|
Extended Service Discovery Profiles Device Identification (ESDP DI) |
This profile is also an enhancement to the existing SDP. It describes how device identification is provided in the service record, where characteristics such as manufacture and model description are further used to ensure that a user is making use of the best available service. This document describes how this is achieved. |
Table 15-7. The Personal Area Networking Profile.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Personal Area Networking Profile (PAN) |
This new profile is considered to be an extension of the existing functionality already offered to us by the foundation profiles. It defines three new scenarios to encompass Group Ad-hoc Networking and Network Access Point. A PAN User is described as a device that accesses these services. In general, it offers a more comprehensive IP solution and is introduced in The PAN Profile: An Overview, Chapter 16. |
Table 15-8. The Bluetooth Network Encapsulation Protocol.
|
PROTOCOL |
DESCRIPTION |
|---|---|
|
Bluetooth Network Encapsulation Protocol (BNEP) |
The PAN Profile requires the implementation of the BNEP to facilitate the use of unmodified Ethernet payloads transported over the L2CAP. This feature enables the incorporation of a large number of networking-related technologies. |
Table 15-9. The Radio working groups undertaking improvements and increased bandwidth capability.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Radio 1.x |
This working group is undertaking enhancements to the existing functionality already offered to us in the Bluetooth Specification v1.1. The improvements that are addressed in the short term are radio and baseband-specific as well as increased bandwidth (2 Mb/s) in combination with errata raised against v1.1. It is, of course, expected that any future functionality would be backward compatible. |
|
Radio 2 |
The Radio 2 working group is concentrating efforts to allow Bluetooth wireless communications to provide greater bandwidth capability (11 Mb/s), whilst ensuring backward capability of v1.1 compliant devices. Increased adoption and the embodiment of other wireless and static technologies are enabled. It is also suggested that the release of this specification and subsequent adoption by the BARB will form the much speculated and hyped Bluetooth v2.0. |
Table 15-10. The services offered by the HID, ISDN Access and Local Positioning Profiles.
|
PROFILE |
DESCRIPTION |
|---|---|
|
Human Interface Device Profile (HID) |
The HID Profile describes how Bluetooth-enabled devices can make use of HID capabilities and then communicate and support them. Such examples of Bluetooth HID devices include keyboards, mice and gaming devices. |
|
Common ISDN Access Profile |
This profile describes how ISDN can be used over Bluetooth-enabled devices. More specifically, it outlines how existing ISDN applications can make use of the Bluetooth transport. |
|
Local Positioning Profile (LP) |
In the last collection of profiles that have been introduced in this chapter, the LP Profile defines a set of protocols and procedures that allow position-related information to be communicated over Bluetooth-enabled devices. Support is provided for position determination, location awareness and time transfer. |
|
Co-existence Profile |
With the increase of wireless communications operating within the 2.4 GHz band, it is becoming increasingly important to help identify how these wireless products can co-exist. This profile outlines a set of procedures and protocols to overcome and help such devices cooperate in all environments. |
|
Unrestricted Digital Information (UDI) |
With the global vision of Bluetooth communication, the adoption of this technology in various countries has an effect on bandwidth requirements. One such country is Japan, where the use of mobile phones differs from those of their American and European counterparts. This profile outlines how Bluetooth-enabled devices can be used with 3rd Generation (3G) mobile handsets, where the initial application being considered is the use of video. |
[1] Member companies refer to companies that have signed and agreed to the terms and conditions as prescribed by the Bluetooth SIG. As such, each member company is free to develop Bluetooth specific technologies. The type of membership, whether adopter or associate, entitles you to various evolutionary phases of the documentation being drafted.
[2] The Bluetooth member company web site access is obtained through http://www.bluetooth.org.
[3] A profile plan is typically a Bluetooth Marketing Requirement Document (MRD).
[4] A profile is ready for incorporation as part of the specification when it has reached v1.0. Thus, it has been reviewed by member companies and they have agreed to adopt it.