Lines Matching +full:data +full:- +full:channel
1 .\" Copyright (c) 2001-2002 Maksim Yevmenkin <m_evmenkin@yahoo.com>
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
45 L2CAP provides connection-oriented and connectionless data services to upper
49 protocols and applications to transmit and receive L2CAP data packets up to
52 .Bl -enum -offset indent
56 delivery of data packets, although there might be individual packet corruption
60 The Baseband always provides the impression of full-duplex communication
62 This does not imply that all L2CAP communications are bi-directional.
66 L2CAP provides a reliable channel using the mechanisms available at the
68 The Baseband always performs data integrity checks when
69 requested and resends data until it has been successfully acknowledged or
72 occur even after the data has been successfully sent.
78 Each channel is bound to a single protocol in a many-to-one fashion.
80 channels can be bound to the same protocol, but a channel cannot be bound to
82 Each L2CAP packet received on a channel is directed to
85 Each one of the end-points of an L2CAP channel is referred to by a channel
87 Channel identifiers (CIDs) are local names representing a logical
88 channel end-point on the device.
92 illegal identifier and must never be used as a destination end-point.
94 CID 0x0002 is reserved for group-oriented channel.
96 channel endpoint for multiple simultaneous L2CAP channels between a local
102 assigned to (remote) channel endpoints by several remote devices connected
105 .Ss Channel Operational States
106 .Bl -tag -width foo
108 In this state, there is no channel associated with this CID.
116 In this state, the CID represents a local end-point and an L2CAP Connect
120 In this state, the remote end-point exists and an L2CAP Connect Request has
128 negotiating the channel parameters.
130 entered when the channel parameters are being renegotiated.
133 state, all outgoing data traffic is suspended since
134 the traffic parameters of the data traffic are to be renegotiated.
136 data traffic is accepted until the remote channel endpoint has entered
157 In this state, the connection has been established and configured, and data
181 The data packets defined by the Baseband Protocol are limited in size.
198 .Bl -dash -offset indent
202 L2CAP does not enforce a reliable channel or ensure data integrity,
205 L2CAP does not support a reliable multicast channel.
211 .Bl -tag -width ".Va hci"
244 .Bl -tag -width foo
246 Requests the creation of a channel representing a logical connection to a
249 device's 48-bit address (BD_ADDR).
257 issued the connection request, the local CID representing the channel being
263 are the remote device's 48-bit address, Identifier sent in the request, local
269 Requests the initial configuration (or reconfiguration) of a channel to a new
270 set of channel parameters.
272 incoming receivable MTU (InMTU), new outgoing flow spec-ification, and flush
277 This message includes the parameters indicating the local CID of the channel
279 be sent across the channel) and the flowspec describing the characteristics of
280 the incoming data.
281 All other channel parameters are set to their default values
294 Requests the disconnection of the channel.
295 Input parameter is the CID representing the local channel endpoint.
298 is zero if an L2CAP Disconnect Response is received, otherwise a non-zero value
306 Response to transfer of data request.
307 Actual data must be received from
309 .Bd -literal -offset indent
310 /* L2CA data packet header */
313 uint16_t length; /* length of the data */
314 uint16_t lcid; /* local channel ID */
318 The output parameters are Result and Length of data written.
327 .Bf -emphasis
332 .Bf -emphasis
340 .Bf -emphasis
348 .Bf -emphasis
358 .Bf -emphasis
365 BD_ADDR, Echo Data and Length of the echo data.
367 Result, Echo Data and Length of the echo data.
373 Result, Information Data and Size of the information data.
382 .Bl -tag -width foo