TWI581204B - Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response - Google Patents

Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response Download PDF

Info

Publication number
TWI581204B
TWI581204B TW104112892A TW104112892A TWI581204B TW I581204 B TWI581204 B TW I581204B TW 104112892 A TW104112892 A TW 104112892A TW 104112892 A TW104112892 A TW 104112892A TW I581204 B TWI581204 B TW I581204B
Authority
TW
Taiwan
Prior art keywords
dr
dr event
notification
target appliance
reduction
Prior art date
Application number
TW104112892A
Other languages
Chinese (zh)
Other versions
TW201638864A (en
Inventor
尤瑞區 赫柏格
喬傑塔G 傑區伊瓦
真島大介
陳偉鵬
Original Assignee
富士通股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通股份有限公司 filed Critical 富士通股份有限公司
Priority to TW104112892A priority Critical patent/TWI581204B/en
Publication of TW201638864A publication Critical patent/TW201638864A/en
Application granted granted Critical
Publication of TWI581204B publication Critical patent/TWI581204B/en

Links

Description

System, method and non-transitory computer readable medium for demand response in residential areas and small and medium enterprises Field of invention

The embodiments discussed herein relate to demand response technologies for residential areas and small and medium-sized businesses.

Background of the invention

Utilities reward the reduction in energy usage during certain high load periods to increase the ability of such utilities to meet larger demand or to reduce production costs. For example, in the summer, peak energy usage may occur in the hot evenings. A utility can provide a factory with incentives to reduce energy use during the evening. In response, the plant can delay high-load production operations until later on, turn off the air conditioning in the plant, or otherwise reduce energy use. In this way, the utility can increase its ability to meet the energy demands during peak energy usage and/or avoid producing or purchasing additional energy to meet those energy demands.

The reduction in energy usage during spikes or high duty cycles is often referred to as demand response (DR). The reduction in energy usage during a particular time period can be referred to as a DR event. DR events usually occur in a common matter Industry is expected to have high demand and require customers to reduce or reduce the use of energy. When a customer reduces their energy usage by one consent amount, the utility can provide incentives to the customer.

In some DR systems, the DR Aggregator Integrator media utilities communicate with customers. These DR aggregator integrators typically contract with such utilities to coordinate such customers and reflect DR events.

The involvement of residential customers and/or small and medium-sized business (SMB) customers (collectively referred to as residential/SMB customers) in DR events may present some difficulties. For example, energy reductions for individual residential/SMB customers are quite limited. Therefore, the utility or the DR aggregator integrator may limit resource investments in coordinating the participation of such residential/SMB customers. In addition, such residential/SMB customers may have varying schedules and restrictions that may reduce the likelihood that such residential/SMB customers will participate in a DR event.

Some utilities or DR aggregator integrators communicate with residential/SMB customers via SMS (SMS) messages or via email messages. However, communication via SMS messages and email messages used to motivate residential/SMB customers to participate in DR events may be invalid and ineffective for resources. For example, a Short Message Service (SMS) may be expensive for the utility or the DR aggregator integrator to communicate via a separate system. In addition, SMS messages may not include enough information to motivate residential/SMB customers to participate in a DR event.

In addition, some electrical appliances are controlled directly or indirectly by the utility or the DR aggregator integrator. However, the purchase of such appliances is expensive and the assembly is complicated. Therefore, such rewards for participating in DR events may not be able to rationalize the costs associated with the interconnection of such appliances.

The subject matter of the claims herein is not limited to embodiments that solve any disadvantages or embodiments that operate only within the aforementioned environments. Instead, the background of the invention is intended to be illustrative of only one embodiment of the embodiments of the invention described herein.

Summary of invention

In accordance with one embodiment, a method of residential area or small and medium business (SMB) demand response (DR) coordination may include receiving a DR event notification from a DR server. The DR event notification may include DR event information and reduction information about a DR event. The method can also include signaling a notification confirmation to the DR server. The notification confirmation indicates the receipt of the DR event notification. The method can include displaying a reduction request for one of the DR events. The reduction request is based on the reduction information included in the DR event notification and a portion including the DR event information. The method can also include receiving a user input including a DR event participation determination or a DR event participation rejection. The method can further include signaling a signal representative of at least a portion of the user input to the DR server.

The objects and advantages of the embodiments are achieved and attained by at least the elements, features, and combinations particularly pointed out in the claims.

It is to be understood that the foregoing general description and the following detailed description are in

100‧‧‧ Demand Response (DR) System

102‧‧‧ Residential and Small and Medium Enterprises (SMB) customers

104‧‧‧ device

106, 222‧‧‧ memory

108, 224‧‧‧ processor

110A-D‧‧‧DR Module

112‧‧‧DR server

114‧‧‧Commercial and Industrial (C&I) Servers

132‧‧‧ Target Appliances

134‧‧‧ display

136‧‧‧ sensor

138‧‧‧ Utilities

140‧‧‧Network

142‧‧‧C&I customers

144‧‧‧ input device

200‧‧‧ computing device

202‧‧‧Communication Module

204‧‧‧Display module

206‧‧‧Evaluation module

208‧‧‧ generating module

212‧‧‧Determining module

216‧‧‧ verification module

218‧‧‧ Estimation module

220‧‧‧ busbar

226‧‧‧Communication unit

248, 250, 252, 254, 256, 260‧‧‧ signal lines

300A-F‧‧‧ screenshot

302A-C‧‧‧ label

302A‧‧‧ Event Label

302B‧‧‧History Label

302C‧‧‧Setting labels

308A-C‧‧‧Reduction request

310‧‧‧Select to join the small map

312‧‧‧Select to withdraw from the map

314‧‧‧ Refreshing the map

316‧‧‧ Watch other events

318‧‧‧List of past DR events

320‧‧‧Electrical list

322‧‧‧Additional appliances

324‧‧‧小图

326‧‧‧Network connection screen (network screen)

328‧‧‧Selection of the collection to join the small map

400, 500‧‧‧ method

402-410, 502-508‧‧‧

It will be described with additional specific specifications and details via the use of the drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In the drawings: FIG. 1 illustrates one embodiment of a demand response (DR) system; FIG. 2 illustrates one embodiment of a computing system that may be embodied in the DR system of FIG. 1; FIGS. 3A-3F illustrate Figure 1 is a screenshot of an embodiment of the information displayed on the device embodiment in the DR system; Figure 4 is a flow chart of one of the method embodiments of residential area or small and medium-sized enterprise (SMB) DR coordination; and Figure 5 A flow chart of one of the other method embodiments of residential area or SMB DR coordination configured in accordance with at least one embodiment described herein.

Detailed description of the preferred embodiment

Several embodiments described herein relate to demand response (DR) for residential customer and/or small and medium business (SMB) customers (collectively residential/SMB customers). In one embodiment, a DR module can be stored on a device coupled to a residential/SMB customer. The DR module can be configured to receive a DR event notification from a DR server coupled to a utility or a DR aggregator integrator. After the device receives the DR event notification, the DR module can transmit a notification confirmation to the DR server. The device can also display a reduction request to the residential/SMB customer. The residential/SMB customer can then opt-in or opt-out of the DR event based on information and rewards included in the reduction request by providing a user input to the device. Additionally or alternatively, the residential/SMB customer may automatically opt in based on, for example, a pre-defined style or a contract. Respond to it, then the device A participation signal can be signaled to the DR server indicating whether the residential/SMB customer will participate in the DR event.

Additionally or alternatively, the DR module can enable one or more target appliances to be selected. In these and other embodiments, resource reduction during a DR event may be based on changes in the operation of the target appliances. The reduction request can then include information and rewards for the target appliances. In addition, the residential/SMB customer can then choose to join or opt out of one or more of the target appliances by providing a user input to the device. Another participation signal sent to the DR server may include or indicate which of the target appliances the residential/SMB customer has agreed to operate in accordance with the reduction request.

Based on the participation signals and the notification confirmation, the utility or the DR aggregator integrator can estimate one of the DR events for resource reduction. In addition, the utility or the DR aggregator integrator can develop historical data related to the residential/SMB customer, for example, sufficient amount of incentives to participate, successful compliance with consent reduction, time delay before a response, and the like. This historical data can be used, for example, to plan for the selection or inclusion of certain residential/SMB customers in future DR events and/or future DR events.

FIG. 1 illustrates one embodiment of a DR system 100. The DR system 100 can be configured to communicate with DR event related information between a DR server 112 and a device 104. More specifically, in some embodiments, the DR system 100 can be configured to communicate the information to a residential/SMB client 102 via the device 104. The information may be communicated to the residential/SMB customer 102 to notify the residential/SMB customer 102 of a DR event and/or solicitation, for example by The residential/SMB customer 102 participates in the DR event. In addition, the DR system 100 can be configured to enable communication of information from the residential area/SMB client 102 to a utility 138 through the device 104 and the DR server 112. The information communicated from the residential/SMB customer 102 to the utility 138 may include, for example, a notification confirmation, feedback, and user input. In some embodiments, the user input can include a DR event to participate in determining or rejecting. The DR system 100 can at least partially activate the implementation of the DR event and/or use the device 104 to reduce energy associated with the DR event relative to a target appliance 132. For example, in some embodiments, operation of the target appliance 132 can be controlled by commands from the DR server 112 and/or from the device 104.

As depicted in FIG. 1, the DR system 100 can include the device 104, the target appliance 132, the DR server 112, and a commercial and industrial (C&I) server 114. In the DR system 100, the device 104, the target appliance 132, the DR server 112, and the C&I server 114 can communicate over a network 140. In addition, in the DR system 100, the DR modules 110A-110D (generally, a DR module 110 or a plurality of DR modules 110) may be included in the device 104, the target appliance 132, and the DR server 112. And one or more of the C&I servers 114. The DR module 110 can be configured to communicate with the network 140 to enable communication of DR event related information between the device 104, the target appliance 132, the DR server 112, and the C&I server 114. Through the use of the DR module 110, the utility 138, the residential/SMB client 102, a C&I client 142, or any combination thereof can be coordinated with the DR event. The network 140, the device 104, the target appliance 132, the DR server 112, and the Each of the C&I servers 114 will be described later in relation to the DR module 110.

Here, the DR system 100 is specifically described below, wherein the utility 138 provides a resource such as power to a residential location or a small and medium business location associated with the residential/SMB customer 102 (not illustrated in the figure) Description). Additionally, in the DR system 100, the utility 138 can provide the resource to a C&I location (not illustrated) associated with the C&I client 142. The DR modules 110 can provide a platform in which DR event related information can be transmitted to the device 104 and the C&I server 114. The residential/SMB customer 102 and/or the C&I customer 142 may then participate in the DR event, which may include reducing resource usage for residential location, SME location, and/or C&I address. In the DR system 100, the DR module 110 can thereby actuate the C&I client 142 to coordinate with the residential/SMB client 102 via a single platform. While described in the context of a utility that supplies electricity, other embodiments may provide contextual representation of other resources, such as utilities for water, natural gas, or other resources.

