TWI495297B - Process, computer readable media, and system for device power management using network connections - Google Patents

Description

Device with network connection device power management, computer readable media and system

The present invention relates to a device power management using a network connection.

Computerized systems have made significant contributions to the advancement of modern society and have been used in some applications to achieve beneficial results. This is an example of the use of electronic data storage, which benefits from the use of computerized systems. Currently known computerized file systems (such as file servers) facilitate the sharing of data with various sizes of networks. When data access to a file system is widely permitted (eg, via the Internet), multiple servers can be combined in the data center to address accessibility and data storage considerations.

The state of the network connection is quite important for many file storage systems deployed on a network. Many network connection protocols (with many levels of implementation) that have variable level of reliability are applied to carry data (typically in the form of packets) between and among network devices. These devices may include: file servers, client devices, and any network edge devices (eg, servers, switches) along the communication path. The complexity of network communication (that is, the inherent difficulty of processing large amounts of data at high speeds over large logical and/or physical distances) is such that disruption of network communication is not completely uncommon. Excess network traffic, software errors, mechanical design flaws, and simple user errors can cause undesired performance, such as packet delays, unresponsive devices, and complete network communication failures.

Unfortunately, as the complexity, capacity, and level of servers in the data center increase with industry standards, the severity of network communication disruptions can increase accordingly. Therefore, the effective and timely maintenance of the server in the data center has become an important consideration. Therefore, automated management solutions have been developed to address these considerations. The repair of the network connection status of a data center may require re-initializing a network server by powering a server's power cycle (ie, turning off the server and then turning on the server).

In some examples, when a server aborts, restarting may be a way to recover the server. In addition, when the server is provided, in order to trigger it to retry the server's pre-boot execution environment ("PXE") to install an updated operating system onto the server, a server may need to be restarted. Therefore, since the restart procedure is so important to these basic operations, it is absolutely indispensable for whether or not the program is reliably executed. Otherwise, these servers may require manual intervention and try these unnecessary extreme and costly fixes.

Wake on LAN ("WOL", sometimes called "WoL") is an Ethernet network standard that allows a computer to remotely access a low-power state via a network message ( For example, hibernate or sleep is turned on or awake. Wake-on-LAN support is usually implemented on a computer's motherboard and is not restricted to LAN traffic, but works on all network traffic, including Internet traffic.

A general procedure for waking up a computer remotely via a network connection includes shutting down a target computer (eg, sleep, hibernation, or "soft off") to reserve power to the network card. The network card listens to a specific data packet (called a "magic packet"), a broadcast frame (included anywhere in its payload), a specific sequence of data, and the MAC of the target computer (media access control) ) Address. The magic packet is a broadcast on the broadcast address of a special subnet (or a full LAN).

When the computer receives the packet, it checks the packet to verify that the packet contains the correct information (ie, the target MAC address contained in the packet matches the MAC address of the machine). A valid match causes the computer to switch. Turn it on and turn it on. In order to make the wake-up on the LAN work, even when it is on standby, it is necessary to keep some of the network interfaces open. This increases the standby power used by the computer. If wake-up on the LAN is not required, turning it off when the computer is turned off but still plugged in reduces power consumption. However, when wake-up on the LAN allows a computer to be turned on or awake from a low power state, the wake-up on the LAN is managed through a properly functioning network. As such, wake-up on the LAN does not cause a computer to reboot itself, and/or re-initializes a network connection to the repaired computer.

There are some known methods to solve the problem of remote reinitialization. The solution to this problem is through the use of servers with IPMI functionality. IPMI (Intelligent Platform Management Interface) is a loosely defined standard that allows a server's frequency band to be out of management (ie, managed on a dedicated channel) and includes power control capabilities for a server. IPMI supports a variety of connectivity types, including stand-alone network connections, shared network connections, or serial connections.

However, all three of these types of connections present an obstacle to effective power management. Since additional components are required (such as connectors, series concentrators, or a network switch), separate network connections and serial connections result in additional costs. The sharing of network connections eliminates these costs, but there are other issues. First, it may be difficult to identify the correct media access control ("MAC") address of the IPMI network device from the server's network device (eg, a router). Furthermore, an IPMI network device requires its own IP address, which becomes a problem in situations where the IP address is restricted. Furthermore, if a server has a program error that would cause it to flood the network, it may not allow IPMI packets to pass through an IPMI controller.

