WO2024155512A1

WO2024155512A1 - Systems and methods for heat pump systems with demand response and/or reduced power consumption

Info

Publication number: WO2024155512A1
Application number: PCT/US2024/011267
Authority: WO
Inventors: Parimal Jagdish NILANGEKAR; Hiram Osuna Carrasco; Jorge Miguel Gamboa REVILLA
Original assignee: Rheem Manufacturing Company
Priority date: 2023-01-18
Filing date: 2024-01-11
Publication date: 2024-07-25

Abstract

Systems and methods are provided for heat pump systems, including water heaters and/or pool heaters, which are capable of communication with one or more utility devices and adjusting operation of the heat pump based on power reduction requests received from the utility devices. For example, a utility company may request a decrease of energy consumption from a device at peak times. The heat pump may include a utility communication port, which may be a CTA-2045 port or may be compliant with any other standardized demand response protocol. The heat pump control system may determine whether or not to reduce power consumption based on the request and may further decide how to adjust operation of the heat pump to comply with the request for decreased energy consumption.

Description

SYSTEMS AND METHODS FOR HEAT PUMP SYSTEMS WITH DEMAND RESPONSE AND/OR REDUCED POWER CONSUMPTION

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Patent Application Serial No. 63/439,771, filed January 18, 2023, the entire contents of which are incorporated herein by reference.

TECHNICAL FIELD

[0002] The present disclosure is generally in the field of heat pumps. For example, systems and methods are provided herein for heat pumps with demand response and/or reduced power consumption.

BACKGROUND

[0003] Heat pump systems including water heaters and pool heaters heat liquids such as water for residential and commercial use. For example, heat pump systems are commonly used to heat water in a residential setting for bathing and/or to warm water of a residential or community pool. Further, water heater systems may be used commercially in a manufacturing process, for example. Heat pump systems can also be used to heat and/or cool residential and/or commercial structures.

[0004] In some instances, demand for warm water may be highest at certain times. For example, in large metropolitan cities, hundreds of residential units of a single building may demand heated water at similar times (e.g., at 8:00 am in the morning). Multiple water heaters may be installed in such buildings and may be tasked with heating the water to appropriate temperatures. At peak times, the power consumption required to operate the water heaters to produce the desired heated water may be quite high. The power demand may be even higher during the winter season when the exterior temperature can reach temperatures below freezing. Similar power demands may be present in commercial facilities and manufacturing plants requiring large volumes of heated water.

[0005] Given the ever-increasing reliance on electronic compliances and various electrically powered machines, demand across the electrical infrastructure has never been greater. Efforts have been made to regulate the electrical grid. For example, OpenADR is a message exchange protocol that has been developed to manage energy resources using demand response messaging. Similarly, ANSI/CTA-2045 specifies a modular communications interface (MCI) to facilitate communications with residential devices for applications such as energy management. However, heat pumps such as water heaters and pool heaters have not fully integrated or implemented such standards and technologies for achieving reduced power consumption and energy management.

[0006] Accordingly, there is a need for improved methods and systems for effectively implementing reduced power consumption and energy' management on heat pump systems including water heater and pool heater systems.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 is a schematic illustration of a heat pump system with a utility communication port in communication with a utility device and a controller in communication with a server and/or a remote controller in accordance with one or more example embodiments of the disclosure.

[0008] FIG. 2 is a schematic illustration a heat pump system with a controller in communication with a utility device, a server, and/or a remote controller in accordance with one or more example embodiments of the disclosure.

[0009] FIG. 3 is a schematic illustration of an example data flow for operating a heat pump based on communication betw een a utility' device and a utility' communication device of the heat pump in accordance with one or more example embodiments of the disclosure.

[0010] FIG. 4 is a schematic illustration of an example process flow for adjusting operation of a heat pump based on a request for reduced power consumption from a utility device in accordance w ith one or more example embodiments of the disclosure.

[0011] FIG. 5 is a schematic illustration a heat pump system with a utility' communication port and a controller in communication with a utility device and external power systems, a server, and/or a remote controller in accordance with one or more example embodiments of the disclosure.

[0012] FIG. 6 is a schematic block diagram of a heat pump system in accordance w ith one or more example embodiments of the disclosure.

DETAILED DESCRIPTION

[0013] Heat pump systems have been developed which are capable of communication with one or more utility devices and adjusting operation of a heat pump, including water heaters and/or pool heaters, based on power consumption requests received from the utility devices. For example, a utility device may be any computing device of a utility company or entity such as one or more servers of the utility company. In one example, a utility' company may send a request to reduce power consumption to certain devices within a sector or area of a utility grid. A utility communication port or a controller may receive. The utility' communication port may communicate the request to the controller. The controller may either alone or together with a server and/or remote controller determine whether and/or how to comply with the request to reduce energy' consumption and may adjust operation of the heat pump based on the request to reduce power consumption from the utility device.

