Radio Baseband LMP HCI L2CAP RFCOMM SDP Profiles

 Bluetooth Profiles

 

Bluetooth Profile Structure:

profile_stack.gif (29646 bytes)

Click on a section of the diagram* above, for a tutorial of its functions

    The profiles have been developed in order to describe how implementations of user models are to be accomplished. The user models describe a number of user scenarios where Bluetooth performs the radio transmission. A profile can be described as a vertical slice through the protocol stack. It defines options in each protocol that are mandatory for the profile. It also defines parameter ranges for each protocol. The profile concept is used to decrease the risk of interoperability problems between different manufacturers' products.

    The Bluetooth profile structure and the dependencies of the profiles are depicted above. A profile is dependent upon another profile if it re-uses parts of that profile, by implicitly or explicitly referencing it. Dependency is illustrated in the figure: a profile has dependencies on the profile(s) in which it is contained – directly and indirectly. For example, the Object Push profile is dependent on Generic Object Exchange, Serial Port, and Generic Access profiles.

    Click on a section below for detailed information.

Profiles Table Of Contents

 

K1

GAP Profile
The Generic Access Profile defines the generic procedures related to discovery of Bluetooth devices and link management aspects of connecting to Bluetooth devices. It is the core on which all other Profiles are based

K2

SDAP Profile

The Service Discovery Application Profile defines the features and procedures for an application in a Bluetooth device to discover services registered in other Bluetooth devices and retrieve any desired available information pertinent to these services.

K3

CTP Profile

The Cordless Telephony Profile defines the features and procedures that are required for interoperability between different units active in the 3-in-1 phone use case. This profile also shows how the use case can be applied generally for wireless telephony in a residential or small office environment,

K4

IP Profile

The Intercom Profile defines the requirements for Bluetooth devices necessary for the support of the intercom functionality within the 3-in-1 phone use case. This is also refereed to as the 'walkie-talkie' usage of Bluetooth

K5

SPP Profile

The Serial Port Profile defines the requirements for Bluetooth devices necessary for setting up emulated serial cable connections using RFCOMM between two peer devices.

K6

HS Profile

The Headset Profile defines the requirements that shall be used by devices implementing the usage model called ‘Ultimate Headset’.  

K7

DNP Profile

The Dial-up Networking Profile defines the requirements that shall be used by devices (modems, cellular phones) implementing the usage model called ‘Internet Bridge'.

K8

FP Profile

The Fax Profile defines the requirements for Bluetooth devices necessary to support the Fax use case. This allows a Bluetooth cellular phone (or modem) to be used by a computer as a wireless fax modem to send/receive a fax message.

K9

LAP Profile

The LAN Access Profile defines how Bluetooth enabled devices can access the services of a LAN using PPP. Also, this profile shows how the same PPP mechanisms are used to form a network consisting of two Bluetooth-enabled devices.

K10

GOEP Profile

The Generic Object Exchange Profile lays the basis (defines the protocols and procedures) for Bluetooth devices necessary for the support of the object exchange usage models. The usage model can be the Synchronization , File Transfer, or Object Push model.

K11

OPP Profile

The Object Push Profile defines the requirements for applications providing the object push usage model.Typical scenarios covered by this profile involve the pushing/pulling of data objects between Bluetooth devices

K12

FTP Profile

The File Transfer Profile defines the requirements for applications providing the file transfer usage model.Typical scenarios involve a Bluetooth device browsing, transferring and manipulating objects on/with another Bluetooth device.  

K13

SP Profile

The Synchronization Profile defines the requirements for applications providing the synchronization usage model.Typical scenarios covered by this profile involving manual or automatic synchronization of PIM data when 2 Bluetooth devices come within range.