Moreover, a typical IPMI management device has a very complex set of features that make the code complex and thus prone to program errors, some of which may not be apparent until the device has been widely deployed. The following facts exacerbate the situation: the upgrade of the code may require a hard power cycle (which cannot be performed by an IPMI device) to process the box.

A second method of automatic server management is through an advanced power cord with management capabilities ("Manager Power Cord"). One or more servers having a supervisor power cord are plugged into a power cord having a network connection. The software is implemented on a power line that can be used to turn the power on or off. Unlike IPMI devices, this solution requires some network connectivity, typically requiring very little software to operate inside the power line (thus reducing the possibility of software program errors) and driving an existing connection to the server (for example, Power cable). However, this method also has many limitations. Manager power lines cost more than traditional, unmanaged power lines and support fewer options than IPMI devices. Newer servers can also be designed to use DC power (rather than traditional AC power) to supply power and/or operate at non-standard voltages (which are not supported by known administrator power lines, or they may Significantly increase the cost). In addition, newer servers share power supplies for efficiency, thereby increasing the impact of managing power at the power line level, adding to the difficulty of specific alignment applications for power management.

This summary is intended to introduce a selection of concepts in a simplified form, which is further described in the following embodiments. This Summary is not intended to identify key features or essential features of the claimed subject matter, and is not intended to limit the scope of the claimed subject matter.

The specific embodiment relates to a computer system to which an internet connection is attached. In particular, a computer system having a variable power state corresponding to certain trigger events is based on the state of the additional network connection.

In one embodiment, a program provides for controlling the power state of the computer system using a network connection attached to a computer system. By configuring the hardware to function when the network is active, and when the network is down when it is not active, a network device (such as a switch) can be used to manage the computer system in a simple and relatively inexpensive manner. Power status.

Reference will now be made in detail to the various embodiments. Since the subject matter of the present invention is described in conjunction with the alternative embodiments, it is understood that they are not intended to limit the claimed subject matter to these embodiments. Rather, the claimed subject matter is intended to cover alternative forms, modifications, and equivalents, which may be included within the spirit and scope of the claimed subject matter as defined by the appended claims.

Further, in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It will be apparent to those skilled in the art, however, that these embodiments may be practiced without these specific details or equivalents. In other instances, well-known steps, procedures, components, and circuits are not described in detail so as not to unnecessarily obscure the aspects and features of the subject matter.

The following detailed description is presented and discussed in terms of a program. Although the steps and sequences herein are disclosed in one of the figures (e.g., Figure 1) to describe this program operation, such steps and sequences are exemplary. The embodiments are susceptible to performing various other steps or variations of the steps, which are described in the flowcharts illustrated herein, and are in a different order than those illustrated and described herein.

Portions of the detailed description are presented in terms of procedures, steps, logic blocks, processing, and other symbolic representations of operations on data bits (which may be implemented on computer memory). These instructions and presentations are used by those skilled in the art of processing technology to best express the substance of their work to other skilled artisans. A program, computer-implemented steps, logic blocks, steps, and the like are generally derived from a self-consistent sequence of steps or instructions leading to a desired result. These steps are the actual number of actual operations required. Generally, although not necessarily, these quantities take the form of electrical or magnetic signals that can be stored, converted, combined, compared, and/or operated in a computer system. It has been proven that for ease of explanation, (mainly for general use) these signals are often referred to as bits, values, elements, symbols, letters, vocabulary, numbers, or the like.

However, it should be borne in mind that all of these and similar words are associated with the appropriate actual quantities and are merely convenient labels applied to these quantities. Unless there is a specific statement, as is apparent from the discussion below, it is understood that the use of vocabulary in various places is "access", "write", "include", "save", "transfer", "cross" , "associated", "identified" or the like represents the actions and steps of a computer system or similar electronic computing device that uses the data (in the computer system register and the entity in the memory) The (electronic) quantity represents the operation and conversion to other data (similarly expressed as the number of entities in a computer system memory or scratchpad or other such information storage, transmission or display device).

