Microsoft Technology Licensing, LLC

Matthew Robert Ayers

Gaurav S Anand

Kevin Michael Woley

George Joy

Darren Louie

Rajeev Dutt

Eric Fleischman

Anshul Rawat

Relja Ivanovic

Jeroen Vanturennout

Tyler Joseph Donahue

Kandarp Jani

Mohammad Saifur Rahman

Benjamin D L Stewart

Donovan P Regan

Brian K McNeil

Sachin Jagadish Patil

Basel Abdus Salam

Cenk Ergan

Michael Richard Fortin

Robert P Fitzgerald

Eliot Carleton Gillum

Alexander Kirshenbaum

Hakki Tunc Bostanci

Michael H Krause

Ravikant Cherukuri

Charles T Lenzmeier

Yosef Firstenberg

Aaron Edward Dietrich

Cheuk Wan William Lau

Alex Bendetov

Robert Edgar Fanfant

Haseeb Ahmed

Zoran Dimov

Application notification techniques are described. Implementations are described in which a representation of an application may include notifications that pertain to the application. Techniques are further described which may be used to manage the notifications, including replacement of notifications, use of queues, overrides, selection of notifications based on execution state of an application, cycling a display of a plurality of notifications, cycling a display of different subsets of notifications, examination of a manifest of an application to determine criteria to be used to display the notifications, display priority of the notifications, and so on.

Application notifications manifest

Various embodiments provide session-based filtering to filter messages in a cooperative manner between a client and a service provider. In at least some embodiments, a service provider can establish a messaging session with a client and deliver messages to the client. The client can implement various client-side techniques to filter some of the messages based on various client designated criteria. The service provider can obtain feedback from the client indicative of one or more of the delivered messages that have been filtered. The service provider can dynamically create a session-based list based on the feedback and use the list during the session to block messages on the server-side according to the client designated criteria. When the session concludes, the session-based list can be discarded. In this manner, message filtering can occur without persistent storage of state data for the filtering at the service provider.

Cooperative session-based filtering

This document describes various techniques for distributing credentials based on hardware profiles. A resource access request including a hardware profile is transmitted to a remote entity having access to a previous hardware profile and a credential useful to access a resource is received if at least a portion of the hardware profile matches the previous hardware profile.

Hardware-based credential distribution

Stateless application notifications are described that enable third parties to provide messages to client applications. A communication channel can be established between a notification service and an application. Upon request, the notification service can generate obfuscated routing data for the channel, which can be in the form of a channel handle or token. The routing data can be encrypted and digitally signed to obscure the content and format of the routing data from third parties. An application service possessing the obfuscated routing data can package a notification with the data and send the package to the notification service for delivery. The application service does so without knowing the channel particulars encoded by the obfuscated routing data. The notification service that produces the obfuscated routing data can decrypt and interpret the data, and deliver the notification on the channel to an appropriate endpoint application on behalf of the application service.

Stateless application notifications

Various embodiments enable automatic cooperative logging of information associated with a connection between at least two computing devices. In some cases, a first computing device can automatically trigger logging on a second computing device upon detection of at least one scenario. Alternately or additionally, the second computing device can respond to the first computing device with additional and/or supplemental logging requests.

Cooperative client and server logging

A service accessible by a set of entities may be provided to each entity at a different service level (e.g., with a different set of privileges) based on the privilege level of the entity. However, many users may attempt to perform malicious activities through the service, and may do so with impunity if the penalties of detection are inconsequential. Instead, privilege levels of entities may be established based on the claims of assets having identifiable value. Such claims may be established by submitting an asset identifier to the service, such as proof of a software license identified by the submission of a license key purchased at a substantial cost. The penalties of malicious activities performed by such users may include the invalidation of such asset identifiers. Establishing the privilege levels of respective entities in this manner raises the penalties, and hence the deterrence, of attempted malicious use of the service.

Establishing privileges through claims of valuable assets

Application notifications

Modern application tracing techniques are described herein that enable dynamic logging of events declared in a static manifest. Various events for logging can be declared in a static manifest. The static manifest may then be compiled to translate the declared events into a library of corresponding functions that can be called by 'modern' applications written using dynamic code. Calls made to these functions from dynamic code are converted to corresponding static events and forwarded to existing tracing application programming interfaces (APIs) designed to handle logging of static events for 'legacy' applications that use compiled code. In this manner, static functions that are compatible with tracing APIs can be created and called dynamically from dynamic code. This can occur without requiring administrative rights to install the code and while preserving existing features for legacy applications, such that a tracing log can include events from both modern applications and legacy applications.

Modern application tracing

Increased efficiency in booting a computer uses a process of logging physical-level disk access during a boot cycle for use in creating a boot plan for a subsequent boot. Processing the log from one or more previous boots removes unnecessary reads such as those associated with temporary files and then orders the remaining read accesses based on times of prior read accesses and and by physical location on the disk. Upon boot, data likely to be requested first orders the remaining read accesses based on times of prior read accesses and By taking advantage of disk head and platter characteristics, data is read in sweeps through the disk, reducing overall latency. Requests that are not in cache may be held if the data is already scheduled for retrieval.

Accelerated system boot

Growing community of inventors

Seattle, WA, United States of America

Matthew Robert Ayers