[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bluetooth and 6310
From: |
Marcel Holtmann |
Subject: |
Re: Bluetooth and 6310 |
Date: |
17 Apr 2003 05:03:54 +0200 |
Hi again,
> I discovered some secrets of the Nokia Bluetooth support in the 6310
> generation. They use a special SDP entry, which is not in the public
> browse group of their SDP database. And here it is:
>
> Attribute Identifier : 0x0 - ServiceRecordHandle
> Integer : 0x10006
> Attribute Identifier : 0x1 - ServiceClassIDList
> Data Sequence
> UUID128 : 0x00005002-0000-1000-8000-0002ee00-0001
> Attribute Identifier : 0x4 - ProtocolDescriptorList
> Data Sequence
> Data Sequence
> UUID16 : 0x0100 - L2CAP
> Data Sequence
> UUID16 : 0x0003 - RFCOMM
> Channel/Port (Integer) : 0xe
>
> The main secret of this is that they use RFCOMM channel 14 for their
> communication protocol. At the moment I am not sure which kind of FBUS
> version did they use, but it makes sense that they use a variant of the
> phonet one, because the RFCOMM channel provides a reliable link.
I was right with my assumption that Nokia uses a phonet like protocol on
the Bluetooth link. This is the initial exchange of the connection
manager:
Suite: 19 00 10 d0 00 01 04
Phone: 19 10 00 d0 00 01 05
Suite: 19 00 10 1b 00 06 00 01 00 07 00 01
Phone: 19 10 00 1b 00 2e 01 2d 00 08 00 01 48 28 00 20
56 20 30 34 2e 31 30 0a 30 34 2d 30 31 2d 30 32
0a 4e 50 45 2d 34 0a 28 63 29 20 4e 4d 50 2e 00
00 00 00 00
So the phonet protocol for Bluetooth would look like this:
{ FrameID, DestDEV, SrcDEV, MsgType, FrameLengthLo, FrameLengthHi,
{block} }
where FrameID: 0x19
DestDev, SrcDev: 0x00: mobile phone
0x10: TE [eg. PC]
MsgType: see List
FrameLength: {block}
Regards
Marcel
- Bluetooth and 6310, Marcel Holtmann, 2003/04/16
- Re: Bluetooth and 6310,
Marcel Holtmann <=