[Interest] Bluetooth Qt Connectivity module
Ramakanthreddy.Kesireddy at techmahindra.com
Thu Feb 13 09:44:02 CET 2014
Thanks a lot for your inputs.
I think App ID(Unique identification used to manage mobile application and user pairing) is not needed if we use Bluetooth SPP connection
as UUID for SPP remain same even if we connect different smartphones(like in android)
From: interest-bounces+ramakanthreddy.kesireddy=techmahindra.com at qt-project.org [mailto:interest-bounces+ramakanthreddy.kesireddy=techmahindra.com at qt-project.org] On Behalf Of Blasche Alexander
Sent: 12 February 2014 19:07
To: interest at qt-project.org
Subject: Re: [Interest] Bluetooth Qt Connectivity module
> -----Original Message-----
> From: interest-bounces+alexander.blasche=digia.com at qt-project.org
> [mailto:interest-bounces+alexander.blasche=digia.com at qt-project.org]
> On Behalf Of Ramakanthreddy Kesireddy
> If the multiple smartphones(multiple apps of different smartphones)
> are connected to Infotainment Linux system through Bluetooth SPP, how
> does Qt Bluetooth handle the requested command say tirepressure from
> IVI system?
The Bluetooth module offers an API to connect the two parties via a socket connection (see QBluetoothSocket and QBluetoothServer).
The actual type of data send across the SPP connection is not known to the API. It is up to the application to react to the readyRead() signal and read/process the received data. In any case the particulars of the IVI command set are at least one layer above the SPP protocol (usually RFCOMM or L2CP). QtBluetooth provides the network layer. IVI operates as a transport layer protocol even further above.
> Do we need to pass the Application ID from smartphone to identify
> particular app so that response would be sent to particular
> application or UUID of the smartphone app is sufficient to connect and send the response?
This is an IVI specific question and would be dependent on the IVI's protocol/command set.
Interest mailing list
Interest at qt-project.org
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
More information about the Interest