l2cap packets are always identified by a channel ID, which is negotiated
when each l2cap connection (channel) is established. Continuation fragments
always have the channel ID in the packet header, so there is no ambiguity
over which continuation fragment belongs to which connection. You should
take another look at the L2CAP section in the core spec.
-albert
On 4/13/06, [email protected] <[email protected]> wrote:
>
>
> Marcel & all,
> I'am puzzling over the following question. How to process fragmentation
> synchronously when two l2cap connections over one acl connection?
> in bluetooth specification, the continuing fragments of l2cap only can be
> identified by acl connection handles. so if two l2cap connections build over
> one acl conncetion (such as two l2cap connections bulid between two
> bluetooth devices), and the two l2cap connections received continuing
> fragments synchronously，how can i identify which fragments belong the first
> l2caps connections and which fragments belong the other?
> thanks.
>
>
>
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
>
>
Albert,
I don't think each l2cap continuation fragment has the CID in it.
It is only the start fragment that has the CID in it. Refer to the
attached image.
At one instance of time we cannot receive two l2cap start fragments.
I mean once we get an l2cap start fragment, we can be rest assured
that the l2cap continuation packets that we will be receiving after
that belong to the same channel ID for which we recieved the start
fragment.
Thus Marcel correctly pointed out that we are not allowed to mix l2cap
fragments.
Regards,
Mayank
On 4/13/06, Albert Huang <[email protected]> wrote:
> l2cap packets are always identified by a channel ID, which is negotiated
> when each l2cap connection (channel) is established. Continuation fragments
> always have the channel ID in the packet header, so there is no ambiguity
> over which continuation fragment belongs to which connection. You should
> take another look at the L2CAP section in the core spec.
>
> -albert
>
>
> On 4/13/06, [email protected] <[email protected] > wrote:
> >
> >
> > Marcel & all,
> > I'am puzzling over the following question. How to process fragmentation
> synchronously when two l2cap connections over one acl connection?
> > in bluetooth specification, the continuing fragments of l2cap only can be
> identified by acl connection handles. so if two l2cap connections build over
> one acl conncetion (such as two l2cap connections bulid between two
> bluetooth devices), and the two l2cap connections received continuing
> fragments synchronously，how can i identify which fragments belong the first
> l2caps connections and which fragments belong the other?
> > thanks.
> >
> >
> >
> > --------------------------------------------------------
> > ZTE Information Security Notice: The
> information contained in this mail is
> solely property of the sender's organization. This
> mail communication is confidential.
> Recipients named above are obligated to maintain
> secrecy and are not permitted to disclose
> the contents of this communication to others.
> > This email and any files transmitted with it
> are confidential and intended solely for
> the use of the individual or entity to
> whom they are addressed. If you have
> received this email in error please notify
> the originator of the message. Any views
> expressed in this message are those of the
> individual sender.
> > This message has been scanned for viruses and Spam by
> ZTE Anti-Spam system.
> >
> >
>
>
Hi Albert,
> l2cap packets are always identified by a channel ID, which is
> negotiated when each l2cap connection (channel) is established.
> Continuation fragments always have the channel ID in the packet
> header, so there is no ambiguity over which continuation fragment
> belongs to which connection. You should take another look at the
> L2CAP section in the core spec.
you are not allowed to mix L2CAP fragments. As simple as that.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel