Geo-fencing with advanced intelligent recovery

Information

  • Patent Grant
  • 10802459
  • Patent Number
    10,802,459
  • Date Filed
    Monday, April 27, 2015
    9 years ago
  • Date Issued
    Tuesday, October 13, 2020
    3 years ago
Abstract
A building temperature may be allowed to deviate from a comfort temperature set point to an energy saving temperature when a user is outside the geo-fence. Crossing information indicating when a user crosses into the geo-fence may be received. The crossing information may be stored over time to develop a history of when the user crosses into the geo-fence. A probability function that operates on at least part of the stored crossing information may be used to predict a time range of when the user is expected to next arrive at the building, the time range having a starting time and an ending time. The HVAC system may be instructed to drive the building temperature to an intermediate temperature at the starting time of the time range, wherein the intermediate temperature is between the energy saving temperature and the comfort temperature set point.
Description
TECHNICAL FIELD

The disclosure relates generally to building automation and more particularly to building automation systems with geo-fencing capabilities.


BACKGROUND

Building automation systems are often used to control safety, security and/or comfort levels within a building or other structure. Illustrative but non-limiting examples of building automation systems include Heating, Ventilation and/or Air Conditioning (HVAC) systems, security systems, lighting systems, fire suppression systems and/or the like. In some cases, a building automation system may enter an unoccupied mode when the building is expected to be unoccupied and an occupied mode when the building is expected to be occupied. For example, when the building automation system includes an HVAC system, the building automation system may set a temperature set point of the HVAC system to a more energy efficient setting when in an unoccupied mode and a more comfortable setting when in an occupied mode. In another example, when the building automation system includes a security system, the building automation system may set the security system to a locked or away state when in an unoccupied mode and an unlocked or home state when in an occupied mode.


SUMMARY

The present disclosure pertains generally to geo-fencing, and more particularly to building automation systems with geo-fencing capabilities. An example of the disclosure may be found in a method of implementing advanced intelligent recovery (AIR) in an HVAC system for a building. The HVAC system may implement geo-fencing using a geo-fence that is defined for the building or for one or more individual users of the building. A building temperature may be allowed to deviate from a comfort temperature set point to an energy saving temperature when a user is outside the geo-fence. Crossing information indicating when a user crosses into the geo-fence may be received. The crossing information may be stored over time to develop a history of when the user crosses into the geo-fence. At least some of the stored crossing information may be processed to determine a comfort time that is related to when the user is expected to next arrive at the building. The HVAC system may be programmed to drive the building temperature towards the comfort temperature set point based on the comfort time. In some cases, the comfort time is based at least in part upon an average value of at least some of the stored crossing information. In some instances, the HVAC system may be instructed to drive the building temperature to reach the comfort temperature set point by the comfort time.


In some instances, processing at least some of the stored crossing information may include using a probability function that operates on at least part of the stored crossing information in order to predict a time range of when the user is expected to next arrive at the building. The time range may have a starting time and an ending time, where the comfort time is at or between the starting time and the ending time. The HVAC system may be programmed to drive the building temperature to an intermediate temperature between the energy saving temperature and the comfort temperature set point at the starting time of the time range. In some cases, the HVAC system may be further programmed to drive the building temperature to the comfort temperature set point by at least the ending time of the time range. In some instances, the user may be permitted to select a balance between comfort and energy savings. When so provided, the intermediate temperature may be determined at least in part based upon the selected balance between comfort and energy savings.


Another example of the disclosure may be found in a method of implementing advanced intelligent recovery (AIR) in an HVAC system for a building. The HVAC system may implement geo-fencing using a geo-fence that is defined for the building. A building temperature may be allowed to deviate from the comfort temperature set point to an energy saving temperature when all of a plurality of users are determined to be outside of the geo-fence. Crossing information indicating when each of the users crosses into the geo-fence may be received. The crossing information may be stored over time for each of the plurality of users to develop a history of when each of the plurality of users crosses into the geo-fence. A probability function that operates on at least part of the stored crossing information may be used to predict a time range of when each of the plurality of users is expected to next arrive at the building. Each time range may have a starting time and an ending time. The HVAC system may be programmed to drive the building temperature to an intermediate temperature by the starting time of the time range that corresponds to the particular user that is expected to arrive first at the building.


Another example of the disclosure may be found in an HVAC control system for controlling operation of HVAC equipment within a building. The HVAC control system may be configured to be in operative communication with a user's mobile device running an executable program (e.g. application program) that provides geo-fence functionality. The HVAC control system may include an input for receiving crossing information indicating when the user's mobile device crosses into a geo-fence that is defined for the building. The HVAC control system has a memory for storing the crossing information over time to develop a history of when the user's mobile device crosses into the geo-fence. The HVAC control system may further have a controller that is operatively coupled to the input and the memory. The controller may be configured to control the HVAC equipment and allow a building temperature in the building to deviate from a comfort temperature set point to an energy saving temperature when the user's mobile device is outside the geo-fence. The controller may be configured to use a probability function that operates on at least part of the stored crossing information to predict a time range of when the user's mobile device is expected to next arrive at the building. The time range may have a starting time and an ending time. The controller may be further configured to control the HVAC equipment to drive the building temperature to an intermediate temperature that is between the energy saving temperature and the comfort temperature set point by the starting time of the time range.


Another example of the disclosure may be found in an HVAC controller configured to operate HVAC equipment within a building. A user of the building may have a mobile device with location services. The HVAC controller may include a memory for storing at least two targets. One of the at least two targets including a starting time point and an intermediate temperature set point. Another of the at least two targets including an ending time point and a comfort temperature set point. A communications module may receive the at least two targets from a remote server. An equipment interface may provide control signals to the HVAC equipment. A controller of the HVAC controller may be operably coupled to the memory, the communications module and the equipment interface, and may be configured to operate the HVAC equipment, via the equipment interface, in accordance with at least two targets received via the communications module and stored in the memory. The controller may be further configured to calculate one or more heating or cooling ramps based upon the at least two targets such that the building will attain the intermediate temperature set point by the starting time point and the building will attain the comfort temperature set point at or before the ending time point.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic view of an illustrative building automation system;



FIG. 2 is a schematic view of another illustrative building automation system;



FIG. 3 is a schematic view of another illustrative building automation system;



FIG. 4 is a schematic view of an illustrative HVAC control system;



FIGS. 5 and 6 are graphs illustrating features of advanced intelligent recovery in accordance with the disclosure;



FIG. 7 is a schematic view of an illustrative HVAC controller;



FIG. 8 is a flow diagram showing an illustrative method that may be carried out using the HVAC control system of FIG. 4;



FIG. 9 is a flow diagram showing an illustrative method that may be carried out using the HVAC control system of FIG. 4; and



FIG. 10 is a flow diagram showing an illustrative method that may be carried out using the HVAC control system of FIG. 4.





While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit aspects of the disclosure to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.


DESCRIPTION

The following description should be read with reference to the drawings wherein like reference numerals indicate like elements. The drawings, which are not necessarily to scale, are not intended to limit the scope of the disclosure. In some of the figures, elements not believed necessary to an understanding of relationships among illustrated components may have been omitted for clarity.


All numbers are herein assumed to be modified by the term “about”, unless the content clearly dictates otherwise. The recitation of numerical ranges by endpoints includes all numbers subsumed within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).


As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include the plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.


It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that the feature, structure, or characteristic may be applied to other embodiments whether or not explicitly described unless clearly stated to the contrary.


The present disclosure is directed generally at building automation systems. Building automation systems are systems that control one or more operations of a building. Building automation systems can include HVAC systems, security systems, fire suppression systems, energy management systems and/or any other suitable systems. While HVAC systems are used as an example below, it should be recognized that the concepts disclosed herein can be applied to building control systems more generally.


A building automation system may include a controller, computer and/or other processing equipment that is configured to control one or more features, functions, systems or sub-systems of a building. In some cases, devices that can be used by individuals to communicate with the controller, computer and/or other processing equipment. In some cases, a building automation system may include a plurality of components that, in combination, perform or otherwise provide the functionality of the building automation system. A building automation system may be fully contained within a single building, or may include components that are spread between multiple housings and/or across multiple locations. In some embodiments, a building automation system, regardless of the physical location(s) of the components within the building automation system, may control one or more building systems within a single building. In some cases, a building automation system, regardless of the physical location(s) of the components within the building automation system, may control one or more building systems within a plurality of buildings, optionally in accordance with a common operating procedure and/or distinct operating procedures for each building as desired.



FIG. 1 is a schematic illustration of an illustrative building automation system 10. The illustrative building automation system 10 includes a server 12 that may be configured to communicate with a mobile device 14 and with a building controller 16. It will be appreciated that for simplicity, only a single mobile device 14 is shown, while in many cases the server 12 may be configured to communicate directly or indirectly with any number of mobile devices 14. Similarly, while a single building controller 16 is illustrated, in many cases the server 12 may be configured to communicate directly or indirectly with any number of building controllers 16, located in a single building or distributed throughout a plurality of buildings. The server 12 is illustrated as a single, cloud-based server. In some cases, the server 12 may be a single server. In some instances, the server 12 may generically represent two, three or more servers commonly located or spread between two or more physical locations. In some cases, the server 12 handles communication with both the mobile device 14 and the building controller 16. In some instances, as shown for example in FIG. 2, distinct servers may carry out each communications protocol if desired.


In some cases, the mobile devices 14 may communicate with the server 12 at least partially through a network such as the Internet, sometimes using a cell phone network, WiFi network and/or any other suitable network. Likewise, it is contemplated that the building controller 16 may communicate with the server 12 at least partially through a network such as the Internet, sometimes using a cell phone network, WiFi network and/or any other suitable network.