[0014] Referring now to FIG. 1, a schematic illustration of a heat pump system including a utility' communication port in communication with a utility device and a controller in communication with the utility communication port, a server, and/or a remote controller is depicted. Specifically, heat pump 102 may include utility communication port 104 and controller 106.

[0015] Heat pump 102 may be any well-known heat pump designed to heat and/or cool a fluid such as water. For example, heat pump 102 may be a water heater or a pool heater. Heat pump 102 may include condenser coils in fluid communication with evaporator coils via a compressor and each may further be in fluid communication with an expansion valve. In one example, heat pump 102 may be installed in a residential setting and may be designed to provide heated water for bathing and/or a pool heating. Alternatively, heat pump 102 may be used for commercial purposes (e.g., manufacturing).

[0016] Controller 106 may be a computing device that may communicate with one or more of utility communication port 104, server 108, and/or mobile device 110 via any well-known wired or wireless system. For example, controller 106 may communicate with utility' communication port 104, serv er 108, and/or mobile device 110 via network 112. which may be any wireless network (e.g., Wi-Fi, cellular network, Bluetooth, Bluetooth Low Energy (BLE) network, near field communication protocol, or the like). [0017] Controller 106 may be any computing device with a processor and may include one or more displays (e.g., touch screen display), one or more user interfaces (e.g., buttons), and/or one or more speakers and/or microphones. Similarly, remote serv er 108 and/or remote controller 110 may be any computing device with one or more processors and may be capable of communicating via network 112. In one example, server 108 may be one or more servers located in a location different from heat pump 102. [0018] Remote controller 1 10 may be a smart phone, tablet, desktop computer, laptop computer, e-reader, wearable device, smart speaker, or the like. In one example, remote controller 110 may be optional and/or the functionality of remote controller 110 may be integrated into controller 106 and a user interface with controller 106 via buttons and/or a touch screen on controller 106. In another example remote server 108 may be optional and the functionality of remote server 108 may be integrated into controller 106 and/or remote controller 110.

[0019] Controller 106 may communicate with utility communication port 104 via a wired electrical connection. Alternatively, or additionally, controller 106 may communicate with utility communication port via any well-known wireless communication techniques (e.g., Bluetooth, Wi-Fi Direct, communication via network 112). It is understood that controller 106 may further communicate with one or more appliances and/or devices in the same residential or commercial facility (e.g., with controllers of other heat pumps, solar power systems, gas power systems, generators, etc.). [0020] Utility communication port 104 may also communicate with utility' device 118. Utility device 118 may be one or more computing devices (e.g., severs, laptops, desktops, tablets, etc.) of a utility company or other entity supplying energy to heat pump 102. For example, the utility company or entity may supply electricity to heat pump and/or any other energy resource (e.g., natural gas). It is understood that heat pump 102 may include multiple utility communication ports 104 for different utility types (e.g., one for electricity and one of for natural gas). It is also understood that utility device 118 may be a third party device in communication with the utility company and may relay requests for energy reduction from the utility company to the utility communication port.

[0021] Utility communication port 104 may communicate with utility device 118 via network 114 which may be any w ireless netw ork (e.g., Wi-Fi, cellular network, Bluetooth, Bluetooth Uow Energy (BEE) network, near field communication protocol, or the like). It is understood that network 112 and network 114 may be the same or may be different. It is further understood that network 112 and/or netw ork 114 may be one or more types of netw orks and/or that different devices may communicate via different communication techniques. In one example, network 114 may be a radio frequency network and utility communication port 104 may be set to a certain frequency at which utility device 118 is broadcasting. [0022] Utility communication port 104 may be any port, adaptor, and/or communication unit designed to facilitate communication between residential or commercial devices and utility companies and/or entities for energy management and/or demand response. Utility communication port 104 may inform heat pump 102 of power grid conditions and may communicate a request from a utility company or entity to reduce power and/or conform to a certain energy mode.

[0023] It is understood that utility communication port 104 may provide the instructions and/or messages from utility device 118 to controller 106 and controller 106 may determine appropriate action. Alternatively, utility communication port 104 may automatically cause heat pump 102 to adjust operation to comply with the message received from utility device 118. For example, communication port 104 may receive instructions to reduce power to a pre-set energy mode and may automatically adjust operation of heat pump 102 to comply with the instructions.

[0024] In one example, utility communication port 104 may conform to or otherwise may be in compliance with one or more standardized protocols and/or architecture for communications between heat pump 102 and utility device 118. For example, communication port 104 may be compliant with and/or certified under ANSI/CTA-2045, OpenADR, JA 13 and/or any other standardized protocol and/or architecture and/or demand management systems for facilitating communication between utility device 118 and/or heat pump 102.

[0025] For example, utility communications port 104 may be a CTA-2045 port and may provide a modular communications interface for communications between residential devices and utility' providers for energy management pursuant to ANSI/CTA-2045. Heat pump 102 may be designed to power and otherwise electrically interface with the CTA- 2045 port via plugs and/or other electrical connections according to ANSI/CTA-2045. However, it is understood that utility communications port 104 may be any other standardized or non-standardized communication port for communicating with utility device 118.

