Microsoft Technology Licensing, LLC

Brian David Cross

Jan H Karachale

Robert J Levy

Zeke Koch

Ori Amiga

Jason William Fuller

Ardan Arac

Darren Ray Davis

Ramrajprabu Balasubramanian

Patrick Joseph Derks

William Scott Stauber

Kenton Allen Shipley

Aman Kansal

Scott Randall Shell

Ryan Pendlay

Issa Yousef Khoury

Petteri Mikkola

Elizabeth Fay Threlkeld

Keri Kruse Moran

Michael E Markley

Nishad Mulye

Giorgio Francesco Sega

Paul Dykstra

Jeffrey D Glaum

Mohammed Kaleemur Rahman

Nathan T Radebaugh

Gerardo Garcia

Lorna Rebecca McNeill

Jan Harold Karachale

Ryan Chandler Pendlay

A system for generating a user interface described herein can include a processor to detect a type of the system based on hardware components residing within the system or coupled to the system and determine a user interface manager to execute based on the type of the system. The processor can also execute the user interface manager to generate a user interface for the system, wherein the type of the user interface manager comprises a plurality of rules to indicate a layout of the user interface.

Rules based user interface generation

In many computing scenarios, a user of a primary device may wish to incorporate an auxiliary device in the presentation of an application. Such incorporation may involve a terminal services session that projects the computing environment of the primary device onto the auxiliary device; mirroring the computing environment of the primary device through the auxiliary device; and/or utilizing applications that interoperate with client applications executing on the second device. However, such techniques may not fully reflect the properties of each device, and/or may only apply to particular applications and/or configurations. Instead, the primary device may adapt the primary computing environment to an auxiliary computing environment according to a device property of the auxiliary device; partition the application into a primary application portion presented within the primary computing environment and an auxiliary application portion presented within the auxiliary computing environment; and transmit the auxiliary computing environment to the auxiliary device.

Partitioned application presentation across devices

A unified mechanism for storing device, application, and service state, as well as a rich notification brokerage architecture includes a notification broker. Clients register with the notification broker to receive notifications for changes to state properties. When a registered state property changes, a notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change. Clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule. An application may also be launched in response to a state change. An application programming interface (API) is provided that provides a unified way of accessing state change information across different components within the device.

Flexible architecture for notifying applications of state changes

In a device, one or more low energy sensors are used to determine a mobility state of the device. Based on both the mobility state of the device and one or more places of interest for the device, a determination is made as to when to use a high energy sensor to determine a location of the device. One of the one or more places of interest for the device within which the device is located at any particular time can be determined based on the mobility state of the device and/or the location of the device as determined by the high energy sensor.

Energy efficient location detection

Described is a method and system a unified mechanism for storing device, application, and service state, as well as a rich notification brokerage architecture. Clients register with a notification broker to receive notifications for changes to state properties. When a registered state property changes, a notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change. Clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule. An application may also be launched in response to a state change. An application programming interface (API) is provided that provides a unified way of accessing state change information across different components within the device.

Described is a system and method in which software images including updates are provided as packages. The package is self-describing, thereby facilitating the replacement of only component parts of an image. A software build process maps operating system features (comprising files, metadata, configuration information and so forth) into the packages, and executable code is processed for relocation purposes. The final package includes a device manifest file that describes the package and conveys dependency information and information about the priority of settings (shadow data).

Self-describing software image update components

Growing community of inventors

Seattle, WA, United States of America

Brian David Cross