The utility 138 can include any entity involved in the production, transmission, and/or distribution of the resource. The utility 138 can be public or private. Several embodiments of the utility 138 may include, but are not limited to, power plants, energy companies, and independent system operators (ISOs). Moreover, in several non-limiting embodiments, the utility 138 can be substituted or included with a DR aggregator integrator. The DR aggregator integrator can act as an intermediary between the utility 138 and the residential/SMB client 102 and/or the C&I client 142. The DR aggregator integrator can coordinate the implementation of one or more DR events and can Information about the DR events is communicated through the DR modules 110.

The DR server 112 can include a hardware server that includes a processor, memory, and communication capabilities. In this embodiment, the DR server 112 can be coupled to the network 140 to transmit and receive information from the network 140 to one or more of the device 104, the C&I server 114, and the target appliance 132. The DR server 112 can host or otherwise store a DR module 110C thereon. The DR module 110C can be configured to communicate information with one or more of the DR modules 110A, 110B, and 110D, and perform operations based on the information. More specifically, in some embodiments, the DR module 110C can be configured to communicate a DR event notification to the DR module 110A of the device 104. The DR event notification may include a DR event related DR event information and reduction information. The information and/or the reduction information may include incentives for DR event participation and/or targeted appliance (eg, target appliance 132) reduction.

The DR module 110C can also generate such rewards. For example, DR module 110C may generate rewards based on one or more of economic conditions, such as current resource prices, current demand, predicted prices, forecasted demand, and the C&I customer 142 and/or the residential/SMB customer 102. Relevant historical data. The DR event notification and other information communicated in the DR system 100 can be grouped according to a particular format, such as a scalable markup language (XML) with a defined schema.

In addition, the DR module 110C of the DR server 112 can be assembled from the DR module 110A of the device 104, the DR module 110B of the target appliance 132, the DR module 110D of the C&I server 114, or any combination thereof. Receive a notification confirmation, feedback, a participation signal, other materials, or a combination thereof. The notification confirmation may indicate receipt of the DR event notification. Accordingly, the utility 138 can thereby cause an indication that the DR event notification has been received at least, even if no connection communication has occurred. The participation signal can represent at least a portion of the user input received by the DR module 110A of the device 104. The user input may include a DR event participation determination, which may indicate that the residential/SMB client 102 agrees to participate in the DR event; or a DR event participation rejection, which may indicate that the residential/SMB client 102 does not agree to participate in the DR event. In several embodiments, lack of DR event participation determination may indicate rejection, or lack of DR event rejection may indicate determination. The feedback may be based on data collected by the sensor 136 included in the device 104. Based on the feedback, the DR module 110C can evaluate the participation of the residential/SMB customer 102. Moreover, based at least in part on the participation signal, the notification confirmation, and/or the feedback, the DR module 110C can estimate a resource reduction for the DR event. For example, the DR module 110C can know whether the residential/SMB customer 102 agrees to participate, the amount that the residential/SMB customer 102 agrees to reduce, and the likelihood of agreeing to cut. In an embodiment of the DR system 100 that includes a plurality of residential/SMB customers 102 and a plurality of C&I customers 142, the DR module 110C can be combined or aggregated from the plurality of residential/SMB customers 102 and multiple C&Is The participation signal of the customer 142, the notification confirmation, and/or the feedback to estimate resource reductions for the DR event.

In some embodiments, the DR module 110C can be configured to communicate a second DR event notification to the C&I client 142. The second DR event notification may include the DR event information about the DR event and related cut information of the C&I client 142. More specifically, in these and other embodiments, DR The module 110C can communicate the DR event notification to the DR module 110D included in the C&I server 114.

In the DR system 100 of FIG. 1, the DR module 110C can be configured to communicate the DR event notification to the DR module 110A of the device 104, and to communicate the second DR event notification to the C&I client 142. In some embodiments, DR system 100 can include multiple residential/SMB customers 102 and multiple C&I customers. In these and other embodiments, the DR module 110C can thereby communicate more than two DR event notifications to the plurality of residential/SMB customers and/or multiple C&I customers. Any subset of such DR event notifications may include different funds associated with the DR event, different reductions, reward information, and the like, without limitation. In addition, DR event notifications can change over time. Changes in DR event notifications can occur during a single DR event and occur with a single residential/SMB customer 102 or a single C&I customer 142. Additionally or alternatively, the DR event notifications for multiple DR events may be similar or identical.

The C&I server 114 can include a hardware server that includes a processor, memory, and communication capabilities. In this embodiment, the C&I server 114 can be coupled to the network 140 to transmit and receive data to and from the device 104, the DR server 112, and the target appliance 132 through the network 140. The C&I server 114 can host or otherwise store the DR module 110D thereon. The C&I server 114 can be located in a C&I location coupled to the C&I client 142. The utility 138 can communicate with the C&I client 142 via the C&I server 114 to rate the participating DR events of the C&I client 142.

Network 140 can be wired or wireless, and can have a myriad of different configurations including, but not limited to, star configuration, token ring configuration, or other configurations. Again, network 140 can include a local area network (LAN), a wide area network (WAN) (e.g., the Internet), and/or other interconnected data paths through which multiple devices can communicate. In some embodiments, network 140 can be a peer-to-peer network. The network 140 can also be coupled to or include portions of a telecommunications network that enable communication over a plurality of different communication protocols and through a plurality of different media.

In some embodiments, the network 140 includes a Bluetooth® communication network and/or a cell-based communication network for transmitting and receiving data through the following: a short message service (SMS), a multimedia messaging service (MMS), and a hypertext transfer protocol (HTTP). ), direct data link, Wireless Application Protocol (WAP), e-mail, Smart Energy Specification (SEP), Echonet Lite, Open ADR (OpenADR), etc.

In some embodiments, the network 140 can actuate communication of control commands to the target appliance 132. Such control instructions may be formatted according to a standard-based agreement or media, such as SEP, feedback network, open ADR, or other appropriate agreement or media (eg, Wi-Fi, ZigBee) ), green socket (HomePlug Green), etc.). In addition, network 140 may include or interface with satellite-based positioning systems (eg, global positioning system (GPS)) and/or terrestrial positioning systems (eg, Wi-Fi based positioning systems (WPS)) Positioning such as device 104 may be provided.

Communication can occur over the network 140 through multiple media and/or multiple protocols. For example, in some embodiments, communication between the DR module 110C and the DR modules 110A and 110D through the network 140 can be formatted according to an open ADR. Moreover, in these and other embodiments, communication between the DR module 110A and the DR module 110B can be formatted according to the SEP.

Target appliance 132 may include any appliance or device that receives and/or consumes resources from the utility 138 and has the ability to cut. For example, the target appliance 132 can be capable of reducing power consumption operation, shutdown, and the like. The target appliance 132 can be under the control of the residential/SMB customer 102 such that the residential/SMB customer 102 can directly or indirectly affect the operation of the target appliance 132. Several embodiments of target appliance 132 may include, but are not limited to, thermostats, lamps, microwave ovens, pumps, motors, washing machines, dishwashers, heaters, air conditioners, dryers, fans, refrigerators, and oven.