In the following embodiments, a method for automatic power management using one of the computerized devices of the network connection is described.

Automatically manage one of the network devices' power states

Referring now to FIG. 1, a flow diagram of a process 100 for automatically managing a network device power state based on a connection state of a network connection is depicted in accordance with an embodiment. Although specific steps of the processes 100, 200, 300 are disclosed, such steps are exemplary. That is, the embodiments of the present invention are adapted to perform various other (additional) steps or step variations listed in the processes 100, 200, 300. It will be appreciated that the steps in the processes 100, 200, 300 can be performed in a different order than presented, and not all of the steps in the processes 100, 200, 300 can be performed.

Referring now to step 101, a network connection of a network device is monitored for the occurrence of a triggering event. In an embodiment, the triggering event is a link state of the network connection. The link state of the network connection for one of the network devices corresponds to the link state associated with a coupled network edge device (e.g., a router or switch). Typically, a network link of a network connection alternates between two states: on (ie, active) and off (ie, inactive). The two states indicate the level of network activity (eg, network packets) processed and/or transmitted through the UI. Therefore, a failed link when it is intended to process and/or transmit a network packet no longer acts, and will have an "off" (or "inactive") link state.

A network device can include, but is not limited to, a host, a server, a router, a switch, a bridge, a disk array, and a network attached server (NAS). The type of network link can include any type of link that uses one of the carrier type signals, such as Ethernet (for local area networks), wireless carrier, wide area network (WAN), and fiber distribution data interface (FDDI). ), Token Ring, fiber and Fibre Channel.

Thus, in one embodiment, when a link state changes from an unresponsive or inactive state, a change in the state of the link (eg, from non-active to active) can be used as a trigger event. . Similarly, in an embodiment, if a link state becomes unresponsive, faulty, or indicates a suspension of network activity, changes in the link state (eg, from active to inactive) can be Used as a trigger event. In other embodiments, a triggering event may include transmission of an active network packet over a period of time. According to this embodiment, a triggering event is used to maintain (or change) the current power state of the network connection. For example, to maintain a network connection in an active state, one or more instances of network activity must occur once every other period of time (eg, every five minutes). If the network connection detects that there is no network activity for the entire period of time, the power state of the corresponding network device can be adjusted accordingly (that is, an inactive network connection state can cause the network device to decrease. The rate at which its power is consumed). In a further embodiment, if no network activity is detected during another time period (usually longer), the corresponding network device can be powered.

Similarly, a trigger event can also be used to change the current state of the network connection. For example, if an active network connection detects one or more instances of network activity, the power state of the corresponding network device can be adjusted accordingly.

Another embodiment is implemented as a specific network packet to be used as a triggering event. According to this embodiment, the network packet will not be processed by the primary network interface card (NIC), but the device can be triggered to turn off or on.

Referring to step 103, the power state of the network device is managed to correspond to the trigger event observed in step 101. There are various embodiments herein that can be used to use the state of the network to support management of power. Many systems have an option to support the provision of power to a sleeping (ie, retaining their power) system for network activity. In one embodiment, if the network is not active, a system is configured to automatically turn off the power of a system, and if the network becomes active, turn it on. For example, this feature can be implemented for changes to the BIOS that already exists in the hardware.

In another embodiment, the existing IPMI hardware can be reprogrammed to support the use of the network connection status to manage this feature of the IPMI hardware device. The IPMI configured to be a coaxial management mode can be used to detect the state of the network without actively using the network. Depending on the state of the network, the IPMI code can use its existing support for managing power to reflect the power state of a system.

In another embodiment, the hardware is changed to use the network link trigger to act as a forward voltage trigger to enter a motherboard of the computer system to control the power supply. In this embodiment, it does not have a specific software, but the server power supply will reflect the network power.

Exemplary power state control flow

Referring now to FIG. 2, an exemplary embodiment of managing the power state of a network device (eg, a host or a server) in a standard operating power state based on a power state of a network link is illustrated in accordance with an embodiment. Flowchart of program 200. Steps 201-223 describe exemplary steps involved in the process 200 in accordance with various embodiments described herein. According to Figure 2, the network device operates ("operating") in a standard power state.

