Microsoft Technology Licensing, LLC

Microsoft Corporation

Om Sharma

Doron J Holan

Marcus J Andrews

James E Veres

Kenneth D Ray

Louis J Giliberto

John Michael Thornton

C Shane Evans

Scott R Leatham

Firdosh Kersy Bhesania

Ervin Peretz

Robert Ingman

Doron J c/o Microsoft Corporation Holan

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.

Method to obtain friendly names for Bluetooth devices

A system for using computer input devices with software applications is disclosed. The system includes an input device mapper API, which uses a language of semantics as an interface between input devices and software applications. The input device mapper receives information about which semantics the devices connected to the computer are able to implement, and which semantics correspond to actions that a user can request the software to perform. The input device mapper maps controls on the available devices into user-requestable software actions by matching, as closely as possible, device controls and software actions that correspond to the same semantic. The system thus makes input devices and software applications transparent to each other, and permits a software application to be designed to operate without regard to which input device is being used to control its actions.

Application programming interface that maps input device controls to software actions

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.

Method to configure a bluetooth logical link control and adaptation protocol channel

A computer peripheral has a processor, non-volatile memory, and a plurality of controls. The non-volatile memory holds control mappings corresponding to a plurality of application program genres. The control mappings indicate actions to be performed in application programs of particular genres in response to actuation of particular controls. The control mappings indicate controls by unique string indexes that are also used in HID control descriptors associated with the computer peripheral.

Game control device having genre data

A system for using computer input devices with software applications is disclosed. The system includes an input device mapper, which uses a language of semantics as an interface between input devices and software applications. The input device mapper receives information about which semantics the devices connected to the computer are able to implement, and which semantics correspond to actions that a user can request the software to perform. The input device mapper maps controls on the available devices into user-requestable software actions by matching, as closely as possible, device controls and software actions that correspond to the same semantic. An input device manager employing the disclosed input device mapper translates device operation events into the software's input dialect to direct the software to perform the action into which an operated control has been mapped. The system thus makes input devices and software applications transparent to each other, and permits a software application to be designed to operate without regard to which input device is being used to control its actions.

System and method for mapping input device controls to software actions

Growing community of inventors

Kirkland, WA, United States of America

Om Sharma