FIG. 2 is a schematic illustration of another illustrative building automation system 20. The illustrative building automation system 20 includes a first server 22 that may be configured to communicate with a mobile device 14 (or multiple mobile devices 14) and a second server 24 that may be configured to communicate with a building controller 16 (or multiple building controllers 16). The first server 22 may be configured to receive data from the mobile device 14, process the data, and send data to the mobile device 14 and/or to the second server 24. The second server 24 may be configured to receive data from the building controller 16, process the data, and send data to the building controller 16 and/or to the first server 22. In some instances, the first server 22 may be configured to permit data from the mobile device 14 to pass directly through to the building controller 16. In some cases, the second server 24 may be configured to permit data from the building controller 16 to pass directly through to the mobile device 14. The first server 22 and the second server 24 may be configured to communicate with each other. In some cases, each of the first server 22 and the second server 24 may perform a defined function.


It will be appreciated that for simplicity, only a single mobile device 14 is shown, while in many cases the first server 22 may be configured to communicate directly or indirectly with any number of mobile devices 14. Similarly, while a single building controller 16 is illustrated, in many cases the second server 24 may be configured to communicate directly or indirectly with any number of building controllers 16, located in a single building or distributed throughout a plurality of buildings.


The first server 22 is illustrated as a single, cloud-based server. In some cases, the first server 22 may be a single server. In some instances, the first server 22 may generically represent two, three or more servers commonly located or spread between two or more physical locations. The second server 24 is illustrated as a single, cloud-based server. In some cases, the second server 24 may be a single server. In some instances, the second server 24 may generically represent two, three or more servers commonly located or spread between two or more physical locations. In some cases, the first server 22 and the second server 24 may, in combination, be considered as representing or forming a building automation server 26.



FIG. 3 is a schematic illustration of a building automation system 30 in which a building automation server 26 is configured to communicate with a plurality of buildings 32 as well as a plurality of mobile devices 34. It is contemplated that the building automation server 26 may include a single server or two or more distinct servers at one or several locations. The building automation system 30 may serve any desired number of buildings. As illustrated, the plurality of buildings 32 includes a Building One, labeled as 32A, a Building Two, labeled as 32B, and so on through a Building “N”, labeled as 32N. It will be appreciated that the building automation system 30 may include a large number of buildings, each in communication with a central (or distributed) building automation server 26. In some cases, each building may be associated with a unique customer account, as further described below.


As illustrated, each of the plurality of buildings 32 includes a building controller and one or more pieces of building equipment. The building equipment may, for example, be HVAC equipment, security equipment, lighting equipment, fire suppression equipment, and/or the like. In particular, the building 32A includes a building controller 36A and building equipment 38A, the building 32B includes a building controller 36B and building equipment 38B, and so on through the building 32N, which includes a building controller 36N and building equipment 38N. It will be appreciated that while each building is illustrated as having a single building controller and single building equipment controlled by the single building controller, in some cases a building may have multiple related or unrelated building controllers and/or multiple pieces of related or unrelated building equipment.


The plurality of mobile devices 34 may be considered as being divided into a set of mobile devices each associated with a corresponding building. In the example shown, the plurality of mobile devices 34 may be considered as being divided into a set of mobile devices 40A that are associated with the building 32A, a set of mobile devices 40B that are associated with the building 32B, and so on through a set of mobile devices 40N that are associated with the building 32N. As illustrated, the set of mobile devices 40A includes a first mobile device 42A, a second mobile device 44A and a third mobile device 46A. The set of mobile devices 40B includes a first mobile device 42B, a second mobile device 44B and a third mobile device 46B and so on through the set of mobile devices 40N, which includes a first mobile device 42N, a second mobile device 44N and a third mobile device 46N. This is merely illustrative, as any number of mobile devices such as smartphones or tablets, may be associated with a particular building, as desired. Each user or occupant of a building may have an associated mobile device, or may have several associated mobile devices. In some cases, a user or occupant may have a mobile device associated with several different locations such as a home, a cabin or a place of work.


Associating a mobile device with a particular building generally involves the individual who uses the particular mobile device. In the example shown in FIG. 3, a mobile device can communicate with the building automation server 26, and may cause the building automation server 26 to provide instructions to the building controller that is associated with the particular mobile device. For example, and in some instances, a mobile phone with location services activated can be used to inform the building automation server 26 as to the whereabouts of the user relative to a geo-fence defined for the associated building, and in some cases an estimate of how long before the user will arrive at the associated building. The building automation server 26 may send a command to the building controller of the associated building to operate the building equipment in an energy savings manner when all of the users that are associated with a particular building are determined to be away from the building (e.g. the building is unoccupied). The building automation server 26 may send a command to the building controller of the associated building to operate the building equipment in a comfort mode when all of the users that are associated with a particular building are determined or deemed not to be away from the building (e.g. the building is occupied).



FIG. 4 is a schematic illustration of an HVAC control system 48 that is configured to control operation of HVAC equipment 50 within a user's building. In some instances, the HVAC control system 48 may be considered as being an example or a manifestation of the building automation server 26 described with respect to FIGS. 2 and 3 and is in operative communication with a user's mobile device 14 that is running an executable program providing geo-fencing functionality, such as a geo-fence application program. The illustrative HVAC control system 48 includes an input 52 for receiving crossing information indicating when the user's mobile device 14 crosses into a geo-fence that is defined for the building, a memory 54 for storing the crossing information over time to develop a history of when the user's mobile device 14 crosses into the geo-fence, and a controller 56 that is operatively coupled to the input 52 and the memory 54. The controller 56 may be configured to control either directly or indirectly through an intervening HVAC controller (not illustrated), the HVAC equipment 50 and allow a building temperature in the building to deviate from a comfort temperature set point to an energy saving temperature when the user's mobile device 14 is outside of the geo-fence.


In some instances, the controller 56 may be configured to analyze historical geo-fence crossing data to determine an estimated comfort time. The comfort time is an indication of when the user is expected to cross the geo-fence and/or actually arrive home for a particular day. The historical geo-fence crossing data may, for example, be analyzed to determine an average or mean estimated return time. In some cases, a median or mode may be calculated, or any other useful statistical analysis. The analysis may be based on a set number of previous days, and thus may be updated periodically. In some instances, for example, the analysis may yield a weighted average in which more recent historical geo-fence crossing data is weighed more heavily than older historical geo-fence crossing data.


In some instances, the controller 56 is further configured to use a probability function that operates on at least part of the stored crossing information to predict a time range of when the user's mobile device 14 is expected to next arrive at the building. The time range may have a starting time and an ending time. The controller 56 may be configured to control the HVAC equipment 50 to drive the building temperature to an intermediate temperature that is between the energy saving temperature and the comfort temperature set point by the starting time of the time range.


Turning briefly to FIGS. 5 and 6, FIG. 5 is a schematic graphical representation showing a probability of a user returning home at any particular point in time. Time is graphed on the X axis while probability is graphed on the Y axis. By tabulating geo-fence crossing data over time, the controller 56 can determine the relative probability that the user will return home, or at least cross a geo-fence heading for home, at any given point in time. In many cases, as can be seen, the probability curve has a bell-shaped curve that is roughly centered on an average return time. If the user tends to return home within a relatively tight time frame, the peak on the probability curve will be relatively narrow, and the probability curve will have a smaller standard deviation. Conversely, if the user tends to return home over a wider range of time, the peak on the probability curve will be wider, and the probability curve will have a relatively larger standard deviation. In some cases, the controller 56 may track and calculate the relative probability of a return home for a single user, or for each of a plurality of users, and/or for a collection of users.


In some instances, the controller 56 may determine a time range including a starting time and an ending time from a probability distribution. The starting time and the ending time may be determined using any suitable or desirable criteria. In some instances, for example, the time range may have a span that is about equal to one standard deviation, although this is not required. On FIG. 5, a starting point 60 corresponds to a Time-1 while an ending point 62 corresponds to a Time-2. These points 60, 62 are carried forward onto FIG. 6, which is a graph of building temperature versus time. Time is again graphed on the X axis while building temperature is graphed on the Y axis. It can be seen that the starting point 60 corresponds to an intermediate temperature 64 that is between an energy saving temperature and a comfort temperature 66. In some cases, the ending point 62 corresponds to the comfort temperature 66. In some instances, if a single time point such as a comfort time is determined, the comfort time may correspond to Time-1, Time-2 or some intermediate point.


This example shows a heating ramp, although a similar (but opposite in direction) cooling ramp can also be drawn when the HVAC system is in a cooling mode. In the example shown, during the day the building temperature 68 may start at the comfort temperature 66. Once the controller 56 determines that the building is now unoccupied, such as after being notified that all users have crossed the geo-fence in an outward direction, the building temperature 68 may be allowed to drift downward as indicated by building temperature line 68. In some cases, the building temperature 68 will only be allowed to drift downward a certain number of degrees and then hold there until a user is expected to return to the building. In some instances, the number of degrees that the building temperature 68 is allowed to drift may depend on, for example, the radius of the geo-fence, how much warning time the system has been given in the past before a user actually arrives at the building, and/or on any other suitable criteria as desired.


Once the building's HVAC controller is notified of the starting point 60, the desired intermediate temperature 64 that is desired at the starting point 60, the ending point 62, and/or the corresponding comfort temperature 66 that is desired at the ending point 62, the HVAC controller may calculate a heating ramp 70. The heating ramp 70 may be based at least in part upon historical data retained by the HVAC controller with respect to how quickly the HVAC equipment 50 (FIG. 4) can heat the building under the present conditions. The particulars of the heating ramp 70, including the slope of the heating ramp 70 and the starting point 72 may vary, depending on season, local climate, etc. The heating ramp 70 may be calculated in order to help ensure that the building is at the intermediate temperature 64 by the starting point 60 and/or is at the comfort temperature 66 by the ending point 62. This way, if a user returns home at or near the starting point 60, which should be a little earlier than an average or even mean expected return time, the building may not be at the comfort temperature but may at least be reasonably comfortable.


