Abstract: Wireless devices that support bootstrapping of a peer-to-peer connection. The wireless devices may use an infrastructure mode connection to exchange security information, such as a PIN, used in establishing the peer-to-peer connection. This security information may be encrypted in accordance with a security protocol used by the access point and then may be applied in a security protocol used to establish a peer-to-peer connection. Such a bootstrapping capability supports operating scenarios in which devices that are communicating over an infrastructure network encounter an operation that requires transfer of large amounts of data and automatically transition to a peer-to-peer connection that provides better performance. With these techniques, a computing device may automatically connect to a display device and stream audio/video data to the display.

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 wireless device that discovers other wireless devices for the formation of a peer-to-peer connection may perform a scan that is limited in duration and power consumption. The scan nonetheless is highly likely to discover a device, if a discoverable device exists. In addition, the scan may be performed in compliance with parameters of a peer-to-protocol such that the scan may be readily implemented in a wireless device, in some embodiments even as a firmware upgrade on a wireless network interface card. Parameters of the scan may be adjusted to increase the likelihood that, if the scan completes without discovering a device, no discoverable device exists. The scan may be used in an overall process in which discovery ends or the scan is selectively repeated following an unsuccessful scan, without entering a find phase.

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: Techniques for detecting presence of a remote device at Layer 2 in response to an indication of an attempt to use the device and without maintaining a Layer 3 connection to the device. The techniques allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection to the remote device to provide services to a user. The Layer 3 connection and underlying Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated when the Layer 3 connection is not actively used. Once use of the remote device is desired, its presence may be detected using a Layer 2 device discovery mechanism and the Layer 2 and Layer 3 connections to the device may be reestablished. Services provided at Layer 3, such as steaming data, may then be performed over the reestablished Layer 3 connection.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Resource management architectures implemented in computer systems to manage resources are described. In one embodiment, a general architecture includes a resource manager and multiple resource providers that support one or more resource consumers such as a system component or application. Each provider is associated with a resource and acts as the manager for the resource when interfacing with the resource manager. The resource manager arbitrates access to the resources provided by the resource providers on behalf of the consumers. A policy manager sets various policies that are used by the resource manager to allocate resources. A resource consumer creates an “activity” at the resource manager and builds one or more “configurations” that describe various sets of preferred resources required to perform the activity. Each resource consumer can specify one or more configurations for each activity.

Abstract: Wireless devices that support bootstrapping of a peer-to-peer connection. The wireless devices may use an infrastructure mode connection to exchange security information, such as a PIN, used in establishing the peer-to-peer connection. This security information may be encrypted in accordance with a security protocol used by the access point and then may be applied in a security protocol used to establish a peer-to-peer connection. Such a bootstrapping capability supports operating scenarios in which devices that are communicating over an infrastructure network encounter an operation that requires transfer of large amounts of data and automatically transition to a peer-to-peer connection that provides better performance. With these techniques, a computing device may automatically connect to a display device and stream audio/video data to the display.

Abstract: A wireless device that automatically forms a connection to a remote device in accordance with a peer-to-peer protocol. The remote device may be designated as an auto-connect device for the wireless device such that, when the wireless device determines that it is in the vicinity of the auto-connect device, it can re-form a connection to the remote device based on stored information for re-establishing connections among a persistent group of devices, but without any express user input. When a user requests that the wireless device perform a function that involves interaction with an auto-connect device, that function may be performed with the delay associated with forming a connection. Any of multiple techniques may be employed for identifying devices designated as auto-connect devices and for determining when the wireless device and a remote, auto-connect devices are in close proximity.

Abstract: A wireless device that automatically forms a connection to a remote device in accordance with a peer-to-peer protocol. The remote device may be designated as an auto-connect device for the wireless device such that, when the wireless device determines that it is in the vicinity of the auto-connect device, it can re-form a connection to the remote device based on stored information for re-establishing connections among a persistent group of devices, but without any express user input. When a user requests that the wireless device perform a function that involves interaction with an auto-connect device, that function may be performed with the delay associated with forming a connection. Any of multiple techniques may be employed for identifying devices designated as auto-connect devices and for determining when the wireless device and a remote, auto-connect devices are in close proximity.