[0026] Utility communications port 104 may be a standalone component that may electrically plug into or otherwise connect to heat pump 102 and/or controller 106 such that utility communications port 104 may be selectively removed from heat pump 102 and/or controller 106. Alternatively, utility communications port 104 may be integrated into heat pump 102 and/or controller 106 such that utility communications port 104 may not be removed from heat pump 102 and/or controller 106.

[0027] As shown in FIG. 1. utility device 118 may also be in communication with other residential and commercial appliances (e.g., appliance 120) along electrical grid 124. In one example, the utility company /entity may determine a certain sector of grid 122 that is using or is expected to use more energy (e.g., electricity) than available and may send a message to utility communication ports in that grid sector requesting devices to reduce power consumption during a given time to help with grid management.

[0028] The utility company or entity may offer monetary incentives to comply with the request for power reduction. Utility communication port 104 may receive the request and may even inform the utility company or entity (e.g., via utility device 118) whether or not the device (e.g., heat pump 102) complied with the request to reduce power consumption. In this manner, the economic incentive to reduce power may be attained.

[0029] Remote controller 1 10 may be used to share certain preferences, set points, settings, and/or schedules for operation of heat pump 102 with remote server 108 and/or controller 106. For example, a user may enter set points for regarding temperature preferences and/or minimums (e.g.. desired and minimum pool temperature).

Additionally, remote controller 110 may be used to enter scheduling preferences for heating. For example, the user may enter certain times and/or ranges of times associated with desired and/or minimum temperature. For example, if the pool is typically used during Monday through Friday between 8:00 am and 5:00 pm only, the desired temperature may only be associated with these times.

[0030] It is understood that controller 106 and/or utility communication port 104 may be programmed to have certain operating modes. In one example, utility device 118 may know the same operating modes and/or the operating modes may be standardized. For example, controller 106, utility communication port 104 and/or utility device 118 may use operating modes energy saver, maximum performance, economy, maximum economy, normal, and/or vacation. However, it is understood that different operating modes may be used and/or that the operating modes may be customized

[0031] Each operating mode may be associated with certain maximum energy values (e.g., a maximum amout of wattage permitted under that operating mode). The utility company/entity and/or heat pump constraints may dictate the maximum energy usage. Alternatively, or additionally, each operating mode and/or temperature setting may be associated with certain heat pump settings (e.g., fan settings such as speed and/or compressor settings).

[0032] As shown in FIG. 1, remote controller 110 may be used to customize temperature settings in various modes (e.g., Maximum Performance, Economy, Maximum Economy). It is further understood that controller 106 or alternatively sen' er 108 may determine operational settings at the various power modes. For example, at a reduced power setting, the fan may be limited to 3,000 RPM, at the economy setting the fan may be limited to 2,500 RPM. and at the Maximum Economy setting the fan may be limited to 2,000 RPM. Controller 106 and/or server 108 may determine these settings based on energy constraints set by utility’ device 1 18 and/or minimum temperature and/or schedule settings set by remote controller 106. While systems and methods described herein with respect to FIG.

1 as well as FIGS. 2-6 are described as including a heat pump, the systems and methods described herein may be used with a similar system having any other suitable heating, ventilation and/or air conditioner device instead of a heat pump. For example, the heat pump in the systems and/or methods of FIGS. 1-6 may be replaced with any suitable electrical heaters (e.g., electric resistance heater, electric water heater, etc.), gas heater (e.g., gas water heater, etc.), or the like.

[0033] Referring now to FIG. 2, a schematic illustration of a heat pump system with a controller in communication with a utility device, a server, and/or a remote controller is depictred. Specifically, heat pump 202 may include controller 206, which may be in communication with remote controller 210, server 208 and/or utility device 218. It is understood that heat pump 202. server 208, remote controller 210. and utility device 218 may be the same as or similar to heat pump 102, server 108, remote controller 110 and utility' device 118 of FIG. 1.

[0034] Controller 202 may be similar to controller 106 of FIG. 1, except that controller 202 may incorporate the functionality’ and operation of communication port 106 of FIG. 1. For example, controller 206 may communicate directly with utility' device 218 via network 214, which may⁷ be the same as network 114 of FIG. 1. Controller 206 may conform to or otherwise may be in compliance with one or more standardized protocols and/or architecture for communications between heat pump 202 and utility device 218 (e.g., ANS1/CTA-2045. OpenADR, JA 13 and/or any other standardized protocol and/or architecture and/or demand management systems for facilitating communication between utility⁷ device 218 and heat pump 202). [0035] Based on the instructions and/or message received from utility device 218, controller 206 may determine appropriate action in response to such messages alone or together with server 208 and/or remote controller 210. Alternatively, utility controller 206 may automatically cause heat pump 202 to adjust operation to comply with the message received from utility device 218. For example, communication port 206 may receive instructions to reduce power to a pre-set energy mode and may automatically adjust operation of heat pump 202 based on the instructions.