Target appliance 132 can include a processor, memory, and communication capabilities. In this embodiment, the target appliance 132 can be coupled to the network 140 to transmit and receive information from the network 140 to one or more of the device 104, the DR server 112, and the C&I server 114. The target appliance 132 can include a DR module 110B. The DR module 110B can receive and embody signals, such as control commands that can affect the operation of the target appliance 132. In some embodiments, control commands may be communicated from DR server 112 and/or device 104. Moreover, in some embodiments, the target appliance 132 can communicate a feedback, a participation signal, and/or a notification confirmation.

The residential/SMB customer 102 can be coupled to the device 104. For example, device 104 may be owned and/or routinely operated by residential/SMB customer 102. In addition, the residential/SMB customer 102 can be further associated with a residential location or SMB location (as described above), such as a building, house, structure, piece of equipment (eg, target appliance 132), or consumed by a utility 138 other items of resources for distribution. Accordingly, the residential/SMB customer 102 can at least partially control the consumption of resources in the residential location or SMB location, which can be included The control of the target appliance 132 is included.

The device 104 can be a computing device including a processor 108, a memory 106, and a network communication capability. The network communication capabilities may include internet (eg, Wi-Fi) networking capabilities, Bluetooth®, 3G, 4G, LTE communication networking capabilities, or may be adapted to pass through the network 140 and DR server 112, target appliances 132, And any combination of one or more of the C&I servers 114. Some embodiments of the device 104 may include a laptop, a desktop, a tablet, a mobile phone, a personal digital assistant (PDA), a mobile email device, a portable game console, a portable music player, A television set with one or more processors embedded therein or coupled thereto, or other electronic device capable of receiving and communicating through the network 140.

Device 104 can include a DR module 110A. The DR module 110A installed on the device 104 can be assembled to interact with the residential/SMB client 102. In addition, the DR module 110A can be configured to interface with the DR modules 110B-110D through the network 140. More specifically, in some embodiments, the DR module 110A can be configured to interface with the DR module 110C of the DR server 112 and the DR module 110B of the target appliance 132. For example, in these and other embodiments, the DR module 110A can be configured to receive a DR event notification from the DR module 110C of the DR server 112. In response to this, the DR module 110A can transmit the notification confirmation to the DR module 110C of the DR server 112. The DR module 110A can then display one of the reduction requests associated with the DR event. The reduction request may be based on a reduction in information included in one of the DR event notifications and one of the DR event notifications.

The DR module 110A is then received from the residential/SMB client 102. User input. The user input may include the DR event participation determination or the DR event participation rejection. The DR module 110A can then communicate the participation signal, which can represent at least a portion of the user input to the DR module 110C of the DR server 112.

In addition, the DR module 110A can activate between the device 104 and the target appliance 132 and/or between the residential/SMB client 102 and the device 104. In several embodiments, the initiation may occur before any DR event notifications are communicated to device 104. Additionally or alternatively, the residential/SMB client 102 can activate the target appliance 132 after one or more DR event notifications have been communicated to the device 104. In several embodiments, DR system 100 includes a plurality of target appliances. In such embodiments, one or more target appliances may be activated prior to any of the DR event notifications being communicated to the device 104, and one or more other target appliances may be in one of the DR event notifications Or more than after the message is sent to the device 104.

For example, the DR module 110A can generate a list of appliances including appliances with resource reduction capabilities. The list of appliances can include the target appliance 132. The DR module 110A can display the list of appliances to the residential/SMB client 102 on a display 134. The DR module 110A then receives a selection of target appliances 132 from the residential/SMB customer 102. The selection of the target appliance 132 may indicate a connection between the residential/SMB customer 102 and the target appliance 132, and/or indicate the willingness of the residential/SMB customer 102 to operate the target appliance 132 in accordance with the reduction request.

In this and other embodiments, the reduction request can include a resource reduction associated with the target appliance 132. Additionally, the user input can include a target appliance selection indicating the DR event of a selected target appliance 132 Reduction during the period. Additionally, the reduction request may include a reward related to the reduction of the target appliance 132 during the DR event.

The DR module 110A can also determine one of the target appliances 132 to control the command. The control command can be configured to affect the operation of the target appliance 132 based on the DR event. The control command may be pre-allocated according to the DR event notification and/or one of the target appliances 132. The control command can then be queried to the target appliance 132 in response to the user input including the DR event participating in the determination.

In some embodiments, device 104 can include display 134. The display 134 can include a light emitting diode (LED) display, an organic LED (OLED), a touch screen (eg, resistive, surface acoustic wave, capacitive, infrared grid, etc.), or any other suitable display device. The display 134 can be communicatively coupled to the processor 108 and/or the memory 106. The images and data stored in the memory 106 can be displayed on the display 134. Additionally, the processor 108 can control the display of images and data on the display 134. For example, DR module 110A can communicate a reduction request to display 134. The reduction request can be displayed to the residential/SMB customer 102 accordingly.

Additionally or alternatively, device 104 can include an input device 144. The input device 144 can include any system or device that is configured to receive the user input. The user input can then be communicated to the processor 108, the memory 106, the DR module 110A, and the like. Input device 144 can include, but is not limited to, a button, a mouse, a keyboard, a remote control, and a microphone. Additionally or alternatively, in some embodiments, display 134 can be assembled to receive user input. For example, in the embodiment, the display 134 includes a touch screen and lives. The home/SMB client 102 can provide user input to the device 104 via the display 134.

Additionally, the device 104 can include the sensor 136. The sensor 136 can be used to measure the condition of the device 104, such as the environmental conditions (e.g., temperature) of the device 104, the location of the device 104, and the directionality of the device 104. The sensor 136 can be communicatively coupled to the processor 108 and/or the memory 106. The processor 108 can receive a signal indicative of the condition measured by the sensor 136 and perform an action based thereon (eg, to signal the signal to the display 134 or to the DR server 112). Additionally, memory 106 can receive a signal indicative of the condition measured by sensor 136 and can store the signal or its representation.

One embodiment of sensor 136 can include a temperature sensor. The temperature sensor can be used to measure the temperature state of an environment of one of the devices 104. The processor 108 or the DR module 110A can receive a measure of one of the temperature states and can generate a signal representation of the one of the metrics. The signal representation of the metric value can be sent to the DR server 112, for example, via the network 140. The temperature state can be one of the embodiments of the feedback from the device 104 to the DR server 112. For example, a DR event may request the residential/SMB customer 102 to decrease or increase the temperature of the residential location or SMB location. The temperature status before, during, and/or after the DR event can be communicated to the DR server 112, which can indicate (whether) compliance with the request.

Additionally or alternatively, the sensor 136 can include a gyroscope sensor. The gyroscope sensor can measure the directivity of the device 104. The directionality metric can be signaled to the DR server 112 for feedback. For example, the residential/SMB customer 102 can be directed to the device 104 at the target appliance 132, which can refer to The residential/SMB customer 102 is shown to be influencing the operation of the target appliance 132. The processor 108 or the DR module 110A can receive one of the directional metrics and generate its signal representation. The measure of directionality can be sent to the DR server 112 over the network 140 where the metric can be used as a feedback.

For example, a DR event may include a request to reduce the thermostat setting of the heater. The residential/SMB customer 102 can then re-adjust the device 104 to communicate a control command to one of the thermostats that control the heater. The signal can include the control command to decrease the thermostat setting. During the communication of the control command to the thermostat, the directional change of the directional measurable device 104 can be communicated to the DR server 112. This measure of the directivity of device 104 can be interpreted as complying with the request.

Additionally or alternatively, the sensor 136 can include a camera. The camera can generate a photo or video of the device 104. The processor 108 or the DR module 110A can receive the photo or video and/or can send the photo or video to the DR server 112 via the network 140. The photo or video may be an embodiment of the feedback from the device 104 to the DR server 112. For example, a DR event may include a request to lower the temperature of the residential location or SMB location. Target appliance 132 can include a thermostat that is controllable by the device 104. The camera may generate one or more screenshots of the thermostat before, during, and/or after a temperature set point of the thermostat is lowered according to a reduction request. The screenshot can be communicated to the DR server 112 and interpreted as complying with one of the reduction requests.

Additionally or alternatively, the sensor 136 can include a position sensor. The positioning sensor can be assembled to present one of the measuring devices 104. For example, the current location of the device 104 can be communicated to the DR server 112 via the network 140. The current location can be based, at least in part, on location information received from a receiver. The receiver can be included in the positioning sensor or can be a separate component from one of the positioning sensor communications. The receiver can be a GPS receiver, a Wi-Fi positioning receiver, or any other suitable receiver that can generate and/or transmit positioning information.

In some embodiments, the position sensor can be assembled to continuously measure the current position of the device 104 continuously, periodically, randomly, virtually randomly, or on demand. The current location can be communicated to the DR server 112. In addition or in addition, the DR module 110C of the DR server 112 can transmit a signal to the DR module 110A of the device 104 to request the positioning sensor to measure the current location of the device 104. The DR module 110A of the device 104 then transmits the current location to the DR server 112 via the network 140.

Based on the current location, the DR server 112 can determine whether the current location of the device 104 and/or the residential/SMB client 102 is within a particular area. In response to the current location within the particular region, the DR server 112 can communicate information about a DR event (e.g., a DR event notification) to the device 104. In response to the current location not being within the particular region, the DR server 112 may not communicate information about a DR event to the device 104.