The graphs shown in FIGS. 5 and 6 are schematic and are generic as to day. In some cases, the probability function used by the controller 56 may vary from day to day. For example, people's daily schedules can vary from day to day. In some cases, it may be useful when determining the probability distribution for a particular user returning home on a Monday, Tuesday, Wednesday or Thursday, the controller 56 may utilize historical geo-fence crossing data from Mondays, Tuesdays, Wednesdays and Thursdays. However, when determining a probability distribution for a particular user returning home on a Friday, the controller 56 may utilize historical geo-fence crossing data from Mondays, Tuesdays, Wednesdays, Thursdays and Fridays. In some cases, for weekends, the controller 56 may utilize historical geo-fence crossing data from Saturdays and Sundays. It will be appreciated that this is illustrative only, as other combinations of historical geo-fence crossing data may prove more accurate for a particular situation.


In some instances, the controller 56 may utilize historical data only for specific days. For example, in order to determine the probability distribution for a user returning home on a particular Tuesday, the controller 56 may look only at historical geo-fence crossing data for previous Tuesdays. In some cases, the controller 56 may look at historical data going back a particular length of time, such as the past two weeks, the past month, and so on. Thus, the controller 56 may periodically update its estimates for when a user is expected to return home.


Returning to FIG. 4, while the HVAC control system 48 has thus far been described with respect to a single user, in some cases there may be a plurality of users. In such cases, the input 52 may be configured to receive crossing information indicating when each of a plurality of user's mobile devices 14 cross into the geo-fence associated with the building. In some cases, the memory 54 may be configured to store crossing information over time for each of the plurality of user's mobile devices 14. The controller 56 may, for example, be configured to control the HVAC equipment 50 and allow the building temperature to deviate from the comfort temperature set point to an energy saving temperature when all of the plurality of user's mobile devices 14 are outside the geo-fence. In some cases, the controller 56 may be configured to use a probability function that operates on at least part of the stored crossing information to predict a time range of when each of the plurality of user's mobile devices 14 is expected to next arrive at the building. Each time range may have a starting time and an ending time. In some instances, the controller 56 may control the HVAC equipment to drive the building temperature to an intermediate temperature that is between the energy saving temperature and a comfort temperature set point by the starting time of the time range that corresponds to the user's mobile device 14 that is expected to arrive first at the building.



FIG. 7 is a schematic diagram of an illustrative HVAC controller 74 that is configured to operate HVAC equipment 76 that is within a building. A user of the building may have a mobile device 14 with location services. In some cases, the HVAC controller 74 may include a memory 78 for storing at least two targets. One of the at least two targets may include a starting time point, such as the starting time point 60 in FIGS. 5 and 6, and an intermediate temperature, such as the intermediate temperature 64 shown in FIGS. 5 and 6. Another of the at least two targets may include an ending time point, such as the ending time point 62 in FIGS. 5 and 6, and a comfort temperature set point, such as the comfort temperature 66 shown in FIGS. 5 and 6. A communications module 80 may allow the HVAC controller 74 to receive the at least two targets from an external source such as a remote server 88. An equipment interface 82 may be used to provide control signals to the HVAC equipment 76. A controller 84 may be operably coupled to the memory 78, to the communications module 80 and to the equipment interface 82.


The controller 84 may be configured to operate the HVAC equipment 76, via the equipment interface 82, in accordance with at least two targets received via the communications module 80 and stored in the memory 78. In some cases, the controller 84 may calculate one or more heating or cooling ramps, such as the heating ramp 70 illustrated in FIG. 6, based upon the at least two targets such that the building will attain the intermediate temperature set point at a time corresponding to the starting time point and/or the building will attain the comfort temperature set point at or before the ending time point.


In some cases, the at least two targets received from the remote server 88 are calculated by the remote server 88 based, at least in part, upon a probability function that references historical geo-fence crossing data. Optionally, the HVAC controller 74 may include a user interface 86, although this is not required. In some cases, the controller 84 is configured to permit a user to select, using the user interface 86, a balance setting between comfort and energy savings. The selected balance setting may be uploaded to the remote server 88 for use in calculating at least one of the at least two targets. If the user selects a balance weighted towards comfort, the remote server 88 may calculate an intermediate temperature that is relatively closer to the comfort temperature. Conversely, if the user selects a balance weighted towards energy savings, the remote server 88 may calculate an intermediate temperature that is relatively farther away from the comfort temperature. In some cases, the intermediate temperature may be far enough from the comfort temperature that the comfort temperature may not be fully achieved by the ending time point.



FIG. 8 is a flow diagram of an illustrative method that may be carried out by the HVAC control system 48 and/or the HVAC controller 74, where the HVAC control system 48 implements geo-fencing using a geo-fence that is defined for a building or for one or more individuals associated with the building. A building temperature is allowed to deviate from a comfort temperature set point to an energy saving temperature when a user is outside the geo-fence as indicated at block 90. As seen at block 92, crossing information indicating when a user crosses into the geo-fence may be received. The crossing information may be stored over time to develop a history of when the user crosses into the geo-fence as indicated at block 94. As seen at block 95, at least some of the stored crossing information may be processed to determine a comfort time that is related to when the user is expected to next arrive at the building. For example, the comfort time may be an estimate of when the user will cross the geo-fence on their way home. In some instances, the comfort time may be an estimate of when the user will actually arrive home and thus may factor in the location of the geo-fence and how far from the home the geo-fence is. In some cases, the comfort time may be based at least in part upon an average value of at least some of the stored crossing information. The HVAC system may be instructed to drive the building temperature towards the comfort temperature set point based on the comfort time as seen at block 97. In some cases, the HVAC system may be instructed to drive the building temperature to reach the comfort temperature by the comfort time.


In some embodiments, processing at least some of the stored crossing information includes using a probability function that operates on at least part of the stored crossing information to predict a time range of when the user is expected to next arrive at the building. The time range may have a starting time and an ending time, and the comfort time may be at or between the starting time and/or the ending time. In some cases, the HVAC system may be programmed to drive the building temperature to an intermediate temperature that is between the energy saving temperature and the comfort temperature set point by the starting time of the time range. In some instances, the HVAC system may be instructed to drive the building temperature to the comfort temperature set point by at least the ending time of the time range.



FIG. 9 is a flow diagram of an illustrative method that may be carried out by the HVAC control system 48 and/or the HVAC controller 74, where the HVAC control system 48 implements geo-fencing using a geo-fence that is defined for a building or for one or more individuals associated with the building. A building temperature is allowed to deviate from a comfort temperature set point to an energy saving temperature when a user is outside the geo-fence as indicated at block 90. As seen at block 92, crossing information indicating when a user crosses into the geo-fence may be received. The crossing information may be stored over time to develop a history of when the user crosses into the geo-fence as indicated at block 94. As seen at block 96, a probability function that operates on at least part of the stored crossing information may be used to predict a time range of when the user is expected to next arrive at the building. The time range may have a starting time and an ending time. The HVAC system may be programmed to drive the building temperature to an intermediate temperature that is between the energy saving temperature and the comfort temperature set point by the starting time of the time range, as generally indicated at block 98.


In some embodiments, and as optionally indicated at block 100, the HVAC system may be instructed to drive the building temperature to the comfort temperature set point at least by the ending time of the time range. Optionally, as seen at block 102, the user may be permitted to select a balance between comfort and energy savings. The intermediate temperature being determined at least in part based upon the selected balance between comfort and energy savings. If, for example, the user selects a balance weighted towards comfort, the intermediate temperature is closer to the comfort temperature set point than if the user selects a balance weighted towards energy savings. In some cases, as optionally indicated at block 104, upon identifying that the user has crossed out of the geo-fence, the user may be informed that the HVAC system will allow the building temperature to deviate from the comfort temperature set point in order to save energy. In some cases, the user may be asked if they would like the HVAC system to allow the building temperature to deviate from the comfort temperature set point in order to save energy. In some embodiments, the user may be given the opportunity, via the executable program running on their mobile device 14, to opt out of geo-fencing. If a user selects this, the HVAC control system 48 may ignore the location of that user until the user opts back in.


In some instances, the user may be given the opportunity, via the executable program running on their mobile device 14 to modify or even cancel a recovery towards the comfort temperature set point. For example, if the HVAC system determines that a user is expected home at about 6 pm on a particular day, but the user has plans after work that day, the user can inform the HVAC system to delay the recovery by several hours. As another example, the user may be leaving work early, and thus may wish to instruct the HVAC system to start the recovery at an earlier time. As another example, perhaps the user is going to the airport after work for a short business trip. In this case, the user can inform the HVAC system to cancel the recovery for the particular day, or perhaps maintain an away temperature for the duration of their business trip. In some instances, the user may modify the recovery by altering the temperature set point and/or the estimated time home. It will be appreciated that each of the steps indicated at block 100, 102 and 104 in the illustrative method of FIG. 9 are optional, and can be included or excluded in any particular combination.



