Microsoft Technology Licensing, LLC

Firdosh Kersy Bhesania

Randall Edward Aull

Kenneth D Ray

Vivek Gupta

Glen T Slick

Andrea A Keating

John Charles Dunn

Hirofumi Yamamoto

Arvind R Aiyar

Mark E Maszak

Robert E Harris, Jr

Philip Albert Froese

Steven Nabil Bathiche

Doron J Holan

Timothy T Brewer

Michael William John McCracken

David Abzarian

Eliyas Yakub

Rahul Ramadas

Tommy T Nguyen

Robbie Harris

Anthony Yuting Chen

Martin Richard Borve

Stephane St Michel

Jayson L Kastens

Cong Yang

Ruston Panabaker

Alain L Michaud

Nathan C Sherman

Gary Rensberger

Marcus J Andrews

Ervin Peretz

Poovanpilli G Madhavan

Gerardo Bermudez

James E Veres

Christopher Mark Dreher

Om Sharma

Stephen Richard Drake

Jay Senior

Yashabh Sethi

Andrew C Glass

Peter E H Hauser

Bernard J Thompson

Paul E Henderson, Jr

Scott R Leatham

Gabriel J Aul

Pradipta Ariyo Bhaskoro Hendri

Bradley L Fosdick

Chih Jen Wen

Robert Ingman

Jason A Schroeder

Steve Wright

Ahmed Smahi

Di Da

Alain Michaud

Robert Harris

Embodiments described herein are directed to mechanisms that enable roles (e.g., host vs. function, power provider vs. power consumer, master vs. slave, server vs. client, source vs. sink, upstream vs. downstream) to be dynamically assigned between two interconnected dual-role devices in an intelligent and deterministic manner based on the available context on each device.

Intelligent role selection for dual-role devices

A peripheral device class identifier is generated for a class of peripheral devices, and is used to identify a setup record that indicates how to install or otherwise set up the class of peripheral devices on a computing device. The peripheral device class identifier is a combination of three components: a vendor identifier, a namespace identifier, and a namespace entry identifier. The vendor identifier is an identifier of the vendor of the class of peripheral devices. The namespace identifier is an identifier of different collections or groups of types of peripheral devices or types of functionality of peripheral devices. The namespace entry identifier is an identifier of a particular type of peripheral device (or particular functionality) of the different collections or groups of types of peripheral devices (or types of functionality of peripheral devices).

Vendor-specific peripheral device class identifiers

Enhanced display rotation techniques are described in which arrangement of on-screen elements and user interfaces may be controlled based upon a combination of inputs from a sensor system of a device indicative of positional relationships. Output positions for elements are controlled in dependence upon a calculated position of a user in relation to the device and alignment of the device with a magnetic direction. The position and alignment may be derived based on sensor data, including at least a camera to obtain eye tracking data and a compass used to determine an alignment of the device. Other factors may also be considered such as data from an accelerometer, facial tracking by the camera, gaze detection, a proximity sensor, and other sensor data. Responsive to manipulation of the device, rotation and/or location of the elements may be controlled in accordance with the positional relationships that are ascertained.

Enhanced Display Rotation

A universal serial bus stack may use an emulation layer to grant a non-universal serial bus device access to universal serial bus drivers and applications. The universal serial bus stack may exchange a device communication at an emulation layer. The universal serial bus stack may translate between a universal serial bus communication and the device communication at the emulation layer, and then may exchange the universal serial bus communication at a universal serial bus client interface.

Universal serial bus emulation layer

Systems and methods for specifying extended descriptor information in a device accessed using a communication interface are disclosed. One method includes transmitting a request to a device from a host computing system, and receiving an extended capability descriptor identifying to the host computing system at least one extended descriptor set stored on the device. The extended capability descriptor identifies a minimum operating system version able to support a corresponding extended descriptor set.

Extraction of operating system-specific characteristics via a communication interface

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 disclosed subject matter, 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.

Method for processing data quantifying force applied to one or more keys of a computer keyboard

An automated power reporting system is provided in one aspect. The system includes one or more devices that can report or transmit power status information over a bus or network. A protocol component utilizes a generalized protocol to process or convert the power status information over the network in order to facilitate power management operations for a plurality of devices. In this manner, devices that send power information can interact and exploit personal computing resources in order to better help users manage limited power resources for their respective devices.

Protocols for reporting power status over multiple buses

Computer-readable media, computerized methods, and computer systems for alerting a user that an operating system has entered a secure mode is provided. Initially, inputs are received at an operating system residing in a default mode. Typically, the default mode allows applications running on the operating system to access the inputs. If the inputs are identified as a call to perform a protected operation, the operating system is transitioned from the default mode to the secure mode. Typically, the secure mode restricts the applications from intercepting the inputs. The transition to the secure mode is automatically communicated to the user via an indicator device. Generally, automatic communication includes providing a message from the operating system to the indicator device over a secure pathway that triggers the indicator device to generate a user-perceivable output. Accordingly, the operating system exerts exclusive control over the operation of the indicator device.

User indicator signifying a secure mode

In embodiments of HID over simple peripheral buses, a peripheral sensor receives inputs from a peripheral device, and the peripheral sensor implements an HID SPB interface to interface the peripheral device with a computing system via a simple peripheral bus (SPB) in an HID data format. The peripheral sensor can also receive extensibility data for a proprietary function of the peripheral device, and communicate the inputs from the peripheral device and the extensibility data via the simple peripheral bus in the computing system. Alternatively or in addition, a peripheral sensor can generate sensor data and the HID SPB interface interfaces the peripheral sensor with the computing system via the simple peripheral bus. The peripheral sensor can then communicate the sensor data as well as extensibility data for a proprietary function of the peripheral sensor via the simple peripheral bus in the HID data format to the computing system.

HID over simple peripheral buses

In embodiments of host side implementation for HID IC data bus, a computing system includes a human interface device (HID) software stack that implements device software, such as for embedded devices, that interfaces the computing system to a peripheral device via HID over IC. An HID IC driver interfaces the HID software stack with the peripheral devices that each include an HID IC interface to a device that communicates data in the computing system via an IC data bus. The HID IC driver is compatible and interfaces with IC controller drivers and GPIO controller drivers of the devices, where the IC controller drivers and the GPIO controller drivers may each have a different implementation configuration.

[object Object]

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.

Growing community of inventors

Kirkland, WA, United States of America

Firdosh Kersy Bhesania