For example, the particular area may include one of the residential/SMB customers 102 residences. In several embodiments, the residential/SMB customer 102 is more likely to participate in a DR event when the residential/SMB customer 102 is in the residential/SMB customer 102 that is susceptible to the operation of an appliance. As such, when the residential/SMB customer 102 is within the home, the DR server 112 Information about a DR event can be communicated to the device 104. When the residential/SMB customer 102 is not within the residence, the DR server 112 may not communicate information about a DR event to the residential/SMB client 102. Utilities 138 may reduce the case where the information is being sub-transmitted based on a decision as to whether or not to upload information about the DR event at the current location, but the residential/SMB client 102 may not participate in a DR event.

Additionally or alternatively, in other cases, depending on the action required to reduce energy usage, the residential/SMB customer 102 is more likely to participate in a DR event when the residential/SMB customer 102 is not in a particular area. For example, the particular area may include one of the residential/SMB customers 102 residences. The requested action may include reducing the temperature set point of a thermostat during the winter. The residential/SMB customer 102 is more likely to participate in a DR event when the residential/SMB customer 102 is not in the residence. As such, when the residential/SMB customer 102 is within the home, the DR server 112 may not communicate a DR event related information to the device 104. When the residential/SMB customer 102 is within the home, the DR server 112 may not communicate the DR event related information to the residential/SMB client 102.

Additionally or alternatively, the device 104 can communicate with the target appliance 132 via different protocols and/or different media based on current location. In some embodiments, in response to the current location of the residential area being within the particular area, the device 104 can communicate a control command to the target appliance 132 via the first protocol and/or the first medium (eg, according to - One of the commands formatted by SEP for media messaging). In response to the current location being not in the particular area, the device 104 can communicate a control command to the second protocol and/or the second medium to The target appliance 132 (eg, a feedback network and a community media).

For example, the particular area may include one of the residential/SMB customers 102. When the residential/SMB customer 102 is internal to the home, the device 104 can communicate a control command to the target appliance 132 using a standard-based agreement. When the residential/SMB customer 102 is not within the home, the device 104 can be aware of one of the wireless gateways' Internet Protocol (IP) addresses (eg, a Dynamic Domain Name System (DNS)). The device 104 can then communicate the control command via a firewall (e.g., via Network Address Translation (NAT) or Universal Plug and Play (UPnP)).

Additionally or alternatively, the sensor 136 can include one or more other sensors that can be assembled to measure the condition of the device 104, the residential/SMB client 102, the target appliance 132, or some combination thereof.

In addition, the DR module 110A can be configured to limit communication between the DR module 110A and the DR server 112. One such restriction can be the limit of notification. The notification limit may include conditions to be met for completion of a DR event notification communication and/or information to be displayed to the residential/SMB customer 102 (eg, a reduction request). The notification limit may include, but is not limited to, the maximum number of DR event notifications, the maximum frequency of DR event notifications, the priority of DR event notifications, and a device preference. In some embodiments, the DR module 110A can display a notification limit query. The DR module 110A can receive a selection of one or more notification limits. Before displaying a reduction request, DR module 110A may verify that one or more of the notification limits have not been violated.

Additionally, the DR module 110A can be assembled to produce automated control of the target appliance 132. The automated control can be embodied in an embodiment, wherein Target appliance 132 includes the ability to be controlled via control commands. In embodiments including multiple appliances, the automated control may be pre-configured for the target appliance 132 and/or for one or more other appliances.

The automated control can include one or more conditions during which the customer 102 agrees to actuate the automated control of the target appliance 132. For example, one of the conditions that triggers the automated control can include a reward that is greater than one of the specific amounts. When the DR event notification includes a reward greater than one of the specific amounts, a control command can be communicated to the target appliance 132 without input from the client 102. This condition that triggers automated control can be stored in memory 106. As such, when the device 104 receives a DR event notification, the DR module 110A can determine whether the condition triggering an automated control exists. In response to the presence of such conditions, the DR module 110A can transmit a control command without the input of the client 102.

The DR system 100 can be modified, added, or deleted without departing from the scope of the disclosure. For example, while Figure 1 depicts one device 104 coupled to a residential/SMB customer 102, the disclosure herein applies to having one or more devices 104, one or more residential/SMB customers 102, or any thereof Combine one of the DR system architectures. Again, although FIG. 1 includes a DR server 112, a C&I server 114, and a target appliance 132, the DR system 100 can include multiple DR servers, multiple C&I servers, multiple appliances, or any of them. combination. Moreover, the separation of various components and servers in the embodiments described herein is not an indication that the separation occurs in all embodiments. Furthermore, it should be understood that the components and servers described using the effects disclosed herein can generally be integrated into a single component or server, or separated into Multiple components or servers.

The DR modules 110 may include code and routines for assisting DR event coordination between the utility 138 and the residential/SMB client 102. In some embodiments, the DR module 110 functions as a thin-client application that can be stored on the device 104 and partially stored as a component that can be stored in the DR server of the DR system 100. 112, one or more of the C&I server 114 and the target appliance 132. In some embodiments, the DR module 110 can be implemented using hardware, including a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). In a number of other cases, the DR module 110 can be embodied using a combination of hardware and software. In some embodiments, the DR module 110 can be stored in a combination of the device 104, the DR server 112, the C&I server 114, and the target appliance 132, or stored in the device 104, the DR server 112, and the C&I server 114. One of them.

In the DR system 100, a memory (eg, memory 106, including one or more of the servers 112, 114, and the target appliance 132) may include stored data to provide the description herein. Functional non-transitory memory. The memory may be included in a storage device, which may be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, a flash memory, or some other memory device. In some embodiments, the storage device also includes a non-electrical memory or similar persistent storage device and media including a hard disk drive device, a floppy disk drive device, a CD-ROM device, a DVD-ROM device, and a DVD- RAM devices, DVD-RW devices, flash memory devices, or several other mass storage devices that store information on a more durable basis.

Referring now to Figure 2, one embodiment of the DR module 110 is shown in further detail. 2 is a block diagram of a computing device 200 including the DR module 110, a processor 224, a memory 222, and a communication unit 226. The components of computing device 200 can be communicatively coupled by a busbar 220. In some embodiments, computing device 200 can include one or more of device 104, DR server 112, C&I server 114, and target appliance 132 of DR system 100 of FIG.

Referring to Figures 1 and 2 in combination, processor 224 can include an arithmetic logic unit (ALU), a microprocessor, a general purpose controller, or several other processor arrays to perform operations and provide electronic display signals to display 134. The processor 224 can be coupled to the bus bar 220 for communicating with other components via a signal line 248. The processor 224 typically processes data signals and may include various computing architectures, including a Complex Instruction Set Computer (CISC) architecture, a Reduced Instruction Set Computer (RISC) architecture, or an architecture that embodies one of a combination of instruction sets. Although FIG. 2 includes a single processor 224, multiple processors may be included with computing device 200. Other processors, operating systems, sensors, displays, and physical configurations are possible.

Memory 222 can be assembled to store instructions and/or data that can be executed by the processor 224. The memory 222 can be coupled to the bus bar 220 for communicating with other components through a signal line 250. The instructions and/or materials may include code for performing the techniques or methods described herein. Memory 222 can be a DRAM device, an SRAM device, a flash memory, or some other memory device. In some embodiments, the memory 222 also includes a non-electrical memory or similar persistent storage device and the medium includes a hard disk drive, and is soft. Disc drive devices, CD-ROM devices, DVD-ROM devices, DVD-RAM devices, DVD-RW devices, flash memory devices, or several other mass storage devices for storing information on a more durable basis.

The communication unit 226 can be configured to transmit data to and from one or more of the DR server 112, the C&I server 114, the device 104, or the target appliance 132 depending on where the DR module 110 is stored. . The communication unit 226 can be coupled to the bus bar 220 through a signal line 254. In some embodiments, the communication unit 226 includes a port for direct physical connection to the network 140 or to another communication channel. For example, communication unit 226 can include USB, SD, CAT-5, or a similar port for wired communication with components of DR system 100. In some embodiments, the communication unit 226 includes a wireless transceiver for exchanging data through the communication channel using one or more wireless communication methods, including IEEE 802.11, IEEE 802.16, Bluetooth®, Global System for Mobile Communications (GSM), and general purpose. Packet Radio Service (GPRS), Enhanced GSM Evolution Data Rate (EDGE), Coded Multiple Access (CDMA), Universal Mobile Telecommunications System (UMTS), LTE, LTE-A, or other suitable wireless communication methods.

In some embodiments, the communication unit 226 includes a cell-type communication transceiver for transmitting and receiving data through a cell-based communication network, including through SMS, MMS, Hypertext Transfer Protocol (HTTP), direct data link, WAP, and electronic Mail, or other appropriate type of electronic communication. In some embodiments, the communication unit 226 includes a cable and a wireless transceiver. Communication unit 226 may also provide other conventional connections to network 140 for the distribution of files and/or media objects using standard network protocols, including TCP/IP, HTTP, HTTPS, and SMTP.