FIG. 10 is a flow diagram of an illustrative method that may be carried out by the HVAC control system 48 and/or the HVAC controller 74, where the HVAC control system 48 implements geo-fencing using a geo-fence that is defined for a building. A building temperature is allowed to deviate from a comfort temperature set point to an energy saving temperature when all of a plurality of users are outside the geo-fence as indicated at block 106. As seen at block 108, crossing information indicating when each of the plurality of users cross into the geo-fence may be received. The crossing information may be stored over time to develop a history of when each of the plurality of users cross into the geo-fence as indicated at block 110. As seen at block 112, a probability function may operate on at least part of the stored crossing information to predict a time range of when each of the plurality of users are expected to next arrive at the building. The time range may have a starting time and an ending time. The HVAC system may be programmed to drive the building temperature to an intermediate temperature that is between the energy saving temperature and the comfort temperature set point by the starting time of the time range that corresponds to the user that is expected to arrive first at the building, s generally indicated at block 114.


Those skilled in the art will recognize that the present disclosure may be manifested in a variety of forms other than the specific embodiments described and contemplated herein. Accordingly, departure in form and detail may be made without departing from the scope and spirit of the present disclosure as described in the appended claims.

Claims
  • 1. A method of implementing advanced intelligent recovery in an HVAC system for a building, the HVAC system implementing geo-fencing using a geo-fence that is defined for the building or a user of the building, the method comprising: allowing a building temperature to deviate from a comfort temperature set point to an energy saving temperature when the user is outside the geo-fence as indicated by an outbound geo-fence crossing;receiving inbound geo-fence crossing information indicating when the user crosses into the geo-fence as indicated by one or more inbound geo-fence crossings;storing the inbound geofence crossing information over time resulting in historical inbound geo-fence crossing data that indicates historically when the user has crossed into the geo-fence;processing, for a particular day of a week, the historical inbound geo-fence crossing data for only one or more specific days of the week associated with the particular day of the week to predict a next inbound geo-fence crossing time representative of when the user is expected to next cross into the geo-fence for the particular day of the week, wherein processing the historical inbound geo-fence crossing data that indicates historically when the user has crossed into the geo-fence comprises determining a probability function of a next inbound geo-fence crossing for the user and for the particular day of the week, wherein the probability function indicates, for the user and for each time of a time range of the particular day of the week, a probability that the user will cross into the geo-fence; andinstructing the HVAC system to drive the building temperature towards the comfort temperature set point based on the predicted next inbound geo-fence crossing time.
  • 2. The method of claim 1, wherein the predicted next inbound geo-fence crossing time is based, at least in part, on one or more of an average, a median or a mode of at least some of the historical inbound geo-fence crossing data.
  • 3. The method of claim 1, wherein the HVAC system is instructed to drive the building temperature to reach the comfort temperature set point by a comfort time that is based at least in part on the predicted next inbound geo-fence crossing time.
  • 4. The method of claim 3, wherein the time range has a starting time and an ending time, the comfort time at or between the starting time and ending time.
  • 5. The method of claim 4, wherein instructing the HVAC system to drive the building temperature towards the comfort temperature set point based on the comfort time comprises instructing the HVAC system to drive the building temperature to an intermediate temperature at the starting time of the time range, wherein the intermediate temperature is between the energy saving temperature and the comfort temperature set point.
  • 6. The method of claim 4, further comprising: instructing the HVAC system to drive the building temperature to the comfort temperature set point by at least the ending time of the time range.
  • 7. The method of claim 5, further comprising permitting the user to select a balance between comfort and energy savings, the intermediate temperature being determined at least in part based upon the selected balance between comfort and energy savings.
  • 8. The method of claim 7, wherein if the user selects a balance weighted towards comfort, the intermediate temperature is closer to the comfort temperature set point than if the user selects a balance weighted towards energy savings.
  • 9. The method of claim 1, further comprising, upon identifying that the user has crossed out of the geo-fence, informing the user that the HVAC system will allow the building temperature to deviate from the comfort temperature set point in order to save energy.
  • 10. The method of claim 9, wherein, when the user has crossed out of the geo-fence, querying the user if the user would like the HVAC system to allow the building temperature to deviate from the comfort temperature set point in order to save energy.
  • 11. The method of claim 9, further comprising allowing the user to instruct the HVAC system to modify or cancel a recovery towards the comfort temperature set point.
  • 12. The method of claim 1, further comprising: allowing the building temperature to deviate from the comfort temperature set point to the energy saving temperature when all of a plurality of users are outside the geo-fence as indicated by outboard geo-fence crossings for each of the plurality of users;receiving inbound geo-fence crossing information indicating when each of the plurality of users crosses into the geo-fence;storing the inbound geo-fence crossing information over time for each of the plurality of users resulting in historical inbound geo-fence crossing data for each of the plurality of users, where the historical inbound geo-fence crossing data for each of the plurality of users indicates when each of the plurality of users has crossed into the geo-fence over time;processing at least some of the historical inbound geo-fence crossing data to predict a next inbound geo-fence crossing time representative of when any of the plurality of users is expected to next cross into the geo-fence; andinstructing the HVAC system to drive the building temperature towards the comfort temperature set point based on the predicted next inbound geo-fence crossing time.
  • 13. The method of claim 1, wherein determining the probability function comprises determining the probability function to vary from another probability function of the next inbound geo-fence crossing for the user and for another day of the week that is different than the particular day.
  • 14. The method of claim 1, wherein the particular day is Tuesday and wherein processing the historical inbound geo-fence crossing data comprises processing the historical inbound geo-fence crossing data only for one or more Tuesdays to predict the next inbound geo-fence crossing time representative of when the user is expected to next cross into the geo-fence for the particular day of the week.
  • 15. An HVAC control system for controlling operation of HVAC equipment within a building, the HVAC control system configured to be in operative communication with a mobile device running an executable program providing geo-fence functionality, the HVAC control system comprising: an input for receiving inbound crossing information indicating when the mobile device crosses into a geo-fence that is defined for the building;a memory for storing the inbound crossing information over time resulting in historical inbound geo-fence crossing data that indicates when the mobile device has crossed into the geo-fence;a controller operatively coupled to the input and the memory, the controller configured to control the HVAC equipment and allow a building temperature in the building to deviate from a comfort temperature set point to an energy saving temperature when the mobile device is outside the geo-fence;the controller is further configured to determine, for a particular day of a week, a probability function of a next inbound geo-fence crossing for the mobile device and for the particular day of the week based on the stored historical inbound geo-fence crossing data for only one or more specific days of the week associated with the particular day of the week, wherein the probability function indicates, for the mobile device and for each time of a time range of the particular day of the week, a probability that the mobile device will cross into the geo-fence, the time range having a starting time and an ending time; andthe controller is further configured to control the HVAC equipment to drive the building temperature to an intermediate temperature at the starting time of the time range, wherein the intermediate temperature is between the energy saving temperature and the comfort temperature set point.
  • 16. The HVAC control system of claim 15, wherein the controller is further configured to control the HVAC equipment to drive the building temperature to the comfort temperature set point by at least the ending time of the time range.
  • 17. The HVAC control system of claim 15, wherein the energy saving temperature is an energy saving temperature set point.
  • 18. The HVAC control system of claim 15, wherein: the input is for receiving inbound geo-fence crossing information indicating when each of a plurality of mobile devices cross into the geo-fence;the memory for storing the inbound geo-fence crossing information over time resulting in historical inbound geo-fence crossing data for each of the plurality of mobile devices;the controller is configured to control the HVAC equipment and allow the building temperature to deviate from the comfort temperature set point to the energy saving temperature when all of the plurality of mobile devices are outside the geo-fence;the controller is further configured to use a respective probability function of a next inbound geo-fence crossing for each mobile device of the plurality of mobile devices and for a particular day of a week and that operates on the stored historical inbound geo-fence crossing data to predict a time range of when each of the plurality of mobile devices is expected to next arrive at the building, each time range having a starting time and an ending time; andthe controller is further configured to control the HVAC equipment to drive the building temperature to an intermediate temperature at the starting time of the time range that corresponds to the mobile device of the plurality of mobile devices that is expected to arrive first at the building.
  • 19. An HVAC controller configured to operate HVAC equipment within a building, a user of the building having a mobile device with location services, the HVAC controller comprising: a memory for storing at least two targets, one of the at least two targets including a starting time point and an intermediate temperature set point, and another of the at least two targets including an ending time point and a comfort temperature set point;a communications module for receiving the at least two targets from a remote server, the starting time point and the ending time point based at least in part on a probability of an expected return time of the user to the building, wherein the at least two targets received from the remote server are calculated by the remote server based, at least in part, upon a probability function of a next inbound geo-fence crossing for the user and for a particular day of a week and that references, for the particular day of the week, historical inbound geo-fence crossing data for only one or more specific days of the week associated with the particular day of the week, wherein the probability function indicates, for the user and for each time of a time range of the particular day of the week, a probability that the user will cross into the geo-fence;an equipment interface for providing control signals to the HVAC equipment;a controller operably coupled to the memory, the communications module and the equipment interface;the controller configured to operate the HVAC equipment, via the equipment interface, in accordance with at least two targets received via the communications module and stored in the memory; andthe controller further configured to calculate one or more heating or cooling ramps based upon the at least two targets such that the building will attain the intermediate temperature set point at a time corresponding to the starting time point where the starting time point is earlier than an average or mean expected return time, and the building will attain the comfort temperature set point at or before the ending time point.
  • 20. The HVAC controller of claim 19, further comprising a user interface, and wherein the controller is configured to permit the user to select, using the user interface, a balance setting between comfort and energy savings, the selected balance setting being uploaded to the remote server for use in calculating at least one of the at least two targets.
