1. Technical Field
The present invention relates to an electrical power controller. In particular, a power node that also provides networking functionality.
2. Description of Related Art
Electric power strips typically have a plurality of electrical outlets mounted within an enclosure and an attached power cord for electrically interconnecting the outlets with an AC power source. While modern power strips may include overload protection and/or surge protection, they do not generally include signal and power electronics enabling the power strip to be incorporated into a networked energy management system.
As home networking has become common, several types of networking have become important including wired ethernet, wireless IEEE 802.11 Wi-Fi, IEEE 802.15.4 Zigbee, Z-Wave wireless networking, and powerline networking including networking using protocols from HomePlug® Powerline Alliance, HD-PLC Alliance and/or IEEE P1901.
A power node may include a power plug and a power socket with a power switch interposed between the power plug and the power socket. A first network interface utilizing a powerline communication physical layer is configured to communicate through the power plug and bridge circuitry is configured to bridge between the first network interface and a second network interface utilizing a second physical layer to provide a bridged network. A processor is configured to control the power switch and to communicate over the bridged network. The processor may control the power switch based on a command received over the bridged network.
A method of reporting what device is plugged into a particular power socket of a power node may include receiving information about a device through a first network interface located on a power node. The first network interface uses a protocol that is does not utilize power line communication. A particular power socket on the power node from which the device is receiving power may be identified and at least some of the information about the device and an identifier of the particular power socket may be sent across a second network interface using power line communication. The flow of power to the particular power socket may also be controlled.
The accompanying drawings, which are incorporated in and constitute part of the specification, illustrate various embodiments of the invention. Together with the general description, the drawings serve to explain the principles of the invention. In the drawings:
In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In other instances, well known methods, procedures and components have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present concepts. A number of descriptive terms and phrases are used in describing the various embodiments of this disclosure. These descriptive terms and phrases are used to convey a generally agreed upon meaning to those skilled in the art unless a different definition is given in this specification. Reference now is made in detail to the examples illustrated in the accompanying drawings and discussed below.
In some embodiments, at least some of the network connectors 16A-C may be associated with at least some of the outlets 14A-C. Network connector 16D is not associated with any outlet and in some embodiments, there may be outlets that are not associated with any network connectors. The association may be identified using any sort of marking, mold feature, physical proximity, color or other technique. In
In some embodiments, the communications means 132 includes a power line communications (“PLC”) device such as a PLC modem for communicating with a gateway 108a, 190a that is also equipped with a PLC device, the two PLC devices being coupled for communication via electric power lines such as the electrical wiring of a building or structure. In an embodiment, an Ethernet switch in the power node 100A or 100B is coupled to the power node PLC and provides one or more Ethernet connections such as an Ethernet connection enabling functions of the power node and an Ethernet connection available to devices external to the power node. More detail on an embodiment for the PLC to ethernet switch is shown in
In various embodiments, a networked power node 100A/100B utilizes the network to communicate with other devices. For example, a host gateway device 108 having a network interface 108a can transmit commands to or receive data from a power node 100A/100B. In this embodiment, a user device and/or processor 110 such as a controller, a special purpose controller, a personal computer, or a special purpose computer, is capable of issuing commands to or receiving data from a power node via the local network 107 by using a connection 109 to the gateway 108. In some embodiments, the host gateway includes one or more of the user device functions. Connections 109 between the user device 110 and the gateway 108 can use any suitable wired or wireless connection including the network connection types mentioned above, USB, RS-232, Bluetooth, or other wired or wireless connections.
A gateway 108 is configured in various embodiments to handle known TCP/IP based devices utilizing, for example, an IP based API available from the gateway. In an embodiment, the gateway 108 uses a simple SSDP discovery daemon allowing IP devices on the network 107 to find it. Typical TCP/IP devices include one or more of an iPhone®, iPad, iPod®, network connected tablet, TV, bluray player, personal computer, and the like.
In some networked embodiments a network management device 106 having a means for communicating with the network 107, such as a network controllers or network coordinators 106a, is included for implementing network management functions. Network management functions can include, among other things, maintaining a list of interconnected devices and maintaining routing tables. In particular, network coordinators are used with Zigbee networks and controllers are used with Z-Wave networks. Network management devices may supplement and/or duplicate the functionality provided by gateway device(s) 108 and their interconnected user devices 110.
And, in some networked embodiments, a second gateway 190 with second gateway communications block 190a interconnects via an external network 193 with a data center 194 (as shown). In other embodiments, the datacenter external network communicates via the host gateway connection 109.
In an exemplary system including one or more power nodes 100A/100B, a host gateway 108 and a user device 110, each of these devices includes memory for storing a device identification code. Device identification codes enable messages to be routed to the correct device. In an embodiment, a common group or home identification code is used to enable communication among members of the group.
Signal electronics include an input/output (“I/O”) block 210 coupled to each of a processor and memory block 212, and a communications block 132. In various embodiments, one or more of a power analyzer block 208, a dial selector block 216 and a temperature sensor block 218 are coupled to the I/O block. And, in some embodiments, an Ethernet switch is included in the communications block 132 or in addition to the communications block 132.
In various embodiments of the signal electronics section 116, a wireless module such as a Z-Wave or Zigbee module is used to implement the I/O block 210, processor block 212, and communications block 132. For example, a Sigma Designs ZM3102 Z-wave module is used in one embodiment and a Zigbee chipset is used in another embodiment. In some embodiments, the input/output functionality is enhanced with a general purpose I/O expander integrated circuit such as an NXP PCA9534BS 8-bit I2C-bus and SMBus low power I/O port with interrupt.
In an embodiment, a power/energy integrated circuit such as a Cirrus Logic CS 5463 integrated circuit may be used to implement the power analysis functionality of the power analyzer block 208. Power consumption and other data available from the power analysis device includes one or more of real/active power, instantaneous and/or RMS values of current and voltage, apparent power, reactive power, fundamental power, and temperature sensing. As will be understood by persons of ordinary skill in the art, waveform profiles of one or more of voltage, current, and power can be constructed by any processor in signal communication with the I/O block.
The power section 114 includes a power sensor block 202, a power switch block 204, and a power outlet block 206. The power sensor block is coupled to a power source 119 via a first power circuit 138. The switch block 204 is coupled to the power sensor block via a second power circuit 140 and to an outlet 206 via a third power circuit 142. A load 121 is coupled to the outlet via a fourth power circuit 144.
The power analyzer 208 of the embodiment shown in
The processor block 212 is coupled to the I/O block 210 via a signal line 168. Where used, dial selector block 216 is coupled to the I/O block via a signal line 146 and temperature sensor block 218 is coupled to the I/O block via a signal line 166. The communications block is coupled to the I/O block via a communications a signal line 169.
In some embodiments, a metering system 309 is implemented in the processor 212. The metering system 309 may aggregate power consumption for each outlet 206 to produce a meter report. In some embodiments an over current protection system (“OCPS”) 313 is implemented in the processor 212. The over current protection system compares measured current for each outlet 206 and for all outlets against safety limits and disconnects offending appliances in case of excess loads. And, in some embodiments a change detection system (“CDS”) 311 is implemented in the processor 212. These systems are discussed more fully below.
The power bus 138 from the power supply 119, which may be an alternating current (AC) circuit, may be coupled into the communications block 132 utilizing a transformer 231. An analog front end (AFE) circuit 232 may be coupled to the transformer 231 to send and/or receive signals coupled on the power but 138. In one embodiment the AFE may be implemented using an INT1400 integrated circuit from Atheros Communications, Inc. The AFE may be coupled to a PLC media access controller (MAC) and physical layer interface (PHY) block 234. The PLC MAC/PHY 234 may be implemented using an INT6400 integrated circuit from Atheros Communications, Inc. The INT1400 AFE and INT6400 MAC/PHY integrated circuits may be compatible with the HomePlug® AV network protocol specification and may provide up to a 200 Mb/s signaling rate over the power line. The PLC communications may be used for the network 107 or as a part of the network 107. Other embodiments may be compatible with different PLC protocols.
The MAC/PHY 234 may provide a media independent interface (MII) 235 for ethernet protocol communication. The MII 235 may be coupled to an ethernet switch 236 integrated circuit such as the AR8236 6-Port Low-Power Fast Ethernet Switch from Atheros Communications, Inc. allowing communications between the various ethernet ports of the ethernet switch 236. One output of the ethernet switch 236 may be used to communicate to the processor 212 over communication signal line 169, which in the embodiment shown may be a 100-Base-T ethernet connection. The other four 10/100-Base-T ethernet connections 261 may be connected to RJ-45 ethernet connectors 16A-D that may have integrated magnetics components for compliance with ethernet specifications. Various embodiments may have any number of ethernet ports from the ethernet switch 236 with zero, one or more ports used inside the power node 100A/100B and zero, one or more ports brought out to ethernet connectors 266 with the power node 100A/100B bridging between the various ports.
In other embodiments, the ethernet switch 236 may provide functionality for the processor 212 to selectively communicate to a particular ethernet connector 16A-D. By using such functionality, the processor may be able to receive information about the device that is physically plugged into the particular ethernet connector 16A-D. As shown in
Alternative embodiments may include a bridge from the PLC connection to a wireless connection such as 802.11 Wi-Fi, 802.15.4 Zigbee, Z-Wave or other radio frequency networks. In some embodiments, the access point or gateway circuitry for the radio frequency network may connect to one port of the ethernet switch 236 to provide a communications link between the PLC network and the wireless network as well as the other ethernet ports. In other embodiments the access point or gateway circuitry may take the place of the ethernet switch 236 providing for the communication signal line 169 to the processor 212 as well as the bridge to the wireless network devices.
For the purposes of this specification and claims, bridging may refer to connections between two network segments performed at any level of the Open Systems Interconnection (OSI) Model, including network routing done at OSI Layer 3 (network layer), network bridging performed at OSI Model Layer 2 (data-link layer), network repeating performed at OSI Model Layer 1 (physical layer) or other methods of connecting two network segments and should not be limited to data-link layer bridging, and as such, may include methods that are not compliant with the IEEE 802.1 D bridging standard.
In the embodiment shown in
Power supplied to the outlet 206 is sensed by a power bus voltage sensor 302 and the power channel current sensor 304, together the power sensor block 202. Voltage and current sensor output signal lines 310, 312 are coupled to the power analyzer block 208 which is coupled to the I/O block 210. In some embodiments, voltage is measured at a gateway 108, 190 rather than at individual power nodes 100A/100B. This may provide valid measurements as it can be assumed that in most instances, the power node 100A/100B and the gateway 108, 190 are on the same voltage distribution leg in the home so the voltage between devices will not vary that much.
In an embodiment, a voltage sensor 302 measures the power node bus voltage. Here, the power supplied to each outlet 206 is known since outlet voltage for all outlets should be the same, and the respective outlet currents are measured by the respective current sensors 304. Further, the power being supplied to the power node 100A/100B from the power supply 119 is approximately equal to the power drawn by all of the power node outlets and is also know.
In some embodiments, the voltage at each outlet is monitored by a respective voltage sensor located between the outlet 206 and the power switch 204. This embodiment provides for, inter alia, measuring a load's voltage decay after the power switch is opened. In other embodiments, an analog multiplexor consisting of relays, field effect transistors (FETs), or other electro-mechanical or electronic devices, may be interposed between the voltage sensors and each outlet 206 to allow a single voltage sensor to selectively measure the voltage at each outlet 206 individually, independent of the state of the power switches 204
Interposed between the power supply 119 and the outlet 206 is a power switch 204. A power switch signal line 160 couples the I/O block 210 with the power switch. The switch may be any switch known in the art that allows for automated control, such as a mechanical or solid state relay, or a semiconductor switch. In one embodiment a latching type relay is used and in another embodiment a TRIAC type switch may be used.
The outlet 206 is coupled to a power output of the power switch 204 via the third power circuit 142. In some embodiments, an insertion switch 306 senses 314 whether a plug is inserted in the outlet 206 and provides an insertion signal to the I/O block 316.
In an embodiment, consumption of each connected load or appliance 121 is monitored during appliance standby periods such that standby power consumption is measured. Typically, an appliance's standby power level is the lowest non-zero power level associated with the appliance. Here, gateway and/or user device 108, 110 selections enable the user to interrupt power flow to an appliance in a standby mode. In some embodiments, the user can define a standby time period which, if exceeded, automatically opens the associated power switch 204 to interrupt the appliance standby power flow.
Plug insertion sensing may be accomplished by any means/device known to persons of ordinary skill in the art. For example, various embodiments employ a capacitive sensor, an optical sensor, and a mechanical sensor. All of these devices are referred to herein as an “insertion switch.”
In some embodiments, a dial selector 216 is coupled to the I/O block 210. The dial selector provides a means for selecting an environmental variable through the use of symbols, letters, numbers, colors, or other indicia associated with dial selector positions. For example, one setting might be used for a power node located in a home theatre while another setting might be used for a power node located in a bedroom. Environmental variables are used in various embodiments to designate a particular room, a category of electrical loads such as a home theatre, a predefined scene such as conserve energy, a particular use such as entertainment, and a particular time or season such as winter.
Where the dial selector 500 is used to designate location, an embodiment includes a multi-colored dial selector wheel 502 having eight colored segments arranged around the periphery of the wheel. In addition to the eight colored segments, black and white segments are included. Each segment corresponds to a switch 506 position. The colors may be used to indicate particular rooms or spaces within a home or another multi-space, multi-use environment such as an office suite or building. Black may be used to indicate a spare or user designated variable and white may be used to indicate a power node monitoring only state where control functions are disabled.
In some embodiments, a temperature sensor 218 is used to sense a temperature of the environment where the power node is located. Signals from the temperature sensor are coupled to the I/O block 210 via a temperature sensor signal line 322.
In operation, various embodiments of the power node 100A/100B are capable of supplying power to a load or, in embodiments with multiple power channels 308, to multiple loads. Load control including switching loads on and off is enabled by network communications 107 between a command issuing device such as a user device 110, network manager 106, or data center 194, and a command receiving device for a particular power node 132. For example, a command issued from the user device to turn a particular outlet on may be routed via the network to a particular power node communications block 132. The power node processor 212 receives the command from the I/O block 210, interprets the command, and sends the power switch an on signal 204 via the I/O block and signal line 160.
Outlets 206 may be capable of being turned on and off by direct commands from a user as described above. Outlets can also be turned on and off under program control. For example, under program control an outlet's state may be selected based on one or more of time, a selected load, energy pricing, power consumption during a particular period of time, environmental conditions, or other data available to a processor in signal communication with the power node I/O block 208.
Energy reporting and management functions are enabled by the bus voltage sensor 302, power channel current sensor 304, the outlet insertion switch 306, and the power node power analyzer 208. Power analyzer inputs include power node bus voltage sensed by the power node bus voltage sensor and outlet current(s) sensed for each power channel 308 by a respective power channel current sensor.
The power provided to each outlet 206 is know because the current supplied to each outlet is measured 304 and a single bus voltage that is common to all outlets is measured 302. From these measurements, the power analyzer 208 can send data to the I/O module 210 including instantaneous current and voltage. In various embodiments, the power analyzer can send additional data to the I/O module including one or more of real power, RMS voltage and current, apparent power, reactive power and fundamental power.
Data from the power analyzer 208 is available to any processor in signal communication with the I/O block 210. For example, a user device 110 can receive data from the power analyzer via the network 107. Instantaneous values, trends, and summaries of data are available from power analyzer data stored in the user device or another network accessible memory device, any of which can be reported to the user. In addition, outlet insertion switch 306 status is available to the I/O block, a first state indicating a plug is inserted in the outlet and a second state indicating no plug is inserted in the outlet.
In some embodiments, data from external sources, such as energy prices reported by an electric utility or electric system operator, are available whether manually entered or acquired from the network via a connection such as an internet connection via the data center 194 or an internet gateway. Using this electric rate/cost information and the electric consumption information, the user device is capable of reporting cost metrics such as instantaneous electric supply costs, summarized electric costs, period specific electric costs, and suggestions for lowering electric costs such as shifting electric loads to less costly times of the day.
In a power node with multiple outlets, a default mode may designate one of the outlets 206 as a master outlet. Depressing the power node “On” button 15 enables the master outlet by closing the respective power switch 204. In the default mode, all power node outlets other than the master outlet are slave outlets. If the master outlet is supplying power to a load 121, the slave outlets are similarly enabled. If the master outlet is not supplying power to a load, the slave outlets are disabled. Where interrelated components of a system such as an entertainment system connect with a common power node 100A, default mode operation allows one of the components to function as a master for turning slave components on and off.
In various embodiments, a processor in signal communication with the power node I/O block 210 infers the nature of the load 121 by analyzing data available from the power node 100A/100B. The method for inferring the nature of the load is referred to herein as Basic Analysis.
A variety of output data may be input and output from the power node power analyzer 208, the insertion switch 306, and the dial selector 216. The power node analyzer 208 may use inputs such as, but not limited to, instantaneous voltage measurements from the voltage sensor, instantaneous current measurements from the current sensor, and/or temperature measurements from the temperature sensor. It may output information such as, but not limited to, instantaneous, average, or root-mean-square (RMS) voltage, instantaneous, average, or root-mean-square (RMS) current, real, apparent, reactive or fundamental instantaneous, RMS or average power, or instantaneous or average temperature. The insertion switch may use plug insertion as an input and may output a state of the switch as open or closed contacts to indicate whether or not a plug is inserted. The dial selector may take a position of the color wheel (or other selection device) as its input and output information such as, but not limited to, a number, a room location, a set of neighbor appliances, a time of use, and/or type of power strip (single outlet or multiple outlets).
Basic analysis uses power clues and contextual information to identify likely device classes for a load, typically a home appliance. Basic analysis may detect whether a plug is inserted and consider standby and operational power consumption, power factor, and peak versus RMS current. In addition, one or more environmental factors including room location, neighbor appliances (in the same room), time of use, and type of power node (single outlet or multiple outlet) may be considered.
In basic analysis, load assessment typically utilizes a few data snapshots. For example, an appliance requiring 10 watts standby power and 200 watts operational power is located in a family room. These data fit the profile of a television and assuming no contra indication from the power factor and peak versus RMS currents, this load would likely be matched with a television.
Data for matching loads to appliances is in various embodiments maintained in storage accessible to the local network 107 or the external network 193. Local data storage devices include the gateway host 108 and the user device 110. External data storage devices include storage devices such as semiconductor and hard disc storage located in the datacenter 194.
Once an outlet/load is matched to a particular appliance, there is no need to run the matching process again unless the appliance is unplugged. In various embodiments, the plug insertion switch 306 sets a flag when a plug is inserted in a respective outlet 206. A set flag results in the load assessment being run for the indicated outlet/load; once the assessment runs, the flag is cleared. With respect to a particular outlet, removal of a plug and reinsertion of a plug resets the flag, and causes the matching process to execute again.
Intermediate analysis examines patterns of use or behavior patterns to perform load assessments. Intermediate analysis may include monitoring power consumption to determine a load's duty cycle including frequency of use and duration of use.
In intermediate analysis, load assessment utilizes data snapshots taken at a low frequency. For example, power consumption might be checked and recorded once per minute. If the load being monitored is turned on frequently and operates for an extended period such as one or more hours each time it is turned on, these data might again suggest the appliance is a television.
Data for matching use profiles can be stored on the local network 107 or external to the network. Local data storage devices include the gateway host 108 and the user device 110. External data storage devices include computers located in the datacenter 194.
Advanced analysis assumes each load has a characteristic electrical signature, for example the frequency content of its voltage and current waveforms. Of particular interest may be the voltage waveform when the device is turned off or cut off from power and/or the current waveform when the device is turned on or connected to power.
As discussed above, information may be transmitted over the local network 107 and, in some embodiments, over the external network 193. In an embodiment, network information exchanges include transmission of one or more network messages such as one or more of: a) waveform profiles; b) change detection system (CDS) filter profile; c) meter report; d) over current alert; and, e) instantaneous power.
In some embodiments, either of the power strip 100A/100B or the gateway host 108 polls the other device to obtain information. For example, the gateway host 108 might poll the power strip 100A/100B, requesting a meter report. In response to the polling request, the power strip 100A/100B would send the meter report to the gateway host 108.
On the external network 193, messages are exchanged between the gateway host 108 and the data center 194. The gateway host 108 transmits waveform profiles to the data center 194 and the data center 194 transmits appliance identifications and matched CDS filter profiles to the gateway host.
Messages may be used in a variety of ways. Instantaneous power shows instantaneous consumption based on on-demand current and/or power readings. Instantaneous power readings may be transmitted on demand, in response to network query, or upon CDS event. They may be used in ways such as (but not limited to) the generation of composite dashboards, overall household load, and breakdowns of individual contributions. By use of CDS change-threshold detection polling can be eliminated and network traffic reduced.
Meter reports may integrate instantaneous power over time to provide power consumption during particular time periods by aggregating power consumption reports. Smart meter consumption reporting for individual outlet(s) may be voluntary, scheduled, or on-demand. It may be thought of as conventional power consumption metering. Some embodiments may utilize a Z-Wave standard smart meter class to implement efficient scheduling and automatically send pertinent consumption reports to a gateway host.
Waveform profiles show how voltage and current vary with time; notably, waveform profiles of voltage and/or current may be, as discussed above, available for each outlet/load 206/121. Waveforms of calculated parameters (such as power) may also be generated by the power analyzer. These messages may be sent from the power strip 10A to a gateway host 108 upon threshold events generated by power strip change detection system (CDS). Waveform profiles may be used to match loads with known appliances. In the datacenter 194, waveform profiles may be be matched against a signature database and used as an indicator for device or device class identification. Waveform profiles may also be used for automation purposes in identification of internal appliance states.
Overcurrent alarms may provide a warning that a current rating and/or capacity of the power strip 100A, or a single outlet 206, has been exceeded. They may be sent from the power strip to a gateway host upon a signal from the power node's Over Current Protection System (OCPS). Whenever an over current situation occurs, there may be short circuit hazards involved, or incorrect operation of the device plugged into the power strip 100A/100B. In either case, generating these over current alert messages on the network provides a means to inform users via a user device or via notice from the data center that remedial action should be taken. In some embodiments, the power strip may automatically cut off power to the offending outlet(s) in addition to sending a message.
A change detection system (“CDS”) profile provides filter parameters controlling change detection system filter behavior for a single outlet/load. CDS filter parameters include any of voltage, current, power, insertion switch state, temperature, and metrics based on these parameters. They may be sent from a gateway host to the power strip to modify change detection filter properties for a single outlet 206. Filter profiles are used to fine tune the power strip hosted change detection system which limits network traffic to only significant or interesting traffic such as significant waveform profiles and significant power consumption changes.
As mentioned above, one device may poll another device to obtain information. Another alternative is automatic reporting triggered by a changed state. In this embodiment, the processor 212 includes a change detection system 311 that monitors one or more variables such as power, current, and voltage. A change in the variable being monitored that exceeds a threshold value triggers automatic reporting. For example, if a threshold power change of 10 watts is set, a load change from 195 to 200 watts would not be reported by the CDS; but, a load change from 195 to 205 watts would be reported.
From the above, it can be seen that use of CDS triggered reporting rather than polling offers a means to reduce network traffic. Traffic is reduced because only exceptional events are reported over the network. Criteria for defining exceptional events are defined in CDS filter profiles. The filter profile to be applied to a particular outlet/load 206/121 is selected when waveform data sent to the data center is matched with a particular appliance. For example, if load waveform data sent to the datacenter is matched with a television known to consume 10 watts in standby and 200 watts in operation, the CDS filter profile might ignore spurious/uninteresting load changes below 10 watts.
Reporting can also be triggered based on elapsed time. For example, instantaneous power might be reported automatically every 2 seconds, or other time period in other embodiments. In an embodiment, reporting is based on a hybrid system including multiple reporting systems. For example, any plurality of time triggered reporting, CDS triggered reporting, and polling are used together.
In some embodiments, advanced analysis such as waveform analysis 904 may be performed and used as an input to the change detection system 311. Measurements may be taken at regular intervals (such as every 12 seconds or other intervals) to create the waveforms. In addition to the uses mentioned above, embodiments of the power node for energy management 100A/100B include informing users of individual appliance power consumption, enabling control of individual outlets to, inter alia, interrupt appliance standby power flows, and managing or lowering one or both of energy consumption and energy cost.
In one commercial embodiment, a consumer kit may include a plurality of multi and/or single outlet power nodes 100A/100B, a gateway 108, and a controller or user device 110. During manufacture and testing, these devices may be preconfigured with identification codes allowing interoperation. The controller may also be preprogrammed with home, night and away selections. The home selection may enable all of the power node outlets 206 by closing the respective power switches 204. The night selection may enable the default mode of multi outlet power nodes and disable single outlet power nodes. The away selection may disable all of the power node outlets.
TV 950 may be drawing electrical power from power outlet 914E through power cord 951 which may have an electrical plug that is plugged into the power socket 914E. The TV 950 may also provide functionality such as, but not limited to, internet TV, digital living network alliance (DLNA) compliant media streaming, remote configuration, or other functions that may use a network. The TV 950 may then have a network cable 952 plugged into network connector 916E.
Networked lamp 980 may allow for control of its on/off state and/or brightness through a network. The networked lamp 980 may have its power cord 981 plugged into socket 914C and be drawing power from socket 914C. The networked lamp 980 may have a network cable 982 plugged into network connector 916D. The network cable 982 and the power cord 981 may be plugged into a network connector 916D and power socket 914C respectively, that are not associated with each other.
Networked coffee pot 960 may provide remote brew initiation, remote status, or other functionality over a network. The networked coffee pot 960 may have its power cord 961 plugged into socket 914B and be drawing power from socket 914B. The networked coffee pot 960 may have a network cable 962 plugged into network connector 916B allowing the networked coffee pot 960 to communicate over the bridged network 107.
Vacuum cleaner 970 may be a legacy device with no network functionality. The vacuum cleaner 970 may be plugged into power socket 914A via power cord 971. Network connector 916A may not have anything plugged in. Computer system 990 may be plugged into a wall outlet directly and not be drawing power from the power node 100D. But the computer system 990 may have a network cable 992 plugged into network connector 916F to access the bridged network 107.
The particular power socket 914E where the TV 950 is plugged in may be identified at block 530A. In a simple embodiment, the processor 212 may be pre-programmed to understand a pre-determined association between the network connector 916E and the power socket 914E. Other embodiments may be used in place of the simple block 530A such as flowchart 530B, flowchart 530C, or other methods, to identify the particular power socket 914E where the TV 950 is plugged in. Flowcharts 530B and 530C are described below.
At least some of the information received about the TV 950 as well as an identifier of the particular power socket 914E may be sent across the PLC network interface in the power node 100D at block 514. The identifier of the particular power socket 914E may be dependent on the embodiment but may include such information as the network address, such as the internet protocol (IP) address and/or the MAC address of the processor 212 in the power node and an identifying number associated with the particular power socket 914E within the power node 100D. In some embodiments, additional information about the TV 950 may also be sent across the PLC network.
At various points in time, the processor 212 may receive commands to turn power on or off at the particular power socket 914E in block 515. The commands may come from the gateway 108 or other device based on a timer, a user input, changing energy cost or availability, another device being turned on or off, or other event. If the power node 100D loses power, the method may end at block 516.
Flowchart 530B may start at block 531B if it is time to identify a particular power socket associated with a device, such as the networked coffee pot 960, that is connected to network connector 916B, such as in place of block 530A in flowchart 510. The processor 212 may turn off the power to a power socket in the power node 100D, such as power socket 914A, at block 532B. The processor 212 may attempt to communicate with the networked coffee pot 960 over the network connector 916B at block 533B. Since the networked coffee pot 960 is still receiving power through power outlet 914B, the communication is successful. Because the communication at block 533B is successful, the processor 212 may turn the power back on for power socket 914A and turn off power to power socket 914B at block 534B although in some embodiments, the power to the previous power socket 914A may be left off, or left off if the power socket 914A was off before the method started. In other embodiments, only those power sockets that are on when the method starts may be checked.
Once the next power socket 914B has been turned off, communication with the networked coffee pot 960 may be attempted again at block 533B. Since the power has been turned off for power socket 914B, the networked coffee pot 960 is now off and the communication attempt is unsuccessful, so the processor 212 may now identify that the networked coffee pot 960 is plugged into power socket 914B at block 535B. Power to power socket 914B may be turned back on at block 536B and the rest of the method continued at block 537B.
Flowchart 530C shows yet another alternative embodiment of identifying a particular power socket associated with a device, such as the networked lamp 980, that may be using network connector 916D. If it is time to identify the particular power socket being used by the networked lamp 980 at block 531C, the information that was previously received, such as in block 512 of flowchart 510, may be used to predict power parameters at block 532C of the networked lamp 980.
In some embodiments, the information received may include power parameters, such as on power, off power, power factor, ripple current, or other parameters. In other embodiments, the information received may include the type of device, such as a TV, coffee pot, lamp, vacuum, or other type of device that may be used to predict a typical power parameter for such a device. For example, a networked lamp may draw very little power, <100 milliwatts (mW), when the lamp is off, and may draw the wattage of a typical incandescent light bulb when on, such as 40 watts (W), 60 W, 75 W or 100 W. In other cases the information received may be used to acquire additional information about a device. In some embodiments, the information received may be a MAC address that may then be used for SSDP queries to acquire more detailed information about the networked light 980. In one embodiment, the make and model of the networked lamp 980 may be acquired, which may then be used to look up information on the internet or other database to determine a power parameter for that particular make and model of networked lamp 980. For the purposes of this description, a prediction of 60 W for overall power usage may be made for the network lamp 980 based on the information received.
At block 533C, the processor 212 may measure one or more power parameters at each power socket 914A-E. In a typical embodiment, a simple RMS power measurement may be taken. Other embodiments may measure a second power parameter such as power factor to help identify whether the load is an inductive load as would be typical for an electric motor. Other embodiments may not measure root-mean-square (RMS) power but may measure RMS current or ripple current or one or more other parameters related to the power delivered to each power socket 914A-E. In the system 900, measurements of 800 W for power socket 914A, 100 mW for power socket 914B, 61 W for power socket 914C, 0 W for power socket 914D and 157 W for power socket 914E are taken at block 533C and compared to the predicted power of 60 W for the networked lamp 980 at block 534C. Since the power or 61 W at power socket 914C is the closest to the predicted power of 60 W for the networked lamp 980, power socket 914C is identified as the particular power socket used by the networked lamp 980 and the overall method may continue at 535C.
Various algorithms may be used to determine which measured value is closest to the predicted value including a simple difference, a difference with limits so that if the value is outside a maximum or minimum limit, the value may not be considered, curve fitting, or other algorithms. If more than one power parameter is predicted and measured, various algorithms using one or more of the parameters may be used including weighted sums of the differences, using one parameter as a limiting range and another for a difference, or any other algorithm.
Because the networked lamp 980 is using a network connector 916D and a power socket 914C that are not physically associated with each other, if the processor 212 simply uses the pre-determined association, an incorrect power socket 914D may be identified. By using the method shown in either flowchart 531B or 531C, the proper particular power socket 914C being used may be identified.
In many embodiments, the methods described in
Unless otherwise indicated, all numbers expressing quantities of elements, optical characteristic properties, and so forth used in the specification and claims are to be understood as being modified in all instances by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the preceding specification and attached claims are approximations that can vary depending upon the desired properties sought to be obtained by those skilled in the art utilizing the teachings of the present invention. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical value, however, inherently contains certain errors necessarily resulting from the standard deviations found in their respective testing measurements. The recitation of numerical ranges by endpoints includes all numbers subsumed within that range (e.g. 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).
As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the content clearly dictates otherwise. Thus, for example, reference to an element described as “an LED” may refer to a single LED, two LEDs or any other number of LEDs. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise. As used herein, the term “coupled” includes direct and indirect connections. Moreover, where first and second devices are coupled, intervening devices including active devices may be located there between.
The description of the various embodiments provided above is illustrative in nature and is not intended to limit the invention, its application, or uses. Thus, different variations beyond those described herein are intended to be within the scope of the embodiments of the present invention. Such variations are not to be regarded as a departure from the intended scope of the present invention. As such, the breadth and scope of the present invention should not be limited by the above-described exemplary embodiments, but should be defined only in accordance with the following claims and equivalents thereof.
This application is a continuation of International Patent Application No. PCT/US11/025350 filed on Feb. 18, 2011, which is a continuation-in-part of U.S. patent application Ser. No. 12/777,229 filed on May 10, 2010 and is a continuation-in-part of International Patent Application No. PCT/US10/053625 filed on Oct. 21, 2010, the entire contents of which are all hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4858141 | Hart et al. | Aug 1989 | A |
5258656 | Pawlick | Nov 1993 | A |
5301122 | Halpern | Apr 1994 | A |
5483153 | Leeb et al. | Jan 1996 | A |
5650771 | Lee | Jul 1997 | A |
5717325 | Leeb et al. | Feb 1998 | A |
5754963 | Nunneley et al. | May 1998 | A |
6445087 | Wang et al. | Sep 2002 | B1 |
6476729 | Liu | Nov 2002 | B1 |
6492897 | Mowery | Dec 2002 | B1 |
6987444 | Bub et al. | Jan 2006 | B2 |
6993417 | Osann, Jr. | Jan 2006 | B2 |
7579711 | Menas et al. | Aug 2009 | B2 |
7663866 | Lee et al. | Feb 2010 | B2 |
7772718 | Lee et al. | Aug 2010 | B2 |
7885917 | Kuhns et al. | Feb 2011 | B2 |
7961111 | Tinaphong et al. | Jun 2011 | B2 |
7970542 | Bent et al. | Jun 2011 | B2 |
8013545 | Jonsson | Sep 2011 | B2 |
20030050737 | Osann | Mar 2003 | A1 |
20040175078 | Imamura | Sep 2004 | A1 |
20060202557 | Menas et al. | Sep 2006 | A1 |
20060271544 | Devarakonda et al. | Nov 2006 | A1 |
20070041340 | Binder | Feb 2007 | A1 |
20070050647 | Conroy et al. | Mar 2007 | A1 |
20070091925 | Miyazaki et al. | Apr 2007 | A1 |
20070135973 | Petite | Jun 2007 | A1 |
20070155349 | Nelson et al. | Jul 2007 | A1 |
20070297112 | Gilbert | Dec 2007 | A1 |
20080094210 | Paradiso et al. | Apr 2008 | A1 |
20090059602 | Santos et al. | Mar 2009 | A1 |
20090198385 | Oe et al. | Aug 2009 | A1 |
20090207034 | Tinaphong et al. | Aug 2009 | A1 |
20090234512 | Ewing et al. | Sep 2009 | A1 |
20090236909 | Aldag et al. | Sep 2009 | A1 |
20090322159 | DuBose et al. | Dec 2009 | A1 |
20100005331 | Somasundaram et al. | Jan 2010 | A1 |
20100084992 | Valois et al. | Apr 2010 | A1 |
20100090542 | Johnson et al. | Apr 2010 | A1 |
20100109619 | Tsou et al. | May 2010 | A1 |
20100141153 | Recker et al. | Jun 2010 | A1 |
20100145542 | Chapel et al. | Jun 2010 | A1 |
20100191487 | Rada et al. | Jul 2010 | A1 |
20100264752 | Wong et al. | Oct 2010 | A1 |
20110031819 | Gunwall | Feb 2011 | A1 |
20110062874 | Knapp | Mar 2011 | A1 |
20110090042 | Leonard et al. | Apr 2011 | A1 |
20110098867 | Jonsson et al. | Apr 2011 | A1 |
Number | Date | Country |
---|---|---|
101-2009-0095689 | Sep 2009 | KR |
Number | Date | Country | |
---|---|---|---|
20120060044 A1 | Mar 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2011/025350 | Feb 2011 | US |
Child | 13289160 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2010/053625 | Oct 2010 | US |
Child | PCT/US2011/025350 | US | |
Parent | 12777229 | May 2010 | US |
Child | PCT/US2010/053625 | US |