In some embodiments, for example, where computing device 200 is included in an embodiment within device 104, computing device 200 can include display 134, sensor 136, input device 144, or it is discussed herein. Several combinations. The display 134, the sensor 136, and the input device 144 can be coupled to the bus bar 220 through the signal lines 252, 256, and 260, respectively, when included. Display 134, sensor 136, input device 144, or a combination thereof may be used to communicate with a module included in DR module 110.

In the embodiment of FIG. 2, the DR module 110 can include a communication module 202, a display module 204, a generation module 208, a determination module 212, a verification module 216, and an estimation module 218. And an evaluation module 206 (collectively referred to as a module of the DR module 110). Each of the modules of the DR modules 110 can be embodied as a software, including one or more routines that are assembled to perform one or more operations. The modules of the DR modules 110 can include a set of instructions executable by the processor 224 to provide the functionality described below. In some cases, the modules of the DR modules 110 can be stored in or at least temporarily loaded into the memory 222 of the computing device 200 and can be accessed and executed by the processor 224. One or more of the modules of the DR modules 110 can be adapted to cooperate and communicate with the components of the processor 224 and the computing device 200 via the bus bar 220. The communication module 202 can be configured to handle communication between the DR module 110 and other components of the computing device 200 (eg, 224, 222, 134, 136, 144, and 226). The communication module 202 can be configured to transmit and receive data to and from the device 104, the DR server 112, the target appliance 132, and the C&I server 114 through the communication unit 226. In some cases, the communication module 202 can cooperate with other modules (eg, 204, 206, 208, 212, 216, and 218) to transmit the The communication unit 226 receives and/or forwards the data from the components of the DR system 100.

In some embodiments, the communication module 202 can receive a DR event notification from the DR server 112. The DR event notification may include a DR event and information about the DR event related to the reduction of information. The DR event information may include, but is not limited to, DR event identification information, time/date of the DR event, duration, and the like. The reduction information may include requesting a reduction by the utility 138 and/or may include a particular resource reduction associated with the target appliance 132.

In response to receiving the DR event notification, the communication module 202 can transmit a notification confirmation to the DR server 112. For example, the communication module 202 can transmit the notification confirmation to the communication unit 226 through the bus bar 220. The communication unit 226 can then transmit the notification confirmation to the DR server 112 via the network 140. The notification confirmation may be indicated by the computing device 200 indicating receipt of the DR event notification. In addition, the communication module 202 can forward the DR event notification to the display module 204.

The display module 204 can be configured to receive data and communicate the data to the display 134 for display thereon. The display module 204 can communicate with other components of the computing device 200 through the bus bar 220. In some embodiments, the display module 204 can receive a reduction request for the DR event from the communication module 202. Display module 204 can then communicate the reduction request to display 134. The reduction request may be based on information about a DR event and/or reduction information included in the DR event notification. For example, the reduction request may include DR event information, such as DR event identification information and/or participation rewards. In addition, the reduction request may include one or more small maps or other User interface (UI) component. The thumbnails or other UI elements enable the residential/SMB client 102 to enter a DR event to participate in the determination (eg, opt-in) or a DR event to participate in the rejection (eg, opt-out).

In some embodiments, except for such widgets or other UI elements, or in addition, DR event participation determinations may be automatically generated. For example, the DR event participates in determining a pre-defined style or contract that may be based on one of the residential/SMB customer 102 and the utility 138. For example, if the residential/SMB customer 102 is in a particular location, the residential/SMB customer 102 may agree to participate, or may participate automatically in certain circumstances, such as cuts, climate patterns, or the DR. The appliance involved in the event (eg, target appliance 132).

User input may be received by computing device 200 via input device 144 and/or display 134. In the depicted embodiment, the residential/SMB client 102 provides user input. The user input can be communicated to the communication module 202. The user input may include the DR event participation determination or the DR event participation rejection. The communication module 202 can then transmit a signal representative of at least one of the user inputs to the DR server 112. In this and other embodiments, the DR server 112 may have received the notification confirmation and the participation signal. Accordingly, the DR server 112 and/or the utility 138 associated therewith can be aware of a plurality of received DR event notifications and multiple participants. Thus, the utility 138 can determine the participation rate, reduction request effect, reliability, or historical participation of the residential area/SMB customer 102.

The generation module 208 can be configured to generate an appliance list and feedback based on the data collected by the sensor 136. The generating module 208 can communicate with other components of the computing device 200 through the bus bar 220. In a few realities In the embodiment, the generating module 208 can generate the appliance list and transmit the appliance list to the display module 204. The display module 204 can communicate the list of appliances to the display 134. The list of appliances may include one or more appliances having a reduction capability. Additionally, the list of appliances can include actuating widgets or other UI elements that select a subset of the appliances. This subset of appliances may include appliances utilized in DR events. For example, in the depicted embodiment, the list of appliances can be displayed to the residential/SMB client 102, who may select the target appliance 132 from the list of appliances using a small map or other UI component. One of the target appliances 132 is selected for receipt via input device 144 and/or display 134.

The generation and/or display of the list of appliances may occur prior to receipt of the DR event notification. Additionally or alternatively, an appliance may be added between the receipt of the DR event notifications. For example, the residential/SMB customer 102 can purchase one of the appliances with the ability to cut. The residential/SMB customer 102 can add the appliance as a new target appliance.

In an embodiment in which the target appliance 132 is selected, the reduction request may include a resource reduction for the target appliance 132 during the DR event and/or a reward for the reduction of the target appliance 132. Moreover, in this and other embodiments, the user input can include a target appliance selection indicating a reduction in the selected target appliance during the DR event.

Moreover, in some embodiments in which the target appliance 132 is selected, the computing device 200 can embody the determination module 212 to determine a control command for the target appliance 132. The decision module 212 can be configured to determine control commands and/or current positioning. The determining module 212 can pass through the bus bar 220 communicates with other components of computing device 200. The control command may be pre-configured according to the DR event notification and/or one of the target appliances 132 associated. For example, memory 222 can include a plurality of pre-configured settings associated with a plurality of appliances included in the list of appliances. When selected, the target appliance 132 can trigger the determination module 212 to determine a control command associated with the target appliance 132. In this and other embodiments, the control command can be transmitted to the communication module 202 in response to the user input including the DR event participating in the determination. Then, the communication module 202 can send the control command to affect the operation of the target appliance 132.

For example, the reduction request may include information about the target appliance 132. Responding to the residential/SMB customer 102 selecting a small map indicating that the residential/SMB customer 102 is participating in the DR event, including the reduction of the target appliance 132, the communication module 202 can be based on the reduction request The reduction is to initiate a control command that affects the operation of the target appliance 132.

In some embodiments, the decision module 212 can determine whether a current location is within a particular area. For example, in these and other embodiments, the sensor 136 can include a position sensor. The sensor 136 can transmit a current location to the decision module 212. The decision module 212 can then determine if the current location is within the particular region. The particular area may include one or more areas, such as a primary business location, a residence, and the like. In some embodiments, the particular area can be stored in memory 222. The determining module 212 can transmit a signal indicating whether the current location is within the specific area for the communication module 202. Responding to the current location in the particular area Internally, the communication module 202 can send a control command to affect the operation of the target appliance 132 through a first protocol and/or a first medium. In response to the current location being outside the particular area, the communication module 202 can send a control command through a second protocol and/or a second medium to affect the operation of the target appliance 132. The first agreement may be different from the second agreement and/or the first medium may be different from the second medium.

In some embodiments, the generation module 208 can generate feedback based on the data collected by the sensor 136. For example, the sensor 136 can include a gyroscope sensor, a thermal sensor, or another sensor that is configured to measure the condition of one of the computing devices 200. The metric can be communicated to the generation module 208. The generation module 208 can then generate a feedback based on the metric. The generating module 208 can then transmit the feedback to the communication module 202. The communication module 202 can then transmit the feedback to the DR server 112. One embodiment of the feedback device can include a temperature metric of an environment of one of the computing devices 200. The temperature metric may indicate that the residential/SMB customer 102 has reduced a thermostat setting based on a DR event reduction request.

Moreover, in some embodiments, display module 204 can display a notification limit query. The notification limit query may include one or more notification limits that may limit communication between the DR server 112 and the computing device 200. Several embodiments of the notification limit may include one of a maximum number of DR event notifications within a particular time period (eg, 5 DR event notifications per month), one of the maximum frequency of DR event notifications (eg, one DR event every two days) Notification), one of the DR event notifications prioritized (eg, a DR event notification with a reward of more than $1), and a device preference (eg, only related to the dryer duty cycle) DR event notification).

The selection of the notification limit can be received via input device 144 and/or display 134. The selected notification limit can be communicated to the verification module 216. The verification module 216 can be configured to verify that the DR event notification does not violate the notification limit. The verification module 216 can communicate with other components of the computing device 200 through the bus bar 220. For example, in an embodiment in which the notification limit is selected, the verification module 216 can verify that the DR event notification has not violated one or more of the notification limits before displaying the reduction request.