Abstract: A system in which wireless devices form a group in accordance with a peer-to-peer protocol and, at a later time, a device may send an invitation request to trigger the devices tore-form the peer-to-peer group. The invitation request may contain an identifier that is associated with a set of a plurality of devices. Those devices may be related such that they perform a function for which a user would want to use those devices together. The group of devices, for example, may be multimedia devices that receive and present streaming multimedia content or may be human interface devices that collectively act as an interface for a work station incorporating a wireless computing device operated by a user. Requesting that remote devices concurrently re-form a group reduces the time and spectral congestion associated with re-forming the group, particularly when the remote devices may periodically enter a low power state.

Abstract: A computing device that forms a group in accordance with a peer-to-peer protocol in which a device may be identified based on a credential of a user. The credential may be used to determine a unique identifier for the user such that the same identifier is used on any device operated by the same user. Such an identifier may be used in connection with a peer-to-peer protocol that supports persistent peer-to-peer groups. As a result, the unique identifier for the user may be retained by remote devices that have paired with any device operated by a particular user such that those remote devices may automatically establish a connection with any other device operated by the same user that similarly uses the same unique identifier for the user.

Abstract: A computing device that selectively renegotiates roles of devices in an existing peer-to-peer group. As the group is formed, the device may negotiate with other devices to select a device to control the group. During operation of the group, a device in the group may initiate a renegotiation that may lead to the selection of an alternative device to control the group. Renegotiation may be triggered by a message containing an information element signifying a request for renegotiation. Such a message may be sent either by the controlling device or other device in the group, and may be sent based on a state of the device. The state may relate to a source of power to the device such that a client that is connected to a source of power or a controlling device that is running low on battery power may request a renegotiation.

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: A wireless peer-to-peer protocol that supports fast and low power joining to an existing group. The protocol may be an extension of a peer-to-peer protocol that supports a sleep state for a device controlling the group. When a device is seeking to join a group at a time when the controlling device is in a sleep state, another device that has information about the controlling device may provide information to the joining device that may then be used by the joining device to more quickly, and using less power, synchronize with the controlling device. The information may include information about a channel used by the controlling device or about timing of availability of the controlling device. The information may also reveal whether the group provides a service being sought by the joining device or may otherwise influence whether the joining device will attempt to join a group.

Abstract: An architecture for a computing device to enable the computing device to support peer-to-peer communications using a wireless radio also configured for infrastructure-based communication. The architecture includes a driver for the wireless radio that supports ports for communication in accordance with the peer-to-peer protocol. A port may act as a control port through which action frames that control the formation of a peer-to-peer group may be sent and received. One or more other ports may be used for exchanging data with other devices in the group. Each of these ports may be configured in accordance with its role in the group, such that each port may be configured for operation as a group owner or a client. Additionally, after establishing a group, the control port may be used as a side channel for controlling a device in a group associated with another port.

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: 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: Resource management architectures implemented in computer systems to manage resources are described. In one embodiment, a general architecture includes a resource manager and multiple resource providers that support one or more resource consumers such as a system component or application. Each provider is associated with a resource and acts as the manager for the resource when interfacing with the resource manager. The resource manager arbitrates access to the resources provided by the resource providers on behalf of the consumers. A policy manager sets various policies that are used by the resource manager to allocate resources. One policy is a priority-based policy that distinguishes among which applications and/or users have priority over others to use the resources. A resource consumer creates an “activity” at the resource manager and builds one or more “configurations” that describe various sets of preferred resources required to perform the activity.

Abstract: A user-mode device driver architecture is provided by the subject invention. The architecture includes a reflector, a driver manager and a host process which hosts and isolates one or more user-mode device driver(s). The user-mode device driver runs in the user-mode (UM) environment and has access to various UM services. The reflector resides in “kernel memory” (e.g., memory/resource(s) available to operating system) while the driver manager, host process and user mode device driver(s) are located in user space (e.g., memory/resource(s) available to user application(s)). The reflector provides a secure, stable communication path for application(s), the host process and/or user-mode device driver(s) to communicate with the operating system.