In step 201, a change in the power state of the network link of the device is detected. The power state of the network link (on the first layer of the OSI model) is different from the link state of the network (on the second layer of the OSI model). If the power state of the network link is active (representing the network as "up"), the process remains at step 201 until the power state of the network link is no longer active. Once the power state of the network link is detected as inactive ("down"), the process proceeds to step 203.

In step 203, the change of the network link status detected in step 201 is received and filtered. Step 203 filters out false, attenuated, and/or intermittent changes in the network link. Filtering can be configured according to a variety of methods (eg, changes in the state of the network link can be ignored for less than ten seconds). Filtering may also include delaying a confirmation notification of a change in the state of the network link to the entire system and/or the rest of the network until it can determine the nature of the change (eg, whether the change is false) The time is up.

In optional step 205, the operating system of the device is checked to determine if the operating system provides a status check of the sleep/hibernate/power down procedure. A successful status check in step 205 (e.g., the operating system of the device is determined to execute a stateful application) will cause the program to proceed to step 207. This decision is particularly applicable to devices with stateful applications that require a controlled sequence to prevent data loss or corruption. The system with stateless application may skip step 207 and proceed directly to step 209. In a specific embodiment, a stateful check includes an informed query from the operating system.

In optional step 207, the system with the stateful application can wait for an instant to proceed to the next step in the sequence. A system with a stateful application may remain in the optional step 207 according to a pre-established maximum duration. If no notification is received during the pre-established maximum duration, the program may proceed to optional step 209 or proceed directly to step 213 in accordance with various embodiments.

