Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Microsoft Corporation

Kiraly, Kenneth Paul

Awad, Nadim

Keljo, Jonathan White

Dolbakian, Levon

Froment, Arnaud Marie

Dumont, Michael David

Sridharan, Srinivasan

Jonathan White Keljo

Kenneth Paul Kiraly

Arnaud Marie Froment

Nadim Awad

Srinivasan Sridharan

Levon Dolbakian

Michael David Dumont

Sean Selitrennikoff

David Michael Broman

Hsu-chieh Yuan

Vance Palmer Morrison

Charles W Kaufman

Samuel Scott Gigliotti

Jason George McHugh

Michael M Magruder

Abraham Martin Passaglia

Brian D Harry

Kinshumann Kinshumann

Matthew E Goldberg

Richard Byers

Shrikrishna Vijaykumar Borde

Ian H Carmichael

Omar Abdul Baki

Varun Bahl

Cristian G Petruta

Levon Dolbakain

Benjamin L Sauer

A system and method for identifying a user of a device includes comparing audio received by a device with acoustic fingerprint information to identify a user of the device. Image data, video data and other data may also be used in the identification of the user. Once the user is identified, operation of the device may be customized based on the user. Further, once the user is identified, data can be associated with the user, for example, usage data, location data, gender data, age data, dominant hand data of the user, and other data. This data can then be used to further customize the operation of the device to the specific user.

Systems and methods for identifying users of devices and customizing devices to users

Described herein are systems, devices and methods for presenting content based on the spatial relationship between a media device and a user of the media device. The media device may present content based on an angle between an eye axis of the user and a device axis of the media device.

Content orientation based on a user orientation

A settings service running on a server remote from a computing device can identify at least one settings group to which the computing device belongs. The settings service can identify all settings that are included in the at least one settings group to which the device belongs. The settings service can compare all the settings and detect any conflicting settings. If there are conflicting settings, the service can choose which of the conflicting settings takes priority, in order to resolve the conflict. For example, a default setting can be overridden by a setting with a higher priority. After resolving the conflict, the settings service can merge the conflicting setting(s) which takes priority, as well as the non-conflicting settings, into a single set of settings to be applied to the device. The settings service can transmit the set of settings to the computing device to be applied.

Remote management of device settings

Users may access a variety of content in many locations. Described herein are systems, devices and methods for introducing users that are in close proximity to one another. Historical location data of the media devices, data indicating content usage on the media devices, or a combination of the two is used to determine a correspondence between two or more users. Once the correspondence has been determined, an introduction may be provided.

Introduction based on location and content usage data

Techniques are described for determining height, weight, or other characteristics of a user based on processed sensor data. The sensor data may include data collected by sensors on the user's computing device or other computing devices, or data collected by stationary, external sensors. Different types of sensor data may be processed to estimate at least one physical characteristic of the user, such as the user's height, weight, apparel size, age, and so forth. The estimated characteristics may be employed to perform actions based on the user's identity or category, to customize content delivery for the user, or for other purposes.

Employing device sensor data to determine user characteristics

Approaches to enable a computing device, such as a phone or tablet computer, to compute a probability that the user currently using the device matches a profile of an authorized user and to set or change a security level of the computing device based on the computed probability. The security level can be one of many security levels each having a different scope of authorized access to data or functions of the computing device. The computing device may periodically re-compute the probability and change the security level whenever the probability crosses certain predefined thresholds.

Controlling access based on recognition of a user

In some examples, an electronic device may include one or more recognition devices able to be used to recognize a current user. If the electronic device recognizes that a primary user, such as an owner, is currently using the electronic device, the electronic device may allow access to all of the primary user's private information and all of the features of the electronic device. On the other hand, when the electronic device determines that the current user is an unknown user, or that the current user is a known user who is authorized to access only limited information or features of the electronic device, the electronic device may send a communication to restrict the current user from accessing private information of the primary user. In some cases, the electronic device may enable the primary user to designate which items known users and/or unknown users may access.

Privacy control based on user recognition

Content is presented by media devices to a user. Described herein are techniques and systems for determining occurrence of one or more events at, or proximate to, the media device. Once an event is determined, one or more actions to modify presentation of the content may be initiated. The actions may include starting presentation of the content, stopping presentation of the content, applying noise mitigation techniques to the content, and so forth. The noise mitigation techniques may include modification of an intended signal from the content to produce a noise mitigation zoneproximate to, or encompassing, at least a portion of the user's head.

Event-based presentation and processing of content

Content orientation based on user orientation

Systems and approaches are provided for automating privacy control for a computing device based on a privacy or security context of the device. The privacy or security context of the computing device can be determined by analyzing sensor data or other input data captured by the device. The sensor and other input data can provide information such as a location of the computing device or the presence of other persons within the vicinity of the device to indicate whether the user is situated within a private or secure setting or a public or unsecure setting. A privacy or security control can be updated based on the determined privacy or security context, such as modifying a manner of displaying a pin or password during entry, elements of a home screen of the computing device, or preview content of user applications.

Automated privacy control

In some implementations, in response to receiving a request message from a client device, a computing device may provide a response message that includes a custom or non-standard control header. The control header may instruct the client device to wait before sending any subsequent request messages to the computing device. For example, the control header may inform the client device to wait until passage of period of time or until after a specified time arrives before sending a subsequent request message. A module, an application, an operating system, or other software on the client device that receives the response message, interprets the control header and performs one or more operations to comply with the control header. Accordingly, some implementations herein utilize message headers to perform message throttling for controlling an amount of network traffic or load on one or more computing devices.

Controlling requests through message headers

A profiler may be detached from an actively running application by first sealing communications between the application and profiler, then evacuating the profiler by waiting for any profiler-modified or instrumented code to complete execution, profiler runtime code to complete execution, cleaning up any residual items from the profiler, and shutting down the profiler. The profiler may be operational in many different environments, including a managed environment such as a virtual machine and those environments having just in time compiling of executable code.

Detaching profilers

Systems and methods are provided for presenting reflow objects of content on an output medium. In some embodiments, the content to be presented may be determined by rendering one or more reflow objects of content to an image file, the image file having a horizontal dimension that approximates the horizontal dimension of the output medium and a vertical dimension that exceeds the vertical dimension of the output medium, and causing a portion of the image file to be presented on the output medium, wherein the portion of the image file presented corresponds to a view window logically superimposed upon the image file. A request for content that is not within the view window may be received, the location of the view window may be adjusted based on the request, and the adjustment may result in changing the portion of the image file presented on the display.

Systems and methods for presenting reflowable content on a display

An error reporting system within the operating system of a computer that provides error reporting and/or debugging for managed applications. The error reporting service supports a registration programming interface through which applications that use non-native or non-standard error reporting functions can register runtime exception modules. A similar interface may be provided for applications to register debuggers. In response to a failure, such as a crash or an application hang, the error reporting service can poll the registered components to ascertain whether any is adapted for use in conjunction with such a failure. If so, the appropriate registered components can be used to collect failure data and/or debug the failed application. In this way, the error reporting service, and an existing framework that supports aggregation of application error reports, can be customized, including to allow error reporting and debugging of non-native applications.

Growing community of inventors

Seattle, WA, United States of America

Jonathan White Keljo