Abstract: A method, apparatus, and computer program product provide applications and application developers with generic access from user mode to the L2CAP layer of Bluetooth by exposing the L2CAP layer to user mode via a socket interface. In particular, a kernel mode primary component and user mode helper component cooperate to expose a Winsock interface to user mode components, and to manage various Bluetooth-specific functions and operations, allowing a user mode user application to access Bluetooth functionality without providing Bluetooth-specific commands or actions, and without being required to use RFCOMM.

Abstract: A method and apparatus to decrease the amount of time it takes to obtain friendly names of Bluetooth devices is presented. A name server caches friendly names for devices that it has acquired from other devices or from other name servers. The name server is any device that caches friendly names of Bluetooth devices and that makes the friendly names available to other devices. A requesting device determines if a name server has responded to an inquiry command. If a name server has responded, the device gets the friendly names the name server has cached and requests the friendly names of devices that responded that have not been cached by the name server. Identification of a name server is accomplished by embedding a marker in the friendly name field after the null character to indicate that the device is a name server.

Abstract: A method for providing an interface to a Bluetooth compliant device can emulate a modem such that computer software programs can communicate through the Bluetooth compliant device in the same manner in which they would communicate through a standard modem to access a dial-up, wide area network. The method also supports an interface to a Bluetooth compliant device which can emulate a network socket such that computer software programs can communicate through the Bluetooth compliant device seemingly in the same manner in which they would communicate through a standard network interface card to access a local area network. The method also allows for the interface to a Bluetooth compliant device to be dependent on the nature of the Bluetooth compliant device.

Abstract: A service discovery stream is represented as an N-ary tree that provides the capability to change, add, or remove an element with only one modification to the entire tree. The number of elements in a stream are counted and each element and the element's children are converted into a node of the N-ary tree. Each node in the tree can have any number of siblings, which are linked to each other using a doubly linked list.

Abstract: A method and apparatus to decrease the amount of time it takes to obtain friendly names of Bluetooth devices is presented. A name server caches friendly names for devices that it has acquired from other devices or from other name servers. The name server is any device that caches friendly names of Bluetooth devices and that makes the friendly names available to other devices. A requesting device determines if a name server has responded to an inquiry command. If a name server has responded, the device gets the friendly names the name server has cached and requests the friendly names of devices that responded that have not been cached by the name server. Identification of a name server is accomplished by embedding a marker in the friendly name field after the null character to indicate that the device is a name server.

Abstract: A technique to simplify L2CAP channel creation/configuration for a node is presented. The method enables a node to determine how involved it is in the L2CAP channel connection creation and management process. There are three levels of participation that the node may specify. The three levels are no involvement at all, minimal involvement, and total involvement. In no involvement, the channel is dropped if a remote node does not accept all node specified parameters. In minimal involvement, the channel is dropped if a remote node does not accept all node specified parameters and the node is notified when the connection has been disconnected by a remote disconnect or HCI link loss. In the total involvement level, the node is fully involved in the channel creation/configuration. The node provides a function pointer that is called to confirm or reject parameters. If a parameter is unacceptable, the connection is disconnected.

Abstract: A method, apparatus, and computer program product provide applications and application developers with generic access from user mode to the L2CAP layer of Bluetooth by exposing the L2CAP layer to user mode via a socket interface. In particular, a kernel mode primary component and user mode helper component cooperate to expose a Winsock interface to user mode components, and to manage various Bluetooth-specific functions and operations, allowing a user mode user application to access Bluetooth functionality without providing Bluetooth-specific commands or actions, and without being required to use RFCOMM.

Abstract: A system and method of Bluetooth compliant architecture and communication uses a miniport driver structure to efficiently implement the Bluetooth protocol layers, while allowing simple communication with underlying hardware.

Abstract: A technique to simplify L2CAP channel creation/configuration for a node is presented. The method enables a node to determine how involved it is in the L2CAP channel connection creation and management process. There are three levels of participation that the node may specify. The three levels are no involvement at all, minimal involvement, and total involvement. In no involvement, the channel is dropped if a remote node does not accept all node specified parameters. In minimal involvement, the channel is dropped if a remote node does not accept all node specified parameters and the node is notified when the connection has been disconnected by a remote disconnect or HCI link loss. In the total involvement level, the node is fully involved in the channel creation/configuration. The node provides a function pointer that is called to confirm or reject parameters. If a parameter is unacceptable, the connection is disconnected.

Abstract: A method and apparatus to decrease the amount of time it takes to obtain friendly names of Bluetooth devices is presented. A name server caches friendly names for devices that it has acquired from other devices or from other name servers. The name server is any device that caches friendly names of Bluetooth devices and that makes the friendly names available to other devices. A requesting device determines if a name server has responded to an inquiry command. If a name server has responded, the device gets the friendly names the name server has cached and requests the friendly names of devices that responded that have not been cached by the name server. Identification of a name server is accomplished by embedding a marker in the friendly name field after the null character to indicate that the device is a name server.