In optional step 209, the device and/or the operating system of the device are inspected to determine whether the device and/or operating system supports advanced configuration and power interface (ACPI, "Advanced configuration and power interface" features. ACPI allows Power management in a device is controlled by the operating system of the device. The device and operating system that is determined not to support ACPI may skip step 211 and proceed directly to step 213.

In optional step 211, the device determined to support one of the ACPI features and/or the operating system of the device may wait for an ACPI signal to proceed to the next step in the sequence. The device or operating system supporting the ACPI feature may remain in the optional step 211 based on a pre-established maximum duration. If no signal is received during the pre-established maximum duration, the program may proceed directly to step 213.

In step 213, the program determines that step 203 has been completed (and steps 205 through 211 in other embodiments) and begins the process of changing the power state of the device. According to some embodiments, the power state of the device can be pre-selected by a defined set of states (eg, sleep, sleep, power down). In a further embodiment, the power state of the device can be pre-selected based on a set of established conditions (e.g., not active for a period of time). Once the process of changing the power state of the device has been completed, an indication that the program has been completed is transmitted to step 215.

In step 215, once the power state of the device has decreased (during step 213), the components of the physical layer ("PHY") implementing the device may also be reduced to their lowest possible state. In one embodiment, any amount of power required to monitor changes in the power state of the network link is turned off by the PHY.

In step 217, the PHY transmitter in the network interface card is closed. The main source of power consumption in the NIC is removed by turning off the transmitter. In addition, turning off the PHY transmitter also removes the WoL's ability to wake up the device itself because a link cannot be established to another device without the need to transfer power to the transmitter. In some embodiments, the completion of step 217 proceeds directly to step 219.

In the optional step 219, the transmitter circuit of the NIC is also turned off to achieve the maximum reduction in power consumption in the device. The optional step 219 is in accordance with various embodiments in accordance with the hardware capacity and the operational system state that can be used. At the end of step 219, the program is completed to convert the power state of a network device from a full operational capacity to a low power state based on the power state of the network.

Referring now to FIG. 3, a flow diagram of an exemplary process 300 for managing the power state of a network device in a reduced operational power state in accordance with a power state of a network link is depicted in accordance with an embodiment. Steps 301-313 describe exemplary steps involved in the process 200 in accordance with various embodiments described herein. According to Fig. 3, a network device (e.g., a host or a server) operates ("operating") with a reduced power state. A reduced power state can include, for example, a device to sleep, sleep, or power down.

In step 301, a change in the power state of the network link of the device is detected in the PHY receiver of the device. The power state of the network link (on the first layer of the OSI model) is different from the link state of the network (on the second layer of the OSI model). If the power state of the network link is inactive (the network is "down"), the process remains at step 301 until the power state of the network link becomes active. Once the power state of the network link is detected as active ("boot"), the process proceeds to step 305.

In step 303, the change of the network link status detected in step 301 is received and filtered. Step 303 filters out false, attenuated, and/or intermittent changes in the network link. Filtering can be configured according to a variety of methods (eg, changes in the state of the network link can be ignored for less than ten seconds). Filtering may also include delaying a confirmation notification of a change in the state of the network link to the entire system and/or the rest of the network until it can determine the nature of the change (eg, whether the change is false) The time is up.

In step 305, after the filtering and/or delay of step 303 has been applied, the power is re-supplied to the circuitry of the transmitter of the NIC.

In step 307, once the power is restored to the circuitry of the transmitter of the NIC, the NIC of the device will establish a link with a network.

In optional step 309, it determines if the device supports wake-up features on the LAN. A successful decision (e.g., the device supports 20 wakeups on the LAN) causes the program to proceed to step 311. For devices that do not support the wake-up feature on the LAN, the program can proceed directly to step 313. Wake-on-LAN support allows a manager to control when the device has reached a fully operational power state.

In the optional step 311, a procedure for a fully operational power state is then initiated to activate the device based on the wake-up feature on the LAN supported by the device (determined in step 309). A wake-on-LAN feature can include any previously known wake-on-LAN feature or program.

In step 313, the device is restored to a fully operational power state. If the device supports the WoL feature (determined in step 309), the device is powered down according to the programs initiated in step 311. For devices that do not support the WoL feature, the power to the device is restored according to conventional means, as determined by the operating system (for devices supporting ACPI) and/or the BIOS of the device.

Exemplary network configuration

Referring now to the fourth diagram, an exemplary network configuration 400 is shown in accordance with an embodiment. When the exemplary network configuration 400 is shown with the specific, enumerated features and elements, it can be appreciated that such illustration is merely exemplary. Thus, the specific embodiments are well suited for applications that include different, additional, or fewer elements, features, or configurations.

As shown, the exemplary network configuration 400 depicts a relatively simple network configuration: some network client devices (eg, servers 411, 413) are connected by a network edge device (eg, network switch 401). ) to attach to the network. As shown, the client can be a discrete computer system that operates as a server. At the same time, the network device used in the exemplary network configuration 400 can be diverse, but will essentially include Layer 2/4 switching and routing functionality. The network switch 401 is shown to include a plurality of ports (e.g., 埠 403, 405) configured in two columns. As depicted in the exemplary network configuration 400, the network interface 415 of the server 411 is coupled to the port 405 of the network switch 401 via a network connector (e.g., network cable 409). Similarly, the network interface 417 of the server 413 is coupled to one of the ports 403 of the network switch 401 via a network cable 407 (unlike the coupling to the network interface 415).

The exemplary network embodiment 400 is also shown to include a power extension cord 431 to supply power to the servers 411, 413 in the configuration. The power extension cord 431 can be any conventionally used power extension cord device that includes a socket strip attached to the end of an elastic cable that allows multiple devices to be inserted (ie, coupled) to a power source (eg, a wall outlet) , or receive power from it. In various embodiments, the power extension cord 431 can also supply power to the network switch 401. Power extension cord 431 supplies power to servers 411 and 413 in the configuration via a power transmission cable (e.g., wires 433, 435). As shown in network specific embodiment 400, power terminal 419 of server 411 is coupled to power extension line 431 via wire 433. Power terminal 421 of server 413 is similarly coupled to power extension line 431 via wire 435.

According to some embodiments, the power state of the server 411 and the server 413 can be managed according to a triggering event corresponding to the state of the network connection (e.g., network activity) processed and/or transmitted in the network switcher 401. . For example, the link state of the network connection of server 411 includes a state of being coupled via network cable 409 to network switch 401 of server 411 located at network interface 415. A change in the state of the link in the queue 405 of the network switcher 401 (eg, from active to inactive, or from inactive to active) can be used as a triggering event sufficient to change the servo The power state of the device 407. Following this example, the power state of the server 411 can be managed to correspond to a more appropriate power consumption level. For example, if the state of the network connection is off, the power state of the server 411 can be adjusted to the "sleep" mode, thus consuming less power until another trigger event is detected in the network connection. In other embodiments, changes in the link state (or other triggering events) may cause the servo 411 to cycle power. For example, a failed link state (i.e., no packet is received or transmitted) may cause the server 411 to cycle power.

