| System Functions | Functions in this module provide interface to DotStack functionality that is common to all protocols and profiles |
| HCI | The Host Controller Interface (HCI) provides a uniform interface method of accessing a Bluetooth Controller's capabilities |
| L2CAP | The Bluetooth logical link control and adaptation protocol (L2CAP) supports higher level protocol multiplexing, packet segmentation and reassembly, and the conveying of quality of service information |
| GAP | The GAP profile defines the generic procedures related to discovery of Bluetooth devices and link management aspects of connecting to Bluetooth devices |
| ▼Serial Port Profile (SPP) | The DotStack SPP API is a simple API for communicating over a Bluetooth link using the Bluetooth Serial Port Profile |
| SPP Configuration | This module describes parameters used to configure SPP layer |
| RFCOMM Configuration | This module describes parameters used to configure RFCOMM layer |
| ▼SDP | This module describe functions and data structures used to start the SDP server and perform SDP queries |
| Configuration | This module describes parameters used to configure SDP |
| HID Profile (HIDP) | |
| Hands Free Profile (HFP) | |
| ▼Audio/Video Distribution Protocol (AVDP) | AVDTP is the transport protocol for audio and/or video distribution connections and streaming of audio or video media over the Bluetooth air interface |
| Configuration | This module describes parameters used to configure AVDTP layer |
| Advanced Audio Distribution Profile (A2DP) | The Advanced Audio Distribution Profile (A2DP) defines the protocols and procedures that realize distribution of audio content of high-quality in mono or stereo on ACL channels |
| ▼Audio/Video Control Transport Protocol (AVCTP) | AVCTP is the transport mechanisms used to exchange messages for controlling Audio and/or Video devices |
| Configuration | This module describes parameters used to configure AVCTP layer |
| ▼Audio/Video Remote Control Profile (AVRCP) | The Audio/Video Remote Control Profile (AVRCP) defines the features and procedures required in order to ensure interoperability between Bluetooth devices with audio/video control functions in the Audio/Video distribution scenarios |
| Configuration | This module describes parameters used to configure AVRCP layer |
| ▼ATT | The attribute protocol allows a device referred to as the server to expose a set of attributes and their associated values to a peer device referred to as the client |
| ▼ATT Server | This module describes functions and data structures used to implement an ATT server (peripheral) |
| Configuration | This module describes parameters used to configure ATT server layer |
| ▼ATT Client | This module describes functions and data structures used to implement an ATT client (central) |
| Configuration | This module describes parameters used to configure ATT client layer |
| ▼GATT | The GATT profile is designed to be used by an application or another profile, so that a client can communicate with a server |
| GATT Server | This module describes functions and data structures used to implement a GATT server (peripheral) |
| ▼GATT Client | This module describes functions and data structures used to implement a GATT client (central) |
| Configuration | This module describes parameters used to configure GATT client |
| Security Manager | This module describes functions and data structures used to implement Security Manager |
| ▼OEM - HCI Communication Interface | |
| HCI UART (H4) transport protocol | |
| OEM - Timer Interface | |
| OEM - Non-volatile Storage Interface | |
| OEM - Logging Interface | |
| OPP | The Object Push profile defines the requirements for the protocols and procedures that shall be used by the applications providing the Object Push usage model |
| ▼FTP | The File Transfer profile defines the requirements for the protocols and procedures that shall be used by the applications providing the File Transfer usage model |
| FTP Configuration | This module describes parameters used to configure FTP layer |
| MAP | The Message Access Profile (MAP) defines the features and procedures that shall be used by devices that exchange message objects |
| OBEX | The OBEX object model describes how OBEX objects are presented |
| OBEX2 | The OBEX object model describes how OBEX objects are presented |
| PBAP | The Phone Book Access Profile (PBAP) defines the protocols and procedures that shall be used by devices for the retrieval of phone book objects |
| ▼Vendor specific extensions to HCI | |
| CSR | |