[0036] It is understood that controller 106 may be designed to conform to communication protocols and other requirements and protocols and standardized features to facilitate communication between controller 106 and utility device 118 such that controller 106 may perform the operations and functionality of utility communication port 104 of FIG. 1.

[0037] Referring now to FIG. 3, an exemplary data flow for operating a heat pump based on communication between a utility communication port and controller of the heat pump and a utility’ device, server, and remote controller is illustrated. Specifically, FIG. 3 illustrates communication between remote controller 310, server 308, and utility device 318 and heat pump 302, which may be the same as or similar to remote controller 110, server 108, utility device 118 and heat pump 102 of FIG. 1.

[0038] As shown in FIG. 3, at step 330, remote controller 310 may be used to create an energy profile via a local application on remote controller 310 and/or an application hosted on server 308. It is understood that the energy profile may be input into remote controller 310 and shared with and/or saved on server 308 and/or the controller of heat pump 302. The energy profile may include set points including various temperature settings (e.g., desired temperatures, minimum temperatures, etc.) for heat pump 310.

[0039] The energy profile may further include a desired schedule associated w ith temperature settings at certain times and/or time periods. It is understood that the energy profile may further customize one or more energy modes, including desired temperatures and minimum temperatures at one or more energy modes. In one example, for each energy mode, the controller of heat pump 302 may determine pump operational settings (e.g., fan speed and compressor settings) and may associate those settings with the energy profile.

[0040] At step 322, utility device 318 may send an energy reduction request to heat pump 302 (e.g., utility device 318 may communicate with a utility communication port and/or a controller of heat pump 302). It is understood that the utility communication port may share the energy reduction request and/or a message indicative of the energy reduction request with the controller. At step 334, heat pump 302 may share the energy reduction request and/or may share a message indicative of the energy reduction request with server 308.

[0041] At optional step 336, server 308 may send a message to remote controller 310 indicative of the request to reduce energy'. The message may include information about an incentive associated with the request and/or information about resulting pump operation (e.g., a reduced water temperature that would result from the requested energy reduction). At optional step 338, server 308 may send a message to remote controller 310 requesting permission to override a schedule or other instructions in the energy' profile necessary' to comply with the requested reduction in power. For example, the reduction may cause the water temperature to drop below a minimum temperature point in the energy profile. It is understood that the message at step 338 may be included in the message at step 336.

[0042] At optional step 340, remote controller 310 may send a message to server 308 indicating that energy reduction request is approved and thus the energy profile or other temperature setting is overridden. At step 342. server 308 may send a message to heat pump 302 (e.g., server 308 may send a message to the controller of heat pump 302) instructing the controller to adjust the heat pump settings based on the energy reduction request. In one example, server 308 may determine appropriate heat pump settings (e.g., fan settings and/or compressor settings) to comply with a reduced energy amount in the energy’ reduction request. Alternatively, the controller of heat pump 302 may make these determinations.

[0043] In another example, the energy reduction request may indicate a certain energy mode needed to comply with the energy reduction request. For example, the energy' reduction request may include instructions to operate at an economy mode for a certain time frame. Server 308 and/or controller 302 may determine the appropriate heat pump settings needed to operate at the desired energy' mode.

[0044] Alternatively, steps 334-342 may be optional and heat pump 302 may automatically enter the energy mode specified in the energy reduction request. For example, the controller 302 and/or server 308 may determine that the requested energy mode conforms to the energy profile for heat pump 302 and thus may automatically’ cause heat pump 302 to enter the specified energy' mode. For example, the energy' reduction request may request entering an economy mode at a time that that does not have a temperature requirement or constraint in the energy profile.

[0045] At step 344, heat pump 344 may send a message to utility device 318 indicating that heat pump 302 complied with the energy reduction request at step 332. For example, the utility communication port of heat pump 302 may send the message to utility device 218. The message sent to the utility device at step 344 may follow a standardized protocol. The message at step 344 may be to claim the incentive associated with the energy’ reduction request at step 332.

[0046] Referring now to FIG. 4, example process flow 400 for adjusting operation of a heat pump based on a request for reduced power consumption from a utility device is depicted. The operations and/or tasks set forth in example process flow 400 may be performed by a controller and/or server, which may be the same or similar to controller 106 and/or server 108 of FIG. 1.

[0047] While example embodiments of the disclosure may be described in the context of a controller and/or server, it should be appreciated that the disclosure is more broadly applicable to various types of computing devices as well as a controller and/or server in combination with a utility communication port, such as utility communication port 104 of FIG. 1. Some or all of the blocks of the process flows in this disclosure may be performed in a distributed manner across any number of devices. The operations of process flow 400 may be optional and may be performed in a different order.

[0048] At block 402, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine a user energy profile. The energy profile may be created by a user using a remote controller or other computing device. The energy⁷ profile may include a desired schedule and/or certain temperature setting associated with times and/or time periods. It is understood that the energy profile may further customize one or more energy modes, including desired temperatures and minimum temperatures for one or more energy modes.