Exemplary networked environment

Referring now to Figure 5, an exemplary networked environment 500 is shown in accordance with an embodiment. When the exemplary networked environment 500 is shown with the specific, enumerated features and elements, it can be appreciated that this description is merely exemplary. Thus, the specific embodiments are well suited for applications that include different, additional or fewer components, features or configurations.

As shown, the exemplary networked environment 500 depicts a relatively simple networked environment: some network client devices (eg, servers 501, 503, 505, and 507) that are connected by network edge devices (eg, Edge devices 511, 513) are attached to the network. As shown, the client can be a discrete computer operating as a server. At the same time, the edge devices used in the exemplary networked environment 500 can vary, but will essentially include Layer 2/5 switching and routing functionality. According to a specific embodiment, the power states of the servers 501, 503, 505, and 507 are managed according to trigger events corresponding to the state of the network connection. For example, the power state of the server 501 and the server 503 may correspond to the link state of the associated network port of the edge device 511. Similarly, the power state of server 505 and server 507 may correspond to the link state of the associated network port of edge device 513.

The exemplary networked embodiment 500 is also shown to include a central router 521, such as interconnect edge devices 511 and 513, and to provide access to the Internet 599. In various embodiments, the central router 521 does not exist, or may take a variety of types, or provide a variety of features and services.

Basic computing device

FIG. 6 illustrates an exemplary computing device 600 in accordance with various embodiments. The computing device 600 depicts such components of a basic computer system that provide an execution platform for certain software-based functions in accordance with various embodiments. The computing device 600 can be a network device having a power state managed according to certain trigger events corresponding to a state of a network connection.

The computing device 600 can be implemented, for example, as a desktop computer system, a laptop computer system, or a server computer system. Similarly, computing device 600 can be implemented as a palm-sized device (e.g., a mobile phone, etc.). The computing device 600 basically includes at least some type of computer readable media. The computer readable medium can be a number of different types of usable media that can be accessed by computing device 600 and can include, but is not limited to, computer storage media.

In its most basic configuration, the computing device 600 basically includes a processing unit 601 and a memory 603. Depending on the actual configuration and type of computing device 600 used, memory 603 can be volatile (e.g., RAM) 605, non-volatile 607 (e.g., ROM, flash memory, etc.), or some combination of the two. In one embodiment, the network connection monitor 609 monitors the state of the network connection coupled to the computing device 600, i.e., instantiated in the non-volatile memory 605. Trigger analysis engine 611 is used to analyze a trigger event and determine the appropriate power state of computing device 600, which may also be instantiated in non-volatile memory 605. Similarly, power state manager 613 for managing the power state of computing device 600 can also be instantiated in non-volatile memory 605. For example, the network connection monitor 609, the trigger analysis engine 611, and the power state manager 613 can all be implemented in the BIOS of the computing device 600 and stored in the non-volatile memory 607.

Further, the computing device 600 can include a number of storage systems (removable 611 and/or non-removable 613) such as magnetic or optical discs or magnetic tape. The network connection monitor 609, the trigger analysis engine 611, and the power state manager 613 can also be implemented in the BIOS, which is referenced by both the removable 615 and non-removable 617 mass storage systems. Similarly, computing device 600 can include input device 619 and/or output device 621 (eg, such as a display). Moreover, computing device 600 can include network connection 623 to other devices, computers, networks, servers, etc., using wired or wireless media. Because all of these devices are well known in the art, they need not be discussed in detail herein.

Although the subject matter has been described in language specific to structural features and/or processing logic, it is understood that the subject matter defined in the scope of the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts described above are disclosed in the form of examples of the scope of the application.

400. . . Exemplary network configuration

401. . . Network switcher

403. . . port

405. . . port

407. . . Network cable

409. . . Network cable

411. . . server

413. . . server

415. . . Network interface

417. . . Network interface

419. . . Power terminal

421. . . Power terminal

431. . . Power extension cord

433. . . wire

435. . . wire

500. . . Exemplary networked environment

