Abstract: In wireless USB data transfers over UWB, software configures hardware thresholds to control data transfer in a manner that uses bandwidth for good connections over bad connections, given the high error rate experienced with wireless USB. Periodic transfers are first attempted before asynchronous transfers, as long as the periodic transfers are successful. When failures are occurring, the hardware includes a mechanism having a software-configurable threshold specifying the number of errors a given endpoint can tolerate before it is paused in the schedule. By pausing transfer attempts that are likely to again fail, endpoints with successful transfers are favored over those experiencing errors. When the number of active transfers pending exceeds a software-configurable notification threshold for isochronous endpoints, the hardware notifies the software of this state, corresponding to a low-buffer condition at the receiver.

Abstract: Disclosed are a unique system and method that facilitate establishing and maintaining a secure connection between at least one wireless input component and a host (e.g., PC). The system and method involve the wireless input component broadcasting a message that can be “heard” by any potential host located within a given distance from the wireless input component. The message can indicate that the input component is available for use or pairing with a PC. PCs in the area can respond to the message by notifying the user that a wireless input component is available and by generating a random PIN. The PIN can be displayed to the user on the respective PC. The user can be prompted to enter the PIN using the wireless device. When a match between the user's response and the corresponding PC is determined, the two can be securely linked. In addition the invention provides support of wireless input devices at boot or start up.

Abstract: Techniques are disclosed to provide I/O handling in generic USB drivers. More particularly, a generic USB device driver architecture is described which enables development through a user-mode USB library that accesses a generic kernel-mode driver. The architecture may be utilized to provide efficient development for I/O handling. In a described implementation, a method includes defining a data structure utilized to access a plugged-in device. A pipe policy of the data structure is defined and utilizing to access the plugged-in device through a plurality of routines provided by a generic user-mode library (e.g., a dynamic link library (DLL)). The generic user-mode library is communicatively coupled to a kernel-mode generic device driver. In another described implementation, a separate generic device driver is loaded for each plugged-in device or for each functionality supported by the device.

Abstract: Techniques are disclosed to provide generic USB drivers. More particularly, a generic USB device driver architecture is described which enables development through a user-mode USB library that accesses a generic kernel-mode driver. In a described implementation, a method includes loading a kernel-mode generic device driver in response to a plug-in event of a device. A user software component accesses the device by utilizing routines provided by the generic user-mode library (e.g., a dynamic link library (DLL)) that communicates with the generic device driver.

Abstract: Techniques are disclosed to provide advanced power management in generic USB drivers. More particularly, a generic USB device driver architecture is described which enables development through a user-mode USB library that accesses a generic kernel-mode driver. The architecture may be utilized to provide advanced power management. In a described implementation, a method includes defining a power management policy for a device plugged into a computing system and utilizing the defined power management policy to determine when the device enters a suspend mode. Once the device enters the suspend mode, the method allows the computing system to enter a lower-power state. In a further described implementation, the power management policy is defined through a plurality of routines provided by a generic user-mode library (e.g., a dynamic link library (DLL)), where the generic user-mode library is communicatively coupled to a kernel-mode generic device driver.

Abstract: A computer receives data from a keyboard having one or more keys which cause generation of keyboard data that quantitatively describe the relative force applied to those keys. The keyboard data are transmitted in an HID report containing identifiers for one or more keys that have been pressed and force data for each key. The force data may be a multi-bit value quantifying the key force, or a null indicator signaling that the key is not force-sensing. Keyboard data messages are then prepared which identify keys pressed, contain force data, and may indicate whether the force data updates previous force data. Force updates are only provided to application programs registering for key force data. In other aspects of the invention, key repeat messages are automatically generated for a key held pressed by a user. The key repeat messages are generated at a rate controlled by the amount of force applied to the key.

Abstract: A system and/or method that facilitates the installation and/or authentication of a device by invoking installation protocols and/or authentication protocols for a non-physical connection. A physical interface component provides a physical connection between at least one wireless device and at least one network entity in which the installation protocols and/or authentication protocols can be exchanged. The physical interface component can utilize a token key to establish multiple non-physical connections with multiple wireless devices. Additionally, the physical interface component can utilize a daisy chain scheme to install and/or authenticate a wireless device.