# US 2015/0106639 A1 · Platform and processor power management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0106639 A1
- Document ID: US20150106639A1
- Status: Published application
- Kind: A1
- Application number: 14/521,170
- Filed: 2014-10-22
- Published: 2015-04-16
- Earliest claimed: 2008-12-31
- Assignees: Intel Corporation
- Inventors: Ren Wang; Christian Mociocco; Sanjay Bakshi; Tsung-Yuan Charles Tai
- Web page: https://patentgrep.com/patent/US20150106639A1

## CPC

- G06F 1/3287: by switching off individual functional units in the computer system
- G06F 1/3203: Power management, i.e. event-based initiation of a power-saving mode
- G06F 1/329: by task scheduling
- G06F 9/4418: {Suspend and resume; Hibernate and awake}
- G06F 1/3209: Monitoring remote activity, e.g. over telephone lines or network connections
- G06F 1/3215: Monitoring of peripheral devices
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- Y02D 30/50: in wire-line communication networks, e.g. low power modes or reduced link rate
- Y02D 30/70: in wireless communication networks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

The present invention relates to platform power management.

## Claims

### Claim at position 1

-14. (canceled)

### Claim 15

A computer-implemented method, comprising:
receiving registration information from one or more applications;
notifying an operating system executing on a computer of an expected period of quietness or an expected idle duration;
holding incoming traffic during the expected period of quietness or expected idle duration;
determining whether one or more application timers have expired; and
synchronizing outgoing network requests from the computer for the one or more applications based on the determination that the one or more application timers have expired.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15, the registration information comprising one or more of message frequency and timing requirements including allowable jitter, network keep-alive, periodic, or outgoing network communications for the one or more applications.

### Claim 17 (depends on 15)

The computer-implemented method of claim 15, the one or more applications comprising applications having non-critical outgoing message deadlines or engaging in periodic network activity.

### Claim 18 (depends on 15)

The computer-implemented method of claim 15, comprising:
running the synchronized outgoing network requests expected to be run within the next period of quietness or next idle duration before the next period of quietness or next idle duration.

### Claim 19 (depends on 15)

The computer-implemented method of claim 15, comprising:
predicting the expected period of quietness or expected idle duration based on one or more of information from one or more peripheral devices and adaptive estimation including heuristic idle durations.

### Claim 20 (depends on 15)

The computer-implemented method of claim 15, comprising:
receiving a task from one or more of the one or more applications;
determining if the task can be put off for at least a break even duration;
delaying servicing of the task if the task can be put off for the break even duration and if the one or more application timers have not expired.

### Claim 21 (depends on 15)

The computer-implemented method of claim 15, comprising:
determining whether one or more periodic application timers have expired, the one or more periodic application timers to include an indication of one or more application with keep-alive messages; and
servicing one or more tasks from the one or more applications with keep-alive messages based on the determination that the one or more periodic application timers have expired.

### Claim 22

An article comprising a non-transitory computer readable storage medium containing instructions that if executed enable a system to:
receive registration information from one or more applications;
notify an operating system of an expected period of quietness or an expected idle duration;
hold incoming traffic during the expected period of quietness or expected idle duration;
determine whether one or more application timers have expired; and
synchronize outgoing network requests from the computer for the one or more applications based on the determination that the one or more application timers have expired.

### Claim 23 (depends on 22)

The article of claim 22, the registration information comprising one or more of message frequency and timing requirements including allowable jitter, network keep-alive, periodic, or outgoing network communications for the one or more applications.

### Claim 24 (depends on 22)

The article of claim 22, the one or more applications comprising applications having non-critical outgoing message deadlines or engaging in periodic network activity.

### Claim 25 (depends on 22)

The article of claim 22, comprising instructions that if executed enable the system to:
run the synchronized outgoing network requests expected to be run within the next period of quietness or next idle duration before the next period of quietness or next idle duration.

### Claim 26 (depends on 22)

The article of claim 22, comprising instructions that if executed enable the system to:
predict the expected period of quietness or expected idle duration based on one or more of information from one or more peripheral devices and adaptive estimation including heuristic idle durations.

### Claim 27 (depends on 22)

The article of claim 22, comprising instructions that if executed enable the system to:
receive a task from one or more of the one or more applications;
determine if the task can be put off for at least a break even duration;
delay servicing of the task if the task can be put off for the break even duration and if the one or more application timers have not expired.

### Claim 28 (depends on 22)

The article of claim 22, comprising instructions that if executed enable the system to:
determine whether one or more periodic application timers have expired, the one or more periodic application timers to include an indication of one or more application with keep-alive messages; and
service one or more tasks from the one or more applications with keep-alive messages based on the determination that the one or more periodic application timers have expired.

### Claim 29

An apparatus, comprising:
logic, at least a portion of which is in hardware, the logic to receive registration information from one or more applications, notify an operating system of an expected period of quietness or an expected idle duration, hold incoming traffic during the expected period of quietness or expected idle duration, determine whether one or more application timers have expired, and synchronize outgoing network requests from the computer for the one or more applications based on the determination that the one or more application timers have expired.

### Claim 30 (depends on 29)

The apparatus of claim 29, the registration information comprising one or more of message frequency and timing requirements including allowable jitter, network keep-alive, periodic, or outgoing network communications for the one or more applications.

### Claim 31 (depends on 29)

The apparatus of claim 29, the one or more applications comprising applications having non-critical outgoing message deadlines or engaging in periodic network activity.

### Claim 32 (depends on 29)

The apparatus of claim 29, the logic to predict the expected period of quietness or expected idle duration based on one or more of information from one or more peripheral devices and adaptive estimation including heuristic idle durations.

### Claim 33 (depends on 29)

The apparatus of claim 29, the logic to receive a task from one or more of the one or more applications, determine if the task can be put off for at least a break even duration, and delay servicing of the task if the task can be put off for the break even duration and if the one or more application timers have not expired.

### Claim 34 (depends on 29)

The apparatus of claim 29, the logic to determine whether one or more periodic application timers have expired, the one or more periodic application timers to include an indication of one or more application with keep-alive messages, and service one or more tasks from the one or more applications with keep-alive messages based on the determination that the one or more periodic application timers have expired.
