Content deleted Content added
No edit summary |
Introiboad (talk | contribs) No edit summary |
||
Line 31:
In Bluetooth devices with simple functionality (e.g., headsets), the host stack and controller can be implemented on the same microprocessor. In this case the HCI is optional, although often implemented as an internal software interface.
=== Low Energy Link Layer (LE LL) ===
This is the LMP equivalent for Bluetooth Low Energy (LE). It is implemented on the controller and manages advertisement, scanning, connection and security from a low-level, close to the hardware point of view.
== Host Stack ==
Line 84 ⟶ 87:
Used by the remote control profile to transfer [[AV/C]] commands over an L2CAP channel. The music control buttons on a stereo headset use this protocol to control the music player
In the protocol stack, AVCTP is bound to L2CAP.
=== Audio/visual data transport protocol (AVDTP) ===
Used by the advanced audio distribution profile to stream music to stereo headsets over an L2CAP channel. Intended to be used by video distribution profile.
In the protocol stack, AVDTP is bound to L2CAP.
=== Object exchange (OBEX) ===
Line 98 ⟶ 101:
In the protocol stack, OBEX is bound to RFComm.
=== Low Energy Attribute Protocol (ATT) ===
Similar in scope to SDP but specially adapted and simplified for Low Energy Bluetooth. It allows a client to read and/or write certain attributes exposed by the server in a non-complex, low-power friendly manner.
In the protocol stack, ATT is bound to L2CAP.
=== Low Energy Security Manager Protocol (SMP) ===
Used by Bluetooth Low Energy implementations for pairing and transport specific key distribution.
In the protocol stack, ATT is bound to L2CAP.
== See also ==
| |||