The present disclosure pertains generally to systems for managing building systems and more particularly to systems for managing a HVAC system within a building.
Building control systems are often used to help control a building's environment, such as the temperature, humidity, air quality, lighting, security and other aspects of a building's environment. An example building control system may include a Heating, Ventilation, and/or Air Conditioning (HVAC) system used to control the comfort level within a building. Another example building control system may include a lighting controller that controls the lighting in the building. Another example building control system may include a security system controller that controls the security of the building.
Many building control systems have a master or central building controller. Such a building controller may have a user interface for allowing designated users to interact with the building controller. In some cases, some users may be restricted as to the kinds of changes that they can make to the operation of the building control system. For example, a tenant or occupant of a building may be more restricted as to the kinds of changes that can be made relative to, for example, a facility management staff member. What would be desirable is a system and method that allows occupants of a building to interact with a building control system in an easy and intuitive manner, and in some cases, get the facility management staff involved when necessary.
The disclosure relates generally to systems for managing operation of building control systems. In a particular example of the disclosure, a building management system is configured to control the operation of one or more building system components of a building. The building management system includes an I/O port for operative coupling to a remote user interface as well as a controller that is operatively coupled to the I/O port. The controller is configured to provide a natural language interaction on the remote user interface via the I/O port and to receive one or more building management requests from one or more users as well as to ascertain whether the received one or more building management requests can be carried out by the building management system. The controller is further configured to instruct the one or more building system components of the building to carry out the received one or more building management requests unless one or more building management requests cannot be carried out, whereby the controller provides one or more natural language messages on the remote user interface via the I/O port that informs the user that one or more of the building management requests cannot be carried out by the building management system.
In another example of the disclosure, an HVAC management system is configured to control operation of one or more HVAC system components of a building. The HVAC management system includes an I/O port for operative coupling to a remote user interface and a controller that is operatively coupled to the I/O port. The controller is configured to provide a natural language interaction on the remote user interface via the I/O port and to receive one or more HVAC comfort requests from one or more users, to determine an HVAC operational parameter change in response to one or more of the HVAC comfort requests and to instruct the one or more HVAC system components to institute the determined HVAC operational parameter change for a period of time, and then to return to a previous setting for the HVAC operational parameter.
In another example of the disclosure, an HVAC management system is configured to control operation of one or more HVAC system components of a building. The HVAC management system includes an I/O port for operative coupling to a remote user interface and a controller that is operatively coupled to the I/O port. The controller is configured to provide a natural language interaction on the remote user interface via the I/O port and to receive one or more HVAC comfort requests from one or more users, to determine a location of the user within the building that is making one or more of the HVAC comfort requests, to determine an HVAC operational parameter change for a specific HVAC zone from a plurality of HVAC zones that corresponds to the determined location of the user that is making one or more of the HVAC comfort requests and to instruct the one or more HVAC system components to institute the determined HVAC operational parameter change in the specific HVAC zone.
The preceding summary is provided to facilitate an understanding of some of the features of the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments of the disclosure in connection with the accompanying drawings, in which:
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.
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.
In some cases, one or more building controllers 20 may control at least some functions and/or operation of the building components 16. For example, a building controller 20a may be operably coupled to the building component 16a while a building controller 20b may be operably coupled to the building component 16b and to the building component 16c. This is just an example, as a particular building controller 20 may control functions and/or operation of any number of the building components 16. In some instances, as shown, the building controllers 20 may be operably coupled to a building network 22, but this is not required in all instances.
A user 24 may be disposed within the building 14. It will be appreciated that while one user 24 is shown, the building 14 may include any number of different users 24. In some cases, the user 24 (or one or more of a plurality of users 24) may desire a change in operation of one or more of the building components 16. For example, the user 24 may desire to alter operation of a security system, such as but not limited to turning the security system on or off, or perhaps canceling a false alarm. The user 24 may desire to make changes in a global lighting scheme within the building 14, or perhaps just change the lighting in their particular portion of the building 14. In some cases, the user 24 may feel uncomfortable, expressing for example that they feel cold, or that they feel hot. The user 24 may express that their particular portion of the building 14 is stuffy, and thus is in need of ventilation. Accordingly, the user 24 may express a desire for, for example, cool air, warm air, and/or fresh air, among other things.
The user 24 may indicate their desire for a change in operation of one or more of the building components 16 by using a remote user interface 26. In this, “remote” indicates that the remote user interface 26 is remote, or at a different location, from a building management system 12. The building management system 12 may be at a particular location within the building or outside of the building such as in the cloud. The building management system 12 may provide a centralized control function for the building system 10. The remote user interface 26 may be accessible to the user 24 from within the building 14. For example, the remote user interface 26 may be manifested within an application running on a smartphone of the user 24. In some cases, the remote user interface 26 may be a chat bot running on a computer that the user 24 is using (at the user's desk). The remote user interface 26 may be a textual interface, or may utilize voice recognition. In some cases, the remote user interface 26 may receive voiced statements from the user 24, and in response the remote user interface 26 may talk back to the user 24 in an interactive manner. These are just examples.
It will be appreciated that various conditions, including lighting and environmental conditions such as temperature and ventilation may vary from zone to zone, or even within various portions of a single zone. It will also be appreciated that individual users 24 may have differing preferences. Perhaps the user 24a is always cold, while the user 24b is always hot, for example. Accordingly, the building management system 12 (
In some cases, before determining what, if anything, to do in response, the building management system 12 may determine the location of the user 24 issuing a comfort request. In the example shown in
In some cases, the building management system 12 may create a natural language interaction on the remote user interface 26 in order to ascertain the current location of the user. In some instances, the building management system 12 may instead ask one or more questions of the user via the remote user interface 26, such as “Are you at your desk?”, or “What is your name?”, or perhaps “Are you in the conference room?”, or “Are you in the lunchroom?”. It will be appreciated that these examples are merely illustrative, and are not intended to be limiting in any manner.
In some cases, the controller 42 may be configured to ascertain whether the one or more building management requests received from the users can actually be carried out by the building management system 12. There are a variety of reasons that a particular building management request could not be carried out. For example, the controller 42 may determine that one or more of the building management requests cannot be carried out due to a building system component equipment fault. In other words, one or more of the building system components 44a-44b may not be working properly. In some cases, if there is a building system component fault, the controller 42 may be configured to provide an alert via the I/O port to a building manager regarding the one or more building management requests that cannot be carried out due to the building system component equipment fault(s).
As another example, the controller 42 may determine that one or more of the received building management requests cannot be carried out due to a conflict with another one of the received building management requests. This might occur, for example, if one user 24 says “I am cold” while another user 24, who is in the same zone, or even in the same office, says “I am hot”.
As another example, the controller 42 may determine that one or more of the received building management requests cannot be carried out because doing so would result in a building system parameter being outside of a predefined allowable range. In some cases, if the building components 44a-44b are HVAC components currently set in a heating mode, a user request that would require air conditioning may not be able to be carried out. As another example, if there is an allowable temperature range, in the heating mode, of 65 to 78 degrees, and the current temperature is already 78 degrees, any further increase would violate the allowable temperature range.
The controller 42 may be further configured to instruct the building system components 44a-44b of the building 14 to carry out the received one or more building management requests unless the one or more building management requests cannot be carried out, whereby the controller 42 provides one or more natural language messages on the remote user interface via the I/O port that informs the user that the one or more of the building management requests cannot be carried out by the building management system 12. In some cases, the controller 42 may be configured to institute a temporary change in operation of the building system components 44a-44b in response to one or more of the building management requests, and then to return the one or more building system components 44a-44b after a predetermined period of time. In other cases, the controller 42 may be configured to institute a permanent change (e.g. until a user changes again) in operation of the building system components 44a-44b in response to one or more of the building management requests.
In some cases, the controller 42 may be configured to enable a user to create an event via the remote user interface 26 by specifying one or more comfort parameters for a zone within the building 14 and a date and time of the created event, and once created, the controller 42 may be configured to instruct the building system components 44a-44b that correspond to the zone to operate in accordance with the one or more comfort parameters at the date and time of the created event. For example, a user at a school may create an event for the gym on the following Friday from 3:00-4:00 PM, and the controller 42 may instruct the building system components that correspond to the gym to operate in accordance with occupied comfort parameters on Friday from 3:00-4:00 PM. The occupied comfort parameters may pre-defined and may be more comfortable but less energy efficient than un-occupied parameters.
In some cases, the controller 42 may be configured to automatically learn one or more future operations of the building system components 44a-44b based on one or more received building management requests from the user. For example, in some cases, the controller 42 may be configured to execute a learning algorithm that schedules a learned event in the future operation of one or more building system components based on one or more of the received building management requests from the user. For example, a particular user 24 may express “I am cold” every day after lunch. The controller 42 may learn this, and automatically increase a temperature set point each day at 1 pm in a particular zone corresponding to the location of the particular user 24. In another example, the controller 42 may learn that a large number of users congregate in the lunch room each day around 9 am for a coffee break, and the corresponding collective body heat causes one or more users 24 each day to express “I am hot” at that time. Accordingly, the controller 42 may learn to drop the temperature in the lunch room starting each day at 8:30 am. These are just examples.
The controller 54 may be configured to determine an HVAC operational parameter change in response to one or more of the HVAC comfort requests and to instruct the one or more HVAC system components 56 to institute the determined HVAC operational parameter change. In some cases, the determined HVAC operational parameter change is instituted for a period of time, and then returned to the previous setting for the HVAC operational parameter. While an HVAC system component 56a and an HVAC system component 56b are illustrated, it will be appreciated that there may be a single HVAC system component 56, or a plurality of HVAC system components 56. In some cases, at least some of the HVAC system components 56 may be variable air volume (VAV) boxes.
In some cases, the controller 54 may be configured to communicate with the one or more HVAC system components 56 in order to confirm that the determined HVAC operational parameter change is being executed. The period of time during which the determined HVAC operational parameter change is instituted and in effect may be an adjustable time period. For example, the period of time may default to a relatively short period of time, say ten minutes or twenty minutes. However, if a particular user is making a request for a new change shortly after the previous change expired, the controller 54 may automatically lengthen the period of time in order to reduce the number of requests and/or to improve the comfort of that particular user, as long as accommodating that particular user isn't contrary to other user's comfort requests.
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.
This application is a continuation of co-pending U.S. patent application Ser. No. 16/443,828, filed Jun. 17, 2019, entitled BUILDING MANAGEMENT SYSTEM WITH NATURAL LANGUAGE INTERFACE, which claims the benefit of U.S. Provisional Application Ser. No. 62/688,934 filed Jun. 22, 2018, entitled BUILDING MANAGEMENT SYSTEM WITH NATURAL LANGUAGE INTERFACE, both of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4598397 | Nelson et al. | Jul 1986 | A |
5086385 | Launey et al. | Feb 1992 | A |
6052666 | Diehl et al. | Apr 2000 | A |
6408272 | White et al. | Jun 2002 | B1 |
6413079 | Lyons et al. | Jul 2002 | B1 |
6988070 | Kawasaki et al. | Jan 2006 | B2 |
7031438 | Cheston, III et al. | Apr 2006 | B1 |
7403838 | Deen et al. | Jul 2008 | B2 |
7447635 | Konopka et al. | Nov 2008 | B1 |
7720683 | Vermeulen et al. | May 2010 | B1 |
7831426 | Bennett | Nov 2010 | B2 |
7933777 | Koll | Apr 2011 | B2 |
7957974 | Cho et al. | Jun 2011 | B2 |
8321444 | Mowatt et al. | Sep 2012 | B2 |
8340975 | Rosenberger | Dec 2012 | B1 |
8346794 | Cheng et al. | Jan 2013 | B2 |
8396710 | White et al. | Mar 2013 | B2 |
8630742 | Stefanski et al. | Jan 2014 | B1 |
8666963 | Sejnoha et al. | Mar 2014 | B2 |
8818789 | Abir | Aug 2014 | B2 |
8831957 | Taubman et al. | Sep 2014 | B2 |
8868428 | Gruenstein et al. | Oct 2014 | B2 |
9058390 | Barve et al. | Jun 2015 | B2 |
9472205 | Kolavennu et al. | Oct 2016 | B2 |
9495962 | Govrin et al. | Nov 2016 | B2 |
9542956 | Nostrant | Jan 2017 | B1 |
9851728 | Matsuoka | Dec 2017 | B2 |
9875741 | Gelfenbeyn et al. | Jan 2018 | B2 |
10042338 | Cifteli et al. | Aug 2018 | B2 |
10145579 | Stoner et al. | Dec 2018 | B2 |
10360304 | Alvarez et al. | Jul 2019 | B1 |
20020034956 | Mekuria | Mar 2002 | A1 |
20020069063 | Buchner et al. | Jun 2002 | A1 |
20030088642 | Price et al. | May 2003 | A1 |
20030093272 | Soufflet et al. | May 2003 | A1 |
20030187659 | Cho et al. | Oct 2003 | A1 |
20040019489 | Funk et al. | Jan 2004 | A1 |
20040193603 | Jubicich | Sep 2004 | A1 |
20050149496 | Mukherjee et al. | Jul 2005 | A1 |
20060142880 | Deen et al. | Jun 2006 | A1 |
20070256435 | Koyama | Nov 2007 | A1 |
20070286181 | Bushmitch et al. | Dec 2007 | A1 |
20070288129 | Komer et al. | Dec 2007 | A1 |
20080147397 | Konig et al. | Jun 2008 | A1 |
20080175261 | Wang | Jul 2008 | A1 |
20080233983 | Park et al. | Sep 2008 | A1 |
20090143918 | Amundson et al. | Jun 2009 | A1 |
20090204410 | Mozer et al. | Aug 2009 | A1 |
20100030734 | Chunilal | Feb 2010 | A1 |
20100223055 | McLean | Sep 2010 | A1 |
20100286985 | Kennewick et al. | Nov 2010 | A1 |
20100332235 | David | Dec 2010 | A1 |
20110046792 | Imes et al. | Feb 2011 | A1 |
20120059658 | Sejnoha et al. | Mar 2012 | A1 |
20120066286 | Heredia et al. | Mar 2012 | A1 |
20120123561 | Park et al. | May 2012 | A1 |
20120158161 | Cohn et al. | Jun 2012 | A1 |
20120232886 | Capuozzo et al. | Sep 2012 | A1 |
20130006400 | Caceres et al. | Jan 2013 | A1 |
20130031476 | Coin et al. | Jan 2013 | A1 |
20130117395 | Buschmitch et al. | May 2013 | A1 |
20130138250 | Mowery | May 2013 | A1 |
20130183944 | Mozer et al. | Jul 2013 | A1 |
20140058567 | Matsuoka et al. | Feb 2014 | A1 |
20140163751 | Davis et al. | Jun 2014 | A1 |
20140223465 | Hatambeiki et al. | Aug 2014 | A1 |
20140033056 | Venkatesha et al. | Nov 2014 | A1 |
20140330435 | Stoner | Nov 2014 | A1 |
20140330569 | Kolavennu et al. | Nov 2014 | A1 |
20140379323 | Anastasakos et al. | Dec 2014 | A1 |
20150053781 | Nelson et al. | Feb 2015 | A1 |
20150088518 | Kim et al. | Mar 2015 | A1 |
20150142180 | Matsuoka | May 2015 | A1 |
20150277681 | Isaacson et al. | Oct 2015 | A1 |
20150348551 | Gruber et al. | Dec 2015 | A1 |
20160091217 | Verberkt et al. | Mar 2016 | A1 |
20160095189 | Vangeel et al. | Mar 2016 | A1 |
20160335264 | Behal et al. | Nov 2016 | A1 |
20160377305 | Kwa | Dec 2016 | A1 |
20160378080 | Uppala et al. | Dec 2016 | A1 |
20170024465 | Yeh et al. | Jan 2017 | A1 |
20170161268 | Badaskar | Jun 2017 | A1 |
20170163435 | Ehsani et al. | Jun 2017 | A1 |
20180024520 | Sinha et al. | Jan 2018 | A1 |
20180031265 | Janniello | Feb 2018 | A1 |
20180061213 | Morehead | Mar 2018 | A1 |
20180129181 | Kratzer, III et al. | May 2018 | A1 |
20180266718 | Gillette | Sep 2018 | A1 |
20180299840 | Sinha | Oct 2018 | A1 |
20180313566 | Nemcek et al. | Nov 2018 | A1 |
20180347840 | Nelson et al. | Dec 2018 | A1 |
20180367484 | Rodriguez et al. | Dec 2018 | A1 |
20190072290 | Stoner | Mar 2019 | A1 |
20190130915 | Nitz et al. | May 2019 | A1 |
20190147883 | Mellenthin et al. | May 2019 | A1 |
20190353379 | Lee et al. | Nov 2019 | A1 |
20210080139 | Brown | Mar 2021 | A1 |
20210223750 | Joshi | Jul 2021 | A1 |
20210381861 | Brown | Dec 2021 | A1 |
Number | Date | Country |
---|---|---|
2017210578 | Aug 2017 | AU |
201225714 | Apr 2009 | CN |
101947788 | Jan 2011 | CN |
202092667 | Dec 2011 | CN |
102332204 | Jan 2012 | CN |
102436273 | May 2012 | CN |
107062528 | Aug 2017 | CN |
1054387 | Nov 2000 | EP |
1119191 | Jul 2001 | EP |
0986808 | Feb 2002 | EP |
1260886 | Nov 2002 | EP |
1135757 | Nov 2006 | EP |
1345360 | Dec 2006 | EP |
1415218 | Feb 2011 | EP |
2738478 | Jun 2014 | EP |
2738478 | Aug 2014 | EP |
2801972 | Dec 2014 | EP |
2094508 | Sep 1982 | GB |
3803045 | Aug 2006 | JP |
2006208460 | Aug 2006 | JP |
2006317573 | Nov 2006 | JP |
4503310 | Jul 2010 | JP |
2010181064 | Aug 2010 | JP |
4533844 | Sep 2010 | JP |
2010236759 | Oct 2010 | JP |
4640178 | Mar 2011 | JP |
4839605 | Dec 2011 | JP |
20100026353 | Mar 2010 | KR |
20110012048 | Feb 2011 | KR |
20110045314 | May 2011 | KR |
20120017492 | Feb 2012 | KR |
101151571 | May 2012 | KR |
9313507 | Jul 1993 | WO |
9855992 | Dec 1998 | WO |
9934339 | Jul 1999 | WO |
2006126192 | Nov 2006 | WO |
2007101164 | Sep 2007 | WO |
2008018102 | Feb 2008 | WO |
2009107211 | Mar 2009 | WO |
2009147927 | Dec 2009 | WO |
2014124353 | Aug 2014 | WO |
Entry |
---|
“Icomfort Wi-Fi Thermostat: Touch Screen Programmable Communicating Thermostat,” Lennox, 21 pages, Sep. 2012. |
The Extended European Search Report for EP Application No. 14806841.4, dated Jan. 24, 2017. |
“Kelvin Talking Thermostat,” Accenda Products, 2 pages, Dec. 9, 2013. |
“Kelvin Installation Manual,” Action Talking Products LLC, vol. 1.5, 8 pages, 2004, 2005. |
U.S. Appl. No. 14/737,076, “User Interaction with Building Controller Device Using a Remote Server and a Duplex Connection,” Filed Jun. 11, 2015. |
“A Thermostat that Speaks to a Consumer's Needs”, Storify, 3 pages, Jul. 14, 2015. |
“Automated Living Control,” HAL, 1 page, Dec. 9, 2013. |
“Voice IR Environmental Voice Controller,” Broadened Horizons, 17 pages, Dec. 9, 2013. |
Brown et al., “Joint DOD Industry Study on Opportunities in Integrated Diagnostics,” 110 pages, Jan. 1990. |
“Comfort System VVTIII,” Carrier, 6 pages, Aug. 1996. |
Caravalho et al., “Voice Thermostat Remote Control,” The Institute of Electrical and Electronics Engineers, Inc. 4 pages, 1999. |
“CEM 24 Series,” Systems Controls and Instruments, LLC, 32 pages, Jan. 2010. |
“Hints for Homeowners A Thermostat That Speaks to a Consumers Needs,” Coleman, 1 page, date accessed, Jun. 26, 2019. |
Walters, “Siri hack allows voice control of home thermostat,” 2 pages, Nov. 21, 2011. |
“SiriProxy-Nest Learning Thermostat,” GitHubchilitechno, 3 pages, Jan. 6, 2014. |
“SiriProxy,” GithubPlamoni, 7 pages, Dec. 9, 2013. |
“P7600A Network Compatible Computer Room Air Conditioning (CRAC) Program Module for W7600 Control Module,” Honeywell, 72 pages, 1993. |
“Voice Recognition & Voice Interactive Products,” Innotech Systems Inc., 1 page, Dec. 9, 2013. |
Jacobson, “Design: A Voice Activated Thermostat,” Biomedical Sciences Instrumentation, vol. 28, 6 pages, 1992. |
“Assistive Technology Transfer Update,” Kohler, vol. 1, Issue 1 (Spring) 2 pages, 1999. |
Lacquet et al., “An Affordable Digital-Display-to-Natural-Voice Converter for Visually Impaired Radio Amateurs,” IEEE Transactions on Rehabilitation Engineering, vol. 4 (4): 6 pages, Dec. 1996. |
Lee et al., “Fault Detection in an Air-Handling Unit Using Residual and Recursive Parameter Identification Methods,” ASHRAE Transactions, vol. 102, Pt. 1, 12 pages, 1996. |
Lopez et al., “Temperature and Humidity Laboratory Remote Controller,” Journal of the Mexican Society of Instrumentation, vol. 3: (6), pp. 14-20, Jun. 1996. |
Miles et al., “An Audible Thermostat for the Blind or Visually Challenged,” IEEE, pp. 68-69, 1997. |
International Search Report and Written Opinion for Application No. PCT/US2013/039326. 5 pages, dated, Aug. 6, 2013. |
Piette et al., “Model-Based Chiller Energy Tracking for Performance Assurance at a University Building,” Environmental Energy Technologies Division, pp. 1-13, Sep. 1997. |
“Telephone Controlled Thermostat,” RCI Automation LLC, 4 pages, Dec. 9, 2013. |
“Talking Thermostat Model VT3000 User's Guide,” SmartWay Solutions, Inc., pp. 1-20, accessed on Jun. 25, 2019. |
“Stargate Interactive Automation System,” JDS Technologies, 9 pages, May 9, 2013. |
“Accessible Thermostat” T2RERC Rehabilitation Engineering Research Center on Technology Transfer, pp. 1-40, accessed on Jun. 25, 2019. |
Watt, “Development of Empirical Temperature and Humidity-Based Degraded Condition Indicators for Low-Tonnage Air Conditioners,” A Thesis, The Office of Graduate Studies of Texas A&M University, 205 pages, Dec. 1997. |
“Comfort Call Owners Manual,” Venstar Inc., 23 pages, Aug. 2007. |
“Talking Thermostats for Persons who are Blind,” The Ezra Group, LLC 3 pages, Dec. 12, 2013. |
Watt et al., “Predictive Maintenance Programs (PMP's) in Small HVAC Applications: Analysis of Available Products and Technology,” Texas Engineering Experiment Station, 4 pages, Apr. 1994. |
“VIP 3000 Residential Talking Thermostat That Promotes Independent Living,” The Ezra Group LLC, 2 pages, date accessed Jun. 26, 2019. |
Segran, “Introducing The First Voice-Activated Hotel Room,” Fast Company, Business and Innovation, 7 pages, Aug. 24, 2016. |
International Search Report and Written Opinion for PCT/US2018/014930, dated May 8, 2018. |
The European Search Report for EP Application No. 14165437.6, dated Aug. 7, 2014. |
Dreilinger et al., “Experiences with Selecting Search Engines Using Metasearch,” ACM Transactions on Information Systems, vol. 15, No. 3, pp. 195-222, Jul. 1997. |
http://federatedsearchblog.com/2009/01/30/steven-bell-on-the-future-of-federated-search/, “Steven Bell on the Future of Federated Search,” 3 pages, printed Feb. 7, 2017. |
https://en.wikipedia.org/wiki/Federated_search, “Federated Search, From Wikipedia, the Free Encyclopedia,” 4 pages, printed Feb. 7, 2017. |
https://en.wikipedia.org/wiki/Search_aggregator, “Search Aggregator, From Wikipedia, the Free Encyclopedia,” 2 pages, printed Mar. 27, 2017. |
EP19181562, European Search Report, pp. 8, Dec. 12, 2019. |
European Extended Search Report, EP Application No. 19181562.0, Dec. 19, 2021 (8 pages). |
Number | Date | Country | |
---|---|---|---|
20220018565 A1 | Jan 2022 | US |
Number | Date | Country | |
---|---|---|---|
62688934 | Jun 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16443828 | Jun 2019 | US |
Child | 17491877 | US |