The disclosed subject matter relates to the field of device monitoring and control, and more particularly to power management of electronic devices.
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings that form a part of this document: Copyright 2009-2010 SynapSense Corporation, All Rights Reserved.
A data center can be modeled as rows of racks that house electronic systems, such as computing systems or other types of electrical devices. The computing systems (such as computers, storage devices, servers, routers, networking devices, etc.) consume power for their operation. The computing systems of the data center may reside in these racks. In a typical data center, there may be dozens or even hundreds of electrical devices. Each of these devices is connected to an electrical power source.
Data centers consume significant amounts of power, much of which is wasted in transmission and distribution, and overcooling idle servers. Various studies have shown that about 35 W (watts) of electricity goes toward 1 W of actual work. In order to effectively utilize power in data centers and to ultimately reduce the overall power usage, it is critical to first understand how different data center equipment (e.g., servers, routers, storage equipment, cooling unit and power distribution units) consume power, and then to use the consumption information to optimize power usage.
The problem of measuring power consumption in data centers is complex for several reasons. First, the number of devices that consume power can be very large. Any solution will need to be cost effective and will need to apply to large as well as small data centers. Second, data centers use a variety of devices and mechanisms to deliver power. Any solution will need to address the heterogeneity and legacy issues in the data center. Finally, a large number of devices or systems in data centers can be idle or outdated. Some mechanism is needed to enable data center operators to remotely manage data center equipment and the power consumption of data center equipment.
Thus, an apparatus and method for instrumenting devices to measure power usage using a multi-tier wireless network are needed.
The various embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which:
In the following detailed description, a reference is made to the accompanying drawings that form a part hereof, and in which are shown, by way of illustration, specific embodiments in which the disclosed subject matter can be practiced. It is understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the disclosed subject matter.
According to various example embodiments of the disclosed subject matter as described herein, there is provided an apparatus and method for instrumenting devices to measure power usage using a multi-tier wireless network. A particular embodiment relates to a network of radio frequency (RF) devices (wireless nodes) that include one or more sensing devices capable of sensing various system conditions, including electrical power consumption. Then, using wireless data communications, the wireless nodes can communicate sensor information, system condition information including power consumption information, or network information with other nodes of the network or with a set of network controllers (e.g., gateways). The network and node configuration in a particular embodiment are described in more detail below.
The system and method of a particular embodiment involves deploying wireless sensor devices for collecting system information, including power consumption information, at different locations and levels in a data center or facility, and then using the system information to manage the consumption of electrical power within the data center.
Wireless mesh network technology can be used for deploying sensors as nodes in a variety of different environments for monitoring diverse parameters such as, for example, power consumption or power usage, temperature, pressure, humidity, airflow/fluid flow, the presence of moisture, the presence of smoke or fire, electrical current, power, air quality, air particle count, and the like. These types of networks can be denoted wireless sensor networks (WSN). Each sensor in a WSN is typically powered by a battery and therefore capable of operating in a wireless configuration. As described in more detail below, the sensors can constantly monitor a system and/or the environment for various system conditions and may communicate with other nodes and/or a network controller or gateway.
Referring still to
Each of the nodes 112 of WSN 110 can also communicate with a set of gateways 105 via a gateway interface 106. The gateway 105 provides a connection between the WSN 110 and an analysis processor 100. Analysis processor 100 can be used to receive sensor data from any of the nodes 112 of WSN 110 via gateway 105 and network 108 and to analyze the sensor data for aggregated system monitoring and control. Gateway 105 and analysis processor 100 can also each provide a connection to a wide area network 108, such as the Internet. In this manner, the analysis processor 100, the gateway 105, and the WSN 110 can obtain access to the Internet. Gateway 105 and analysis processor 100 can use a conventional data storage device 104 for data storage and retrieval. In some embodiments, an internal data connection 102 can be provided to link Gateway 105 and analysis processor 100 for data communications.
The WSN 110 can be configured in any of a variety of ways. Nodes 112 can be added, removed, or moved within the array of nodes of WSN 110. Each of the nodes 112 include functionality to join or reconfigure themselves in the WSN 110 when a node is added or moved. As part of this functionality, each node 112 can discover its neighbor nodes and automatically negotiate and establish communication paths with those neighbors. A node can be in direct data communication with neighbors that are within the radio reception range of the node. Depending on the strength of the wireless transceivers (e.g., radios) within each node 112, the distance between neighbor nodes is variable. Given that in some applications the environment in which WSN 110 is being used may be subject to radio interference, it is possible that the wireless data communications between nodes may be disrupted. In these cases, each node can sense the loss of data communications with a neighbor and may reconfigure itself to use alternate data paths through other functioning nodes of WSN 110. As such, the WSN 110 is highly adaptable to changing conditions in the environment and in the configuration of the wireless network.
The example node 200 includes a processor 202 (e.g., a central processing unit (CPU)), a main memory 204 and optionally a static memory 206, which communicate with each other via a bus 201. The node 200 may further include one or more sensor devices 212, 214, and 216. These sensor devices can include power consumption or power usage sensors, voltage measurement devices, electrical current measurement devices, wattage measurement devices, inductance measurement devices, electromagnetic field (EMF) measurement devices, temperature sensors, humidity sensors, air pressure sensors, air flow sensors, moisture detectors, carbon monoxide detectors, fire/smoke detectors, motion detectors, seismic detectors, electrical current sensors, power sensors, air quality sensors, air particle count sensors, magnetic anomaly sensors, and/or other types of sensors for detecting and measuring a desired system or environmental condition.
The node 200 may further include a non-volatile memory 218, a control signal generation device 222, and a network interface device 208 (e.g., a radio transceiver or wireless device capable of connection with a network). The non-volatile memory 218 includes a machine-readable medium 219 in which is stored one or more sets of instructions (e.g., software and data 220) embodying any one or more of the methodologies or functions described herein. The instructions 220 may also reside, completely or partially, within the main memory 204, the static memory 206, and/or within the processor 202 during execution thereof by the node 200. The main memory 204, static memory 206, and the processor 202 also may constitute machine-readable media. The software, instructions, and/or related data 220 may further be transmitted or received over a network 210 via the network interface device 208. The network interface device 208, in a wireless node configuration of one embodiment, may include a radio transceiver for sending and receiving data to/from network 210 using a wireless data transfer protocol, such as the family of 802.11 standards from IEEE. In this manner, node 200 can perform wireless data communications with other nodes of WSN 110. The control signal generation device 222 can be used to control the operation of a management system, such as a power management system, electrical control unit, a heating/ventilating/air conditioning (HVAC) system, a fan, a heat pump, or other device or system that can alter the power consumption or environmental conditions being monitored by sensors 212, 214, and 216.
Gateway 105 can provide synchronization timing for the nodes 112 of WSN 110. Gateway 105 can send periodic messages to each of the nodes 112 of WSN 110. These periodic messages can include a timing signal (e.g. a beacon) to which each of the nodes 112 can synchronize their internal timers. Similarly, messages from gateway 105 to each of the nodes 112 can be used to provide system status, configuration, and control settings for the nodes of WSN 110.
As described herein, an apparatus and method for instrumenting devices to measure power usage using a multi-tier wireless network is disclosed. The apparatus and method in a particular embodiment include using a network of wireless sensors to monitor various system conditions, including power consumption, in specific devices of a data center over time and to generate control signals to manage power consumption and related conditions. Particular example embodiments are described in more detail below.
Referring now to
Referring still to
Each power monitor 318 is capable of sampling power usage data at a very high rate. After sampling the data, the power monitor 318 can perform computations to calculate different power related metrics. The power monitor 318 may also store the measured data and calculated metrics, generally denoted system data, in long-term data storage on the power monitor 318 device itself. Periodically, the power monitor 318 can send the calculated and measured system data to its primary communication hub 320. In one embodiment, the primary communication hub 320 can be the communication hub 320 associated with the rack 312 in which the monitored device 314 is installed. In other embodiments, the primary communication hub 320 can be the communication hub 320 associated with a particular one of the plurality of power monitors 318 at system initialization time. The primary communication hub 320 can collect data wirelessly from a plurality of associated power monitors 318. The communication hub 320 can aggregate the system data and use a multi-hop mesh network (such as network 110) to send the data to the analysis processor 100 via gateway 330 for data processing.
As shown in the example of
Referring now to
Referring now to
In a particular embodiment, the global network is a multi-hop mesh network that integrates a plurality of communication hubs 320 with one or more gateways 330. An example embodiment is shown in
In an example embodiment, such as the example embodiment shown in
In a particular embodiment, an example system can include a centralized software system, called the Analysis Processor 100 (shown in
Referring to
In one embodiment, the electronics that implement the power measurement and radio functions of the power monitor 318 are housed in a Poly Carbonate-acrylonitrile butadiene styrene (PC-ABS) plastic module attached to the cord 628/630. Each power monitor 318 has a unique identifier (ID) that is provided during manufacturing and is bar-coded on the outside of the device. As described above, each power monitor 318 includes power measurement circuitry 620, a microprocessor or central processing unit (CPU) 622, and a wireless radio 624. In order to calculate power usage, both voltage and current need to be sensed. In one embodiment, voltage sensing is accomplished via a potential divider chain placed across the live and neutral (phase to phase in a delta configuration) conductors; the junction of the divider is connected to the power circuitry's voltage analog/digital (A/D) converter input. Measuring the voltage drop across a current sensing resistor, utilizing the current A/D input to the power measurement circuitry 620, senses current. The power measurement circuitry 620 then calculates the power data taking into account PF (Power Factor). All four parameters, voltage, current, PF and power can be made available to an external device via a bus. These measured and computed metrics can be retained in a memory and ultimately sent from the power monitor 318 by a local wireless network transmission to the communication hub 320 using the wireless radio 624. The wireless radio 624 of a particular embodiment contains a 2.4 GHz ISM band transceiver and an embedded microcontroller 622. The network stack and data management firmware is housed in and executed by the microcontroller 622. An internal antenna supports the wireless radio 624. Power for the electronics of the power monitor 318 is scavenged from the power being monitored.
In an example embodiment, a communication hub 320 manages the local communication network that includes a set of power monitors 318. In addition, the communication hub 320 collects power data from the power monitors 318 and uses the global network to transmit the information to a centralized location for storage and processing. Communication hubs 320 can have a display to show current per phase and allow outlets to be selected during the installation process. Push buttons can be provided to set the mode of operation and provide installation functions. A serial port can be provided to attach a bar-code scanner during the installation process. The hardware architecture of a particular embodiment of the communication hub 320 includes a serial port to support the bar code scanner, an embedded 8-bit, 16-bit, or 32-bit processor, two radio devices, one for the local communication network, and another for the global communication network.
Before the power monitors 318 and communication hub 320 can be used, these devices need to be configured. In a particular embodiment, configuration involves associating a specific power monitor 318 with a set of communication hubs 320, and the outlet/equipment to which the power monitor 318 is attached. A configuration tool is used to record and store this information. In a particular embodiment, the configuration tool uses a process involving four steps: (i) Identification, (ii) Device and power monitor 318 association, (iii) Local Network Registration, and (iv) Router configuration. These steps are described in more detail below.
Identification involves collecting the unique identifier associated with each power monitor 318 and storing these identifiers with the configuration tool. This identification step can be achieved in one of the several ways:
Every power monitor 318 can be associated with a device 314 or power outlet to which the power monitor 318 is attached. This association is used to determine which power monitor 318 is used to measure the power of which device 314. The process involves associating the identifier of a power monitor 318 with a unique identifier of the device 314 to which the power monitor 318 is attached. This association can take place in one of several ways:
Local network registration in a particular embodiment involves creating a subnet that includes a set of power monitors 318. This subnet creation involves using the configuration tool to assign a unique identifier (subnet address) to each local network. The configuration tool may also assign a unique name or location to each subnet.
Finally, each local network is associated with a primary communication hub 320, which acts as a router and manager for the local network. Router (e.g., primary communication hub 320) configuration takes place in one of the several ways in various embodiments:
The initialization phase involves the formation of the network in which both local and global networks are initialized. The techniques for building the global network are described above in relation to building the WSN 110. The method used for initialization of the local network in a particular embodiment is described next.
Once a power monitor 318 is turned on (activated), the power monitor 318 tries to connect with a communication hub 320 by sending beacons. A beacon is a data message sent via the wireless network. If there is no response from a communication hub 320, possibly because the communication hub 320 has not been turned on or the global network has not been formed, the power monitor 318 can: 1) sleep for some pre-configured length of time, 2) try sending the beacon again, or 3) choose a channel (e.g., a particular radio frequency band) on which the power monitor 318 can periodically request formation of the network.
If a communication hub 320 is active and the global network has been formed, the communication hub 320 can collect information related to the local networks that the communication hub 320 needs to support. The communication hub 320 can then monitor all channels on its secondary radio for request beacons from power monitors 318. Once the communication hub 320 receives a request beacon from a power monitor 318, the communication hub 320 can check its list of power monitors 318 that the communication hub 320 needs to support. If the requesting power monitor 318 is on the list of power monitors 318 that the communication hub 320 needs to support, the request from the power monitor 318 is verified. If the request is verified, the communication hub 320 can send a confirm message to the requesting power monitor 318. Once the communication hub 320 receives an acknowledgement from the requesting power monitor 318, a confirmation message is sent back to a network manager, which records the formation of the local network.
Another possible way in which a power monitor can become part of a local network is by sending request beacons to other power monitors that are already part of the network. In this approach, a power monitor sends beacons on a fixed number of channels. The power monitors that are already part of the local network monitor these channels for beacon messages. Once they receive request beacons, they forward the beacons to the associated communication hub. The communication hub responds to the requesting power monitor.
The various embodiments described herein provide a universal power monitoring system that allows for monitoring of power to individual electrical loads. Although various embodiments have application in several markets, a primary application is to measure the power usage of servers, routers, storage equipment, etc. within data centers. Certainly, the ability to accurately monitor power consumption at the server level can significantly reduce the frequency of power problems associated with power needs that exceed budgeted power. The various embodiments also enable data center operators to adequately budget for per-cabinet power usage.
The basic functionality of the various embodiments may be broken down into three primary parts: (a) per plug power usage data acquisition, (b) per cabinet data aggregation, and (c) data transmission. The idea for acquiring per-equipment power usage data is to augment the power cord to the load with a power monitoring capability. This is accomplished through the use of a power-sensing device that has compatible male and female power connectors, such as the power monitor 318 as described above. It is envisioned that each device to be monitored will be equipped with a power monitor 318.
By measuring power usage data at the plug-level, the power monitor 318 and communication hub 320 provides the ability to aggregate data to provide cabinet level metrics. Each power monitor 318 within a cabinet shall communicate its data to a local communication hub 320. The communication hub 320 may support power monitors 318 in multiple cabinets. The communication hub 320 bridges the wireless communications of the per plug power monitor 318 to the wireless network. The communication hub 320 also reports a power monitor 318 configuration to the server. This configuration information contains a mapping of power monitors 318 to outlets on the rack PDU. The communication hub 320 can have a display that provides visualization for total current, total kW, max current, and historical charting. The data is provided at phase-level per strip, per rack, in order to facilitate power load balancing. Each communication hub 320 can join the wireless network and report the measured and computed power data captured from each power monitor 318 via the WSN.
As described herein, the various embodiments enable several advantages. These advantages are summarized below:
Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
In example embodiments, a node configured by an application may constitute a “module” that is configured and operates to perform certain operations as described herein. In other embodiments, the “module” may be implemented mechanically or electronically. For example, a module may comprise dedicated circuitry or logic that is permanently configured (e.g., within a special-purpose processor) to perform certain operations. A module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a module mechanically, in the dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Accordingly, the term “module” should be understood to encompass a functional entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein.
While the machine-readable medium 219 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any non-transitory medium that is capable of storing, encoding or embodying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies described herein. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.
As noted, the software and/or related data may be transmitted over a network using a transmission medium. The term “transmission medium” shall be taken to include any medium that is capable of storing, encoding or carrying instructions for transmission to and execution by the machine, and includes digital or analog communication signals or other intangible media to facilitate transmission and communication of such software and/or data.
The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of components and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of ordinary skill in the art upon reviewing the description provided herein. Other embodiments may be utilized and derived, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The figures herein are merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
The description herein may include terms, such as “up”, “down”, “upper”, “lower”, “first”, “second”, etc. that are used for descriptive purposes only and are not to be construed as limiting. The elements, materials, geometries, dimensions, and sequence of operations may all be varied to suit particular applications. Parts of some embodiments may be included in, or substituted for, those of other embodiments. While the foregoing examples of dimensions and ranges are considered typical, the various embodiments are not limited to such dimensions or ranges.
The Abstract is provided to comply with 37 C.F.R. §1.74(b) to allow the reader to quickly ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments have more features than are expressly recited in each claim. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
Thus, as described above, an apparatus and method for instrumenting devices to measure power usage using a multi-tier wireless network is disclosed. Although the disclosed subject matter has been described with reference to several example embodiments, it may be understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the disclosed subject matter in all its aspects. Although the disclosed subject matter has been described with reference to particular means, materials, and embodiments, the disclosed subject matter is not intended to be limited to the particulars disclosed; rather, the subject matter extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4866606 | Kopetz | Sep 1989 | A |
5194848 | Kerr | Mar 1993 | A |
5379290 | Kleijne | Jan 1995 | A |
5408506 | Mincher et al. | Apr 1995 | A |
5515369 | Flammer, III | May 1996 | A |
5896412 | Levanon | Apr 1999 | A |
6028857 | Poor | Feb 2000 | A |
6208247 | Agre | Mar 2001 | B1 |
6304556 | Haas | Oct 2001 | B1 |
6404756 | Whitehill | Jun 2002 | B1 |
6442596 | Dyer | Aug 2002 | B1 |
6480497 | Flammer, III | Nov 2002 | B1 |
6590928 | Haartsen | Jul 2003 | B1 |
6735630 | Gelvin | May 2004 | B1 |
6807165 | Belcea | Oct 2004 | B2 |
6850502 | Kagan | Feb 2005 | B1 |
6856591 | Ma et al. | Feb 2005 | B1 |
6859831 | Gelvin | Feb 2005 | B1 |
7010392 | Bash | Mar 2006 | B2 |
7020701 | Gelvin | Mar 2006 | B1 |
7031329 | Lipsanen | Apr 2006 | B2 |
7031870 | Sharma | Apr 2006 | B2 |
7086603 | Bash | Aug 2006 | B2 |
7119676 | Silverstrim et al. | Oct 2006 | B1 |
7176808 | Broad | Feb 2007 | B1 |
7180915 | Beyer | Feb 2007 | B2 |
7269753 | Farkas et al. | Sep 2007 | B2 |
7272129 | Calcev | Sep 2007 | B2 |
7277414 | Younis et al. | Oct 2007 | B2 |
7313461 | Sharma et al. | Dec 2007 | B2 |
7363516 | Bresniker et al. | Apr 2008 | B2 |
7386743 | Bahali et al. | Jun 2008 | B2 |
7421599 | Bahali et al. | Sep 2008 | B2 |
7436789 | Caliskan et al. | Oct 2008 | B2 |
7463644 | Zhu | Dec 2008 | B2 |
7467311 | Bahali et al. | Dec 2008 | B2 |
7502360 | Liu | Mar 2009 | B2 |
7509506 | Bahali et al. | Mar 2009 | B2 |
7633882 | Das et al. | Dec 2009 | B2 |
7680092 | Van Laningham | Mar 2010 | B2 |
7839764 | Jiang et al. | Nov 2010 | B2 |
7992021 | Bahali et al. | Aug 2011 | B2 |
8053926 | Lehmann et al. | Nov 2011 | B2 |
8108703 | Bahali et al. | Jan 2012 | B2 |
8212395 | Jansma | Jul 2012 | B2 |
8305737 | Ewing et al. | Nov 2012 | B2 |
8494661 | Ewing et al. | Jul 2013 | B2 |
8527619 | Ewing et al. | Sep 2013 | B2 |
20020073152 | Andrew et al. | Jun 2002 | A1 |
20030067745 | Chandrakant | Apr 2003 | A1 |
20030067892 | Beyer | Apr 2003 | A1 |
20040090329 | Hitt | May 2004 | A1 |
20050024826 | Bash | Feb 2005 | A1 |
20050030968 | Rich et al. | Feb 2005 | A1 |
20050074025 | Shao et al. | Apr 2005 | A1 |
20050129051 | Zhu | Jun 2005 | A1 |
20050157698 | Park et al. | Jul 2005 | A1 |
20050173549 | Bash | Aug 2005 | A1 |
20050201340 | Wang | Sep 2005 | A1 |
20050213612 | Pister | Sep 2005 | A1 |
20050223090 | Ewing et al. | Oct 2005 | A1 |
20050237928 | Le Scolan et al. | Oct 2005 | A1 |
20050239411 | Hazra | Oct 2005 | A1 |
20060029060 | Pister | Feb 2006 | A1 |
20060029061 | Pister | Feb 2006 | A1 |
20060034191 | Sahinoglu | Feb 2006 | A1 |
20060126501 | Ramaswamy | Jun 2006 | A1 |
20060149408 | Speetzer | Jul 2006 | A1 |
20060161909 | Pandey | Jul 2006 | A1 |
20060164040 | Ohkubo | Jul 2006 | A1 |
20060198346 | Liu | Sep 2006 | A1 |
20060215581 | Castagnoli | Sep 2006 | A1 |
20060215583 | Castagnoli | Sep 2006 | A1 |
20060225446 | Bash | Oct 2006 | A1 |
20060245360 | Ensor et al. | Nov 2006 | A1 |
20060268791 | Cheng | Nov 2006 | A1 |
20060269028 | Bley | Nov 2006 | A1 |
20060282685 | Bahali et al. | Dec 2006 | A1 |
20060282687 | Bahali et al. | Dec 2006 | A1 |
20070005994 | Bahali et al. | Jan 2007 | A1 |
20070050523 | Emeott | Mar 2007 | A1 |
20070116060 | Qu | May 2007 | A1 |
20070143043 | Wafer et al. | Jun 2007 | A1 |
20070208992 | Koren | Sep 2007 | A1 |
20070211686 | Belcea | Sep 2007 | A1 |
20070258508 | Werb | Nov 2007 | A1 |
20070268880 | Bellur et al. | Nov 2007 | A1 |
20080008138 | Pun | Jan 2008 | A1 |
20080019265 | Alluisi et al. | Jan 2008 | A1 |
20080019302 | Nagarajan et al. | Jan 2008 | A1 |
20080043707 | Ren | Feb 2008 | A1 |
20080062003 | Paetz | Mar 2008 | A1 |
20080084294 | Zhiying et al. | Apr 2008 | A1 |
20080095222 | Van Laningham | Apr 2008 | A1 |
20080129495 | Hitt | Jun 2008 | A1 |
20080151801 | Mizuta | Jun 2008 | A1 |
20080174446 | Ghabra et al. | Jul 2008 | A1 |
20080215900 | Bahali et al. | Sep 2008 | A1 |
20080244281 | Felter et al. | Oct 2008 | A1 |
20080253327 | Kohvakka et al. | Oct 2008 | A1 |
20080269932 | Chardon | Oct 2008 | A1 |
20080298450 | Zhang | Dec 2008 | A1 |
20090007706 | Hitt et al. | Jan 2009 | A1 |
20090031051 | Nguyen | Jan 2009 | A1 |
20090031148 | Densham | Jan 2009 | A1 |
20090059814 | Nixon et al. | Mar 2009 | A1 |
20090062970 | Forbes et al. | Mar 2009 | A1 |
20090109992 | Lurie et al. | Apr 2009 | A1 |
20090168796 | Pandey et al. | Jul 2009 | A1 |
20090234512 | Ewing et al. | Sep 2009 | A1 |
20090243895 | Mitchell et al. | Oct 2009 | A1 |
20090289812 | Kim et al. | Nov 2009 | A1 |
20090302996 | Rhee et al. | Dec 2009 | A1 |
20090322518 | Liang et al. | Dec 2009 | A1 |
20100005331 | Somasundaram et al. | Jan 2010 | A1 |
20100008286 | Abedi | Jan 2010 | A1 |
20100042860 | Kwon et al. | Feb 2010 | A1 |
20100085903 | Pandey et al. | Apr 2010 | A1 |
20100127141 | Chan et al. | May 2010 | A1 |
20100142425 | Lee et al. | Jun 2010 | A1 |
20100148940 | Gelvin et al. | Jun 2010 | A1 |
20100164720 | Kore | Jul 2010 | A1 |
20100177708 | Pandey et al. | Jul 2010 | A1 |
20100211669 | Dalgas et al. | Aug 2010 | A1 |
20100211810 | Zacho | Aug 2010 | A1 |
20100220653 | Hwang et al. | Sep 2010 | A1 |
20100235654 | Malik et al. | Sep 2010 | A1 |
20100280796 | Ramin et al. | Nov 2010 | A1 |
20100316009 | Han et al. | Dec 2010 | A1 |
20110072289 | Kato | Mar 2011 | A1 |
20110101777 | Jansma | May 2011 | A1 |
20110167280 | Ewing et al. | Jul 2011 | A1 |
20110205693 | Jansma et al. | Aug 2011 | A1 |
20110218689 | Chan et al. | Sep 2011 | A1 |
20110245988 | Ingels et al. | Oct 2011 | A1 |
20110248823 | Silberbauer et al. | Oct 2011 | A1 |
20110291813 | Jansma | Dec 2011 | A1 |
20110320827 | Siegman et al. | Dec 2011 | A1 |
20110320849 | Cochran et al. | Dec 2011 | A1 |
20120011378 | Dalton et al. | Jan 2012 | A1 |
20120017102 | Turicchi et al. | Jan 2012 | A1 |
20120042180 | Ewing et al. | Feb 2012 | A1 |
20120054527 | Pfeifer et al. | Mar 2012 | A1 |
20120181869 | Chapel et al. | Jul 2012 | A1 |
20130191658 | Malik et al. | Jul 2013 | A1 |
Number | Date | Country |
---|---|---|
2616715 | Feb 2007 | CA |
101401480 | Apr 2009 | CN |
202006019810 | May 2007 | DE |
1719301 | Nov 2006 | EP |
1911184 | Apr 2009 | EP |
2006311549 | Nov 2006 | JP |
2009504010 | Jun 2007 | JP |
2004336779 | Nov 2007 | JP |
100646748 | Nov 2006 | KR |
1020070009390 | Jan 2007 | KR |
1020070105731 | Oct 2007 | KR |
WO2005083953 | Sep 2005 | WO |
WO2007015962 | Jun 2007 | WO |
WO2008021278 | Jul 2008 | WO |
WO2010077253 | Jul 2010 | WO |
WO2010147622 | Dec 2010 | WO |
Entry |
---|
PCT International Search Report and Written Opinion, Feb. 28, 2012, PCT/US2011/049235. |
PCT International Preliminary Report on Patentability (PCT/US2010/001614), Dec. 16, 2011. |
Kanzaki, Akimitsu et al.; Dynamic TDMA Slot Assignments in Ad Hoc Networks; 17th Int'l Conference on Advanced Information Networking and Applications; Mar. 2003; pp. 330-335. |
Lee, Myung J. et al.; Emerging Standards for Wireless Mesh Technology; IEEE Wireless Communications; Apr. 2006; vol. 13; pp. 56-63. |
Wei Li, et al.; Dynamic TDMA Slot Assignment Protocol for Multihop Ad Hoc Networks; Int'l Conference on Communication Technology; Nov. 2006; pp. 1-4. |
C. Frank et al., Proceedings of the 3rd International Conference on Embedded Networked Sensor Systems, pp. 230-242, 02-04; Nov. 2005. |
PCT International Preliminary Report on Patentability, PCTUS2009/004508, Jul. 5, 2011. |
Sensicast White Paper; 4 pages; Written by Nick Larkin, “Best Practices for Data Center Monitoring Using wireless Sensor Neworks”; 2007; printed from Internet on Oct. 23, 2011. |
Public Announcement or Press Release entitled, “Seniscast Announces SensiNet Wireless Sensor Network Support for SNMP”; 3 pages; Nov. 6, 2007; published on www.marketwire.com; printed from Internet on Oct. 23, 2011. |