US20130132745A1 - System and method for network enabled wake for networks - Google Patents
System and method for network enabled wake for networks Download PDFInfo
- Publication number
- US20130132745A1 US20130132745A1 US13/302,544 US201113302544A US2013132745A1 US 20130132745 A1 US20130132745 A1 US 20130132745A1 US 201113302544 A US201113302544 A US 201113302544A US 2013132745 A1 US2013132745 A1 US 2013132745A1
- Authority
- US
- United States
- Prior art keywords
- network
- message
- network device
- devices
- network devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
- G06F1/3209—Monitoring remote activity, e.g. over telephone lines or network connections
Definitions
- This disclosure relates in general to the field of communications and, more particularly, to a system and a method for network enabled wake for networks.
- FIG. 1 is a simplified block diagram of an energy management system in accordance with one embodiment of the present disclosure
- FIG. 2A is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure
- FIG. 2B is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure
- FIG. 3 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure
- FIG. 4 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure.
- FIG. 5 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure.
- a method in one example embodiment and includes receiving a message at a network element configured for routing packets.
- the message directs a network device to change its power state.
- the method also includes identifying the network device as being associated with a network for which the network element has responsibility, and communicating at least a portion of the message from the network element to the network device.
- an application program interface is leveraged in order to communicate the portion of the message, which identifies a media access control (MAC) address associated with the network device.
- the message includes filter criteria to be used to identify the network device.
- the method may include searching a selection criteria database to identify the network device identified by the filter criteria.
- the filter criteria is used to identify a group of network devices for which a subsequent message for changing power states is intended.
- the network device can be part of a subnet associated with the network element.
- FIG. 1 is a simplified block diagram of an energy management system 10 in accordance with one example implementation of the present disclosure.
- FIG. 1 includes a subnet 18 , which can include any number of network devices 32 .
- Subnet 18 is typically a logically visible subdivision of an internet protocol (IP) network; however, subnet 18 can be any network that allows a switch to communicate with, control, and/or manage network devices 32 in subnet 18 .
- IP internet protocol
- a controller 20 can be provisioned in a network 22 in order to execute certain power management activities discussed herein.
- a number of switches 34 are also provisioned in network 22 .
- each switch 34 may contain a wake-on-local area network (LAN) module 26 . Wake-on-LAN module 26 can be configured to send change power state requests to network devices 32 at appropriate times.
- a gateway 28 may be provisioned in network 22 such that it can interface with converging-IP devices 36 , as is being illustrated in FIG. 1 .
- the infrastructure of subnet 18 can interact with a number of network devices 32 (e.g., personal computers (PCs), building controllers, wireless devices, telephones, lighting fixtures, HVAC systems, video devices (e.g., Telepresence systems), etc).
- Certain network devices 32 may be associated with IP devices having corresponding Software Development Kit (SDK) elements.
- SDK Software Development Kit
- gateway 28 may operate as a parent SDK for its child endpoints (e.g., a plurality of converging-IP devices 36 ).
- Subnet 18 is also coupled to a set of power management applications 12 , which may include elements such as a LAN management element, etc. Management applications 12 can operate to intelligently control (directly or indirectly) any of the devices of FIG. 1 .
- energy management system 10 is configured to measure and monitor power for network devices 32 (e.g., phones, AP's, PCs, building systems, etc.) and, further, provide command and control for network devices 32 .
- the activities of energy management system 10 may include communicating messages to individual network devices 32 for shifting from one power state to a different power state (e.g., shifting from a normal operating state to a hibernation state), as further detailed below.
- energy management system 10 provides a mechanism that understands the power consumption characteristics of network devices 32 for which it has responsibility. This can include understanding which network devices 32 can shift from one power state (e.g., a normal operating state) to a different power state (e.g., a hibernation, sleep mode, or shut down state).
- the architecture is configured to query for power information using the network and, furthermore, implement time-of-day policies to control network devices 32 .
- the network can operate as a control plane for controlling the energy consumption/usage for one or more network devices 32 within subnet 18 . In this sense, the network serves as a platform for intelligent energy control. From a practical perspective, the smart loading capabilities of the architecture allow for a tangible cost savings for an associated enterprise.
- the infrastructure of subnet 18 can interact with a number of network devices 32 (e.g., a local storage module, personal computers (PCs), building controllers, wireless devices, telephones, lighting fixtures, HVAC systems, video devices (e.g., Telepresence systems), etc.).
- the wake-on-LAN technology of energy management system 10 can enable network devices 32 to be remotely awaken from a hibernating or sleep state.
- the wake-on-LAN mechanism uses a management station to broadcast a “magic packet” containing a media access control (MAC) address of a target network device 32 .
- MAC media access control
- wake-on-LAN wake-on-LAN technology
- wake-on-LAN requests etc. generally refer to any suitable request for the transition of a device from one power state to a different power state.
- a network card on a wake-on-LAN enabled network device 32 is kept powered so when the network card sees its MAC address contained in a wake-on-LAN message, the network card initiates a power-up of the network device.
- the broadcast mechanism of directing wake-on-LAN requests can be difficult to deploy in an enterprise network because security policies in routers typically drop subnet directed broadcasts, thus preventing wake-on-LAN messages from being received. For this reason, wake-on-LAN is often restricted to working on local area networks instead of working on other networks (e.g., an enterprise wide area network (WAN)).
- WAN enterprise wide area network
- the wake-on-LAN feature may be provided in enterprise WAN networks.
- one or more network devices 32 in a subnet can remain powered on and run a special software agent, which is used to locally broadcast a received wake-on-LAN payload within the subnet.
- one or more powered on network devices 32 can receive a unicast transmission of a wake-on-LAN message.
- a wake-on-LAN message can be broadcast within the subnet by one or more of the powered on network devices 32 , which effectively circumvents the problem of routers dropping global broadcasts.
- the proxy model has several disadvantages including the requirement of vendor software, the installation of the vendors network devices' agent across the enterprise, the necessity of dedicated network devices 32 to remain powered on, and the failure issues when the agent is down or otherwise unreachable.
- enterprises with many small subnets may find leaving one or two network devices 32 active (e.g., per subnet) can significantly diminish their energy savings of reducing energy consumption for network devices 32 (e.g., to sleep during off peak hours).
- the architecture of FIG. 1 can overcome these shortcomings (and others) in leveraging a network element (e.g., a switch) to be utilized as a local broadcaster for a request to change power states (e.g., a wake-on-LAN request).
- the network element e.g., a switch, a router, a gateway, etc.
- receiving the message can have responsibility for one or more network devices for which the message was intended (e.g., the network element has an association with the network device, has a relationship with the network device, has been entrusted to manage the network device, has a geographical congruency with the network device, shares some commonality with device, has been assigned power management for the network device, shares a subnet with the network device, etc.).
- CLI command-line interface
- SNMP simple network management protocol
- APIs application programming interfaces
- a network domain of devices may use a protocol (e.g., an EnergyWise protocol) to transmit a change power state request based on a MAC address (or other addresses) to switches 34 residing in the network domain.
- a protocol e.g., an EnergyWise protocol
- Each switch 34 after checking certain filter criteria, can locally broadcast the change power state request to network device(s) 32 in the local subnet(s) assigned to switch 34 .
- network device(s) 32 matching the MAC address(es) in the change power state request would be awoken.
- filter criteria can be specified to narrow the broadcasts (e.g., anywhere from each of network devices 32 in the domain, to a single network device specific to the switch). This feature would effectively allow a change power state request to be tunneled over the underlying protocol (e.g., EnergyWise protocol).
- a network domain of devices may use a protocol (e.g., EnergyWise protocol) to transmit multiple change power state requests based on selection criteria that does not include a MAC address.
- the selection criteria may include all network devices 32 in a specific department or all network devices 32 that are at (or above) a security level.
- the MAC address of the network device(s) matching the selection criteria can be determined by switch 34 .
- the switch can determine the MAC address for the network devices assigned to the switch that are above the certain security level. In this manner, one or more network devices can be requested to change power states with a single filter criterion.
- the network domain of devices may include controller 20 . While controller 20 can initiate the request, controller 20 does not necessarily need to know the MAC address of network devices 32 , or which switches 34 are assigned to each network device 32 .
- the architecture of energy management system 10 allows for the management of network devices (e.g., personal computers (PCs)) connected to switches, wireless access point, etc. using the network to monitor, control, and (ultimately) save energy.
- the architecture has the ability to issue, distribute, and deliver change power state requests (e.g., wake-on-LAN messages) throughout energy management system 10 .
- Any of the components of energy management system 10 can readily communicate a broadcast message that requests certain network devices to shift from one power state to another power state. This broadcast message can be triggered based on specific policies, based on administrator preferences/provisioning, based on cost considerations, etc.
- the broad term ‘message’ is inclusive of the previously mentioned items (e.g., requests to change power state) and any other suitable network message that can be communicated from one location to another.
- the actual message can be received, and then forwarded (in its entirety, or at least a part of the message) based on certain criteria, as discussed herein.
- a message is received for network devices to enter into low power state (e.g., a message indicating network devices 32 should enter into a hibernation state)
- a broadcast message can be communicated to each network device, where the broadcast message is requesting/instructing the network devices to shift from a normal operating state to a hibernation state. This would reduce the power being consumed over this time interval.
- Switch 34 is configured to send out appropriate messages to network devices 32 , to selected network devices 32 , to selected groups of network devices 32 , etc. in order to instruct them that they should switch power states.
- the network devices are configured to interpret the broadcast messages such that network devices 32 can readily switch power states.
- the broadcast messages received by network devices 32 can include an assigned time interval for the network devices to remain in the power state. Additional instructions can indicate particular states for transitioning from the power state (e.g., transitioning to a normal operating state after being in a hibernation state for the requisite time interval).
- Management applications 12 can communicate with designated network devices 32 using various communication protocols.
- the communication is delivered over a wired network.
- a wireless access point can deliver the communication wirelessly via management frames in a corresponding 802.11 message.
- an Energy Efficient Ethernet protocol e.g., IEEE 802.3az
- Other protocols can include proprietary mechanisms, unicasting activities, multicasting activities, simple TCP/IP communications, user datagram protocol (UDP) communications, appropriate discovery protocols, etc.
- demand response broadcast messages instruct the devices to shift into different power states.
- the broadcast message can include a WindowsTM PowerCfg command, which instructs a network device to switch power states.
- existing protocols in network devices can be used as a mechanism to affect the power state change.
- DASH Desktop and mobile Architecture for System Hardware
- vPro e.g., in Intel environments
- WMI Windows Management Instrumentation
- WMI is simply an API in the Windows operating system that enables devices and systems in a network (e.g., typically enterprise networks) to be managed and controlled.
- CIM common information model
- network devices 32 are configured to enter into a different power state based on any number of potential options. For example, one option may be associated with a timeout message provided in the request to switch power states. The message would indicate, for example, to switch to a hibernation state for the next four hours. Another option would involve a second message sent to instruct network devices 32 to enter into a new power state (e.g., a normal operational power state after being in a hibernation state). Still other options can involve default-timing mechanisms (specific to each network device 32 ) such that network devices 32 would automatically shift to their normal power state after some predefined time interval (e.g., 60 minutes, etc.).
- some predefined time interval e.g. 60 minutes, etc.
- certain infrastructure may be aware of whether network devices 32 have the option of changing power states.
- the switch to which network devices 32 are connected would know that each network device 32 has several different power states (power options).
- Other mechanisms for knowing the power state options of network devices 32 (before the power state change signals are sent) can involve simple provisioning by an administrator, discovery mechanisms when network devices 32 come online, querying activities involving individual network devices 32 , etc.
- the different power states may include a normal operating power state, a reduced or low power state, a hibernation power state, etc.
- the architecture of energy management system 10 is configured to intelligently control power from the network perspective.
- the architecture of energy management system 10 allows network and network-attached equipment to take advantage of a configuration that includes no central processing and no central repository.
- Such a configuration also offers the advantage of having no single point of failure.
- the group devices of a cloud i.e., the network
- Controller 20 can be representative of a single computing device, which could be provisioned virtually anywhere in the network, or a plurality of controllers 20 can be provisioned at strategic locations in the network, as further described below.
- the configuration of energy management system 10 is protocol agnostic, where various communication transports can be used.
- the architecture also fosters cloud computing to be done to a variable number of entities (all of which may have different types of ASICS, OSs, etc.).
- Dynamically, network devices 32 can join and leave the heterogeneous environment, where various types of network devices 32 can be readily managed by energy management system 10 .
- energy management system 10 enables businesses to monitor and to control the electric consumption of networking equipment.
- An administrator can monitor devices like switches and routers, as well as LAN switch connected Power over Ethernet (PoE) devices such as phones, access points, IP security cameras, door access equipment, etc.
- PoE Power over Ethernet
- Energy management system 10 also has the ability to monitor and to control the energy demands of AC powered devices such as smart power distribution units, networked building systems, office equipment, etc.
- Energy management system 10 also includes an open interface to allow 3rd party management systems to participate in the framework. This simplifies integration of power reporting and automation for existing business practices.
- the system of FIG. 1 can leverage a simple network management protocol (SNMP) and a secure socket layer (SSL) protocol [as part of a management application program interface (API)] to execute any of the functions of the present disclosure.
- Management applications 12 can be tailored for particular facilities, or configured for specific IT scenarios. Management applications 12 can also be configured to correlate power data with location, and then allocate power accordingly.
- Switches and routers can readily communicate through a management API, where the network can aggregate status and power information. In terms of a client protocol mechanism, this element can communicate status and receive policies.
- a management information base can be available on each enabled network device and, further, can include power usage, power policy, alarms, etc.
- the MIB can also provide per-device information.
- Network management systems interested in a network-wide query can use the SSL interface.
- the SSL interface can allow a single switch to query/set information from/to certain switches in a domain.
- FIG. 2A is a simplified block diagram illustrating one possible set of details associated with energy management system 10 .
- FIG. 2A includes controller 20 , network 22 , switches 34 , and subnets 18 , which may include one or more network devices (not shown for purposes of simplicity).
- Each switch 34 may include an instance of wake-on-LAN module 26 to communicate change power state requests to network devices 32 .
- Wake-on-LAN module 26 may include a processor 40 and a network memory element 38 , which may include a selection criteria database 46 .
- subnets 18 may include switches, routers, network controllers, gateways, network appliances, or any other suitable network infrastructure, which make up the data network proper (as well as network devices 32 not shown).
- Subnets 18 are much like a community in network management, where each subnet 18 can form a unit of power management. Hence, subnets 18 can be viewed as a logical group of entity devices. Additionally, managers (e.g., control applications) can be used to measure, monitor, and/or manage power consumption.
- subnet 18 members e.g., the switches and the routers
- Keywords can be used to tag devices in subnet 18 with labels to filter searches or queries.
- the keywords can be stored in selection criteria database 46 of switch 34 (or at any other suitable location), where these keywords can be used to identify specific devices or groups of devices with common attributes (e.g., devices in a building lobby, related to security, etc.).
- the actual queries can determine energy usage, set power levels and/or power states across the network.
- the actual power level can indicate the power state of an entity.
- devices can be differentiated by how they would be affected by power state changes. For example, critical devices (e.g., stairway lighting, HVAC, fire alarms, etc.) would have a higher priority than noncritical devices (e.g., charging laptops, courtesy phones provided a lobby, etc.).
- policies can be set with a network-based query to make power state changes (e.g., return all devices on the first three floors of a building to a normal operating state at 7:00 a.m.).
- the network query can be initiated by controller 20 , sent to one or more switch(s) 34 , and then propagated across subnet(s) 18 , which contain the devices that satisfy the network query.
- tags or keywords are available in energy management system 10 , and these can be used to improve the search capability of a network-based query.
- Any arbitrary set of keywords can be defined per port, per network device, per subnet, or using any other suitable criteria.
- a given client such as a PC can have specific keywords stored within the device such that, as the client moves between ports or subnets 18 , the keywords can follow the device.
- controller 20 may determine which devices in each subnet 18 should change power states. Controller 20 can send a change power state request to each switch 34 . Each switch 34 can then locally broadcast the change power state request to each device (in subnet 18 ) that is associated with the switch. Controller 20 does not need to know which devices (or how many devices) are in each subnet 18 because that information can be managed elsewhere (e.g., by wake-on-LAN module 26 ).
- controller 20 may determine that a specific subnet or a specific device in a subnet should change power state. Controller 20 can then send a change power state request to each switch 34 , where the change power state request can include a specific MAC address, or set of MAC addresses. After receiving the change power state request, each switch 34 can determine if the MAC address matches a MAC address in selection criteria database 46 for switch 34 . If the MAC address matches a MAC address in selection criteria database 46 , then switch 34 can locally broadcast the change power state request to the device that is associated with the MAC address. A device matching the MAC address in the change power state request can receive the change power state request from switch 34 .
- controller 20 may determine that a specific group of devices should change power state. Controller 20 can then send a change power state request to each switch 34 , where the change power state request includes certain filter criteria (e.g., only devices that are non-essential devices should change power state, only devices that are located on a certain floor of a building should change state, etc.). Each switch 34 can then determine if the filter criteria matches data in selection criteria database 46 . Switch 34 can locally broadcast the change power state request to the devices in subnet 18 that match the filter criteria. Controller 20 does not need to know the MAC address of the devices, or where the devices are located in the network, or which switches control the devices that should change power state. If the filter criteria matches filter criteria in selection criteria database 46 in switch 34 , then the switch would determine the MAC address of the network device(s) that should receive the change power state request.
- filter criteria e.g., only devices that are non-essential devices should change power state, only devices that are located on a certain floor of a building should change state, etc.
- Controller 20 can maintain any number of data (e.g., tables, lists, policies, etc.) that can be used in the management of the architecture.
- the data can reveal a given network device's identification or ID, the network device's role, the domain of the network device, the importance/priority of the network device, the current state of the network device, a respective management interface for the network device, any keywords or filter criteria associated with the network device, etc.
- Power policies can be sent to each switch 34 , where the policies can be propagated to individual network devices. For example, a policy could be propagated to switches 34 to indicate to shut down phones in a building at 8 PM. Another example could involve moving HVAC systems to certain levels after the workday has concluded. Another example could involve switching to a hibernation state for all PCs during a lunch hour (e.g., 12 PM-1 PM).
- controller 20 and/or wake-on-LAN module 26 can include software to facilitate energy management operations.
- controller 20 and/or wake-on-LAN module 26 may include software that is configured to intelligently evaluate an opportune time for sending broadcast messages to the network devices for switching between power states.
- network access can be leveraged to offer the capability for an end user to control energy parameters in a given domain.
- Controller 20 is a network element configured to interact with switches 34 in order to manage energy usage of network devices 32 in energy management system 10 .
- controller 20 can readily be part of a server in certain embodiments of this architecture, or provisioned in conjunction with management applications 12 , or provisioned in any other suitable device or network location.
- the term ‘network element’ is meant to encompass proprietary devices, servers, network appliances, routers, switches, management appliances, gateways, bridges, loadbalancers, firewalls, processors, modules, or any other suitable device, note, proprietary component, element, or object operable to exchange information in a network environment.
- the network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.
- Software for providing intelligent energy management functionalities can be provided at various locations.
- this software is resident in a network element (e.g., provisioned in controller 20 , wake-on-LAN module 26 , etc.).
- this could involve combining domain devices, controller 20 and/or switch 34 with an application server, a firewall, a gateway, or some proprietary element, which could be provided in (or be proximate to) these identified network elements, or this could be provided in any other device being used in a given network.
- each network device 32 , switch 34 (inclusive of wake-on-LAN module 26 ), and/or each instance of controller 20 may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate these energy management operations. This may be inclusive of appropriate communication protocols that allow for the effective exchange of data or information for achieving energy management in a network environment.
- network devices 32 can include an agent (for example, in software) that allows network devices 32 to respond to broadcast messages from the network.
- agent for example, in software
- broadcast message as used herein in this Specification is meant to encompass any type of signaling, packet information, messaging, short message service (SMS) communications, instant messaging (IM), e-mail protocols, or any other message type that can be delivered to a network device such that it understands to switch between available power states.
- SMS short message service
- IM instant messaging
- e-mail protocols or any other message type that can be delivered to a network device such that it understands to switch between available power states.
- the energy management features may be provided externally to controller 20 , switch 34 , and/or network devices 32 , or included in some other network device, or in a computer to achieve these intended functionalities.
- FIG. 2B is a simplified block diagram illustrating one possible set of details associated with energy management system 10 .
- FIG. 2B includes a number of subnets 18 a - c , which are coupled to switch 34 .
- Each of subnets 18 a - c can include any number of network devices 32 a - g (with accompanying infrastructure) provisioned in any suitable computing environment.
- switch 34 can determine which network devices 32 a - g are associated with switch 34 , specific keywords associated with each network device 32 a - g , the MAC address of each network device 32 a - g , etc.
- Energy management system 10 is configured to leverage the network to enable monitoring and controlling of connected network devices 32 a - g through switch 34 .
- the architecture allows the network to form a control plane for energy management and, further, offers IT organizations a tool for managing energy more effectively.
- Network devices 32 a - g are representative of power consumers of any kind.
- network devices 32 a - g can be representative of PoE and non-PoE devices that can connect to the network.
- network devices 32 a - g can include nontraditional network devices such as facility controllers, lighting, heating ventilation, and air conditioning (HVAC), etc.
- HVAC heating ventilation, and air conditioning
- network device can also be inclusive of devices used to initiate a communication, such as a switch, a console, a proprietary endpoint, a telephone, a bridge, a computer, a personal digital assistant (PDA), a laptop or electronic notebook, an i-Phone, an iPad, a Google Droid, any other type of smartphone, a Telepresence system, an access point, a router, a switch, a gateway, a server, or any other device, component, element, or object capable of facilitating voice, audio, or data exchanges within energy management system 10 .
- PDA personal digital assistant
- Network devices 32 a - g may also be inclusive of a suitable interface to an end user, such as a microphone, a display, or a keyboard or other terminal equipment.
- Network devices 32 a - g may also include any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange within energy management system 10 .
- Data refers to any type of video, numeric, voice, packet, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another.
- example network protocols can include WakeOnLan, DASH, SMASH, and VPRO.
- example non-network protocols can include toggling power on a PoE port, PDU plug, and a virtual circuit breaker.
- a switch or management station could determine which protocol to use to wake up a device (e.g., based on which protocol(s) the device supports).
- the architecture of the present disclosure can use a WakeOnNetwork protocol, which refers to the device capability to support protocols such as WakeOnLan, SMASH, DASH, VPRO, or other protocols, that effectively change energy state (e.g., wake-up a device) such that the device transitions from a non-operational to an operational state.
- Operational and non-operational levels can be defined by power levels 0-10.
- Non-operational state could be, for example, 0 shut off, 1 hibernate, 2 sleep.
- operational states could be, for example, 3 standby, 4 ready, 5 low, 6 frugal, 7 medium, 8 reduced, 9 high, 10 full.
- discovery packets received from endpoints can contain a WakeOnNetwork (WoN) capability vector that indicates which types of WoN protocols it supports. This data can be stored by the switch for each endpoint. Based on the device's WakeOnNetwork capability vector (and other configurable parameters), the switch can compose a WoN packet. Separately, the switch can use the cached MAC address, and send the WoN packet to the device.
- WiN WakeOnNetwork
- a given device can be configured to inform the switch which protocol(s) are supported and, based on this information, the switch can compose the appropriate packet, or other mechanisms to change the energy state of the device.
- the device can provide configurations in addition to the WoN capability vector.
- the device can also provide a UDP port number to be used when the switch transmits WoN packets.
- the device may provide values for certain power levels that are relevant to WoN, such as maximum non-operational level, and minimum operational level. Such levels can be used to determine if WakeOnNetwork is indicated for a particular situation.
- FIG. 3 is a simplified flowchart 300 illustrating example activities of network enabled energy management provisioning for a device.
- a network domain controller determines which devices associated with a subnet should receive a change for a power request.
- controller 20 may determine which network devices 32 should receive a change power state request.
- the change of power request can be communicated to a switch, which is associated with each device that is to receive the change power state request.
- controller 20 may communicate the change in power request to switch 34 .
- the switch receives the change power state request and communicates the change power state request to the device.
- switch 34 may communicate the change of power request to each network device 32 in subnet 18 .
- the device can transition from one power state to a different power state (e.g., a non-operable state to an operable state).
- FIG. 4 is a simplified flowchart 400 illustrating example activities of network-enabled energy management provisioning for a device.
- a change power request is received at a switch associated with a subnet.
- switch 34 may be associated with subnet 18 and receive a switch power request from controller 20 .
- the system determines if the change power request is for the entire subnet.
- switch 34 may determine if the change power request is for the entire subnet 18 . If the change power request is for the entire subnet, then a change power request is sent to the entire subnet, as illustrated in 408 . If the change power request is not for the entire subnet, then a change power request is sent to the devices designated in the change power request, as illustrated in 408 .
- switch 34 may send the change power request to only network devices 32 designated in the change power request (or switch 34 may use priority characteristics to determine a subset of network devices for which the message should be sent).
- FIG. 5 is a simplified flowchart 500 illustrating example activities of network-enabled energy management provisioning for a device.
- a switch receives a change power request for a device.
- switch 34 may receive a change power request from controller 20 .
- the system determines if a keyword or MAC address in the change power request matches a keyword or MAC address in a database associated with the switch.
- switch 34 may determine if a keyword or MAC address in the change power request matches a keyword or MAC address in selection criteria database 46 . If the keyword or MAC address does not match a keyword or MAC address in the database associated with the switch, then the change power request is ignored, as illustrated in 506 .
- the change power request is sent to the device associated with the keyword or MAC address, as illustrated in 508 .
- specific network devices 32 may be identified, and the change power request can be communicated to the identified network devices 32 .
- a network element can include software to achieve the energy management operations, as outlined herein in this document.
- the energy management functions outlined herein may be implemented by logic encoded in one or more non-transitory tangible media (e.g., embedded code provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by a processor [processor 40 shown in FIGS. 2A and 2B ], or other similar machine, etc.).
- ASIC application specific integrated circuit
- DSP digital signal processor
- a memory element network memory element 38 shown in FIGS. 2A and 2B
- the processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification.
- the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing.
- the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.
- FPGA field programmable gate array
- EPROM erasable programmable read only memory
- EEPROM electrically erasable programmable ROM
- any of these elements can include memory elements for storing information to be used in achieving the energy management activities as outlined herein.
- each of these devices may include a processor that can execute software or an algorithm to perform the energy management activities as discussed in this Specification.
- These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs.
- RAM random access memory
- ROM read only memory
- EPROM Erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- ASIC application specific integrated circuitry
- any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’
- any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’
- Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
- a management application can monitor power consumption and receive a peak power alert.
- a policy can be created to minimize this peak consumption by leveraging power states. Part of this policy may include identifying eligible phones, laptops, and building HVAC systems that could be candidates for shifting to a low power state or hibernation state. For example, in the context of these identified devices, a laptop could move to hibernation, eligible phones could also move to a low power state, printers could move to a sleep mode or hibernation state.
- energy management system 10 (and its teachings) are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of energy management system 10 , as potentially applied to a myriad of other architectures.
- energy management system 10 may be applicable to other exchanges and protocols in which data are exchanged in order to provide energy management operations.
- energy management system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture or process that achieves the intended functionality of energy management system 10 .
Abstract
A method is provided in one example embodiment and includes receiving a message at a network element configured for routing packets, where the message directs a network device to change its power state; identifying the network device as being associated with a network for which the network element has responsibility; and communicating at least a portion of the message from the network element to the network device.
Description
- This disclosure relates in general to the field of communications and, more particularly, to a system and a method for network enabled wake for networks.
- Energy consumption has become a preeminent concern for industrialized societies. Both consumers and businesses have become aware of their energy usage. Whether motivated by altruistic reasons, or by profitability concerns, individuals have come to terms with the notion that energy is a finite commodity: a commodity having accompanying costs that should be managed. Administrators now focus on power usage and, more specifically, on how to reduce those expenditures. In recent times, device manufacturers have added instrumentation and features in the network to quell these concerns. As network systems have become more sophisticated, while energy demands have continued to increase, architectures often fail in matching network capabilities with more intelligent energy consumption.
- To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
-
FIG. 1 is a simplified block diagram of an energy management system in accordance with one embodiment of the present disclosure; -
FIG. 2A is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure; -
FIG. 2B is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure; -
FIG. 3 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure; -
FIG. 4 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure; and -
FIG. 5 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure. - A method is provided in one example embodiment and includes receiving a message at a network element configured for routing packets. The message directs a network device to change its power state. The method also includes identifying the network device as being associated with a network for which the network element has responsibility, and communicating at least a portion of the message from the network element to the network device.
- In more specific implementations, an application program interface (API) is leveraged in order to communicate the portion of the message, which identifies a media access control (MAC) address associated with the network device. In yet other embodiments, the message includes filter criteria to be used to identify the network device. In addition, the method may include searching a selection criteria database to identify the network device identified by the filter criteria. In more specific implementations, the filter criteria is used to identify a group of network devices for which a subsequent message for changing power states is intended. The network device can be part of a subnet associated with the network element.
-
FIG. 1 is a simplified block diagram of anenergy management system 10 in accordance with one example implementation of the present disclosure.FIG. 1 includes asubnet 18, which can include any number ofnetwork devices 32.Subnet 18 is typically a logically visible subdivision of an internet protocol (IP) network; however,subnet 18 can be any network that allows a switch to communicate with, control, and/or managenetwork devices 32 insubnet 18. Acontroller 20 can be provisioned in anetwork 22 in order to execute certain power management activities discussed herein. A number ofswitches 34 are also provisioned innetwork 22. In certain implementations, eachswitch 34 may contain a wake-on-local area network (LAN)module 26. Wake-on-LAN module 26 can be configured to send change power state requests tonetwork devices 32 at appropriate times. Additionally, agateway 28 may be provisioned innetwork 22 such that it can interface with converging-IP devices 36, as is being illustrated inFIG. 1 . - In this particular implementation of
FIG. 1 , the infrastructure ofsubnet 18 can interact with a number of network devices 32 (e.g., personal computers (PCs), building controllers, wireless devices, telephones, lighting fixtures, HVAC systems, video devices (e.g., Telepresence systems), etc).Certain network devices 32 may be associated with IP devices having corresponding Software Development Kit (SDK) elements. Similarly,gateway 28 may operate as a parent SDK for its child endpoints (e.g., a plurality of converging-IP devices 36).Subnet 18 is also coupled to a set ofpower management applications 12, which may include elements such as a LAN management element, etc.Management applications 12 can operate to intelligently control (directly or indirectly) any of the devices ofFIG. 1 . - In general terms,
energy management system 10 is configured to measure and monitor power for network devices 32 (e.g., phones, AP's, PCs, building systems, etc.) and, further, provide command and control fornetwork devices 32. The activities ofenergy management system 10 may include communicating messages toindividual network devices 32 for shifting from one power state to a different power state (e.g., shifting from a normal operating state to a hibernation state), as further detailed below. - In operation,
energy management system 10 provides a mechanism that understands the power consumption characteristics ofnetwork devices 32 for which it has responsibility. This can include understanding whichnetwork devices 32 can shift from one power state (e.g., a normal operating state) to a different power state (e.g., a hibernation, sleep mode, or shut down state). Additionally, the architecture is configured to query for power information using the network and, furthermore, implement time-of-day policies to controlnetwork devices 32. In essence, the network can operate as a control plane for controlling the energy consumption/usage for one ormore network devices 32 withinsubnet 18. In this sense, the network serves as a platform for intelligent energy control. From a practical perspective, the smart loading capabilities of the architecture allow for a tangible cost savings for an associated enterprise. - For purposes of illustrating certain example techniques of
energy management system 10, it is important to understand howenergy management system 10 provides command and control functions fornetwork devices 32. The infrastructure ofsubnet 18 can interact with a number of network devices 32 (e.g., a local storage module, personal computers (PCs), building controllers, wireless devices, telephones, lighting fixtures, HVAC systems, video devices (e.g., Telepresence systems), etc.). The wake-on-LAN technology ofenergy management system 10 can enablenetwork devices 32 to be remotely awaken from a hibernating or sleep state. In one particular instance, the wake-on-LAN mechanism uses a management station to broadcast a “magic packet” containing a media access control (MAC) address of atarget network device 32. The terms wake-on-LAN, wake-on-LAN technology, wake-on-LAN requests, etc. generally refer to any suitable request for the transition of a device from one power state to a different power state. A network card on a wake-on-LAN enablednetwork device 32 is kept powered so when the network card sees its MAC address contained in a wake-on-LAN message, the network card initiates a power-up of the network device. However, the broadcast mechanism of directing wake-on-LAN requests can be difficult to deploy in an enterprise network because security policies in routers typically drop subnet directed broadcasts, thus preventing wake-on-LAN messages from being received. For this reason, wake-on-LAN is often restricted to working on local area networks instead of working on other networks (e.g., an enterprise wide area network (WAN)). - In one particular example involving the use of a proxy model, the wake-on-LAN feature may be provided in enterprise WAN networks. In such an example, one or
more network devices 32 in a subnet can remain powered on and run a special software agent, which is used to locally broadcast a received wake-on-LAN payload within the subnet. For example, one or more powered onnetwork devices 32 can receive a unicast transmission of a wake-on-LAN message. In response, a wake-on-LAN message can be broadcast within the subnet by one or more of the powered onnetwork devices 32, which effectively circumvents the problem of routers dropping global broadcasts. However, while functional, the proxy model has several disadvantages including the requirement of vendor software, the installation of the vendors network devices' agent across the enterprise, the necessity ofdedicated network devices 32 to remain powered on, and the failure issues when the agent is down or otherwise unreachable. In addition, enterprises with many small subnets may find leaving one or twonetwork devices 32 active (e.g., per subnet) can significantly diminish their energy savings of reducing energy consumption for network devices 32 (e.g., to sleep during off peak hours). - The architecture of
FIG. 1 can overcome these shortcomings (and others) in leveraging a network element (e.g., a switch) to be utilized as a local broadcaster for a request to change power states (e.g., a wake-on-LAN request). In at least one sense, the network element (e.g., a switch, a router, a gateway, etc.) receiving the message can have responsibility for one or more network devices for which the message was intended (e.g., the network element has an association with the network device, has a relationship with the network device, has been entrusted to manage the network device, has a geographical congruency with the network device, shares some commonality with device, has been assigned power management for the network device, shares a subnet with the network device, etc.). - In more specific instances, this can involve using a command-line interface (CLI), a simple network management protocol (SNMP), or other available management application programming interfaces (APIs). These mechanisms allow
controller 20 to transmit a change power state request for network device(s) 32 to switch 34, which can then locally broadcast a change power state request to network device(s) 32 in alocal subnet 18 assigned to switch 34. [Note that more than onesubnet 18 may be assigned to switch 34]. - In another example embodiment, a network domain of devices may use a protocol (e.g., an EnergyWise protocol) to transmit a change power state request based on a MAC address (or other addresses) to
switches 34 residing in the network domain. Eachswitch 34, after checking certain filter criteria, can locally broadcast the change power state request to network device(s) 32 in the local subnet(s) assigned to switch 34. In this example, network device(s) 32 matching the MAC address(es) in the change power state request would be awoken. Additionally, filter criteria can be specified to narrow the broadcasts (e.g., anywhere from each ofnetwork devices 32 in the domain, to a single network device specific to the switch). This feature would effectively allow a change power state request to be tunneled over the underlying protocol (e.g., EnergyWise protocol). - In yet another example embodiment, a network domain of devices may use a protocol (e.g., EnergyWise protocol) to transmit multiple change power state requests based on selection criteria that does not include a MAC address. For example, the selection criteria may include all
network devices 32 in a specific department or allnetwork devices 32 that are at (or above) a security level. In this model, the MAC address of the network device(s) matching the selection criteria can be determined byswitch 34. - For example, if the selection criteria includes network devices above a certain security level, then the switch can determine the MAC address for the network devices assigned to the switch that are above the certain security level. In this manner, one or more network devices can be requested to change power states with a single filter criterion. The network domain of devices may include
controller 20. Whilecontroller 20 can initiate the request,controller 20 does not necessarily need to know the MAC address ofnetwork devices 32, or which switches 34 are assigned to eachnetwork device 32. - In operation, the architecture of
energy management system 10 allows for the management of network devices (e.g., personal computers (PCs)) connected to switches, wireless access point, etc. using the network to monitor, control, and (ultimately) save energy. The architecture has the ability to issue, distribute, and deliver change power state requests (e.g., wake-on-LAN messages) throughoutenergy management system 10. Any of the components ofenergy management system 10 can readily communicate a broadcast message that requests certain network devices to shift from one power state to another power state. This broadcast message can be triggered based on specific policies, based on administrator preferences/provisioning, based on cost considerations, etc. No that as used herein in this Specification, the broad term ‘message’ is inclusive of the previously mentioned items (e.g., requests to change power state) and any other suitable network message that can be communicated from one location to another. The actual message can be received, and then forwarded (in its entirety, or at least a part of the message) based on certain criteria, as discussed herein. - Consider an example campus network deployment, where users are not using their network devices 32 (e.g., at night). If a message is received for network devices to enter into low power state (e.g., a message indicating
network devices 32 should enter into a hibernation state), a broadcast message can be communicated to each network device, where the broadcast message is requesting/instructing the network devices to shift from a normal operating state to a hibernation state. This would reduce the power being consumed over this time interval. -
Switch 34 is configured to send out appropriate messages to networkdevices 32, to selectednetwork devices 32, to selected groups ofnetwork devices 32, etc. in order to instruct them that they should switch power states. In one particular example, the network devices are configured to interpret the broadcast messages such thatnetwork devices 32 can readily switch power states. In certain implementations, the broadcast messages received bynetwork devices 32 can include an assigned time interval for the network devices to remain in the power state. Additional instructions can indicate particular states for transitioning from the power state (e.g., transitioning to a normal operating state after being in a hibernation state for the requisite time interval). -
Management applications 12 can communicate with designatednetwork devices 32 using various communication protocols. In one example, the communication is delivered over a wired network. In other instances, a wireless access point can deliver the communication wirelessly via management frames in a corresponding 802.11 message. Note that in particular use cases, an Energy Efficient Ethernet protocol (e.g., IEEE 802.3az) can be involved in such messaging. Other protocols can include proprietary mechanisms, unicasting activities, multicasting activities, simple TCP/IP communications, user datagram protocol (UDP) communications, appropriate discovery protocols, etc. - In one example operation, demand response broadcast messages instruct the devices to shift into different power states. In particular implementations involving personal computers, the broadcast message can include a Windows™ PowerCfg command, which instructs a network device to switch power states. Moreover, existing protocols in network devices can be used as a mechanism to affect the power state change. For example, ‘Desktop and mobile Architecture for System Hardware’ (DASH) and vPro (e.g., in Intel environments) can be leveraged to achieve this activity. In other instances, Windows Management Instrumentation (WMI) could be leveraged for initiating the change. WMI is simply an API in the Windows operating system that enables devices and systems in a network (e.g., typically enterprise networks) to be managed and controlled. Often utilizing common information model (CIM), WMI allows network administrators to query and manage workstations, applications, networks, etc.
- Operationally,
network devices 32 are configured to enter into a different power state based on any number of potential options. For example, one option may be associated with a timeout message provided in the request to switch power states. The message would indicate, for example, to switch to a hibernation state for the next four hours. Another option would involve a second message sent to instructnetwork devices 32 to enter into a new power state (e.g., a normal operational power state after being in a hibernation state). Still other options can involve default-timing mechanisms (specific to each network device 32) such thatnetwork devices 32 would automatically shift to their normal power state after some predefined time interval (e.g., 60 minutes, etc.). - Note that certain infrastructure may be aware of whether
network devices 32 have the option of changing power states. For example, in an EnergyWise™ domain, the switch to whichnetwork devices 32 are connected would know that eachnetwork device 32 has several different power states (power options). Other mechanisms for knowing the power state options of network devices 32 (before the power state change signals are sent) can involve simple provisioning by an administrator, discovery mechanisms whennetwork devices 32 come online, querying activities involvingindividual network devices 32, etc. The different power states may include a normal operating power state, a reduced or low power state, a hibernation power state, etc. - A number of advantages can be achieved by the architecture of
energy management system 10. For example, the architecture is configured to intelligently control power from the network perspective. Hence, the architecture ofenergy management system 10 allows network and network-attached equipment to take advantage of a configuration that includes no central processing and no central repository. Such a configuration also offers the advantage of having no single point of failure. The group devices of a cloud (i.e., the network) can be self-managed, where there is no central control.Controller 20 can be representative of a single computing device, which could be provisioned virtually anywhere in the network, or a plurality ofcontrollers 20 can be provisioned at strategic locations in the network, as further described below. - Separately, the configuration of
energy management system 10 is protocol agnostic, where various communication transports can be used. The architecture also fosters cloud computing to be done to a variable number of entities (all of which may have different types of ASICS, OSs, etc.). Dynamically,network devices 32 can join and leave the heterogeneous environment, where various types ofnetwork devices 32 can be readily managed byenergy management system 10. - As a stand-alone solution,
energy management system 10 enables businesses to monitor and to control the electric consumption of networking equipment. An administrator can monitor devices like switches and routers, as well as LAN switch connected Power over Ethernet (PoE) devices such as phones, access points, IP security cameras, door access equipment, etc.Energy management system 10 also has the ability to monitor and to control the energy demands of AC powered devices such as smart power distribution units, networked building systems, office equipment, etc.Energy management system 10 also includes an open interface to allow 3rd party management systems to participate in the framework. This simplifies integration of power reporting and automation for existing business practices. - Briefly discussing some of the possible signaling mechanisms of the architecture, the system of
FIG. 1 can leverage a simple network management protocol (SNMP) and a secure socket layer (SSL) protocol [as part of a management application program interface (API)] to execute any of the functions of the present disclosure.Management applications 12 can be tailored for particular facilities, or configured for specific IT scenarios.Management applications 12 can also be configured to correlate power data with location, and then allocate power accordingly. Switches and routers can readily communicate through a management API, where the network can aggregate status and power information. In terms of a client protocol mechanism, this element can communicate status and receive policies. - In regards to the management API for
management applications 12, there can be several methods for a management application to communicate with the network (e.g., SNMP, SSL, etc.). A management information base (MIB) can be available on each enabled network device and, further, can include power usage, power policy, alarms, etc. The MIB can also provide per-device information. Network management systems interested in a network-wide query can use the SSL interface. The SSL interface can allow a single switch to query/set information from/to certain switches in a domain. - Turning to
FIG. 2A ,FIG. 2A is a simplified block diagram illustrating one possible set of details associated withenergy management system 10.FIG. 2A includescontroller 20,network 22, switches 34, andsubnets 18, which may include one or more network devices (not shown for purposes of simplicity). Eachswitch 34 may include an instance of wake-on-LAN module 26 to communicate change power state requests to networkdevices 32. Wake-on-LAN module 26 may include aprocessor 40 and anetwork memory element 38, which may include aselection criteria database 46. - Members of
subnets 18 may include switches, routers, network controllers, gateways, network appliances, or any other suitable network infrastructure, which make up the data network proper (as well asnetwork devices 32 not shown).Subnets 18 are much like a community in network management, where eachsubnet 18 can form a unit of power management. Hence,subnets 18 can be viewed as a logical group of entity devices. Additionally, managers (e.g., control applications) can be used to measure, monitor, and/or manage power consumption. - In terms of relationships,
subnet 18 members (e.g., the switches and the routers) can operate as “neighbors” while establishing “parent-child” relationships with network devices in eachsubnet 18. Keywords can be used to tag devices insubnet 18 with labels to filter searches or queries. The keywords can be stored inselection criteria database 46 of switch 34 (or at any other suitable location), where these keywords can be used to identify specific devices or groups of devices with common attributes (e.g., devices in a building lobby, related to security, etc.). The actual queries can determine energy usage, set power levels and/or power states across the network. The actual power level can indicate the power state of an entity. In regards to importance (priority), devices can be differentiated by how they would be affected by power state changes. For example, critical devices (e.g., stairway lighting, HVAC, fire alarms, etc.) would have a higher priority than noncritical devices (e.g., charging laptops, courtesy phones provided a lobby, etc.). - Additionally, policies can be set with a network-based query to make power state changes (e.g., return all devices on the first three floors of a building to a normal operating state at 7:00 a.m.). The network query can be initiated by
controller 20, sent to one or more switch(s) 34, and then propagated across subnet(s) 18, which contain the devices that satisfy the network query. - The ability to create tags or keywords is available in
energy management system 10, and these can be used to improve the search capability of a network-based query. Any arbitrary set of keywords can be defined per port, per network device, per subnet, or using any other suitable criteria. For example, a given client such as a PC can have specific keywords stored within the device such that, as the client moves between ports orsubnets 18, the keywords can follow the device. - In an embodiment,
controller 20 may determine which devices in eachsubnet 18 should change power states.Controller 20 can send a change power state request to eachswitch 34. Eachswitch 34 can then locally broadcast the change power state request to each device (in subnet 18) that is associated with the switch.Controller 20 does not need to know which devices (or how many devices) are in eachsubnet 18 because that information can be managed elsewhere (e.g., by wake-on-LAN module 26). - In another embodiment,
controller 20 may determine that a specific subnet or a specific device in a subnet should change power state.Controller 20 can then send a change power state request to eachswitch 34, where the change power state request can include a specific MAC address, or set of MAC addresses. After receiving the change power state request, eachswitch 34 can determine if the MAC address matches a MAC address inselection criteria database 46 forswitch 34. If the MAC address matches a MAC address inselection criteria database 46, then switch 34 can locally broadcast the change power state request to the device that is associated with the MAC address. A device matching the MAC address in the change power state request can receive the change power state request fromswitch 34. - In another embodiment,
controller 20 may determine that a specific group of devices should change power state.Controller 20 can then send a change power state request to eachswitch 34, where the change power state request includes certain filter criteria (e.g., only devices that are non-essential devices should change power state, only devices that are located on a certain floor of a building should change state, etc.). Eachswitch 34 can then determine if the filter criteria matches data inselection criteria database 46.Switch 34 can locally broadcast the change power state request to the devices insubnet 18 that match the filter criteria.Controller 20 does not need to know the MAC address of the devices, or where the devices are located in the network, or which switches control the devices that should change power state. If the filter criteria matches filter criteria inselection criteria database 46 inswitch 34, then the switch would determine the MAC address of the network device(s) that should receive the change power state request. -
Controller 20 can maintain any number of data (e.g., tables, lists, policies, etc.) that can be used in the management of the architecture. For example, the data can reveal a given network device's identification or ID, the network device's role, the domain of the network device, the importance/priority of the network device, the current state of the network device, a respective management interface for the network device, any keywords or filter criteria associated with the network device, etc. - Power policies can be sent to each
switch 34, where the policies can be propagated to individual network devices. For example, a policy could be propagated toswitches 34 to indicate to shut down phones in a building at 8 PM. Another example could involve moving HVAC systems to certain levels after the workday has concluded. Another example could involve switching to a hibernation state for all PCs during a lunch hour (e.g., 12 PM-1 PM). - In one example implementation,
controller 20 and/or wake-on-LAN module 26 can include software to facilitate energy management operations. For example,controller 20 and/or wake-on-LAN module 26 may include software that is configured to intelligently evaluate an opportune time for sending broadcast messages to the network devices for switching between power states. In example embodiments, network access can be leveraged to offer the capability for an end user to control energy parameters in a given domain. -
Controller 20 is a network element configured to interact withswitches 34 in order to manage energy usage ofnetwork devices 32 inenergy management system 10. Note thatcontroller 20 can readily be part of a server in certain embodiments of this architecture, or provisioned in conjunction withmanagement applications 12, or provisioned in any other suitable device or network location. As used herein in this Specification, the term ‘network element’ is meant to encompass proprietary devices, servers, network appliances, routers, switches, management appliances, gateways, bridges, loadbalancers, firewalls, processors, modules, or any other suitable device, note, proprietary component, element, or object operable to exchange information in a network environment. Moreover, the network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information. - Software for providing intelligent energy management functionalities can be provided at various locations. In one example implementation, this software is resident in a network element (e.g., provisioned in
controller 20, wake-on-LAN module 26, etc.). In other examples, this could involve combining domain devices,controller 20 and/or switch 34 with an application server, a firewall, a gateway, or some proprietary element, which could be provided in (or be proximate to) these identified network elements, or this could be provided in any other device being used in a given network. In other embodiments, eachnetwork device 32, switch 34 (inclusive of wake-on-LAN module 26), and/or each instance ofcontroller 20 may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate these energy management operations. This may be inclusive of appropriate communication protocols that allow for the effective exchange of data or information for achieving energy management in a network environment. - Logistically, certain items or elements can be provisioned for the intelligent energy management system to function. For example,
network devices 32 can include an agent (for example, in software) that allowsnetwork devices 32 to respond to broadcast messages from the network. Note that the term ‘broadcast message’ as used herein in this Specification is meant to encompass any type of signaling, packet information, messaging, short message service (SMS) communications, instant messaging (IM), e-mail protocols, or any other message type that can be delivered to a network device such that it understands to switch between available power states. In still other embodiments, the energy management features may be provided externally tocontroller 20,switch 34, and/ornetwork devices 32, or included in some other network device, or in a computer to achieve these intended functionalities. - Turning to
FIG. 2B ,FIG. 2B is a simplified block diagram illustrating one possible set of details associated withenergy management system 10.FIG. 2B includes a number ofsubnets 18 a-c, which are coupled to switch 34. Each ofsubnets 18 a-c can include any number ofnetwork devices 32 a-g (with accompanying infrastructure) provisioned in any suitable computing environment. Usingselection criteria database 46, switch 34 can determine whichnetwork devices 32 a-g are associated withswitch 34, specific keywords associated with eachnetwork device 32 a-g, the MAC address of eachnetwork device 32 a-g, etc.Energy management system 10 is configured to leverage the network to enable monitoring and controlling ofconnected network devices 32 a-g throughswitch 34. The architecture allows the network to form a control plane for energy management and, further, offers IT organizations a tool for managing energy more effectively. -
Network devices 32 a-g are representative of power consumers of any kind. For example,network devices 32 a-g can be representative of PoE and non-PoE devices that can connect to the network. Further,network devices 32 a-g can include nontraditional network devices such as facility controllers, lighting, heating ventilation, and air conditioning (HVAC), etc. The term ‘network device’ can also be inclusive of devices used to initiate a communication, such as a switch, a console, a proprietary endpoint, a telephone, a bridge, a computer, a personal digital assistant (PDA), a laptop or electronic notebook, an i-Phone, an iPad, a Google Droid, any other type of smartphone, a Telepresence system, an access point, a router, a switch, a gateway, a server, or any other device, component, element, or object capable of facilitating voice, audio, or data exchanges withinenergy management system 10. -
Network devices 32 a-g may also be inclusive of a suitable interface to an end user, such as a microphone, a display, or a keyboard or other terminal equipment.Network devices 32 a-g may also include any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange withinenergy management system 10. Data, as used herein, refers to any type of video, numeric, voice, packet, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another. - It should be noted that there are various protocols that can change the energy state for a device (e.g., wake-up the device). For example, example network protocols can include WakeOnLan, DASH, SMASH, and VPRO. Separately, example non-network protocols can include toggling power on a PoE port, PDU plug, and a virtual circuit breaker. In operation, a switch or management station could determine which protocol to use to wake up a device (e.g., based on which protocol(s) the device supports).
- The architecture of the present disclosure can use a WakeOnNetwork protocol, which refers to the device capability to support protocols such as WakeOnLan, SMASH, DASH, VPRO, or other protocols, that effectively change energy state (e.g., wake-up a device) such that the device transitions from a non-operational to an operational state. Operational and non-operational levels can be defined by power levels 0-10. Non-operational state could be, for example, 0 shut off, 1 hibernate, 2 sleep. In addition, operational states could be, for example, 3 standby, 4 ready, 5 low, 6 frugal, 7 medium, 8 reduced, 9 high, 10 full.
- In specific implementations of the presence disclosure, discovery packets received from endpoints can contain a WakeOnNetwork (WoN) capability vector that indicates which types of WoN protocols it supports. This data can be stored by the switch for each endpoint. Based on the device's WakeOnNetwork capability vector (and other configurable parameters), the switch can compose a WoN packet. Separately, the switch can use the cached MAC address, and send the WoN packet to the device.
- A given device can be configured to inform the switch which protocol(s) are supported and, based on this information, the switch can compose the appropriate packet, or other mechanisms to change the energy state of the device. The device can provide configurations in addition to the WoN capability vector. The device can also provide a UDP port number to be used when the switch transmits WoN packets. In addition, the device may provide values for certain power levels that are relevant to WoN, such as maximum non-operational level, and minimum operational level. Such levels can be used to determine if WakeOnNetwork is indicated for a particular situation.
-
FIG. 3 is asimplified flowchart 300 illustrating example activities of network enabled energy management provisioning for a device. At 302, a network domain controller determines which devices associated with a subnet should receive a change for a power request. For example,controller 20 may determine whichnetwork devices 32 should receive a change power state request. At 304, the change of power request can be communicated to a switch, which is associated with each device that is to receive the change power state request. For example,controller 20 may communicate the change in power request to switch 34. At 306, the switch receives the change power state request and communicates the change power state request to the device. For example, switch 34 may communicate the change of power request to eachnetwork device 32 insubnet 18. At 308, the device can transition from one power state to a different power state (e.g., a non-operable state to an operable state). -
FIG. 4 is asimplified flowchart 400 illustrating example activities of network-enabled energy management provisioning for a device. At 402, a change power request is received at a switch associated with a subnet. For example, switch 34 may be associated withsubnet 18 and receive a switch power request fromcontroller 20. At 404, the system determines if the change power request is for the entire subnet. For example, switch 34 may determine if the change power request is for theentire subnet 18. If the change power request is for the entire subnet, then a change power request is sent to the entire subnet, as illustrated in 408. If the change power request is not for the entire subnet, then a change power request is sent to the devices designated in the change power request, as illustrated in 408. For example, switch 34 may send the change power request toonly network devices 32 designated in the change power request (or switch 34 may use priority characteristics to determine a subset of network devices for which the message should be sent). -
FIG. 5 is asimplified flowchart 500 illustrating example activities of network-enabled energy management provisioning for a device. At 502, a switch receives a change power request for a device. For example, switch 34 may receive a change power request fromcontroller 20. At 504, the system determines if a keyword or MAC address in the change power request matches a keyword or MAC address in a database associated with the switch. For example, switch 34 may determine if a keyword or MAC address in the change power request matches a keyword or MAC address inselection criteria database 46. If the keyword or MAC address does not match a keyword or MAC address in the database associated with the switch, then the change power request is ignored, as illustrated in 506. If the keyword or MAC address matches a keyword or MAC address in the database associated with the switch, then the change power request is sent to the device associated with the keyword or MAC address, as illustrated in 508. For example, based on the keyword or MAC address in the change power request matching information inselection criteria database 46,specific network devices 32 may be identified, and the change power request can be communicated to the identifiednetwork devices 32. - As identified previously, a network element can include software to achieve the energy management operations, as outlined herein in this document. In certain example implementations, the energy management functions outlined herein may be implemented by logic encoded in one or more non-transitory tangible media (e.g., embedded code provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by a processor [
processor 40 shown inFIGS. 2A and 2B ], or other similar machine, etc.). In some of these instances, a memory element [network memory element 38 shown inFIGS. 2A and 2B ] can store data used for the operations described herein. This includes the memory element being able to store code (e.g., logic, software, or processor instructions) executed to carry out the activities described in this Specification. The processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof. - Any of these elements (e.g., the network elements, etc.) can include memory elements for storing information to be used in achieving the energy management activities as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the energy management activities as discussed in this Specification. These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein (e.g., a database) should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
- Note the previous examples can involve identifying peak power times in smoothing or time shifting the power usage in a given environment. For example, a management application can monitor power consumption and receive a peak power alert. A policy can be created to minimize this peak consumption by leveraging power states. Part of this policy may include identifying eligible phones, laptops, and building HVAC systems that could be candidates for shifting to a low power state or hibernation state. For example, in the context of these identified devices, a laptop could move to hibernation, eligible phones could also move to a low power state, printers could move to a sleep mode or hibernation state.
- Note that with the examples provided above, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that energy management system 10 (and its teachings) are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of
energy management system 10, as potentially applied to a myriad of other architectures. - It is also important to note that the steps in the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within,
energy management system 10. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided byenergy management system 10 in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure. - Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges involving certain protocols (e.g., UDP, SSL, SNMP, etc.),
energy management system 10 may be applicable to other exchanges and protocols in which data are exchanged in order to provide energy management operations. In addition, althoughenergy management system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture or process that achieves the intended functionality ofenergy management system 10. - Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.
Claims (20)
1. A method, comprising:
receiving a message at a network element configured for routing packets, wherein the message directs a network device to change its power state;
identifying the network device as being associated with a network for which the network element has responsibility; and
communicating at least a portion of the message from the network element to the network device.
2. The method of claim 1 , wherein an application program interface (API) is leveraged in order to communicate the portion of the message, which identifies a media access control (MAC) address associated with the network device.
3. The method of claim 1 , wherein the message includes filter criteria to be used to identify the network device.
4. The method of claim 3 , further comprising:
searching a selection criteria database to identify the network device identified by the filter criteria.
5. The method of claim 3 , wherein the filter criteria is used to identify a group of network devices for which a subsequent message for changing power states is intended.
6. The method of claim 1 , wherein the network device is part of a subnet associated with the network element.
7. The method of claim 1 , further comprising:
receiving a subsequent message at the network element, wherein the subsequent message directs a group of network devices to change their respective power states;
identifying priority characteristics associated with the group of network devices; and
communicating at least a portion of the subsequent message to a certain subset of the group of network devices based on their respective priority characteristics.
8. Logic encoded in non-transitory media that includes code for execution and when executed by a processor operable to perform operations, comprising:
receiving a message at a network element configured for routing packets, wherein the message directs a network device to change its power state;
identifying the network device as being associated with a network for which the network element has responsibility; and
communicating at least a portion of the message from the network element to the network device.
9. The logic of claim 8 , wherein an application program interface (API) is leveraged in order to communicate the portion of the message, which identifies a media access control (MAC) address associated with the network device.
10. The logic of claim 8 , wherein the message includes filter criteria to be used to identify the network device.
11. The logic of claim 10 , further comprising:
searching a selection criteria database to identify the network device identified by the filter criteria.
12. The logic of claim 10 , wherein the filter criteria is used to identify a group of network devices for which a subsequent message for changing power states is intended.
13. The logic of claim 8 , wherein the network device is part of a subnet associated with the network element.
14. The logic of claim 8 , the operations further comprising:
receiving a subsequent message at the network element, wherein the subsequent message directs a group of network devices to change their respective power states;
identifying priority characteristics associated with the group of network devices; and
communicating at least a portion of the subsequent message to a certain subset of the group of network devices based on their respective priority characteristics.
15. An apparatus, comprising:
a memory element;
a processor operable to execute instructions associated with electronic code; and
a module operable to interface with the processor such that the apparatus is configured for:
receiving a message at a network element configured for routing packets, wherein the message directs a network device to change its power state;
identifying the network device as being associated with a network for which the network element has responsibility; and
communicating at least a portion of the message from the network element to the network device.
16. The apparatus of claim 15 , wherein an application program interface (API) is leveraged in order to communicate the portion of the message, which identifies a media access control (MAC) address associated with the network device.
17. The apparatus of claim 15 , wherein the message includes filter criteria to be used to identify the network device.
18. The apparatus of claim 17 , the apparatus being further configured for:
searching a selection criteria database to identify the network device identified by the filter criteria.
19. The apparatus of claim 17 , wherein the filter criteria is used to identify a group of network devices for which a subsequent message for changing power states is intended.
20. The apparatus of claim 15 , wherein the network device is part of a subnet associated with the network element.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/302,544 US20130132745A1 (en) | 2011-11-22 | 2011-11-22 | System and method for network enabled wake for networks |
US14/579,854 US9977479B2 (en) | 2011-11-22 | 2014-12-22 | System and method for network enabled wake for networks |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/302,544 US20130132745A1 (en) | 2011-11-22 | 2011-11-22 | System and method for network enabled wake for networks |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/579,854 Continuation US9977479B2 (en) | 2011-11-22 | 2014-12-22 | System and method for network enabled wake for networks |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130132745A1 true US20130132745A1 (en) | 2013-05-23 |
Family
ID=48428107
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/302,544 Abandoned US20130132745A1 (en) | 2011-11-22 | 2011-11-22 | System and method for network enabled wake for networks |
US14/579,854 Active 2032-03-15 US9977479B2 (en) | 2011-11-22 | 2014-12-22 | System and method for network enabled wake for networks |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/579,854 Active 2032-03-15 US9977479B2 (en) | 2011-11-22 | 2014-12-22 | System and method for network enabled wake for networks |
Country Status (1)
Country | Link |
---|---|
US (2) | US20130132745A1 (en) |
Cited By (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100083020A1 (en) * | 2008-09-29 | 2010-04-01 | Canon Kabushiki Kaisha | Information processing system and control method thereof |
US20130136131A1 (en) * | 2011-11-30 | 2013-05-30 | Buffalo Inc. | Relay device and activation method of electronic device |
US20140031126A1 (en) * | 2012-07-24 | 2014-01-30 | Binh Nguyen | Optimized power consumption in a gaming device |
US20150067815A1 (en) * | 2013-08-28 | 2015-03-05 | Cisco Technology, Inc. | Configuration of energy savings |
US20150121520A1 (en) * | 2013-10-31 | 2015-04-30 | Advanced Micro Devices, Inc. | System and method for security processor control over cpu power states |
US9058167B2 (en) | 2011-09-06 | 2015-06-16 | Cisco Technology, Inc. | Power conservation in a distributed digital video recorder/content delivery network system |
US9141169B2 (en) | 2012-01-20 | 2015-09-22 | Cisco Technology, Inc. | System and method to conserve power in an access network without loss of service quality |
US20160080580A1 (en) * | 2013-04-30 | 2016-03-17 | Nec Platforms, Ltd. | Key telephone system, control method, terminal, and program |
US9486697B2 (en) | 2009-10-17 | 2016-11-08 | Nguyen Gaming Llc | Asynchronous persistent group bonus games with preserved game state data |
US9486704B2 (en) | 2010-11-14 | 2016-11-08 | Nguyen Gaming Llc | Social gaming |
US20170003736A1 (en) * | 2015-06-30 | 2017-01-05 | Google Inc. | Systems and methods for efficiently communicating between low-power devices |
US9564018B2 (en) | 2010-11-14 | 2017-02-07 | Nguyen Gaming Llc | Temporary grant of real-time bonus feature |
US9576425B2 (en) | 2013-03-15 | 2017-02-21 | Nguyen Gaming Llc | Portable intermediary trusted device |
US9595161B2 (en) | 2010-11-14 | 2017-03-14 | Nguyen Gaming Llc | Social gaming |
US9600976B2 (en) | 2013-03-15 | 2017-03-21 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US9607474B2 (en) | 2010-06-10 | 2017-03-28 | Nguyen Gaming Llc | Reconfigurable gaming zone |
US9630096B2 (en) | 2011-10-03 | 2017-04-25 | Nguyen Gaming Llc | Control of mobile game play on a mobile vessel |
US9672686B2 (en) | 2011-10-03 | 2017-06-06 | Nguyen Gaming Llc | Electronic fund transfer for mobile gaming |
US9741205B2 (en) | 2009-11-16 | 2017-08-22 | Nguyen Gaming Llc | Asynchronous persistent group bonus game |
US20170310559A1 (en) * | 2016-04-21 | 2017-10-26 | Wyse Technology L.L.C. | Cloud based wake-on-lan for thin clients |
US9814970B2 (en) | 2013-03-15 | 2017-11-14 | Nguyen Gaming Llc | Authentication of mobile servers |
US9875606B2 (en) | 2010-04-09 | 2018-01-23 | Nguyen Gaming Llc | Spontaneous player preferences |
US20180074562A1 (en) * | 2016-09-09 | 2018-03-15 | Verint Americas Inc. | System and Method of Remote Power/Power Over Ethernet (POE) Device Controls |
US9977479B2 (en) | 2011-11-22 | 2018-05-22 | Cisco Technology, Inc. | System and method for network enabled wake for networks |
US10052551B2 (en) | 2010-11-14 | 2018-08-21 | Nguyen Gaming Llc | Multi-functional peripheral device |
US10176666B2 (en) | 2012-10-01 | 2019-01-08 | Nguyen Gaming Llc | Viral benefit distribution using mobile devices |
US10235516B2 (en) | 2016-05-10 | 2019-03-19 | Cisco Technology, Inc. | Method for authenticating a networked endpoint using a physical (power) challenge |
US10421010B2 (en) | 2013-03-15 | 2019-09-24 | Nguyen Gaming Llc | Determination of advertisement based on player physiology |
US10438446B2 (en) | 2009-11-12 | 2019-10-08 | Nguyen Gaming Llc | Viral benefit distribution using electronic devices |
US10467857B2 (en) | 2010-11-14 | 2019-11-05 | Nguyen Gaming Llc | Peripheral management device for virtual game interaction |
US10916090B2 (en) | 2016-08-23 | 2021-02-09 | Igt | System and method for transferring funds from a financial institution device to a cashless wagering account accessible via a mobile device |
US20210176137A1 (en) * | 2014-12-23 | 2021-06-10 | Talari Networks Incorporated | Methods and apparatus for providing adaptive private network centralized management system discovery processes |
WO2022015328A1 (en) * | 2020-07-17 | 2022-01-20 | Hewlett-Packard Development Company, L.P. | Switching communication connections based on processor type |
US11386747B2 (en) | 2017-10-23 | 2022-07-12 | Aristocrat Technologies, Inc. (ATI) | Gaming monetary instrument tracking system |
US11398131B2 (en) | 2013-03-15 | 2022-07-26 | Aristocrat Technologies, Inc. (ATI) | Method and system for localized mobile gaming |
US11488440B2 (en) | 2010-11-14 | 2022-11-01 | Aristocrat Technologies, Inc. (ATI) | Method and system for transferring value for wagering using a portable electronic device |
US11704971B2 (en) | 2009-11-12 | 2023-07-18 | Aristocrat Technologies, Inc. (ATI) | Gaming system supporting data distribution to gaming devices |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160218935A1 (en) * | 2015-01-27 | 2016-07-28 | Bank Of America Corporation | User interface and dashboard for holistic data transmission throughout an enterprise |
Citations (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030052180A1 (en) * | 2001-09-19 | 2003-03-20 | Trw Inc. | Method and apparatus for establishing addresses for plural actuators connected to a bus |
US20050123109A1 (en) * | 2003-12-08 | 2005-06-09 | Toshihiro Yamagishi | System and method for remote control |
US20060053324A1 (en) * | 2002-10-15 | 2006-03-09 | Yaniv Giat | Rack level power management for power over Ethernet |
US20060056397A1 (en) * | 2004-09-15 | 2006-03-16 | Kabushiki Kaisha Toshiba | Access management apparatus, program and remote start-up method of terminal device |
US20060184694A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for handling broadcast messages over an access domain |
US20070070998A1 (en) * | 2005-09-28 | 2007-03-29 | Dell Products L.P. | System and method for delivering the magic packet to wake up a node in remote subnet |
US7324518B2 (en) * | 2003-06-05 | 2008-01-29 | International Business Machines Corporation | Method and apparatus for transmitting wake-up packets over a network data processing system |
US20080062960A1 (en) * | 2006-09-07 | 2008-03-13 | Via Technologies, Inc. | Systems and methods for packet forward control |
US20080244282A1 (en) * | 2007-03-30 | 2008-10-02 | Foundry Networks, Inc. | Managing Power Allocation To Ethernet Ports In The Absence Of Mutually Exclusive Detection And Powering Cycles In Hardware |
US20080301322A1 (en) * | 2007-05-30 | 2008-12-04 | Kabushiki Kaisha Toshiba | Network controller, information processing apparatus and wake-up control method |
US20090182834A1 (en) * | 2008-01-15 | 2009-07-16 | Thomas Zettler | Device and Method for Providing Data |
US20090217063A1 (en) * | 2008-02-21 | 2009-08-27 | Sony Corporation | Information processing apparatus |
US20090228723A1 (en) * | 2008-03-07 | 2009-09-10 | Daisuke Yoshizaki | Power supplying device, power supply controlling method, power supply controlling program and network system |
US20090229288A1 (en) * | 2006-11-15 | 2009-09-17 | Glacier Bay, Inc. | Hvac system |
US20090310607A1 (en) * | 2008-06-12 | 2009-12-17 | Cisco Technology, Inc. | Static neighbor wake on local area network |
US7908501B2 (en) * | 2007-03-23 | 2011-03-15 | Silicon Image, Inc. | Progressive power control of a multi-port memory device |
US20110239019A1 (en) * | 2010-03-23 | 2011-09-29 | Unisys Corporation | Method and system for managing power consumption of a computing device |
US20120091804A1 (en) * | 2009-07-30 | 2012-04-19 | Lutron Electronics Co., Inc. | Load Control System Having an Energy Savings Mode |
US20120120958A1 (en) * | 2010-02-01 | 2012-05-17 | Priya Mahadevan | Deep sleep mode management for a network switch |
US20120131369A1 (en) * | 2004-11-24 | 2012-05-24 | Michael Paljug | Systems and methods for waking wireless lan devices |
US20120213085A1 (en) * | 2011-02-18 | 2012-08-23 | Ofir Koren | Stand alone wimax system and method |
US20120226918A1 (en) * | 2011-03-02 | 2012-09-06 | Rallo Aaron J | Non-intrusive Power Management |
US20120233478A1 (en) * | 2010-09-14 | 2012-09-13 | Andrea Mucignat | Methods and systems for data interchange between a network-connected thermostat and cloud-based management server |
US20120284537A1 (en) * | 2011-05-05 | 2012-11-08 | Empire Technology Development Llc | Device power management using compiler inserted device alerts |
US8407332B1 (en) * | 2010-07-01 | 2013-03-26 | Applied Micro Circuits Corporations | System and method for in-network power management |
US20130219197A1 (en) * | 2010-10-14 | 2013-08-22 | Jum Han Lee | Remote power management system and method |
US20130303202A1 (en) * | 2012-05-08 | 2013-11-14 | Qualcomm Incorporated | Systems and methods for paging message enhancement |
Family Cites Families (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4785927A (en) | 1987-03-02 | 1988-11-22 | Mars Incorporated | Vending machine control with product delivery motor home detection, motor speed control and power supply |
US6255943B1 (en) * | 1995-03-29 | 2001-07-03 | Cabletron Systems, Inc. | Method and apparatus for distributed object filtering |
US5991830A (en) * | 1996-01-04 | 1999-11-23 | Compaq Computer Corp. | Apparatus and method for coupling multiple peripheral devices to a single port of a computer |
US20020016639A1 (en) | 1996-10-01 | 2002-02-07 | Intelihome, Inc., Texas Corporation | Method and apparatus for improved building automation |
US6618709B1 (en) | 1998-04-03 | 2003-09-09 | Enerwise Global Technologies, Inc. | Computer assisted and/or implemented process and architecture for web-based monitoring of energy related usage, and client accessibility therefor |
AU5898099A (en) | 1998-08-25 | 2000-03-14 | Accompany Inc. | On-line marketing system and method |
US6785592B1 (en) | 1999-07-16 | 2004-08-31 | Perot Systems Corporation | System and method for energy management |
US6415270B1 (en) | 1999-09-03 | 2002-07-02 | Omnihub, Inc. | Multiple auction coordination method and system |
US6823223B2 (en) * | 1999-12-30 | 2004-11-23 | Microsoft Corporation | Method and apparatus for providing distributed scene programming of a home automation and control system |
US6834208B2 (en) * | 1999-12-30 | 2004-12-21 | Microsoft Corporation | Method and apparatus for providing distributed control of a home automation and control system |
US20020040475A1 (en) | 2000-03-23 | 2002-04-04 | Adrian Yap | DVR system |
US6980526B2 (en) | 2000-03-24 | 2005-12-27 | Margalla Communications, Inc. | Multiple subscriber videoconferencing system |
US6681156B1 (en) | 2000-09-28 | 2004-01-20 | Siemens Aktiengesellschaft | System and method for planning energy supply and interface to an energy management system for use in planning energy supply |
US20020157030A1 (en) | 2001-04-19 | 2002-10-24 | International Business Machines Corporation | Power conservation in communication systems |
EP1265265A3 (en) | 2001-06-09 | 2002-12-18 | Lg Electronics Inc. | Deflection yoke in CRT |
US6622097B2 (en) | 2001-06-28 | 2003-09-16 | Robert R. Hunter | Method and apparatus for reading and controlling electric power consumption |
US7188260B1 (en) | 2001-08-29 | 2007-03-06 | Cisco Technology, Inc. | Apparatus and method for centralized power management |
US6966005B2 (en) | 2001-12-26 | 2005-11-15 | International Business Machines Corporation | Energy caching for a computer |
EP1490941A4 (en) | 2002-03-28 | 2007-01-10 | Robertshaw Controls Co | Energy management system and method |
US7653401B2 (en) * | 2002-07-25 | 2010-01-26 | Hai Qu | Filtering of broadcast SMS messages |
US20040148388A1 (en) | 2003-01-24 | 2004-07-29 | Wen-Tzu Chung | Protocol at layer two for discovering and configuring network devices |
TWI220174B (en) | 2003-07-08 | 2004-08-11 | Winbond Electronics Corp | Power source detector and detecting method thereof |
KR200330467Y1 (en) | 2003-08-01 | 2003-10-17 | (주) 피엔텔레컴 | Data cable for detecting power source automatically |
JP2005078607A (en) | 2003-09-04 | 2005-03-24 | Sony Corp | Server, client, and network system |
US7203849B2 (en) | 2003-12-12 | 2007-04-10 | Hewlett-Packard Development Company, L.P. | Method and system for distributing power to networked devices |
US7177728B2 (en) | 2003-12-30 | 2007-02-13 | Jay Warren Gardner | System and methods for maintaining power usage within a set allocation |
US7515526B2 (en) | 2004-04-19 | 2009-04-07 | Microsemi Corp.—Analog Mixed Signal Group Ltd. | Dual mode power over ethernet controller |
CN100435069C (en) | 2004-05-10 | 2008-11-19 | 美高森美股份有限公司-模拟混合信号集团有限公司 | Method for rapid port power reduction |
US7084752B2 (en) | 2004-05-12 | 2006-08-01 | Cisco Technology, Inc. | Method and apparatus for triage of network alarms |
US7366933B1 (en) | 2004-07-09 | 2008-04-29 | American Power Conversion Corporation | Power event analysis |
US20060072531A1 (en) | 2004-10-04 | 2006-04-06 | Ewing Carrel W | Communication network |
US7345998B2 (en) * | 2004-12-15 | 2008-03-18 | Smart Labs, Inc. | Mesh network of intelligent devices communicating via powerline and radio frequency |
US7756544B1 (en) | 2005-01-13 | 2010-07-13 | Enterasys Networks, Inc. | Power controlled network devices for security and power conservation |
US7392407B2 (en) | 2005-02-09 | 2008-06-24 | Cisco Technology, Inc. | Method and apparatus for negotiating power between power sourcing equipment and powerable devices |
US7570601B2 (en) | 2005-04-06 | 2009-08-04 | Broadcom Corporation | High speed autotrunking |
US7274975B2 (en) | 2005-06-06 | 2007-09-25 | Gridpoint, Inc. | Optimized energy management system |
KR100717962B1 (en) | 2005-07-15 | 2007-05-14 | 전자부품연구원 | Method of controlling data transmission in a wireless network having many nodes and sensor network system using the same and computer readable media using the same |
US7716705B2 (en) | 2005-08-31 | 2010-05-11 | Time Warner Cable Inc. | Remote DVR manager |
US7831844B2 (en) | 2005-12-12 | 2010-11-09 | Linear Technology Corporation | Integrated powered device connector in system for supplying power over communication link |
US7500119B2 (en) | 2005-12-21 | 2009-03-03 | Intel Corporation | Power saving techniques for use in communication systems, networks, and devices |
JP4966603B2 (en) | 2006-02-08 | 2012-07-04 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile terminal, radio communication system, and mobile terminal control method |
CN101395559A (en) | 2006-03-01 | 2009-03-25 | Tivo有限公司 | Recommended recording and downloading guides |
US7734572B2 (en) | 2006-04-04 | 2010-06-08 | Panduit Corp. | Building automation system controller |
US8565105B2 (en) | 2008-09-29 | 2013-10-22 | Broadcom Corporation | Method and system for ethernet switching, conversion, and PHY optimization based on link length in audio/video systems |
US7647510B2 (en) | 2006-06-22 | 2010-01-12 | Silicon Laboratories, Inc. | System and method of classification in power over ethernet systems |
US7890776B2 (en) | 2006-06-28 | 2011-02-15 | Broadcom Corporation | Use of priority information to intelligently allocate power for personal computing devices in a Power-over-Ethernet system |
TWI315457B (en) | 2006-06-30 | 2009-10-01 | Mstar Semiconductor Inc | Power supply apparatus and method for providing voltage |
JP2008039809A (en) | 2006-08-01 | 2008-02-21 | Matsushita Electric Ind Co Ltd | Wide band modulation signal generating apparatus |
US7698580B2 (en) | 2006-08-25 | 2010-04-13 | Cisco Technology, Inc. | Inline power policing |
US20080222675A1 (en) | 2006-08-29 | 2008-09-11 | Hillcrest Laboratories, Inc. | Pointing capability and associated user interface elements for television user interfaces |
US8352754B2 (en) | 2006-11-15 | 2013-01-08 | Broadcom Corporation | Power management of PoE devices based on powered queue and unpowered queue of time order connection priority while maintaining reserve power |
US7941677B2 (en) | 2007-01-05 | 2011-05-10 | Avaya Inc. | Apparatus and methods for managing power distribution over Ethernet |
US20080178232A1 (en) | 2007-01-18 | 2008-07-24 | Verizon Data Services Inc. | Method and apparatus for providing user control of video views |
US8218567B2 (en) | 2007-03-12 | 2012-07-10 | Broadcom Corporation | Method and system for reducing transceiver power via a variable signal constellation |
CN101682179B (en) | 2007-03-14 | 2015-09-16 | 佐尼特结构解决方案有限责任公司 | Nema outlets and the network be associated of intelligence |
US7966504B2 (en) | 2007-04-11 | 2011-06-21 | Broadcom Corporation | System and method for power management in a computing device for power over ethernet |
US20080263191A1 (en) * | 2007-04-19 | 2008-10-23 | Hemal Shah | Method and system for handling packet filtering information |
US20080272741A1 (en) | 2007-05-03 | 2008-11-06 | Summit Microelectronics, Inc. | Systems and methods for detecting power sources |
US8242742B2 (en) | 2007-06-06 | 2012-08-14 | O2Micro, Inc | Chargers, systems and methods for detecting a power source |
US7870401B2 (en) | 2007-08-15 | 2011-01-11 | Broadcom Corporation | System and method for power over Ethernet provisioning for a computing device using a network user profile |
US8001399B2 (en) | 2007-09-12 | 2011-08-16 | Broadcom Corporation | System and method for secure communication for power over ethernet between a computing device and a switch |
US8140279B2 (en) | 2007-09-24 | 2012-03-20 | Budderfly Ventures, Llc | Computer based energy management |
US7966502B2 (en) | 2007-12-20 | 2011-06-21 | Broadcom Corporation | System and method for enabling power over ethernet for legacy devices |
US8255090B2 (en) | 2008-02-01 | 2012-08-28 | Energyhub | System and method for home energy monitor and control |
US8306018B2 (en) | 2008-02-04 | 2012-11-06 | Siemens Enterprise Communications, Inc. | Energy star compliant voice over internet protocol (VoIP) telecommunications network including energy star compliant VoIP devices |
US8812970B2 (en) | 2008-02-27 | 2014-08-19 | Microsoft Corporation | Dynamic device state representation in a user interface |
US8301921B2 (en) | 2008-03-27 | 2012-10-30 | International Business Machines Corporation | Secondary power utilization during peak power times |
US8000602B2 (en) | 2008-04-17 | 2011-08-16 | Pmc-Sierra Israel Ltd. | Methods and devices for reducing power consumption in a passive optical network while maintaining service continuity |
US20090282277A1 (en) | 2008-05-07 | 2009-11-12 | Aquantia Corporation | Low-power idle mode for network transceiver |
US8225124B2 (en) | 2008-07-30 | 2012-07-17 | Symbol Technologies, Inc. | Method and system for determining power over ethernet class capabilities |
US8160753B2 (en) | 2008-07-31 | 2012-04-17 | Microsemi Corp.—Analog Mixed Signal Group Ltd. | Time integrated guard band |
US8713627B2 (en) * | 2008-08-14 | 2014-04-29 | Juniper Networks, Inc. | Scalable security services for multicast in a router having integrated zone-based firewall |
US8106530B2 (en) | 2008-08-28 | 2012-01-31 | Cisco Technology, Inc. | Network-centric scheduled power provisioning method |
US8433530B2 (en) | 2008-09-18 | 2013-04-30 | ThinkEco, Inc. | System and method for monitoring and management of utility usage |
US8498534B2 (en) | 2008-11-05 | 2013-07-30 | Broadcom Corporation | Epon with power-saving features |
US8442498B2 (en) | 2008-12-19 | 2013-05-14 | Verizon Patent And Licensing Inc. | Methods, systems and computer program products for remote DVR interface provisioning |
US8726314B2 (en) | 2008-12-23 | 2014-05-13 | Verizon Patent And Licensing Inc. | System and method for extending recording time for a digital video record (DVR) |
US9088434B2 (en) | 2009-02-06 | 2015-07-21 | Broadcom Corporation | System and method for power over ethernet power mode policy and network management |
US8732501B1 (en) | 2009-02-09 | 2014-05-20 | Cisco Technology, Inc. | System and method for intelligent energy management in a network environment |
US8352769B1 (en) | 2009-02-09 | 2013-01-08 | Cisco Technology, Inc. | System and method for querying for energy data in a network environment |
US8495687B2 (en) | 2009-03-16 | 2013-07-23 | Centurylink Intellectual Property Llc | DVR home network content shifting |
US8201005B2 (en) | 2009-03-17 | 2012-06-12 | Intel Corporation | Negotiating a transmit wake time |
US8351759B2 (en) | 2009-03-31 | 2013-01-08 | Centurylink Intellectual Property Llc | Power outage DVR back up system |
US8515340B2 (en) | 2009-06-08 | 2013-08-20 | Mitel Networks Corporation | Power management in an internet protocol (IP) telephone |
US7936777B2 (en) | 2009-06-19 | 2011-05-03 | Broadcom Corporation | Parallel detection of remote LPI request and send zero mode |
US8804578B2 (en) | 2009-06-29 | 2014-08-12 | Broadcom Corporation | Method and system for jitter and frame balance and/or rebalance for EEE refresh cycles |
US8769082B2 (en) | 2009-07-24 | 2014-07-01 | Broadcom Corporation | Method and system for PHY initiated wake-up in energy efficient ethernet networks |
US8347121B2 (en) | 2009-07-31 | 2013-01-01 | Broadcom Corporation | System and method for adjusting an energy efficient ethernet control policy using measured power savings |
WO2011029983A1 (en) * | 2009-09-10 | 2011-03-17 | Nokia Corporation | Radio communication |
US8370671B2 (en) | 2009-12-02 | 2013-02-05 | International Business Machines Corporation | Saving power by powering down an instruction fetch array based on capacity history of instruction buffer |
US8259482B2 (en) | 2009-12-28 | 2012-09-04 | Advanced Connection Technology, Inc. | Power adapter apparatus and power management method |
US8996900B2 (en) | 2010-02-04 | 2015-03-31 | Cisco Technology, Inc. | System and method for managing power consumption in data propagation environments |
TWM385858U (en) | 2010-02-12 | 2010-08-01 | Fu Da Tong Technology Co Ltd | Frequency conversion type wireless power supply and charging device |
US9026812B2 (en) | 2010-06-29 | 2015-05-05 | Cisco Technology, Inc. | System and method for providing intelligent power management in a network environment |
CN102377489B (en) | 2010-08-19 | 2015-12-16 | 韩国电子通信研究院 | Light user network |
US20110125337A1 (en) | 2010-08-30 | 2011-05-26 | Vyacheslav Zavadsky | Household appliance adapted to work with time of use electricity rates |
US8996181B2 (en) | 2011-04-11 | 2015-03-31 | General Electric Company | Systems and methods for analyzing energy usage |
US8760280B2 (en) * | 2011-07-28 | 2014-06-24 | Tyco Fire & Security Gmbh | Method and apparatus for communicating with non-addressable notification appliances |
US8849473B2 (en) | 2011-08-17 | 2014-09-30 | Cisco Technology, Inc. | System and method for notifying and for controlling power demand |
US9058167B2 (en) | 2011-09-06 | 2015-06-16 | Cisco Technology, Inc. | Power conservation in a distributed digital video recorder/content delivery network system |
US20130132745A1 (en) | 2011-11-22 | 2013-05-23 | Cisco Technology Inc. | System and method for network enabled wake for networks |
US20130332001A1 (en) | 2012-06-08 | 2013-12-12 | Cisco Technology, Inc. | System and method for detecting a power source and metering points of a network device in a network environment |
-
2011
- 2011-11-22 US US13/302,544 patent/US20130132745A1/en not_active Abandoned
-
2014
- 2014-12-22 US US14/579,854 patent/US9977479B2/en active Active
Patent Citations (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030052180A1 (en) * | 2001-09-19 | 2003-03-20 | Trw Inc. | Method and apparatus for establishing addresses for plural actuators connected to a bus |
US20060053324A1 (en) * | 2002-10-15 | 2006-03-09 | Yaniv Giat | Rack level power management for power over Ethernet |
US7324518B2 (en) * | 2003-06-05 | 2008-01-29 | International Business Machines Corporation | Method and apparatus for transmitting wake-up packets over a network data processing system |
US20050123109A1 (en) * | 2003-12-08 | 2005-06-09 | Toshihiro Yamagishi | System and method for remote control |
US20060056397A1 (en) * | 2004-09-15 | 2006-03-16 | Kabushiki Kaisha Toshiba | Access management apparatus, program and remote start-up method of terminal device |
US20120131369A1 (en) * | 2004-11-24 | 2012-05-24 | Michael Paljug | Systems and methods for waking wireless lan devices |
US20060184694A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for handling broadcast messages over an access domain |
US20070070998A1 (en) * | 2005-09-28 | 2007-03-29 | Dell Products L.P. | System and method for delivering the magic packet to wake up a node in remote subnet |
US20080062960A1 (en) * | 2006-09-07 | 2008-03-13 | Via Technologies, Inc. | Systems and methods for packet forward control |
US20090229288A1 (en) * | 2006-11-15 | 2009-09-17 | Glacier Bay, Inc. | Hvac system |
US7908501B2 (en) * | 2007-03-23 | 2011-03-15 | Silicon Image, Inc. | Progressive power control of a multi-port memory device |
US20080244282A1 (en) * | 2007-03-30 | 2008-10-02 | Foundry Networks, Inc. | Managing Power Allocation To Ethernet Ports In The Absence Of Mutually Exclusive Detection And Powering Cycles In Hardware |
US20080301322A1 (en) * | 2007-05-30 | 2008-12-04 | Kabushiki Kaisha Toshiba | Network controller, information processing apparatus and wake-up control method |
US20090182834A1 (en) * | 2008-01-15 | 2009-07-16 | Thomas Zettler | Device and Method for Providing Data |
US20090217063A1 (en) * | 2008-02-21 | 2009-08-27 | Sony Corporation | Information processing apparatus |
US20090228723A1 (en) * | 2008-03-07 | 2009-09-10 | Daisuke Yoshizaki | Power supplying device, power supply controlling method, power supply controlling program and network system |
US20090310607A1 (en) * | 2008-06-12 | 2009-12-17 | Cisco Technology, Inc. | Static neighbor wake on local area network |
US20120091804A1 (en) * | 2009-07-30 | 2012-04-19 | Lutron Electronics Co., Inc. | Load Control System Having an Energy Savings Mode |
US20120120958A1 (en) * | 2010-02-01 | 2012-05-17 | Priya Mahadevan | Deep sleep mode management for a network switch |
US20110239019A1 (en) * | 2010-03-23 | 2011-09-29 | Unisys Corporation | Method and system for managing power consumption of a computing device |
US8407332B1 (en) * | 2010-07-01 | 2013-03-26 | Applied Micro Circuits Corporations | System and method for in-network power management |
US20120233478A1 (en) * | 2010-09-14 | 2012-09-13 | Andrea Mucignat | Methods and systems for data interchange between a network-connected thermostat and cloud-based management server |
US20130219197A1 (en) * | 2010-10-14 | 2013-08-22 | Jum Han Lee | Remote power management system and method |
US20120213085A1 (en) * | 2011-02-18 | 2012-08-23 | Ofir Koren | Stand alone wimax system and method |
US20120226918A1 (en) * | 2011-03-02 | 2012-09-06 | Rallo Aaron J | Non-intrusive Power Management |
US20120284537A1 (en) * | 2011-05-05 | 2012-11-08 | Empire Technology Development Llc | Device power management using compiler inserted device alerts |
US20130303202A1 (en) * | 2012-05-08 | 2013-11-14 | Qualcomm Incorporated | Systems and methods for paging message enhancement |
Non-Patent Citations (1)
Title |
---|
"MAC Address Definition", 15 September 2005, The Linux Information Project, retrieved from the Internet at on 3/25/15, pg. 1 * |
Cited By (100)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100083020A1 (en) * | 2008-09-29 | 2010-04-01 | Canon Kabushiki Kaisha | Information processing system and control method thereof |
US9486697B2 (en) | 2009-10-17 | 2016-11-08 | Nguyen Gaming Llc | Asynchronous persistent group bonus games with preserved game state data |
US10878662B2 (en) | 2009-10-17 | 2020-12-29 | Nguyen Gaming Llc | Asynchronous persistent group bonus games with preserved game state data |
US10140816B2 (en) | 2009-10-17 | 2018-11-27 | Nguyen Gaming Llc | Asynchronous persistent group bonus games with preserved game state data |
US10438446B2 (en) | 2009-11-12 | 2019-10-08 | Nguyen Gaming Llc | Viral benefit distribution using electronic devices |
US11682266B2 (en) | 2009-11-12 | 2023-06-20 | Aristocrat Technologies, Inc. (ATI) | Gaming systems including viral benefit distribution |
US11704971B2 (en) | 2009-11-12 | 2023-07-18 | Aristocrat Technologies, Inc. (ATI) | Gaming system supporting data distribution to gaming devices |
US9741205B2 (en) | 2009-11-16 | 2017-08-22 | Nguyen Gaming Llc | Asynchronous persistent group bonus game |
US11393287B2 (en) | 2009-11-16 | 2022-07-19 | Aristocrat Technologies, Inc. (ATI) | Asynchronous persistent group bonus game |
US9875606B2 (en) | 2010-04-09 | 2018-01-23 | Nguyen Gaming Llc | Spontaneous player preferences |
US11631297B1 (en) | 2010-04-09 | 2023-04-18 | Aristorcrat Technologies, Inc. (Ati) | Spontaneous player preferences |
US9607474B2 (en) | 2010-06-10 | 2017-03-28 | Nguyen Gaming Llc | Reconfigurable gaming zone |
US10818133B2 (en) | 2010-06-10 | 2020-10-27 | Nguyen Gaming Llc | Location based real-time casino data |
US9666021B2 (en) | 2010-06-10 | 2017-05-30 | Nguyen Gaming Llc | Location based real-time casino data |
US9626826B2 (en) | 2010-06-10 | 2017-04-18 | Nguyen Gaming Llc | Location-based real-time casino data |
US9842462B2 (en) | 2010-11-14 | 2017-12-12 | Nguyen Gaming Llc | Social gaming |
US10657762B2 (en) | 2010-11-14 | 2020-05-19 | Nguyen Gaming Llc | Social gaming |
US9595161B2 (en) | 2010-11-14 | 2017-03-14 | Nguyen Gaming Llc | Social gaming |
US10497212B2 (en) | 2010-11-14 | 2019-12-03 | Nguyen Gaming Llc | Gaming apparatus supporting virtual peripherals and funds transfer |
US9564018B2 (en) | 2010-11-14 | 2017-02-07 | Nguyen Gaming Llc | Temporary grant of real-time bonus feature |
US10467857B2 (en) | 2010-11-14 | 2019-11-05 | Nguyen Gaming Llc | Peripheral management device for virtual game interaction |
US9486704B2 (en) | 2010-11-14 | 2016-11-08 | Nguyen Gaming Llc | Social gaming |
US11532204B2 (en) | 2010-11-14 | 2022-12-20 | Aristocrat Technologies, Inc. (ATI) | Social game play with games of chance |
US10614660B2 (en) | 2010-11-14 | 2020-04-07 | Nguyen Gaming Llc | Peripheral management device for virtual game interaction |
US11488440B2 (en) | 2010-11-14 | 2022-11-01 | Aristocrat Technologies, Inc. (ATI) | Method and system for transferring value for wagering using a portable electronic device |
US11544999B2 (en) | 2010-11-14 | 2023-01-03 | Aristocrat Technologies, Inc. (ATI) | Gaming apparatus supporting virtual peripherals and funds transfer |
US10186110B2 (en) | 2010-11-14 | 2019-01-22 | Nguyen Gaming Llc | Gaming system with social award management |
US11922767B2 (en) | 2010-11-14 | 2024-03-05 | Aristocrat Technologies, Inc. (ATI) | Remote participation in wager-based games |
US10235831B2 (en) | 2010-11-14 | 2019-03-19 | Nguyen Gaming Llc | Social gaming |
US11024117B2 (en) | 2010-11-14 | 2021-06-01 | Nguyen Gaming Llc | Gaming system with social award management |
US11232676B2 (en) | 2010-11-14 | 2022-01-25 | Aristocrat Technologies, Inc. (ATI) | Gaming apparatus supporting virtual peripherals and funds transfer |
US11055960B2 (en) | 2010-11-14 | 2021-07-06 | Nguyen Gaming Llc | Gaming apparatus supporting virtual peripherals and funds transfer |
US10052551B2 (en) | 2010-11-14 | 2018-08-21 | Nguyen Gaming Llc | Multi-functional peripheral device |
US10096209B2 (en) | 2010-11-14 | 2018-10-09 | Nguyen Gaming Llc | Temporary grant of real-time bonus feature |
US11232673B2 (en) | 2010-11-14 | 2022-01-25 | Aristocrat Technologies, Inc. (ATI) | Interactive gaming with local and remote participants |
US11127252B2 (en) | 2010-11-14 | 2021-09-21 | Nguyen Gaming Llc | Remote participation in wager-based games |
US9058167B2 (en) | 2011-09-06 | 2015-06-16 | Cisco Technology, Inc. | Power conservation in a distributed digital video recorder/content delivery network system |
US10537808B2 (en) | 2011-10-03 | 2020-01-21 | Nguyem Gaming LLC | Control of mobile game play on a mobile vehicle |
US11495090B2 (en) | 2011-10-03 | 2022-11-08 | Aristocrat Technologies, Inc. (ATI) | Electronic fund transfer for mobile gaming |
US9630096B2 (en) | 2011-10-03 | 2017-04-25 | Nguyen Gaming Llc | Control of mobile game play on a mobile vessel |
US10586425B2 (en) | 2011-10-03 | 2020-03-10 | Nguyen Gaming Llc | Electronic fund transfer for mobile gaming |
US9672686B2 (en) | 2011-10-03 | 2017-06-06 | Nguyen Gaming Llc | Electronic fund transfer for mobile gaming |
US10777038B2 (en) | 2011-10-03 | 2020-09-15 | Nguyen Gaming Llc | Electronic fund transfer for mobile gaming |
US11458403B2 (en) | 2011-10-03 | 2022-10-04 | Aristocrat Technologies, Inc. (ATI) | Control of mobile game play on a mobile vehicle |
US9977479B2 (en) | 2011-11-22 | 2018-05-22 | Cisco Technology, Inc. | System and method for network enabled wake for networks |
US20130136131A1 (en) * | 2011-11-30 | 2013-05-30 | Buffalo Inc. | Relay device and activation method of electronic device |
US9141169B2 (en) | 2012-01-20 | 2015-09-22 | Cisco Technology, Inc. | System and method to conserve power in an access network without loss of service quality |
US11816954B2 (en) | 2012-07-24 | 2023-11-14 | Aristocrat Technologies, Inc. (ATI) | Optimized power consumption in a gaming establishment having gaming devices |
US20140031126A1 (en) * | 2012-07-24 | 2014-01-30 | Binh Nguyen | Optimized power consumption in a gaming device |
US9325203B2 (en) * | 2012-07-24 | 2016-04-26 | Binh Nguyen | Optimized power consumption in a gaming device |
US10249134B2 (en) | 2012-07-24 | 2019-04-02 | Nguyen Gaming Llc | Optimized power consumption in a network of gaming devices |
US11380158B2 (en) | 2012-07-24 | 2022-07-05 | Aristocrat Technologies, Inc. (ATI) | Optimized power consumption in a gaming establishment having gaming devices |
US10176666B2 (en) | 2012-10-01 | 2019-01-08 | Nguyen Gaming Llc | Viral benefit distribution using mobile devices |
US10445978B2 (en) | 2013-03-15 | 2019-10-15 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US9600976B2 (en) | 2013-03-15 | 2017-03-21 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US10421010B2 (en) | 2013-03-15 | 2019-09-24 | Nguyen Gaming Llc | Determination of advertisement based on player physiology |
US10380840B2 (en) | 2013-03-15 | 2019-08-13 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US11861979B2 (en) | 2013-03-15 | 2024-01-02 | Aristocrat Technologies, Inc. (ATI) | Gaming device docking station for authorized game play |
US10706678B2 (en) | 2013-03-15 | 2020-07-07 | Nguyen Gaming Llc | Portable intermediary trusted device |
US10755523B2 (en) | 2013-03-15 | 2020-08-25 | Nguyen Gaming Llc | Gaming device docking station for authorized game play |
US11783666B2 (en) | 2013-03-15 | 2023-10-10 | Aristocrat Technologies, Inc. (ATI) | Method and system for localized mobile gaming |
US11670134B2 (en) | 2013-03-15 | 2023-06-06 | Aristocrat Technologies, Inc. (ATI) | Adaptive mobile device gaming system |
US11636732B2 (en) | 2013-03-15 | 2023-04-25 | Aristocrat Technologies, Inc. (ATI) | Location-based mobile gaming system and method |
US9576425B2 (en) | 2013-03-15 | 2017-02-21 | Nguyen Gaming Llc | Portable intermediary trusted device |
US11004304B2 (en) | 2013-03-15 | 2021-05-11 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US11020669B2 (en) | 2013-03-15 | 2021-06-01 | Nguyen Gaming Llc | Authentication of mobile servers |
US11571627B2 (en) | 2013-03-15 | 2023-02-07 | Aristocrat Technologies, Inc. (ATI) | Method and system for authenticating mobile servers for play of games of chance |
US11532206B2 (en) | 2013-03-15 | 2022-12-20 | Aristocrat Technologies, Inc. (ATI) | Gaming machines having portable device docking station |
US10186113B2 (en) | 2013-03-15 | 2019-01-22 | Nguyen Gaming Llc | Portable intermediary trusted device |
US9811973B2 (en) | 2013-03-15 | 2017-11-07 | Nguyen Gaming Llc | Gaming device docking station for authorized game play |
US11132863B2 (en) | 2013-03-15 | 2021-09-28 | Nguyen Gaming Llc | Location-based mobile gaming system and method |
US11161043B2 (en) | 2013-03-15 | 2021-11-02 | Nguyen Gaming Llc | Gaming environment having advertisements based on player physiology |
US9814970B2 (en) | 2013-03-15 | 2017-11-14 | Nguyen Gaming Llc | Authentication of mobile servers |
US10115263B2 (en) | 2013-03-15 | 2018-10-30 | Nguyen Gaming Llc | Adaptive mobile device gaming system |
US11443589B2 (en) | 2013-03-15 | 2022-09-13 | Aristocrat Technologies, Inc. (ATI) | Gaming device docking station for authorized game play |
US11398131B2 (en) | 2013-03-15 | 2022-07-26 | Aristocrat Technologies, Inc. (ATI) | Method and system for localized mobile gaming |
US9875609B2 (en) | 2013-03-15 | 2018-01-23 | Nguyen Gaming Llc | Portable intermediary trusted device |
US10135998B2 (en) * | 2013-04-30 | 2018-11-20 | Nec Platforms, Ltd. | Key telephone system, control method, terminal, and program |
US20160080580A1 (en) * | 2013-04-30 | 2016-03-17 | Nec Platforms, Ltd. | Key telephone system, control method, terminal, and program |
US20150067815A1 (en) * | 2013-08-28 | 2015-03-05 | Cisco Technology, Inc. | Configuration of energy savings |
US10481665B2 (en) | 2013-08-28 | 2019-11-19 | Cisco Technology, Inc. | Configuration of energy savings |
US9958924B2 (en) * | 2013-08-28 | 2018-05-01 | Cisco Technology, Inc. | Configuration of energy savings |
US9870473B2 (en) * | 2013-10-31 | 2018-01-16 | Advanced Micro Devices, Inc. | System and method for security processor control over CPU power states |
US20150121520A1 (en) * | 2013-10-31 | 2015-04-30 | Advanced Micro Devices, Inc. | System and method for security processor control over cpu power states |
US20210176137A1 (en) * | 2014-12-23 | 2021-06-10 | Talari Networks Incorporated | Methods and apparatus for providing adaptive private network centralized management system discovery processes |
US11595270B2 (en) * | 2014-12-23 | 2023-02-28 | Talari Networks Incorporated | Methods and apparatus for providing adaptive private network centralized management system discovery processes |
US20170003736A1 (en) * | 2015-06-30 | 2017-01-05 | Google Inc. | Systems and methods for efficiently communicating between low-power devices |
US10691196B2 (en) | 2015-06-30 | 2020-06-23 | Google Llc | System and methods for efficiently communicating between low-power devices |
US10203748B2 (en) * | 2015-06-30 | 2019-02-12 | Google Llc | Systems and methods for efficiently communicating between low-power devices |
US20170310559A1 (en) * | 2016-04-21 | 2017-10-26 | Wyse Technology L.L.C. | Cloud based wake-on-lan for thin clients |
US10284436B2 (en) * | 2016-04-21 | 2019-05-07 | Wyse Technology L.L.C. | Cloud based wake-on-LAN for thin clients |
US10235516B2 (en) | 2016-05-10 | 2019-03-19 | Cisco Technology, Inc. | Method for authenticating a networked endpoint using a physical (power) challenge |
US10916090B2 (en) | 2016-08-23 | 2021-02-09 | Igt | System and method for transferring funds from a financial institution device to a cashless wagering account accessible via a mobile device |
US11307624B2 (en) | 2016-09-09 | 2022-04-19 | Verint Americas Inc. | System and method of remote power/power over Ethernet (POE) device controls |
US11366503B2 (en) | 2016-09-09 | 2022-06-21 | Verint Americas Inc. | System and method of remote power/power over ethernet (POE) device controls |
US10379588B2 (en) * | 2016-09-09 | 2019-08-13 | Verint Americas Inc. | System and method of remote power/power over ethernet (POE) device controls |
US20180074562A1 (en) * | 2016-09-09 | 2018-03-15 | Verint Americas Inc. | System and Method of Remote Power/Power Over Ethernet (POE) Device Controls |
US11790725B2 (en) | 2017-10-23 | 2023-10-17 | Aristocrat Technologies, Inc. (ATI) | Gaming monetary instrument tracking system |
US11386747B2 (en) | 2017-10-23 | 2022-07-12 | Aristocrat Technologies, Inc. (ATI) | Gaming monetary instrument tracking system |
WO2022015328A1 (en) * | 2020-07-17 | 2022-01-20 | Hewlett-Packard Development Company, L.P. | Switching communication connections based on processor type |
Also Published As
Publication number | Publication date |
---|---|
US20150113299A1 (en) | 2015-04-23 |
US9977479B2 (en) | 2018-05-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9977479B2 (en) | System and method for network enabled wake for networks | |
US8352769B1 (en) | System and method for querying for energy data in a network environment | |
US8732501B1 (en) | System and method for intelligent energy management in a network environment | |
US8849473B2 (en) | System and method for notifying and for controlling power demand | |
US20130332001A1 (en) | System and method for detecting a power source and metering points of a network device in a network environment | |
Gunaratne et al. | Managing energy consumption costs in desktop PCs and LAN switches with proxying, split TCP connections, and scaling of link speed | |
US8443071B2 (en) | Data server system and method | |
US9923978B2 (en) | Automated network service discovery and communication | |
US10149165B2 (en) | Virtual wireless networking | |
US9026812B2 (en) | System and method for providing intelligent power management in a network environment | |
US20100332212A1 (en) | Method and apparatus for sleep and wake of computer devices | |
US20110029659A1 (en) | Method and System for Network Proxy Services for Energy Efficient Networking | |
US10581697B2 (en) | SDN controlled PoE management system | |
US9058167B2 (en) | Power conservation in a distributed digital video recorder/content delivery network system | |
Khan et al. | Design and implementation of an automated network monitoring and reporting back system | |
Bolla et al. | Network connectivity proxy: An optimal strategy for reducing energy waste in network edge devices | |
Kurowski et al. | Distributed power management and control system for sustainable computing environments | |
US10924369B2 (en) | Traffic aware operations, administration, and maintenance (OAM) solutions for internet of things (IoT) networks | |
CN101132301A (en) | Self-adapting exchange method for dynamic management data of distributed node | |
Jain et al. | Deriving a generic energy consumption model for network enabled devices | |
Cisco | Leveragine JouleX and Cisco Energywise to Reduce Energy, Costs, and Carbon | |
US11601305B2 (en) | Physical infrastructure/virtual infrastructure integration system | |
Brienza et al. | E-Net-Manager: A power management system for networked PCs based on soft sensors | |
US20240039743A1 (en) | Path and interface selection based on power and interface operating modes in a software defined wide area network | |
WO2024031682A1 (en) | Device control method and apparatus, and device, storage medium and program product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SCHOENING, CHARLES B.;PARELLO, JOHN D.;GHOSE, TIRTHANKAR;AND OTHERS;SIGNING DATES FROM 20110928 TO 20111118;REEL/FRAME:027265/0362 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |