Introduction<\/h2>\n\n\n
Bluetooth in RDK, provides short range wireless connectivity between RDK devices and consumer electronics devices. RDK Bluetooth architecture is designed to support any Bluetooth stack.
The Bluetooth stack currently supports common Bluetooth profile such as A2DP, AVRCP, and can be extended to various profiles such as HID, PAN, etc.. Bluetooth may be enabled directly on capable RDK boxes or indirectly via USB-to-Bluetooth adaptor.<\/p>\n\n\n
Features supported in RDK<\/h2>\n\n\n\n\n\nBluetooth feature in RDK<\/th> Feature Descriptions<\/th><\/tr> Audio Encoding<\/td> Detail SBC (sub-band coding) and aptX encoding (Bluetooth chip, in software, or in SoC hardware).<\/td><\/tr> Audio Output Muting<\/td> The Bluetooth audio output may be muted independently of other audio outputs (e.g. HDMI)<\/td><\/tr> Audio Input (Settop as AD2P SNK)<\/td> Using RDK device speakers over bluetooth i.e transmitting audio input back to a speaker connected with RDK device.<\/td><\/tr> Audio Output Routing<\/td> Detail PCM audio routing to Bluetooth A2DP SRC, It uses H\/W accelerations, S\/W processing, RMF involvement on streaming audio\/video contents.<\/td><\/tr> Audio Output Sources<\/td> Bluetooth audio may be different than HDMI audio (e.g. secondary audio program, application sourced audio such as Pandora, voice navigation audio, etc).<\/td><\/tr> Dual Decode<\/td> Supports ability to simultaneously output one audio stream to HDMI and a different audio stream to Bluetooth<\/td><\/tr> Power Control<\/td> In future, the power state of each Bluetooth connected device and the Bluetooth subsystem can be controlled<\/td><\/tr> Audio\/Video Remote Control Profile (AVRCP)<\/td> Controller (Remote Control) sends mute and volume commands to target. AV\/C commands are defined by the 1394 trade association<\/td><\/tr><\/tbody><\/table>\n\n\n<\/div>\n\n\nBluetooth in RDK – Block Diagram<\/h2>\n\n\n
Bluetooth in RDK provides Interface API and implementation to abstract Bluetooth stack and it provides 5 layers in the BTR (Bluetooth-RDK) stack.<\/p>\n
1. Bluetooth daemon (Bluez based)<\/strong> – Interacts with kernel layer bluetooth modules
2. Bt-Ifce<\/strong> (Abstracts Bluez versions and servers as a HAL for other Bluetooth stacks) – Interacts with Bluez over DBus
3. Bluetooth HAL (BTRCore)<\/strong> – Provide API to perform Bluetooth operations by abstracting and simplifying the complexities of Bt-Ifce (& BLuez)
<\/strong>4. BTRMgr<\/strong> – Utilize API’s exposed by BTRCore<\/strong> to perform high level Bluetooth ops like Scan, Pair, Connect and achieve usecases like AudioOut.
Exposes interfaces for external entities to perform BTRMgr related operation using IARM
5. ServiceManager [BluetoothService]<\/strong> – Interacts with BTRMgr based on Application requirements using IARM. Guide applications are interact with Service Manager.<\/p>\n6. RDK Apps\/Diagnostics<\/strong> – HTML-5 based UI applications to make use of Bluetooth service using Service Manager APIs.<\/p>\n<\/p>\n![](\"\/wp-content\/uploads\/sites\/16\/2023\/09\/bluetooth1.drawio.png\")
<\/p>\n\n\n
Bluetooth Architecture<\/h2>\n\n\n
Bluetooth Manager and Bluetooth HAL [BTRCore] is that Bluetooth Manager implements the BT HAL [BTRCore] API. Then BT HAL [BTRCore] integrates and manages the BlueZ stack though the D-BUS interface.<\/p>\n<\/p>\n
![](\"\/wp-content\/uploads\/sites\/16\/2023\/09\/Bluetooth2.drawio.png\")
<\/p>\n<\/p>\n\n\n
BlueZ D-Bus Communication<\/h2>\n\n\n<\/p>\n
![](\"\/wp-content\/uploads\/sites\/16\/2023\/09\/bluetooth4.drawio.png\")
<\/p>\n\n\n
Bluetooth – Service Manager<\/h2>\n\n\n
Bluetooth Service Manager component in RDK exposes Java scripts APIs against each of the Core Bluetooth features supported in the current implementation Javascript API’s have been exposed to invoke IARM communication in the context of a browser which have a Javascript engine when we have HTML\/HTML5\/Browser based applications. Applications which don’t have a Java-script engine should also be able to invoke Service manager methods\/IARM methods to communicate with BTRMgr.<\/p>\n
Provides methods and events to support the following features,<\/p>\n
\n- Device discovery<\/li>\n
- Pairing with the remote device<\/li>\n
- Connecting to the device after authentication.<\/li>\n
- Choose Audio stream to be streamed to other bluetooth device.<\/li>\n
- Provides method to select appropriate audio sink<\/li>\n<\/ul>\n
Contains Methods and Events to communicate with the Bluetooth manager
Service Manager will send event in case external Bluetooth adapter is inserted or removed, or it is requested for pairing.<\/p>\n
List of API & Events<\/h3>\n
| Bluetooth feature in RDK<\/th> | Feature Descriptions<\/th><\/tr> |
|---|---|
| Audio Encoding<\/td> | Detail SBC (sub-band coding) and aptX encoding (Bluetooth chip, in software, or in SoC hardware).<\/td><\/tr> |
| Audio Output Muting<\/td> | The Bluetooth audio output may be muted independently of other audio outputs (e.g. HDMI)<\/td><\/tr> |
| Audio Input (Settop as AD2P SNK)<\/td> | Using RDK device speakers over bluetooth i.e transmitting audio input back to a speaker connected with RDK device.<\/td><\/tr> |
| Audio Output Routing<\/td> | Detail PCM audio routing to Bluetooth A2DP SRC, It uses H\/W accelerations, S\/W processing, RMF involvement on streaming audio\/video contents.<\/td><\/tr> |
| Audio Output Sources<\/td> | Bluetooth audio may be different than HDMI audio (e.g. secondary audio program, application sourced audio such as Pandora, voice navigation audio, etc).<\/td><\/tr> |
| Dual Decode<\/td> | Supports ability to simultaneously output one audio stream to HDMI and a different audio stream to Bluetooth<\/td><\/tr> |
| Power Control<\/td> | In future, the power state of each Bluetooth connected device and the Bluetooth subsystem can be controlled<\/td><\/tr> |
| Audio\/Video Remote Control Profile (AVRCP)<\/td> | Controller (Remote Control) sends mute and volume commands to target. AV\/C commands are defined by the 1394 trade association<\/td><\/tr><\/tbody><\/table>\n\n\n<\/div>\n\n\nBluetooth in RDK – Block Diagram<\/h2>\n\n\nBluetooth in RDK provides Interface API and implementation to abstract Bluetooth stack and it provides 5 layers in the BTR (Bluetooth-RDK) stack.<\/p>\n 1. Bluetooth daemon (Bluez based)<\/strong> – Interacts with kernel layer bluetooth modules 6. RDK Apps\/Diagnostics<\/strong> – HTML-5 based UI applications to make use of Bluetooth service using Service Manager APIs.<\/p>\n<\/p>\n Bluetooth Manager and Bluetooth HAL [BTRCore] is that Bluetooth Manager implements the BT HAL [BTRCore] API. Then BT HAL [BTRCore] integrates and manages the BlueZ stack though the D-BUS interface.<\/p>\n<\/p>\n Bluetooth Service Manager component in RDK exposes Java scripts APIs against each of the Core Bluetooth features supported in the current implementation Javascript API’s have been exposed to invoke IARM communication in the context of a browser which have a Javascript engine when we have HTML\/HTML5\/Browser based applications. Applications which don’t have a Java-script engine should also be able to invoke Service manager methods\/IARM methods to communicate with BTRMgr.<\/p>\n Provides methods and events to support the following features,<\/p>\n Contains Methods and Events to communicate with the Bluetooth manager |
![](\"\/wp-content\/uploads\/sites\/16\/2023\/09\/Bluetooth5.drawio.png\")
<\/p>\n<\/p>\n\n\n