The platform supports connections to external devices over Bluetooth—it can initiate a Bluetooth connection or accept a connection request.
Supported Bluetooth profiles include:
- HFP (Hands-Free Profile)
- MAP (Message Access Profile)
- PBAP (Phone Book Access Profile)
- SPP (Serial Port Profile)
- A2DP/AVRCP (Audio Profiles)
The QNX CAR platform uses the Cybercom blueGO application software framework, which is a wrapper around Sybase iAnywhere's Bluetooth protocol stack and profiles. While the profiles listed above are preintegrated and tested for this release, the Bluetooth stack supports many other profiles that can also be integrated.
The front-end resource manager for Bluetooth is io-bluetooth, which offers a POSIX-compliant API and provides:
- low-level access to the Bluetooth radio chip (typically via a serial interface such as UART, USB, or I2S)
- support for Bluetooth profiles
- profile concurrency and control
Figure 1. The QNX CAR architecture for BluetoothThe PPS abstraction layer for Bluetooth provides an application interface for activities such as pairing, profile management, status updates, and device list management.
A Bluetooth connection can be initiated either by the vehicle or by the mobile device. When requesting the connection, the developer selects a Bluetooth profile. After the connection has been established, the system creates PPS objects that io-bluetooth uses to manage the connection according to the permissions and other parameters in the selected profile.