[0049] At block 404, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine heat pump requirements corresponding to the user energy profile. For example, the controller and/or server may determine operational settings for the heat pump (e.g., fan settings, compressor settings, estimated energy consumption) necessary to operate the pump according the parameters set forth in the energy’ profile and may cause the heat pump to operate at such parameters. [0050] In one example, where the heat pump uses programmed energy modes, the operational settings in the energy profile may be compared to various energy modes and known operational ranges within each energy' mode to determine which modes are in compliance with the set points at various times throughout the schedule. Alternatively, the energy' profile determine at step 402 may already associate the desired or minimum energy mode at each time in the schedule. For example, it may be determined that energy saver mode is not possible Monday -Friday between 8:00-5:00 pm due to schedule constraints. [0051] At block 406, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine a request to reduce energy' use. For example, the request may be received by a utility communication port of the heat pump. The request to reduce energy' use may specify a maximum energy' value for the heat pump and/or may specify an operating mode and may further specify a certain time or time period associated with the request.

[0052] At optional block 406, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine adjusted heat pump settings corresponding to a request to reduce energy use. This may include determining fan settings and/or compressor settings necessary to satisfy a specified reduced energy amount. An output temperature associated with the adjusted operational parameters corresponding to the reduced energy may also be determined. It is understood that this step may not be necessary' where the request at step 406 includes an energy' mode known by the heat pump.

[0053] At block 410, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine if the current heat pump settings or heat pump settings at a certain time in the future based on the schedule satisfy the requirements of the request to reduce energy use. For example, the temperature corresponding to the reduced energy and the associated time period may be compared to the energy' profile.

[0054] At decision 410, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to determine if the pump settings required to comply with the request to reduce energy’ conform with or satisfy the settings in the energy profile. If there is not a conflict (e.g., the temperature estimate for the reduced power settings is larger than a minimum temperature setting), at step 414 computer-executable instructions stored on a memory' of a device, such as a controller and/or server, may be executed to adjust the heat pump setting to operate according to the reduced energy request.

[0055] Alternatively, if there is a conflict with the energy profile (e.g., the reduced power temperature is smaller than a minimum temperature setting), at block 412, computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to send a request for permission to deviate from the user energy profile (e.g., to the remote controller). At decision 416, computer-executable instructions stored on a memory’ of a device, such as a controller and/or server, may be executed to determine if permission to deviate from the energy- profile was granted.

[0056] If permission was granted, at block 420, computer-executable instructions stored on a memory ■ of a device, such as a controller and/or server, may be executed to cause the heat pump to operate the adjusted heat pump settings necessary- to satisfy the request to reduce energy. Alternatively, if permission not granted, at step 418. computer-executable instructions stored on a memory of a device, such as a controller and/or server, may be executed to either cause the heat pump to operate the adjusted heat pump using unadjusted settings according to the energy profile.

[0057] Referring now to FIG. 5, a schematic illustration a heat pump system yvith a controller in communication with a utility device and external appliances, a server, and/or a remote controller in accordance yvith one or more example embodiments of the disclosure is illustrated.

It is understood that heat pump 502, server 508, remote controller 510 and utility device 518 may be the same as or similar to heat pump 102. server 108. remote controller 110 and utility device 118 of FIG. 1.

[0058] As shown in FIG. 5, heat pump 502 (e.g., via the controller), server 508, and/or remote controller 510 may be in communication one or more external power sources 550. External power sources 550 may include, for example, a solar power system, a natural gas system, and/or a generator. Pump 502 (e.g., via the controller), server 508, and/or remote controller 510 may manage energy usage across all energy- systems (e.g., electrical, solar, natural gas, and/or generator) and may determine to reallocate energy usage in response to a request for power reduction from utility device 518.

[0059] In one example, the request to reduce energy from utility device 518 may be accepted but heat pump 502 (e.g., via the controller), server 508, and/or remote controller 510 may cause energy- from one or more external power source 550 to provide supplemental energy to offset the reduction in energy corresponding to the request for energy reduction. For example, heat pump 502 may continue with normal non-adjusted pump operation despite accepting a request to reduce energy conception. In one example, the supplemental power may come from a solar power system, a gas system, and/or a generator system.

[0060] FIG. 6 is a schematic block diagram of an illustrative server 600, which may be in communication with a heat pump, is illustrated. Server 600 may be the same or similar to server 108 of FIG. 1 or otherwise one or more of the servers of FIGS. 1-5. It is understood that a controller of the heat pump may alternatively, or additionally, include one or more of the components illustrated in FIG. 6 and controller or server may alone or together perform one or more of the operations of server 600.

[0061] Server 600 may be designed to communicate with one or more servers, mobile devices, user devices, other systems, or the like. Server 600 may be designed to communicate via one or more networks. Such network(s) may include, but are not limited to, any one or more different types of communications networks such as, for example, cable networks, public networks (e.g., the Internet), private networks (e.g., frame-relay networks), wireless networks, cellular networks, telephone networks (e.g.. a public switched telephone network), or any other suitable private or public packet-switched or circuit-switched netw orks.

