# US 2010/0169684 A1 · Downstream device service latency reporting for power management

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

- Number: US 2010/0169684 A1
- Document ID: US20100169684A1
- Status: Published application
- Kind: A1
- Application number: 12/346,853
- Filed: 2008-12-31
- Published: 2010-07-01
- Earliest claimed: 2008-12-31
- Assignees: Intel Corporation
- Inventors: Jaya L. Jeyaseelan; Jim Walsh; Robert E. Gough; Barnes Cooper; Neil W. Songer
- Web page: https://patentgrep.com/patent/US20100169684A1

## CPC

- H04W 52/0225: {using monitoring of external events, e.g. the presence of a signal}
- G06F 1/206: {comprising thermal management}
- G06F 1/3203: Power management, i.e. event-based initiation of a power-saving mode
- G06F 1/3206: Monitoring of events, devices or parameters that trigger a change in power modality
- G06F 1/3296: by lowering the supply or operating voltage
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- H04L 43/0858: {One way delays}
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- 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

For one disclosed embodiment, a transition from a first state to a second, different state for at least a portion of a downstream device may be identified. The first and second states may correspond to different levels relating to activity for at least a portion of the downstream device. Data corresponding to a service latency may be transmitted to an upstream device in response to the identified transition for one or more upstream devices to manage power based at least in part on the service latency. Other embodiments are also disclosed.

## Claims

### Claim 1

An apparatus comprising:
first logic to identify a transition for at least a portion of a downstream device from a first state to a second, different state, wherein the first and second states correspond to different levels relating to activity for at least a portion of the downstream device; and
second logic to transmit to an upstream device data corresponding to a service latency in response to the identified transition for one or more upstream devices to manage power based at least in part on the service latency.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the second logic is to wait a predetermined period of time after identification of the transition before transmitting the data.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the second state is an idle state.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the second state is an idle state and the service latency is based at least in part on an available capacity of a buffer for the downstream device to receive data.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the second state is an active state and the service latency is based at least in part on a reserve capacity of a buffer for the downstream device to receive data.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the second state is a lower power state relative to the first state.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the first state corresponds to the performance of one or more tasks by the downstream device and the second state corresponds to completion of one or more tasks by the downstream device.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the second logic is to transmit to an upstream device data corresponding to a service latency identified by the upstream device.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein at least a portion of the downstream device is to transition from the first state to the second state at substantially fixed time intervals.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the first logic is to identify that at least a portion of the downstream device is about to transition from the first state to the second state.

### Claim 11 (depends on 1)

The apparatus of claim 1, wherein the first logic is to identify that at least a portion of the downstream device has transitioned from the first state to the second state.

### Claim 12

A method comprising:
identifying a transition for at least a portion of a downstream device from a first state to a second, different state, wherein the first and second states correspond to different levels relating to activity for at least a portion of the downstream device; and
transmitting to an upstream device data corresponding to a service latency in response to the identified transition for one or more upstream devices to manage power based at least in part on the service latency.

### Claim 13 (depends on 12)

The method of claim 12, comprising waiting a predetermined period of time after identification of the transition before transmitting the data.

### Claim 14 (depends on 12)

The method of claim 12, wherein the second state is an idle state and the service latency is based at least in part on an available capacity of a buffer for the downstream device to receive data.

### Claim 15 (depends on 12)

The method of claim 12, wherein the second state is a lower power state relative to the first state.

### Claim 16 (depends on 12)

The method of claim 12, wherein the first state corresponds to the performance of one or more tasks by the downstream device and the second state corresponds to completion of one or more tasks by the downstream device.

### Claim 17 (depends on 12)

The method of claim 12, wherein the transmitting includes transmitting to an upstream device data corresponding to a service latency identified by the upstream device.

### Claim 18 (depends on 12)

The method of claim 12, comprising transitioning by at least a portion of the downstream device from the first state to the second state at substantially fixed time intervals.

### Claim 19

A downstream device comprising:
first logic to identify a transition for at least a portion of the downstream device from a first state to a second, different state, wherein the first and second states correspond to different levels relating to activity for at least a portion of the downstream device;
second logic to transmit to an upstream device data corresponding to a service latency in response to the identified transition for one or more upstream devices to manage power based at least in part on the service latency; and
third logic to help control functionality of the downstream device.

### Claim 20 (depends on 19)

The downstream device of claim 19, wherein the second logic is to wait a predetermined period of time after identification of the transition before transmitting the data.

### Claim 21 (depends on 19)

The downstream device of claim 19, wherein the second state is an idle state and the service latency is based at least in part on an available capacity of a buffer for the downstream device to receive data.

### Claim 22 (depends on 19)

The downstream device of claim 19, wherein the second state is a lower power state relative to the first state.

### Claim 23 (depends on 19)

The downstream device of claim 19, wherein the first state corresponds to the performance of one or more tasks by the downstream device and the second state corresponds to completion of one or more tasks by the downstream device.

### Claim 24 (depends on 19)

The downstream device of claim 19, wherein the second logic is to transmit to an upstream device data corresponding to a service latency identified by the upstream device.

### Claim 25 (depends on 19)

The downstream device of claim 19, wherein at least a portion of the downstream device is to transition from the first state to the second state at substantially fixed time intervals.