Moreover, in some embodiments, the display module 204 can display an automated control decision query. The automated control decision query can include one or more conditions during which the customer 102 can actuate the automated control decisions of the target appliance 132. The automated control determines an automated control that can actuate the target appliance 132 during the DR event in which there is such a condition. These conditions can then be selected for the target appliance 132. One of these conditions can be selected via input device 144 and/or display 134. The selected condition can be communicated to the decision module 218.

In this and other embodiments, the communication module 202 can receive the DR event notification. The communication module 202 can transmit information about the DR event to the determination module 212. The determination module 212 can determine whether the condition of the period during which the customer 102 has actuated the automated control of the target appliance 132 is present. The decision module 212 can signal a signal to the generation module 208 to indicate whether the condition exists. The generating module 208 can generate a control command that can be transmitted to the target appliance 132 through the communication module 202 and the network 140.

One of the aforementioned functions of the modules of the DR module 110 or Many may change based on the particular computing device 200. For example, some of the aforementioned functions of the modules of the DR module 110 may conform to the following embodiments, wherein the computing device 200 includes the device 104 and/or the target appliance 132. For example, computing device 200 can include a mobile phone. Accordingly, the DR module 110 can include as an application or app that runs on the mobile phone and performs one or more of the functions as described herein.

A number of alternative functions of one or more of the modules of the DR module 110 are described below. The alternate functions may conform to the embodiment in which the computing device 200 includes a DR server 112 or other similar system that is configured to communicate with the device 104, the target appliance 132, the C&I server 114, or a combination thereof.

For example, in some embodiments, the communication module 202 can transmit the DR event notification to the device 104 and/or the C&I server 114, and receive notification confirmation from the device 104 and/or the C&I server 114. And receiving the participation signal from the device 104 and/or the C&I server 114. Additionally or alternatively, in this and other embodiments, the generation module 208 can generate rewards for DR event participation and/or target appliance reduction. The generation module 208 can communicate the rewards to the communication module 202. The communication module 202 then includes the generated rewards in the DR event notification.

The communication module 202 can transmit the notification confirmation and/or participation signal to the estimation module 218. The estimation module 218 can be assembled to estimate resource reductions. The estimation module 218 can communicate with other components of the computing device 200 through the bus bar 220. For example, the estimation module can receive the notification confirmation and/or participation signal. Based at least in part on the participation signal and the notification The estimation module 218 can estimate resource reductions for a DR event. The estimate may include the number of participants, the amount of committed resource reduction, and the like.

Moreover, as discussed above, decision module 212 can determine whether a current location is within a particular area. For example, the current location may be related to the device 104. A signal indicating that the device 104 (whether) is within the particular area can be signaled to the communication module 202. In response to the current location of the device 104 being within the particular area, the communication module 202 can communicate the DR event notification to the device 104. In response to the current location of the device 104 being outside of the particular area, the communication module 202 may not communicate the DR event notification to the device 104.

The communication module 202 can also receive feedback from the device 104 and/or the C&I server 114. As discussed above, in several embodiments, the feedback can be based on data collected by sensor 136. The communication module 202 can transmit the feedback to the evaluation module 206 and/or the estimation module 218.

The evaluation module 206 can be assembled to evaluate feedback. The evaluation module 206 can communicate with other components of the computing device 200 through the bus bar 220. In some embodiments, based on the feedback, the evaluation module 206 can evaluate the participation of the residential/SMB customer 102, or more generally, the participation of a user associated with the device 104.

The estimation module 218 can receive the feedback. The estimation module 218 can estimate the amount of reduction based on the feedback. For example, the feedback can include the signal representation of the metrics performed by the sensor 136. The estimation module 218 can determine from a metric that the client 102 is participating and participating to what extent. Accordingly, the estimation module 218 can estimate the amount of reduction based on the feedback.

3A-3F illustrate several embodiments of screen shots 300A-300G (typically, a screen shot 300 or multiple screen shots 300) that can be displayed on the device 104 as discussed with respect to FIGS. 1 and 2. In Figures 3A-3F, the device 104 includes a mobile device, such as a smart phone or tablet personal computer. In addition, in FIGS. 3A-3F, the device 104 includes a touch screen display that can be assembled to receive user input by a user touching the display. In an alternate embodiment, device 104 may include another type of device, which may include different types of displays, may include an input (eg, input device 144), or any combination thereof.

Referring collectively to Figures 3A-3F, the screenshots 300 can include one or more tags 302A-302C. The selection of one of the tags 302A-302C can change which information is displayed by the device 104. When selected, an event tag 302A can be assembled to display information about a pending DR event. For example, when the event tag 302A is selected, one of the pending DR events is displayed. When selected, a history tag 302B can be assembled to display information about one or more past DR events. When selected, a setting tab 302C can be assembled to display one or more settings related to a DR event, appliance, or communication protocol. In several alternative embodiments, additional or fewer tags may be included. Moreover, in several alternative embodiments, tags with other names may be combined to display other information.

FIG. 3A depicts a first screen shot 300A. The first screenshot 300A includes a first cut request 308A. The first reduction request 308A includes DR event information. More specifically, in the specific embodiment, the DR event information of the first reduction request 308A includes a DR event identifier (in the figure). 3A "Event ID"), a network identifier ("VTN ID" in Figure 3A), a resource identifier ("Resource ID" in Figure 3A), and a target reduction (in Figure 3A "Target" "). In addition, the first screenshot 300A may also include an optional thumbnail 310 and an opt-out banner 312. The selection of the selection bonus map 310 may result in or indicate a DR event participation determination. The selection of the exit thumbnail 312 may result in or indicate that a DR event participates in the rejection. The selection to add the thumbnails 310 and/or the selection to exit the thumbnails 312 may include rewards. Such rewards may indicate, for example, the amount of participation in a DR event exchange. Although the concise diagrams for discussion are discussed here and elsewhere, buttons or other UI elements may be used instead or in addition.

FIG. 3B depicts a second screen shot 300B. The second screenshot 300B includes a second cut request 308B. The second reduction request 308B includes a simple reduction request ("New event: Do you want to participate?"). In addition, the second screenshot 300B may also include the selection thumbnail 310 and the selection thumbnail 312, as discussed with reference to FIG. 3A.

FIG. 3C depicts a third screen shot 300C. The third screenshot 300C includes a third cut request 308C. The third reduction request 308C includes a request for reduction of a specific target appliance, including "AC", "TV", "washing machine", "fan", "refrigerator", and "oven" in FIG. 3C. The third reduction request 308C includes a reduction request ("New event: Which appliance will you turn off?"). In addition, the third screenshot 300C may also include a set of opt-in maps 328. The selection of the set is added to each of the maps 328 to list a target device. Choosing the selection of the collection to add to a small map in the small map 328 may result in or indicate the inclusion in the small map. The participation of the standard electrical equipment is determined. In addition, each of the selections of the collection added to the thumbnail 328 can include a reward. The reward may indicate, for example, that one of the target appliances cuts the exchangeable amount.

In Figures 3A-3C, the event tag 302A can be selected. In addition, the first, second, and third screen shots 300A-300C may include a refresh thumbnail 314 and a view of other event thumbnails 316. When selected, the refresh map 314 can be assembled to update the first, second, and third screen shots 300A-300C. When selected, the view other event thumbnails 316 can be grouped to display information about other DR events.

FIG. 3D depicts a fourth screen shot 300D. The fourth screenshot 300D includes a list of past DR events 318. The past DR event 318 of the list may be displayed in response to the selection of the history tag 302B. A user associated with device 104 can view information about the DR events including past DR events 318 included in the list.

FIG. 3E depicts a fifth screen shot 300E. The fifth screen shot 300E includes an appliance list 320. The appliance list 320 may include appliances having a reduction capability, including "AC", "TV", "Washing Machine", "Fan", "Fridge", and "Oven" in FIG. 3E. The selection of the map 324 corresponding to one of the appliances may indicate that the appliance is a target appliance. Referring to FIG. 3C and FIG. 3E in combination, in the fifth screen shot 300E and the third screen shot 300C, "fan" and "oven" can be indicated as "off". This indicates that the "oven" and "fan" are not selected as the target appliances. Referring back to FIG. 3E, the fifth screen shot 300E can include an add-on tile 322. Selecting the appliance icon 322 can trigger a new or updated appliance column including one of the additional appliances. A table, or a manual loading screen, in which a new appliance can be added to the appliance list or as a target appliance.

FIG. 3F depicts a sixth screen shot 300F. The sixth screen shot 300F includes a network link assembly screen (network screen) 326. The network screen 326 can actuate the selection or presentation of one or more network communication links between the device 104 and other systems, such as the DR server 112 and the target appliance 132 of FIG. Referring to FIG. 3E and FIG. 3F, the fifth screen shot 300E and the sixth screen shot 300F respectively can be selected from the setting label 302C by a target appliance template (not illustrated in the figure) or a network setting thumbnail ( It is not illustrated in the figure) and is viewed.

4 is a flow diagram of one embodiment of a method 400 of residential area or SMB DR coordination configured in accordance with at least one embodiment described herein. The method 400 can be performed in a DR system, such as the DR system 100 of FIG. 2, where the utility 138 supplies power to a location where the residential/SMB customer 102 is connected. A similar approach may be embodied in a DR system in which utility 138 supplies other resources to such locations.

In some embodiments, the method 400 can be performed programmatically by the computing device 200 described with reference to FIGS. 1 and 2. Additionally or alternatively, the method 400 can be performed programmatically by the apparatus 104. One or more of the device 104 and the computing device 200 can include or be communicably coupled to the non-transitory computer readable medium (eg, the memory 106 of FIG. 1 or the memory 222 of FIG. 2) Or where the code or instruction is encoded, it can be executed by a processor to perform method 400 or cause execution of method 400. Additionally or alternatively, one or more of the device 104 and the computing device 200 can include a processor (eg, the processor of FIG. 1) 108 or processor 224 of FIG. 2) is configured to execute computer instructions to initiate or control execution of method 400. Although illustrated in separate blocks, each block may be subdivided into additional blocks, combined into fewer blocks, or deleted, depending on the desired embodiment.