[0062] In an illustrative configuration, server 600 may include one or more processors 602, one or more memory devices 604 (also referred to herein as memory 604), one or more input/output (I/O) interface(s) 606, one or more network interface(s) 608, one or more transceiver(s) 610, one or more antenna(s) 634, and data storage 620. The server 600 may further include one or more bus(es) 618 that functionally couple various components of the server 600.

[0063] The bus(es) 618 may include at least one of a system bus, a memory bus, an address bus, or a message bus, and may permit exchange of information (e.g., data (including computer-executable code), signaling, etc.) between various components of the server 600. The bus(es) 618 may include, without limitation, a memory bus or a memory controller, a peripheral bus, an accelerated graphics port, and so forth. The bus(es) 618 may be associated with any suitable bus architecture including.

[0064] The memory 604 may include volatile memory (memory that maintains its state when supplied with pow er) such as random access memory (RAM) and/or non-volatile memory (memory that maintains its state even when not supplied with power) such as read-only memory (ROM), flash memory', ferroelectric RAM (FRAM), and so forth. Persistent data storage, as that term is used herein, may include non-volatile memory'. In various implementations, the memory’ 604 may include multiple different types of memory such as various types of static random access memory (SRAM), various types of dynamic random access memory' (DRAM), various types of unalterable ROM, and/or writeable variants of ROM such as electrically erasable programmable read-only memory' (EEPROM), flash memory, and so forth.

[0065] The data storage 620 may include removable storage and/or non-removable storage including, but not limited to, magnetic storage, optical disk storage, and/or tape storage. The data storage 620 may provide non-volatile storage of computer-executable instructions and other data. The memory 604 and the data storage 620, removable and/or non-removable, are examples of computer-readable storage media (CRSM) as that term is used herein. The data storage 620 may store computer-executable code, instructions, or the like that may be loadable into the memory 604 and executable by the processor(s) 602 to cause the processor(s) 602 to perform or initiate various operations. The data storage 620 may additionally store data that may be copied to memory 604 for use by the processor(s) 602 during the execution of the computer-executable instructions. Moreover, output data generated as a result of execution of the computer-executable instructions by the processor(s) 602 may be stored initially in memory' 604, and may ultimately be copied to data storage 620 for non-volatile storage.

