[soraberri]

When the features sheet of a mobile phone (or other programmable Bluetooth device) states that a particular bluetooth profile is supported (GAP, SPP, Headset, etc..) what does it exactly mean?
I have the feeling about it means that a developer could IMPLEMENT any of the aforesaid profiles successfully, but this doesn't necessarily imply that this profiles are actually IMPLEMENTED.

So, have I the hit feeling?

Thanks to all

[petrib]

Different Bluetooth functionality is defined through a Bluetooth profile.

E.g., the Bluetooth DUN (Dial-Up Networkin) profile defines how, for example, you can use a Bluetooth phone as a modem.

The Bluetooth Handsfree profile defines how a headset or a carkit should work with a Bluetooth phone.

And so on.

Different profiles are defined by different versions of the Bluetooth specifications.

Device manufacturers decide which profiles the implement on their devices.

It is also possible for developers to implement additional profiles on top of manufacturer-supplied profiles.

More details on https://www.bluetooth.org/

[soraberri]

So, it's for me possible to IMPLEMENT the CTP (cordless Telephony profile) on top of manufacturer supplies of a Symbian phone not SUPPORTING the CTP profile?
If this is true, why shouldn't the manufacturer say in his product specification that the phone doesn't support CTP?

[seppo_fn]

When it is said that a device supports a certain profile, it DOES mean that the profile is implemented in that product. So the use case defined by the profile should be possible.

Many of the 3rd party applications can use some of the existing profiles of the product or simply create a proprietary service for the application. Examples of re-usable profiles are Serial Port Profile and Object Push Profile.

The possibility for a developer to implement a new profile depends on the existing hardware/software support on lowel levels of the Bluetooth architecture in the product and on APIs available for accessing the features.

In case of MIDP, you hardly have a possibility to develop a new profile. In case of a Symbian C++, you have better chances of implementing something new. However, the restrictions in the existing architecture might prevent from implementing all required features for a new profile with the SDKs. In case of CTP, you would need access to telephony interfaces of which all are not public.

Seppo
Forum Nokia

[soraberri]

Thanks Seppo, your post have been really explanatory.
Nevertheless I perhaps need additional hints about:

You wrote:
"Many of the 3rd party applications can use some of the existing profiles of the product"

and the question is: How do they manage it? e.g. Series 60 APIs are ready for RFCOMM, L2CAP, secutity, SDP... tasks, but there are no specific API for File Transfer Profile, however BT enabled Nokia phones do implement the File Transfer profile. How can I make use of that?

You wrote:
"In case of CTP, you would need access to telephony interfaces of which all are not public"

so, does it imply that these interfaces (I understand APIs) are not even written or advertised at all in the series60 SDK, or that having been advertised, they won't work on the device?

Thank you for your helpull answers

Luis

[seppo_fn]

As a service class UUID, you use the UUID of Serial Port Profile (0x1101) or Object Push Profile (0x1105). Examples BluetoothPoint-To-Point and BluetoothObjectExchange describe how to use SPP or OPP profile functionality in the application.

In Nokia phones, only a server side implementation of the FTP is implemented, meaning that only a remote device can send files via FTP to the phone or browse the files of the predefined folder (in Series 60 phones it covers the files sent via Bluetooth FTP in Inbox, in Series 80 it is C:\MyFiles folder and its files).

So there is no real need for 3rd party applications to use FTP. The applications wishing to send/receive files from/into the application, can use Object Push Profile. In practice, they only miss the browsing feature.

Symbian OS uses client-server architecture, and in the case of Bluetooth you get access to protocols mainly via Sockets interface. You don't have access to low-level system interfaces; those are reserved for the manufacturer.

Seppo
Forum Nokia