Microsoft Technology Licensing, LLC

Doron J Holan

Randall Edward Aull

Kenneth D Ray

Jacob Kappeler Oshins

Louis J Giliberto

Mukund Sankaranarayan

James George Cavalaris

Narayanan Ganapathy

Christopher Mark Dreher

Om Sharma

Viraf Rusi Gandhi

Andrew C Glass

Husni Roukbi

Craig Steven Ranta

Firdosh Kersy Bhesania

Esaias Engelbertus Greeff

Douglas Keith Brubacher

Eliyas Yakub

Ellick H Sung

Joseph M Joy

William Michael Zintel

Janet Lynn Schneider

Stanley William Adermann

Samuel David Adams

Mark D Bertoglio

Benjamin Scott McGregor

Kumar Rajeev

Jay Senior

Siamak Poursabahian

Eirik Herskedal

Zachary Allan Lockard

Reed L Townsend

Steven P Dodge

Bryan Douglas Scott

David A Roberts

Garret Buban

Gary Rensberger

Robert D Young

John Charles Dunn

Marcus J Andrews

Olumuyiwa M Durojaiye

Michael H Tsang

Hirofumi Yamamoto

Ervin Peretz

Gerardo Bermudez

Paresh J Maisuria

Noel Richard Cross

James E Veres

Stephen Clifford Cooper

Anand Ganesh

Peter E H Hauser

Bernard J Thompson

Bradley L Carpenter

Neil Sandlin

Joseph G Souza

Scott R Leatham

Brien Roell

Dennis Ming-Shu Lee

Bradley L Fosdick

Chih Jen Wen

Robert Ingman

Jason A Schroeder

Matthew John Montera

David V Skyberg

Interfaces are provided for receiving software development kit runtime binaries configured for a standardized platform; receiving a driver framework package that is generated based on the software development kit and configured to enable extensibility under a set of constraints; and interacting with first party frameworks and allowing third party frameworks to access the software development kit runtime binaries and allow applications to use the third party frameworks.

Extensibility of unified platform

Methods and devices for selecting an application for download for use with hardware on a computer device may include receiving, from a remote application store, application metadata that includes at least one hardware constraint for an application in response to an application request for installation of the application. The methods and devices may include evaluating the application metadata to determine whether the at least one hardware constraint is satisfied on the computer device. The methods and devices may include installing the application when the at least one hardware constraint is satisfied on the computer device.

Maintaining tight coupling between driver and application versions

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.

Associating hardware to store applications

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.

Detecting state loss on a device

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.

Driver interface functions to interface client function drivers

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.

Multi-function device ID with unique identifier

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.

Generalized architecture to support representation of multi-transport devices

A system, device, and method for virtually connecting a media device to a computing device are disclosed. One embodiment comprises a method to operate a virtual media device in a computing device, wherein the virtual media device that is controlled by a remote media device. In this manner, a computing device may stream media data to and from the remote media device.

Virtual media device

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.

USB driver interface functions to interface USB client function drivers

The present invention provides a unified layer for Plug and Play (PnP) components and power management components while relieving device drivers from system-level complexities associated with implementing PnP and/or power management functionality. The layer operates at a level between low-level device drivers and more complex operating system tasks. The subject invention simplifies designing device drivers having proper power management support by creating an infrastructure that allows a device driver to operate within a driver framework or model and without having to process Plug-and-Play or Power Management I/O Request Packets (IRPs) directly.

Interlocked plug and play with power management for operating systems

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.

Capacitive bonding of devices

Growing community of inventors

Seattle, WA, United States of America

Doron J Holan