US Referenced Citations (500)
Number Name Date Kind
3472452 Beeston, Jr. Oct 1969 A
3581985 Thorsteinsson et al. Jun 1971 A
3665360 Norden May 1972 A
3784094 Goodwin Jan 1974 A
3817453 Pinckaers Jun 1974 A
3972471 Ziegler Aug 1976 A
3979708 Thompson Sep 1976 A
3988708 Thorsteinsson et al. Oct 1976 A
4016520 Hummel Apr 1977 A
4089462 Bradford May 1978 A
4114681 Denny Sep 1978 A
4176785 Allard et al. Dec 1979 A
4187543 Healey et al. Feb 1980 A
4205381 Games et al. May 1980 A
4215408 Games et al. Jul 1980 A
4223831 Szarka Sep 1980 A
4228511 Simcoe et al. Oct 1980 A
4235368 Neel Nov 1980 A
4251025 Bonne et al. Feb 1981 A
4253153 Bitterli et al. Feb 1981 A
4266599 Saunders et al. May 1981 A
4270693 Hayes Jun 1981 A
4300199 Yoknis et al. Nov 1981 A
4314441 Pannone et al. Feb 1982 A
4329138 Riordan May 1982 A
4334855 Nelson Jun 1982 A
4335847 Levine Jun 1982 A
4338791 Stamp, Jr. et al. Jul 1982 A
4340355 Nelson et al. Jul 1982 A
4341345 Hammer et al. Jul 1982 A
4347974 Pinckaers et al. Sep 1982 A
4366534 Kompelien Dec 1982 A
4373897 Torborg Feb 1983 A
4386649 Hines et al. Jun 1983 A
4387763 Benton Jun 1983 A
4388692 Jones et al. Jun 1983 A
4421268 Bassett et al. Dec 1983 A
4429829 Dutton Feb 1984 A
4435149 Astheimer Mar 1984 A
4439139 Nelson et al. Mar 1984 A
4442972 Sahay et al. Apr 1984 A
4489882 Rodgers Dec 1984 A
4502625 Mueller Mar 1985 A
4531064 Levine Jul 1985 A
4533315 Nelson Aug 1985 A
4577278 Shannon Mar 1986 A
4598764 Beckey Jul 1986 A
4656835 Kidder et al. Apr 1987 A
4684060 Adams et al. Aug 1987 A
4685614 Levine Aug 1987 A
4686060 Crabtree et al. Aug 1987 A
4688547 Ballard et al. Aug 1987 A
4702413 Beckey et al. Oct 1987 A
4703795 Beckey Nov 1987 A
4708636 Johnson Nov 1987 A
4729207 Dempsey et al. Mar 1988 A
4751961 Levine et al. Jun 1988 A
4759498 Levine et al. Jul 1988 A
4767104 Plesinger Aug 1988 A
4799176 Cacciatore Jan 1989 A
4817705 Levine et al. Apr 1989 A
4819587 Tsutsui et al. Apr 1989 A
4828016 Brown et al. May 1989 A
4881686 Mehta Nov 1989 A
4892245 Dunaway et al. Jan 1990 A
4901918 Grald et al. Feb 1990 A
4911358 Mehta Mar 1990 A
4915615 Kawamura et al. Apr 1990 A
4941609 Bartels et al. Jul 1990 A
4971136 Mathur et al. Nov 1990 A
5002226 Nelson Mar 1991 A
5026270 Adams et al. Jun 1991 A
5070932 Vlasak Dec 1991 A
5088645 Bell Feb 1992 A
5115967 Wedekind May 1992 A
5115968 Grald May 1992 A
5192020 Shah Mar 1993 A
5197666 Wedekind Mar 1993 A
5211332 Adams May 1993 A
5240178 Dewolf et al. Aug 1993 A
5248083 Adams et al. Sep 1993 A
5259445 Pratt et al. Nov 1993 A
5270952 Adams et al. Dec 1993 A
5289362 Liebl et al. Feb 1994 A
5299631 Dauvergne Apr 1994 A
5314004 Strand et al. May 1994 A
5317670 Elia May 1994 A
5331944 Kujawa et al. Jul 1994 A
5340028 Thompson Aug 1994 A
5347981 Southern et al. Sep 1994 A
5370990 Staniford et al. Dec 1994 A
5395042 Riley et al. Mar 1995 A
5405079 Neeley et al. Apr 1995 A
5408986 Bigham Apr 1995 A
5454511 Van Ostrand et al. Oct 1995 A
5456407 Stalsberg et al. Oct 1995 A
5476221 Seymour Dec 1995 A
5485953 Bassett et al. Jan 1996 A
5520533 Vrolijk May 1996 A
5524556 Rowlette et al. Jun 1996 A
5539633 Hildebrand et al. Jul 1996 A
5555927 Shah Sep 1996 A
5590642 Borgeson et al. Jan 1997 A
5601071 Carr et al. Feb 1997 A
5607014 Van Ostrand et al. Mar 1997 A
5611484 Uhrich Mar 1997 A
5616995 Hollenbeck Apr 1997 A
5622310 Meyer Apr 1997 A
5630408 Versluis May 1997 A
5666889 Evens et al. Sep 1997 A
5676069 Hollenbeck Oct 1997 A
5680029 Smits et al. Oct 1997 A
5682826 Hollenbeck Nov 1997 A
5720231 Rowlette et al. Feb 1998 A
5732691 Maiello et al. Mar 1998 A
5791332 Thompson et al. Aug 1998 A
5806440 Rowlette et al. Sep 1998 A
5819721 Carr et al. Oct 1998 A
5822997 Atterbury Oct 1998 A
5860411 Thompson et al. Jan 1999 A
5865611 Maiello Feb 1999 A
5902183 D'Souza May 1999 A
5909378 De Milleville Jun 1999 A
5977964 Williams Nov 1999 A
5993195 Thompson Nov 1999 A
6000622 Tonner et al. Dec 1999 A
6062482 Gauthier et al. May 2000 A
6098893 Berglund et al. Aug 2000 A
6109255 Dieckmann et al. Aug 2000 A
6216956 Ehlers et al. Apr 2001 B1
6254008 Erickson et al. Jul 2001 B1
6255988 Bischoff Jul 2001 B1
6257870 Hugghins et al. Jul 2001 B1
6260765 Natale et al. Jul 2001 B1
6283115 Dempsey et al. Sep 2001 B1
6321744 Dempsey et al. Nov 2001 B1
6349883 Simmons et al. Feb 2002 B1
6354327 Mayhew Mar 2002 B1
6356282 Roytman et al. Mar 2002 B2
6357870 Beach et al. Mar 2002 B1
6377426 Hugghins et al. Apr 2002 B2
6400956 Richton Jun 2002 B1
6402043 Cockerill Jun 2002 B1
6478233 Shah Nov 2002 B1
6504338 Eichorn Jan 2003 B1
6529137 Roe Mar 2003 B1
6571817 Bohan, Jr. Jun 2003 B1
6604023 Brown et al. Aug 2003 B1
6645066 Gutta et al. Nov 2003 B2
6665613 Duvall Dec 2003 B2
6705533 Casey et al. Mar 2004 B2
6729390 Toth et al. May 2004 B1
6749423 Fredricks et al. Jun 2004 B2
6758909 Jonnalagadda et al. Jul 2004 B2
6764298 Kim et al. Jul 2004 B2
6769482 Wagner Aug 2004 B2
6786225 Stark et al. Sep 2004 B1
6793015 Brown et al. Sep 2004 B1
6846514 Jonnalagadda et al. Jan 2005 B2
6866202 Sigafus et al. Mar 2005 B2
6880548 Schultz et al. Apr 2005 B2
6909891 Yamashita et al. Jun 2005 B2
6918756 Fredricks et al. Jul 2005 B2
6923643 Schultz et al. Aug 2005 B2
6925999 Hugghins et al. Aug 2005 B2
6990335 Shamoon et al. Jan 2006 B1
7024336 Salsbury et al. Apr 2006 B2
7055759 Wacker et al. Jun 2006 B2
7073365 Gebo et al. Jul 2006 B2
7083109 Pouchak Aug 2006 B2
7099748 Rayburn Aug 2006 B2
7101172 Jaeschke Sep 2006 B2
7111503 Brumboiu et al. Sep 2006 B2
7113086 Shorrock Sep 2006 B2
7127734 Amit Oct 2006 B1
7130719 Ehlers et al. Oct 2006 B2
7155305 Hayes et al. Dec 2006 B2
D535573 Barton et al. Jan 2007 S
7159789 Schwendinger et al. Jan 2007 B2
7185825 Rosen Mar 2007 B1
7188779 Alles Mar 2007 B2
7191826 Byrnes et al. Mar 2007 B2
7216016 Van Ostrand et al. May 2007 B2
7228693 Helt Jun 2007 B2
7241135 Munsterhuis et al. Jul 2007 B2
7257397 Shamoon et al. Aug 2007 B2
7293718 Sigafus et al. Nov 2007 B2
7327250 Harvey Feb 2008 B2
7343226 Ehlers et al. Mar 2008 B2
7385500 Irwin Jun 2008 B2
RE40437 Rosen Jul 2008 E
7392661 Alles Jul 2008 B2
7432477 Teti Oct 2008 B2
D580801 Takach et al. Nov 2008 S
7451017 McNally Nov 2008 B2
7451612 Mueller et al. Nov 2008 B2
7469550 Chapman, Jr. et al. Dec 2008 B2
7510126 Rossi et al. Mar 2009 B2
7555364 Poth et al. Jun 2009 B2
7571865 Nicodem et al. Aug 2009 B2
7574208 Hanson et al. Aug 2009 B2
7580775 Kujyk et al. Aug 2009 B2
7584021 Bash et al. Sep 2009 B2
7599808 Weekly Oct 2009 B2
7614567 Chapman et al. Nov 2009 B2
7636604 Bergman et al. Dec 2009 B2
7644869 Hoglund et al. Jan 2010 B2
7668532 Shamoon et al. Feb 2010 B2
7693809 Gray Apr 2010 B2
7707428 Poth et al. Apr 2010 B2
7720621 Weekly May 2010 B2
7735743 Jaeschke Jun 2010 B2
7768393 Nigam Aug 2010 B2
7784704 Harter Aug 2010 B2
7801646 Amundson et al. Sep 2010 B2
7802618 Simon et al. Sep 2010 B2
7812274 Dupont et al. Oct 2010 B2
7839275 Spalink et al. Nov 2010 B2
7848900 Steinberg Dec 2010 B2
7854389 Ahmed Dec 2010 B2
7861547 Major et al. Jan 2011 B2
7861941 Schultz et al. Jan 2011 B2
7904608 Price Mar 2011 B2
7908211 Chen et al. Mar 2011 B1
7918406 Rosen Apr 2011 B2
7945799 Poth et al. May 2011 B2
7949615 Ehlers et al. May 2011 B2
7953518 Kansal et al. May 2011 B2
7973678 Petricoin, Jr. et al. Jul 2011 B2
8018329 Morgan et al. Sep 2011 B2
8019567 Steinberg et al. Sep 2011 B2
8026261 Tam et al. Sep 2011 B2
8027518 Baker et al. Sep 2011 B2
8032254 Amundson et al. Oct 2011 B2
8064935 Shamoon et al. Nov 2011 B2
8065342 Borg et al. Nov 2011 B1
8078325 Poth Dec 2011 B2
8087593 Leen Jan 2012 B2
8090477 Steinberg Jan 2012 B1
8091795 McLellan et al. Jan 2012 B1
8091796 Amundson et al. Jan 2012 B2
8095340 Brown Jan 2012 B2
8115656 Bevacqua et al. Feb 2012 B2
8125332 Curran et al. Feb 2012 B2
8126685 Nasle Feb 2012 B2
8131401 Nasle Mar 2012 B2
8135413 Dupray Mar 2012 B2
8140279 Subbloie Mar 2012 B2
8141791 Rosen Mar 2012 B2
8146584 Thompson Apr 2012 B2
8150421 Ward et al. Apr 2012 B2
8180492 Steinberg May 2012 B2
8195313 Fadell et al. Jun 2012 B1
8204628 Schnell et al. Jun 2012 B2
8205244 Nightingale et al. Jun 2012 B2
8219114 Larsen Jul 2012 B2
8219249 Harrod et al. Jul 2012 B2
8229722 Nasle Jul 2012 B2
8229772 Tran et al. Jul 2012 B2
8232877 Husain Jul 2012 B2
8255090 Frader-Thompson et al. Aug 2012 B2
8269620 Bullemer et al. Sep 2012 B2
8280536 Fadell et al. Oct 2012 B1
8280559 Herman et al. Oct 2012 B2
8301765 Goodman Oct 2012 B2
8305935 Wang Nov 2012 B2
8315717 Forbes, Jr. et al. Nov 2012 B2
8323081 Koizumi et al. Dec 2012 B2
8332055 Veillette Dec 2012 B2
8334906 Lipton et al. Dec 2012 B2
8346396 Amundson et al. Jan 2013 B2
8350697 Trundle et al. Jan 2013 B2
8386082 Oswald Feb 2013 B2
8390473 Krzyzanowski et al. Mar 2013 B2
8406162 Haupt et al. Mar 2013 B2
8412381 Nikovski et al. Apr 2013 B2
8412654 Montalvo Apr 2013 B2
8428867 Ashley, Jr. et al. Apr 2013 B2
8433344 Virga Apr 2013 B1
8442695 Imes et al. May 2013 B2
8457796 Thind Jun 2013 B2
8457797 Imes et al. Jun 2013 B2
8498753 Steinberg et al. Jul 2013 B2
8509954 Imes et al. Aug 2013 B2
8510241 Seshan Aug 2013 B2
8510255 Fadell et al. Aug 2013 B2
8510421 Matsuzaki et al. Aug 2013 B2
8531294 Slavin et al. Sep 2013 B2
8543244 Keeling et al. Sep 2013 B2
8554374 Lunacek et al. Oct 2013 B2
8554714 Raymond et al. Oct 2013 B2
8556188 Steinberg Oct 2013 B2
8560127 Leen et al. Oct 2013 B2
8571518 Imes et al. Oct 2013 B2
8577392 Pai et al. Nov 2013 B1
8587445 Rockwell Nov 2013 B2
8596550 Steinberg et al. Dec 2013 B2
8606374 Fadell et al. Dec 2013 B2
8620393 Bornstein et al. Dec 2013 B2
8620841 Filson et al. Dec 2013 B1
8626344 Imes et al. Jan 2014 B2
8630741 Matsuoka et al. Jan 2014 B1
8634796 Johnson Jan 2014 B2
8648706 Ranjun et al. Feb 2014 B2
8666558 Wang et al. Mar 2014 B2
8670783 Klein Mar 2014 B2
8686841 Macheca et al. Apr 2014 B2
8718826 Ramachandran et al. May 2014 B2
8725831 Barbeau et al. May 2014 B2
8731723 Boll et al. May 2014 B2
8798804 Besore et al. Aug 2014 B2
8810454 Cosman Aug 2014 B2
8812024 Obermeyer et al. Aug 2014 B2
8812027 Obermeyer et al. Aug 2014 B2
8840033 Steinberg Sep 2014 B2
8868254 Louboutin Oct 2014 B2
8874129 Forutanpour et al. Oct 2014 B2
8876013 Amundson et al. Nov 2014 B2
8886178 Chatterjee Nov 2014 B2
8890675 Ranjan et al. Nov 2014 B2
8909256 Fraccaroli Dec 2014 B2
8918219 Sloo et al. Dec 2014 B2
8941489 Sheshadri et al. Jan 2015 B2
8954201 Tepper et al. Feb 2015 B2
8965401 Sheshadri et al. Feb 2015 B2
8965406 Henderson Feb 2015 B2
9020647 Johnson et al. Apr 2015 B2
9026261 Bukhin et al. May 2015 B2
9033255 Tessier et al. May 2015 B2
9055475 Lacatus et al. Jun 2015 B2
9071453 Shoemaker et al. Jun 2015 B2
9113298 Qiu Aug 2015 B2
9167381 McDonald et al. Oct 2015 B2
9168927 Louboutin Oct 2015 B2
9183530 Schwarz et al. Nov 2015 B2
9210125 Nichols Dec 2015 B1
9210545 Sabatelli et al. Dec 2015 B2
9215560 Jernigan Dec 2015 B1
9219983 Sheshadri et al. Dec 2015 B2
9247378 Bisson et al. Jan 2016 B2
9280559 Jones Mar 2016 B1
9288620 Menendez Mar 2016 B2
9292022 Ramachandran et al. Mar 2016 B2
9363638 Jones Mar 2016 B1
9307344 Rucker et al. Apr 2016 B2
9311685 Harkey et al. Apr 2016 B2
9313320 Zeilingold et al. Apr 2016 B2
9363636 Ganesh et al. Jun 2016 B2
9363772 Burks Jun 2016 B2
9396344 Jones Jul 2016 B1
9414422 Belghoul et al. Aug 2016 B2
9432807 Kern, Jr. et al. Aug 2016 B2
9433681 Constien et al. Sep 2016 B2
9449491 Sager et al. Sep 2016 B2
9477239 Bergman et al. Oct 2016 B2
9491577 Jones Nov 2016 B1
9495866 Roth et al. Nov 2016 B2
9521519 Chiou et al. Dec 2016 B2
9552002 Sloo et al. Jan 2017 B2
9560482 Frenz Jan 2017 B1
9589435 Finlow-Bates Mar 2017 B2
9594384 Bergman et al. Mar 2017 B2
9609478 Frenz et al. Mar 2017 B2
9618227 Drew Apr 2017 B2
9628951 Kolavennu et al. Apr 2017 B1
9635500 Becker et al. Apr 2017 B1
9645589 Leen et al. May 2017 B2
9674658 Partheesh et al. Jun 2017 B2
9900174 Gamberini Feb 2018 B2
9979763 Nichols May 2018 B2
20020147006 Coon et al. Oct 2002 A1
20020155405 Casey et al. Oct 2002 A1
20040034484 Solomita, Jr. et al. Feb 2004 A1
20050128067 Zakrewski Jun 2005 A1
20050172056 Ahn Aug 2005 A1
20050189429 Breeden Sep 2005 A1
20060063522 McFarland Mar 2006 A1
20060097063 Zeevi May 2006 A1
20060196953 Simon et al. Sep 2006 A1
20070037605 Logan Feb 2007 A1
20070043478 Ehlers et al. Feb 2007 A1
20070060171 Sudit et al. Mar 2007 A1
20070099626 Lawrence et al. May 2007 A1
20070114295 Jenkins May 2007 A1
20070235179 Phillips Oct 2007 A1
20070239316 Jelinek et al. Oct 2007 A1
20070249319 Faulkner et al. Oct 2007 A1
20080094230 Mock et al. Apr 2008 A1
20080098760 Seefeldt May 2008 A1
20080127963 Thompson Jun 2008 A1
20080143550 Ebrom et al. Jun 2008 A1
20080217419 Ehlers et al. Sep 2008 A1
20080262820 Nasle Oct 2008 A1
20090012704 Franco et al. Jan 2009 A1
20090143880 Amundson et al. Jun 2009 A1
20090171862 Harrod et al. Jul 2009 A1
20090187499 Mulder et al. Jul 2009 A1
20090240381 Lane Sep 2009 A1
20090302994 Rhee et al. Dec 2009 A1
20090308372 Nordberg et al. Dec 2009 A1
20100025483 Hoeynck Feb 2010 A1
20100034386 Choong et al. Feb 2010 A1
20100042940 Monday et al. Feb 2010 A1
20100065245 Imada et al. Mar 2010 A1
20100081375 Rosenblatt et al. Apr 2010 A1
20100084482 Kennedy et al. Apr 2010 A1
20100127854 Helvick et al. May 2010 A1
20100156628 Ainsbury et al. Jun 2010 A1
20100261465 Rhoads et al. Oct 2010 A1
20110015352 Steffen et al. Jan 2011 A1
20110046805 Bedros et al. Feb 2011 A1
20110148634 Putz Jun 2011 A1
20110153525 Benco et al. Jun 2011 A1
20110185895 Freen Aug 2011 A1
20110214060 Imes et al. Sep 2011 A1
20110314144 Goodman Dec 2011 A1
20120065802 Seeber et al. Mar 2012 A1
20120085831 Kopp Apr 2012 A1
20120095614 DeLayo Apr 2012 A1
20120172027 Partheesh et al. Jul 2012 A1
20120185101 Leen Jul 2012 A1
20120191257 Corcoran et al. Jul 2012 A1
20120209730 Garrett Aug 2012 A1
20120259466 Ray et al. Oct 2012 A1
20120284769 Dixon et al. Nov 2012 A1
20130073094 Knapton Mar 2013 A1
20130204441 Sloo et al. Aug 2013 A1
20130225196 James et al. Aug 2013 A1
20130226352 Dean-Hendricks et al. Aug 2013 A1
20130231137 Hugie et al. Sep 2013 A1
20130267253 Case et al. Oct 2013 A1
20130310053 Srivastava et al. Nov 2013 A1
20130318217 Imes et al. Nov 2013 A1
20130331087 Shoemaker et al. Dec 2013 A1
20130331128 Qiu Dec 2013 A1
20140031989 Bergman et al. Jan 2014 A1
20140031991 Bergman et al. Jan 2014 A1
20140039692 Leen et al. Feb 2014 A1
20140045482 Bisson et al. Feb 2014 A1
20140100835 Majumdar et al. Apr 2014 A1
20140156087 Amundson Jun 2014 A1
20140164118 Polachi Jun 2014 A1
20140172176 Deilmann et al. Jun 2014 A1
20140200718 Tessier Jul 2014 A1
20140244048 Ramachandran et al. Aug 2014 A1
20140248910 Dave et al. Sep 2014 A1
20140266635 Roth et al. Sep 2014 A1
20140266669 Fadell Sep 2014 A1
20140277762 Drew Sep 2014 A1
20140302879 Kim et al. Oct 2014 A1
20140313032 Sager et al. Oct 2014 A1
20140324410 Mathews Oct 2014 A1
20140330435 Stoner et al. Nov 2014 A1
20140337123 Neurenberg et al. Nov 2014 A1
20140349672 Kern et al. Nov 2014 A1
20140370911 Gorgenyi et al. Dec 2014 A1
20150065161 Ganesh et al. Mar 2015 A1
20150094860 Finnerty et al. Apr 2015 A1
20150100167 Sloo Apr 2015 A1
20150140994 Partheesh et al. May 2015 A1
20150141045 Qiu et al. May 2015 A1
20150156031 Fadell Jun 2015 A1
20150159895 Quam et al. Jun 2015 A1
20150163631 Quam et al. Jun 2015 A1
20150163945 Barton et al. Jun 2015 A1
20150167999 Seem Jun 2015 A1
20150180713 Stewart Jun 2015 A1
20150181382 McDonald et al. Jun 2015 A1
20150186497 Patton et al. Jul 2015 A1
20150228419 Fadell Aug 2015 A1
20150237470 Mayor Aug 2015 A1
20150271638 Menayas et al. Sep 2015 A1
20150285527 Kim Oct 2015 A1
20150301543 Janoso et al. Oct 2015 A1
20150309484 Lyman Oct 2015 A1
20150338116 Furuta et al. Nov 2015 A1
20150370272 Reddy et al. Dec 2015 A1
20150372832 Kortz et al. Dec 2015 A1
20160007156 Chiou et al. Jan 2016 A1
20160018122 Frank Jan 2016 A1
20160018800 Gettings Jan 2016 A1
20160018832 Frank Jan 2016 A1
20160054865 Kerr et al. Feb 2016 A1
20160057572 Bojorquez et al. Feb 2016 A1
20160142872 Nicholson et al. May 2016 A1
20160189496 Modi et al. Jun 2016 A1
20160195861 Chen Jul 2016 A1
20160223998 Songkakul Aug 2016 A1
20160261424 Gamberini Sep 2016 A1
20160286033 Frenz et al. Sep 2016 A1
20160313749 Frenz Oct 2016 A1
20160313750 Frenz et al. Oct 2016 A1
20170026506 Haepp et al. Jan 2017 A1
20170130979 Kolavennu et al. May 2017 A1
20170134214 Sethuraman et al. May 2017 A1
20170139580 Kimura May 2017 A1
20170171704 Frenz Jun 2017 A1
20170181100 Kolavennu et al. Jun 2017 A1
20170241660 Sekar et al. Aug 2017 A1
20180241789 Nichols Aug 2018 A1
Foreign Referenced Citations (45)
Number Date Country
2015201441 Oct 2015 AU
2202008 Oct 1998 CA
101689327 May 2013 CN
103175287 Jun 2013 CN
104704863 Jun 2015 CN
105318499 Feb 2016 CN
102013226390 Jun 2015 DE
0196069 Oct 1986 EP
1515289 Mar 2005 EP
2607802 Jun 2013 EP
2675195 Dec 2013 EP
3001116 Mar 2016 EP
59-106311 Jun 1984 JP
1-252850 Oct 1989 JP
2011203841 Oct 2011 JP
2012109680 Jun 2012 JP
2012000906 Sep 2012 MX
2006055334 May 2006 WO
2009034720 Mar 2009 WO
2009036764 Mar 2009 WO
WO 2009034720 Mar 2009 WO
WO 2009036764 Mar 2009 WO
2009067251 May 2009 WO
WO 2009067251 May 2009 WO
2011011404 Jan 2011 WO
WO 2011011404 Jan 2011 WO
2011121299 Oct 2011 WO
2012000107 Jan 2012 WO
WO 2012000107 Jan 2012 WO
2012068517 May 2012 WO
2013170791 Nov 2013 WO
WO 2013170791 Nov 2013 WO
2014016705 Jan 2014 WO
WO 2014016705 Jan 2014 WO
2014047501 Mar 2014 WO
WO 2014047501 Mar 2014 WO
2014055939 Apr 2014 WO
2014144323 Sep 2014 WO
WO 2014144323 Sep 2014 WO
2014197320 Dec 2014 WO
2014200524 Dec 2014 WO
WO 2014197320 Dec 2014 WO
2015047739 Apr 2015 WO
2015089116 Jun 2015 WO
2015164400 Oct 2015 WO
Non-Patent Literature Citations (86)
Entry
“BACnet Direct Digital Control Systems for HVAC,” Whole NOSC Facility Modernization, Greensboro, NC, GRN98471, 40 pages, Aug. 2009.
Aprilaire “Electronic Thermostats Model 8355 7 Day Programmable 2 Heat/2 Cool Heat Pump, User's Manual, Installation, and Programming,” pp. 1-16, Dec. 2000.
Bishop, “Adaptive Identification and Control of HVAC Systems,” USA CER, Technical Report E-85, 50 pages, Sep. 1985.
Braeburn, “Model 5200 Premier Series Programmable Thermostats. Up to 2 Heat/2 Cool 7 Day, 5-2 Day or Non-Programmable Conventional and Heat Pump,” 11 pages, 2011.
Braeburn, “Model 5300 Premier Series Universal Auto Changeover, Up to 3 Heat/2 Cool Heat Pump or 2 Heat/2Cool Conversion Thermostat, User Manual,” 2009.
California Energy Commission, “Buildings End-Use Energy Efficiency, Alternatives to Compressor Cooling,” 80 pages, Jan. 2000.
Carrier, “SYSTXCCUIZ01-V Infinity Control, Installation Instructions,” pp. 1-20, 2012.
Carrier, “TB-PAC, TB-PHP Base Series Programmable Thermostats, Installation Instructions,” 4 pages, 2012.
U.S. Appl. No. 14/640,984, filed Mar. 6, 2015.
U.S. Appl. No. 14/668,800, filed Mar. 25, 2015.
U.S. Appl. No. 14/696,662, filed Apr. 27, 2015.
U.S. Appl. No. 14/933,948, filed Nov. 5, 2015.
U.S. Appl. No. 14/934,543, filed Nov. 6, 2015.
U.S. Appl. No. 14/938,595, filed Nov. 11, 2015.
U.S. Appl. No. 14/938,642, filed Nov. 11, 2015.
U.S. Appl. No. 14/964,264, filed Dec. 9, 2015.
U.S. Appl. No. 14/964,349, filed Dec. 9, 2015.
DeLeeuw, “Ecobee Wifi Enabled Smart Thermostat Part 2: The Features Review,” 7 pages, Apr. 1, 2014.
Ecobee, “Smart Si Thermostat User Manual,” 44 pages, 2012.
Ecobee, “Smart Thermostat Installation Manual,” pp. 1-36, 2011.
Ecobee, “Smart Thermostat User Manual,” 20 pages, 2010.
Federspiel et al., “User Adaptable Comfort Control for HVAC Systems,” Proceedings of the 1992 American Control Conference, pp. 2312-2319, Jun. 24-26, 1992.
Fong et al., “A Robust Evolutionary Algorithm for HVAC Engineering Optimization,” HVAC C&R Research, vol. 14, No. 5, pp. 683-705, Sep. 2008.
Gao, “The Self-Programming Thermostat: Optimizing Setback Schedules Based on Home Occupancy Patterns,” BuildSys '09, 6 pages, Nov. 3, 2009.
Hai, “Omnistat RC-Series Electronic Communicating Thermostats,” 2 pages, prior to Jan. 13, 2011.
Honeywell, “45.801.175—Amplification Gas/Air Module for VK4105R/VK8105R Gas Controls,” 8 pages, prior to Oct. 18, 2006.
Honeywell, “FocusPRO 6000 Series Programmable Thermostat, User Guide,” 24 pages, Dec. 2013.
Honeywell, “FocusPRO TH6000 Series Programmable Thermostat, Operating Manual,” 26 pages, Mar. 2011.
Honeywell, “FocusPRO Wi-Fi TH6000 Series Programmable Thermostat, Installation Guide,” 36 pages, 2012.
Honeywell, “Perfect Climate Comfort Center Control System, Product Data,” 44 pages, Apr. 2001.
Honeywell, Prestige THX9321/9421 Operating Manual, 120 pages, Jul. 2011.
Honeywell, “T8611G Chronotherm IV Deluxe Programmable Heat Pump Thermostats, Installation Instructions,” 12 pages, 2002.
Honeywell, “T8624D Chronotherm IV Deluxe Programmable Thermostat, Product Data,” 20 pages, Oct. 1997.
Honeywell, “THX9321 Prestige 2.0 and THX9421 Prestige IAQ with EIM,” Product Data, 160 pages, Apr. 2013.
Honeywell, “VisionPRO IAQ, Installation Guide,”24 pages, Jul. 2009.
Honeywell, “VisionPRO TH8000 Series Installation Guide,” 12 pages, 2012.
Honeywell, “VisionPRO TH8000 Series Operating Manual,” 64 pages, 2007.
Honeywell, “VK41..R/VK81..R Series, Gas Controls with Integrated Gas/Air for Combined Valve and Ignition System,” 6 pages, prior to Oct. 18, 2006.
http://www.ecobee.com/solutions/whats-new/, “Introducing the New Smart Si Thermostat,” 1 page, printed Apr. 1, 2014.
http://www.regal-beloit.comgedrafthtml., “Regal-Beloit ECM, formerly GE ECM, Draft Inducer Motors, (44 Frame),” 1 page, printed Apr. 26, 2006.
Kuntze et al., “A New Fuzzy-Based Supervisory Control Concept for the Demand-Responsive Optimization of HVAC Control Systems,” Proceedings of the 37th IEEE Conference on Decision & Control, Tampa, Fl, pp. 4258-4263, 1998.
Lennox, “ComfortSense 5000 Series Models L5711U and 5732U Programmable Touch Screen Thermostats,” Owner's Guide, 32 pages, Feb. 2008.
Lennox, “G61MPV Series Unit, Installation Instructions,” 2 pages, Oct. 2006.
Lennox, “G61MPV Series Unit, Installation Instructions,” 68 pages, Jan. 2010.
Lennox, “Homeowner's Manual, Comfortsense 7000 Series, Model L7742U Touch Screen Programmable Thermostat,” 15 pages, May 2009.
Lennox, “icomfort Touch Thermostat, Homeowner's Manual,” Controls 506053-01, 20 pages, Dec. 2010.
Lu et al., “The Smart Thermostat: Using Occupancy Sensors to Save Energy in Homes,” Sensys'10, 14 pages, Nov. 3-5, 2010.
Luxpro, “Luxpro PSPU732T 3 Heating and 2 Cooling with Automatic Humidity Control and Dual Fuel Switch, Instruction Manual,” 48 pages, downloaded Apr. 5, 2014.
Robertshaw, “9620 7 Day Programmable 2 Heat/2Coo1 User's Manual,” 13 pages, 2001.
Robertshaw, “9801i2, 9825i2 Deluxe Programmable Thermostats, User's Manual,” 36 pages, Jul. 17, 2006.
Trane, “ComfortLink II Installation Guide,” 18-HD64D1-3, 20 pages, Aug. 2011.
Trane, “Communicating Thermostats for Fan Coil Control Echelon Version X13511543020, BACnet MS-TP Version X13511543010, User Guide,” 32 pages, May 3, 2011.
Trane, “TCONT600AF11MA Programmable Comfort Control, Installation Instructions,” Pub. No. 18-HD25D20-3, 16 pages, 2006.
Utkin et al., “Automobile Climate Control Using Sliding Mode,” IEEE International Electric Machines and Drives Conference, 18 pages, Jun. 17-20, 2001.
Venstar, “Commercial Thermostat T2900 7-Day Programmable Up to 3-Heat & 2 Cool, Owner's Manual,” 113 pages, Apr. 2008.
Venstar, “Residential Thermostat T5800 Owner's Manual and Installation Instructions,” 64, pages, downloaded Apr. 9, 2014.
Washington State University, Extension Energy Program, “Electric Heat Lock Out on Heat Pumps,” pp. 1-3, Apr. 2010.
White Rodgers, “Emerson Blue Wireless Comfort Interface 1F98EZ-1621 Homeowner User Guide,” 28 pages, downloaded Apr. 5, 2014.
www.networkthermostat.com, “Net/X Wifi Thermostat,” 2 pages, 2012.
Yan et al., “Iterative Learning Control in Large Scale HVAC System,” IEEE Proceedings of the 8th World Congress on Intelligent Control and Automation, Jul. 6-9, 2010, Jinan, China, 2010.
Zaheer-Uddin et al., “Optimal Control of Time-Scheduled Heating, Ventilating and Air Conditioning Processes in Buildings,” Energy Conversion & Management, vol. 41, pp. 49-60, 2000.
Zaheer-Uddin, “Digital Control of a Heat Recovery and Storage System,” Heat Recovery Systems & CHP, vol. 10, No. 5/6, pp. 583-593, 1990.
U.S. Appl. No. 15/048,902, filed Feb. 19, 2016.
Balaji et al., “Sentinel: Occupancy Based HVAC Actuation Using Existing WiFi Infrastructure Within Commercial Buildings,” SenSys '13, 14 pages, Nov. 11-15, 2015.
“Petition for Inter Partes Review of U.S. Pat. No. 8,571,518 Pursuant to 35 U.S.C. 311-319, 37 CFR 42,” Inventor Imes et al., dated Oct. 29, 2014.
Do, “Programmable Communicating Thermostats for Demand Response in California,” DR ETD Workshop, 26 pages, Jun. 11, 2007.
Green, “PM's Thermostat Guide,” Popular Mechanics, pp. 155-158, Oct. 1985.
Gupta et al., “Adding GPS-Control to Traditional Thermostats: An Exploration of Potential Energy Savings and Design Challenges,” Pervasive, LNCS 5538, pp. 95-114, 2009.
Gupta, “A Persuasive GPS-Controlled Thermostat System,” 89 pages, Sep. 2008.
http://community.lockitron.com/notifications-geofencing-scheduling-sense-bluetooth/633, “Lockitron Community, Notifications, Geofencing, Scheduling, Sense/Bluetooth,” 14 pages, printed Oct. 29, 2014.
http://stackoverflow.com/questions/14232712/tracking-multiple-20-locations-with-ios-geofencing, “Tracking Multiple (20+) Locations with iOS Geofencing—Stack Overflow,” 2 pages, printed Oct. 29, 2014.
http://www.allure-energy.com/aenf_jan9_12.html, “CES Gets First Look at EverSense,” Allure Energy, 2 pages, printed Feb. 17, 2015.
http:/IWww.prnev.tswire.com/nev.ts-releases/allure-energy-unveils-a-combination-of-ibeacon-and-nfc-enabled-smart-sensor-technology-known-as-aura-23885 . . . , “Allure Energy Unveils a Combination of iBeacon and NFC Enabled Smart Sensor Technology Known as Aura,” 6 pages, Jan. 6, 2014.
Mobile Integrated Solutions, LLC, “MobiLinc Take Control of Your Home, MobiLinc and Geo-Fence Awareness,” 9 pages, downloaded Mar. 27, 2015.
Pan et al., “A Framework for Smart Location-Based Automated Energy Controls in a Green Building Testbed,” 6 pages, downloaded Jan. 30, 2015.
SmartThings Inc., “2 Ecobee Si Thermostat + Geofencing,” 17 pages, downloaded Nov. 3, 2014.
Allure Energy, “Our Technology,” http://www.allure-energy.com/pages/about.jsp 1 page, printed May 30, 2012.
The Extended European Search Report for EP Application No. 16195639.6, dated May 31, 2017.
The International Search Report for PCT Application No. PCT/US2010/042589 dated Nov. 22, 2010.
Mozer, “The Neural Network House: An Environment that Adapts to Its Inhabitants,” Department of Computer Science, University of Colorado, 5 pages, downloaded May 29, 2012.
The Extended European Search Report and Opinion for EP Application No. 16156760.7-1862, dated Jul. 8, 2016.
The Extended European Search Report for EP Application No. 1619416, dated Feb. 2, 2017.
The Extended European Search Report for EP Application No. 16196128.9, dated Mar. 7, 2017.
Gentec, “Feature Focus, Threat Level Management,” 2 pages, 2013.
Scanlon et al., “Mutual Information Based Visual Feature Selection for Lipreading,” 8th International Conference on Spoken Language Processing, 5 pages, Oct. 4-8, 2004.
Transportation Research Board of the National Academies, “Commuting in America III, the Third National Report on Commuting Patterns and Trends,” 199 pages, 2006.
Related Publications (1)
Number Date Country
20160313749 A1 Oct 2016 US