The QNX CAR application platform supports connections to external devices over Bluetooth—it can initiate a Bluetooth connection or accept a connection request.
The supported profiles include:
- HFP (Hands-Free Profile)
- MAP (Message Access Profile)
- PBAP (Phone Book Access Profile)
- SPP (Serial Port Profile)
The QNX CAR application platform comes preintegrated with SAP's (iAnywhere’s) Bluetooth stack. While the profiles listed above are preintegrated and tested for this release, SAP's Bluetooth stack supports many other profiles that can also be integrated.
The front-end resource manager for Bluetooth is io-bluetooth. This resource manager offers a POSIX-compliant API and provides:
- low-level access to the Bluetooth radio (typically a serial interface such as UART, USB, or I2S)
- support for Bluetooth profiles and profile concurrency
- the Bluetooth stack (iAnywhere) and any/all other direct control functionality (e.g., Cybercom BlueGo for handsfree)
The 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.