Summary
The Bluetooth API, as part of Local Connectivity API, enables applications to scan and pair with devices, search and use services on other devices, and allow transfer data.
Supported Functionality
| Requirement |
Comments |
Priority |
| Device Discovery |
- The ability to search for devices within range using General Unlimited Inquiry or Limited Inquiry.
- Device discovery shall be performed asynchronously. Results shall be obtained both incrementally and non-incrementally.
|
|
| Service Discovery |
- The ability to query devices within range for the services that they provide.
- The ability to limit the result set based on Bluetooth device address, service UUID.
- Service discovery shall be performed asynchronously. Results shall be obtained both incrementally and non-incrementally.
|
|
| Service Record |
- The ability to retrieve the service record of a service offered by a Bluetooth device.
- The ability to query the attributes of a service record.
- The ability to construct a new service record that describes a to be published service.
- The ability to register a service record with the platforms SDP database.
- The ability to remove a previously registered service record from the platforms SDP database.
|
|
| Address |
- The ability to construct, manipulate and compare Bluetooth addresses.
|
|
| UUID |
- The ability to construct manipulate and compare Bluetooth UUIDs.
|
|
| Sockets |
- The ability to connect to a remote device via L2CAP.
- The ability to connect to a remote device via RFCOMM.
- The ability to listen for incoming L2CAP connections.
- The ability to listen for incoming RFCOMM connections.
|
|
| Security |
- The ability to specify the security parameters (authorization, authentication and encryption) required for incoming connections.
|
|
| Device Control |
- The ability to control the power state of the local Bluetooth device.
- The ability to control the discoverability of the local Bluetooth device.
|
|
| Pairing |
- The ability to add/request a device pairing with a given Bluetooth device.
- The ability to remove/request removal of a device pairing with a given Bluetooth device.
- The ability to flag/request that a paired device is (not) automatically authorized.
|
|
| UI Elements |
- UI elements (i.e. PIN entry, confirmation dialogs etc) are expected to be provided by the platform (symbian) and via the application for BlueZ based systems.
|
|
| Local Device Selection |
- The ability to select which local Bluetooth device is used. As it is typical/possible to have only one local Bluetooth device the API should default to this device unless another device explicitly specified.
|
|
| QML accessability |
- Most classes shall be easily accessible from within QML and a QML plug-in shall provide link dependency
|
|
| Send file |
- The ability to send file to another devices.
- Support OBEX to send get and put commands to remote devices.
- The ability to cancel transfers in progres.
|
|
Suggestion
Not Evaluated