Bluetooth Tutorial - Profiles
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.
Note: A number of
additional Bluetooth profiles are currently in the final stages of
development. To stay up to date check this page regularly or see our Bluetooth
Bluetooth Profile Dependencies:
Click on a section of the diagram* above, for a
tutorial of its functions
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.
* Diagram Source: palowireless.com, All