Abstract: Methods and devices for identifying available applications for use with hardware of a computer device may include generating an application request with at least one device identification and a hardware identification to determine available applications. The methods and devices may include transmitting the application request to a remote application store. The methods and devices may include receiving, from the remote application store, an available application list with one or more applications having application relationship metadata that identifies compatible usage with the at least one hardware identification. The methods and devices may include presenting the available application list on a display of the computer device.

Abstract: Methods and devices for identifying available applications for use with hardware of a computer device may include generating an application request with at least one device identification and a hardware identification to determine available applications. The methods and devices may include transmitting the application request to a remote application store. The methods and devices may include receiving, from the remote application store, an available application list with one or more applications having application relationship metadata that identifies compatible usage with the at least one hardware identification. The methods and devices may include presenting the available application list on a display of the computer device.

Abstract: Methods and devices for identifying available applications for use with hardware of a computer device may include generating an application request with at least one device identification and a hardware identification to determine available applications. The methods and devices may include transmitting the application request to a remote application store. The methods and devices may include receiving, from the remote application store, an available application list with one or more applications having application relationship metadata that identifies compatible usage with the at least one hardware identification. The methods and devices may include presenting the available application list on a display of the computer device.

Abstract: Methods and devices for identifying available applications for use with hardware of a computer device may include generating an application request with at least one device identification and a hardware identification to determine available applications. The methods and devices may include transmitting the application request to a remote application store. The methods and devices may include receiving, from the remote application store, an available application list with one or more applications having application relationship metadata that identifies compatible usage with the at least one hardware identification. The methods and devices may include presenting the available application list on a display of the computer device.

Abstract: This document describes techniques for detecting state loss on a device. These techniques permit a computer connected to a device to forgo, in many cases, reinitializing the device when returning to a normal-power mode.

Abstract: In embodiments of driver interface functions to interface client function drivers, a set of serial communication protocol driver interfaces are exposed by a core driver stack, and the serial communication protocol driver interfaces include driver interface functions to interface with client function drivers that correspond to client devices configured for data communication in accordance with the serial communication protocol. A client function driver can check for the availability of a driver interface function before interfacing with the core driver stack via the serial communication protocol driver interfaces. A contract version identifier can also be received from the client function driver via an extension of the driver interface functions, where the contract version identifier indicates a set of operation rules by which the client function driver interfaces with the core driver stack.

Abstract: A computer system that recognizes multi-function devices and associates functions with multi-function devices. Each multi-function device may be represented by a multi-function object, allowing tools, applications or other components within the computer to take actions relating to the entire device or relating to a function based on the association of that function with other functions in the same device. These actions include displaying information about devices, instead of or in addition to information about functions. Actions also include selecting functions based on proximity within a device. Functions may be associated with a multi-function device using a unique device identifier provided by the device or generated for the function based on a connection hierarchy between functions and the computer. Devices may be configured to provide the same identifier regardless of the transport over which the device is accessed.

Abstract: In embodiments of driver interface functions to interface client function drivers, a set of serial communication protocol driver interfaces are exposed by a core driver stack, and the serial communication protocol driver interfaces include driver interface functions to interface with client function drivers that correspond to client devices configured for data communication in accordance with the serial communication protocol. A client function driver can check for the availability of a driver interface function before interfacing with the core driver stack via the serial communication protocol driver interfaces. A contract version identifier can also be received from the client function driver via an extension of the driver interface functions, where the contract version identifier indicates a set of operation rules by which the client function driver interfaces with the core driver stack.

Abstract: A computer system that accesses multi-transport devices and associates device instances of the multi-transport device with each other. Devices provide the same device identifier such as a device unique identifier regardless of the transport over which the device is accessed. A visual representation for the multi-transport device may be provided to a user using the device identifier. Also, a single functional representation for the multi-transport device may be provided based on an identifier provided by each function of the device. The functional representation may be independent of the addition and removal of transports and allows abstracting device access via multiple transports from a user and an application. Transports may be selected at an application and/or a system level. Operating characteristics of available transports may be used to select a desired transport, based on transport requirements specified by the application, the user or the system.

Abstract: In embodiments of driver interface functions to interface client function drivers, a set of serial communication protocol driver interfaces are exposed by a core driver stack, and the serial communication protocol driver interfaces include driver interface functions to interface with client function drivers that correspond to client devices configured for data communication in accordance with the serial communication protocol. A client function driver can check for the availability of a driver interface function before interfacing with the core driver stack via the serial communication protocol driver interfaces. A contract version identifier can also be received from the client function driver via an extension of the driver interface functions, where the contract version identifier indicates a set of operation rules by which the client function driver interfaces with the core driver stack.