501. . . server

503. . . server

505. . . server

507. . . server

511. . . Edge device

513. . . Edge device

521. . . Central router

599. . . Internet

600. . . Arithmetic device

601. . . Processing unit

603. . . Memory

605. . . volatility

607. . . Non-volatile

609. . . Network connection monitor

611. . . Trigger analysis engine

613. . . Power status manager

615. . . Removable

617. . . Non-removable

619. . . Input device

621. . . Output device

623. . . Network connection

The accompanying drawings are incorporated in and constitute a part of the specification, A flow chart of a program that automatically manages the power state of a network device.

2 is a flow chart showing an exemplary procedure for managing the power state of a network device in a standard operating power state in accordance with power state of a network link in various embodiments.

3 is a flow chart showing an exemplary procedure for managing the power state of a network device in a reduced operating power state in accordance with power state of a network link in various embodiments.

4 is a schematic diagram of an exemplary network configuration in accordance with one of many specific embodiments.

FIG. 5 is a schematic diagram of an exemplary network environment in accordance with one of many specific embodiments.

Figure 6 is a schematic diagram of a basic computing system in accordance with one of many specific embodiments.

200~219. . . Step flow

Claims (19)

A program for automatically managing a power state having a network connected to a computing device of a network, the program comprising the steps of: monitoring, in the computing device, the network connection for a triggering event; and managing the computing device The power state corresponds to the occurrence of the triggering event, the triggering event comprising providing a change in one of a link state of one of the first devices of the network device that accesses the network connection to the computing device. The procedure of claim 1, wherein the step of managing the power state comprises the step of: power cycling the computing device. The process of claim 1, wherein the step of managing the power state comprises the steps of: changing the power state of the computing device by a first power state and a second power state, the second power state ratio This first power state consumes less power. The process of claim 1, wherein the step of managing the power state comprises the steps of: changing the power state of the computing device by a first power state and a second power state, the second power state ratio The first power state consumes more power. The process of claim 1, wherein the triggering event comprises a network activity transmitted through the first network of the network device. The process of claim 5, wherein the triggering event is the receipt or transmission of the first network packet through the network device for a predefined period of time. The procedure of claim 5, wherein the triggering event is an absence of a network packet received or transmitted through the first network of the network device for a predefined period of time. The program of claim 6, wherein the network packet further comprises a specific combination of instructed packets. The program of claim 1, wherein the triggering event comprises detecting a power transmission to the computing device over a network cable. In the procedure of claim 1, the triggering event includes detecting the termination of power to the system over a network cable. A non-transitory computer readable medium having a computer executable component that, when executed by a computing device, implements the computing device as a power state management application, the non-transitory computer readable The media collection includes: a network monitor for monitoring a network connection for a trigger event, the network connection comprising one of a plurality of network devices that facilitate one of the network devices of the network connection; a trigger analysis Engine for analyzing an observed trigger event Determining an appropriate corresponding power state of the computing device; and a power state manager for managing the power state of the computing device to comply with the appropriate power state corresponding to the observed trigger event, wherein The trigger event contains a change in one of the states of the network connection. The non-transitory computer readable medium of claim 11, wherein the triggering event comprises a network activity detected on the first side of the network device. The non-transitory computer readable medium of claim 11, wherein the triggering event comprises a network inactivity in the first node of the network device. The non-transitory computer readable medium of claim 11, wherein the computer readable medium is implemented in a data storage device. A system for power management using a network connected device, the system comprising: a computer coupled to a processor of a memory, the computer receiving power via a network cable; a network device, the network The circuit device includes a plurality of ports, and the first one of the plurality of ports is coupled to the computer via a network cable; wherein a power state of the computer is determined according to a trigger event Dynamically, the triggering event corresponds to transmitting power from the first device of the network device to the computer through the network cable. A system as claimed in claim 15 wherein the triggering event comprises the beginning of a power source transmitted to the computer on the network cable. The system of claim 16 wherein the triggering event comprises termination of a power source transmitted to the computer over the network cable. The system of claim 15, wherein the power state of the computer is automatically managed between a first power state and a second power state, the second power state being consumed compared to the first power state Less power. The system of claim 15, wherein the power state of the computer is managed by power cycling the computer.