Patent Grant
10732651
This patent specification relates to system monitoring and control for property and/or environmental control systems. More particularly, this patent specification relates to systems and methods for using a network enabled, battery powered thermostat to monitor and control an HVAC system while conserving the use of energy.
Substantial effort and attention continue toward the development of newer and more sustainable energy supplies. The conservation of energy by increased energy efficiency remains crucial to the world's energy future. According to an October 2010 report from the U.S. Department of Energy, heating and cooling account for 56% of the energy use in a typical U.S. home, making it the largest energy expense for most homes. Along with improvements in the physical plant associated with home heating and cooling (e.g., improved insulation, higher efficiency furnaces), substantial increases in energy efficiency can be achieved by better control and regulation of home heating and cooling equipment.
As is known, for example as discussed in the technical publication No. 50-8433, entitled “Power Stealing Thermostats” from Honeywell (1997), early thermostats used a bimetallic strip to sense temperature and respond to temperature changes in the room. The movement of the bimetallic strip was used to directly open and close an electrical circuit. Power was delivered to an electromechanical actuator, usually relay or contactor in the HVAC equipment whenever the contact was closed to provide heating and/or cooling to the controlled space. Since these thermostats did not require electrical power to operate, the wiring connections were very simple. Only one wire connected to the transformer and another wire connected to the load. Typically, a 24 VAC power supply transformer, the thermostat, and 24 VAC HVAC equipment relay were all connected in a loop with each device having only two external connections required.
When electronics began to be used in thermostats the fact that the thermostat was not directly wired to both sides of the transformer for its power source created a problem. This meant either the thermostat had to have its own independent power source, such as a battery, or be hardwired directly from the system transformer. Direct hardwiring a “common” wire from the transformer to the electronic thermostat may be very difficult and costly. However, there are also disadvantages to using a battery for providing the operating power. One primary disadvantage is the need to continually check and replace the battery. If the battery is not properly replaced and cannot provide adequate power, the electronic thermostat may fail during a period of extreme environmental conditions.
Because many households do not have a direct wire from the system transformer (such as a “common” wire), some thermostats have been designed to derive power from the transformer through the equipment load. The method for powering an electronic thermostat from the transformer with a single direct wire connection to the transformer is called “power stealing” or “power sharing.” The thermostat “steals,” “shares” or “harvests” its power during the “OFF” periods of the heating or cooling system by allowing a small amount of current to flow through it into the load coil below its response threshold (even at maximum transformer output voltage). During the “ON” periods of the heating or cooling system the thermostat draws power by allowing a small voltage drop across itself. Ideally, the voltage drop will not cause the load coil to dropout below its response threshold (even at minimum transformer output voltage). Examples of thermostats with power stealing capability include the Honeywell T8600, Honeywell T8400C, and the Emerson Model 1F97-0671. However, these systems do not have power storage means and therefore must always rely on power stealing or must use disposable batteries.
Additionally, microprocessor controlled “intelligent” thermostats may have more advanced environmental control capabilities that can save energy while also keeping occupants comfortable. To do this, these thermostats require more information from the occupants as well as the environments where the thermostats are located. These thermostats may also be capable of connection to computer networks, including both local area networks (or other “private” networks) and wide area networks such as the Internet (or other “public” networks), in order to obtain current and forecasted outside weather data, cooperate in so-called demand-response programs (e.g., automatic conformance with power alerts that may be issued by utility companies during periods of extreme weather), enable users to have remote access and/or control thereof through their network-connected device (e.g., smartphone, tablet computer, PC-based web browser), and other advanced functionalities that may require network connectivity.
Issues arise in relation to providing microprocessor-controlled, network-connected thermostats, one or more such issues being at least partially resolved by one or more of the embodiments described herein below. On the one hand, it is desirable to provide a thermostat having advanced functionalities such as those associated with relatively powerful microprocessors and reliable wireless communications chips, while also providing a thermostat that has an attractive, visually pleasing electronic display that users will find appealing to behold and interact with. On the other hand, it is desirable to provide a thermostat that is compatible and adaptable for installation in a wide variety of homes, including a substantial percentage of homes that are not equipped with the “common” wire discussed above. It is still further desirable to provide such a thermostat that accommodates easy do-it-yourself installation such that the expense and inconvenience of arranging for an HVAC technician to visit the premises to install the thermostat can be avoided for a large number of users. It is still further desirable to provide a thermostat having such processing power, wireless communications capabilities, visually pleasing display qualities, and other advanced functionalities, while also being a thermostat that, in addition to not requiring a “common” wire, likewise does not require to be plugged into household line current or a so-called “power brick,” which can be inconvenient for the particular location of the thermostat as well as unsightly.
Described herein are advanced, multi-sensing, microprocessor-controlled intelligent or “learning” control units for which one or more of the embodiments is particularly suitable, the control units providing a rich combination of processing capabilities, intuitive and visually pleasing user interfaces, and network connectivity, while at the same time not requiring a C-wire (or line power from a household 110V source such as a wall plug) even though the requisite underlying control unit hardware can require greater instantaneous power than power-stealing can safely provide. The described control unit achieves these goals at least by virtue of the use of a rechargeable battery (or equivalently capable onboard power storage medium) that may recharge during time intervals in which the hardware power usage is less than what power stealing can safely provide, and that will discharge to provide the needed extra electrical power during time intervals in which the hardware power usage is greater than what power stealing can safely provide. Provided according to one or more embodiments herein are methods, systems and related architectures for facilitating network communications between the control unit and a cloud-based management server in a manner that promotes reduced power usage and extended service life of the rechargeable battery, while at the same time accomplishing timely data transfer between the thermostat and the cloud-based management for suitable and time-appropriate control of a system.
According to one embodiment, a thermostat is presented. The thermostat may include a plurality of heating, ventilation, and air conditioning (HVAC) connectors, a rechargeable battery, and a battery charging circuit configured to charge the rechargeable battery at least in part by harvesting power from an HVAC system through the plurality of HVAC connectors without requiring a common wire. The thermostat may also include a processor powered at least in part by the rechargeable battery. In one embodiment, the processor may be configured to operate in a low-power state, and a high-power state. The thermostat may further include a wireless communication module operatively coupled to the processor and configured to establish and maintain wireless communications with a router, including receiving transmissions from the router; and process the transmissions from the router by discriminating between a first type of transmission and a second type of transmission. In one embodiment, the first type of transmission may include keep-alive messages associated with a communication channel between a remote thermostat-controller server and the thermostat, and the second type of transmission may include information associated with controlling the HVAC system. The wireless communication module may be further configured to, in response to identifying a transmission of the second type during a time period in which the processor is operating in the low-power state, cause the processor to transition from the low-power state to the high-power state, whereby the processor can operate in the low-power state for an extended period of time while a Natural Address Translation (NAT) table entry in the router that is associated with the communication channel between the processor and the remote thermostat-controller server remains maintained during said extended period of time.
According to another embodiment, a method of controlling an environmental condition may be presented. The method may include charging a power supply using a first power harvested from an external power source; and powering a circuit with energy from the power supply. In one embodiment, the circuit may be configured to operate in a plurality of modes, and the plurality of modes may include a low-power mode where the circuit uses less power than the first power, and an operating mode where the circuit uses more power than the first power. The method may also include establishing one or more communication channels with a server through a gateway; and communicating with the server using a protocol. In one embodiment, the protocol may include a time interval that represents a time that the gateway is expected to maintain the one or more communication channels between transmissions; a first type of transmission sent from the server at least in part to maintain one of the one or more communication channels at the gateway, and a second type of transmission comprising data for controlling the environmental condition. The method may additionally include discriminating between transmissions of the first type and transmissions of the second type, and in response to identifying a transmission of the first type during a time period in which the circuit is operating in the low-power mode; allowing the circuit to continue operating in the low-power mode. The method may further include, in response to identifying a transmission of the second type during a time period in which the circuit is operating in the low-power mode, causing the circuit to transition from the low-power mode to the operating mode, and initiating a change in the environmental condition according to the transmission of the second type.
According to yet another embodiment, a system for controlling one or more property functions may be presented. The system may include a power manager including a power-storage module configured to provide a first power; and a power input configured to provide energy to the power-storage module by harvesting a second power from an external source, wherein the second power is less than the first power. The system may further include a processing function configured to control the one or more property functions and operate in a plurality of modes including a first mode where the processing function uses a third power and the third power is less than the second power, and a second mode where the processing function uses a fourth power that is higher than the second power and not greater than the first power. The system may additionally include a network-communication module configured to establish one or more communication channels to a controller server through a gateway; utilize a communication protocol with the controller server, where the communication protocol may include a time interval that represents a time that the gateway is expected to maintain the one or more communication channels between transmissions; receive a first transmission from the controller server through the one or more communication channels while the processing function operates in the first mode; determine that the first transmission was sent from the controller server to maintain one of the one or more communication channels, and that the first transmission does not require the processing function to operate in the second mode; receive a second transmission from the controller server through the one or more communication channels, wherein the second transmission includes information for controlling the one or more property functions; and cause the processing function to operate in the second mode after receiving the second transmission.
Many other embodiments, features, and aspects are disclosed further herein.
The subject matter of this patent specification relates to the subject matter of the following commonly assigned applications, each of which is incorporated by reference herein: U.S. Ser. No. 12/881,430 filed Sep. 14, 2010; U.S. Ser. No. 12/881,463 filed Sep. 14, 2010; U.S. Prov. Ser. No. 61/415,771 filed Nov. 19, 2010; U.S. Prov. Ser. No. 61/429,093 filed Dec. 31, 2010; U.S. Ser. No. 12/984,602 filed Jan. 4, 2011; U.S. Ser. No. 12/987,257 filed Jan. 10, 2011; U.S. Ser. No. 13/033,573 filed Feb. 23, 2011; U.S. Ser. No. 29/386,021, filed Feb. 23, 2011; U.S. Ser. No. 13/034,666 filed Feb. 24, 2011; U.S. Ser. No. 13/034,674 filed Feb. 24, 2011; U.S. Ser. No. 13/034,678 filed Feb. 24, 2011; U.S. Ser. No. 13/038,191 filed Mar. 1, 2011; U.S. Ser. No. 13/038,206 filed Mar. 1, 2011; U.S. Ser. No. 29/399,609 filed Aug. 16, 2011; U.S. Ser. No. 29/399,614 filed Aug. 16, 2011; U.S. Ser. No. 29/399,617 filed Aug. 16, 2011; U.S. Ser. No. 29/399,618 filed Aug. 16, 2011; U.S. Ser. No. 29/399,621 filed Aug. 16, 2011; U.S. Ser. No. 29/399,623 filed Aug. 16, 2011; U.S. Ser. No. 29/399,625 filed Aug. 16, 2011; U.S. Ser. No. 29/399,627 filed Aug. 16, 2011; U.S. Ser. No. 29/399,630 filed Aug. 16, 2011; U.S. Ser. No. 29/399,632 filed Aug. 16, 2011; U.S. Ser. No. 29/399,633 filed Aug. 16, 2011; U.S. Ser. No. 29/399,636 filed Aug. 16, 2011; U.S. Ser. No. 29/399,637 filed Aug. 16, 2011; U.S. Ser. No. 13/199,108, filed Aug. 17, 2011; U.S. Ser. No. 13/267,871 filed Oct. 6, 2011; U.S. Ser. No. 13/267,877 filed Oct. 6, 2011; U.S. Ser. No. 13/269,501, filed Oct. 7, 2011; U.S. Ser. No. 29/404,096 filed Oct. 14, 2011; U.S. Ser. No. 29/404,097 filed Oct. 14, 2011; U.S. Ser. No. 29/404,098 filed Oct. 14, 2011; U.S. Ser. No. 29/404,099 filed Oct. 14, 2011; U.S. Ser. No. 29/404,101 filed Oct. 14, 2011; U.S. Ser. No. 29/404,103 filed Oct. 14, 2011; U.S. Ser. No. 29/404,104 filed Oct. 14, 2011; U.S. Ser. No. 29/404,105 filed Oct. 14, 2011; U.S. Ser. No. 13/275,307 filed Oct. 17, 2011; U.S. Ser. No. 13/275,311 filed Oct. 17, 2011; U.S. Ser. No. 13/317,423 filed Oct. 17, 2011; U.S. Ser. No. 13/279,151 filed Oct. 21, 2011; U.S. Ser. No. 13/317,557 filed Oct. 21, 2011; U.S. Prov. Ser. No. 61/627,996 filed Oct. 21, 2011; PCT/US11/61339 filed Nov. 18, 2011; PCT/US11/61344 filed Nov. 18, 2011; PCT/US11/61365 filed Nov. 18, 2011; PCT/US11/61379 filed Nov. 18, 2011; PCT/US11/61391 filed Nov. 18, 2011; PCT/US11/61479 filed Nov. 18, 2011; PCT/US11/61457 filed Nov. 18, 2011; PCT/US11/61470 filed Nov. 18, 2011; PCT/US11/61339 filed Nov. 18, 2011; PCT/US11/61491 filed Nov. 18, 2011; PCT/US11/61437 filed Nov. 18, 2011; PCT/US11/61503 filed Nov. 18, 2011; U.S. Ser. No. 13/342,156 filed Jan. 2, 2012; PCT/US12/00008 filed Jan. 3, 2012; PCT/US12/20088 filed Jan. 3, 2012; PCT/US12/20026 filed Jan. 3, 2012; PCT/US12/00007 filed Jan. 3, 2012; U.S. Ser. No. 13/351,688 filed Jan. 17, 2012; U.S. Ser. No. 13/356,762 filed Jan. 24, 2012; PCT/US12/30084 filed Mar. 22, 2012; U.S. Ser. No. 13/434,573 filed Mar. 29, 2012; U.S. Ser. No. 13/434,560 filed Mar. 29, 2012; U.S. Ser. No. 13/440,907 filed Apr. 5, 2012; and U.S. Ser. No. 13/440,910 filed Apr. 5, 2012. The above-referenced patent applications are collectively referenced herein as “the commonly assigned incorporated applications.”
In the following detailed description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of the various embodiments of the present invention. Those of ordinary skill in the art will realize that these various embodiments of the present invention are illustrative only and are not intended to be limiting in any way. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.
In addition, for clarity purposes, not all of the routine features of the embodiments described herein are shown or described. One of ordinary skill in the art would readily appreciate that in the development of any such actual embodiment, numerous embodiment-specific decisions may be required to achieve specific design objectives. These design objectives will vary from one embodiment to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming but would nevertheless be a routine engineering undertaking for those of ordinary skill in the art having the benefit of this disclosure.
It is to be appreciated that while one or more embodiments are described further herein in the context of typical HVAC system used in a residential home, such as single-family residential home, the scope of the present teachings is not so limited. More generally, thermostats according to one or more of the embodiments are applicable for a wide variety of enclosures having one or more HVAC systems including, without limitation, duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings and industrial buildings. Further, it is to be appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons who are interacting with the thermostat or other device or user interface in the context of one or more scenarios described herein, these references are by no means to be considered as limiting the scope of the present teachings with respect to the person or persons who are performing such actions.
In addition to controlling HVAC systems, the embodiments described herein may also be used in the context of controlling any function related to property. As used herein, the term “property controller,” or commonly just “controller” may encompass HVAC controllers, thermostats, and many other types of controllers. For example, in addition to controlling an HVAC system, a controller may be used to control other property functions, such as sprinkler systems, light systems, security systems, entertainment systems, medical equipment, pet-care systems, emergency systems, distributed sensor networks, transportation systems, food-preservation systems, and/or any other type of system amenable to automated or interactive control. According to one embodiment, a property controller may be used to control an environmental condition, such as temperature, humidity, air flow, volume, and/or the like.
Some embodiments of thermostat 110 in
As used herein, a “learning” thermostat refers to a thermostat, or one of plural communicating thermostats in a multi-thermostat network, having an ability to automatically establish and/or modify at least one future setpoint in a heating and/or cooling schedule based on at least one automatically sensed event and/or at least one past or current user input.
As used herein, a “primary” thermostat refers to a thermostat that is electrically connected to actuate all or part of an HVAC system, such as by virtue of electrical connection to HVAC control wires (e.g. W, G, Y, etc.) leading to the HVAC system.
As used herein, an “auxiliary” thermostat refers to a thermostat that is not electrically connected to actuate an HVAC system, but that otherwise contains at least one sensor and influences or facilitates primary thermostat control of an HVAC system by virtue of data communications with the primary thermostat.
In one scenario, the thermostat 110 is a primary learning thermostat and is wall-mounted and connected to all of the HVAC control wires, while the remote thermostat 112 is an auxiliary learning thermostat positioned on a nightstand or dresser, the auxiliary learning thermostat being similar in appearance and user-interface features as the primary learning thermostat, the auxiliary learning thermostat further having similar sensing capabilities (e.g., temperature, humidity, motion, ambient light, proximity) as the primary learning thermostat, but the auxiliary learning thermostat not being connected to any of the HVAC wires. Although it is not connected to any HVAC wires, the auxiliary learning thermostat wirelessly communicates with and cooperates with the primary learning thermostat for improved control of the HVAC system, such as by providing additional temperature data at its respective location in the enclosure, providing additional occupancy information, providing an additional user interface for the user, and so forth.
It is to be appreciated that while certain embodiments are particularly advantageous where the thermostat 110 is a primary learning thermostat and the remote thermostat 112 is an auxiliary learning thermostat, the scope of the present teachings is not so limited. Thus, for example, while certain initial provisioning methods that automatically pair associate a network-connected thermostat with an online user account are particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors. By way of further example, while certain graphical user interfaces for remote control of a thermostat may be particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors. By way of even further example, while certain methods for cooperative, battery-conserving information polling of a thermostat by a remote cloud-based management server may be particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors.
Enclosure 100 further includes a private network accessible both wirelessly and through wired connections and may also be referred to as a Local Area Network or LAN. Network devices on the private network include a computer 124, thermostat 110 and remote thermostat 112 in accordance with some embodiments of the present invention. In one embodiment, the private network is implemented using an integrated router 122 that provides routing, wireless access point functionality, firewall and multiple wired connection ports for connecting to various wired network devices, such as computer 124. Each device is assigned a private network address from the integrated router 122 either dynamically through a service like Dynamic Host Configuration Protocol (DHCP) or statically through actions of a network administrator. These private network addresses may be used to allow the devices to communicate with each directly over the LAN. Other embodiments may instead use multiple discrete switches, routers and other devices (not shown) to perform more other networking functions in addition to functions as provided by integrated router 122.
Integrated router 122 further provides network devices access to a public network, such as the Internet, provided enclosure 100 has a connection to the public network generally through a cable-modem, DSL modem and an Internet service provider or provider of other public network service. Public networks like the Internet are sometimes referred to as a Wide-Area Network or WAN. In the case of the Internet, a public address is assigned to a specific device allowing the device to be addressed directly by other devices on the Internet. Because these public addresses on the Internet are in limited supply, devices and computers on the private network often use a router device, like integrated router 122, to share a single public address through entries in Network Address Translation (NAT) table. The router makes an entry in the NAT table for each communication channel opened between a device on the private network and a device, server, or service on the Internet. A packet sent from a device on the private network initially has a “source” address containing the private network address of the sending device and a “destination” address corresponding to the public network address of the server or service on the Internet. As packets pass from within the private network through the router, the router replaces the “source” address with the public network address of the router and a “source port” that references the entry in the NAT table. The server on the Internet receiving the packet uses the “source” address and “source port” to send packets back to the router on the private network which in turn forwards the packets to the proper device on the private network doing a corresponding lookup on an entry in the NAT table.
Entries in the NAT table allow both the computer device 124 and the thermostat 110 to establish individual communication channels with a thermostat management system (not shown) located on a public network such as the Internet. In accordance with some embodiments, a thermostat management account on the thermostat management system enables a computer device 124 in enclosure 100 to remotely access thermostat 110. The thermostat management system passes information from the computer device 124 over the Internet and back to thermostat 110 provided the thermostat management account is associated with or paired with thermostat 110. Accordingly, data collected by thermostat 110 also passes from the private network associated with enclosure 100 through integrated router 122 and to the thermostat management system over the public network. Other computer devices not in enclosure 100 such as Smartphones, laptops and tablet computers (not shown in
In some embodiments, thermostat 110 may wirelessly communicate with remote thermostat 112 over the private network or through an adhoc network formed directly with remote thermostat 112. During communication with remote thermostat 112, thermostat 110 may gather information remotely from the user and from the environment detectable by the remote thermostat 112. For example, remote thermostat 112 may wirelessly communicate with the thermostat 110 providing user input from the remote location of remote thermostat 112 or may be used to display information to a user, or both. Like thermostat 110, embodiments of remote thermostat 112 may also include sensors to gather data related to occupancy, temperature, light and other environmental conditions. In an alternate embodiment, remote thermostat 112 may also be located outside of the enclosure 100.
In heating, heating coils or elements 242 within air handler 240 provide a source of heat using electricity or gas via line 236. Cool air is drawn from the enclosure via return air duct 246 through filter 270, using fan 238 and is heated through heating coils or elements 242. The heated air flows back into the enclosure at one or more locations via supply air duct system 252 and supply air registers such as register 250. In cooling, an outside compressor 230 passes a gas such as Freon through a set of heat exchanger coils 244 to cool the gas. The gas then goes through line 232 to the cooling coils 234 in the air handler 240 where it expands, cools and cools the air being circulated via fan 238. A humidifier 254 may optionally be included in various embodiments that returns moisture to the air before it passes through duct system 252. Although not shown in
Referring to
For some embodiments, the backplate processor 316 is a very low-power device that, while having some computational capabilities, is substantially less powerful than the head unit processor 314. The backplate processor 316 is coupled to, and responsible for polling on a regular basis, most or all of the sensors 322 including the temperature and humidity sensors, motion sensors, ambient light sensors, and proximity sensors. For sensors 322 that may not be located on the backplate hardware itself but rather are located in the head unit, ribbon cables or other electrical connections between the head unit and backplate are provided for this purpose. Notably, there may be other sensors (not shown) for which the head unit processor 314 is responsible, with one example being a ring rotation sensor that senses the user rotation of an outer ring of the thermostat. Each of the head unit processor 314 and backplate processor 316 is capable of entering into a “sleep” state, and then “waking up” to perform various tasks.
The backplate processor 316, which in some embodiments will have a low-power sleep state that corresponds simply to a lower clock speed, generally enters into and out of its sleep mode substantially more often than does the more powerful head unit processor 314. The backplate processor 316 is capable of waking up the head unit processor 314 from its sleep state. For one embodiment directed to optimal battery conservation, the head unit processor 314 is allowed to sleep when its operations are not being called for, while the backplate processor 316 performs polling of the sensors 322 on an ongoing basis, maintaining the sensor results in memory 317. The backplate processor 316 will wake up the head unit processor 314 in the event that (i) the sensor data indicates that an HVAC operation may be called for, such as if the current temperature goes below a currently active heating setpoint, or (ii) the memory 317 gets full and the sensor data needs to be transferred up to the head unit processor 314 for storage in the memory 315. The sensor data can then be pushed up to the cloud server (thermostat management server) during a subsequent active communication session between the cloud server and the head unit processor 314.
By way of example, the head unit processor 314 can draw on the order of 250 mW when awake and processing. Other controller functions, such as an LCD module, can draw on the order of 250 mW when active. Moreover, the Wi-Fi module 312 can draw 250 mW when active, and needs to be active on a consistent basis such as at a consistent 2% duty cycle in some scenarios. However, in order to avoid falsely tripping the HVAC relays for a large number of commercially used HVAC systems, power-stealing circuitry is often limited to power providing capacities on the order of 100 mW-200 mW, which would not be enough to supply the needed power for many common scenarios. Table 1 shows how the total system power consumption of an example embodiment might be calculated.
As can be seen from Table 1, the dominant power is that of standby, though waking the head unit 8 times per hour (192 times per day) is also not insignificant. Switching each HVAC zone also takes power, estimated at ˜1 mA@3.3 v. One embodiment may be likely to be switching multiple circuits concurrently. This can significantly increase the power consumption and hence should also be optimized appropriately. In one embodiment, the processing functions may use more than 250 mW in the operating mode. In another embodiment, the processing functions may use more than 200 mW in the operating mode. In another embodiment, the processing functions may use more than 150 mW in the operating mode. In another embodiment, the processing functions may use less than 150 mW in the sleep mode. In another embodiment, the processing functions may use less than 100 mW in the sleep mode. Finally, in another embodiment, the processing functions may use less than 75 mW in the sleep mode.
As used herein, the term “network-communication module” may include all forms of hardware and software used to communicate between the controller and a network. For example, a network-communication module may include the Wi-Fi module 312 in this embodiment, as well as a cellular network interface, an Ethernet adapter, a LAN adapter, a Bluetooth interface, and/or any other type of wired or wireless interface with a network. In the case of Wi-Fi module 312, one embodiment may be implemented using Murata Wireless Solutions LBWA19XSLZ module, which is based on the Texas Instruments WL1270 chipset supporting the 802.11 b/g/n WLAN standard. Embodiments of the present invention configure and program Wi-Fi module 312 to allow thermostat 308 to enter into a low power or “sleep” mode to conserve energy until one or several events occurs. For example, in some embodiments the Wi-Fi module 312 may leave this low power mode when a user physically operates thermostat 308, which in turn may also cause activation of both head-unit processor 314 and backplate processor 316 for controlling functions in head-unit and backplate portions of thermostat 110.
It is also possible for Wi-Fi module 312 to wake from a low power mode at regular intervals in response to a beacon from wireless access point 324. To conserve energy, Wi-Fi module 312 may briefly leave the low power mode to acknowledge the beacon as dictated by the appropriate wireless standard and then return to a low power mode without activating the processors or other components of thermostat 308 in
In yet another embodiment, Wi-Fi module 312 may selectively filter an incoming data packet to determine if the header is merely an acknowledgement packet (i.e., a keep-alive packet) or contains a payload that needs further processing. If the packet contains only a header and no payload, the Wi-Fi module 312 may be configured to either ignore the packet or send a return acknowledgement to the thermostat management system or other source of the packet received.
In further embodiments, Wi-Fi module 312 may be used to establish multiple communication channels between thermostat 112 and a cloud-based management server as will be described and illustrated later in this disclosure. As previously described, thermostat 112 uses the multiple communication channels to receive different types of data classified with different levels of priority. In one embodiment, Wi-Fi module 312 may be programmed to use one or more filters and a wake-on-LAN feature to then selectively ignore or discard data arriving over one or more of these communication channels. For example, low-priority data arriving over a port on Wi-Fi module 312 may be discarded by disabling the corresponding wake-on-LAN feature associated with the port. This allows the communication channel to continue to operate yet conserves battery power by discarding or ignoring the low-priority packets.
Operation of the microprocessors 314, 316, Wi-Fi module 312, and other electronics may be powered by a rechargeable battery (not shown) located within the thermostat 110. In some embodiments, the battery is recharged directly using 24 VAC power off a “C” wire drawn from the HVAC system or a AC-DC transformer coupled directly into the thermostat 110. Alternatively, one or more different types of energy harvesting may also be used to recharge the internal battery if these direct methods are not available as described, for example, in U.S. Ser. No. 13/034,678, supra, and U.S. Ser. No. 13/267,871, supra. Embodiments of the present invention communicate and operate the thermostat 110 in a manner that promotes efficient use of the battery while also keeping the thermostat operating at a high level of performance and responsiveness controlling the HVAC system. Some embodiments may use the battery-level charge and the priority or relative importance of a communication to determine when a thermostat management system located on a public network such as the Internet may communicate with the thermostat 110. Further details on the communication methods and system used in accordance with these embodiments are described in detail later herein.
Turning now to power harvesting methods and systems,
The HVAC functions are controlled by the HVAC control general purpose input/outputs (GPIOs) 322 within microcontroller (MCU) 320. MCU 320 is a general purpose microcontroller such as the MSP430 16-bit ultra-low power MCU available from Texas Instruments. MCU 320 communicates with the head unit via Head Unit Interface 340. The head unit together with the backplate make up the thermostat. The head unit has user interface capability such that it can display information to a user via an LCD display and receive input from a user via buttons and/or touch screen input devices. According to some embodiments, the head unit has network capabilities for communication to other devices either locally or over the internet. Through such network capability, for example, the thermostat can send information and receive commands and setting from a computer located elsewhere inside or outside of the enclosure. The MCU detects whether the head unit is attached to the backplate via head unit detect 338.
Clock 342 provides a low frequency clock signal to MCU 320, for example 32.768 kHz. According to some embodiments there are two crystal oscillators, one for high frequency such as 16 MHz and one for the lower frequency. Power for MCU 320 is supplied at power input 344 at 3.0 V. Circuitry 336 provides wiring detection, battery measurement, and buck input measurement. A temperature sensor 330 is provided, and according to some embodiments and a humidity sensor 332 are provided. According to some embodiments, one or more other sensors 334 are provided such as: pressure, proximity (e.g. using infrared), ambient light, and pyroelectric infrared (PIR).
Power circuitry 350 is provided to supply power. According to some embodiments, when the thermostat is first turned on with insufficient battery power, a bootstrap power system is provided. A high voltage low dropout voltage regulator (LDO) 380 provides 3.0 volts of power for the bootstrap of the MCU 320. The bootstrap function can be disabled under MCU control but according to some embodiments the bootstrap function is left enabled to provide a “safety net” if the head unit supply vanishes for any reason. For example, if the head-unit includes the re-chargeable battery 384 and is removed unexpectedly, the power would be lost and the bootstrap function would operate. The input to this Bootstrap LDO 380 is provided by connectors and circuitry 368 that automatically selects power from common 362 (highest priority), cool 366 (lower priority); or heat (lowest priority) 364.
In normal operation, a 3.0 volt primary LDO 382 powers the backplate circuitry and itself is powered by VCC Main. According to some embodiments, high voltage buck 360 is provided as a second supply in the backplate. The input to this supply is the circuitry 368. According to some embodiments, the high voltage buck 380 can supply a maximum of 100 mA at 4.5 v. According to some embodiments, the VCC main and the Primary LDO 382 can be powered by a rechargeable battery (shown in
Rectified input 624 is input to the high voltage buck circuit 610, according to some embodiments. In buck circuit 610, which corresponds to high voltage buck 360 in
In order to control the HVAC functions, the HVAC function wire is shorted to the return or power wire. For example, in the case of heating, the W wire is shorted to the Rh (or R or Rc depending on the configuration). In the case of cooling the Y wire is shorted to the Rc (or R or Rh depending on the configuration). By shorting these two wires, the 24 VAC transformer is placed in series with a relay that controls the HVAC function. However, for power harvesting, a problem is that when these wires are shorted, there is no voltage across them, and when open, there is no current flow. Since power equals voltage multiplied by current, if either quantity is zero the power that can be extracted is zero. According to some embodiments, the power harvesting circuitry allows power to be taken from the two wires in both the states of HVAC—the HVAC “on” and the HVAC “off”.
In the HVAC “off” state, some energy can be harvested from these two wires by taking less energy than would cause the of the relay to turn on, which would cause the HVAC function to erroneously turn on. Based on testing, it has been found that HVAC functions generally do not turn on when (0.040 A*4.5V)=0.180 watts is extracted at the output. So after the input diodes, capacitors, and switching regulator, this allows us to take 40 mA at 4.5 volts from these wires without turning on the HVAC system.
In the HVAC “on” state, the two wires must be connected together to allow current to flow, which turns on the HVAC relay. This, however, shorts out the input supply, so our system does not get any power when the HVAC “on” switch is closed. To get around this problem, the voltage is monitored on the capacitors 612, 614 and 616 at the input switching power supply node 620. When the voltage on these capacitors “Cin” drops close to the point at which the switching power supply would “Drop out” and lose output regulation, for example at about +8 Volts, the HVAC “on” switch is turned off and Cin is charged. During the time that Cin is charging, current is still flowing in the HVAC relay, so the HVAC relay stays on. When the Cin capacitor voltages increases some amount, for example about +16 Volts, the HVAC “on” switch is closed again, Cin begins to discharge while it feeds the switching regulator, and current continues to flow in the HVAC relay. Note that Cin is not allowed to discharge back to the HVAC “on” switch due to input diodes 632. When the voltage on Cin drops to about +8 Volts the HVAC “on” switch is turned off and the process repeats. This continues until the system tells the HVAC “on” switch to go off because HVAC is no longer needed. According to some embodiments, the ability of the HVAC “on” switch to turn on and off relatively quickly is provided by circuitry 450 as shown in and described with respect to
According to some embodiments, one or more alternative power harvesting techniques are used. For example, rather than having the HVAC “on” switch turn on when the voltage on Cin reaches a certain point, it the system might turn off the “HVAC “on” switch for a predetermined period of time instead. According to some embodiments, power harvesting is enhanced by synchronizing the power harvesting with the AC current waveform.
Although the embodiment illustrated in
Generally, the power supply or power-storage module may receive energy from another source and then store that energy for use by the controller. This process of providing energy to the power supply or power-storage module may be called “charging” or “recharging;” however, it may also include all forms of providing energy, such as providing charge to capacitors, charging a secondary cell battery, or providing current to an inductor. This energy may be stored in the form of a magnetic or electric field, and/or in a battery cell. The source of the energy provided to the power supply or power-storage module may be sourced from any external power supply. The embodiment in
According to some embodiments, charger 673 is a USB power manager and li-ion battery charger such as the LTC4085-3 from Linear Technology. Backplate voltage 671 is input to charger 673. The circuitry 672 is used to select the charging current. In particular the value of resistor 674 (24.9 k) in parallel with resistor 634 (16.9 k) in combination with the inputs Double Current 638 and High Power 628 are used to select the charging current. If High Power 628 and Double Current 638 are both set to 0, then the charging current is 8.0 mA; if the High Power 628 is set to 0 and Double Current 638 is set to 1, then the charging current is 19.9 mA; if the High Power 628 is set to 1 and Double Current 638 is set to 0, then the charging current is 40.1 mA; and if the High Power 628 and Double Current 638 are both set to 1, then the charging current is 99.3 mA. Resistor 636 is used to set the default charge current. In the case shown, a 220 k resistor set the default charge current to 227 mA. According to some embodiments, a charge temperature range of 0-44 degrees C. is set via the Thermistor Monitoring Circuits.
According to some embodiments, the thermostat is capable of being powered by a USB power supply. This could be supplied by a user, for example, by attaching the thermostat via a USB cable to a computer or another USB power supply. In cases there a USB power supply is available, it is selected as the preferred power source for the thermostat and can be used to recharge the rechargeable battery. According to some embodiments, a charge current of about 227 mA is used when a USB supply source is available; a charge current of about 100 mA is used when an HVAC common wire is present; and a charge current of between about 20-40 mA is used when power is harvested from an HVAC heating and/or cooling circuit.
Thermostat access client 714 is a client application designed in accordance with aspects of the present invention to access a cloud-based management server 716 over public network 704. The term “thermostat management system” can be interchangeably referenced as a “cloud-based management server” for the thermostats, or more simply “cloud server”, in various descriptions hereinabove and hereinbelow. Because thermostat access client 714 is designed to execute on different devices, multiple client applications may be developed using different technologies based on the requirements of the underlying device platform or operating system. For some embodiments, thermostat access client 714 is implemented such that end users operate their Internet-accessible devices (e.g., desktop computers, notebook computers, Internet-enabled mobile devices, cellphones having rendering engines, or the like) that are capable of accessing and interacting with the cloud-based management server 716. The end user machine or device has a web browser (e.g., Internet Explorer, Firefox, Chrome, Safari) or other rendering engine that, typically, is compatible with AJAX technologies (e.g., XHTML, XML, CSS, DOM, JSON, and the like). AJAX technologies include XHTML (Extensible HTML) and CSS (Cascading Style Sheets) for marking up and styling information, the use of DOM (Document Object Model) accessed with client-side scripting languages, the use of an XMLHttpRequest object (an API used by a scripting language) to transfer XML and other text data asynchronously to and from a server using HTTP), and use of XML or JSON (Javascript Object Notation, a lightweight data interchange format) as a format to transfer data between the server and the client. In a web environment, an end user accesses the site in the usual manner, i.e., by opening the browser to a URL associated with a service provider domain. The user may authenticate to the site (or some portion thereof) by entry of a username and password. The connection between the end user entity machine and the system may be private (e.g., via SSL). The server side of the system may comprise conventional hosting components, such as IP switches, web servers, application servers, administration servers, databases, and the like. Where AJAX is used on the client side, client side code (an AJAX shim) executes natively in the end user's web browser or other rendering engine. Typically, this code is served to the client machine when the end user accesses the site, although in the alternative it may be resident on the client machine persistently. Finally, while a web-based application over Internet Protocol (IP) is described, this is not a limitation, as the techniques and exposed user interface technologies may be provided by a standalone application in any runtime application, whether fixed line or mobile. It is to be appreciated that although the TCP/IP protocol is set forth as the network protocol used for communications among the cloud-based management server 716, the thermostat access client 714, and other devices for some embodiments, it is set forth by way of example and not by way of limitation, with the use of any other suitable protocol, such as UDP over IP in particular, may be used without departing from the scope of the present teachings. In yet another embodiment, thermostat access client 714 may be a stand-alone application or “app” designed to be downloaded and run on a specific device such Smartphone 708 or table 710 device running the Apple iOS operating system, Google Android operating system or others.
It is to be appreciated that the embodiments described herein, while advantageously providing battery-conscious methods for reliable communication of thermostatically related data between the thermostats 110/112 and the cloud-based management server 716, are also advantageously configured to be compatible with a large variety of conventional integrated routers that service a large population of homes and businesses. Thus, by way of example only and not by way of limitation, the router (not shown) that services the private network 702 can be, for example, a D-Link DIR-655 Extreme N Wireless Router, a Netgear WNDR3700 RangeMax Dual Band Wireless USB Gigabit Router, a Buffalo Technology Nfiniti WZR-HP-G300NH Wireless-N Router, an Asus RT-N16 Wireless Router, Cisco Linksys E4200 Dual Band Wireless Router, or a Cisco Linksys E4200 Dual Band Wireless Router.
In one embodiment, cloud-based management server 716 illustrated in
Each of the thermostat 110 and remote thermostat 112 also communicate with cloud-based management server 716 through one or several communication channels established through public network 704. Like other devices on the private network 702, thermostat 110 and remote thermostat 112 do not have a public network address and therefore cannot communicate directly on the Internet or other public network without the assistance of the router and corresponding entries in NAT table 718. In the example in
As described above, one embodiment uses a router to connect the Public Network 704 to the Private Network 702. However, other embodiments may use many other devices and methods for connecting two networks. As used herein, the term “gateway” may be interpreted to encompass any device implementing a method of connecting one network to another network. Many embodiments discussed herein use gateways that perform address translation between multiple networks, such as the NAT table examples discussed above. However, it should be understood that a gateway may use any method of translating addresses between multiple networks.
In an alternative configuration, thermostats 110 and 112 may be configured with multiple communication channels to cloud-based management server 716 rather than a single connection as depicted with thermostat 110. As an example, thermostat 112 initiates the establishment of communication channels over three ports 60744, 60743, and 60722, causing the router to make three more entries in the NAT table 718 identified by NAT PORTs 1044, 1921 and 1758. The additional corresponding entries in NAT table 718 identified as NAT PORT 1044, 1921, and 1758 include SOURCE ADDRESS 192.168.1.110 and SOURCE PORTS 60744, 60744, 60722 each associated with DESTINATION ADDRESS 107.20.224.12 and DESTINATION PORT 443 of cloud-based management server 716. In various embodiments of the present invention, communications between cloud-based management server 716 and other thermostats may take place over a single communication channel as configured on remote thermostat 110 while other embodiments may use multiple communications channels as provided with thermostat 112.
As data is transferred using a protocol such as TCP/IP, the router in private network 702 modifies the addresses in packets of data passing over the communication channels between the private network and a server or device on the public network such as cloud-based management server 716. In one example, the router may receive a packet from remote thermostat 110 having a SOURCE ADDRESS field of 192.168.1.108 and a SOURCE PORT of 60720 combined with a DEST ADDRESS of 107.20.224.12 and DEST PORT 443 of cloud-based management server 716. Before placing this packet on the Internet, the router references NAT table 718 and replaces the SOURCE ADDRESS field and SOURCE PORT field values with the public address 76.21.3.203 assigned to the router and the corresponding NAT port 1022 respectively. A resulting modified packet header 720 in
During these communications, embodiments of the present invention take into consideration battery-levels of the thermostats and the impact on the performance of the thermostat. If a battery-level on a thermostat is low, further communications with a thermostat may impact the ability of the thermostat to perform essential functions such as controlling the HVAC system or communicating over the network. As illustrated in
The battery levels may be monitored by the thermostat 110 and/or by the cloud-based management server 716 in order to regulate the power used by any of the processing functions or processing circuits in the thermostat, such as head unit processor 314 and/or backplate processor 316. Oftentimes, as discussed above, the energy harvested from the HVAC system may provide less energy than may be required when the processing functions are operating in various modes. Therefore, the sleep state, or low power state of the processing functions may be configured such that the energy used during the sleep state by the processing functions is less than what is harvested from the HVAC system. Generally, a first power may be provided by the power-storage module that is higher than a second power that may be harvested from the HVAC system. Because of this configuration, the processing function may operate in a first mode, i.e., a sleep mode, which uses less power than the second power harvested from the HVAC system. This may allow for the power harvested from the HVAC system to both provide power to the power-supply module and to the processing functions while the processing functions are operating in the sleep mode (first mode). This may also enable the processing functions to operate in a second mode, i.e., an operating mode, which may require more instantaneous power than the HVAC harvesting may provide. The second mode may use a fourth power that is less than the first power that may be provided by the power-supply module, but it may also be more than the second power harvested from the HVAC system.
In one embodiment illustrated in
Prior to entering into a low power state, each thermostat 110/112 sends a connection-opening long-polling packet to the thermostat communication server 820. When a response is not required for normal operational purposes (i.e., when the cloud-based management server 716 has no instructions or requests to render), cloud-based management server 716 maintains a long-polling communication with thermostats 110/112 allowing the communication channels to remain open even though the actual data exchanged may be infrequent or subject to long delays. This not only uses the battery-charge of the thermostats more efficiently but reduces the overhead and delay associated with reestablishing a communication channel for each data transmission. In one embodiment, cloud-based management server 716 maintains the long-polling communication in a manner that preserves the entry in NAT table 718 by sending a keep-alive priority packet at regular keep-alive intervals. In one embodiment, the keep-alive priority packet is consistent with a keep-alive facility built into a TCP/IP protocol stack. If no messages need to otherwise be sent to the thermostats 110/112 within the long-polling time interval, the protocol stack sends one or more “keep-alive” packets to the router on private network 702 at respective keep-alive intervals that are less than the long-polling time interval, thereby preserving the entry in NAT table 718. In one embodiment, the keep-alive intervals are substantially less than the interval over which many common routers might otherwise flush their NAT table with respect to that particular connection.
At a predetermined time interval or upon an event occurrence, thermostats 110 and 112 may wake from a low power state to check on their respective battery-levels and perform other administrative functions. In accordance with some embodiments, the battery-level is transmitted over a wireless connection from each thermostat 110 and 112 through an access point 806 on the private network and then stored for future reference by thermostat communication server 820. For example, battery image 110A appears about 80% charged representing the battery-level inside thermostat 110 to be almost fully charged while battery image 112A appears about 20% charged thus indicating that the battery inside of thermostat 112 is at a low level. One embodiment of cloud-based management server 716 updates this data in a device-battery-charge table 816 that includes a device address, a battery-level, and a keep-alive interval used for the corresponding communication channel. For example, device-battery-charge table 816 provides that device address 76.21.3.203:1022 (corresponding to thermostat 110 by way of NAT table 718) has a “high” battery-level and a keep-alive interval set to 5000 time units. In contrast, device addresses 76.21.3.203:1044, 76.21.3.203:1921, and 76.21.3.203:1758 (corresponding to thermostat 112 by way of NAT table 718) in device-battery-charge table 816 all have a “low” battery-level and a longer keep-alive interval set to 10000. Some embodiments of cloud-based management server 716 may set the keep-alive interval shorter if the battery-level is high to reduce the chance that an entry in the NAT table 718 will be flushed by the router. If the battery-level is “low”, the keep-alive interval may be set to a maximum long-poll interval that represents a maximum time interval not likely to exceed a NAT time-out period of most router devices.
Some embodiments of cloud-based management server 716 may further use device-battery-charge table 816 to help determine when data should be communicated from cloud-based management server 716 to one or more thermostats. To implement, one embodiment further creates a power-priority table 818 that associates low and high battery-levels reported from each thermostat with high thermostatic importance data or low thermostatic importance data. In these embodiments, power-priority table 818 establishes a trade-off between the importance assigned to data being communicated compared with the drain on the current battery charge associated with the thermostat. For example, data communications with data classified as high thermostatic importance data may be filtered and transmitted even when the battery is low since the data is considered of higher importance to the overall operation of cloud-based management server 716 and the thermostat. In one embodiment, a low battery-level may be between 0 and 39% of charge capacity.
Data communications classified under a low thermostatic importance may not be transmitted when the battery level is low as indicated in power-priority table 818. Since the battery is not fully charged, low thermostatic importance data may not be transmitted in accordance with power-priority table 818 to preserve energy on the battery of the thermostat. Accordingly, low and high thermostatic importance data types are transmitted in accordance with some embodiments when the battery-level is detected as high or in a range from 80% to 100% charged.
In an alternate embodiment illustrated in
In some embodiments, the data communications may be classified in a number of different ways and often will be determined based on the particular implementation requirements of the cloud-based management server 716 and performance requirements for the thermostats. In one implementation, a high-priority data type may include data communications actively requesting a thermostat perform some function. This may include a data communication from cloud-based management server 716 requesting thermostat 110 or 112 to change a temperature setpoint. Another high-priority data type may include a data communication requesting thermostat 110 or 112 to turn on or turn off a cooling function. In contrast, low-priority data types may include certain operations or functions deemed less critical for a thermostat to perform immediately. Downloading a software update from cloud-based management server 716 to a thermostat is one example of a low-priority communication as the software update is not required and likely does not affect the immediate operation of the thermostat. In addition, it may also be preferred to not download a software update when a thermostat has a low battery-level as a partially-completed update may render the thermostat inoperable.
In one embodiment, processes in memory 902 may include a battery-level collection process 918 that stores a battery-level associated with the battery used to power a thermostat. As previously described, the battery-level in some embodiments is provided by the thermostat over a communication channel established over a network between the thermostat management system and the thermostat and provides an indication of remaining energy in the battery associated with the thermostat. The battery-level collection process is able to collect these battery-levels over a long period of time as a result of ongoing communications between the thermostat and the cloud-based management server 716, which includes the long-polling process that keeps the communication channels open between the cloud-based management server 716 and thermostats. In some embodiments, the battery-level data is stored in a device-battery-charge table 816 as illustrated in
Some embodiments may further include a data priority process 920 in memory 902 that classifies and prioritizes one or more types of data to be transmitted to the thermostat over a communication channel. Depending on the implementation, data priority process 920 classifies the data transmission according to a data priority ranging from a low thermostatic importance data type to a high thermostatic importance data type. In some implementations, the low thermostatic importance data is of lesser importance to the operation of the thermostat management system and the thermostat. For example, a low thermostatic importance data type may include a software update as the software update may not be required for the thermostat to operate. In comparison, high thermostatic importance data types may include data of higher importance to the operation of the thermostat management system such as a request to change a setpoint in a thermostat or turn-on heating or cooling in the HVAC system.
Further embodiments may also include a power-classification transmission process 922 that transmits data to a thermostat depending on a classification of the data and the battery-level associated with the thermostat. As previously described, the data priority classification ranges from a low thermostatic importance data type to a high thermostatic importance data type depending on the importance of the data to the overall operation of cloud-based management server 716 and the thermostat. Consequently, low thermostatic importance data may not be transmitted when a battery-level is low in order to conserve the battery power remaining on the thermostat. However, the power-classification transmission process 922 may transmit all data classifications when the battery-level associated with a thermostat is fully-charged or “high”.
Embodiments of the present invention may also include a long-polling process 924 in memory 902 to facilitate keeping the communication channel open with a thermostat. This long-polling process 924 initially receive receives a request over the network from a thermostat to establish the communication channel between the cloud-based management server 716 located on a public network and the thermostat located on a private network. In some embodiments, cloud-based management server 716 has a public network address registered on the Internet while the thermostat has a shared public network address provided through an entry in a NAT table from a router on a private network, such as NAT table 718 in
Next, thermostat communication server classifies one or more types of data to be transmitted to the thermostat over the communication channel according to a thermostatic importance ranging from a low thermostatic importance to a high thermostatic importance classification. (1004) In one implementation, the low thermostatic importance data type includes data of lesser importance to the operation of the overall thermostat management system and thermostat. These may include optional functions to be performed on the thermostat such as software update or other maintenance. Conversely, the high thermostatic importance data type includes data of higher importance to the operation of the thermostat management system and the thermostat and generally includes requests to actively perform an action on the thermostat such as changing a setpoint, turning-on/off heating or cooling or checking ambient temperature in a residence or commercial location where the thermostat is located.
Next, thermostat communication server stores a battery-level associated with a thermostat in a storage area accessible by the thermostat communication server. (1006) In some embodiments, each thermostat periodically checks its own battery and provides the battery-level to the thermostat communication server over a communication channel established over the network. Battery-level information for each thermostat may be stored in a device-battery-charge table, such as device-battery-charge table 816 as illustrated in
To keep the communication channel open, thermostat communication server may configure a long-poll interval for transmitting a keep-alive packet over the communication channel to the thermostat. (1008) In some embodiments, the thermostat communication server sets the long-poll interval to a maximum value not to exceed a NAT timeout period used by most routers, which is often approximately 100 minutes.
If no data passes between thermostat communication server and the thermostat (1010—No), a timer value, originally set to the long-poll interval, decreases over time within the communication protocol stack and the process continues. Eventually, if the long-poll interval runs out of time and the communication protocol stack on the thermostat communication server, such as TCP/IP, does not detect communication activity within the long-poll interval, the built-in keep-alive feature sends a packet to keep the NAT entry on the router and communication channel open. (1012) In some embodiments, the thermostat communication server may request to terminate the communication channel when the long-poll interval has elapsed and wait for new communication channel to be established by the thermostat.
Alternatively if there is data to be sent, the thermostat communication server checks the most recent battery-level of the thermostat before sending. (1010—Yes) One embodiment determines if there is a low battery-level associated with the thermostat (1014—Yes) that only data classified as high thermostatic importance data should be transmitted. (1016) This preserves some of the battery charge in the thermostat by not sending low thermostatic importance data. In some embodiments, thermostat communication server have predetermined classifications setup in advance according to a particular configuration requirement. If the data is of higher importance to the operation of the thermostat management system then the data is classified as a high thermostatic importance data type and should be sent even when there is a low battery-level. For example, high thermostatic importance data may include instructions sent to a thermostat actively requesting the thermostat change a temperature setpoint or other setting.
When the battery-level associated with the thermostat is not at a low level (1014—No), all data classified as low to high thermostatic importance will be transmitted as the battery on the thermostat is considered fully charged. (1018)
An example data flow chart in
In an alternate embodiment, a battery powered thermostat and system illustrated in
For example, thermostat 112 in
Settings within the Wi-Fi module (not shown) of thermostat 112 determine whether to process or discard the data depending on which communication channel the data is received. As a reflection of settings in the Wi-Fi module, a power-priority table 1104 identifies that the recent battery-level of thermostat 112 is at a low level, as illustrated by battery image 112A, and that ports 60744 and 60743 are used to process high and low data types respectively. Because the most recent battery-level was low, power-priority table 1104 also indicates in this example that the Wi-Fi module has been configured to ignore or discard low-priority data arriving on ports 60743 and process only high-priority data received over port 60744. Over time, thermostat 112 may update the configuration of the Wi-Fi module to accept or discard packets depending on the battery-level the thermostat 112 detects. If thermostat 112 later determines the battery-level is high, thermostat 112 reconfigures Wi-Fi module to subsequently process both low and high-priority data packets arriving over both ports. In alternate embodiments, Wi-Fi module may also be configured to use greater or fewer ports and process either greater or fewer data priority types. For example, three communication channels may be used to process either high-priority, medium-priority or low-priority data types rather than just either high-priority or low-priority data types.
Flowchart diagram in
Next, thermostat communication server classifies one or more types of data to be transmitted to the thermostat over the communication channel according to a data priority ranging from a low-priority data type to a high-priority data type. (1130) In one implementation, the low-priority data type includes data of lesser importance to the operation of the overall thermostat management system and thermostat. These may include optional functions to be performed on the thermostat such as software update or other maintenance. Conversely, the high-priority data type includes data of higher importance to the operation of the thermostat management system and the thermostat and generally includes requests to actively perform an action on the thermostat such as changing a setpoint, turning-on/off heating or cooling or checking ambient temperature in a residence or commercial location where the thermostat is located.
To keep the communication channel open, thermostat communication server may configure a long-poll interval for transmitting keep-alive packets over the plurality of communication channels to the thermostat. (1132) In some embodiments, the thermostat communication server sets the long-poll interval to a maximum value not to exceed a NAT timeout period used by most routers, which is often approximately 100 minutes.
If no data passes between thermostat communication server and the thermostat (1134—No), a timer, initially set to the long-poll interval, decreases over time within the communication protocol stack and the process continues. Eventually, if the long-poll interval runs out of time and the communication protocol stack on the thermostat communication server, such as TCP/IP, did not detect communication activity, the built-in keep-alive feature sends packets to keep the NAT entries on the router and the communication channels open. (1138) In some embodiments, the thermostat communication server may request the thermostat to terminate and reestablish the communication channel when the timer associated with the long-poll interval expires to help make sure the communication channel is available and operating properly.
Alternatively if there is data to be sent, the thermostat communication server checks the priority of the data and sends over the proper communication channel. Accordingly in one embodiment, if the data is classified as low-priority (1140—Yes), thermostat communication server sends the data over a communication channel reserved for low-priority data transmissions. (1142) Alternatively, if the data is classified as high-priority and not low-priority (1140—No), thermostat communication server sends the data over a communication channel reserved for high-priority data transmissions. (1148) In this embodiment, thermostat communication server segregates the data on different communication channels but allows the thermostat to determine whether to process or discard the data as it easy easier for the thermostat to obtain battery-level data and make a decisions. Generally, a determination may be made by the network-communication module (in this embodiment, the Wi-Fi module 312) that the a transmission is classified as a low-priority transmission at least in part because an indication that the power level of the power supply was below a threshold power level was sent to the server. In response, the transmission may be processed by the network-communication module while the processing function, or circuit, remains in the low-power mode.
In some embodiments, the thermostat may determine that the communication channels with thermostat communication server, such as with thermostat communication server 820, have not been established. (1152—No) Accordingly, one embodiment of the present invention may request and establish two communication channels between the thermostat communication server and the thermostat. (1154) In accordance with some embodiments, the thermostat reserves the first and second communication channels on the thermostat to receive data classified as low and high-priority data types. The thermostat initially configures its Wi-Fi module, such as Wi-Fi module 312 in
Alternatively, if the communication channels are established, (1152—Yes), the thermostat determines if a data packet has been received and requires further processing. (1160) In some embodiments, the Wi-Fi module on the thermostat may inspect the data packet header or payload and determine that the data packet needs no further processing and can be discarded. (1160—No) For example, the data packet may be discarded if it is a keep-alive packet meant to preserve the NAT table entries in the router or if the packet otherwise has no payload data associated with it. If the packet is discarded, the thermostat may conserve overall power consumed because other components in the thermostat, such as head unit processor 314 or backplate processor 316, can remain in a low power state. (1162)
If the packet does require further processing, (1160—Yes) then the thermostat may activate or power-up other portions of the thermostat to service the data packet received. (1164) In some embodiments, thermostat may activate head unit processor 314 to perform a change of a setpoint or other feature on the thermostat or may activate back plate processor 316 to gather sensor information as requested from thermostat communication server 820.
Once a packet has been processed or discarded, embodiments of the present invention check the current battery-level of the thermostat and adjust the communication channels to either accept or discard subsequent data packets. If the thermostat determines the battery charge is at or below a low battery-level, (1168—Yes) the Wi-Fi module is configured to discard subsequent data received over a first communication channel reserved to received low priority data. (1172) As previously described, some embodiments discard packets over a communication channel and port of the Wi-Fi module by turning off a wake-on-LAN feature for the channel. This causes subsequent low priority packets received on the channel to be ignored and discarded. In some implementations, the Wi-Fi module is configured to process packets on the second communication channel using a filter to locate the proper port number and enabling the wake-on-LAN feature for the selected filter. Lastly, if the battery charge is above the low battery-level (1168—No) then embodiments of the present invention enable processing of subsequently received packets over the first and second communication channels. (1178) For example, if the battery-level charge is high then embodiments of the present invention are adjusted to process more data and further improve the thermostat's performance and ability to respond to instructions and requests. After checking the battery-level and adjusting the Wi-Fi module, the thermostat returns to a low power state to conserve energy consumption and await the next event and/or data to be processed. (1158)
In another embodiment, a communication module, such as the Wi-Fi module, may be configured to establish one or more communication channels to a controller server through a gateway. The communication module may further be configured to utilize a communication protocol with the controller server, where the communication protocol includes a time interval that represents a time that the gateway is expected to maintain the one or more communication channels between transmissions. For example, this time may correspond to the time that a router is expected to maintain an address in an NAT table. After establishing the communication channels, the controller may receive a first transmission from the controller server through the communication channels while a processing function, such as the head unit processor 314 and/or the backplate processor 316, operates in a first mode, or a sleep mode. The controller may then determine that the first transmission was sent from the controller server to maintain one of the communication channels, and/or that the first transmission does not require the processing function to operate in the second mode. For example, the first transmission may comprise a header portion of information without a payload that requires processing by the processing functions. In addition to receiving the first transmission, the controller may also receive a second transmission from the controller server through the communication channels, where the second transmission includes information for controlling a property function associated with the controller. In this case, the second transmission may require processing by the processing function, and the controller may cause the processing function to operate in a second mode, or operating mode, after receiving the second transmission in order to process the second transmission.
An example data flow chart in
Once selected, thermostat 1204 gathers log data over the network from other thermostats 1206, 1208 and 1210 through local transfers 1212, 1214, and 1216 respectively. These local transfers include the log data from each thermostat combined into a common log 1216 identifying a time stamp, event type, device ID and data content for each entry. After a period of time or when memory (not shown) in thermostat 1204 fills up, the common log 1216 is uploaded over a communication channel to a central server such as the cloud-based management server 716. This approach allows event log information to be gathered using fewer uploads than would be required if each thermostat was required to upload individually. It also allows thermostats having a low battery-level to preserve their battery charge while still allowing such data to be collected and analyzed on a server such as cloud-based management server 716 in
As previously described, embodiments of the present invention select a proxy reporting thermostat to represent the other thermostats. (1218). In some embodiments, the proxy reporting thermostat is selected based on having the highest battery-level compared with the other battery powered thermostats in the thermostat reporting group. For example, thermostat 1204 in
Over time, the proxy reporting thermostat gathers events recorded from each of the thermostats in the thermostat reporting group. (1220) Proxy reporting thermostat may collect these events from each thermostat in the thermostat reporting group using a wireless ad-hoc connection or a wireless connection made available through a network access point or router. The proxy reporting thermostat generally continues to collect the data from the other thermostats until storage on the proxy reporting thermostat is full or has reached a maximum allocation for such logs. (1222) For example, a thermostat may have allocated 500 megabytes for storing the log information from multiple thermostats before triggering the upload process.
If the storage on the proxy reporting thermostat is full, one embodiment of the proxy reporting thermostat establishes a communication channel to a thermostat management system to store the thermostat events. (1224) For example, this may be connection over the Internet between the thermostat on a private network and the thermostat management system. Next, one embodiment uploads events gathered on the proxy reporting thermostat over the communication channel to the thermostat management system on behalf of the thermostats in the thermostat reporting group. (1226) Once the data in the common event log has been successfully uploaded, embodiments of the present invention clear the storage area on the proxy reporting thermostat of the events gathered from the thermostat reporting group. (1228). This makes way for storage of more events in the event log on the proxy reporting thermostat.
In one embodiment, illustrated in
According to one embodiment, the wireless access device 1302 may comprise a router. Many routers used in residential locations include a NAT table that translates public network addresses into private network addresses as described previously herein. Recall that the NAT may be flushed periodically by the router after a specified period of nonuse. In one embodiment, keep alive messages may be sent from the cloud-based management server 716 to the property controller in order to keep an entry in the NAT operation that is associated with the property controller.
According to one embodiment, the property controller may be a thermostat 1320. The thermostat 1320 may include, among other things, a Wi-Fi chip 1304 and a thermostat processor 1316. The thermostat processor 1316 may operate in at least two different modes. A first mode may be a low-power mode, or a sleep mode, where some of the functions of the thermostat processor 1316 are not fully operational in order to save power. A second mode may be a high-power mode, or operational mode, where some of the functions that were not fully operational in the low-power mode are operational to a greater extent. In one embodiment, a kernel 1312 (or other sub-components or sub-routines having equivalent background significance) may run while in the low-power mode, while an application 1314 may run while in the high-power mode. In one embodiment, when the thermostat processor 1316 is operating in the low-power mode, an interrupt 1322 may be received on a designated input of the thermostat processor 1316 to cause the thermostat processor 1316 to transition from the low-power mode to the high-power mode. In at least one embodiment, the thermostat processor 1316 may be implemented by the head unit processor 304 of
In one embodiment, the Wi-Fi chip 1304 may include, among other things, a radio 1306, a packet filtering function 1308, and a processor 1310. In one embodiment, the packet filtering function 1308 is operated on separate circuitry from the processor 1310, while in another embodiment the packet filtering function 1308 is implemented using the processor 1310. The processor 1310, like the thermostat processor 1316, may operate in at least a high-power mode and a low-power mode, possibly a sleep state and an operating state. In order to save power, the Wi-Fi chip 1304 may operate in a low-power state until messages are received from the wireless access device 1302.
In one embodiment, when the radio 1306 receives a message, it may pass the message to the packet filtering function 1308 prior to waking up the processor 1310. The packet filtering function 1308 may examine one or more fields within the message to determine whether the processor 1310 should wake up. In some cases, the radio 1306 may receive any messages that are electronically receivable by an antenna 1330 communicatively coupled to the radio 1306. The data filtering function 1308 may check the address of the messages to determine whether or not they are intended for the thermostat 1320. Messages that are not for the thermostat 1320 may be discarded without waking the processor 1310. Messages that are properly addressed to the thermostat 1320 may require further processing.
In one embodiment, some of the messages properly addressed to the thermostat 1320 may also be discarded in a similar fashion to messages that were not properly addressed to the thermostat 1320. For example, keep-alive messages sent from the cloud-based management server 716 that are merely intended to maintain an entry in the NAT of the wireless access device 1302 may be discarded without requiring additional processing. A keep-alive message will generally be addressed to the thermostat 1320; however, the packet filtering function 1308 may examine additional fields in addition to the address fields of the message in order to determine whether the message is a keep-alive message. In one embodiment, a single bit may represent a flag signifying a keep-alive message. If the packet filtering function 1308 determines that a message is not a keep-alive message and is properly addressed, the packet filtering function 1308 may wake up the processor 1310 for further processing. In one embodiment, the packet filtering function 1308 may be implemented using a simple mask that is compared bit by bit to one or more fields in a received message.
In one embodiment, the processor 1310 may examine one or more fields within the message to determine whether it should wake up the thermostat processor 1316. In some cases, this may mean causing the thermostat processor to transition from the low-power state to the high-power state by sending an interrupt 1322. The processor 1310 may also communicate with the thermostat processor 1316 via data communication lines 1324. The data communication lines 1324 may be implemented using any data communication protocol, such as SDIO, USB, I2C, RS-232, and/or the like. In one embodiment, the processor 1310 may determine whether the message contains information of high thermostatic importance or information critical to the operation of the thermostat 1320. Messages of high thermostatic importance may be passed to the thermostat processor 1320, while messages of low thermostatic importance may be discarded and/or saved until the thermostat processor 1316 is awakened for other reasons.
In addition to discarding keep-alive messages, the packet filtering function 1308 may additionally filter messages based on the port number. For example, a plurality of communication channel may be established, and the packet filtering function 1308 may discard messages based on the communication channel by which they were received. In another embodiment, the packet filtering function 1308 may pass these messages to the processor 1310, which may then determine whether to discard the message based on the communication channel by which it was received. In light of this disclosure it will be understood that combinations of these methods for preserving power in the thermostat 1320 by selectively processing messages received from the wireless access device 1302 may be used depending on the particular application. For example, keep alive messages may be filtered, along with messages based on thermostatic importance and/or messages based on port number.
The Rh wire, which leads to one side of the HVAC power transformer (or simply “HVAC transformer”) that is associated with a heating call relay, can go by different names in the art, which can include heating call switch power wire, heat call power return wire, heat return wire, return wire for heating, or return for heating. The Rc wire, which leads to one side of the HVAC transformer that is associated with a cooling call relay, can likewise go by different names including cooling call switch power wire, cooling call power return wire, cooling return wire, return wire for cooling, or return for cooling. In the case of single-HVAC-transformer systems having both heating and cooling functions, it is one and the same HVAC power transformer that is associated with both the heating call relay and cooling call relay, and in such cases there is just a single wire, usually labeled “R”, leading back to one side of that HVAC transformer, which likewise can go by different names in the art including call switch power wire, call relay power wire, call power return wire, power return wire, or simply return wire.
As illustrated generally in
Thermostat 1400 further comprises powering circuitry 1410 that comprises components contained on both the backplate 1404 and head unit 1402. Generally speaking, it is the purpose of powering circuitry 1410 to extract electrical operating power from the HVAC wires and convert that power into a usable form for the many electrically-driven components of the thermostat 1400. Thermostat 1400 further comprises insertion sensing components 1412 configured to provide automated mechanical and electrical sensing regarding the HVAC wires that are inserted into the thermostat 1400. Thermostat 1400 further comprises a relatively high-power head unit microprocessor 1432, such as an AM3703 Sitara ARM microprocessor available from Texas Instruments, that provides the main general governance of the operation of the thermostat 1400. Thermostat 1400 further comprises head unit/backplate environmental sensors 1434/1438 (e.g., temperature sensors, humidity sensors, active IR motion sensors, passive IR motion sensors, ambient visible light sensors, accelerometers, ambient sound sensors, ultrasonic/infrasonic sound sensors, etc.), as well as other components 1436 (e.g., electronic display devices and circuitry, user interface devices and circuitry, wired communications circuitry, wireless communications circuitry such as Wi-Fi and/or ZigBee chips) that are operatively coupled to the head unit microprocessor 1432 and/or backplate microprocessor 1408 and collectively configured to provide the functionalities described in the instant disclosure and/or the commonly assigned incorporated applications.
The insertion sensing components 1412 include a plurality of HVAC wiring connectors 1414, each containing an internal springable mechanical assembly that, responsive to the mechanical insertion of a physical wire thereinto, will mechanically cause an opening or closing of one or more dedicated electrical switches associated therewith. Exemplary configurations for each of the HVAC wiring connectors 1414 can be found in the commonly assigned U.S. Ser. No. 13/034,666, supra. With respect to the HVAC wiring connectors 1414 that are dedicated to the C, W, Y, Rc, and Rh terminals, those dedicated electrical switches are, in turn, networked together in a manner that yields the results that are illustrated in
Likewise, for clarity of presentation in
As illustrated in
Basic operation of each of the FET switches 1406 is achieved by virtue of a respective control signal (OFF or ON) provided by the backplate microcontroller 1408 that causes the corresponding FET switch 1406 to “connect” or “short” its respective HVAC lead inputs for an ON control signal, and that causes the corresponding FET switch 1406 to “disconnect” or “leave open” or “open up” its respective HVAC lead inputs for an OFF control signal. For example, the W-Rh FET switch keeps the W and Rh leads disconnected from each other unless there is an active heating call, in which case the W-Rh FET switch shorts the W and Rh leads together. As a further example, the Y-Rc FET switch keeps the Y and Rc leads disconnected from each other unless there is an active cooling call, in which case the Y-Rc FET switch shorts the Y and Rc leads together. (There is one exception to this basic operation for the particular case of “active power stealing” that is discussed in more detail infra, in which case the FET switch corresponding to the HVAC lead from which power is being stolen is opened up for very brief intervals during an active call involving that lead. Thus, if power-stealing is being performed using the Y lead, then during an active cooling call the Y-Rc FET switch is opened up for very brief intervals from time to time, these brief intervals being short enough such that the Y HVAC relay does not un-trip.)
Advantageously, by virtue of the above-described operation of block 1418, it is automatically the case that for single-transformer systems having only an “R” wire (rather than separate Rc and Rh wires as would be present for two-transformer systems), that “R” wire can be inserted into either of the Rc or Rh terminals, and the Rh-Rc nodes will be automatically shorted to form a single “R” node, as needed for proper operation. In contrast, for dual-transformer systems, the insertion of two separate wires into the respective Rc and Rh terminals will cause the Rh-Rc nodes to remain disconnected to maintain two separate Rc and Rh nodes, as needed for proper operation. The G-Rc FET switch keeps the G and Rc leads disconnected from each other unless there is an active fan call, in which case the G-Rc FET switch shorts the G and Rc leads together (and, advantageously, the proper connection will be achieved regardless of whether the there is a single HVAC transformer or dual HVAC transformers because the Rc and Rh terminals will be automatically shorted or isolated accordingly). The AUX-Rh FET switch keeps the AUX and Rh leads disconnected from each other unless there is an active AUX call, in which case the AUX-Rh FET switch shorts the AUX and Rh leads together (and, advantageously, the proper connection will be achieved regardless of whether the there is a single HVAC transformer or dual HVAC transformers because the Rc and Rh terminals will be automatically shorted or isolated accordingly). For heat pump calls, the O/B-Rc FET switch and Y-Rc FET switch are jointly operated according to the required installation-dependent convention for forward or reverse operation (for cooling or heating, respectively), which convention can advantageously be determined automatically (or semi-automatically using feedback from the user) by the thermostat 1400 as described further in the commonly assigned PCT/US12/30084, supra.
Referring now to the powering circuitry 1410 in
By virtue of the configuration illustrated in
Operation of the powering circuitry 1410 for the case in which the “C” wire is present is now described. Although the powering circuitry 1410 may be referenced as a “power-stealing” circuit in the general sense of the term, the mode of operation for the case in which the “C” wire is present does not constitute “power stealing” per se, because there is no power being “stolen” from a wire that leads to an HVAC call relay coil (or to the electronic equivalent of an HVAC call relay coil for some newer HVAC systems). For the case in which the “C” wire is present, there is no need to worry about accidentally tripping (for inactive power stealing) or untripping (for active power stealing) an HVAC call relay, and therefore relatively large amounts of power can be assumed to be available from the input at nodes 1419/1417. When the 24 VAC input voltage between nodes 1419 and 1417 is rectified by the full-wave bridge rectifier 1420, a DC voltage at node 1423 is present across the bridge output capacitor 1422, and this DC voltage is converted by the buck regulator 1424 to a relatively steady voltage, such as 4.45 volts, at node 1425, which provides an input current IBP to the power-and-battery (PAB) regulation circuit 1428.
The microcontroller 1408 controls the operation of the powering circuitry 1410 at least by virtue of control leads leading between the microcontroller 1408 and the PAB regulation circuit 1428, which for one embodiment can include an LTC4085-3 chip available from Linear Technologies Corporation. The LTC4085-3 is a USB power manager and Li-Ion/Polymer battery charger originally designed for portable battery-powered applications. The PAB regulation circuit 1428 provides the ability for the microcontroller 1408 to specify a maximum value IBP(max) for the input current IBP. The PAB regulation circuit 1428 is configured to keep the input current at or below IBP(max), while also providing a steady output voltage Vcc, such as 4.0 volts, while also providing an output current Icc that is sufficient to satisfy the thermostat electrical power load, while also tending to the charging of the rechargeable battery 1430 as needed when excess power is available, and while also tending to the proper discharging of the rechargeable battery 1430 as needed when additional power (beyond what can be provided at the maximum input current IBP(max)) is needed to satisfy the thermostat electrical power load. If it is assumed for the sake of clarity of explanation that the voltages at the respective input, output, and battery nodes of the PAB regulation circuit 1428 are roughly equal, the functional operation of the PAB regulation circuit 1428 can be summarized by relationship IBP=Icc+IBAT, where it is the function of the PAB regulation circuit 1428 to ensure that IBP remains below IBP(max) at all times, while providing the necessary load current Icc at the required output voltage Vcc even for cases in which Icc is greater than IBP(max). The PAB regulation circuit 1428 is configured to achieve this goal by regulating the value of IBAT to charge the rechargeable battery 1430 (IBAT>0) when such charge is needed and when Icc is less than IBP(max), and by regulating the value of IBAT to discharge the rechargeable battery 1430 (IBAT<0) when Icc is greater than IBP(max).
For one embodiment, for the case in which the “C” wire is present, the value of IBP(max) for the PAB regulation circuit 1428 is set to a relatively high current value, such as 100 mA, by the microcontroller 1408. Assuming a voltage of about 4.45 volts at node 1425, this corresponds to a maximum output power from the buck regulator 1424 of about 445 mW. Advantageously, by virtue of the rechargeable battery-assisted operation described above, the powering circuitry 1410 can provide instantaneous thermostat electrical power load levels higher than 445 mW on an as-needed basis by discharging the rechargeable battery, and then can recharge the rechargeable battery once the instantaneous thermostat electrical power load goes back down. Generally speaking, depending especially on the instantaneous power usage of the large visually pleasing electronic display (when activated by the user coming close or manipulating the user interface), the high-powered microprocessor 1432 (when not in sleep mode), and the Wi-Fi chip (when transmitting), the instantaneous thermostat electrical power load can indeed rise above 445 mW by up to several hundred additional milliwatts. For preferred embodiments in which the rechargeable battery 1430 has a capacity in the several hundreds of milliamp-hours (mAh) at or near the nominal Vcc voltage levels (e.g., 560 mAh at 3.7 volts), supplying this amount of power is generally not problematic, even for extended time periods (even perhaps up to an hour or more), provided only that there are sufficient periods of lower-power usage below 445 mW in which the rechargeable battery 1430 can be recharged. The thermostat 1400 is configured such that this is easily the case, and indeed is designed such that the average power consumption is below a much lower threshold power than this, as discussed further below in the context of “active power stealing.”
Operation of the powering circuitry 1410 for the case in which the “C” wire is not present is now described. For such case, in accordance with the above-described operation of insertion sensing components/switches 1412/1416, it will be the Y-lead that is connected to the node 1419 if a “Y” wire has been inserted, and it will otherwise be the W-lead that is connected to the node 1419 if no “Y” wire has been inserted. Stated differently, it will be the Y-lead from which “power is stolen” if a “Y” wire has been inserted, and it will otherwise be the W-lead from which “power is stolen” if no “Y” wire has been inserted. As used herein, “inactive power stealing” refers to the power stealing that is performed during periods in which there is no active call in place based on the lead from which power is being stolen. Thus, for cases where it is the “Y” lead from which power is stolen, “inactive power stealing” refers to the power stealing that is performed when there is no active cooling call in place. As used herein, “active power stealing” refers to the power stealing that is performed during periods in which there is an active call in place based on the lead from which power is being stolen. Thus, for cases where it is the “Y” lead from which power is stolen, “active power stealing” refers to the power stealing that is performed when there is an active cooling call in place.
Operation of the powering circuitry 1410 for “inactive power stealing” is now described. In the description that follows it will be assumed that the “Y” wire has been inserted and therefore that power is to be stolen from the Y-lead, with it being understood that similar counterpart operation based on the “W” lead applies if no “Y” wire has been inserted and power is to be stolen from the W-lead. During inactive power stealing, power is stolen from between the “Y” wire that appears at node 1419 and the Rc lead that appears at node 1417. As discussed previously, the Rc lead will be automatically shorted to the Rh lead (to form a single “R” lead) for a single-HVAC transformer system, while the Rc lead will be automatically segregated from the Rh lead for a dual-HVAC transformer system. In either case, there will be a 24 VAC HVAC transformer voltage present across nodes 1419/1417 when no cooling call is in place (i.e., when the Y-Rc FET switch is open). For one embodiment, the maximum current IBP(max) is set to a relatively modest value, such as 20 mA, for the case of inactive power stealing. Assuming a voltage of about 4.45 volts at node 1425, this corresponds to a maximum output power from the buck regulator 1424 of about 90 mW. The power level of 90 mW has been found to be a generally “safe” power stealing level for inactive power stealing, where the term “safe” is used to indicate that, at such power level, all or virtually all HVAC cooling call relays that are installed in most residential and commercial HVAC systems will not accidentally trip into an “on” state due to the current following through the cooling call relay coil. During this time period, the PAB regulator 1428 operates to discharge the battery 1430 during any periods of operation in which the instantaneous thermostat electrical power load rises above 90 mW, and to recharge the battery (if needed) when the instantaneous thermostat electrical power load drops below 90 mW. Provided that the rechargeable battery 1430 is selected to have sufficient capacity (such as 560 mAh at 3.7 volts as discussed above), supplying power at above 90 mW (even several hundred milliwatts more) is generally not problematic even for extended time periods (even perhaps up to an hour or more), provided only that there are sufficient periods of lower-power usage below 90 mW in which the rechargeable battery 1430 can be recharged. The thermostat 1400 is configured such that the average power consumption is well below 90 mW, and indeed for some embodiments is even below 10 mW on a long term time average.
According to one embodiment, the powering circuitry 1410 is further monitored and controlled during inactive power stealing by the microcontroller 1408 by virtue of monitoring the voltage VBR across the bridge output capacitor 1422 at node 1423 that leads into the buck regulator 1424. For the embodiment of
Operation of the powering circuitry 1410 for “active power stealing” is now described. In the description that follows it will be assumed that the “Y” wire has been inserted and therefore that power is to be stolen from the Y-lead, with it being understood that similar counterpart operation based on the “W” lead applies if no “Y” wire has been inserted. During an active cooling call, it is necessary for current to be flowing through the HVAC cooling call relay coil sufficient to maintain the HVAC cooling call relay in a “tripped” or ON state at all times during the active cooling call. In the absence of power stealing, this would of course be achieved by keeping the Y-Rc FET switch 1406 in ON state at all times to short the Y and Rc leads together. To achieve active power stealing, the microcontroller 1408 is configured by virtue of circuitry denoted “PS MOD” to turn the Y-Rc FET switch OFF for small periods of time during the active cooling call, wherein the periods of time are small enough such that the cooling call relay does not “un-trip” into an OFF state, but wherein the periods of time are long enough to allow inrush of current into the bridge rectifier 1420 to keep the bridge output capacitor 1422 to a reasonably acceptable operating level. For one embodiment, this is achieved in a closed-loop fashion in which the microcontroller 1408 monitors the voltage VBR at node 1423 and actuates the signal Y-CTL as necessary to keep the bridge output capacitor 1422 charged. By way of example, during active power stealing operation, the microcontroller 1408 will maintain the Y-Rc FET switch in an ON state while monitoring the voltage VBR until it drops below a certain lower threshold, such as 8 volts. At this point in time, the microcontroller 1408 will switch the Y-Rc FET switch into an OFF state and maintain that OFF state while monitoring the voltage VBR, which will rise as an inrush of rectified current charges the bridge capacitor 1422. Then once the voltage VBR rises above a certain upper threshold, such as 10 volts, the microcontroller 1408 will turn the Y-Rc FET switch back into in an ON state, and the process continues throughout the active power stealing cycling. Although the scope of the present teachings is not so limited, the microcontroller 1408 is preferably programmed to keep the maximum current IBP(max) to a relatively modest level, such as 20 mA (corresponding to a maximum “safe” power stealing level of about 90 mW assuming 4.45 volts) throughout the active power stealing cycle. The circuit elements are designed and configured such that the ON-OFF cycling of the Y-Rc FET switch occurs at a rate that is much higher than 60 Hz and generally has no phase relationship with the HVAC power transformer, whereby the specter of problems that might otherwise occur due to zero crossings of the 24 VAC voltage signal are avoided. By way of example and not by way of limitation, for some embodiments the time interval required for charging the bridge output capacitor 1422 from the lower threshold of 8 volts to the upper threshold of 10 volts will be on the order 10 to 100 microseconds, while the time that it takes the bridge output capacitor 1422 to drain back down to the lower threshold of 8 volts will be on the order of 1 to 10 milliseconds. It has been found that, advantageously, at these kinds of rates and durations for the intermittent “OFF” state of the Y-Rc FET switch 1406, there are very few issues brought about by accidental “un-tripping” of the HVAC cooling call relay during active power stealing across a wide population of residential and commercial HVAC installations.
According to one embodiment, it has been found advantageous to introduce a delay period, such as 60-90 seconds, following the instantiation of an active cooling cycle before instantiating the active power stealing process. This delay period has been found useful in allowing many real-world HVAC systems to reach a kind of “quiescent” operating state in which they will be much less likely to accidentally un-trip away from the active cooling cycle due to active power stealing operation of the thermostat 1400. According to another embodiment, it has been found further advantageous to introduce another delay period, such as 60-90 seconds, following the termination of an active cooling cycle before instantiating the inactive power stealing process. This delay period has likewise been found useful in allowing the various HVAC systems to reach a quiescent state in which accidental tripping back into an active cooling cycle is avoided. Preferably, the microcontroller 1408 implements the above-described instantiation delays for both active and inactive power stealing by setting the maximum current IBP(max) to zero for the required delay period. In some embodiments, the operation of the buck regulator circuit 1424 is also shut down for approximately the first 10 seconds of the delay period to help ensure that the amount of current being drawn by the powering circuitry 1410 is very small. Advantageously, the rechargeable-battery-assisted architecture of the powering circuitry 1410 readily accommodates the above-described instantiation delays in that all of the required thermostat electrical power load can be supplied by the rechargeable battery 1430 during each of the delay periods.
While examples and embodiments have been described, they should not serve to limit any aspect of the present invention. Accordingly, various modifications may be made without departing from the spirit and scope of the invention. Indeed, various methods and system for communicating and operating thermostats, HVACSs and other devices have been provided yet the methods and systems are meant to be illustrative and not limiting as to the scope of the overall invention. It is to be appreciated that the term thermostat, as used hereinabove and hereinbelow, can include thermostats having direct control wires to an HVAC system, and can further include thermostats that do not connect directly with the HVAC system, but that sense an ambient temperature at one location in an enclosure and cooperatively communicate by wired or wireless data connections with a separate thermostat unit located elsewhere in the enclosure, wherein the separate thermostat unit does have direct control wires to the HVAC system. Accordingly, the invention is not limited to the above-described embodiments, but instead is defined by the appended claims in light of their full scope of equivalents.
This application is a continuation of U.S. application Ser. No. 14/720,578, filed May 22, 2015. U.S. application Ser. No. 14/720,578 is a continuation of U.S. application Ser. No. 13/466,815, filed May 8, 2012, now U.S. Pat. No. 9,046,898. U.S. application Ser. No. 13/466,815 claims the benefit of 61/627,996, filed Oct. 21, 2011. U.S. application Ser. No. 13/466,815 is also a continuation-in-part of the following commonly-assigned applications: U.S. patent application Ser. No. 13/275,307, filed Oct. 17, 2011, now U.S. Pat. No. 9,098,279; U.S. patent application Ser. No. 13/267,871, filed Oct. 6, 2011, now U.S. Pat. No. 9,261,287; PCT Application No. PCT/US11/61437, filed Nov. 18, 2011; U.S. patent application Ser. No. 13/267,877, filed Oct. 6, 2011, now U.S. Pat. No. 9,026,254; U.S. application Ser. No. 13/034,674, filed Feb. 24, 2011, now U.S. Pat. No. 9,605,858; and U.S. application Ser. No. 13/034,678, filed Feb. 24, 2011, now U.S. Pat. No. 8,752,771. U.S. patent application Ser. No. 13/267,871 claims the benefit of U.S. Patent Application No. 61/429,093, filed Dec. 31, 2010 and U.S. Patent Application No. 61/415,771, filed Nov. 19, 2010. U.S. patent application Ser. No. 13/267,877 claims the benefit of U.S. Patent Application No. 61/429,093 and U.S. Patent Application No. 61/415,771. U.S. patent application Ser. No. 13/034,674 claims the benefit of U.S. Patent Application No. 61/429,093 and U.S. Patent Application No. 61/415,771. U.S. patent application Ser. No. 13/034,678 claims the benefit of U.S. Patent Application No. 61/429,093 and U.S. Patent Application No. 61/415,771. Each of the above-listed applications is hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1639299 | Kinnard | Aug 1927 | A |
| 2101637 | Howlett | Dec 1937 | A |
| 2492774 | Wild | Dec 1949 | A |
| 3025484 | Cunningham | Mar 1962 | A |
| 3640455 | Romanelli | Feb 1972 | A |
| 3948441 | Perkins et al. | Apr 1976 | A |
| 3991357 | Kaminski | Nov 1976 | A |
| 4049973 | Lambert | Sep 1977 | A |
| 4157506 | Spencer | Jun 1979 | A |
| 4177923 | Krump | Dec 1979 | A |
| 4183290 | Kucharczyk | Jan 1980 | A |
| 4223831 | Szarka | Sep 1980 | A |
| 4249696 | Donnelly et al. | Feb 1981 | A |
| 4308991 | Peinetti et al. | Jan 1982 | A |
| 4335847 | Levine | Jun 1982 | A |
| 4408711 | Levine | Oct 1983 | A |
| 4417687 | Grant | Nov 1983 | A |
| 4460125 | Barker et al. | Jul 1984 | A |
| 4506827 | Jamieson et al. | Mar 1985 | A |
| 4528459 | Wiegel | Jul 1985 | A |
| 4615380 | Beckey | Oct 1986 | A |
| 4632303 | Rodittis | Dec 1986 | A |
| 4646964 | Parker et al. | Mar 1987 | A |
| 4656835 | Kidder et al. | Apr 1987 | A |
| 4657179 | Aggers et al. | Apr 1987 | A |
| 4674027 | Beckey | Jun 1987 | A |
| 4685614 | Levine | Aug 1987 | A |
| 4695246 | Beilfuss et al. | Sep 1987 | A |
| 4716957 | Thompson et al. | Jan 1988 | A |
| 4741476 | Russo et al. | May 1988 | A |
| 4742475 | Kaiser et al. | May 1988 | A |
| 4751961 | Levine et al. | Jun 1988 | A |
| 4772876 | Laud | Sep 1988 | A |
| 4798971 | Gravely | Jan 1989 | A |
| 4830095 | Friend | May 1989 | A |
| 4842510 | Grunden et al. | Jun 1989 | A |
| 4847781 | Brown, III et al. | Jul 1989 | A |
| 4872828 | Mierzwinski et al. | Oct 1989 | A |
| 4881686 | Mehta | Nov 1989 | A |
| 4886110 | Jackson | Dec 1989 | A |
| 4897798 | Cler | Jan 1990 | A |
| 4898229 | Brown et al. | Feb 1990 | A |
| 4948040 | Kobayashi et al. | Aug 1990 | A |
| 4948044 | Cacciatore | Aug 1990 | A |
| 4955806 | Grunden et al. | Sep 1990 | A |
| 4971136 | Mathur et al. | Nov 1990 | A |
| 5065813 | Berkeley et al. | Nov 1991 | A |
| 5088645 | Bell | Feb 1992 | A |
| 5107918 | McFarlane et al. | Apr 1992 | A |
| 5127464 | Butler et al. | Jul 1992 | A |
| 5158477 | Testa et al. | Oct 1992 | A |
| 5161606 | Berkeley et al. | Nov 1992 | A |
| 5175439 | Haerer et al. | Dec 1992 | A |
| 5181389 | Hanson et al. | Jan 1993 | A |
| 5211332 | Adams | May 1993 | A |
| 5224648 | Simon et al. | Jul 1993 | A |
| 5226591 | Ratz | Jul 1993 | A |
| 5240178 | Dewolf et al. | Aug 1993 | A |
| 5244146 | Jefferson et al. | Sep 1993 | A |
| 5251813 | Kniepkamp | Oct 1993 | A |
| 5255179 | Zekan et al. | Oct 1993 | A |
| 5260669 | Higgins et al. | Nov 1993 | A |
| 5277363 | Hart | Jan 1994 | A |
| 5318104 | Shah et al. | Jun 1994 | A |
| 5318224 | Darby et al. | Jun 1994 | A |
| 5347982 | Binzer et al. | Sep 1994 | A |
| 5348078 | Dushane et al. | Sep 1994 | A |
| 5352930 | Ratz | Oct 1994 | A |
| 5381950 | Aldridge | Jan 1995 | A |
| 5395042 | Riley et al. | Mar 1995 | A |
| 5422808 | Catanese et al. | Jun 1995 | A |
| 5452762 | Zillner, Jr. | Sep 1995 | A |
| 5456407 | Stalsberg et al. | Oct 1995 | A |
| 5460327 | Hill et al. | Oct 1995 | A |
| 5462225 | Massara et al. | Oct 1995 | A |
| 5467921 | Shreeve et al. | Nov 1995 | A |
| 5476221 | Seymour | Dec 1995 | A |
| 5485953 | Bassett et al. | Jan 1996 | A |
| 5495887 | Kathnelson et al. | Mar 1996 | A |
| 5499196 | Pacheco | Mar 1996 | A |
| 5506569 | Rowlette | Apr 1996 | A |
| 5533668 | Erikson | Jul 1996 | A |
| 5544036 | Brown, Jr. et al. | Aug 1996 | A |
| 5555927 | Shah | Sep 1996 | A |
| 5570837 | Brown et al. | Nov 1996 | A |
| 5595342 | McNair et al. | Jan 1997 | A |
| 5611484 | Uhrich | Mar 1997 | A |
| 5635896 | Tinsley et al. | Jun 1997 | A |
| 5644173 | Elliason et al. | Jul 1997 | A |
| 5646349 | Twigg et al. | Jul 1997 | A |
| 5655709 | Garnett et al. | Aug 1997 | A |
| 5673850 | Uptegraph | Oct 1997 | A |
| 5697552 | McHugh et al. | Dec 1997 | A |
| 5711480 | Zepke et al. | Jan 1998 | A |
| 5736795 | Zuehlke et al. | Apr 1998 | A |
| 5742833 | Dea et al. | Apr 1998 | A |
| 5761083 | Brown, Jr. et al. | Jun 1998 | A |
| 5802467 | Salazar et al. | Sep 1998 | A |
| 5808294 | Neumann | Sep 1998 | A |
| 5816491 | Berkeley et al. | Oct 1998 | A |
| 5839654 | Weber | Nov 1998 | A |
| 5902183 | D'Souza | May 1999 | A |
| 5903139 | Kompelien | May 1999 | A |
| 5909378 | De Milleville | Jun 1999 | A |
| 5918474 | Khanpara et al. | Jul 1999 | A |
| 5926776 | Glorioso et al. | Jul 1999 | A |
| 5931378 | Schramm | Aug 1999 | A |
| 5944098 | Jackson | Aug 1999 | A |
| 5950709 | Krueger et al. | Sep 1999 | A |
| 5957374 | Bias et al. | Sep 1999 | A |
| 5958009 | Friedrich | Sep 1999 | A |
| 5977964 | Williams et al. | Nov 1999 | A |
| 6032867 | Dushane et al. | Mar 2000 | A |
| 6060719 | DiTucci et al. | May 2000 | A |
| 6062482 | Gauthier et al. | May 2000 | A |
| 6066843 | Scheremeta | May 2000 | A |
| 6072784 | Agrawal et al. | Jun 2000 | A |
| 6084518 | Jamieson | Jul 2000 | A |
| 6088688 | Crooks et al. | Jul 2000 | A |
| 6089310 | Toth et al. | Jul 2000 | A |
| 6095427 | Hoium et al. | Aug 2000 | A |
| 6098893 | Berglund et al. | Aug 2000 | A |
| 6102749 | Lynn et al. | Aug 2000 | A |
| 6116512 | Dushane et al. | Sep 2000 | A |
| 6122603 | Budike, Jr. | Sep 2000 | A |
| D435473 | Eckel et al. | Dec 2000 | S |
| 6196468 | Young | Mar 2001 | B1 |
| 6205041 | Baker | Mar 2001 | B1 |
| 6207899 | Gillespie | Mar 2001 | B1 |
| 6213404 | Dushane et al. | Apr 2001 | B1 |
| 6216956 | Ehlers et al. | Apr 2001 | B1 |
| 6222719 | Kadah | Apr 2001 | B1 |
| 6260765 | Natale et al. | Jul 2001 | B1 |
| 6275160 | Ha | Aug 2001 | B1 |
| 6295823 | Odom et al. | Oct 2001 | B1 |
| 6311105 | Budike, Jr. | Oct 2001 | B1 |
| 6315211 | Sartain et al. | Nov 2001 | B1 |
| 6336593 | Bhatnagar | Jan 2002 | B1 |
| 6347747 | Nesbitt | Feb 2002 | B1 |
| 6349883 | Simmons et al. | Feb 2002 | B1 |
| 6356038 | Bishel | Mar 2002 | B2 |
| 6356204 | Guindi et al. | Mar 2002 | B1 |
| 6363422 | Hunter et al. | Mar 2002 | B1 |
| 6370894 | Thompson et al. | Apr 2002 | B1 |
| 6385510 | Hoog et al. | May 2002 | B1 |
| 6415205 | Myron et al. | Jul 2002 | B1 |
| 6437999 | Wittenbreder | Aug 2002 | B1 |
| 6453687 | Sharood et al. | Sep 2002 | B2 |
| 6478233 | Shah | Nov 2002 | B1 |
| 6509838 | Payne et al. | Jan 2003 | B1 |
| 6513723 | Mueller et al. | Feb 2003 | B1 |
| 6519509 | Nierlich et al. | Feb 2003 | B1 |
| 6560977 | Hupfel et al. | May 2003 | B1 |
| 6566768 | Zimmerman et al. | May 2003 | B2 |
| 6574581 | Bohrer et al. | Jun 2003 | B1 |
| 6604023 | Brown et al. | Aug 2003 | B1 |
| 6619055 | Addy | Sep 2003 | B1 |
| 6619555 | Rosen | Sep 2003 | B2 |
| 6622115 | Brown et al. | Sep 2003 | B1 |
| 6622925 | Carner et al. | Sep 2003 | B2 |
| 6623311 | Dehan | Sep 2003 | B1 |
| 6631185 | Fleming, III | Oct 2003 | B1 |
| 6643567 | Kolk et al. | Nov 2003 | B2 |
| 6645066 | Gutta et al. | Nov 2003 | B2 |
| 6657418 | Atherton | Dec 2003 | B2 |
| 6743010 | Bridgeman et al. | Jun 2004 | B2 |
| 6769482 | Wagner et al. | Aug 2004 | B2 |
| 6785630 | Kolk et al. | Aug 2004 | B2 |
| 6789739 | Rosen | Sep 2004 | B2 |
| 6794771 | Orloff | Sep 2004 | B2 |
| 6798341 | Eckel et al. | Sep 2004 | B1 |
| 6804117 | Phillips et al. | Oct 2004 | B2 |
| 6826454 | Sulfstede | Nov 2004 | B2 |
| 6851621 | Wacker et al. | Feb 2005 | B1 |
| 6851967 | Miyoshi et al. | Feb 2005 | B2 |
| 6886754 | Smith et al. | May 2005 | B2 |
| 6888078 | Loeffelholz et al. | May 2005 | B2 |
| 6888441 | Carey | May 2005 | B2 |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6904385 | Budike, Jr. | Jun 2005 | B1 |
| 6909921 | Bilger | Jun 2005 | B1 |
| 6933655 | Morrison et al. | Aug 2005 | B2 |
| 6956463 | Crenella et al. | Oct 2005 | B2 |
| 6975958 | Bohrer et al. | Dec 2005 | B2 |
| 6983889 | Alles | Jan 2006 | B2 |
| 6990821 | Singh et al. | Jan 2006 | B2 |
| 6997390 | Alles | Feb 2006 | B2 |
| 7024336 | Salsbury et al. | Apr 2006 | B2 |
| 7028203 | Nakai | Apr 2006 | B2 |
| 7055759 | Wacker et al. | Jun 2006 | B2 |
| 7083109 | Pouchak | Aug 2006 | B2 |
| 7130719 | Ehlers et al. | Oct 2006 | B2 |
| 7135965 | Chapman, Jr. et al. | Nov 2006 | B2 |
| 7149727 | Nicholls et al. | Dec 2006 | B1 |
| 7149729 | Kaasten et al. | Dec 2006 | B2 |
| 7156316 | Kates | Jan 2007 | B2 |
| 7156318 | Rosen | Jan 2007 | B1 |
| 7167079 | Smyth et al. | Jan 2007 | B2 |
| 7168627 | Kates | Jan 2007 | B2 |
| 7174239 | Butler et al. | Feb 2007 | B2 |
| 7181317 | Amundson et al. | Feb 2007 | B2 |
| 7188482 | Sadegh et al. | Mar 2007 | B2 |
| 7200467 | Schanin et al. | Apr 2007 | B2 |
| 7209870 | Simmons et al. | Apr 2007 | B2 |
| 7274975 | Miller | Sep 2007 | B2 |
| 7289887 | Rodgers | Oct 2007 | B2 |
| 7331852 | Ezell et al. | Feb 2008 | B2 |
| 7333880 | Brewster et al. | Feb 2008 | B2 |
| 7346467 | Bohrer et al. | Mar 2008 | B2 |
| 7360370 | Shah et al. | Apr 2008 | B2 |
| 7379791 | Tamarkin et al. | May 2008 | B2 |
| RE40437 | Rosen | Jul 2008 | E |
| 7434742 | Mueller et al. | Oct 2008 | B2 |
| 7460690 | Cohen et al. | Dec 2008 | B2 |
| 7469550 | Chapman, Jr. et al. | Dec 2008 | B2 |
| 7476988 | Mulhouse et al. | Jan 2009 | B2 |
| 7510126 | Rossi et al. | Mar 2009 | B2 |
| 7537171 | Mueller et al. | May 2009 | B2 |
| 7555364 | Poth et al. | Jun 2009 | B2 |
| 7558648 | Hoglund et al. | Jul 2009 | B2 |
| 7562536 | Harrod et al. | Jul 2009 | B2 |
| 7566263 | Snyder | Jul 2009 | B2 |
| 7571865 | Nicodem et al. | Aug 2009 | B2 |
| 7605714 | Thompson et al. | Oct 2009 | B2 |
| 7634504 | Amundson | Dec 2009 | B2 |
| 7644869 | Hoglund et al. | Jan 2010 | B2 |
| 7648077 | Rossi et al. | Jan 2010 | B2 |
| 7673809 | Juntunen | Mar 2010 | B2 |
| 7702424 | Cannon et al. | Apr 2010 | B2 |
| 7703694 | Mueller et al. | Apr 2010 | B2 |
| D614976 | Skafdrup et al. | May 2010 | S |
| 7720576 | Warren et al. | May 2010 | B2 |
| 7735118 | Brok et al. | Jun 2010 | B2 |
| 7746242 | Schwendinger et al. | Jun 2010 | B2 |
| 7748640 | Roher et al. | Jul 2010 | B2 |
| 7755220 | Sorg et al. | Jul 2010 | B2 |
| 7765419 | Fuccello | Jul 2010 | B2 |
| 7775452 | Shah et al. | Aug 2010 | B2 |
| 7784704 | Harter | Aug 2010 | B2 |
| 7802618 | Simon et al. | Sep 2010 | B2 |
| 7809472 | Silva et al. | Oct 2010 | B1 |
| 7821218 | Butler et al. | Oct 2010 | B2 |
| 7832465 | Zou et al. | Nov 2010 | B2 |
| 7837128 | Helt et al. | Nov 2010 | B2 |
| 7841542 | Rosen | Nov 2010 | B1 |
| 7844764 | Williams | Nov 2010 | B2 |
| 7845576 | Siddaramanna et al. | Dec 2010 | B2 |
| 7847681 | Singhal et al. | Dec 2010 | B2 |
| 7848900 | Steinberg et al. | Dec 2010 | B2 |
| 7849698 | Harrod et al. | Dec 2010 | B2 |
| 7854389 | Ahmed | Dec 2010 | B2 |
| 7900849 | Barton et al. | Mar 2011 | B2 |
| 7904209 | Podgorny et al. | Mar 2011 | B2 |
| 7904830 | Hoglund et al. | Mar 2011 | B2 |
| 7908116 | Steinberg et al. | Mar 2011 | B2 |
| 7908117 | Steinberg et al. | Mar 2011 | B2 |
| 7921309 | Isbister et al. | Apr 2011 | B1 |
| 7933635 | Oh et al. | Apr 2011 | B2 |
| 7933689 | Warren et al. | Apr 2011 | B2 |
| 7967212 | Euler et al. | Jun 2011 | B1 |
| 7975292 | Corella | Jul 2011 | B2 |
| 8001400 | Fadell | Aug 2011 | B2 |
| 8010237 | Cheung et al. | Aug 2011 | B2 |
| 8019567 | Steinberg et al. | Sep 2011 | B2 |
| 8023432 | Herzog | Sep 2011 | B2 |
| 8024593 | Ito et al. | Sep 2011 | B2 |
| 8037022 | Rahman et al. | Oct 2011 | B2 |
| 8067912 | Mullin | Nov 2011 | B2 |
| D651529 | Mongell et al. | Jan 2012 | S |
| 8090477 | Steinberg | Jan 2012 | B1 |
| 8091375 | Crawford | Jan 2012 | B2 |
| 8131207 | Hwang et al. | Mar 2012 | B2 |
| 8131497 | Steinberg et al. | Mar 2012 | B2 |
| 8131506 | Steinberg et al. | Mar 2012 | B2 |
| 8161302 | Woo | Apr 2012 | B2 |
| D660732 | Bould et al. | May 2012 | S |
| 8174381 | Imes et al. | May 2012 | B2 |
| 8180492 | Steinberg | May 2012 | B2 |
| 8195313 | Fadell et al. | Jun 2012 | B1 |
| 8219249 | Harrod et al. | Jul 2012 | B2 |
| 8234694 | Youn et al. | Jul 2012 | B2 |
| 8249731 | Tran et al. | Aug 2012 | B2 |
| 8255090 | Frader-Thompson et al. | Aug 2012 | B2 |
| 8265798 | Imes | Sep 2012 | B2 |
| 8280536 | Fadell et al. | Oct 2012 | B1 |
| 8285200 | Backholm et al. | Oct 2012 | B2 |
| 8350694 | Trundle et al. | Jan 2013 | B1 |
| 8352769 | Ghose et al. | Jan 2013 | B1 |
| D677180 | Plitkins et al. | Mar 2013 | S |
| 8392561 | Dyer et al. | Mar 2013 | B1 |
| 8415829 | Di Cristofaro | Apr 2013 | B2 |
| 8442695 | Imes et al. | May 2013 | B2 |
| 8442752 | Wijaya et al. | May 2013 | B2 |
| D687043 | Matas et al. | Jul 2013 | S |
| D687044 | Ruff | Jul 2013 | S |
| D687045 | Plitkins et al. | Jul 2013 | S |
| D687046 | Plitkins et al. | Jul 2013 | S |
| D687047 | Hales, IV et al. | Jul 2013 | S |
| D687050 | Matas et al. | Jul 2013 | S |
| D687056 | Matas et al. | Jul 2013 | S |
| D687057 | Plitkins | Jul 2013 | S |
| D687058 | Corcoran et al. | Jul 2013 | S |
| D687059 | Bruck et al. | Jul 2013 | S |
| 8478447 | Fadell et al. | Jul 2013 | B2 |
| D687459 | Sloo et al. | Aug 2013 | S |
| D687851 | Sloo et al. | Aug 2013 | S |
| 8510255 | Fadell et al. | Aug 2013 | B2 |
| D690322 | Matas et al. | Sep 2013 | S |
| 8532007 | Araki | Sep 2013 | B2 |
| D691629 | Matas et al. | Oct 2013 | S |
| 8544285 | Stefanski et al. | Oct 2013 | B2 |
| D696677 | Corcoran et al. | Dec 2013 | S |
| 8606374 | Fadell et al. | Dec 2013 | B2 |
| D697526 | Bruck et al. | Jan 2014 | S |
| D697930 | Crabtree et al. | Jan 2014 | S |
| 8627127 | Mucignat et al. | Jan 2014 | B2 |
| 8630740 | Matsuoka et al. | Jan 2014 | B2 |
| D701515 | Matas et al. | Mar 2014 | S |
| D701869 | Matas et al. | Apr 2014 | S |
| 8708242 | Conner et al. | Apr 2014 | B2 |
| 8727611 | Huppi et al. | May 2014 | B2 |
| 8740101 | Leen et al. | Jun 2014 | B2 |
| 8752771 | Warren et al. | Jun 2014 | B2 |
| 8757507 | Fadell et al. | Jun 2014 | B2 |
| 8788103 | Warren et al. | Jul 2014 | B2 |
| D711916 | Matas | Aug 2014 | S |
| 8811377 | Weston | Aug 2014 | B1 |
| 8843239 | Mighdoll et al. | Sep 2014 | B2 |
| 8918219 | Sloo et al. | Dec 2014 | B2 |
| 8950686 | Matsuoka et al. | Feb 2015 | B2 |
| 8972065 | Matsuoka et al. | Mar 2015 | B2 |
| 9026254 | Warren et al. | May 2015 | B2 |
| 9046898 | Mucignat et al. | Jun 2015 | B2 |
| 9092040 | Fadell et al. | Jul 2015 | B2 |
| 9098096 | Matsuoka | Aug 2015 | B2 |
| 9098279 | Mucignat et al. | Aug 2015 | B2 |
| 9104211 | Fadell et al. | Aug 2015 | B2 |
| 9223323 | Matas et al. | Dec 2015 | B2 |
| 9261287 | Warren et al. | Feb 2016 | B2 |
| 9453655 | Bruck et al. | Sep 2016 | B2 |
| 9489062 | Corcoran et al. | Nov 2016 | B2 |
| 9494332 | Filson et al. | Nov 2016 | B2 |
| 9605858 | Warren et al. | Mar 2017 | B2 |
| 9851729 | Mucignat et al. | Dec 2017 | B2 |
| 10241527 | Fadell et al. | Mar 2019 | B2 |
| 20020004911 | Nakai | Jan 2002 | A1 |
| 20020005707 | Kerai et al. | Jan 2002 | A1 |
| 20020074865 | Zimmerman et al. | Jun 2002 | A1 |
| 20020075145 | Hardman et al. | Jun 2002 | A1 |
| 20020091784 | Baker et al. | Jul 2002 | A1 |
| 20020181251 | Kompelien | Dec 2002 | A1 |
| 20020198629 | Ellis | Dec 2002 | A1 |
| 20030037555 | Street et al. | Feb 2003 | A1 |
| 20030064335 | Canon | Apr 2003 | A1 |
| 20030069648 | Douglas et al. | Apr 2003 | A1 |
| 20030084112 | Curray et al. | May 2003 | A1 |
| 20030090243 | Atherton | May 2003 | A1 |
| 20030124979 | Tanada | Jul 2003 | A1 |
| 20030135772 | Haulk et al. | Jul 2003 | A1 |
| 20030137277 | Mori et al. | Jul 2003 | A1 |
| 20030151513 | Herrmann et al. | Aug 2003 | A1 |
| 20030231001 | Bruning | Dec 2003 | A1 |
| 20040012477 | Engler et al. | Jan 2004 | A1 |
| 20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
| 20040058637 | Laiti | Mar 2004 | A1 |
| 20040090329 | Hitt | May 2004 | A1 |
| 20040095237 | Chen et al. | May 2004 | A1 |
| 20040114399 | Lincoln et al. | Jun 2004 | A1 |
| 20040117311 | Agarwal et al. | Jun 2004 | A1 |
| 20040120084 | Readio et al. | Jun 2004 | A1 |
| 20040130454 | Barton | Jul 2004 | A1 |
| 20040164238 | Xu et al. | Aug 2004 | A1 |
| 20040193324 | Hoog et al. | Sep 2004 | A1 |
| 20040209209 | Chodacki et al. | Oct 2004 | A1 |
| 20040238651 | Juntunen et al. | Dec 2004 | A1 |
| 20040245349 | Smith | Dec 2004 | A1 |
| 20040245352 | Smith | Dec 2004 | A1 |
| 20040249479 | Shorrock | Dec 2004 | A1 |
| 20040256472 | DeLuca | Dec 2004 | A1 |
| 20050035877 | Kim | Feb 2005 | A1 |
| 20050040250 | Wruck | Feb 2005 | A1 |
| 20050043907 | Eckel et al. | Feb 2005 | A1 |
| 20050047382 | Park et al. | Mar 2005 | A1 |
| 20050053063 | Madhavan | Mar 2005 | A1 |
| 20050055432 | Rodgers | Mar 2005 | A1 |
| 20050080493 | Arntson | Apr 2005 | A1 |
| 20050090915 | Geiwitz | Apr 2005 | A1 |
| 20050097375 | Nakai | May 2005 | A1 |
| 20050119793 | Amundson et al. | Jun 2005 | A1 |
| 20050128067 | Zakrewski | Jun 2005 | A1 |
| 20050131553 | Yoon et al. | Jun 2005 | A1 |
| 20050145705 | Shah et al. | Jul 2005 | A1 |
| 20050150968 | Shearer | Jul 2005 | A1 |
| 20050159846 | Van Ostrand et al. | Jul 2005 | A1 |
| 20050159847 | Shah et al. | Jul 2005 | A1 |
| 20050187867 | Sokolic et al. | Aug 2005 | A1 |
| 20050189429 | Breeden | Sep 2005 | A1 |
| 20050192915 | Ahmed et al. | Sep 2005 | A1 |
| 20050194455 | Alles | Sep 2005 | A1 |
| 20050194456 | Tessier et al. | Sep 2005 | A1 |
| 20050195757 | Kidder et al. | Sep 2005 | A1 |
| 20050270151 | Winick | Dec 2005 | A1 |
| 20050280421 | Yomoda et al. | Dec 2005 | A1 |
| 20060009863 | Lingemann | Jan 2006 | A1 |
| 20060017581 | Schwendinger et al. | Jan 2006 | A1 |
| 20060077845 | Nakai | Apr 2006 | A1 |
| 20060090066 | Maze et al. | Apr 2006 | A1 |
| 20060102731 | Mueller et al. | May 2006 | A1 |
| 20060102732 | Garrett et al. | May 2006 | A1 |
| 20060105697 | Aronstam et al. | May 2006 | A1 |
| 20060111796 | Van Heteren | May 2006 | A1 |
| 20060124759 | Rossi et al. | Jun 2006 | A1 |
| 20060147003 | Archacki et al. | Jul 2006 | A1 |
| 20060149395 | Archacki et al. | Jul 2006 | A1 |
| 20060161275 | Plankl et al. | Jul 2006 | A1 |
| 20060164257 | Giubbini | Jul 2006 | A1 |
| 20060186214 | Simon et al. | Aug 2006 | A1 |
| 20060196953 | Simon et al. | Sep 2006 | A1 |
| 20060208099 | Chapman et al. | Sep 2006 | A1 |
| 20060219799 | Schultz et al. | Oct 2006 | A1 |
| 20060236143 | Kidoguchi | Oct 2006 | A1 |
| 20060251086 | Ha et al. | Nov 2006 | A1 |
| 20070025390 | Jain | Feb 2007 | A1 |
| 20070043478 | Ehlers et al. | Feb 2007 | A1 |
| 20070045431 | Chapman, Jr. et al. | Mar 2007 | A1 |
| 20070045432 | Juntunen | Mar 2007 | A1 |
| 20070045433 | Chapman et al. | Mar 2007 | A1 |
| 20070045441 | Ashworth et al. | Mar 2007 | A1 |
| 20070095082 | Garrett et al. | May 2007 | A1 |
| 20070103824 | Patterson et al. | May 2007 | A1 |
| 20070105252 | Lee et al. | May 2007 | A1 |
| 20070114295 | Jenkins | May 2007 | A1 |
| 20070114848 | Mulhouse et al. | May 2007 | A1 |
| 20070115135 | Mulhouse et al. | May 2007 | A1 |
| 20070115902 | Shamoon et al. | May 2007 | A1 |
| 20070131787 | Rossi et al. | Jun 2007 | A1 |
| 20070157639 | Harrod | Jul 2007 | A1 |
| 20070158442 | Chapman et al. | Jul 2007 | A1 |
| 20070183475 | Hutcherson | Aug 2007 | A1 |
| 20070183478 | Becker et al. | Aug 2007 | A1 |
| 20070183493 | Kimpe | Aug 2007 | A1 |
| 20070199076 | Rensin et al. | Aug 2007 | A1 |
| 20070202837 | Araki et al. | Aug 2007 | A1 |
| 20070205297 | Finkam et al. | Sep 2007 | A1 |
| 20070208461 | Chase | Sep 2007 | A1 |
| 20070221741 | Wagner et al. | Sep 2007 | A1 |
| 20070227862 | Yim et al. | Oct 2007 | A1 |
| 20070228183 | Kennedy et al. | Oct 2007 | A1 |
| 20070241203 | Wagner et al. | Oct 2007 | A1 |
| 20070266575 | Nash | Nov 2007 | A1 |
| 20070272527 | Mattlar et al. | Nov 2007 | A1 |
| 20070296280 | Sorg et al. | Dec 2007 | A1 |
| 20080006709 | Ashworth et al. | Jan 2008 | A1 |
| 20080011736 | Lenhart et al. | Jan 2008 | A1 |
| 20080015740 | Osann | Jan 2008 | A1 |
| 20080015742 | Kulyk et al. | Jan 2008 | A1 |
| 20080048046 | Wagner et al. | Feb 2008 | A1 |
| 20080054082 | Evans et al. | Mar 2008 | A1 |
| 20080054084 | Olson | Mar 2008 | A1 |
| 20080094010 | Black | Apr 2008 | A1 |
| 20080099568 | Nicodem et al. | May 2008 | A1 |
| 20080112348 | Park et al. | May 2008 | A1 |
| 20080120420 | Sima et al. | May 2008 | A1 |
| 20080123554 | Ku | May 2008 | A1 |
| 20080128523 | Hoglund et al. | Jun 2008 | A1 |
| 20080133956 | Fadell | Jun 2008 | A1 |
| 20080142344 | Hickam | Jun 2008 | A1 |
| 20080147242 | Roher et al. | Jun 2008 | A1 |
| 20080151458 | Beland et al. | Jun 2008 | A1 |
| 20080161977 | Takach et al. | Jul 2008 | A1 |
| 20080164984 | Sheffer | Jul 2008 | A1 |
| 20080179412 | Rhodes | Jul 2008 | A1 |
| 20080183335 | Poth et al. | Jul 2008 | A1 |
| 20080185450 | Kwon et al. | Aug 2008 | A1 |
| 20080191045 | Harter | Aug 2008 | A1 |
| 20080192389 | Muench et al. | Aug 2008 | A1 |
| 20080192666 | Koskan et al. | Aug 2008 | A1 |
| 20080202135 | Francis | Aug 2008 | A1 |
| 20080221737 | Josephson et al. | Sep 2008 | A1 |
| 20080222736 | Boodaei et al. | Sep 2008 | A1 |
| 20080225865 | Herzog | Sep 2008 | A1 |
| 20080238660 | Dayton et al. | Oct 2008 | A1 |
| 20080260416 | Nosaki | Oct 2008 | A1 |
| 20080273754 | Hick et al. | Nov 2008 | A1 |
| 20080311961 | Cotevino et al. | Dec 2008 | A1 |
| 20080313481 | Paljug | Dec 2008 | A1 |
| 20080317292 | Baker et al. | Dec 2008 | A1 |
| 20090012959 | Ylivainio et al. | Jan 2009 | A1 |
| 20090045263 | Mueller et al. | Feb 2009 | A1 |
| 20090057425 | Sullivan et al. | Mar 2009 | A1 |
| 20090057427 | Geadelmann et al. | Mar 2009 | A1 |
| 20090062970 | Forbes, Jr. et al. | Mar 2009 | A1 |
| 20090065595 | Kates | Mar 2009 | A1 |
| 20090070412 | D'Angelo et al. | Mar 2009 | A1 |
| 20090099697 | Li et al. | Apr 2009 | A1 |
| 20090099699 | Steinberg et al. | Apr 2009 | A1 |
| 20090125151 | Steinberg et al. | May 2009 | A1 |
| 20090127932 | Warren et al. | May 2009 | A1 |
| 20090135751 | Hodges et al. | May 2009 | A1 |
| 20090140056 | Leen | Jun 2009 | A1 |
| 20090140057 | Leen | Jun 2009 | A1 |
| 20090140060 | Stoner et al. | Jun 2009 | A1 |
| 20090140064 | Schultz et al. | Jun 2009 | A1 |
| 20090140065 | Juntunen et al. | Jun 2009 | A1 |
| 20090143879 | Amundson et al. | Jun 2009 | A1 |
| 20090143880 | Amundson et al. | Jun 2009 | A1 |
| 20090164823 | Aaltonen et al. | Jun 2009 | A1 |
| 20090171862 | Harrod et al. | Jul 2009 | A1 |
| 20090180415 | Park et al. | Jul 2009 | A1 |
| 20090192894 | Dikeman | Jul 2009 | A1 |
| 20090194601 | Flohr | Aug 2009 | A1 |
| 20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
| 20090228724 | Chinen et al. | Sep 2009 | A1 |
| 20090236433 | Mueller et al. | Sep 2009 | A1 |
| 20090243842 | Mitchell et al. | Oct 2009 | A1 |
| 20090252032 | Jiang | Oct 2009 | A1 |
| 20090254225 | Boucher et al. | Oct 2009 | A1 |
| 20090259713 | Blumrich et al. | Oct 2009 | A1 |
| 20090261174 | Butler et al. | Oct 2009 | A1 |
| 20090297901 | Kilian et al. | Dec 2009 | A1 |
| 20090302996 | Rhee et al. | Dec 2009 | A1 |
| 20090307036 | Archer et al. | Dec 2009 | A1 |
| 20090312968 | Phillips et al. | Dec 2009 | A1 |
| 20090319551 | Jung | Dec 2009 | A1 |
| 20090327354 | Resnick et al. | Dec 2009 | A1 |
| 20100000239 | Lifson et al. | Jan 2010 | A1 |
| 20100006660 | Leen et al. | Jan 2010 | A1 |
| 20100012737 | Kates | Jan 2010 | A1 |
| 20100019051 | Rosen | Jan 2010 | A1 |
| 20100025483 | Hoeynck et al. | Feb 2010 | A1 |
| 20100026379 | Simard et al. | Feb 2010 | A1 |
| 20100027426 | Nair | Feb 2010 | A1 |
| 20100033424 | Kabasawa et al. | Feb 2010 | A1 |
| 20100038440 | Ersavas | Feb 2010 | A1 |
| 20100039971 | Lor et al. | Feb 2010 | A1 |
| 20100050004 | Hamilton, II et al. | Feb 2010 | A1 |
| 20100058450 | Fein et al. | Mar 2010 | A1 |
| 20100070084 | Steinberg et al. | Mar 2010 | A1 |
| 20100070086 | Harrod et al. | Mar 2010 | A1 |
| 20100070089 | Harrod et al. | Mar 2010 | A1 |
| 20100070099 | Watson et al. | Mar 2010 | A1 |
| 20100070234 | Steinberg et al. | Mar 2010 | A1 |
| 20100076605 | Harrod et al. | Mar 2010 | A1 |
| 20100084482 | Kennedy et al. | Apr 2010 | A1 |
| 20100084918 | Fells et al. | Apr 2010 | A1 |
| 20100085969 | Aoki | Apr 2010 | A1 |
| 20100106305 | Pavlak et al. | Apr 2010 | A1 |
| 20100106322 | Grohman | Apr 2010 | A1 |
| 20100114382 | Ha et al. | May 2010 | A1 |
| 20100127881 | Schechter | May 2010 | A1 |
| 20100128719 | Araki | May 2010 | A1 |
| 20100131112 | Amundson et al. | May 2010 | A1 |
| 20100138926 | Kashchenko et al. | Jun 2010 | A1 |
| 20100141406 | Jo | Jun 2010 | A1 |
| 20100163633 | Barrett et al. | Jul 2010 | A1 |
| 20100163635 | Ye | Jul 2010 | A1 |
| 20100167783 | Alameh et al. | Jul 2010 | A1 |
| 20100168924 | Tessier et al. | Jul 2010 | A1 |
| 20100174808 | Dabagh et al. | Jul 2010 | A1 |
| 20100179704 | Ozog | Jul 2010 | A1 |
| 20100182743 | Roher | Jul 2010 | A1 |
| 20100191387 | Warren et al. | Jul 2010 | A1 |
| 20100193592 | Simon et al. | Aug 2010 | A1 |
| 20100198425 | Donovan | Aug 2010 | A1 |
| 20100198547 | Mulligan | Aug 2010 | A1 |
| 20100199086 | Kuang et al. | Aug 2010 | A1 |
| 20100211224 | Keeling et al. | Aug 2010 | A1 |
| 20100225452 | Murdoch | Sep 2010 | A1 |
| 20100250009 | Lifson et al. | Sep 2010 | A1 |
| 20100261465 | Rhoads et al. | Oct 2010 | A1 |
| 20100262298 | Johnson et al. | Oct 2010 | A1 |
| 20100262299 | Cheung et al. | Oct 2010 | A1 |
| 20100273610 | Johnson | Oct 2010 | A1 |
| 20100280667 | Steinberg | Nov 2010 | A1 |
| 20100282857 | Steinberg | Nov 2010 | A1 |
| 20100289643 | Trundle et al. | Nov 2010 | A1 |
| 20100298985 | Hess et al. | Nov 2010 | A1 |
| 20100305771 | Rodgers | Dec 2010 | A1 |
| 20100308119 | Steinberg et al. | Dec 2010 | A1 |
| 20100318227 | Steinberg et al. | Dec 2010 | A1 |
| 20110001812 | Kang et al. | Jan 2011 | A1 |
| 20110006887 | Shaull et al. | Jan 2011 | A1 |
| 20110015797 | Gilstrap | Jan 2011 | A1 |
| 20110015798 | Golden et al. | Jan 2011 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110022242 | Bukhin et al. | Jan 2011 | A1 |
| 20110025257 | Weng | Feb 2011 | A1 |
| 20110029488 | Fuerst et al. | Feb 2011 | A1 |
| 20110046792 | Imes et al. | Feb 2011 | A1 |
| 20110046805 | Bedros et al. | Feb 2011 | A1 |
| 20110046806 | Nagel et al. | Feb 2011 | A1 |
| 20110054699 | Imes et al. | Mar 2011 | A1 |
| 20110054710 | Imes et al. | Mar 2011 | A1 |
| 20110055280 | Fan | Mar 2011 | A1 |
| 20110077758 | Tran et al. | Mar 2011 | A1 |
| 20110077896 | Steinberg et al. | Mar 2011 | A1 |
| 20110078675 | Van Camp et al. | Mar 2011 | A1 |
| 20110106328 | Zhou et al. | May 2011 | A1 |
| 20110119747 | Lambiase | May 2011 | A1 |
| 20110137467 | Leen et al. | Jun 2011 | A1 |
| 20110151837 | Winbush, III | Jun 2011 | A1 |
| 20110152024 | Kuehl | Jun 2011 | A1 |
| 20110160913 | Parker et al. | Jun 2011 | A1 |
| 20110160918 | McMasters et al. | Jun 2011 | A1 |
| 20110166712 | Kramer et al. | Jul 2011 | A1 |
| 20110166828 | Steinberg et al. | Jul 2011 | A1 |
| 20110185895 | Freen | Aug 2011 | A1 |
| 20110202730 | Sonoda et al. | Aug 2011 | A1 |
| 20110241624 | Park et al. | Oct 2011 | A1 |
| 20110253796 | Posa et al. | Oct 2011 | A1 |
| 20110257795 | Narayanamurthy et al. | Oct 2011 | A1 |
| 20110267974 | Kozaki et al. | Nov 2011 | A1 |
| 20110282937 | Deshpande et al. | Nov 2011 | A1 |
| 20110290893 | Steinberg | Dec 2011 | A1 |
| 20110307103 | Cheung et al. | Dec 2011 | A1 |
| 20110307112 | Barrilleaux | Dec 2011 | A1 |
| 20120008581 | Kojima | Jan 2012 | A1 |
| 20120017611 | Coffel et al. | Jan 2012 | A1 |
| 20120024969 | Kates | Feb 2012 | A1 |
| 20120031984 | Feldmeier et al. | Feb 2012 | A1 |
| 20120053745 | Ng | Mar 2012 | A1 |
| 20120065935 | Steinberg et al. | Mar 2012 | A1 |
| 20120066168 | Fadell et al. | Mar 2012 | A1 |
| 20120085831 | Kopp | Apr 2012 | A1 |
| 20120086562 | Steinberg | Apr 2012 | A1 |
| 20120089523 | Hurri et al. | Apr 2012 | A1 |
| 20120101637 | Imes et al. | Apr 2012 | A1 |
| 20120126019 | Warren et al. | May 2012 | A1 |
| 20120126020 | Filson et al. | May 2012 | A1 |
| 20120126021 | Warren et al. | May 2012 | A1 |
| 20120128025 | Huppi et al. | May 2012 | A1 |
| 20120130546 | Matas et al. | May 2012 | A1 |
| 20120130547 | Fadell et al. | May 2012 | A1 |
| 20120130679 | Fadell et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120158350 | Steinberg et al. | Jun 2012 | A1 |
| 20120179300 | Warren et al. | Jul 2012 | A1 |
| 20120186774 | Matsuoka et al. | Jul 2012 | A1 |
| 20120188928 | Wang et al. | Jul 2012 | A1 |
| 20120191257 | Corcoran et al. | Jul 2012 | A1 |
| 20120199558 | Faulkner | Aug 2012 | A1 |
| 20120199660 | Warren et al. | Aug 2012 | A1 |
| 20120203379 | Sloo et al. | Aug 2012 | A1 |
| 20120221151 | Steinberg | Aug 2012 | A1 |
| 20120229521 | Hales, IV et al. | Sep 2012 | A1 |
| 20120232969 | Fadell et al. | Sep 2012 | A1 |
| 20120233478 | Mucignat et al. | Sep 2012 | A1 |
| 20120239221 | Mighdoll et al. | Sep 2012 | A1 |
| 20120248210 | Warren et al. | Oct 2012 | A1 |
| 20120248211 | Warren et al. | Oct 2012 | A1 |
| 20120252430 | Imes et al. | Oct 2012 | A1 |
| 20120258776 | Lord et al. | Oct 2012 | A1 |
| 20120267089 | Mucignat et al. | Oct 2012 | A1 |
| 20120273580 | Warren et al. | Nov 2012 | A1 |
| 20120325919 | Warren et al. | Dec 2012 | A1 |
| 20130007484 | Gobriel et al. | Jan 2013 | A1 |
| 20130067059 | Gatta et al. | Mar 2013 | A1 |
| 20130073506 | Camp et al. | Mar 2013 | A1 |
| 20130087629 | Stefanski et al. | Apr 2013 | A1 |
| 20130091303 | Mitra | Apr 2013 | A1 |
| 20130173064 | Fadell et al. | Jul 2013 | A1 |
| 20130221117 | Warren et al. | Aug 2013 | A1 |
| 20130228633 | Toth et al. | Sep 2013 | A1 |
| 20130255297 | Matsuoka et al. | Oct 2013 | A1 |
| 20130313331 | Warren et al. | Nov 2013 | A1 |
| 20140084072 | Conner et al. | Mar 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1187966 | May 1985 | CA |
| 2202008 | Oct 1998 | CA |
| 1656661 | Aug 2005 | CN |
| 101305248 | Nov 2008 | CN |
| 101522447 | Sep 2009 | CN |
| 101849311 | Sep 2010 | CN |
| 207295 | Jan 1987 | EP |
| 447458 | Sep 1991 | EP |
| 196069 | Dec 1991 | EP |
| 0510807 | Oct 1992 | EP |
| 0632234 | Jan 1995 | EP |
| 0660287 | Jun 1995 | EP |
| 0690363 | Jan 1996 | EP |
| 0710804 | May 1996 | EP |
| 0772319 | May 1997 | EP |
| 1148749 | Oct 2001 | EP |
| 1275037 | Feb 2006 | EP |
| 2051157 | Apr 2009 | EP |
| 2302326 | Mar 2011 | EP |
| 2294828 | May 1996 | GB |
| 59106311 | Jun 1984 | JP |
| 01252850 | Oct 1989 | JP |
| H08-265373 | Oct 1996 | JP |
| H09-190394 | Jul 1997 | JP |
| 09298780 | Nov 1997 | JP |
| 10023565 | Jan 1998 | JP |
| H1127316 | Jan 1999 | JP |
| 2000078008 | Mar 2000 | JP |
| 2002010341 | Jan 2002 | JP |
| 2003502913 | Jan 2003 | JP |
| 2004511148 | Apr 2004 | JP |
| 2004246811 | Sep 2004 | JP |
| 2006340223 | Dec 2006 | JP |
| 2007235197 | Sep 2007 | JP |
| 2007267335 | Oct 2007 | JP |
| 2008040680 | Feb 2008 | JP |
| 2008516179 | May 2008 | JP |
| 2008147738 | Jun 2008 | JP |
| 2013540079 | Oct 2013 | JP |
| 20556 | Oct 2001 | SI |
| 274364 | Apr 1996 | TW |
| 316955 | Oct 1997 | TW |
| 362230 | Jun 1999 | TW |
| 532469 | May 2003 | TW |
| 535320 | Jun 2003 | TW |
| 2007009529 | Mar 2007 | TW |
| 201232994 | Aug 2012 | TW |
| 0078008 | Dec 2000 | WO |
| 2005019740 | Mar 2005 | WO |
| 2006041599 | Apr 2006 | WO |
| 2007027554 | Mar 2007 | WO |
| 2008054938 | May 2008 | WO |
| 2009008411 | Jan 2009 | WO |
| 2010033563 | Mar 2010 | WO |
| 2010078459 | Jul 2010 | WO |
| 2010113320 | Oct 2010 | WO |
| 2011149600 | Dec 2011 | WO |
| 2012024534 | Feb 2012 | WO |
| 2012068436 | May 2012 | WO |
| 2012068437 | May 2012 | WO |
| 2012068437 | May 2012 | WO |
| 2012068447 | May 2012 | WO |
| 2012068453 | May 2012 | WO |
| 2012068459 | May 2012 | WO |
| 2012068495 | May 2012 | WO |
| 2012068503 | May 2012 | WO |
| 2012068507 | May 2012 | WO |
| 2012068517 | May 2012 | WO |
| 2012068526 | May 2012 | WO |
| 2012068591 | May 2012 | WO |
| 2012092622 | Jul 2012 | WO |
| 2012092625 | Jul 2012 | WO |
| 2012092627 | Jul 2012 | WO |
| 2013052901 | Apr 2013 | WO |
| 2013052905 | Apr 2013 | WO |
| 2013058820 | Apr 2013 | WO |
| 2013058820 | Apr 2013 | WO |
| Entry |
|---|
| International Preliminary Report on Patentability dated Apr. 17, 2014, for International Patent Application No. PCT/US2012/059111, all pages. |
| International Search Report and Written Opinion dated Jan. 9, 2013 in International Patent Application PCT/US2012/059111, all pages. |
| International Preliminary Report on Patentability dated Apr. 15, 2014 for International Patent Application No. PCT/US2012/059107 filed Oct. 5, 2012, 10 pages. |
| Aprilaire Electronic Thermostats Model 8355 User's Manual, Research Products Corporation, Dec. 2000, 16 pages. |
| Braeburn 5300 Installer Guide, Braeburn Systems, LLC, Dec. 9, 2009, 10 pages. |
| Braeburn Model 5200, Braeburn Systems, LLC, Jul. 20, 2011, 11 pages. |
| Ecobee Smart Si Thermostat Installation Manual, Ecobee, Apr. 3, 2012, 40 pages. |
| Ecobee Smart Si Thermostat User Manual, Ecobee, Apr. 3, 2012, 44 pages. |
| Ecobee Smart Thermostat Installation Manual, Jun. 29, 2011, 20 pages. |
| Ecobee Smart Thermostat User Manual, May 11, 2010, 20 pages. |
| Electric Heat Lock Out on Heat Pumps, Washington State University Extension Energy Program, Apr. 2010, pp. 1-3. |
| Energy Joule, Ambient Devices, retrieved from the Internet: <URL: http://web.archive.org/web/20110723210421/http://www.ambientdevices.com/products/energyjoule.html> [retrieved on Aug. 1, 2012], Jul. 23, 2011, 2 pages. |
| Green, Thermo Heat Tech Cool, Popular Mechanics Electronic Thermostat Guide, Oct. 1985, pp. 155-158. |
| Honeywell CT2700, An Electronic Round Programmable Thermostat—User's Guide, Honeywell, Inc., 1997, 8 pages. |
| Honeywell CT8775AC, The digital Round Non-Programmable Thermostats—Owner's Guide, Honeywell International Inc., 2003, 20 pages. |
| Honeywell T8775 The Digital Round Thermostat, Honeywell, 2003, 2 pages. |
| Honeywell Installation Guide FocusPRO TH6000 Series, Honeywell International, Inc., Jan. 5, 2012, 24 pages. |
| Honeywell Operating Manual FocusPRO TH6000 Series, Honeywell International, Inc., Mar. 25, 2011, 80 pages. |
| Honeywell Prestige IAQ Product Data 2, Honeywell International, Inc., Jan. 12, 2012, 126 pages. |
| Honeywell Prestige THX9321 and TXH9421 Product Data, Honeywell International, Inc., 68-0311, Jan. 2012, 126 pages. |
| Honeywell Prestige THX9321-9421 Operating Manual, Honeywell International, Inc., Jul. 6, 2011, 120 pages. |
| Hunter Internet Thermostat Installation Guide, Hunter Fan Co., Aug. 14, 2012, 8 pages. |
| ICY 3815TT-001 Timer-Thermostat Package Box, ICY BV Product Bar Code No. 8717953007902, 2009, 2 pages. |
| Introducing the New Smart Si Thermostat, Datasheet [online]. Ecobee, Mar. 2012 [retrieved on Feb. 25, 2013]. Retrieved from the Internet: <URL: https://www.ecobee.com/solutions/home/smart-si/>, Mar. 12, 2012, 4 pages. |
| Lennox ComfortSense 5000 Owners Guide, Lennox Industries, Inc., Feb. 2008, 32 pages. |
| Lennox ComfortSense 7000 Owners Guide, Lennox Industries, Inc., May 2009, 15 pages. |
| Lennox iComfort Manual, Lennox Industries, Inc., Dec. 2010, 20 pages. |
| Lux PSPU732T Manual, LUX Products Corporation, Jan. 6, 2009, 48 pages. |
| NetX RP32-WIFI Network Thermostat Consumer Brochure, Network Thermostat, May, 2011, 2 pages. |
| NetX RP32-WIFI Network Thermostat Specification Sheet, Network Thermostat, Feb. 28, 2012, 2 pages. |
| RobertShaw Product Manual 9620, Maple Chase Company, Jun. 12, 2001, 14 pages. |
| RobertShaw Product Manual 9825i2, Maple Chase Company, Jul. 17, 2006, 36 pages. |
| SYSTXCCUIZ01-V Infinity Control Installation Instructions, Carrier Corp, May 31, 2012, 20 pages. |
| T8611G Chronotherm IV Deluxe Programmable Heat Pump Thermostat Product Data, Honeywell International Inc., Oct. 1997, 24 pages. |
| TB-PAC, TB-PHP, Base Series Programmable Thermostats, Carrier Corp, May 14, 2012, 8 pages. |
| The Perfect Climate Comfort Center PC8900A W8900A-C Product Data Sheet, Honeywell International Inc, Apr. 2001, 44 pages. |
| TP-PAC, TP-PHP, TP-NAC, TP-NHP Performance Series AC/HP Thermostat Installation Instructions, Carrier Corp, Sep. 2007, 56 pages. |
| Trane Communicating Thermostats for Fan Coil, Trane, May 2011, 32 pages. |
| Trane Communicating Thermostats for Heat Pump Control, Trane, May 2011, 32 pages. |
| Trane Install XL600 Installation Manual, Trane, Mar. 2006, 16 pages. |
| Trane XL950 Installation Guide, Trane, Mar. 2011, 20 pages. |
| Venstar T2900 Manual, Venstar, Inc., Apr. 2008, 113 pages. |
| Venstar T5800 Manual, Venstar, Inc., Sep. 7, 2011, 63 pages. |
| VisionPRO TH8000 Series Installation Guide, Honeywell International, Inc., Jan. 2012, 12 pages. |
| VisionPRO TH8000 Series Operating Manual, Honeywell International, Inc., Mar. 2011, 96 pages. |
| VisionPRO Wi-Fi Programmable Thermostat, Honeywell International, Inc. Operating Manual, Aug. 2012, 48 pages. |
| White Rodgers (Emerson) Model 1F81-261 Installation and Operating Instructions, White Rodgers, Apr. 15, 2010, 8 pages. |
| White Rodgers (Emerson) Model IF98EZ-1621 Homeowner's User Guide, White Rodgers, Jan. 25, 2012, 28 pages. |
| Akhlaghinia et al., “Occupancy Monitoring in Intelligent Environment through Integrated Wireless Localizing Agents”, IEEE, 2009, 7 pages. |
| Akhlaghinia et al., “Occupant Behaviour Prediction in Ambient Intelligence Computing Environment”, Journal of Uncertain Systems, vol. 2, No. 2, 2008, pp. 85-100. |
| Allen et al., “Real-Time Earthquake Detection and Hazard Assessment by ElarmS Across California”, Geophysical Research Letters, vol. 36, L00B08, 2009, pp. 1-6. |
| Arens et al., Demand Response Electrical Appliance Manager—User Interface Design, Development and Testing, Poster, Demand Response Enabling Technology Development, University of California Berkeley, 2005, 1 page. |
| Arens et al., Demand Response Enabled Thermostat—Control Strategies and Interface, Demand Response Enabling Technology Development Poster, University of California Berkeley, 2004, 1 page. |
| Arens et al., “Demand Response Enabling Technology Development”, Phase I Report: Jun. 2003-Nov. 2005, Jul. 27, P:/DemandRes/UC Papers/DR-Phase1Report-Final DraftApril24-26.doc, University of California Berkeley, pp. 1-108. |
| Arens et al., “New Thermostat Demand Response Enabling Technology”, Poster, University of California Berkeley, Jun. 10, 2004, all pages. |
| Auslander et al., UC Berkeley DR Research Energy Management Group, Power Point Presentation, DR ETD Workshop, State of California Energy Commission, Jun. 11, 2007, pp. 1-35. |
| Bourke, “Server Load Balancing”, O'Reilly & Associates, Inc., Aug. 2001, 182 pages. |
| Bryant, SYSTXBBUIDO1 Evolution Control Installation Instructions, 2004, all pages. |
| Chen et al., Demand Response-Enabled Residential Thermostat Controls, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Mechanical Engineering Dept. and Architecture Dept., University of California Berkeley, 2008, pp. 1-24 through 1-36. |
| Deleeuw, “Ecobee WiFi Enabled Smart Thermostat Part 2: The Features Review”, Retrieved from <URL: http://www.homenetworkenabled.com/content.php?136-ecobee-WiFi-enabled-Smart-Thermostat-Part-2-The-Features-review>, Dec. 2, 2011, 5 pages. |
| Detroitborg, “Nest Learning Thermostat: Unboxing and Review”, [online]. Feb. 2012 [retrieved on Aug. 22, 2013]. Retrieved from the Internet: <URL: http://www.youtube.com/watch?v=KrgcOL4oLzc>, all pages. |
| Gao et al., “The Self-Programming Thermostat: Optimizing Setback Schedules Based on Home Occupancy Patterns”, In Proceedings of the First ACM Workshop on Embedded Sensing Systems for Energy-Efficiency in Buildings, Nov. 3, 2009, 6 pages. |
| Loisos et al., “Buildings End-Use Energy Efficiency: Alternatives to Compressor Cooling”, California Energy Commission, Public Interest Energy Research, Jan. 2000, 80 pages. |
| Lu et al., “The Smart Thermostat: Using Occupancy Sensors to Save Energy in Homes”, In Proceedings of the 8th ACM Conference on Embedded Networked Sensor Systems, Nov. 3-5, 2010, pp. 211-224. |
| Mozer, “The Neural Network House: An Environmental that Adapts to it's Inhabitants”, AAAI Technical Report SS-98-02, 1998, pp. 110-114. |
| International Patent Application No. PCT/US2012/059107, International Search Report & Written Opinion, dated Jan. 3, 2013, 10 pages. |
| Ros et al., “Multi-Sensor Human Tracking with the Bayesian Occupancy Filter”, IEEE, 2009, 8 pages. |
| White et al., “A Conceptual Model for Simulation Load Balancing”, Proc. 1998 Spring Simulation Interoperability Workshop, 1998, 7 pages. |
| Wong et al., “Maximum Likelihood Estimation of ARMA Model with Error Processes for Replicated Observations”, National University of Singapore, Department of Economics, Working Paper No. 0217, 2002, 19 pages. |
| Chatzigiannakis et al., “Priority Based Adaptive Coordination of Wireless Sensors and Actors” Q2SWinet '06, Oct. 2, 2006, pp. 37-44. |
| Stigge Jr. B. J. (2001). Informed Home Energy Behavior: Developing a tool for homeowners to monitor plan and learn about energy conservation (Master's thesis). Massachusetts Institute of Technology Cambridge, all pages. |
| Meier et al., Thermostat Interface Usability: A Survey, Ernest Orlando Lawrence Berkeley National Laboratory, Environmental Energy Technologies Division, Berkeley California, Sep. 2010, pp. 1-73. |
| Peffer et al., A Tale of Two Houses: The Human Dimension of Demand Response Enabling Technology from a Case Study of Adaptive Wireless Thermostat, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Architecture Dept. and Mechanical Engineering Dept., University of California Berkeley, 2008, pp. 7-242 through 7-253. |
| Peffer et al., Smart Comfort at Home: Design of a Residential Thermostat to Achieve Thermal Comfort, and Save Money and Peak Energy, University of California Berkeley, Mar. 2007, 1 page. |
| Salus, S-Series Digital Thermostat Instruction Manual-ST620 Model No. Instruction Manual, www.salus-tech.com, Version 005, Apr. 29, 2010, 24 pages. |
| Sanford, iPod (Click Wheel) (2004), www.apple-history.com, retrieved from: http://apple-history.com/ipod [retrieved on Apr. 9, 2012], Apr. 9, 2012, 2 pages. |
| Shadrach, Energy Scavenging for Wireless Sensor Nodes with a Focus on Vibration to Electricity Conversion, Dissertation [online], retrieved from the Internet: <URL: http://users.cecs.anu.edu.au/˜Shad.Roundy/paper/ShadThesis.pdf>, Jun. 2003, 297 pages. |
| The Clever Thermostat, ICY BV Web Page, http://www.icy.nl/en/consumer/products/clever-thermostat, ICY BV, 2012, 1 page. |
| The Clever Thermostat User Manual and Installation Guide, ICY BV ICY3815 Timer-Thermostat, 2009, pp. 1-36. |
| Wright, et al., DR ETD—Summary of New Thermostat, TempNode, & New Meter (UC Berkeley Project), Power Point Presentation, Public Interest Energy Research, University of California Berkeley, 2005, pp. 1-49. |
| International Search Report and Written Opinion dated Apr. 11, 2012 in International Patent Application PCT/US2011/061391, all pages. |
| International Preliminary Report on Patentability dated Feb. 25, 2014 for International Patent Application No. PCT/US2011/061391, all pages. |
| International Search Report and Written Opinion dated Jul. 6, 2012 for International Patent Application No. PCT/US2012/030084, all pages. |
| International Preliminary Report on Patentability dated May 1, 2014 for International Patent Application No. PCT/US2012/030084, all pages. |
| International Search Report and Written Opinion dated Jan. 22, 2013 for International Patent Application No. PCT/US2012/061148, all pages. |
| International Preliminary Report on Patentability dated May 1, 2014 for International Patent Application No. PCT/US2012/061148, all pages. |
| Taiwanese Office Action dated Mar. 18, 2014 in ROC (Taiwan) Patent Application No. 100142429, all pages. |
| U.S. Appl. No. 60/512,886, Volkswagen Rotary Knob for Motor Vehicle—English Translation of German Application filed Oct. 20, 2003, all pages. |
| Non-Final Office Action dated Dec. 23, 2014 in U.S. Appl. No. 14/504,220, all pages. |
| Taiwanese Office Action dated May 5, 2014 in ROC (Taiwan) Patent Application No. 100142428, all pages. |
| Taiwanese Office Action dated Sep. 30, 2014 for ROC (Taiwan) Patent Application No. 100142428, all pages. |
| International Search Report and Written Opinion dated Apr. 3, 2012 in International Patent Application No. PCT/US2011/061339, all pages. |
| International Preliminary Report on Patentability dated May 30, 2013 in International Patent Application No. PCT/US2011/061339, all pages. |
| International Search Report and Written Opinion dated Jun. 7, 2012 in International Patent Application No. PCT/US2011/061344, all pages. |
| Office action dated Feb. 5, 2016 in Chinese Patent Application No. 201180055867.1, all pages. |
| Notice of Decision to Grant dated Dec. 16, 2016 in Chinese Patent Application No. 201180055867.1, all pages. |
| Notice of Allowance dated Mar. 22, 2016 in Japanese Patent Application No. 2013-540079, all pages. |
| JP Patent Application No. 2016-084428 filed Nov. 18, 2011, Office Action dated May 23, 2017, all pages. |
| Arens et al., “Demand Response Electrical Appliance Manager—User Interface Design, Development and Testing”, Poster, Demand Response Enabling Technology Development, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2005_6GUIposter.pdf, 2005, 1 page. |
| Arens et al., “Demand Response Enabled Thermostat—Control Strategies and Interface”, Demand Response Enabling Technology Development Poster, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2004_11CEC_TstatPoster.pdf, 2004, 1 page. |
| Arens et al., “Demand Response Enabling Technology Development”, Phase I Report: Jun. 2003-Nov. 2005, University of California Berkeley, Apr. 4, 2006, pp. 1-108. http://escholarship.org/uc/item/0971h43j#page-1. |
| Chatzigiannakis et al., “Priority Based Adaptive Coordination of Wireless Sensors and Actors,” [online] Q2SWinet '06, Oct. 2, 2006 [Retrieved on Mar. 12, 2012]. Retrieved from the Internet: <URL: http://dl.acm.org/citation.cfm?id=1163681>. |
| Chen et al., “Demand Response-Enabled Residential Thermostat Controls”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Mechanical Engineering Dept. and Architecture Dept., University of California Berkeley, Summer 2008, pp. 1-24 through 1-36. |
| Chinese Office Action dated Jun. 25, 2015 for Chinese Patent Application No. 201180055867.1 filed on Nov. 18, 2011, 26 pages. |
| De Almeida et al., “Advanced Monitoring Technologies for the Evaluation of Demand-Side Management Programs”, Energy, vol. 19, No. 6, 1994, pp. 661-678. |
| Detroitborg , “Nest Learning Thermostat: Unboxing and Review”, [online]. Feb. 2012 [retrieved on Aug. 22, 2013]. Retrieved from the Internet: <URL: http://www.youtube.com/watch?v=KrgcOL4oLzc>, 4 pages. |
| Extended European Search Report dated Jul. 8, 2015 for European Patent Application No. 11840968.9 filed on Nov. 18, 2011, 9 pages. |
| Gevorkian, “Alternative Energy Systems in Building Design”, 2009, pp. 195-200. |
| Hoffman et al., “Integration of Remote Meter Reading, Load Control and Monitoring of Customers' Installations for Customer Automation with Telephone Line Signaling”, Electricity Distribution, 1989. CIRED 1989. 10th International Conference on, May 8-12, 1989, pp. 421-424. |
| International Patent Application No. PCT/US2011/061503, International Preliminary Report on Patentability, dated May 30, 2013, 11 pages. |
| International Patent Application No. PCT/US2011/061503, International Search Report and Written Opinion Received, dated Mar. 30, 2012, 11 pages. |
| International Search Report and Written Opinion of PCT/US2012/030084 dated Jul. 6, 2012, all pages. |
| International Preliminary Report on Patentability dated Apr. 22, 2014 for PCT/US2012/030084 filed Mar. 22, 2012, all pages. |
| Japanese Office Action dated Apr. 27, 2015 for Japanese Patent Application No. JP 2013-540079 filed on Nov. 18, 2011, all pages. |
| Levy, “A Vision of Demand Response—2016”, The Electricity Journal, vol. 19, Issue 8, Oct. 2006, pp. 12-23. |
| Lopes, “Case Studies in Advanced Thermostat Control for Demand Response”, AEIC Load Research Conference, St. Louis, MO, Jul. 2004, 36 pages. |
| Martinez, “SCE Energy$mart Thermostat Program”, Advanced Load Control Alliance, Oct. 5, 2004, 20 pages. |
| Matty, “Advanced Energy Management for Home Use”, IEEE Transaction on Consumer Electronics, vol. 35, No. 3, Aug. 1989, pp. 584-588. |
| Motegi et al., “Introduction to Commercial Building Control Strategies and Techniques for Demand Response”, Demand Response Research Center, May 22, 2007, 35 pages. |
| Pash, Adam, “Access your computer anytime and save energy with wake-on LAN,” lifehacker.com, Jan. 24, 2008, 10 pages. |
| Peffer et al., “A Tale of Two Houses: The Human Dimension of Demand Response Enabling Technology from a Case Study of Adaptive Wireless Thermostat”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Architecture Dept. and Mechanical Engineering Dept., University of California Berkeley, Summer 2008, pp. 7-242 through 7-253. |
| SCE Energy$mart Thermostat Study for Southern California Edison—Presentation of Study Results, Population Research Systems, Project #1010, Nov. 10, 2004, 51 pages. |
| Wright et al., “DR ETD—Summary of New Thermostate, TempNode, & New Meter (UC Berkeley Project)”, Power Point Presentation, Public Interest Energy Research, University of California Berkeley. Retrieved from: http://dr.berkeley.edu/dream/presentations/2005_6CEC.pdf, 2005, pp. 1-49. |
| Number | Date | Country | |
|---|---|---|---|
| 20180157280 A1 | Jun 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61627996 | Oct 2011 | US | |
| 61429093 | Dec 2010 | US | |
| 61415771 | Nov 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14720578 | May 2015 | US |
| Child | 15854539 | US | |
| Parent | 13466815 | May 2012 | US |
| Child | 14720578 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13275307 | Oct 2011 | US |
| Child | 13466815 | US | |
| Parent | 13267871 | Oct 2011 | US |
| Child | 13275307 | US | |
| Parent | PCT/US2011/061437 | Nov 2011 | US |
| Child | 13267871 | US | |
| Parent | 13267877 | Oct 2011 | US |
| Child | PCT/US2011/061437 | US | |
| Parent | 13034674 | Feb 2011 | US |
| Child | 13267877 | US | |
| Parent | 13034678 | Feb 2011 | US |
| Child | 13034674 | US |