At block 402, a DR event notification can be received from a DR server. The DR event notification may include DR event information and reduction information about a DR event. At block 404, a notification confirmation can be signaled to the DR server. The notification confirmation may indicate that the DR event notification was received. At block 406, a request to reduce the DR event may be displayed. The reduction request may be based on the reduction information included in the DR event notification and certain portions of the DR event information.

At block 408, user input can be received. The user input may include a DR event participation confirmation or a DR event participation rejection. At block 410, a participating signal can be signaled. In some embodiments, the participation signal can be signaled to the DR server. The participation signal can be a representation of at least a portion of the user input.

Those skilled in the art will appreciate that the functions and methods disclosed herein may be embodied in a different order. Further, the steps and operations disclosed are for illustrative purposes only, and without departing from the disclosed embodiments, portions of the steps and operations may be selective, combined into fewer steps and operations, or expanded into additional Steps and operations.

For example, in several embodiments, a notification limit query can be displayed. One of the notification limits can be accepted. Such notice limits may include, However, without limitation, the maximum number of DR event notifications, the maximum frequency of DR event notifications, the priority of DR event notifications, and a device preference. In this and other embodiments, prior to displaying the reduction request, the DR event notification may be verified to have violated one or more of the notification limits.

Additionally or alternatively, in several embodiments of method 400, a list of appliances can be generated. The list of appliances can include appliances with energy reduction capabilities. The list of appliances can be displayed. A selection of a target appliance included in the list of appliances can be received. In these and other embodiments, the reduction request can include an energy reduction for the target appliance and/or a reward for the reduction of the target appliance during the DR event. In addition, the user input can include a selection of a target appliance indicating a reduction in the selected target appliance during the DR event.

Additionally or alternatively, in some embodiments of the method 400, a control command can be determined for a target appliance. The control command can be based on the DR event notification and/or a pre-assigned setting associated with the target appliance. In this and other embodiments, in response to the user input including the DR event participating in the determination, the control command can be transmitted to affect the operation of the target appliance.

Additionally or alternatively, in some embodiments of the method 400, it may be determined whether a current location is within a particular area. In response to the current location being in the particular area, a control command can be transmitted through one or more of the first protocol and the first medium to affect the operation of a target appliance. In response to the current location being outside the specific area, the control command may be transmitted through one or more of the second protocol and the second medium to affect the operation of the target appliance Work. Additionally or alternatively, in some embodiments of the method 400, feedback can be generated based on data collected by a sensor. The feedback can be signaled to the DR server.

Additionally or alternatively, in some embodiments of the method 500, one of the conditions of triggering an automated control of a target appliance can be received. In this and other embodiments, in response to the presence of the condition, a control command can be generated and communicated to the target appliance.

5 is a flow diagram of one embodiment of a method 500 of a residential area or SMB DR coordination configured in accordance with at least one embodiment described herein. The method 500 can be performed in a DR system, such as the DR system 100 of FIG. 2, wherein the utility 138 supplies power to a location where the residential/SMB customer 102 is connected. A similar approach may be embodied in a DR system in which utility 138 supplies other resources to such locations.

In some embodiments, the method 500 can be performed programmatically by the computing device 200 described with reference to FIGS. 1 and 2. Additionally or alternatively, the method 500 can be performed programmatically by the DR server 112. One or more of the DR server 112 and the computing device 200 may include or be communicably coupled to the non-transitory computer readable medium (eg, the memory 106 of FIG. 1 or the memory 222 of FIG. 2) The code or instructions stored therein may be executed by a processor to perform method 500 or cause execution of method 500. Additionally or alternatively, one or more of the DR server 112 and the computing device 200 can include a processor (eg, the processor 108 of FIG. 1 or the processor 224 of FIG. 2) that is configured to execute computer instructions To initiate or control the execution of method 500. Although illustrated as separate blocks, depending on the desired embodiment, each square can be subdivided into additional Squares, combined into a few more squares, or deleted.

At block 502, a DR event notification can be signaled to a device. The DR event notification may include DR event information and reduction information about a DR event. At block 504, a notification confirmation can be received from the device. The notification confirmation may indicate that the DR event notification was received. At block 506, a participation signal can be received from the device. The participation signal may be a representation of at least a portion of the user input, which may include a DR event participation determination or a DR event participation rejection. At block 508, energy reduction may be estimated for the DR event based at least in part on the participation signal and the notification confirmation.

Additionally or alternatively, in several embodiments of the method 500, it may be determined whether one of the devices is currently positioned within a particular area. In response to the current location of the device being within the particular area, the DR event notification can be signaled to the device. In response to the current location of the device being outside of the particular area, the DR event notification may not be signaled to the device.

Additionally or alternatively, in some embodiments of the method 500, feedback can be received from the device. This feedback can be based on data collected by a sensor. Based on the feedback, the participation of a user associated with the device can be assessed and/or the amount of reduction can be estimated based on the feedback.

Additionally or alternatively, in some embodiments of the method 500, rewards for DR event participation and target appliance reductions may be generated. The DR event notification can include the generated reward.

Additionally or alternatively, in some embodiments of the method 500, a second DR event notification can be signaled to a C&I server. The second DR event notification cocoa includes information about the DR event of the DR event and a C&I guest Household related information reduction.

Embodiments described herein may include the use of one of a variety of computer hardware or software modules or a general purpose computer, as described in more detail below.

Embodiments described herein may be embodied in a computer readable medium stored thereon for carrying or having computer executable instructions or data structures stored thereon. Such computer readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, such computer-readable media may include specific tangible or non-transitory computer readable storage media including RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, disk storage A device or other magnetic storage device, or any other non-transitory storage medium that can be used to carry or store a desired code in a computer-executable instruction or data structure and that can be accessed by a general purpose or special purpose computer. Combinations of the foregoing may also be included within the scope of computer readable media.

Computer-executable instructions, for example, include instructions and materials that cause a general purpose computer, special purpose computer, or special purpose processing device to perform a function or combination of functions. Although the subject matter has been described in the specific language of the structural features and/or method of operation, it is to be understood that the subject matter defined in the appended claims Instead, the foregoing specific features or actions are disclosed as examples of the various forms of the scope of the claims.

As used herein, the term "module" or "component" means a soft object or routine that is executed on a computing system. The various components, modules, engines, and services described herein can be embodied as objects or processes executing on a computing system (eg, as separate threads). Although the system and method described herein It can be embodied in software, but it is possible and desirable to embody the combination of hardware or software and hardware. In the detailed description, the "computing entity" may be any computing system as defined herein before, or any combination of modules or modules running on a computing system.

All of the examples and conditional languages cited herein are intended to be used for teaching purposes, to assist the reader in understanding the present invention and the concepts which the present inventors have contributed to the future art, and are not intended to be construed as limited to the specific examples and conditions. Nor is it an indication that the organizational structure of such examples in the specification is indicative of the advantages and disadvantages of the present invention. While the embodiments of the present invention have been described in detail, it will be understood that various changes, substitutions

400‧‧‧ method

402-410‧‧‧ square

