Microsoft Technology Licensing, LLC

Nimesh I Amin

Akhilesh Kaza

Lucia Darsa

Randal James Ramig

Gunjan A Shah

Shawn T Oster

Jonathan D Sheller

Eric Bie

Tony Seeley

Vishal Vikram Ghotge

Keith Stuart Kaplan

Thomas Walter Getzinger

Syed Mansoor Jafry

Andrew Dadi

Shawn Patrick Henry

Fabian Toader

Robert Charles Aldinger

Alan C T Liu

Akhil Kaza

Vij Vasu

Steve Serdy

Neeraj Sharma

Alan Ct Liu

Alan Chun Tung Liu

A runtime management system is described herein that allows a hosting layer to dynamically control an underlying runtime to selectively turn on and off various subsystems of the runtime to save power and extend battery life of devices on which the system operates. The hosting layer has information about usage of the runtime that is not available within the runtime, and can do a more effective job of disabling parts of the runtime that will not be needed without negatively affecting application performance or device responsiveness. The runtime management system includes a protocol of communication between arbitrary hosts and underlying platforms to expose a set of options to allow the host to selectively turn parts of a runtime on and off depending on varying environmental pressures. Thus, the runtime management system provides more effective use of potentially scarce power resources available on mobile platforms.

Controlling runtime execution from a host to conserve resources

A computer-implemented system is provided that facilitates implementation of a voice over IP (VOIP) application. The system includes a host system and a user interface (UI) host process residing on the host system. The system also includes an agent host process residing on the host system which is being configured to process a VOIP call received by one or more VOIP applications executable on the host system. The agent host process running as a foreground or background process for the duration of the VOIP call to (i) communicate with a VOIP server associated with the VOIP application, (ii) capture content from at least one input device associated with the host system and (iii) render content on an output device associated with the host system when an instance of the UI host process operates in the foreground.

Voice-over-internet protocol (VOIP) application platform

A computer-implemented system is provided that facilitates implementation of a voice-over-IP (VOIP) application. The system includes a host system and a user interface (UI) host process residing on the host system. The system also includes an agent host process residing on the host system which is being configured to process a VOIP call received by one or more VOIP applications executable on the host system. A moniker protocol is utilized for redirection of input and output between a media element which is utilized to render media on a display on the system. The redirection enables media processing to be allocated between the UI host process in the foreground and the agent host process in the background to thereby reduce latency perceived by a user during a VOIP experience.

Cross-process media handling in a voice-over-internet protocol (VOIP) application platform

A central manager receives tick subscription requests from subscribers, including a requested period and an allowable variance. The manager selects a group period for a group of requests, based on requested period(s) and allowable variance(s). In some cases, the group period is not a divisor of every requested period but nonetheless provides at least one tick within the allowable variance of each requested period. Ticks may be issued by invoking a callback function. Ticks may be issued in a priority order based on the subscriber's category, e.g., whether it is a user-interface process. An application platform may send a tick subscription request on behalf of an application process, e.g., a mobile device platform may submit subscription requests for processes which execute on a mobile computing device. Tick subscription requests may be sent during application execution, e.g., while the application's user interface is being built or modified.

Subscriber-based ticking model for platforms

In a low-power device a runtime hands video capture and other markup language video objects to a video service, which renders them onto a shared surface. An application-specific compositor manipulates the shared surface, e.g., by texture wrapping or animation. A system compositor composites the manipulated shared surface with other data, such as rendered frames from other application-specific compositors and/or computer generated text. The device then displays the attendant rendered, manipulated, and composited video frames. In some cases, only a single copy of the shared surface is utilized. When the video object's shape, alignment, and opacity satisfy predetermined criteria, the video service renders the video object onto the shared surface using a hardware scaler; otherwise, rendering is done without using the hardware scaler.

Shared surface hardware-sensitive composited video

Growing community of inventors

Seattle, WA, United States of America

Nimesh I Amin