[0066] The data storage 620 may store one or more operating systems (O/S) 622; one or more optional database management systems (DBMS) 624; and one or more program module(s), applications, engines, computer-executable code, scripts, or the like such as, for example, one or more implementation modules 626, utility communication modules 627. pump operation modules 629, and one or more communication modules 628. Some or all of these modules may be sub-modules. Any of the components depicted as being stored in data storage 620 may include any' combination of software, firmware, and/or hardware. The software and/or firmware may include computer-executable code, instructions, or the like that may be loaded into the memory 604 for execution by one or more of the processor(s) 602. Any of the components depicted as being stored in data storage 620 may support functionality described in reference to correspondingly named components earlier in this disclosure. [0067] Referring now to other illustrative components depicted as being stored in the data storage 620, the O/S 622 may be loaded from the data storage 620 into the memory' 604 and may provide an interface between other application software executing on the server 600 and hardware resources of the server 600. More specifically, the O/S 622 may include a set of computer-executable instructions for managing hardware resources of the server 600 and for providing common services to other application programs (e.g., managing memory' allocation among various application programs). In certain example embodiments, the O/S 622 may control execution of the other program module(s) to for content rendering. The O/S 622 may include any operating system now known or which may' be developed in the future including, but not limited to, any server operating system, any mainframe operating system, or any other proprietary' or non-proprietary operating system.

[0068] The optional DBMS 624 may be loaded into the memory 604 and may support functionality for accessing, retrieving, storing, and/or manipulating data stored in the memory' 604 and/or data stored in the data storage 620. The DBMS 624 may use any of a variety' of database models (e g., relational model, object model, etc.) and may support any of a variety of query’ languages. The DBMS 624 may access data represented in one or more data schemas and stored in any suitable data repository including, but not limited to, databases (e.g., relational, object-oriented, etc.), file systems, flat files, distributed datastores in which data is stored on more than one node of a computer network, peer-to- peer network datastores, or the like.

[0069] The optional input/output (I/O) interface(s) 606 may facilitate the receipt of input information by the server 600 from one or more I/O devices as well as the output of information from the server 600 to the one or more I/O devices. The I/O devices may include any of a variety of components such as a display or display screen having a touch surface or touchscreen; an audio output device for producing sound, such as a speaker; an audio capture device, such as a microphone; an image and/or video capture device, such as a camera; and so forth. Any of these components may be integrated into the server 600 or may be separate.

[0070] The server 600 may further include one or more network interface(s) 608 via which the server 600 may communicate with any of a variety of other systems, platforms, networks, devices, and so forth. The network interface(s) 608 may' enable communication. for example, with one or more wireless routers, one or more host servers, one or more web servers, and the like via one or more of networks.

[0071] The antenna(s) 634 may include any suitable type of antenna depending, for example, on the communications protocols used to transmit or receive signals via the antenna(s) 634. Non-limiting examples of suitable antennas may include directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, or the like. The antenna(s) 634 may be communicatively coupled to one or more transceivers 612 or radio components to which or from which signals may be transmitted or received. Antenna(s) 634 may include, without limitation, a cellular antenna for transmitting or receiving signals to/from a cellular network infrastructure, an antenna for transmitting or receiving Wi-Fi signals to/from an access point (AP), a Global Navigation Satellite System (GNSS) antenna for receiving GNSS signals from a GNSS satellite, a Bluetooth antenna for transmitting or receiving Bluetooth signals including BLE signals, a Near Field Communication (NFC) antenna for transmitting or receiving NFC signals, a 900 MHz antenna, and so forth.

[0072] The transceiver(s) 612 may include any suitable radio component(s) for, in cooperation with the antenna(s) 634, transmitting or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by the server 600 to communicate with other devices. The trans ceiver(s) 612 may include hardware, software, and/or firmware for modulating, transmitting, or receiving - potentially in cooperation with any of antenna(s) 634 - communications signals according to any of the communications protocols discussed above including, but not limited to, one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the IEEE 802. 11 standards, one or more non-Wi-Fi protocols, or one or more cellular communications protocols or standards. The transceiver(s) 612 may further include hardware, firmware, or software for receiving GNSS signals. The transceiver(s) 612 may include any known receiver and baseband suitable for communicating via the communications protocols utilized by the server 600. The transceiver(s) 612 may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, a digital baseband, or the like.

[0073] Referring now to functionality supported by the various program module(s) depicted in FIG. 6, the implementation module(s) 626 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, overseeing coordination and interaction between one or more modules and computer executable instructions in data storage 620, determining user selected actions and tasks, determining actions associated with user interactions, determining actions associated with user input, initiating commands locally or at remote devices, and the like.

[0074] The utility' communication module(s) 627 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, analyzing messages, signals, data and/or any other information provided from or originating from a utility device, processing and/or analyzing such information and overseeing communications with the utility' device in conformity' with any relevant communication protocols.

[0075] The communication module(s) 628 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, communicating with one or more devices, for example, via wired or wireless communication, communicating with mobile devices, communicating with servers (e.g., remote servers), communicating with remote datastores and/or databases, sending or receiving notifications or commands/directives, communicating with cache memory^ data, communicating with user devices, and the like.

[0076] The pump operation module(s) 628 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, operating the heat pump according to certain set points, settings and other parameters provided by a user. For example, the pump operation module 628 may operate the heat pump according to a user energy profile.

[0077] Although specific embodiments of the disclosure have been described, one of ordinary skill in the art will recognize that numerous other modifications and alternative embodiments are within the scope of the disclosure. For example, any of the functionality' and/or processing capabilities described with respect to a particular device or component may be performed by any other device or component. Further, while various illustrative implementations and architectures have been described in accordance with embodiments of the disclosure, one of ordinary' skill in the art will appreciate that numerous other modifications to the illustrative implementations and architectures described herein are also within the scope of this disclosure.

[0078] Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to example embodiments. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by execution of computerexecutable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some embodiments. Further, additional components and/or operations beyond those depicted in blocks of the block and/or flow diagrams may be present in certain embodiments.

[0079] Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

[0080] Program module(s), applications, or the like disclosed herein may include one or more software components, including, for example, software objects, methods, data structures, or the like. Each such software component may include computer-executable instructions that, responsive to execution, cause at least a portion of the functionality described herein (e.g., one or more operations of the illustrative methods described herein) to be performed.

[0081] A software component may be coded in any of a variety of programming languages. An illustrative programming language may be a lower-level programming language such as an assembly language associated with a particular hardware architecture and/or operating system platform. A software component comprising assembly language instructions may require conversion into executable machine code by an assembler prior to execution by the hardware architecture and/or platform. [0082] Another example programming language may be a higher-level programming language that may be portable across multiple architectures. A software component comprising higher-level programming language instructions may require conversion to an intermediate representation by an interpreter or a compiler prior to execution.

[0083] Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database query or search language, or a report writing language. In one or more example embodiments, a software component comprising instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form.

[0084] A software component may be stored as a file or other data storage construct. Software components of a similar ty pe or functionally related may be stored together such as, for example, in a particular directory, folder, or library. Software components may be static (e.g., pre-established or fixed) or dynamic (e.g., created or modified at the time of execution).

[0085] Software components may invoke or be invoked by other software components through any of a wide variety of mechanisms. Invoked or invoking software components may comprise other custom-developed application software, operating system functionality (e.g., device drivers, data storage (e.g., file management) routines, other common routines, and services, etc.), or third-party software components (e.g., middleware, encry ption, or other security softw are, database management software, file transfer or other network communication software, mathematical or statistical software, image processing software, and format translation software).

[0086] Software components associated with a particular solution or system may reside and be executed on a single platform or may be distributed across multiple platforms. The multiple platforms may be associated with more than one hardware vendor, underlying chip technology, or operating system. Furthermore, software components associated with a particular solution or system may⁷ be initially⁷ written in one or more programming languages, but may invoke software components written in another programming language.

[0087] Computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that execution of the instructions on the computer, processor, or other programmable data processing apparatus causes one or more functions or operations specified in the flow diagrams to be performed. These computer program instructions may also be stored in a computer-readable storage medium (CRSM) that upon execution may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement one or more functions or operations specified in the flow diagrams. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer- implemented process.

[0088] Additional ty pes of CRSM that may be present in any of the devices described herein may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory⁷ (EEPROM), flash memory⁷ or other memory⁷ technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the information and which can be accessed. Combinations of any of the above are also included within the scope of CRSM. Alternatively, computer-readable communication media (CRCM) may include computer- readable instructions, program module(s), or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, CRSM does not include CRCM.

[0089] Although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood w ithin the context as used, is generally intended to convey that certain embodiments could include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply⁷ that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment.

Claims

We claim:

1. A method for operating a heat pump in a reduced power mode, the method comprising: receiving, by a server, a first temperature value from a first device, the first temperature value indicative of a desired temperature output of the heat pump; receiving a second temperature value for the heat pump, the second temperature value indicative of a minimum temperature output of the heat pump; determining first operational parameters of the heat pump corresponding to the first temperature value; causing the heat pump to operate at the first operational parameters; determining power reduction instructions; determining second operational parameters of the heat pump corresponding to power reduction instructions; determining the second operational parameters correspond to a third temperature value; determining that the third temperature value is larger than the second temperature value; and causing the heat pump to operate at the second operational parameters.

2. The method according to claim 1, further comprising: determining second power reduction instructions; determining third operational parameters of the heat pump corresponding to the second power reduction instructions; determining the third operational parameters correspond to a fourth temperature value; determining the fourth temperature value is smaller than the second temperature value; determining permission is required to operate the heat pump at the third operational parameters.

3. The method according to claim 2. further comprising: sending the first device a request to operate the heat pump at the third operational parameters; receiving permission to operate the heat pump at the third operational parameters; and causing the heat pump to operate at the third operational parameters.

4. The method according to any one of the preceding claims, wherein the heat pump comprises a fan and a compressor and the second operational parameters correspond to one or more of fan settings or compressor settings.

5. The method according to any one of the preceding claims, wherein the heat pump is a water heater or pool heater.

6. The method according to any one of the preceding claims, wherein the power reduction instructions comprise instructions to reduce power by a certain energy value and the second operational parameters correspond to an estimated power amount less than or equal to the certain energy value .

7. The method according to any one of the preceding claims, further comprising receiving power reduction instructions from a CTA-2045 port.

8. The method according to claim 7, wherein the CTA-2045 port and a controller are electrically integrated into the heat pump.

9. The method according to claim 7, wherein the CTA-2045 port is in wireless or wired communication with the controller.

10. The method according to claim 9. wherein the controller is in wireless communication with the server.

11. The method according to any one preceding claims, further comprising causing an external power source to provide supplemental energy to the heat pump.

12. A method for operating a heat pump in a reduced power mode, the method comprising: receiving, by a server, a first temperature value from a first device, the first temperature value indicative of a desired temperature output of the heat pump; receiving a schedule from the first device, the schedule associating the first temperature value with a first time point but not a second time point; determining first operational parameters of the heat pump corresponding to the first temperature value; causing the heat pump to operate at the first operational parameters at the first time point; determining power reduction instructions; determining second operational parameters of the heat pump corresponding to power reduction instructions; determining the second operational parameters correspond to a second temperature value; determining the second temperature is less than the first temperature; and causing the heat pump to operate at the second operational parameters at the second time point.

13. The method according to claim 12, wherein the schedule further associates the first temperature with a third time point, the method further comprising: determining, based on the second temperature being less than the first temperature, that permission is required to operate the heat pump at the second operational parameters at the third time point; and sending a request to the first device to operate the heat pump at the second operational parameters at the third time point.

14. The method according to any of claims 12-13, wherein the heat pump is a water heater or pool heater.

15. The method according to any of claims 12-14, wherein the power reduction instructions comprise instructions to reduce power by a certain energy value and the second operational parameters correspond to an estimated power amount less than or equal to the certain energy value.

16. The method according to any of claims 12-1 , further comprising receiving power reduction instructions from a CTA-2045 port.

17. The method according to claim 16, wherein the CTA-2045 port and a controller are electrically integrated into the heat pump.

18. The method according to claim 16, wherein the CTA-2045 port is in wireless or wired communication with the controller.

19. The method according to claim 18, wherein the controller is in wireless communication with the server.

20. The method according to any one of claims 12-19, further comprising causing an external power source to provide supplemental energy to the heat pump.