Abstract: A remote power management system and method for awakening a remote computing device over a computer network. A wakeup event is initiated by a client on the network, and an application server publishes the wakeup event. A subscriber, such as the subnet where the remote computing device resides, picks up the wakeup event and gives it to a computing device on the subnet that is awake. The awake computing device constructs a “magic packet” to take advantage of the automatic wakeup feature of the network card on the remote computing device, and broadcasts the “magic packet” throughout the subnet. Stateless handling of wakeup events is used to alleviate any need for a dedicated proxy server on the subnet to send the “magic packets.” The computing device on the subnet that constructs and broadcasts the “magic packets” is rotated to provide equitable rest time for each of the computing devices.

Abstract: A remote power management system and method for awakening a remote computing device over a computer network. A wakeup event is initiated by a client on the network, and an application server publishes the wakeup event. A subscriber, such as the subnet where the remote computing device resides, picks up the wakeup event and gives it to a computing device on the subnet that is awake. The awake computing device constructs a “magic packet” to take advantage of the automatic wakeup feature of the network card on the remote computing device, and broadcasts the “magic packet” throughout the subnet. Stateless handling of wakeup events is used to alleviate any need for a dedicated proxy server on the subnet to send the “magic packets.” The computing device on the subnet that constructs and broadcasts the “magic packets” is rotated to provide equitable rest time for each of the computing devices.

Abstract: A data service that manages user and subscription data for multiple services. The data service maintains a database of the user and subscription data and provides an interface that allows the other services, that act as clients to the data service, to access that data. The data service avoids the need for the client services to implement a framework to manage the storage of user and subscription data. The data service also allows user profile data to be updated by one client service and used by all others. Further, data, such as usage history or information on policy violations, may be shared by multiple services.