Patent Grant
10078319
This patent specification relates to systems, methods, and related computer program products for the monitoring and control of energy-consuming systems or other resource-consuming systems. More particularly, this patent specification relates to user interfaces for control units that govern the operation of energy-consuming systems, household devices, or other resource-consuming systems, including user interfaces for thermostats that govern the operation of heating, ventilation, and air conditioning (HVAC) systems.
While substantial effort and attention continues 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 5 energy efficiency can be achieved by better control and regulation of home heating and cooling equipment. By activating heating, ventilation, and air conditioning (HVAC) equipment for judiciously selected time intervals and carefully chosen operating levels, substantial energy can be saved while at the same time keeping the living space suitably comfortable for its occupants.
Some thermostats offer programming abilities that provide the potential for balancing user comfort and energy savings. However, users are frequently intimidated by a dizzying array of switches and controls. Thus, the thermostat may frequently resort to default programs, thereby reducing user satisfaction and/or energy-saving opportunities.
Provided according to some embodiments are methods for programming a device, such as a thermostat, for control of an HVAC system. Configurations and positions of device components allow for the device to improve energy conservation and to simultaneously allow users to experience pleasant interactions with the device (e.g., to set preferences). HVAC schedules may be programmed for the device using a combination of pre-existing HVAC schedules or template schedules and automated schedule learning. For example, a pre-existing schedule may be initiated on the thermostat and the automated schedule learning may be used to update the pre-existing schedule based on users' interactions with the thermostat. The preexisting HVAC schedules may be stored on a device or received from a social networking service or another online service that includes shared HVAC schedules.
According to some embodiments, a method for programming an HVAC schedule for a thermostat is provided. The method includes generating one or more input options on a schedule interface; receiving input corresponding to one or more responses to the one or more input options, wherein the input is received at the schedule interface; selecting an HVAC schedule from one or more of a plurality of pre-existing HVAC schedules stored on the thermostat, wherein the selection of the HVAC schedule is based on the received input; associating the thermostat with the selected HVAC schedule, wherein associating includes initiating the selected HVAC schedule on the thermostat; receiving, during a time period subsequent to the association, input corresponding to one or more temperature control selections, wherein the input is received on a control interface; generating an updated HVAC schedule based on the selected HVAC schedule and the one or more temperature control selections; and associating the thermostat with the updated HVAC schedule, wherein associating includes initiating the updated HVAC schedule on the thermostat.
According to some embodiments, a method for programming an HVAC schedule for a thermostat is provided. The method includes receiving input corresponding to a selection of a pre-existing HVAC schedule, wherein the pre-existing HVAC schedule was shared on a social networking service, associating the thermostat with the selected pre-existing HVAC schedule, wherein associating includes initiating the selected pre-existing HVAC schedule on the thermostat; receiving, during a time period subsequent to the association, input corresponding to one or more temperature control selections, wherein the input is received on a control interface; generating an updated HVAC schedule based on the selected pre-existing HVAC schedule and the one or more temperature control selections; and associating the thermostat with the updated HVAC schedule, wherein associating includes initiating the updated HVAC schedule on the thermostat.
To better understand the nature and advantages of the present invention, reference should be made to the following description and the accompanying figures. It is to be understood, however, that each of the figures is provided for the purpose of illustration only and is not intended as a definition of the limits of the scope of the present invention. Also, as a general rule, and unless it is evident to the contrary from the description, where elements in different figures use identical reference numbers, the elements are generally either identical or at least similar in function or purpose.
The present invention will now be described in detail with reference to certain embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known details have not been described in detail in order not to unnecessarily obscure the present invention.
Provided according to one or more embodiments are systems, methods, computer program products, and related business methods for controlling and/or programming one or more HVAC systems based on one or more versatile sensing and control units (VSCU units), each VSCU unit being configured and adapted to provide sophisticated, customized, energy-saving HVAC control functionality while at the same time being visually appealing, non-intimidating, elegant to behold, and delightfully easy to use. The term “thermostat” is used hereinbelow to represent a particular type of VSCU unit (Versatile Sensing and Control) that is particularly applicable for HVAC control in an enclosure. Although “thermostat” and “VSCU unit” may be seen as generally interchangeable for the contexts of HVAC control of an enclosure, it is within the scope of the present teachings for each of the embodiments hereinabove and hereinbelow to be applied to VSCU units having control functionality over measurable characteristics other than temperature (e.g., pressure, flow rate, height, position, velocity, acceleration, capacity, power, loudness, brightness) for any of a variety of different control systems involving the governance of one or more measurable characteristics of one or more physical systems, and/or the governance of other energy or resource consuming systems such as water usage systems, air usage systems, systems involving the usage of other natural resources, and systems involving the usage of various other forms of energy. Each VSCU unit includes a user-interface component, such as a rotatable ring. Using the ring, a user can easily navigate through and select between selection options (e.g., to set a temperature setpoint or identify preferences). For example, a user may rotate a ring (e.g., in a clockwise direction); a processing system may dynamically identify a setpoint temperature value (e.g., higher than a previous value) based on rotational input; an electronic display may dynamically display a digital numerical value representative of the identified setpoint temperature value. Further, the user may be able to view and/or navigate through a menuing system using the ring. For example, a user input (e.g., inwards pressure on the ring) may result in a presentation of a menuing system on the display. A user may rotate the ring to, e.g., scroll through selection options and select an option by pressing on the ring. Inwards pressure on the ring may cause a distinct sensory response (e.g., a clicking sound or feel) that may confirm to the user that the selection has been made. In some instances, the ring is the primary or only user-input component within the VSCU. Thus, a user will not be intimidated by a large number of controls and will be able to easily understand how to interact with the unit.
Nevertheless, each VSCU unit may be advantageously provided with a selectively layered functionality, such that unsophisticated users are only exposed to a simple user interface, but such that advanced users can access and manipulate many different energy-saving and energy tracking capabilities. For example, an advanced user may be able to set a plurality of time-dependent temperature setpoints (i.e., scheduled setpoints) through thermostat interactions via the rotatable ring, while an unsophisticated user may limit such interactions to only set seemingly or actually static setpoints. Importantly, even for the case of unsophisticated users who are only exposed to the simple user interface, the VSCU unit provides advanced energy-saving functionality that runs in the background, the VSCU unit quietly using multi-sensor technology to “learn” about the home's heating and cooling environment and optimizing the energy-saving settings accordingly.
The VSCU unit also “learns” about the users themselves through user interactions with the device (e.g., via the rotatable ring) and/or through automatic learning of the users' preferences. For example, in a congenial “setup interview”, a user may respond to a few simple questions (e.g., by rotating the rotatable ring to a position at which a desired response option is displayed). Multi-sensor technology may later be employed to detect user occupancy patterns (e.g., what times of day they are home and away), and a user's control over set temperature on the dial may be tracked over time. The multi-sensor technology is advantageously hidden away inside the VSCU unit itself, thus avoiding the hassle, complexity, and intimidation factors associated with multiple external sensor-node units. On an ongoing basis, the VSCU unit processes the learned and sensed information according to one or more advanced control algorithms, and then automatically adjusts its environmental control settings to optimize energy usage while at the same time maintaining the living space at optimal levels according to the learned occupancy patterns and comfort preferences of the user. Even further, the VSCU unit is programmed to promote energy-saving behavior in the users themselves by virtue of displaying, at judiciously selected times on its visually appealing user interface, information that encourages reduced energy usage, such as historical energy cost performance, forecasted energy costs, and even fun game-style displays of congratulations and encouragement.
Advantageously, the selectively layered functionality of the VSCU unit allows it to be effective for a variety of different technological circumstances in home and business environments, thereby making the same VSCU unit readily saleable to a wide variety of customers. For simple environments having no wireless home network or internet connectivity, the VSCU unit operates effectively in a standalone mode, being capable of learning and adapting to its environment based on multi-sensor technology and user input, and optimizing HVAC settings accordingly. However, for environments that do indeed have home network or internet connectivity, the VSCU unit can operate effectively in a network-connected mode to offer a rich variety of additional capabilities.
It is to be appreciated that while one or more embodiments is detailed herein for the context of a residential home, such as a single-family house, the scope of the present teachings is not so limited, the present teachings being likewise applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space having one or more HVAC systems. It is to be further 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 VSCU unit or other device or user interface in the context of some particularly advantageous situations 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. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, and is also one of the users of the unit and is a customer of the utility company and/or VSCU data service provider. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. Importantly, while the identity of the person performing the action may be germane to a particular advantage provided by one or more of the embodiments—for example, the password-protected temperature governance functionality described further herein may be particularly advantageous where the landlord holds the sole password and can prevent energy waste by the tenant—such identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those particular individuals having those particular identities.
It is to be appreciated that although exemplary embodiments are presented herein for the particular context of HVAC system control, there are a wide variety of other resource usage contexts for which the embodiments are readily applicable including, but not limited to, water usage, air usage, the usage of other natural resources, and the usage of other (i.e., non-HVAC-related) forms of energy, as would be apparent to the skilled artisan in view of the present disclosure. Therefore, such application of the embodiments in such other resource usage contexts is not outside the scope of the present teachings.
As used herein, “setpoint” or “temperature setpoint” or “temperature selections” may refer to a target temperature setting of a temperature control system, such as one or more of the VSCU units described herein, as set by a user or automatically according to a schedule. As would be readily appreciated by a person skilled in the art, many of the disclosed thermostatic functionalities described hereinbelow apply, in counterpart application, to both the heating and cooling contexts, with the only different being in the particular setpoints and directions of temperature movement. To avoid unnecessary repetition, some examples of the embodiments may be presented herein in only one of these contexts, without mentioning the other. Therefore, where a particular embodiment or example is set forth hereinbelow in the context of home heating, the scope of the present teachings is likewise applicable to the counterpart context of home cooling, and vice versa, to the extent such counterpart application would be logically consistent with the disclosed principles as adjudged by the skilled artisan.
The detailed description includes three subsections: (1) overview of VSCU unit & smart-home environment, (2) automated control-schedule learning in the context of a VSCU unit, and (3) HVAC schedule establishment in a VSCU unit. The first subsection provides a description of one area technology that offers many opportunities for of application and incorporation of automated-control-schedule-learning methods. The second subsection provides a detailed description of automated control-schedule learning, including a first, general implementation. The third subsection provides specific examples of establishing HVAC schedules using a combination of pre-existing HVAC schedules and automated control-schedule learning.
The outer ring 106 preferably has an outer finish identical to that of the main body 108, while the sensor ring 104 and circular display monitor 102 have a common circular glass (or plastic) outer covering that is gently arced in an outward direction and that provides a sleek yet solid and durable-looking overall appearance. The outer ring 106 may be disposed along a front face of a housing of the VSCU unit 100. The front face may be circular, and the housing may be disk-like in shape. The outer ring may substantially surround the circular display monitor or substantially surround a portion of the circular display monitor visible to a user. The outer ring 106 may be generally coincident with an outer lateral periphery of said disk-like shape, as illustrated, e.g., in
The sensor ring 104 contains any of a wide variety of sensors including, without limitation, infrared sensors, visible-light sensors, and acoustic sensors. Preferably, the glass (or plastic) that covers the sensor ring 104 is smoked or mirrored such that the sensors themselves are not visible to the user. An air venting functionality is preferably provided, such as by virtue of the peripheral gap 100, which allows the ambient air to be sensed by the internal sensors without the need for visually unattractive “gills” or grill-like vents.
For one embodiment, the inward push of
By virtue of user rotation of the outer ring 106 (referenced hereafter as a “ring rotation”) and the inward pushing of the outer ring 106 (referenced hereinafter as an “inward click”) responsive to intuitive and easy-to-read prompts on the circular display monitor 102, the VSCU unit 100 is advantageously capable of receiving all necessary information from the user for basic setup and operation. Preferably, the outer ring 106 is mechanically mounted in a manner that provides a smooth yet viscous feel to the user, for further promoting an overall feeling of elegance while also reducing spurious or unwanted rotational inputs. According to various implementations, the outer ring 106 rotates on plastic bearings and uses an optical digital encoder to measure the rotational movement and/or rotational position of the outer ring 106. In accordance with alternate implementations, other technologies such as mounting the outer ring 106 on a central shaft may be employed. For one embodiment, the VSCU unit 100 recognizes three fundamental user inputs by virtue of the ring rotation and inward click: (1) ring rotate left, (2) ring rotate right, and (3) inward click.
According to some implementations, multiple types of user input may be generated depending on the way a pushing inward of head unit front including the outer ring 106 is effectuated. In some implementations a single brief push inward of the outer ring 106 until the audible and/or tactile click occurs followed by a release (single click) can be interpreted as one type of user input (also referred to as an “inward click”). In other implementations, pushing the outer ring 106 in and holding with an the inward pressure for an amount of time such as 1-3 seconds can be interpreted as another type of user input (also referred to as a “press and hold”). According to some further implementations, other types of user input can be effectuated by a user such as double and/or multiple clicks, and pressing and holding for longer and/or shorter periods of time. According to other implementations, speed-sensitive or acceleration-sensitive rotational inputs may also be implemented to create further types of user inputs (e.g., a very large and fast leftward rotation specifies an “Away” occupancy state, while a very large and fast rightward rotation specifies an “Occupied” occupancy state).
Although the scope of the present teachings is not so limited, it is preferred that there not be provided a discrete mechanical HEAT-COOL toggle switch, or HEAT-OFF-COOL selection switch, or HEAT-FAN-OFF-COOL switch anywhere on the VSCU unit 100, this omission contributing to the overall visual simplicity and elegance of the VSCU unit 100 while also facilitating the provision of advanced control abilities that would otherwise not be permitted by the existence of such a switch. It is further highly preferred that there be no electrical proxy for such a discrete mechanical switch (e.g., an electrical push button or electrical limit switch directly driving a mechanical relay). Instead, it is preferred that the switching between these settings be performed under computerized control of the VSCU unit 100 responsive to its multi-sensor readings, its programming (optionally in conjunction with externally provided commands/data provided over a data network), and/or the above-described “ring rotation” and “inward click” user inputs.
The VSCU unit 100 comprises physical hardware and firmware configurations, along with hardware, firmware, and software programming that is capable of carrying out the functionalities described explicitly herein or in one of the commonly assigned incorporated applications. In view of the instant disclosure, a person skilled in the art would be able to realize the physical hardware and firmware configurations and the hardware, firmware, and software programming that embody the physical and functional features described herein without undue experimentation using publicly available hardware and firmware components and known programming tools and development platforms. Similar comments apply to described devices and functionalities extrinsic to the VSCU unit 100, such as devices and programs used in remote data storage and data processing centers that receive data communications from and/or that provide data communications to the VSCU unit 100. By way of example, references hereinbelow to machine learning and mathematical optimization algorithms, as carried out respectively by the VSCU unit 100 in relation to home occupancy prediction and setpoint optimization, for example, can be carried out using one or more known technologies, models, and/or mathematical strategies including, but not limited to, artificial neural networks, Bayesian networks, genetic programming, inductive logic programming, support vector machines, decision tree learning, clustering analysis, dynamic programming, stochastic optimization, linear regression, quadratic regression, binomial regression, logistic regression, simulated annealing, and other learning, forecasting, and optimization techniques.
In either case, the VSCU unit 100 can advantageously serve as an “inertial wedge” for inserting an entire energy-saving technology platform into the home. Simply stated, because most homeowners understand and accept the need for home to have a thermostat, even the most curmudgeonly and techno-phobic homeowners will readily accept the simple, non-intimidating, and easy-to-use VSCU unit 100 into their homes. Once in the home, of course, the VSCU unit 100 will advantageously begin saving energy for a sustainable planet and saving money for the homeowner, including the curmudgeons. Additionally, however, as homeowners “warm up” to the VSCU unit 100 platform and begin to further appreciate its delightful elegance and seamless operation, they will be more inclined to take advantage of its advanced features, and they will furthermore be more open and willing to embrace a variety of compatible follow-on products and services as are described further hereinbelow. This is an advantageous win-win situation on many fronts, because the planet is benefitting from the propagation of energy-efficient technology, while at the same time the manufacturer of the VSCU unit and/or their authorized business partners can further expand their business revenues and prospects. For clarity of disclosure, the term “VSCU Efficiency Platform” refers herein to products and services that are technologically compatible with the VSCU unit 100 and/or with devices and programs that support the operation of the VSCU unit 100.
Some implementations of the VSCU unit 100 incorporate one or more sensors to gather data from the environment associated with the house 201. Sensors incorporated in VSCU unit 100 may detect occupancy, temperature, light and other environmental conditions and influence the control and operation of HVAC system 299. VSCU unit 100 uses a grille member (not shown in
The HVAC system is selectively actuated via control electronics 212 that communicate with the VSCU unit 100 over control wires 298. Thus, for example, as known in the art, for a typical simple scenario of a four-wire configuration in which the control wires 298 consist of power (R), heat (W), cool (Y), and fan (G), the VSCU unit 100 will short-circuit W to R to actuate a heating cycle (and then disconnect W from R to end the heating cycle), will short-circuit Y to R to actuate a cooling cycle (and then disconnect Y from R to end the cooling cycle), and will short-circuit G to R to turn on the fan (and then disconnect G from R to turn off the fan). For a heating mode, when VSCU unit 100 determines that an ambient temperature is below a lower threshold value equal to a setpoint temperature minus a swing value, the heating cycle will be actuated until the ambient temperature rises to an upper threshold value equal to the setpoint value plus the swing value. For a cooling mode, when VSCU unit 100 determines that an ambient temperature is above an upper threshold value equal to a setpoint temperature plus a swing value, the cooling cycle will be actuated until the ambient temperature lowers to a lower threshold value equal to the setpoint value minus the swing value. Without limitation, the swing values for heating and cooling can be the same or different, the upper and lower swing amounts can be symmetric or asymmetric, and the swing values can be fixed, dynamic, or user-programmable, all without departing from the scope of the present teachings.
When this happens, as illustrated in
Also displayed is a setpoint icon 302 disposed along a periphery of the circular display monitor 102 at a location that is spatially representative the current setpoint. Although it is purely electronic, the setpoint icon 302 is reminiscent of older mechanical thermostat dials, and advantageously imparts a feeling of familiarity for many users as well as a sense of tangible control.
Notably, the example of
Referring now to
Whenever the actual current temperature is different than the setpoint temperature, a representation (e.g., a digital numeric representation) of an actual temperature readout 306 is provided in relatively small digits along the periphery of the circular a location spatially representative the actual current temperature. Further provided is a trailing icon 308, which could alternatively be termed a tail icon or difference-indicating, that extends between the location of the actual temperature readout 306 and the setpoint icon 302. Further provided is a time-to-temperature readout 310 that is indicative of a prediction, as computed by the VSCU unit 100, of the time interval required for the HVAC system to bring the temperature from the actual current temperature to the setpoint temperature.
In some embodiments, user interactions with the VSCU unit 100 by virtue of manipulations of the outer ring 106 are analyzed and non-numeric indicators (e.g., related to environmental favorability of the action) are presented to the user.
For one embodiment, the VSCU unit 100 is designed to be entirely silent unless a user has walked up and begun controlling the unit. Advantageously, there are no clicking-type annoyances when the heating or cooling units are activated as with conventional prior art thermostats. Optionally, the VSCU unit 100 can be configured to synthesize artificial audible clicks, such as can be output through a piezoelectric speaker, to provide “tick” feedback as the user dials through different temperature settings. Thus, in some instances, VSCU unit 100 includes an audio output device configured to output synthesized audible ticks through said audio output device in correspondence with user rotation of the outer ring 106.
Via the single outer ring 106, a user may easily be able to perform multiple types of interactions with the VSCU unit 100. For example, as described above, the user may be able to set a setpoint temperature value. Other types of interactions may additionally be performed using the rotating and clicking features of the same outer ring 106. A selection component (e.g., ring 106) and electronic display 102 may enable a user to, e.g.: (1) identify a type of variable to be set or information to be input; and/or (2) identify a value for one or more variables and/or for one or more information fields.
For example, an HVAC system may include a plurality of variable categories (e.g., energy, schedule, settings, heating/cooling mode, etc.). As described in greater detail below, display 102 may be configured to present a circular menu: as the user rotates outer ring 106, a different category may appear at or near a top of the display. A user may select a particular type of category by clicking outer ring 106. Selection of some categories allows a user to view available sub-menus. For example, rotation of outer ring 106 may cause an apparent translation of the entire screen, such that a first sub-menu moves off of the screen as a second sub-menu moves on to the screen. In some instances, the user may be able to instantly interact with the displayed sub-menu even without clicking ring 106.
Each variable and/or information field may be defined by a value. The value may include, e.g., a numeric value (e.g., a setpoint-temperature variable is set at “75”), a word (e.g., a password is set as “Password”), a letter (e.g., a thermostat is identified as Thermostat “A”), a selection amongst a plurality of options (e.g., smart learning is “Enabled”), etc. An active variable/field may be identified based on a user's selection of the variable/field, a default thermostat state and/or other information.
Various value options may then be presented to the user. For example, a list of options may be presented in a grid-like fashion on the display, and a user may move a highlighted option by rotating outer ring 106. As another example, alphanumeric characteristics may be accurately presented around an outer border of electronic display 316. In some embodiments, the options are indicatively presented (e.g., by presenting a series of tick marks, representing options of evenly spaced values), and one or more options (e.g., a highlighted option) may be expressly presented (e.g., by displaying a value of the highlighted option at or near a center of the display). A user may rotate outer ring 106 until a desired option is highlighted. When a selection is highlighted, the selection may be confirmed by an inward click input on the outer ring 106.
The screens shown, according to some embodiments, are displayed on a thermostat 100 on a round dot-matrix electronic display 102 having a rotatable ring 106.
Upon user rotation of the rotatable ring 106 (see
Menu items may include text (e.g., “Schedule”) and/or icons (e.g., disks 510 and 512).
Menu items may further indicate a currently active selection or mode of operation. For example, one of disks 510 and 512, in this case the heating disk 512, is highlighted with a colored outline, to indicate the current operating mode (i.e. heating or cooling) of the thermostat. In one alternative embodiment, the mode icon 509 can be replaced with the text string “HEAT/COOL/OFF” or simply the word “MODE”.
If in inward click is performed from screen 508, a menu screen 514 appears (e.g. using a “coin flip” transition). In screen 514 the user can view the current mode (marked with a check mark). Screen 514 illustrates another way in which rotatable ring 106 may be used to make a selection. A plurality of selection options may be presented, with one or more options being emphasized (e.g., highlighted). A user may highlight a different option by rotating rotatable ring 106. For example, as a user rotates rotatable ring 106 in a clockwise fashion, options further down the list become highlighted. Once the user is satisfied that the desired option is highlighted, they may click the ring to confirm the selection. Thus, in the example shown in screen 514, a user may rotate rotatable ring 106 clockwise to move the highlighting from “HEAT” to “COOL” or “OFF.” The user may then establish the selection by clicking the ring, and thereby change the mode. If “COOL” is selected then the thermostat will change over to cooling mode (such changeover as might be performed in the springtime), and the cooling disk icon will highlighted on screens 514 and 508. The menu can also be used to turn the thermostat off by selecting “OFF.” In cases the connected HVAC system only has heating or cooling but not both, the words “HEAT” or “COOL” or “OFF” are displayed on the menu 520 instead of the colored disks.
Screen 608 has a central disk 606 indicating the name of the sub-menu, in this case the Fan mode. Some sub menus only contain a few options which can be selected or toggled among by inward clicking alone. For example, the Fan sub-menu 608 only has two settings “automatic” (shown in screen 608) and “always on” (shown in screen 610). In this case the fan mode is changed by inward clicking, which simply toggles between the two available options. Ring rotation shifts to the next (or previous) settings sub-menu item. Thus rotating the ring from the fan sub-menu shift to the system on/off sub-menu shown in screens 612 (in the case of system “ON”) and 614 (in the case of system “OFF”). The system on/off sub-menu is another example of simply toggling between the two available options using the inward click user input.
Screens 666 and 667 are used to toggle between Celsius and Fahrenheit units, according to some embodiments. According to some embodiments, if Celsius units is selected, then half-degrees are displayed by the thermostat when numerical temperature is provided (for example, a succession of 21, 215, 22, 225, 23, 235, and so forth in an example in which the user is turning up the rotatable ring on the main thermostat display). According to another embodiment, there is another sub-menu screen disk (not shown) that is equivalent to the “Brightness” and “Click Sound” disks in the menu hierarchy, and which bears one of the two labels “SCREEN ON when you approach” and “SCREEN ON when you press,” the user being able to toggle between these two options by an inward click when this disk is displayed. When the “SCREEN ON when you approach” is active, the proximity sensor-based activation of the electronic display screen 102 is provided (as described above with the description accompanying
For one embodiment, the VSCU unit 100 is programmed to provide a software lockout functionality, wherein a person is required to enter a password or combination before the VSCU unit 100 will accept their control inputs. The user interface for password request and entry can be similar to that shown in
Thus, as exemplified in
As described below, an implementation of automated control-schedule learning is included in the aforementioned VSCU unit 100. For example, VSCU unit 100 includes intelligent features that learn about the users, beginning with a setup dialog (e.g., the setup interview as mentioned above and further described in the paragraphs below corresponding to
As mentioned above, for simple environments having no wireless home network or internet connectivity, VSCU unit 100 operates effectively in a standalone mode, learning and adapting to an environment based on multi-sensor technology and user input. However, for environments that have home network or Internet connectivity, the intelligent thermostat operates effectively in a network-connected mode to offer additional capabilities. For example, when VSCU unit 100 is connected to the Internet via a home network, such as through IEEE 802.11 (Wi-Fi) connectivity, the intelligent thermostat may: (1) provide real-time or aggregated home energy performance data to a utility company, intelligent thermostat data service provider, intelligent thermostats in other homes, or other data destinations; (2) receive real-time or aggregated home energy performance data from a utility company, intelligent thermostat data service provider, intelligent thermostats in other homes, or other data sources; (3) receive new energy control instructions and/or other upgrades from one or more intelligent thermostat data service providers or other sources; (4) receive current and forecasted weather information for inclusion in energy-saving control algorithm processing; (5) receive user control commands from the user's computer, network-connected television, smart phone, and/or other stationary or portable data communication appliance; (6) provide an interactive user interface to a user through a digital appliance; (7) receive control commands and information from an external energy management advisor, such as a subscription-based service aimed at leveraging collected information from multiple sources to generate energy-saving control commands and/or profiles for their subscribers; (8) receive control commands and information from an external energy management authority, such as a utility company to which limited authority has been voluntarily given to control the intelligent thermostat in exchange for rebates or other cost incentives; (9) provide alarms, alerts, or other information to a user on a digital appliance based on intelligent thermostat-sensed HVAC-related events; (10) provide alarms, alerts, or other information to the user on a digital appliance based on intelligent thermostat-sensed non-HVAC related events; and (11) provide a variety of other useful functions enabled by network connectivity. Additional features and details concerning the networking of VSCU unit 100 are described in the paragraphs below corresponding to
Next, an implementation of the above-described automated-control-schedule-learning methods for VSCU unit 100 is provided.
The initial learning process represents an “aggressive learning” approach in which the goal is to quickly establish a basic and at least roughly appropriate HVAC schedule for the user based on a very brief period of automated observation and tracking of user behavior. Once the initial learning process is established, the VSCU unit 100 then switches over to a different mode of automated learning, termed herein steady-state learning, which is directed to perceiving and adapting to longer-term repeated behaviors of the user, and which is described further infra with respect to
At step 804, a default beginning schedule is accessed, which can be thought of as a sort of “clay” that will be quickly formed into an at least roughly appropriate schedule for the user by the initial learning process. For one preferred embodiment, the beginning schedule is simply a single setpoint that takes effect at 8 AM each day, having a single setpoint temperature. This single setpoint temperature is dictated by a user response that is provided near the end of the setup interview, or upon re-instantiation of initial learning, where the user is simply asked whether they want their thermostat to start learning a heating schedule or a cooling schedule. If the user chooses heating, then the initial single setpoint temperature is set to 68 degrees F. (or some other appropriate heating setpoint temperature), and if the user chooses cooling, then the initial single setpoint temperature is set to 80 degrees F. (or some other appropriate cooling setpoint temperature). In other preferred embodiments, the default beginning schedule can be one of a plurality of predetermined or pre-existing “HVAC schedules” or “template schedules” selected directly or indirectly by the user at the initial setup interview (e.g., “single-person household”; “working family”, “retired couple”, etc.).
At step 806, a new day of initial learning is instantiated. The selection of a one-day period as a basis for initial learning has been found to provide good results. As used herein, a “basis” time period means the period of time over which user behavior is observed and captured before it is processed to produce a next version, iteration, or refinement of the schedule. While a basis period of one day has been found to provide good results, it is to be appreciated that the periodic basis for learning can be other periods of time, such multi-day blocks of time, sub-day blocks of time (e.g., 6 hours at a time), time intervals (e.g., weekdays and weekends), any other suitable period as 6-hour blocks of time, and can even be variable, random, or continuous. For example, when performed in a continuous basis, any user setpoint change or scheduled setpoint input can be used as a trigger for processing that information in conjunction with the present schedule to produce a next version, iteration, or refinement of the schedule. For one preferred embodiment in which the VSCU unit 100 is a power-stealing thermostat having a rechargeable battery, the period of one day has been found to provide a suitable balance between the freshness of the schedule revisions and the need to maintain a modest computing load on the head unit microprocessor to preserve battery power. Therefore, in the discussion that follows, it is to be appreciated that the use of a “day” as the basis period is not to be construed as limiting the scope of the present teachings.
At step 808, throughout the day, the VSCU unit 100 (hereinbelow simply “thermostat”) receives and stores both real-time (RT) and non-real time (NRT) user setpoint entries. As used herein, a real-time (RT) user setpoint entry corresponds to a user-entered setpoint that is to take effect immediately upon entry. Thus, for example, any time the user walks up to the dial and changes the current setpoint temperature by a ring rotation, as shown in
Shown in
Referring now to step 810, throughout the day of initial learning, the thermostat proceeds to control the HVAC system according to (i) whatever current version of the schedule is then in effect, which would be the default beginning schedule from step 804 if this is indeed the first day of initial learning, as well as (ii) whatever RT setpoint entries are made by the user, as well as (iii) whatever NRT setpoint entries have been made that are causally applicable. The effect of an RT setpoint entry on the current setpoint temperature is maintained until the next pre-existing setpoint is encountered, until a causally applicable NRT setpoint is encountered, or until a subsequent RT setpoint entry is made. Thus, with reference to
According to one optional alternative embodiment, step 810 can be carried out such that any RT setpoint entry is only effective for a maximum of 2 hours (or other relatively brief interval) in terms of the actual operating setpoint temperature, and then the operating setpoint temperature is returned to whatever would be dictated by the pre-existing setpoints on the current schedule, or whatever would be dictated by any causally applicable NRT setpoint entries. This optional alternative embodiment is designed to encourage the user to make more RT setpoint entries during the initial learning period, such that the learning process can be achieved more quickly. As an additional optional alternative, the default beginning schedule at step 804 is assigned with relatively low-energy setpoints (i.e., relatively cold in winter, such as 62 degrees or 65 degrees), which can result in a lower-energy total schedule since any higher-energy setpoints would necessarily be resulting from the explicit wishes of the user. As yet another additional optional alternative, during the first few days, instead of reverting to any pre-existing setpoints after 2 hours that would otherwise be applicable, the operating setpoint instead reverts to a lowest-energy pre-existing setpoint in the schedule. For simplicity and clarity of disclosure, however, it is presumed in the following description that these “forcible low-energy” optional alternative embodiments are not activated.
Referring now to step 812, at the end of the day (or other suitable basis period as discussed above), the stored RT and NRT setpoints are processed against each other and against the schedule of pre-existing setpoints in the schedule that was in effect that day to generate a modified version, iteration, or refinement of that schedule, the particular steps for which are set forth in
For some embodiments, the decision at step 814 as to whether initial or “aggressive” schedule learning is complete is based on both the passage of time and whether there has been a sufficient amount of user behavior to observe. For one preferred embodiment, the initial learning is considered to be complete only if both of the following criteria are met: (i) two days of initial learning have passed, and (ii) there have been ten separate one-hour intervals for which there has been at least one user setpoint entry. Any of a variety of different criteria can be used for judging whether there has been enough observed user setpoint entry behavior to conclude initial learning without departing from the scope of the present teachings.
At step 832, each cluster of setpoint entries is processed to generate a single new setpoint that represents the entire cluster in terms of effective time and temperature value. This process, which could be called setpoint entry harmonization or fighting resolution, is directed to simplifying the schedule while at the same time best capturing the true intent of the user by virtue of their setpoint entry behavior. While a variety of different approaches (e.g., averaging of temperature values and effective times of cluster members) could be used without necessarily departing from the scope of the present teachings, one particularly effective method for carrying out the objective of step 832, which is described in more detail in
Referring now to
Referring now again to
Thus, referring now to
Referring now again to
Referring now to step 842 of
Illustrated in
Referring now to step 844 of
Referring now to
Subsequent to the deletion of any new setpoints (of the first type) pursuant to step 881, at step 882 there is identified any new setpoint of the first type that has an effective time that is within 30 minutes (or other suitable nearness interval) of the immediately subsequent pre-existing setpoint, and if so, that new setpoint is moved later in time to one hour (or other suitable proximity interval greater than the suitable nearness interval) later than the immediately preceding pre-existing setpoint, and the immediately subsequent pre-existing setpoint is deleted. When applied to the example scenario at
Subsequently to step 886, at step 887 there is identified and deleted any RT-tagged new setpoint that is within one hour (or other suitable proximity interval) of an immediately subsequent pre-existing setpoint and that has a temperature value not greater than one degree F. (or other suitable temperature similarity value) different from an immediately preceding pre-existing setpoint. Subsequently to step 887, step 888 is carried in which, for each new setpoint, any pre-existing setpoint that is within one hour (or other suitable proximity interval) of that new setpoint is deleted. Thus, for example, shown in
Subsequently to step 888, step 890 is carried out in which, starting from the earliest effective setpoint time in the schedule and moving later in time to the latest effective setpoint time, any setpoint (new or pre-existing) is deleted if that setpoint has a temperature value that differs by not more than 1 degree F. or 0.5 degree C. from that of the immediately preceding setpoint (when quantized to the nearest 1 degree F. or 0.5 degree C. as discussed above). Thus, for example, shown in
Certain differences do arise between initial and steady state learning, however, in that for the steady state learning process there is an attention to the detection of historical patterns in the setpoint entries, an increased selectivity in the target days across which the detected setpoint patterns are replicated, and other differences as described further hereinbelow. Referring now to
However, it is within the scope of the present teachings that there can be a previously established schedule that is accessed at step 1004. By way of example, there can be stored in the VSCU unit 100, or alternatively in a cloud server to which it has a network connection, a plurality of different schedules that were previously built up by the VSCU unit 100 over a similar period in the preceding year. For example, there can be a “January” schedule that was built up over the preceding January and then stored to memory on January 31. If step 1004 is being carried out on January 1 of the following year, then that previously stored “January” schedule can be accessed. It is within the scope of the present teachings for the VSCU unit 100 to build up and store schedules that are applicable for any of a variety of time periods (e.g., by month, by season, etc.) and then to later access those schedules at step 1004 for use as the next current schedule. Similar storage and recall methods are applicable for the historical RT/NRT setpoint entry databases that are discussed further hereinbelow.
At step 1006, a new day (or other suitable observation period, see discussion supra) of steady-state learning is begun. At step 1008, throughout the day, the thermostat receives and tracks both real-time (RT) and non-real time (NRT) user setpoint entries. At step 1010, throughout the day, the thermostat proceeds to control the HVAC system according to (i) the current version of the schedule, (ii) whatever RT setpoint entries are made by the user, and (iii) whatever NRT setpoint entries have been made that are causally applicable.
According to one optional alternative embodiment, step 1010 can be carried out such that any RT setpoint entry is only effective for a maximum of 4 hours (or other interval that is reasonably extensive but not permanent) in terms of the actual operating setpoint temperature, and then the operating setpoint temperature is returned to whatever would be dictated by the pre-existing setpoints on the current schedule, or whatever would be dictated by any causally applicable NRT setpoint entries. As another optional alternative, instead of reverting to any pre-existing setpoints after 4 hours that would otherwise be applicable, the operating setpoint instead reverts to a relatively low energy value, such as a lowest pre-existing setpoint in the schedule. This kind of “low-energy bias” operation, which can optionally be a user-settable mode of operation such that the user can activate it and de-activate it, can advantageously serve to drive the schedule to a kind of low-energy steady-state resulting schedule, which can save energy and money for the user. For simplicity and clarity of disclosure, however, it is presumed in the following description that such four hour reversions and/or “low-energy bias” modes are not activated.
At the end of the steady-state learning day such as at or around midnight, processing steps 1012-1016 are carried out. At step 1012, a historical database of RT and NRT user setpoint entries, which preferably extends back at least two weeks, is accessed. At step 1014, the day's tracked RT/NRT setpoint entries are processed in conjunction with the historical database of RT/NRT setpoint entries and the pre-existing setpoints in the current schedule to generate a modified version of the current schedule, using steps that are described further infra with respect to
Referring now to
For one preferred embodiment, in carrying out step 1036, the replicated setpoints are assigned the same effective time of day, and the same temperature value, as the particular current day pattern-candidate setpoint for which a pattern was detected. However, the scope of the present teachings is not so limited. In other preferred embodiments, the replicated setpoints can be assigned the effective time of day of the historical pattern-candidate setpoint that was involved in the match, and/or the temperature value of that historical pattern-candidate setpoint. In still other preferred embodiments, the replicated setpoints can be assigned the average effective time of day of the current and historical pattern-candidate setpoints that were matched, and/or the average temperature value of the current and historical pattern-candidate setpoints that were matched.
Subsequent to step 1036, at step 1038 the resulting replicated schedule of new setpoints is overlaid onto the current schedule of pre-existing setpoints. Also at step 1038, any NRT-tagged setpoints resulting from step 1030, supra, are overlaid onto the current schedule of pre-existing setpoints. At step 1040, the overlaid new and pre-existing setpoints are then mutually filtered and/or shifted in effective time using methods similar to those discussed supra for step 846 of
Examples of how setup interviews may be used in conjunction with pre-existing HVAC schedules and automated schedule learning are discussed in the following section.
This “HVAC Schedule Establishment in a VSCU Unit” subsection includes four subsections: (A) selecting pre-existing HVAC schedules based on a setup interview, (B) using automated schedule learning to update a pre-existing HVAC schedule selected based on a setup interview, (C) selecting HVAC schedules shared on a social networking service, and (D) using automated schedule learning to update a selected HVAC schedule that were shared on a social networking service
(A) Selecting Pre-Existing HVAC Schedules Based on a Setup Interview
HVAC schedules may be programmed for VSCU unit 100. According to some embodiments, the user's responses to the questions at the initial setup interview (e.g., the setup interview mentioned above) are used to automatically “snap” that household onto one of a plurality of pre-existing HVAC schedules or template schedules, i.e., a schedule of time intervals (e.g., weekdays and weekends) and set point temperatures or temperature selections for each time interval, stored in the VSCU unit and corresponding to some of the most common schedule paradigms, e.g., household life categories or business categories. Examples of the setup interview are discussed below.
According to some embodiments, the initial setup interview includes the following interactive questioning flow. The VSCU unit display format will look similar to
According to some embodiments, the user's responses to the questions at the initial setup interview are used to automatically “snap” that household onto one of a plurality of pre-existing template schedules, i.e., a schedule of time intervals and set point temperatures for each time interval, stored in the VSCU unit and corresponding to some of the most common household or business schedule paradigms. Examples of different household schedule paradigms, each of which can correspond to a pre-existing HVAC schedule or template schedule, can include: working couple without kids; working couple with infants or young children; working family; working spouse with stay-at-home spouse; young people with active nightlife who work freelance from home; retired couple; and solo retiree. Examples of different business schedule paradigms, each of which can have its own pre-existing HVAC schedule or template schedule, can include: office buildings, businesses open only on the weekdays and daycare center. The template schedules to which the household is “snapped” at system initialization based on the setup interview (or at some other time upon user request) serve as convenient starting points for the operational control of the HVAC system for a large number of installations. The users can then modify their template schedules (e.g., using the user on the VSCU unit itself, the web interface, or smart phone interface, etc.) to suit their individual desires. The VSCU units may also modify these template schedules automatically based on automated schedule learning, i.e., learned occupancy patterns and manual user temperature control setting patterns. By way of nonlimiting example, a typical HVAC schedule or template schedule for a working family would be, for heating in wintertime “Mo Tu We Th Fr: [7:00 68] [9:00 62] [16:00 68] [22:00 62] Sa Su [7:00 68] [22:00 62]” (meaning that, for all five weekdays the set point temperatures will be 68 degrees from 7 AM-9 AM, then 62 degrees from 9 AM-4 PM, then 68 degrees from 4 PM-10 PM, then 62 degrees from 10 PM-7 AM, and that for both weekend days the set point temperatures will be 68 degrees from 7 AM-10 PM, then 62 degrees from 10 PM-7 AM), and for cooling in summertime, “Mo Tu We Th Fr: [7:00 75] [9:00 82] [16:00 78] [22:00 75] Sa Su [7:00 75] [9:00 78] [22:00 75].” In other embodiments, permissible swing temperature amounts, humidity ranges, and so forth can also be included in the template schedules.
According to some embodiments, the ZIP code of the household or business is asked at a point near the beginning of the setup interview, and then different setup interview questions can be asked that are pre-customized for different geographical regions based on the ZIP code. This is useful because the best set of interview questions for Alaskan homes or businesses, for example, will likely be different than the best set of interview questions for Floridian homes, for example.
The setup interview may include one or more closed-end questions, as described above, or open-ended questions. Specific embodiments of steps and features related to the setup interview are shown in the following figures.
Alternatively, a schedule interface may be web-based. An example of a web-based schedule interface is shown in the following figures.
Input options and input corresponding to responses to the input options may be generated and received, respectively, at browser 1200 of an internet-enabled device, e.g., desktop computers and notebook computers. Similarly, as shown in
VSCU unit 100, the devices of the web based interfaces of
At step 1305, input may be received corresponding to responses to the input options of 1305. For example, a user may provide manual input (e.g., input as described with regard to
At decision step 1310, if the received input does not correspond to a pre-existing schedule paradigm, then step 1315 is the next step of method 1300. That is, a null HVAC schedule may be selected at step 1315 if the received input does not correspond to a pre-existing schedule paradigm (e.g., schedule paradigms enumerated herein). The received input may not correspond to a pre-existing schedule paradigm for a number of reasons, e.g., the environment in which the thermostat is implemented is not common or the received inputs were not representative of the environment in which the thermostat is implemented. The null HVAC schedule may be one of the pre-existing HVAC schedules stored on the thermostat or on a server accessible by the thermostat. The null HVAC schedule may be a very common HVAC schedule such that it would a good starting point schedule regardless of the particulars of the environment in which the thermostat, e.g., VSCU unit 100, is implemented.
At decision step 1310, if the received input does correspond to a pre-existing schedule paradigm, then step 1320 is the next step of method 1300. At step 1320, an HVAC schedule is selected from the pre-existing HVAC schedules based on the input received at step 1305. For example, as discussed above, the received inputs may correspond to a schedule paradigm that corresponds to one of the pre-existing HVAC schedules. Thus, the received inputs may correspond to a pre-existing HVAC schedule that may be selected at step 1320. Examples of schedule paradigms and HVAC schedules are discussed above. Following step 1315 or step 1320, depending on step 1310, method 1300 may proceed to step 1325.
At step 1325, the thermostat may be associated with the HVAC schedule selected at step 1320 or 1315. That is, the selected HVAC schedule may be run or initiated on the thermostat. In some cases, a user may be given the option to confirm the selection of the HVAC schedule selected at step 1320 or 1315. The user or a server may also modify the selected HVAC schedule before it is initiated on the thermostat. For example, individual temperature selections may be modified, deleted or added to the selected HVAC schedule before it is initiated.
The HVAC schedule selected at step 1320 or 1315 may also be modified after the HVAC schedule is initiated at step 1325. An example of how the selected schedule may be updated is discussed in the following section.
(B) Using Automated Schedule Learning to Update a Pre-Existing HVAC Schedule Selected Based on a Setup Interview
An implementation of automated schedule learning, as described above, may be included in the aforementioned VSCU unit 100. For example, VSCU unit 100 may include intelligent features that learn about users, beginning with a setup dialog (e.g., the setup interview as mentioned above) in which the user answers a few simple questions, and then continuing, over time, using multi-sensor technology to detect user occupancy patterns and to track the way the user controls the temperature using schedule changes and immediate-temperature control selections or inputs.
At a step 1330, input is received corresponding to template control selections. Temperature control selections or setpoints may be manually provided by a user at a control interface. Similar to the schedule interface discussed above, the control interface may be a web-based interface or provided at a display of the thermostat. The temperature control selections may be made at the control interface, e.g., the interface described with respect to
At a step 1340, an updated HVAC schedule may be generated based on the HVAC schedule selected at step 1320 or 1315 and temperature control selections receiving during step 1330. Generating the updated HVAC schedule may include a number of subs-steps and may be characterized by different learning phases. For example, generating may include the following sub-steps: processing, replicating, overlaying, mutually filtering, clustering, harmonizing, comparing, and establishing. These subsets are further explained and variations thereof are provided in the paragraphs above corresponding to
At step 1350, the thermostat may be associated with the updated HVAC schedule generated at step 1340. That is, the updated HVAC schedule may be run or initiated on the thermostat. In some cases, a user may be given the option to confirm the selection of the HVAC schedule generated at step 1340. The user or a server may modify the updated HVAC schedule before it is initiated on the thermostat. For example, individual temperature selections may be modified, deleted or added to the updated HVAC schedule before it is initiated.
Although method 1300 of
(C) Selecting HVAC Schedules Shared on a Social Networking Service
Thermostats, e.g., VSCU unit 100, may include wired and wireless network connectivity as previously mentioned above. This network connectivity can be used to connect to third party social networking services, third-party on-line gaming services, and other on-line services. These services may serve as a forum for sharing and downloading HVAC schedules for a thermostat, e.g., VSCU unit 100. Examples of features and capabilities of embodiments of VSCU unit 100 are described in the following paragraphs.
The embodiments described herein are 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 1402 of
Thermostat access client 1416 is a client application designed in accordance with aspects of the present invention to access the thermostat management system 1406 over public network 1404. 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 1416 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 1416 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 thermostat management system 1406. 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 thermostat management system 1406, the thermostat access client 1414, 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 1416 may be a stand-alone application or “app” designed to be downloaded and run on a specific device such as smartphone 1408 or a tablet 1410 device running the Apple iOS operating system, Android operating system, or others. Developers create these stand-alone applications using a set of application programming interfaces (APIs) and libraries provided by the device manufacturer packaged in software development toolkit or SDK. Once completed, the “app” is made available for download to the respective device through an application store or “app” store curated by the app store owners to promote quality, usability and customer satisfaction.
In one embodiment, thermostat management system 1406 illustrated in
VSCU unit 100 and remote VSCU unit 112 may be accessed remotely from numerous different locations on the private network 1402 or public network 1404. As will be described in further detail hereinbelow, upon installation a thermostat such as VSCU unit 100 first registers with the thermostat management system 1406 and then requests the thermostat management system create a pairing between the thermostat and a corresponding thermostat management account. Thereafter, a device such as a tablet 1418 may be connected to public network 4604 directly or through a series of other private networks (not shown) yet still access these thermostats, while outside the private network where they are located, by way of thermostat management system 506. In one embodiment, a tablet 1418 running the Apple iOS operating system may remotely access to these thermostats through the thermostat management system 1406 and thermostat management account using an iOS “app” version of thermostat access client 1416. Pairing thermostats with the thermostat management account allows tablet 1418 and other computer devices to remotely control, gather data, and generally interact with thermostats such as VSCU unit 100 and remote VSCU unit 112.
In one embodiment, thermostat management system 1406 distributes the task of communication and control with the thermostats to one or more thermostat management servers 1420. These thermostat management servers 1420 may coordinate communication, manage access, process data and analyze results using data produced by thermostats such as VSCU unit 100 and remote VSCU unit 112. Intermediate and final results from computations on these servers 1420, as well as raw data, may be stored temporarily or archived on thermostat databases 1422 for future reference and use. Thermostat management servers 1420 may also send a portion of the data along with control information, and more generally any of a variety of different kinds of information, back to VSCU unit 100 and remote VSCU unit 112. Results from the thermostat management servers 1420 may also be stored in one or more thermostat databases 1422 for subsequent access by a device such as tablet 1418 running thermostat access client 1416.
These thermostat management servers 1420 each may perform one or several discrete functions, may serve as redundant fail-over servers for these different discrete functions or may share performance of certain discrete functions in tandem or in a cluster as well as other combinations performing more complex operations in parallel or distributed over one or more clusters of computers. In some embodiments, one of the thermostat management servers 1420 may correspond directly to a physical computer or computing device while in other embodiments, the thermostat management servers 1420 may be virtualized servers running on one or more physical computers under the control of a virtual machine computing environment such as provided by VMWARE of Palo Alto, Calif. or any other virtual machine provider. In yet another embodiment, the thermostat management servers 1420 and thermostat databases 1422 are provisioned from a “cloud” computing and storage environment such as the Elastic Compute Cloud or EC2 offering from Amazon.com of Seattle, Wash. In an EC2 solution, for example, the thermostat management servers 1420 may be allocated according to processor cycles and storage requirements rather than according to a number of computers, either real or virtual, thought to be required for the task at hand.
Also shown connected to the public network 1404 is a third party social networking service 1480, a third-party on-line gaming service 1490, and a utility company 1495. Social networking service 1480 is an online service, platform, or site such as Facebook and Twitter that focuses on building and reflecting of social networks or social relations among people, who, for example, share interests and/or activities. The social network services are web-based and thereby provide means for users to interact over the Internet, such as e-mail and instant messaging. The service 1480 allows users to share ideas, activities, events, and interests. Preferably, the social networking service 1480 contains category places (such as former school year or classmates), means to connect with friends (usually with self-description pages), and a recommendation system linked to trust. Besides Facebook and Twitter which are used worldwide, other examples of service 1480 include, Nexopia, Bebo, VKontakte, HiS, Hyves, Draugiem.lv, StudiVZ, iWiW, Tuenti, Nasza-Klasa, Decayenne, Tagged, XING, Badoo, Skyrock, Orkut, Mixi, Multiply, Wretch, renren, Cyworld, LinkedIn and Google+. Social network service 1480, according to some embodiments, allows the users to share and review various settings, features and algorithms that pertain to the thermostats. According to some embodiment the users can compete with each as a means of encouraging energy-savings behavior.
On-line gaming service 1490 are site(s), server(s), and/or service(s) that provide or facilitate video game play. In general on-line games can range from simple text based games to games incorporating complex graphics and virtual worlds populated by many players simultaneously. Many on-line games have associated online communities, making on-line games a form of social activity beyond single player games.
Examples of types of video games that can be facilitated using service 1490 include one or more of the following games and/or series of games: action games, such as shooter games, first-person shooter games (e.g. Doom, Team Fortress, Halo, Killzone, Metroid Prime, Unreal Tournament, Call of Duty, and TimeSplitters), third-person shooter games, massively multiplayer online games (e.g. Happy Farm, World of Warcraft, Final Fantasy), and fighting games; adventure games; action-adventure games (Assassin's Creed); role-playing games (Pokémon, Final Fantasy and Dragon Quest), simulation games (e.g. The Sims, Alter Ego, Animal Crossing, Harvest Moon, Jones in the Fast Lane, Little Computer People, Miami Nights: Singles in the City, Shin Megami Tensei: Persona, Singles: Flirt Up Your Life, and Tokimeki Memorial); social simulation games (e.g. FrontierVille, CityVille, Gardens of Time, FarmVille and The Sims Social); strategy games (e.g. Civilization, Heroes of Might and Magic, Panzer General, Age of Wonders); on-line collectable card games (e.g. Magic: The Gathering Online, Alteil, Astral Masters and Astral Tournament) music games (e.g. Guitar Hero, Audition Online, and X-Beat); dance games (e.g. Dance Dance Revolution); party games; puzzle games; sports games (e.g. FIFA, NBA Live, Madden Football, NHL, and Tiger Woods); racing games (e.g. Forza, Gran Turismo, and Mario Kart); trivia games; video games directed to different target age groups ranging from games intended for children, to games intended for teens, to games intended for adults; and educational games.
According to some embodiments, incentives and/or rewards can be awarded to users to provide encouragement to adopt energy-saving behaviors, as facilitated by the network-connected thermostat and associated home energy network platform as described herein. Examples of incentives and/or rewards include: points, credits, lives, money (e.g. coins or cash), status, cheat codes, unlock codes, hit or health points, experience points or levels, gifts, games items (such as weapons, buildings, farm animals, and cars), decorations, game players (e.g. draft picks) or allies, and game-related merchandise (such as souvenirs, clothing, toys, license plate covers, and action figures).
In some embodiments, the thermostat management servers 1420 making up this thermostat management system 1406 may manage thermostats located in multiple enclosures across various geographic locations and time zones. Each enclosure may use one or several thermostats in accordance with embodiments of the present invention to control one or several HVAC systems, such as HVAC system 120 in
One embodiment of registration server 1502 provides a number of services related to registering a thermostat on the thermostat management system 1406 and preparing it for pairing with a thermostat management account. In operation, the registration server 1502 may be first accessed by a thermostat when the thermostat is wired to the HVAC of an enclosure and then connected to the Internet through a private network. To make the thermostat known on system 1420, the thermostat sends thermostat metadata from the private network to the public network, such as the Internet, and then onto processing by registration server 1502. Preferably, the thermostat metadata includes a unique thermostat identifier, such as one that is assigned at the time of manufacturing. As the communication that sends the thermostat metadata passes through the network address translator (NAT) of the router (not shown) that serves the associated private network (1402, 1432, 1462), it is appended with the public network address of that router, which is thus the public address that is “used” by the thermostat to communicate over the public network. The thermostat identifier is used to identify the thermostat from other thermostats being registered by registration server 1502 and may be based, in part or in whole, on a media access control (MAC) address assigned to the NIC of the thermostat. As one security measure against registering unauthorized devices, registration server 1502 may compare the MAC address in the thermostat metadata against a list of valid MAC addresses provided by the manufacturer of the thermostat or NIC component. In accordance with one embodiment, the thermostat registration is complete when the registration server 1502 provisions an entry in a thermostat registration pool and marks the thermostat entry ready to be paired with a thermostat management account. Entries in the thermostat registration pool may be referenced by their unique thermostat identifier, the public network address that they used (or, more particularly, the public address of the private network router through which they connect to the Internet), and optionally other relevant metadata associated with the thermostat.
In some embodiments, update server 1504 attempts to update software, firmware and configuration updates to each of the thermostats registered in the thermostat registration pool. If metadata from entries in the registration pool exclude versioning information, update server may need to further query each thermostat for current versions installed. Update server 1504 may access entries in the registration pool and then use corresponding network addresses in each entry to connect to the associated thermostat over the public network or private network, or both.
If newer software versions exist than currently used on a thermostat, update server 1504 proceeds to send software updates to the thermostat over the public network. For example, update server may use file transfer protocols such as ftp (file transfer protocol), tftp (trivial file transfer protocol) or more secure transfer protocols when uploading the new software. Once uploaded, installation and update of the software on the thermostat may occur immediately through an auto-update option on the thermostat or manually through the interface of the thermostat as requested by a user.
One embodiment of pairing server 1506 facilitates the association or “pairing” of a thermostat with a thermostat management account on thermostat management account server 1512. The term “thermostat management account” can be used interchangeably with “user account” herein unless specified otherwise. Once the thermostat is paired with a user account, a rich variety of network-enabled capabilities are enabled as described further herein and in one or more of the commonly assigned incorporated applications, supra. For example, once pairing has been achieved, a person with access to the thermostat management account may access the thermostat (through the thermostat management system 1406 using the thermostat access client 1416) for a variety of purposes such as seeing the current temperature of the home, changing the current setpoint, changing the mode of the thermostat between “home” and “away”, and so forth. Moreover, the thermostat management system 1406 can then start tracking the various information provided by the thermostat which, in turn, enables a rich variety of cloud-based data aggregation and analysis that can be used to provide relevant reports, summaries, updates, and recommendations to the user either through the thermostat display itself, through the thermostat access client 1416, or both. A variety of other capabilities, such as demand-response actions in which the thermostat management server sends an energy alert and/or sends energy-saving setpoint commands to the thermostats of users who have enrolled in such programs, can be carried out.
In view of the importance of establishing a pairing between the thermostat and a thermostat management account, there is provided an ability for a fallback method of pairing, which can be termed a “manually assisted” method of pairing, that can take effect and be carried out in the event that the convenient auto-pairing methods described further hereinbelow cannot be securely and reliably carried out for a particular installation. The manually assisted method may use an alphanumeric “passcode” to pair the thermostat to the thermostat management account. Typically, the passcode is sent to the thermostat over a public network, like the Internet, and displayed on the display area of the thermostat. Authorization to access the thermostat is provided if the user obtaining the passcode from the display on the thermostat then enters it into a pairing dialog presented when the user logs into their thermostat management account. Pairing server 1506 pairs the thermostat with the user's thermostat management account if the user enters that same passcode that was displayed on their thermostat display.
According to a preferred “auto-pairing” method, the pairing server 1506 may automatically pair or “auto-pair” a thermostat management account to a thermostat if both are located on the same private network. If the thermostat and thermostat management account are associated with the same private network, embodiments of the present invention presume the thermostat is at the user's home, office, or other area where the user should also have control of the device. To make this determination automatically, the pairing server 1506 compares the public network address that was used to register the thermostat over the Internet with the public network address used by the computer device that has most recently been used to access the thermostat management account. Since the thermostat and computer device only have private network addresses, the router on the private network they share inserts the same public network address into their packets thus allowing the two devices to access servers, services, and other devices on the Internet. “Auto-pairing” takes advantage of this fact and automatically pairs devices sharing the same public network address. This is particularly advantageous from a user standpoint in that the user is not bothered with the need to enter a passcode or other alphanumerical identifier in order to achieve the pairing process, and avoids the concern that a user may inadvertently enter incorrect codes or identifiers into the system. Details on auto-pairing and manually assisted pairing are described in further detail later herein.
Thermostat front end user-interface (UI) server 1508 facilitates the generation and presentation of intuitive, user-friendly graphical user-interfaces that allow users to remotely access, configure, interact with, and control one or more of their network-connected thermostats 100/112 from a computer web browser, smartphone, tablet, or other computing device. The user-friendly graphical user-interfaces can also provide useful tools and interfaces that do not necessarily require real-time connectivity with the thermostats 100/112 with examples including, for some embodiments, providing user interfaces for displaying historical energy usage, historical sensor readings and/or occupancy patterns, allowing the user to learn about and/or enroll in demand-response programs, provide social networking forums that allow users to interact with each other in informative, competitive, fun ways that promote energy savings, provide access to local information including weather, public safety information, neighborhood calendar events, and local blogs, and more generally provide services and information associated with a comprehensive “energy portal” functionality. Examples of intuitive, user-friendly graphical user-interfaces provided by the UI server 1508 according to one or more preferred embodiments are described further in co-pending U.S. patent application Ser. No. 13/317,423.
In some embodiments, a thermostat access client user-interface displays an image of a house representing a primary enclosure paired to the thermostat management account in the thermostat management system. Thermostat front end UI server 1508 may further instruct the thermostat access client, such as thermostat access client 1416 in
Thermostat backend server 1510 manages the storage of data used by various thermostat management servers in the thermostat management system 1406. In some embodiments, thermostat backend server 1510 may manage storage of the thermostat registration pool data used by the registration server 1502 or may organize and store new software updates and releases for the update server 1504. In another embodiment, thermostat backend server 1510 may also store heating and cooling related data (i.e., date and time HVAC system was in either heating or cooling mode within the enclosure), sensor information, battery-level data, alarms, etc. associated with an enclosure that was sent to the thermostat management system 1406 by thermostats registered therewith, and in some embodiments and provide pre-computed heating and cooling schedules, applications, and other data for download over the public network for use by the thermostats.
In some embodiments, thermostat management account server 1512 is used to create new accounts and update existing accounts on thermostat management system 1406. To access their thermostat over a thermostat access client 1416 and enjoy the benefits of thermostat connectedness, the user is first required to create of a thermostat management account (“user account”) on thermostat management account server 1512 using their thermostat access client 1416. Accordingly, users execute the thermostat access client 1416 on a computer or other computer device to access the thermostat management account server 612. The thermostat management account server 1512 should receive at least the zip code and/or city and state for the enclosure in which the thermostat is (or will be) installed, such that weather information provided by a weather service can be accessed and downloaded to the thermostat, which can be used as part of its optimal enclosure characterization and HVAC control algorithms. Optionally, a variety of other information including a user's contact information, enclosure street addresses, and so forth can also be received. Primary options associated with the thermostat management account server 1512 include pairing one or more thermostats to the correct thermostat management account through pairing operations provided by pairing server 1506. However, even if the account is not yet paired with a thermostat, the user may use the thermostat management account to access local information including weather, public safety information, neighborhood calendar events, local blogs and more information based upon the user's contact information, locale and other interests.
According to some embodiments, one or more of the household systems or devices connected or linked to VSCU unit 100 are compatible under license or other business arrangement with the thermostat unit manufacturer and/or thermostat data service provider. According to some embodiments, the VSCU unit 100 functional as central “energy hub” for the whole house. Especially for a residential context, it has been found that VSCU unit 100 is an advantageous way to instantiate such a “home energy network,” at least because virtually all homes need to have a thermostat anyway. Once the VSCU unit 100 is installed (by replacement of an old thermostat, as part of new construction, etc.) and connected or paired (such as via local network 1402, public network 1404 and/or thermostat management system 1406 shown in
According to some embodiments, VSCU unit 100 is used in connection with video game console 1464 and/or computer 1414 to encourage adoption of energy-efficient behavior through the use of competition, game-related incentive or rewards, and/or exchange of thermostat-related settings or algorithms with other users.
As mentioned above, social network service 1480, according to some embodiments, may allow users to share and review various settings, features and algorithms that pertain to the thermostats. Social network service 1480 may also allow users to share HVAC schedules generated at a thermostat or elsewhere. On-line gaming service 1490 and other online forums or services may also allow users to share HVAC schedules.
Thermostat access client 1416 may access a thermostat management account (not illustrated) provisioned by thermostat management system 1406, on behalf of devices, in order to associate a pre-existing shared HVAC schedules with a VSCU unit 100. As mentioned above, thermostat access client 1416 may be a stand-alone application or “app” designed to be downloaded and run on a specific device such as smartphone 1408 or a tablet 1410 device running the Apple iOS operating system, Android operating system, or others. Thermostat access client 1416 may also be 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 thermostat management system 1406 and the thermostat management account. The app or the browser may be used to access a social networking service 1480 or other online services to download shared HVAC schedules and the thermostat access client 1416 may be used to select the downloaded shared HVAC schedule and associate the selected HVAC schedule with the thermostat management account and ultimately the VSCU unit 100.
In some embodiments, a shared HVAC schedule may be downloaded based upon a setup interview, similar to the setup interview discussed in the paragraphs corresponding to
In other embodiments, a shared HVAC schedule may be downloaded based upon efficiency metrics corresponding to the shared HVAC schedules. For example, stand-alone performance metrics (SPM) and other metrics, which may be generated as part of a competition or otherwise, result in metrics related the HVAC schedules shared by the user and even the user themselves. Examples of the how to calculate metrics and the ecosystem for generating metric sharing communities are described in the following figures.
According to some embodiments, an SPM is based only on the percentage of time that their HVAC system is cycled on (“on-time percentage” or “OTP”), wherein the performance metric is higher (better) when the on-time percentage is lower. For other embodiments, the user's energy-saving performance is measured only by virtue of physical parameters that can be sensed or governed by the thermostats themselves in combination with weather information that can be readily accessed based on the user's geographical information, such as ZIP code. For these embodiments, the standalone performance metric preferably is modified to take into account the outside weather, such as the outside temperature.
In one example, for a heating scenario, the SPM “M” can have the formula:
where OTP[T>50° F.] is the on-time percentage when the outside temperature is greater than 50 F, and OTP[30° F.<T≤50° F.] is the on-time percentage when the outside temperature is between 30 F-50 F, and so forth.
According to some other embodiments, the performance metrics can be more complex, including both HVAC performance and other energy performance metrics, such as can be acquired from homes with smart meters connected to the cloud.
In addition to the efficiency metrics described in relation to
In some embodiments, the thermostat management account will allow user search for shared HVAC schedules on a social network service based on a corresponding metric score, or any other information relevant to selecting a shared HVAC schedule.
Specific embodiments of steps and features related to downloading HVAC schedules from social networking services are shown in the following figures.
At step 1910, the thermostat may be associated with the pre-existing HVAC schedule selected at step 1905. That is, the selected HVAC schedule may be run or initiated on the thermostat of VSCU unit. The user or a server may modify the selected pre-existing HVAC schedule before it is initiated on the thermostat. For example, individual temperature selections may be modified, deleted or added to the selected HVAC schedule before it is initiated.
The selected pre-existing HVAC schedule may also be modified after the HVAC schedule is initiated at step 1900. An example of how the selected schedule may be updated is discussed in the following section.
(D) Using Automated Schedule Learning to Update a Selected HVAC Schedule that was Shared on a Social Networking Service
As mentioned previously, an implementation of automated schedule learning, as described above, may be included with the aforementioned VSCU unit 100. For example, VSCU unit 100 may include intelligent features that learn about the users over time, using multi-sensor technology to detect user occupancy patterns and to track the way the user controls the temperature using schedule changes and immediate-temperature control selections or inputs.
At a step 1920, input is received corresponding to template control selections. The temperature control selections may be provided at the control interface, e.g., as described with respect to
At a step 1930, an updated HVAC schedule may be generated based on the pre-existing HVAC schedule selected at step 1905 and temperature control selections receiving during step 1920. Generating the updated HVAC schedule may include a number of subs-steps and may be characterized by different learning phases. For example, generating may include the following sub-steps: processing, replicating, overlaying, mutually filtering, clustering, harmonizing, comparing, and establishing. These subsets are further explained and variations thereof are provided in the paragraphs above corresponding to
At step 1940, the thermostat may be associated with the updated HVAC schedule generated at step 1930. That is, the updated HVAC schedule may be run or initiated on the thermostat. In some cases, a user may be given the option to confirm the selection of the HVAC schedule generated at step 1930. The user or a server may modify the updated HVAC schedule before it is initiated on the thermostat. For example, individual temperature selections may be modified, deleted or added to the updated HVAC schedule before it is initiated.
Although method 1900 of
The updated HVAC schedules generated at steps 1930 and 1340 above can be shared, similar to the way iTunes music playlists can be shared, optionally in a social networking context. For example, updated schedules can be shared on Facebook or MySpace or any other of the social networking services and online gaming services enumerated above. These updated schedules can be selected and initiated on other thermostats according to steps 1905 and 1910 above. Social network service 1480, according to some embodiments, may allow the users to review shared HVAC schedules. According to some embodiment the users can compete with each to receive the best reviews as a means of encouraging energy-savings behavior.
Another example of sharing updated HVAC schedules is shown in the following figure.
The sharing of settings and algorithms may be particularly useful among members of a specific demographic. For example, swing/non-standard shift workers may benefit from adopting a program setpoint schedule that more accurately reflects their occupancy and sleep patterns. In another example, swing/non-standard shift workers may benefit from occupancy algorithms that are more sensitive to occupancy detection during the nighttime. An example of such an algorithm may include decreasing the number of consecutive buckets of PIR sensor activity needed to activate an auto-away and/or auto arrival. For further details of thermostat sensing systems, see co-pending International Patent Application No. PCT/US11/61479, supra. For further details of auto-away and auto-arrival algorithms, see co-pending International Patent Application No. PCT/US11/61437, supra. Another example of types of algorithms that might be shared among thermostat owners relates to detection of the activity of household pets. In some cases, for example in mild climates it may be useful for the auto-away and auto-arrival algorithms to ignore the detection of pets, while in more extreme climates it may be useful not to ignore pets. Certain settings and/or algorithms may further be suited to households with large or small pets, for example settings relating to the PIR sensor angle of sensitivity may be set differently to ignore or detect occupancy and/or activity of certain sizes of pets. In another example, a first user may post a particular algorithm or setting for review by others. Other thermostat users may review the efficacy of algorithm or setting or even suggest changes. Yet other thermostat users may decide to adopt the posted algorithm or setting depending on such reviews.
In step 2010, a first user refines settings and/or algorithms in his or her thermostat. In step 2012, the first user uploads the settings and/or algorithms to a database, such as database 1422 shown in
Various modifications may be made without departing from the spirit and scope of the invention. Indeed, various user interfaces for operating thermostats, HVACSs and other devices have been provided yet the designs are meant to be illustrative and not limiting as to the scope of the overall invention. While methods and systems have been described for establishing HVAC schedules, it is contemplated that these methods may be applied to any to other schedules, e.g., watering schedules, indoor/outdoor lighting schedules, and security schedules. It is to be further 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. According to some embodiments, one or more of the above teachings is advantageously combined with one or more teachings of one or more of the following commonly assigned applications, each of which is incorporated by reference herein: International Application No. PCT/US12/00007 filed Jan. 3, 2012 (Ref. No. NES0190-PCT); U.S. Ser. No. 13/434,560 filed Mar. 29, 2012 (Ref. No. NES0212-US); and U.S. Ser. No. 13/624,875 filed Sep. 21, 2012 (Ref. No. NES0245-US). 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 Ser. No. 13/842,048 filed Mar. 15, 2013, which is a continuation-in-part of the following commonly assigned applications: U.S. application Ser. No. 13/632,041 filed Sep. 30, 2012; PCT/US2012/20026 filed Jan. 3, 2012; and U.S. application Ser. No. 13/269,501 filed Oct. 7, 2011. U.S. application Ser. No. 13/632,041 claims the benefit of U.S. Provisional Application No. 61/550,346 filed Oct. 21, 2011. International Application No. PCT/US2012/20026 claims the benefit of International Application No. PCT/US11/61437 filed Nov. 18, 2011, U.S. Ser. No. 13/317,423 filed Oct. 17, 2011, and U.S. Prov. Ser. No. 61/429,093 filed Dec. 31, 2010. U.S. application Ser. No. 13/269,501 is a continuation-in-part of U.S. application Ser. No. 13/033,573 filed Feb. 23, 2011 and furthermore claims the benefit of U.S. U.S. Prov. Ser. No. 61/429,093 and U.S. Prov. Ser. No. 61/415,771 filed Nov. 19, 2010. Each of the above-referenced applications is incorporated by reference herein. The above-referenced patent applications are collectively referenced herein below as “the commonly assigned incorporated applications.”
| Number | Name | Date | Kind |
|---|---|---|---|
| 2558648 | Warner | Jun 1951 | A |
| 3991357 | Kaminski | Nov 1976 | A |
| 4183290 | Kucharczyk | Jan 1980 | A |
| 4223831 | Szarka | Sep 1980 | A |
| 4316577 | Adams et al. | Feb 1982 | A |
| 4335847 | Levine | Jun 1982 | A |
| 4408711 | Levine | Oct 1983 | A |
| 4460125 | Barker et al. | Jul 1984 | A |
| 4613139 | Robinson, II et al. | Sep 1986 | A |
| 4615380 | Beckey | Oct 1986 | A |
| 4621336 | Brown | Nov 1986 | A |
| 4669654 | Levine et al. | Jun 1987 | A |
| 4674027 | Beckey | Jun 1987 | A |
| 4685614 | Levine | Aug 1987 | A |
| 4741476 | Russo et al. | May 1988 | A |
| 4751961 | Levine et al. | Jun 1988 | A |
| 4768706 | Parfitt | Sep 1988 | A |
| 4847781 | Brown et al. | Jul 1989 | A |
| 4897798 | Cler | Jan 1990 | A |
| 4971136 | Mathur et al. | Nov 1990 | A |
| 4997029 | Otsuka et al. | Mar 1991 | A |
| 5005365 | Lynch | Apr 1991 | A |
| D321903 | Chepaitis | Nov 1991 | S |
| 5065813 | Berkeley et al. | Nov 1991 | A |
| 5088645 | Bell | Feb 1992 | A |
| 5115967 | Wedekind | May 1992 | A |
| 5211332 | Adams | May 1993 | A |
| 5224648 | Simon et al. | Jul 1993 | A |
| 5224649 | Brown et al. | Jul 1993 | A |
| 5240178 | Dewolf et al. | Aug 1993 | A |
| 5244146 | Jefferson et al. | Sep 1993 | A |
| D341848 | Bigelow et al. | Nov 1993 | S |
| 5294047 | Schwer et al. | Mar 1994 | A |
| 5303612 | Odom et al. | Apr 1994 | A |
| 5395042 | Riley et al. | Mar 1995 | A |
| 5415346 | Bishop | May 1995 | A |
| 5460327 | Hill et al. | Oct 1995 | A |
| 5462225 | Massara et al. | Oct 1995 | A |
| 5476221 | Seymour | Dec 1995 | A |
| 5482209 | Cochran et al. | Jan 1996 | A |
| 5485954 | Guy et al. | Jan 1996 | A |
| 5499196 | Pacheco | Mar 1996 | A |
| 5499330 | Lucas et al. | Mar 1996 | A |
| 5544036 | Brown, Jr. et al. | Aug 1996 | A |
| 5555927 | Shah | Sep 1996 | A |
| 5603451 | Helander et al. | Feb 1997 | A |
| 5611484 | Uhrich | Mar 1997 | A |
| 5627531 | Posso et al. | May 1997 | A |
| 5673850 | Uptegraph | Oct 1997 | A |
| 5690277 | Flood | Nov 1997 | A |
| 5761083 | Brown, Jr. et al. | Jun 1998 | A |
| D396488 | Kunkler | Jul 1998 | S |
| 5779143 | Michaud et al. | Jul 1998 | A |
| 5782296 | Mehta | Jul 1998 | A |
| 5808294 | Neumann | Sep 1998 | A |
| 5808602 | Sellers | Sep 1998 | A |
| 5816491 | Berkeley et al. | Oct 1998 | A |
| 5819840 | Wilson | Oct 1998 | A |
| 5902183 | D'Souza | May 1999 | A |
| 5909378 | De Milleville | Jun 1999 | A |
| 5918474 | Khanpara et al. | Jul 1999 | A |
| 5924486 | Ehlers et al. | Jul 1999 | A |
| 5931378 | Schramm | Aug 1999 | A |
| 5959621 | Nawaz et al. | Sep 1999 | A |
| 5973662 | Singers et al. | Oct 1999 | A |
| 5977964 | Williams et al. | Nov 1999 | A |
| 6020881 | Naughton et al. | Feb 2000 | A |
| 6032867 | Dushane et al. | Mar 2000 | A |
| 6062482 | Gauthier et al. | May 2000 | A |
| 6066843 | Scheremeta | May 2000 | A |
| 6072784 | Agrawal et al. | Jun 2000 | A |
| D428399 | Kahn et al. | Jul 2000 | S |
| 6093914 | Diekmann et al. | Jul 2000 | A |
| 6095427 | Hoium et al. | Aug 2000 | A |
| 6098893 | Berglund et al. | Aug 2000 | A |
| 6122603 | Budike, Jr. | Sep 2000 | A |
| 6157943 | Meyer | Dec 2000 | A |
| 6164374 | Rhodes et al. | Dec 2000 | A |
| 6206295 | LaCoste | Mar 2001 | B1 |
| 6211921 | Cherian et al. | Apr 2001 | B1 |
| 6213404 | Dushane et al. | Apr 2001 | B1 |
| 6216956 | Ehlers et al. | Apr 2001 | B1 |
| 6285912 | Ellison | Sep 2001 | B1 |
| 6286764 | Garvey et al. | Sep 2001 | B1 |
| 6298285 | Addink et al. | Oct 2001 | B1 |
| 6311105 | Budike, Jr. | Oct 2001 | B1 |
| D450059 | Itou | Nov 2001 | S |
| 6318639 | Toth | Nov 2001 | B1 |
| 6349883 | Simmons et al. | Feb 2002 | B1 |
| 6351693 | Monie et al. | Feb 2002 | B1 |
| 6356204 | Guindi et al. | Mar 2002 | B1 |
| 6359564 | Thacker | Mar 2002 | B1 |
| 6370894 | Thompson et al. | Apr 2002 | B1 |
| 6415205 | Myron et al. | Jul 2002 | B1 |
| 6438241 | Silfvast et al. | Aug 2002 | B1 |
| 6453687 | Sharood et al. | Sep 2002 | B2 |
| D464660 | Weng et al. | Oct 2002 | S |
| 6478233 | Shah | Nov 2002 | B1 |
| 6490174 | Kompelien | Dec 2002 | B1 |
| 6502758 | Cottrell | Jan 2003 | B2 |
| 6513723 | Mueller et al. | Feb 2003 | B1 |
| 6519509 | Nierlich et al. | Feb 2003 | B1 |
| D471825 | Peabody | Mar 2003 | S |
| 6574581 | Bohrer et al. | Jun 2003 | B1 |
| 6595430 | Shah | Jul 2003 | B1 |
| 6619055 | Addy | Sep 2003 | B1 |
| 6622925 | Carner et al. | Sep 2003 | B2 |
| D480401 | Kahn et al. | Oct 2003 | S |
| 6636197 | Goldenberg et al. | Oct 2003 | B1 |
| 6641054 | Morey | Nov 2003 | B2 |
| 6641055 | Tiernan | Nov 2003 | B1 |
| 6643567 | Kolk et al. | Nov 2003 | B2 |
| 6644557 | Jacobs | Nov 2003 | B1 |
| 6645066 | Gutta et al. | Nov 2003 | B2 |
| D485279 | DeCombe | Jan 2004 | S |
| 6726112 | Ho | Apr 2004 | B1 |
| D491956 | Ombao et al. | Jun 2004 | S |
| 6769482 | Wagner et al. | Aug 2004 | B2 |
| 6785630 | Kolk et al. | Aug 2004 | B2 |
| 6798341 | Eckel et al. | Sep 2004 | B1 |
| D497617 | Decombe et al. | Oct 2004 | S |
| 6814299 | Carey | Nov 2004 | B1 |
| 6824069 | Rosen | Nov 2004 | B2 |
| 6851621 | Wacker et al. | Feb 2005 | B1 |
| 6864879 | Nojima et al. | Mar 2005 | B2 |
| 6868293 | Schurr et al. | Mar 2005 | B1 |
| D503631 | Peabody | Apr 2005 | S |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6909921 | Bilger | Jun 2005 | B1 |
| 6951306 | DeLuca | Oct 2005 | B2 |
| D511527 | Hernandez et al. | Nov 2005 | S |
| 6975958 | Bohrer et al. | Dec 2005 | B2 |
| 6990821 | Singh et al. | Jan 2006 | B2 |
| 7000849 | Ashworth et al. | Feb 2006 | B2 |
| 7024336 | Salsbury et al. | Apr 2006 | B2 |
| 7028912 | Rosen | Apr 2006 | B1 |
| 7035805 | Miller | Apr 2006 | B1 |
| 7038667 | Vassallo et al. | May 2006 | B1 |
| 7047092 | Wimsatt | May 2006 | B2 |
| 7055759 | Wacker et al. | Jun 2006 | B2 |
| 7083109 | Pouchak | Aug 2006 | B2 |
| 7108194 | Hankins, II | Sep 2006 | B1 |
| 7109970 | Miller | Sep 2006 | B1 |
| 7111788 | Reponen | Sep 2006 | B2 |
| 7114554 | Bergman | Oct 2006 | B2 |
| 7135965 | Chapman, Jr. et al. | Nov 2006 | B2 |
| 7140551 | de Pauw et al. | Nov 2006 | B2 |
| 7141748 | Tanaka et al. | Nov 2006 | B2 |
| 7142948 | Metz | Nov 2006 | B2 |
| 7149727 | Nicholls et al. | Dec 2006 | B1 |
| 7149729 | Kaasten et al. | Dec 2006 | B2 |
| 7152806 | Rosen | Dec 2006 | B1 |
| 7156318 | Rosen | Jan 2007 | B1 |
| 7159789 | Schwendinger et al. | Jan 2007 | B2 |
| 7159790 | Schwendinger et al. | Jan 2007 | B2 |
| 7181317 | Amundson et al. | Feb 2007 | B2 |
| 7188482 | Sadegh et al. | Mar 2007 | B2 |
| 7222494 | Peterson et al. | May 2007 | B2 |
| 7222800 | Wruck | May 2007 | B2 |
| 7225054 | Amundson et al. | May 2007 | B2 |
| 7225057 | Froman et al. | May 2007 | B2 |
| D544877 | Sasser | Jun 2007 | S |
| 7258280 | Wolfson | Aug 2007 | B2 |
| D550691 | Hally et al. | Sep 2007 | S |
| 7264175 | Schwendinger et al. | Sep 2007 | B2 |
| 7274972 | Amundson et al. | Sep 2007 | B2 |
| 7287709 | Proffitt et al. | Oct 2007 | B2 |
| 7289887 | Rodgers | Oct 2007 | B2 |
| 7299996 | Garrett et al. | Nov 2007 | B2 |
| 7302642 | Smith et al. | Nov 2007 | B2 |
| 7333880 | Brewster et al. | Feb 2008 | B2 |
| 7346467 | Bohrer et al. | Mar 2008 | B2 |
| D566587 | Rosen | Apr 2008 | S |
| 7379791 | Tamarkin et al. | May 2008 | B2 |
| 7379997 | Ehlers et al. | May 2008 | B2 |
| RE40437 | Rosen | Jul 2008 | E |
| 7418663 | Pettinati et al. | Aug 2008 | B2 |
| 7427926 | Sinclair et al. | Sep 2008 | B2 |
| 7434742 | Mueller et al. | Oct 2008 | B2 |
| 7451937 | Flood et al. | Nov 2008 | B2 |
| 7455240 | Chapman, Jr. et al. | Nov 2008 | B2 |
| 7460690 | Cohen et al. | Dec 2008 | B2 |
| 7469550 | Chapman, Jr. et al. | Dec 2008 | B2 |
| D588152 | Okada | Mar 2009 | S |
| 7509753 | Nicosia et al. | Mar 2009 | B2 |
| D589792 | Clabough et al. | Apr 2009 | S |
| D590412 | Saft et al. | Apr 2009 | S |
| D593120 | Bouchard et al. | May 2009 | S |
| 7537171 | Mueller et al. | May 2009 | B2 |
| D594015 | Singh et al. | Jun 2009 | S |
| D595309 | Saski et al. | Jun 2009 | S |
| 7555364 | Poth et al. | Jun 2009 | B2 |
| D596194 | Vu et al. | Jul 2009 | S |
| D597101 | Chaudhri et al. | Jul 2009 | S |
| 7558648 | Hoglund et al. | Jul 2009 | B2 |
| D598463 | Hirsch et al. | Aug 2009 | S |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7571865 | Nicodem et al. | Aug 2009 | B2 |
| 7575179 | Morrow et al. | Aug 2009 | B2 |
| D599806 | Brown et al. | Sep 2009 | S |
| D599810 | Scalisi et al. | Sep 2009 | S |
| 7584899 | de Pauw et al. | Sep 2009 | B2 |
| 7600694 | Helt et al. | Oct 2009 | B2 |
| D603277 | Clausen et al. | Nov 2009 | S |
| D603421 | Ebeling et al. | Nov 2009 | S |
| D604740 | Matheny et al. | Nov 2009 | S |
| 7614567 | Chapman, Jr. et al. | Nov 2009 | B2 |
| 7620996 | Torres et al. | Nov 2009 | B2 |
| D607001 | Ording | Dec 2009 | S |
| 7624931 | Chapman, Jr. et al. | Dec 2009 | B2 |
| 7634504 | Amundson | Dec 2009 | B2 |
| 7641126 | Schultz et al. | Jan 2010 | B2 |
| 7644869 | Hoglund et al. | Jan 2010 | B2 |
| 7667163 | Ashworth et al. | Feb 2010 | B2 |
| D613301 | Lee et al. | Apr 2010 | S |
| D614194 | Guntaur et al. | Apr 2010 | S |
| D614196 | Guntaur et al. | Apr 2010 | S |
| 7693582 | Bergman et al. | Apr 2010 | B2 |
| 7702421 | Sullivan et al. | Apr 2010 | B2 |
| 7703694 | Mueller et al. | Apr 2010 | B2 |
| D614976 | Skafdrup et al. | May 2010 | S |
| D615546 | Lundy et al. | May 2010 | S |
| D616460 | Pearson et al. | May 2010 | S |
| 7721209 | Tilton | May 2010 | B2 |
| 7726581 | Naujok et al. | Jun 2010 | B2 |
| D619613 | Dunn | Jul 2010 | S |
| 7761189 | Froman et al. | Jul 2010 | B2 |
| 7784704 | Harter | Aug 2010 | B2 |
| 7802618 | Simon et al. | Sep 2010 | B2 |
| D625325 | Vu et al. | Oct 2010 | S |
| D625734 | Kurozumi et al. | Oct 2010 | S |
| D626133 | Murphy et al. | Oct 2010 | S |
| 7823076 | Borovsky et al. | Oct 2010 | B2 |
| RE41922 | Gough et al. | Nov 2010 | E |
| 7845576 | Siddaramanna et al. | Dec 2010 | B2 |
| 7848900 | Steinberg et al. | Dec 2010 | B2 |
| 7849698 | Harrod et al. | Dec 2010 | B2 |
| 7854389 | Ahmed | Dec 2010 | B2 |
| 7861179 | Reed | Dec 2010 | B2 |
| D630649 | Tokunaga et al. | Jan 2011 | S |
| 7890195 | Bergman et al. | Feb 2011 | 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 |
| 7913925 | Ashworth | Mar 2011 | B2 |
| 7918406 | Rosen | Apr 2011 | B2 |
| D638835 | Akana et al. | May 2011 | S |
| D640269 | Chen | Jun 2011 | S |
| D640273 | Arnold et al. | Jun 2011 | S |
| D640278 | Woo | Jun 2011 | S |
| D640285 | Woo | Jun 2011 | S |
| 7963454 | Sullivan et al. | Jun 2011 | B2 |
| D641373 | Gardner et al. | Jul 2011 | S |
| 7984384 | Chaudhri et al. | Jul 2011 | B2 |
| D643045 | Woo | Aug 2011 | S |
| 8010237 | Cheung et al. | Aug 2011 | B2 |
| 8019567 | Steinberg et al. | Sep 2011 | B2 |
| 8037022 | Rahman et al. | Oct 2011 | B2 |
| D648735 | Arnold et al. | Nov 2011 | S |
| D651529 | Mongell et al. | Jan 2012 | S |
| 8087593 | Leen | Jan 2012 | B2 |
| 8090477 | Steinberg | Jan 2012 | B1 |
| 8091375 | Crawford | Jan 2012 | B2 |
| 8091794 | Siddaramanna et al. | Jan 2012 | B2 |
| 8091795 | McLellan | Jan 2012 | B1 |
| 8091796 | Amundson et al. | Jan 2012 | B2 |
| 8131207 | Hwang et al. | Mar 2012 | B2 |
| 8131497 | Steinberg et al. | Mar 2012 | B2 |
| 8131506 | Steinberg et al. | Mar 2012 | B2 |
| 8136052 | Shin et al. | Mar 2012 | B2 |
| D656950 | Shallcross et al. | Apr 2012 | S |
| D656952 | Weir et al. | Apr 2012 | S |
| 8156060 | Borzestowski et al. | Apr 2012 | B2 |
| 8166395 | Omi et al. | Apr 2012 | B2 |
| D658674 | Shallcross et al. | May 2012 | S |
| D660732 | Bould et al. | May 2012 | S |
| 8174381 | Imes et al. | May 2012 | B2 |
| 8180492 | Steinberg | May 2012 | B2 |
| 8185164 | Kim | May 2012 | B2 |
| 8195313 | Fadell et al. | Jun 2012 | B1 |
| D663743 | Tanghe et al. | Jul 2012 | S |
| D663744 | Tanghe et al. | Jul 2012 | S |
| D664559 | Ismail et al. | Jul 2012 | S |
| 8219249 | Harrod et al. | Jul 2012 | B2 |
| 8219250 | Dempster et al. | Jul 2012 | B2 |
| 8223134 | Forstall et al. | Jul 2012 | B1 |
| 8234581 | Kake | Jul 2012 | B2 |
| D664978 | Tanghe et al. | Aug 2012 | S |
| D665397 | Naranjo et al. | Aug 2012 | S |
| 8239922 | Sullivan et al. | Aug 2012 | B2 |
| 8243017 | Brodersen et al. | Aug 2012 | B2 |
| 8253704 | Jang | Aug 2012 | B2 |
| 8253747 | Niles et al. | Aug 2012 | B2 |
| 8265798 | Imes | Sep 2012 | B2 |
| 8280536 | Fadell et al. | Oct 2012 | B1 |
| 8281244 | Neuman et al. | Oct 2012 | B2 |
| 8292494 | Rosa et al. | Oct 2012 | B2 |
| D671136 | Barnett et al. | Nov 2012 | S |
| 8316022 | Matsuda et al. | Nov 2012 | B2 |
| D673171 | Peters et al. | Dec 2012 | S |
| D673172 | Peters et al. | Dec 2012 | S |
| 8341557 | Pisula et al. | Dec 2012 | B2 |
| D677180 | Plitkins et al. | Mar 2013 | S |
| 8387891 | Simon et al. | Mar 2013 | B1 |
| 8387892 | Koster et al. | Mar 2013 | B2 |
| 8406816 | Marui et al. | Mar 2013 | B2 |
| 8442693 | Mirza et al. | May 2013 | B2 |
| 8442695 | Imes et al. | May 2013 | B2 |
| 8442752 | Wijaya et al. | May 2013 | B2 |
| 8446381 | Molard et al. | May 2013 | B2 |
| D687046 | Plitkins et al. | Jul 2013 | S |
| 8489243 | Fadell et al. | Jul 2013 | B2 |
| 8527096 | Pavlak et al. | Sep 2013 | B2 |
| 8543243 | Wallaert et al. | Sep 2013 | B2 |
| D691629 | Matas et al. | Oct 2013 | S |
| 8630740 | Matsuoka et al. | Jan 2014 | B2 |
| 8689572 | Evans et al. | Apr 2014 | B2 |
| 8706270 | Fadell et al. | Apr 2014 | B2 |
| 8850478 | Moshiri et al. | Sep 2014 | B2 |
| 8893032 | Bruck et al. | Nov 2014 | B2 |
| 8918219 | Sloo et al. | Dec 2014 | B2 |
| 9223323 | Matas et al. | Dec 2015 | B2 |
| 20010052052 | Peng | Dec 2001 | A1 |
| 20020005435 | Cottrell | Jan 2002 | A1 |
| 20020022991 | Sharood et al. | Feb 2002 | A1 |
| 20020178047 | Or | Nov 2002 | A1 |
| 20030034898 | Shamoon et al. | Feb 2003 | A1 |
| 20030042320 | Decker | Mar 2003 | A1 |
| 20030112262 | Adatia et al. | Jun 2003 | A1 |
| 20030150927 | Rosen | Aug 2003 | A1 |
| 20030231001 | Bruning | Dec 2003 | A1 |
| 20030233432 | Davis et al. | Dec 2003 | A1 |
| 20040015504 | Ahad et al. | Jan 2004 | A1 |
| 20040027271 | Schuster et al. | Feb 2004 | A1 |
| 20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
| 20040055446 | Robbin et al. | Mar 2004 | A1 |
| 20040067731 | Brinkerhoff et al. | Apr 2004 | A1 |
| 20040074978 | Rosen | Apr 2004 | A1 |
| 20040095237 | Chen et al. | May 2004 | A1 |
| 20040107717 | Yoon et al. | Jun 2004 | A1 |
| 20040117330 | Ehlers et al. | Jun 2004 | A1 |
| 20040164238 | Xu et al. | Aug 2004 | A1 |
| 20040249479 | Shorrock | Dec 2004 | A1 |
| 20040256472 | DeLuca | Dec 2004 | A1 |
| 20040260427 | Wimsatt | Dec 2004 | A1 |
| 20040262410 | Hull | Dec 2004 | A1 |
| 20050040247 | Pouchak | Feb 2005 | A1 |
| 20050040250 | Wruck | Feb 2005 | A1 |
| 20050040943 | Winick | Feb 2005 | A1 |
| 20050043907 | Eckel et al. | Feb 2005 | A1 |
| 20050055432 | Rodgers | Mar 2005 | A1 |
| 20050071780 | Muller et al. | Mar 2005 | A1 |
| 20050090915 | Geiwitz | Apr 2005 | A1 |
| 20050091596 | Anthony et al. | Apr 2005 | A1 |
| 20050103875 | Ashworth et al. | May 2005 | A1 |
| 20050119766 | Amundson et al. | Jun 2005 | A1 |
| 20050119793 | Amundson et al. | Jun 2005 | A1 |
| 20050120181 | Arunagirinathan et al. | Jun 2005 | A1 |
| 20050128067 | Zakrewski | Jun 2005 | A1 |
| 20050150968 | Shearer | Jul 2005 | A1 |
| 20050159847 | Shah et al. | Jul 2005 | A1 |
| 20050189429 | Breeden | Sep 2005 | A1 |
| 20050192915 | Ahmed et al. | Sep 2005 | A1 |
| 20050194456 | Tessier et al. | Sep 2005 | A1 |
| 20050195757 | Kidder et al. | Sep 2005 | A1 |
| 20050199737 | De Pauw et al. | Sep 2005 | A1 |
| 20050204997 | Fournier | Sep 2005 | A1 |
| 20050279840 | Schwendinger et al. | Dec 2005 | A1 |
| 20050279841 | Schwendinger et al. | Dec 2005 | A1 |
| 20050280421 | Yomoda et al. | Dec 2005 | A1 |
| 20050287424 | Schwendinger et al. | Dec 2005 | A1 |
| 20060000919 | Schwendinger et al. | Jan 2006 | A1 |
| 20060143236 | Wu | Jun 2006 | A1 |
| 20060147003 | Archacki et al. | Jul 2006 | A1 |
| 20060184284 | Froman et al. | Aug 2006 | A1 |
| 20060186214 | Simon et al. | Aug 2006 | A1 |
| 20060196953 | Simon et al. | Sep 2006 | A1 |
| 20060206220 | Amundson | Sep 2006 | A1 |
| 20060283965 | Mueller et al. | Dec 2006 | A1 |
| 20070001830 | Dagci et al. | Jan 2007 | A1 |
| 20070012793 | Flood et al. | Jan 2007 | A1 |
| 20070043473 | Anderson et al. | Feb 2007 | A1 |
| 20070045430 | Chapman et al. | Mar 2007 | A1 |
| 20070045431 | Chapman et al. | Mar 2007 | A1 |
| 20070045433 | Chapman et al. | Mar 2007 | A1 |
| 20070045444 | Gray et al. | Mar 2007 | A1 |
| 20070050732 | Chapman et al. | Mar 2007 | A1 |
| 20070057079 | Stark et al. | Mar 2007 | A1 |
| 20070084941 | de Pauw et al. | Apr 2007 | A1 |
| 20070114295 | Jenkins | May 2007 | A1 |
| 20070115902 | Shamoon et al. | May 2007 | A1 |
| 20070120856 | De Ruyter et al. | May 2007 | A1 |
| 20070132503 | Nordin | Jun 2007 | A1 |
| 20070157639 | Harrod | Jul 2007 | A1 |
| 20070158442 | Chapman et al. | Jul 2007 | A1 |
| 20070158444 | Naujok et al. | Jul 2007 | A1 |
| 20070173978 | Fein et al. | Jul 2007 | A1 |
| 20070177857 | Troost et al. | Aug 2007 | A1 |
| 20070182580 | Elwell | Aug 2007 | A1 |
| 20070192739 | Hunleth et al. | Aug 2007 | A1 |
| 20070205297 | Finkam et al. | Sep 2007 | A1 |
| 20070220907 | Ehlers | Sep 2007 | A1 |
| 20070221741 | Wagner et al. | Sep 2007 | A1 |
| 20070225867 | Moorer et al. | Sep 2007 | A1 |
| 20070227721 | Springer et al. | Oct 2007 | A1 |
| 20070228183 | Kennedy et al. | Oct 2007 | A1 |
| 20070241203 | Wagner et al. | Oct 2007 | A1 |
| 20070246553 | Morrow et al. | Oct 2007 | A1 |
| 20070257120 | Chapman et al. | Nov 2007 | A1 |
| 20070278320 | Lunacek | Dec 2007 | A1 |
| 20070296280 | Sorg et al. | Dec 2007 | A1 |
| 20080006709 | Ashworth 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 |
| 20080099568 | Nicodem et al. | May 2008 | A1 |
| 20080155915 | Howe et al. | Jul 2008 | A1 |
| 20080168368 | Louch | Jul 2008 | A1 |
| 20080183335 | Poth et al. | Jul 2008 | A1 |
| 20080191045 | Harter | Aug 2008 | A1 |
| 20080215240 | Howard et al. | Sep 2008 | A1 |
| 20080219227 | Michaelis | Sep 2008 | A1 |
| 20080221737 | Josephson et al. | Sep 2008 | A1 |
| 20080245480 | Knight et al. | Oct 2008 | A1 |
| 20080256475 | Amundson et al. | Oct 2008 | A1 |
| 20080273754 | Hick et al. | Nov 2008 | A1 |
| 20080290183 | Laberge et al. | Nov 2008 | A1 |
| 20080317292 | Baker et al. | Dec 2008 | A1 |
| 20090001180 | Siddaramanna et al. | Jan 2009 | A1 |
| 20090001181 | Siddaramanna et al. | Jan 2009 | A1 |
| 20090024927 | Schrock et al. | Jan 2009 | A1 |
| 20090057424 | Sullivan et al. | Mar 2009 | A1 |
| 20090099699 | Steinberg et al. | Apr 2009 | A1 |
| 20090125151 | Steinberg et al. | May 2009 | A1 |
| 20090140056 | Leen | Jun 2009 | A1 |
| 20090140057 | Leen | Jun 2009 | A1 |
| 20090140060 | Stoner et al. | Jun 2009 | A1 |
| 20090140062 | Amundson et al. | Jun 2009 | A1 |
| 20090140064 | Schultz et al. | Jun 2009 | A1 |
| 20090143916 | Boll et al. | Jun 2009 | A1 |
| 20090143918 | Amundson et al. | Jun 2009 | A1 |
| 20090144642 | Crystal | Jun 2009 | A1 |
| 20090158188 | Bray et al. | Jun 2009 | A1 |
| 20090171862 | Harrod et al. | Jul 2009 | A1 |
| 20090194601 | Flohr | Aug 2009 | A1 |
| 20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
| 20090215534 | Wilson et al. | Aug 2009 | A1 |
| 20090254225 | Boucher et al. | Oct 2009 | A1 |
| 20090259713 | Blumrich et al. | Oct 2009 | A1 |
| 20090261174 | Butler et al. | Oct 2009 | A1 |
| 20090263773 | Kotlyar et al. | Oct 2009 | A1 |
| 20090273610 | Busch et al. | Nov 2009 | A1 |
| 20090283603 | Peterson et al. | Nov 2009 | A1 |
| 20090297901 | Kilian et al. | Dec 2009 | A1 |
| 20090327354 | Resnick et al. | Dec 2009 | A1 |
| 20100000417 | Tetreault et al. | Jan 2010 | A1 |
| 20100019051 | Rosen | Jan 2010 | A1 |
| 20100025483 | Hoeynck et al. | Feb 2010 | A1 |
| 20100050004 | Hamilton, II et al. | Feb 2010 | A1 |
| 20100053464 | Otsuka | Mar 2010 | A1 |
| 20100070084 | Steinberg et al. | Mar 2010 | A1 |
| 20100070085 | Harrod et al. | Mar 2010 | A1 |
| 20100070086 | Harrod et al. | Mar 2010 | A1 |
| 20100070089 | Harrod et al. | Mar 2010 | A1 |
| 20100070093 | Harrod et al. | Mar 2010 | A1 |
| 20100070096 | Harrod et al. | Mar 2010 | A1 |
| 20100070101 | Benes et al. | Mar 2010 | A1 |
| 20100070234 | Steinberg et al. | Mar 2010 | A1 |
| 20100070907 | Harrod et al. | Mar 2010 | A1 |
| 20100076605 | Harrod et al. | Mar 2010 | A1 |
| 20100076835 | Silverman | Mar 2010 | A1 |
| 20100084482 | Kennedy et al. | Apr 2010 | A1 |
| 20100106305 | Pavlak et al. | Apr 2010 | A1 |
| 20100106322 | Grohman | Apr 2010 | A1 |
| 20100107070 | Devineni et al. | Apr 2010 | A1 |
| 20100107076 | Grohman et al. | Apr 2010 | A1 |
| 20100107103 | Wallaert et al. | Apr 2010 | A1 |
| 20100107111 | Mirza et al. | Apr 2010 | A1 |
| 20100156665 | Krzyzanowski et al. | Jun 2010 | A1 |
| 20100163633 | Barrett et al. | Jul 2010 | A1 |
| 20100167783 | Alameh et al. | Jul 2010 | A1 |
| 20100168924 | Tessier et al. | Jul 2010 | A1 |
| 20100179704 | Ozog | Jul 2010 | A1 |
| 20100198425 | Donovan | Aug 2010 | A1 |
| 20100211224 | Keeling et al. | Aug 2010 | A1 |
| 20100262298 | Johnson et al. | Oct 2010 | A1 |
| 20100262299 | Cheung et al. | Oct 2010 | A1 |
| 20100273610 | Johnson | Oct 2010 | A1 |
| 20100282857 | Steinberg | Nov 2010 | A1 |
| 20100289643 | Trundle et al. | Nov 2010 | A1 |
| 20100308119 | Steinberg et al. | Dec 2010 | A1 |
| 20100318227 | Steinberg et al. | Dec 2010 | A1 |
| 20100324962 | Nesler | Dec 2010 | A1 |
| 20110001812 | Kang et al. | Jan 2011 | A1 |
| 20110015797 | Gilstrap | Jan 2011 | A1 |
| 20110015798 | Golden et al. | Jan 2011 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110016017 | Carlin et al. | Jan 2011 | A1 |
| 20110022242 | Bukhin et al. | Jan 2011 | A1 |
| 20110029488 | Fuerst et al. | Feb 2011 | A1 |
| 20110046756 | Park | Feb 2011 | A1 |
| 20110046792 | Imes et al. | Feb 2011 | A1 |
| 20110046805 | Bedros et al. | Feb 2011 | A1 |
| 20110046806 | Nagel et al. | Feb 2011 | A1 |
| 20110054710 | Imes et al. | Mar 2011 | A1 |
| 20110077758 | Tran et al. | Mar 2011 | A1 |
| 20110077896 | Steinberg et al. | Mar 2011 | A1 |
| 20110082594 | Dage et al. | Apr 2011 | A1 |
| 20110106328 | Zhou et al. | May 2011 | A1 |
| 20110151837 | Winbush, III | Jun 2011 | A1 |
| 20110160913 | Parker et al. | Jun 2011 | A1 |
| 20110166828 | Steinberg et al. | Jul 2011 | A1 |
| 20110167369 | van Os | Jul 2011 | A1 |
| 20110173542 | Imes et al. | Jul 2011 | A1 |
| 20110185895 | Freen | Aug 2011 | A1 |
| 20110224838 | Imes et al. | Sep 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 |
| 20120017611 | Coffel et al. | Jan 2012 | A1 |
| 20120036250 | Vaswani et al. | Feb 2012 | A1 |
| 20120053745 | Ng | Mar 2012 | A1 |
| 20120065783 | Fadell et al. | Mar 2012 | A1 |
| 20120065935 | Steinberg et al. | Mar 2012 | A1 |
| 20120066168 | Fadell et al. | Mar 2012 | A1 |
| 20120067561 | Bergman | 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 |
| 20120125559 | Fadell et al. | May 2012 | A1 |
| 20120125592 | Fadell et al. | May 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 |
| 20120130548 | 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 |
| 20120165993 | Whitehouse | Jun 2012 | A1 |
| 20120179300 | Warren et al. | Jul 2012 | A1 |
| 20120186774 | Matsuoka et al. | Jul 2012 | A1 |
| 20120191257 | Corcoran et al. | Jul 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 |
| 20120233478 | Mucignat et al. | Sep 2012 | A1 |
| 20120239207 | Fadell et al. | Sep 2012 | A1 |
| 20120239221 | Mighdoll et al. | Sep 2012 | A1 |
| 20120252430 | Imes et al. | Oct 2012 | A1 |
| 20120286051 | Lyle | Nov 2012 | A1 |
| 20120296488 | Dharwada et al. | Nov 2012 | A1 |
| 20130014057 | Reinpoldt et al. | Jan 2013 | A1 |
| 20130024799 | Fadell et al. | Jan 2013 | A1 |
| 20130046397 | Fadell et al. | Feb 2013 | A1 |
| 20130090767 | Bruck et al. | Apr 2013 | A1 |
| 20130090768 | Amundson et al. | Apr 2013 | A1 |
| 20130099011 | Matsuoka et al. | Apr 2013 | A1 |
| 20140005837 | Fadell et al. | Jan 2014 | A1 |
| 20140058567 | Matsuoka | Feb 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2202008 | Feb 2000 | CA |
| 103890667 | Jun 2014 | CN |
| 19609390 | Sep 1997 | DE |
| 207295 | Jan 1987 | EP |
| 434926 | Jul 1991 | EP |
| 196069 | Dec 1991 | EP |
| 720077 | Jul 1996 | EP |
| 802471 | Oct 1997 | EP |
| 1065079 | Jan 2001 | EP |
| 1184804 | Mar 2002 | EP |
| 1731984 | Dec 2006 | EP |
| 1283396 | Mar 2007 | EP |
| 2157492 | Feb 2010 | EP |
| 1703356 | Sep 2011 | EP |
| 2212317 | May 1992 | GB |
| 59106311 | Jun 1984 | JP |
| 01252850 | Oct 1989 | JP |
| 09298780 | Nov 1997 | JP |
| 10023565 | Jan 1998 | JP |
| 2002087050 | Mar 2002 | JP |
| 2003054290 | Feb 2003 | JP |
| 1020070117874 | Dec 2007 | KR |
| 1024986 | Jun 2005 | NL |
| 0248851 | Jun 2002 | WO |
| 2005019740 | Mar 2005 | WO |
| 2008054938 | May 2008 | WO |
| 2009073496 | Jun 2009 | WO |
| 2010033563 | Mar 2010 | WO |
| 2011128416 | Oct 2011 | WO |
| 2011149600 | Dec 2011 | WO |
| 2012024534 | Feb 2012 | WO |
| 2012068436 | 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 |
| 2012068591 | May 2012 | WO |
| 2013052389 | Apr 2013 | WO |
| 2013058820 | Apr 2013 | WO |
| 2013059671 | Apr 2013 | WO |
| Entry |
|---|
| Advanced Model Owner's Manual, Bay Web Thermostat, manual [online]-[retrieved on Nov. 7, 2012]. Retrieved from the Internet: <URL:http://www.bayweb.com/wp-content/uploads/BW-WT4-2DOC.pdf> Oct. 6, 2011; 31 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. |
| 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. |
| 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. |
| 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>. |
| 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. |
| 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/020026, International Search Report & Written Opinion, dated May 3, 2012, 8 pages. |
| Ros et al., “Multi-Sensor Human Tracking with the Bayesian Occupancy Filter”, IEEE, 2009, 8 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. |
| Energy Joule. Ambient Devices, Jul. 23, 2011, [retrieved on Aug. 1, 2012]. Retrieved from: http://web.archive.org/web/20110723210421/http://www.ambientdevices.com/products/energyjoule.htm I-2 pages. |
| International Patent Application No. PCT/US2012/030084, International Search Report & Written Opinion, dated Jul. 6, 2012, 7 pages. |
| International Patent Application No. PCT/US2012/030084, International Preliminary Report on Patentability dated Apr. 22, 2014, 5 pages. |
| International Preliminary Report on Patentability dated Apr. 8, 2014 for International Patent Application No. PCT/US2012/058207 filed Sep. 30, 2012, 8 pages. |
| Honeywell CT2700, An Electronic Round Programmable Thermostat , User's Guide, Honeywell, Inc., 1997, 8 pages. |
| Honeywell CT8775A,C, The digital Round Non, Programmable Thermostats , Owner's Guide, Honeywell International Inc., 2003, 20 pages. |
| Honeywell T8700C, An Electronic Round Programmable Thermostat , Owner's Guide, Honeywell, Inc., 1997, 12 pages. |
| Honeywell T8775 The Digital Round Thermostat, Honeywell, 2003, 2 pages. |
| Honeywell T8775AC Digital Round Thermostat Manual No. 69-1679EF-1-www.honeywell.com/yourhome, Jun. 2004, pp. 1-16. |
| ICY 3815TT-001 Timer, Thermostat Package Box, ICY BV Product Bar Code No. 8717953007902, 2009, 2 pages. |
| The Clever Thermostat, ICY BV Web Page, http://www.icy.nl/en/consurner/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. |
| U.S. Appl. No. 60/512,886, Volkswagen Rotary Knob for Motor Vehicle , English Translation of German Application filed Oct. 20, 2003. |
| 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, 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. |
| 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. |
| 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. |
| 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>. |
| Green, “Thermo Heat Tech Cool”, Popular Mechanics Electronic Thermostat Guide, Oct. 1985, pp. 155-158. |
| 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. |
| International Patent Application No. PCT/US2011/061470, International Search Report & Written Opinion, dated Apr. 3, 2012, 11 pages. |
| International Patent Application No. PCT/US2012/058207, International Search Report & Written Opinion, dated Jan. 11, 2013, 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., 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.saltech.com, Version 005, Apr. 29, 2010, 24 pages. |
| Sanford, “iPod (Click Wheel) (2004)”, www.apple-history.com [retrieved on Apr. 9, 2012]. Retrieved from: http://apple-history.com/ipod, Apr. 9, 2012, 2 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. |
| International Patent Application No. PCT/US2011/061491, International Search Report & Written Opinion, dated Mar. 30, 2012, 6 pages. |
| International Patent Application No. PCT/US2012/020026, International Preliminary Report on Patentability, dated Jul. 11, 2013, 7 pages. |
| Bourke, Server Load Balancing, O'Reilly & Associates, Inc., Aug. 2001, 182 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. |
| 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. |
| 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. |
| White, et al., “A Conceptual Model for Simulation Load Balancing”, Proc. 1998 Spring Simulation Interoperability Workshop, 1998, 7 pages. |
| Chinese Office Action dated Jul. 20, 2015 for Chinese Patent Application No. 201280051592.9 filed Mar. 22, 2012, 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160139582 A1 | May 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61550346 | Oct 2011 | US | |
| 61429093 | Dec 2010 | US | |
| 61415771 | Nov 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13842048 | Mar 2013 | US |
| Child | 14975061 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13632041 | Sep 2012 | US |
| Child | 13842048 | US | |
| Parent | 13269501 | Oct 2011 | US |
| Child | 13632041 | US | |
| Parent | 13317423 | Oct 2011 | US |
| Child | 13269501 | US | |
| Parent | 13033573 | Feb 2011 | US |
| Child | 13317423 | US |
