Abstract: In one embodiment, a notification server 110 may batch together notifications to reduce power consumption. A notification server 110 may receive a power consumption profile 430 from a client device 120. The notification server 110 may assign a notification batch schedule at a notification server 110 based on the power consumption profile 430.

Abstract: 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.

Abstract: In one embodiment, a notification server 110 may batch together notifications to reduce power consumption. A notification server 110 may receive a power consumption profile 430 from a client device 120. The notification server 110 may assign a notification batch schedule at a notification server 110 based on the power consumption profile 430.

Abstract: 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.

Abstract: Pre-installed application activation techniques are described in which live content for applications is activated before user interaction with the applications. Input indicative of an initial log-in of a user to access an operating system is detected. In response, configuration of an account for the user with the operating system may be initiated to set-up a device for first use by the user. During the configuration, notifications are activated through a notification system of the operating system to obtain live content for one or more pre-installed applications on the computing device. The activation occurs before interaction of the user with the pre-installed applications. Live content may then be incorporated with representations of the applications within a user interface for the operating system, such as displaying application tiles having corresponding live content in a start screen presented to the user after completion of the initial set-up.

Abstract: Applications on a computing device provide notifications associated with the application to a notification system. A notification includes an identification of content to be presented for the notification and an indication of when the content is to be presented. The notification system presents the notification content at the appropriate time regardless of whether the application is executing and without resuming execution of the application if the application is not running. Various power efficiency techniques are also used to determine which notifications are presented and when a user interface is updated to reflect those notifications in order to avoid updating the user interface to reflect notifications that would not be observable (e.g., due to a power mode of the computing device).

Abstract: A notification service receives messages including various data from application services, and provides notifications including that data to the appropriate computing devices. Each computing device includes a notification system that receives notifications from the notification service and provides those notifications to the appropriate applications on the computing device. If an application is not allowed to run on a computing device, the notification system on the computing device provides an indication to the notification service to block notifications for the application on the computing device. The notification service ceases providing notifications to a computing device targeting applications for which notifications are blocked on the computing device until an indication is received from the computing device to unblock notifications for the application.

Abstract: 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.

Abstract: Various embodiments provide a user interface that displays a history of resource usage of a computing device's applications over time. Historical resource usage data can be presented in a manner which informs the user, on an application-by-application basis, of each application's resource usage across a plurality of resources. In at least some embodiments, the user interface can provide one or more instrumentalities that enable the user to interact with and/or modify operational characteristics of various applications based upon the presented historical resource usage data.

Abstract: In one embodiment, a notification server 110 may batch together notifications to reduce power consumption. A notification server 110 may receive a power consumption profile 430 from a client device 120. The notification server 110 may assign a notification batch schedule at a notification server 110 based on the power consumption profile 430.

Abstract: 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.

Abstract: 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.

Abstract: Application notification tag 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.

Abstract: Described herein are various principles for assisting in the identification of a configuration of computing device and reconfiguration of the computing device. More particularly, some of the principles relate to identifying one or more software processes configured to be executed during operation of the computing device in a usage scenario. Following operation of the computing device in the usage scenario, amounts of one or more resources consumed by each of the software processes throughout the usage scenario may also be identified. In some embodiments, once the software processes and amounts of the resource(s) consumed by the software processes have been identified, the processes and the amounts can be displayed to a user and the user may then reconfigure the computing device, such as by preventing some software processes from executing during the usage scenario or by delaying an execution of some software processes.

Abstract: 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.

Abstract: 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.