0.49 - 28.11.2000 - Added HID over L2CAP subdocument.


The host is the device using or requesting the services of a Human Interface Device.


Master/Slave roles. Although there are no mandated master/slave roles, it is recommended that Bluetooth Human Interface Devices normally be a slave device, in order to avoid having the host radio multiplex between piconets.

Human Interface Devices use only limited discoverable mode and non-discoverable mode.


limited discoverable mode for 30-180 seconds, for parse


how:
PIN - pairing
HID descriptors
..rest like USB device


5.2.2 L2CAP HID Protocol Support
The implementation of L2CAP on the host should meet the default minimum MTU (maximum transmission unit) of 48 bytes, although the default value of 672 is recommended. The host BT-HID adapter driver should implement packet segmentation and reassembly up to the largest practical size (64k bytes maximum) in order to maintain compatibility with all possible Bluetooth HIDs, but this is not required for hosts which support only Boot Protocol mode. Both the HID and the Host should look at the other's L2CA_ConfigReq primitive to determine the MTU they use for Segmentation and their own MTU for Reassembly


5.4.5.1 HID Protocol Connection Establishment
Both HID_Control and HID_Interrupt L2CAP channels shall be established in order for the HID protocol connection to be considered established. The HID_Control connection shall be initiated first. It is permissible for the host (or the device, in the event of device initiated reconnection) to configure both channels simultaneously (i.e. configuration sequence can overlap). The HID channels shall be closed in reverse order, i.e. Interrupt then Control.

??
The host will typically implement the HID profile by writing an interface driver (sometimes called a miniport driver on a PC host) between a standard HID class driver and the Bluetooth L2CAP and Link Manager layers. Recommended Bluetooth link parameters for connecting to HIDs are specified.


http://discussion.forum.nokia.com/forum/showthread.php?t=101026
btl2cap://btaddr:11


Original Post: L2CAP - PSM Value  (eGroups Msg. )    Date: 2000-08-24

http://www.palowireless.com/infotooth/knowbase/l2cap/110.asp
The L2CAP spec (page. 278) say "PSM values are separated into two ranges. Values in the first range are assigned by the Bluetooth SIG and indicate protocols. The second range of values [0x1001 - 0xffff] are dynamically allocated and used in conjunction with the Service Discovery Protocol (SDP). The dynamically assigned values may be used to support multiple implementations of a particular protocol, e.g., RFCOMM, residing on top of L2CAP or for prototyping an experimental protocol."

------------Sony ericson-------
Service Name: HID Mouse & Keyboard
Service Description: Remote Control of PC applications and other devices
Service Provider: Sony Ericsson
Service RecHandle: 0x1000e
Service Class ID List:
  "Human Interface Device" (0x1124)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 17
  "HIDP" (0x0011)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Human Interface Device" (0x1124)
    Version: 0x0100