Abstract: This document describes techniques for detecting state loss on a device. These techniques permit a computer connected to a device to forgo, in many cases, reinitializing the device when returning to a normal-power mode.

Abstract: This document describes techniques for detecting state loss on a device. These techniques permit a computer connected to a device to forgo, in many cases, reinitializing the device when returning to a normal-power mode.

Abstract: In embodiments of driver interface functions to interface client function drivers, a set of serial communication protocol driver interfaces are exposed by a core driver stack, and the serial communication protocol driver interfaces include driver interface functions to interface with client function drivers that correspond to client devices configured for data communication in accordance with the serial communication protocol. A client function driver can check for the availability of a driver interface function before interfacing with the core driver stack via the serial communication protocol driver interfaces. A contract version identifier can also be received from the client function driver via an extension of the driver interface functions, where the contract version identifier indicates a set of operation rules by which the client function driver interfaces with the core driver stack.

Abstract: In embodiments of extensions for USB driver interface functions, a set of USB driver interfaces are exposed by a USB core driver stack, and the USB driver interfaces include USB driver interface functions to interface with USB client function drivers that correspond to client USB devices. A composite device driver registers itself and requests a function handle for each function of a client USB device. The USB client function drivers are enumerated and the function handles generated for each function of the client USB device. A check first protocol is enforced that directs a USB client function driver to check for availability of a USB driver interface function before interfacing with the USB core driver stack via the USB driver interfaces. A contract version identifier is received that indicates a set of operation rules by which a USB client function driver interfaces with the USB core driver stack.

Abstract: Various embodiments relate to systems and methods that facilitate wireless device communications and configuration. A detection component identifies N devices that are coupled together via a biological medium, N being an integer, wherein the medium includes direct or indirect touching to a device or devices. After biological contact, a configuration component initiates a configuration between a subset of the devices.

Abstract: A computer system that recognizes multi-function devices and associates functions with multi-function devices. Each multi-function device may be represented by a multi-function object, allowing tools, applications or other components within the computer to take actions relating to the entire device or relating to a function based on the association of that function with other functions in the same device. These actions include displaying information about devices, instead of or in addition to information about functions. Actions also include selecting functions based on proximity within a device. Functions may be associated with a multi-function device using a unique device identifier provided by the device or generated for the function based on a connection hierarchy between functions and the computer. Devices may be configured to provide the same identifier regardless of the transport over which the device is accessed.

Abstract: Multi-function devices expose multiple functions to device drivers or other lower-level software. Device function providers can interface with such drivers or lower-level software and can provide information, including device identifiers regarding such functions, to a device display object infrastructure. A device display object can then be created that encompasses one or more functions such that, in one embodiment, the device display object corresponds to a single, physical multi-function device. Alternatively, any combination of functionality from one or more physical devices can be combined into a single device display object representing a virtual multi-function device. Properties of the device display object can be set with reference to user-specified settings, remotely maintained metadata, locally available metadata, and information associated with each function.

Abstract: In embodiments of extensions for USB driver interface functions, a set of USB driver interfaces are exposed by a USB core driver stack, and the USB driver interfaces include USB driver interface functions to interface with USB client function drivers that correspond to client USB devices. A composite device driver registers itself and requests a function handle for each function of a client USB device. The USB client function drivers are enumerated and the function handles generated for each function of the client USB device. A check first protocol is enforced that directs a USB client function driver to check for availability of a USB driver interface function before interfacing with the USB core driver stack via the USB driver interfaces. A contract version identifier is received that indicates a set of operation rules by which a USB client function driver interfaces with the USB core driver stack.

Abstract: Extensions for USB driver interface functions are described. In embodiments, input/output of computer instructions and data exchange is managed in a USB core driver stack. A set of USB driver interfaces are exposed by the USB core driver stack, and the USB driver interfaces include USB driver interface functions that interface with USB client function drivers that correspond to client USB devices. Extensions for the USB driver interface functions are also exposed by the USB core driver stack to interface with the USB client function drivers.

Abstract: This document describes techniques for detecting state loss on a device. These techniques permit a computer connected to a device to forgo, in many cases, reinitializing the device when returning to a normal-power mode.