Lines Matching +full:quality +full:- +full:of +full:- +full:service
1 .\" Copyright (c) 2001-2002 Maksim Yevmenkin <m_evmenkin@yahoo.com>
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
10 .\" notice, this list of conditions and the following disclaimer in the
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
42 Control and Adaptation Protocol as per chapter D of the Bluetooth Specification
45 L2CAP provides connection-oriented and connectionless data services to upper
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.
76 concept of
78 Each channel is bound to a single protocol in a many-to-one fashion.
85 Each one of the end-points of an L2CAP channel is referred to by a channel
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.
106 .Bl -tag -width foo
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
123 sent to the upper layer and the part of the local L2CAP entity processing the
134 the traffic parameters of the data traffic are to be renegotiated.
145 If a large amount of parameters need to be negotiated,
167 Indication has been sent to the upper layer to notify the owner of the CID
178 L2CAP is able to distinguish between upper layer protocols such as the Service
187 .Ss Quality of Service
188 The L2CAP connection establishment process allows the exchange of information
189 regarding the quality of service (QoS) expected between two Bluetooth units.
191 The Baseband Protocol supports the concept of a piconet, a group of devices
197 The following features are outside the scope of L2CAP responsibilities:
198 .Bl -dash -offset indent
207 L2CAP does not support the concept of a global group name.
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).
251 allocated by the local L2CAP entity, and Result of the request.
254 of what processing is delaying the establishment of the connection.
256 This message includes the parameters for the address of the remote device that
263 are the remote device's 48-bit address, Identifier sent in the request, local
265 The output parameter is the Result of the service request.
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
286 include the local CID of the endpoint being configured, outgoing transmit MTU
291 This message includes the parameter indicating the address of the remote
294 Requests the disconnection of the channel.
298 is zero if an L2CAP Disconnect Response is received, otherwise a non-zero value
306 Response to transfer of data request.
309 .Bd -literal -offset indent
313 uint16_t length; /* length of the data */
318 The output parameters are Result and Length of data written.
320 Requests the creation of a CID to represent a logical connection to multiple
327 .Bf -emphasis
331 The use of this message closes down a Group.
332 .Bf -emphasis
336 Requests the addition of a member to a group.
338 CID representing the group and the BD_ADDR of the group member to be added.
339 The output parameter Result confirms the success or failure of the request.
340 .Bf -emphasis
344 Requests the removal of a member from a group.
346 the CID representing the group and BD_ADDR of the group member to be removed.
347 The output parameter Result confirms the success or failure of the request.
348 .Bf -emphasis
352 Requests a report of the members of a group.
355 failure of the operation.
357 of the Bluetooth addresses of the N members of the group.
358 .Bf -emphasis
362 Initiates an L2CA Echo Request message and the reception of the corresponding
365 BD_ADDR, Echo Data and Length of the echo data.
367 Result, Echo Data and Length of the echo data.
369 Initiates an L2CA Information Request message and the reception of the
373 Result, Information Data and Size of the information data.
375 Request to disable (enable) the reception of connectionless packets.
377 parameter is the PSM value indicating service that should be blocked
382 .Bl -tag -width foo
391 Returns list of active baseband connections (i.e., ACL links).
393 Returns list of active L2CAP channels.
395 Returns an integer containing the current value of the auto disconnect
398 This command accepts an integer and sets the value of the auto disconnect
400 The special value of 0 (zero) disables auto disconnect timeout.
403 This node shuts down upon receipt of an