System and method for providing intelligent power management in a network environment

• US 9,026,812 B2
• Filed: 06/29/2010
• Issued: 05/05/2015
• Est. Priority Date: 06/29/2010
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Ravindranath, Ram Mohan, Girirajan, Prasad Babu
• Primary Examiner(s): Abbaszadeh, Jaweed A
• Assistant Examiner(s): Mazyad, Alyaa T
• Application Number:
  US12/826,416
• Publication Number:
  US 20110320833A1
• Time in Patent Office: 1,771 Days
• Field of Search: 713/300, 713/323, 713/310, 713/320
• US Class Current: 713/310
• CPC Class Codes: H04L 12/10 Current supply arrangements
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

An example method is provided and includes communicating a first packet to a network element in order to indicate whether an endpoint can have its power managed by network communications. The first packet includes an Internet protocol (IP) address associated with the endpoint. The method also includes receiving a second packet from the network element to identify whether the endpoint can have its power managed. The endpoint is configured to have its power managed via a port associated with the endpoint. In more specific embodiments, a state associated with the endpoint is used to determine whether to power on, or to power off the endpoint. In other implementations, the endpoint is powered on, or powered off at a specific time based on a policy associated with the endpoint.

Claims

1. A method, comprising:

communicating a first packet to a network element, from a call agent, in order to indicate whether an endpoint can have its power managed by network communications, wherein the first packet includes an Internet protocol (IP) address associated with the endpoint;

receiving, at the call agent, a second packet from the network element to identify whether the endpoint can have its power managed, wherein the endpoint is configured to have its power managed via a Power over Ethernet port associated with the endpoint, and wherein a current state of the endpoint is communicated using a Type Length Value (TLV) format;

communicating a request from the network element to power off the endpoint, wherein the end point determines whether it can be power off based, at least partially, on the current state of the endpoint; and

receiving, from the endpoint, a power off request at the call agent when the end point determines it can be powered off, wherein the call agent can override the power off request.

2. The method of claim 1, wherein the endpoint is powered on, or powered off at a specific time based on a policy associated with the endpoint.

3. The method of claim 1, wherein the first packet includes the TLV format, wherein a command from the call agent is provided to power on the endpoint based on a presence of an incoming call for the endpoint.

4. The method of claim 1, wherein the first packet includes an opcode for identifying the current state associated with the endpoint.

5. The method of claim 1, wherein the endpoint is an Internet protocol (IP) phone, and wherein the first packet includes interface data and port details associated with the IP phone.

6. The method of claim 1, wherein the endpoint is configured to signal when it should be subsequently powered on, as the endpoint is being powered off.

7. The method of claim 1, wherein the endpoint obtains state information using an application program interface.

8. The method of claim 1, wherein the current state is a current power state of the endpoint.

9. The method of claim 1, wherein the call agent is separate from the network element.

10. The method of claim 1, wherein the call agent, the network element, and the endpoint are physically separate from each other.

11. Logic encoded in one or more non-transitory tangible media that includes code for execution and when executed by a processor operable to perform operations comprising:

communicating a first packet to a network element, from a call agent, in order to indicate whether an endpoint can have its power managed by network communications, wherein the first packet includes an Internet protocol (IP) address associated with the endpoint;

receiving, at the call agent, a second packet from the network element to identify whether the endpoint can have its power managed, wherein the endpoint is configured to have its power managed via a Power over Ethernet port associated with the endpoint, and wherein a current state of the endpoint is communicated using a Type Length Value (TLV) format;

communicating a request from the network element to power off the endpoint, wherein the end point determines whether it can be power off based, at least partially, on the current state of the endpoint; and

receiving, from the endpoint, a power off request at the call agent when the end point determines it can be powered off, wherein the call agent can override the power off request.

12. The logic of claim 11, wherein the first packet includes the TLV format, wherein a command from the call agent is provided to power on the endpoint based on a presence of an incoming call for the endpoint.

13. The logic of claim 11, wherein the first packet includes an opcode for identifying the current state associated with the endpoint.

14. The logic of claim 11, wherein the endpoint is an Internet protocol (IP) phone, and wherein the first packet includes interface data and port details associated with the IP phone.

15. The logic of claim 11, wherein the endpoint is configured to signal when it should be subsequently powered on, as the endpoint is being powered off.

16. An apparatus, comprising:

a memory element configured to store electronic code,

a processor operable to execute instructions associated with the electronic code, and

a power management module configured to interface with the memory element and the processor such that the apparatus can;

communicate a first packet to a network element, from a call agent, in order to indicate whether an endpoint can have its power managed by network communications, wherein the first packet includes an Internet protocol (IP) address associated with the endpoint;

receive, at the call agent, a second packet from the network element to identify whether the endpoint can have its power managed, wherein the endpoint is configured to have its power managed via a Power over Ethernet port associated with the endpoint, and wherein a current state of the endpoint is communicated using a Type Length Value (TLV) format;

communicate a request from the network element to power off the endpoint, wherein the end point determines whether it can be power off based, at least partially, on the current state of the endpoint; and

receive, from the endpoint, a power off request at the call agent when the end point determines it can be powered off, wherein the call agent can override the power off request.

17. The apparatus of claim 16, wherein the endpoint is powered on, or powered off at a specific time based on a policy associated with the endpoint.

18. The apparatus of claim 16,

wherein the call agent is configured to communicate a command to power on the endpoint based on a presence of an incoming call for the endpoint.

19. The apparatus of claim 16, wherein the first packet includes an opcode for identifying the current state associated with the endpoint, and wherein the first packet includes the TLV format, wherein a command from a call agent is provided.

20. The apparatus of claim 16, wherein the endpoint is configured to signal when it should be subsequently powered on, as the endpoint is being powered off.