Claims (16)

  1. A method for implementing a residential area or small and medium-sized enterprise (SMB) demand response (DR) event, the method comprising: receiving a DR event notification from a DR server in a mobile device associated with a residential area/SMB client The DR event notification includes information about the DR event of a DR event, reduction information, and a target appliance related to the DR event; the mobile device transmits a notification confirmation to the DR server, and the notification confirmation indicates the Receiving a DR event notification; displaying a reduction request for the DR event on a display of the mobile device, the reduction request being based on the reduction information included in the DR event notification and including one of the DR event information And a target appliance related to the DR event; receiving, on an input device of the mobile device, a user event input including determining a DR event; wherein the mobile device indicates at least the user input via a network One of the parts participates in signal transmission to the DR server; and based on the DR event notification and a pre-assigned setting associated with the target appliance, the mobile device determines Determining a control command for one of the target appliances; determining whether the current positioning of one of the mobile devices is within a specific area based on the input of the one of the mobile devices; and responding to the current positioning within the specific area By Transmitting the control command by one or both of the first protocol and a first medium to control operation of the target appliance; and responding to the current location being outside the particular area by using the first agreement The operation of the target appliance is controlled by a different one of the second agreement and the transmission of the control command of one or both of the second media different from the first medium.
  2. The method of claim 1, further comprising: generating a list of appliances including an appliance having energy reduction capability; displaying the appliance list on the display of the mobile device; and receiving the target appliance included in the appliance list One choice.
  3. The method of claim 2, wherein the reduction request includes an energy reduction for the target appliance; and the user input includes a target appliance selection indicating a reduction during the DR event of the selected appliance.
  4. The method of claim 3, wherein the reduction request includes a reward for a reduction in the target appliance during the DR event.
  5. The method of claim 1, further comprising: receiving one of a condition of triggering automatic control of the target appliance; and responding to the situation being present in the DR event notification, transmitting one without user input Control commands to the target appliance.
  6. The method of claim 1, further comprising: displaying a notification limit query; Receiving one of a notification limit including one of a maximum number of DR event notifications, one of DR event notification maximum frequencies, one of DR event notification priorities, and one device preference; and before displaying the reduction request Verify that the DR event notification does not violate one or more of these notification limits.
  7. The method of claim 1, further comprising: generating a feedback based on the data collected by a sensor; and transmitting the feedback to the DR server.
  8. A residential area or small and medium-sized enterprise (SMB) demand response (DR) coordination method, the method comprising: determining, by a DR server, a mobile device associated with a residential area/SMB customer prior to a DR event Whether the current location is within a particular area; the current location in response to the mobile device is within the particular area: a DR event notification is communicated to the mobile device by the DR server, the DR event notification includes The DR event information and the reduction information of the DR event; receiving, at the DR server, a notification confirmation from the mobile device, the notification confirmation indicating receipt of the DR event notification by the mobile device; receiving the DR server from the One of the mobile devices participates in a signal, the participating signal being a representation of at least a portion of the user input, the user input including a DR event participation determination; Receiving a feedback from the mobile device at the DR server, the feedback being based on data measured by a sensor included in the mobile device, the data indicating a target of a target appliance during the DR event Adjusting, based at least in part on the participation signal, the feedback and the notification confirmation, estimating an energy reduction for the DR event at the DR server; and evaluating the residential/SMB client at the DR server based on the feedback One involved.
  9. The method of claim 8, further comprising: in response to the current location of the device being outside the particular area, not transmitting the DR event notification to the device.
  10. The method of claim 8, further comprising transmitting a second DR event notification to a commercial and industrial (C&I) customer, the second DR event notification including the DR event information about the DR event and the C&I client Related reductions.
  11. A non-transitory computer readable medium for residential area or small and medium business (SMB) demand response coordination, the medium having code encoded therein, the code being executable by one or more processors for inclusion The following operations or controls include the performance of one of the following: a communication unit in a mobile device associated with a residential area or a small and medium business (SMB) customer, receiving a DR event notification from one of the DR servers, the DR The event notification includes information about the DR event of a DR event, reduction information, and a target appliance involved in the DR event; The communication unit of the mobile device transmits a notification confirmation to the DR server, the notification confirmation indicating receipt of the DR event notification; displaying a reduction request for the DR event on one of the mobile devices, the reduction The request is based on the reduction information included in the DR event notification and includes a portion of the DR event information and a target appliance related to the DR event; and the input device receives an DR event participation determination in the mobile device a user input; by means of the communication unit communicating through a network, indicating that at least one of the user inputs participates in the signal; and based on the DR event notification and a pre-configured setting associated with the target appliance Determining, by the one or more processors of the mobile device, a control command for a target appliance; determining, by the one of the mobile devices, the one of the mobile devices by the one or more processors Whether the current location is within a particular area; in response to the current location being within the particular area, by using a first agreement and a first medium The transmission of the control command of one or both of the bodies to control the operation of the target appliance; and in response to the current location being outside the particular area, by a second agreement and by a different one from the first agreement The first medium is different from one of the second media or the transmission of the control command to control the operation of the target appliance.
  12. Non-transitory computer readable medium as claimed in claim 11, wherein the operations Further comprising: generating a list of appliances including one of the appliances having energy reduction capability; displaying the list of appliances on the display of the mobile device; and receiving one of the target appliances included in the list of appliances.
  13. The non-transitory computer readable medium of claim 12, wherein the reduction request includes an energy reduction for the target appliance and a reward for the reduction of the target appliance during the DR event; and the user input includes an indication A target appliance selected during the DR event of the selected target appliance is selected.
  14. The non-transitory computer readable medium of claim 11, wherein the operations further comprise: generating a feedback based on the data collected by a sensor; and transmitting the feedback to the DR server.
  15. The non-transitory computer readable medium of claim 11, wherein the operations further comprise: displaying a notification limit query; receiving one of a maximum number of ones including a DR event notification, a maximum frequency of one of the DR event notifications, and one of the DR event notifications One of a notification limit of one or more of a priority order and a device preference is selected; and prior to displaying the reduction request, verifying that the DR event notification does not violate one or more of the notification limits.
  16. The non-transitory computer readable medium of claim 11 wherein the operations further comprise: Receiving one of the conditions of triggering the automatic control of the target appliance; and responding to the situation being present in the DR event notification, transmitting a control command to the target appliance without user input.
TW104112892A 2015-04-22 2015-04-22 Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response TWI581204B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW104112892A TWI581204B (en) 2015-04-22 2015-04-22 Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW104112892A TWI581204B (en) 2015-04-22 2015-04-22 Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response

Publications (2)

Publication Number Publication Date
TW201638864A TW201638864A (en) 2016-11-01
TWI581204B true TWI581204B (en) 2017-05-01

Family

ID=57850356

Family Applications (1)

Application Number Title Priority Date Filing Date
TW104112892A TWI581204B (en) 2015-04-22 2015-04-22 Systems,methods and non-transitory computer-readable medium for residential and small and medium business demand response

Country Status (1)

Country Link
TW (1) TWI581204B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040043775A1 (en) * 2002-08-29 2004-03-04 Kennedy Joseph P. Tasking and reporting method and implementation for wireless appliance location systems
TW200825963A (en) * 2006-10-13 2008-06-16 Responsiveload Ltd Optimisation of use or provision of a resource or service
US20100076835A1 (en) * 2008-05-27 2010-03-25 Lawrence Silverman Variable incentive and virtual market system
US20110276288A1 (en) * 2008-10-24 2011-11-10 Mark Chang-Ming Hsieh Apparatus for analysing an interior energy system
TW201340026A (en) * 2012-01-04 2013-10-01 Better Place GmbH System and method for management of electric power consumption
US20130289785A1 (en) * 2011-01-19 2013-10-31 Hitachi, Ltd. Power demand regulating apparatus, power regulating network system, and power regulating method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040043775A1 (en) * 2002-08-29 2004-03-04 Kennedy Joseph P. Tasking and reporting method and implementation for wireless appliance location systems
TW200825963A (en) * 2006-10-13 2008-06-16 Responsiveload Ltd Optimisation of use or provision of a resource or service
US20100076835A1 (en) * 2008-05-27 2010-03-25 Lawrence Silverman Variable incentive and virtual market system
US20110276288A1 (en) * 2008-10-24 2011-11-10 Mark Chang-Ming Hsieh Apparatus for analysing an interior energy system
US20130289785A1 (en) * 2011-01-19 2013-10-31 Hitachi, Ltd. Power demand regulating apparatus, power regulating network system, and power regulating method
TW201340026A (en) * 2012-01-04 2013-10-01 Better Place GmbH System and method for management of electric power consumption

Also Published As

Publication number Publication date
TW201638864A (en) 2016-11-01

Similar Documents

Publication Publication Date Title
Aman et al. Energy management systems: state of the art and emerging trends
KR101768186B1 (en) Energy management system and method
Zhou et al. Cloudthings: A common architecture for integrating the internet of things with cloud computing
US9600571B2 (en) Interoperability mechanisms for internet of things integration platform
KR20150123839A (en) Automatic iot device social network expansion
Li et al. Efficient and scalable IoT service delivery on cloud
US8515383B2 (en) Utility powered communications gateway
JP6389256B2 (en) Mechanism for routing IoT notifications according to user activity and / or proximity detection
US9977440B2 (en) Establishing proximity detection using 802.11 based networks
KR101702799B1 (en) Collaborative intelligence and decision-making in an iot device group
US20140244710A1 (en) Context aware actions among heterogeneous internet of things (iot) devices
US9838255B2 (en) Mobile demand response energy management system with proximity control
US9209652B2 (en) Mobile device with scalable map interface for zone based energy management
KR102002420B1 (en) Smart home system with portable gateway
US10444781B2 (en) Energy management system and method
US20130159153A1 (en) Apparatus and methods for energy management system
US8774143B2 (en) System and method of communication using a smart meter
US9996094B2 (en) NOC-oriented apparatus and method for controlling peak energy demand
Fernandes et al. Dynamic load management in a smart home to participate in demand response events
US20130079931A1 (en) Method and system to monitor and control energy
US20130307702A1 (en) Method and system for effective management of energy consumption by household appliances
KR101970029B1 (en) Automated demand response system
US9568973B2 (en) Remote energy management using persistent smart grid network context
US8461725B1 (en) Identification of powered devices for energy saving
US20150267935A1 (en) Method for saving energy efficient setpoints