Patent Grant
11650612
The present invention relates generally to the field of electrical power load control systems and more particularly to a method and system for actively controlling power load management for individual customers and optionally tracking power savings for both the individual customer as well as the overall electric utility.
The increased awareness of the impact of carbon emissions from the use of fossil fueled electric generation combined with the increased cost of producing peak power during high load conditions has increased the need for alternative solutions utilizing load control as a mechanism to defer, or in some cases eliminate, the need for the deployment of additional generation capacity by electric utilities. Existing electric utilities are pressed for methods to defer or eliminate the need for construction of fossil-based electricity generation. Today, a patchwork of systems exist to implement demand response load management programs, whereby various radio subsystems in various frequency bands utilize “one-way” transmit only methods of communication. Under these programs, RF controlled relay switches are typically attached to a customer's air conditioner, water heater, or pool pump. A blanket command is sent out to a specific geographic area whereby all receiving units within the range of the transmitting station (e.g., typically a paging network) are turned off during peak hours at the election of the power utility. After a period of time when the peak load has passed, a second blanket command is sent to turn on those devices that have been turned off.
While tele-metering has been used for the express purpose of reporting energy usage, no techniques exist for calculating power consumption, carbon gas emissions, sulfur dioxide (SO.sub.2) gas emissions, and/or nitrogen dioxide (NO.sub.2) emissions, and reporting the state of a particular device under the control of a two-way positive control load management device. In particular, one way wireless communications devices have been utilized to de-activate electrical appliances, such as heating, ventilation, and air-conditioning (HVAC) units, water heaters, pool pumps, and lighting, from an existing electrical supplier or distribution partner's network. These devices have typically been used in combination with wireless paging receivers that receive “on” or “off” commands from a paging transmitter. Additionally, the one-way devices are typically connected to a serving electrical supplier's control center via landline trunks, or in some cases, microwave transmission to the paging transmitter. The customer subscribing to the load management program receives a discount for allowing the serving electrical supplier (utility) to connect to their electrical appliances and deactivate those appliances during high energy usage periods.
While one-way devices are generally industry standard and relatively inexpensive to implement, the lack of a return path from the receiver, combined with the lack of information on the actual devices connected to the receiver, make the system highly inefficient for measuring the actual load shed to the serving utility. While the differential current draw is measurable on the serving electric utility's transmission lines, the actual load shed is approximate and the location of the load deferral is approximated at the control center of the serving utility.
One exemplary tele-metering system is disclosed in U.S. Pat. No. 6,891,838 B1. This patent describes details surrounding a mesh communication of residential devices and the reporting and control of those devices, via WANs, to a computer. The stated design goal in this patent is to facilitate the “monitoring and control of residential automation systems.” This patent does not explain how a serving utility or customer could actively control the devices to facilitate the reduction of electricity. In contrast, this patent discloses techniques that could be utilized for reporting information that is being displayed by the serving utility's power meter (as do many other prior applications in the field of tele-metering).
An additional exemplary tele-metering system is disclosed in U.S. Patent Application Publication No. 2005/0240315 A1. The primary purpose of this published application is not to control utility loads, but rather “to provide an improved interactive system for remotely monitoring and establishing the status of a customer utility load.” A stated goal of this publication is to reduce the amount of time utility field personnel have to spend in the field servicing meters by utilizing wireless technology.
Another prior art system is disclosed in U.S. Pat. No. 6,633,823 B2, which describes, in detail, the use of proprietary hardware to remotely turn off or turn on devices within a building or residence. While initially this prior art generally describes a system that would assist utilities in managing power load control, the prior art does not contain the unique attributes necessary to construct or implement a complete system. In particular, this patent is deficient in the areas of security, load accuracy of a controlled device, and methods disclosing how a customer utilizing applicable hardware might set parameters, such as temperature set points, customer preference information, and customer overrides, within an intelligent algorithm that reduces the probability of customer dissatisfaction and service cancellation or churn.
Attempts have been made to bridge the gap between one-way, un-verified power load control management systems and positive control verified power load control management systems. However, until recently, technologies such as smart breakers and command relay devices were not considered for use in residential and commercial environments primarily due to high cost entry points, lack of customer demand, and the cost of power generation relative to the cost of implementing load control.
One such gap-bridging attempt is described in U.S. Patent Application Publication No. US 2005/0065742 A1. This publication discloses a system and method for remote power management using IEEE 802 based wireless communication links. The system disclosed in this publication includes an on-premise processor (OPP), a host processor, and an end device. The host processor issues power management commands to the OPP, which in turn relays the commands to the end devices under its management. While the disclosed OPP does provide some intelligence in the power management system, it does not determine which end devices under its control to turn-off during a power reduction event, instead relying on the host device to make such decision. For example, during a power reduction event, the end device must request permission from the OPP to turn on. The request is forwarded to the host device for a decision on the request in view of the parameters of the on-going power reduction event. The system also contemplates periodic reading of utility meters by the OPP and storage of the read data in the OPP for later communication to the host device. The OPP may also include intelligence to indicate to the host processor that the OPP will not be able to comply with a power reduction command due to the inability of a load under the OPP's control to be deactivated. However, neither the host processor nor the OPP determine which loads to remove in order to satisfy a power reduction command from an electric utility, particularly when the command is issued by one of several utilities under the management of a power management system. Further, neither the host processor nor the OPP tracks or accumulates power saved and/or carbon credits earned on a per customer or per utility basis for future use by the utility and/or customer. Still further, the system of this publication lacks a reward incentive program to customers based on their participation in the power management system. Still further, the system described in this publication does not provide for secure communications between the host processor and the OPP, and/or between the OPP and the end device. As a result, the described system lacks many features that may be necessary for a commercially viable implementation.
Therefore, a need exists for a system and method for active power load management for individual customers that is optionally capable of tracking power savings for the individual customer as well as the electric utility to thereby overcome the shortcomings of the prior art.
Before describing in detail exemplary embodiments that are in accordance with the present invention, it should be observed that the embodiments reside primarily in combinations of apparatus components and processing steps related to actively managing power loading on an individual subscriber basis and optionally tracking power savings incurred by both individual subscribers and an electric utility. Accordingly, the apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
In this document, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms “comprises,” “comprising,” or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The term “plurality of” as used in connection with any object or action means two or more of such object or action. A claim element proceeded by the article “a” or “an” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Additionally, the term “ZigBee” refers to any wireless communication protocol adopted by the Institute of Electronics & Electrical Engineers (IEEE) according to standard 802.15.4 or any successor standard(s), the term “Wi-Fi” refers to any communication protocol adopted by the IEEE under standard 802.11 or any successor standard(s), the term “WiMax” refers to any communication protocol adopted by the IEEE under standard 802.16 or any successor standard(s), and the term “Bluetooth” refers to any short-range communication protocol implementing IEEE standard 802.15.1 or any successor standard(s). Additionally or alternatively to WiMax, other communications protocols may be used, including but not limited to a “1 G” wireless protocol such as analog wireless transmission, first generation standards based (IEEE, ITU or other recognized world communications standard), a “2-G” standards based protocoal such as “EDGE or CDMA 2000 also known as 1×RTT”, a 3G based standard such as “High Speed Packet Access (HSPA) or Evolution for Data Only (EVDO), any accepted 4 G standard such as “IEEE, ITU standards that include WiMax, Long Term Evolution “LTE” and its derivative standards, any Ethernet solution wireless or wired, or any proprietary wireless or power line carrier standards that communicate to a client device or any controllable device that sends and receives an IP based message.
It will be appreciated that embodiments of the invention described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions for managing power load distribution and tracking individual subscriber power consumption and savings in one or more power load management systems as described herein. The non-processor circuits may include, but are not limited to, radio receivers, radio transmitters, antennas, modems, signal drivers, clock circuits, power source circuits, relays, meters, smart breakers, current sensors, and user input devices. As such, these functions may be interpreted as steps of a method to distribute information and control signals between devices in a power load management system. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill in the art, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein, will be readily capable of generating such software instructions, programs and integrated circuits (ICs), and appropriately arranging and functionally integrating such non-processor circuits, without undue experimentation.
Recently, the IEEE has released improved WiMax wireless standards that have facilitated the consideration of new technologies to improve the response and control of power load control devices employing smart breaker technologies. Embodiments of the present invention expand upon and enhance prior technologies by, among other things, employing WiMax or IP-based load control in a system with the ability to monitor, in real time, the amount of power deferred (or carbon, SO.sub.2, or NO.sub.2 eliminated). These improvements allow new options for electric utilities to defer or invest in new power generation that is friendlier to the environment.
IP-based power management is advantageous over existing systems for many reasons. For example, positive control allows a system controller to receive a response from an end device installed at a customer location, which indicates that the actual target device has turned “off” or “on.” Additionally, each equipment identifier is unique and each IP address is either dynamically assigned when the device is activated (e.g., through use of the dynamic host configuration protocol (DHCP)) or statically assigned by the serving IP network, thereby providing enhanced security to protect against an act of random terrorism or sabotage inadvertently shutting down power services. Existing power management systems, including those utilizing radio subsystems, do not address security problems adequately and thus are more likely susceptible to hostile or malicious acts.
IP-based systems are also bandwidth or network efficient. For example, IP devices are controlled via the 7-layer Open Systems Interconnection (OSI) model whereby the payload of each packet can contain a message or “change in state” and does not require synchronous communication. This method of transmission allows for very minimum overhead and low data rates on a broadband network. Additionally, IP devices can report many states, including “no power.” For example, the active load client 300 may be implemented with a battery backup mechanism to provide backup or auxiliary power to the active load client 300 when AC power is lost. In this case, when battery backup is invoked, the active load client 300 can report a “no power” condition. Alternatively, a “no power” condition may be assumed if an active load client 300 fails to timely respond to a message (e.g., a poll or other message) from the ALD server 100, particularly where multiple active load clients 300 in a geographic area fail to timely respond to the ALD server messaging. Because the geographic location of each customer premises and active load client 300 may be known at the time of installation or thereafter (e.g., using GPS coordinates), such network outages may be located on a per meter basis.
One of the most beneficial advantages of an IP-based power management system, as provided in one embodiment of the present invention, is accurate reporting of the actual amount of power saved by each customer on an individual basis. Embodiments of the present invention monitor and calculate precisely how many kilowatts (or carbon credits) are being generated or saved per customer instead of merely providing an estimate. Furthermore, embodiments of the present invention provide means for tracking the actual amount of deferred load and pollutants according to generation mix, serving utility and geographic area.
Embodiments of the present invention include an exemplary system for supporting a serving utility or power distributor (e.g., such as a municipality, electric cooperative, or any other wholesale or retail producer of electric power), methods for providing continuous, real time active power control in the system, and a method for determining how much actual load may be controlled at any given time for the purposes of conservation, alternative power generation and the creation of carbon (and other gaseous emissions) credits.
Additional embodiments of the present invention provide a system that implements the exemplary methods through the unique use of load information, location of customers consuming electricity, changes in state of controlled devices, current sensing, customer set points/preferences and artificial intelligence (e.g., as implemented through software) to optimize the presentation of load available to the serving utility for control.
Generally, the embodiments disclosed in the present invention are directed towards the real time (active) control of residential and commercial electrical devices that generally are 240V or less. However, specific features and functions may also be applicable to larger commercial installations that are greater than 240V. The description herein is intended to provide a practical implementation of real time load management for either voluntary or involuntary participants over large geographies and ideally for many serving electrical power producers, wholesalers or distributors. The exemplary methods and systems disclosed in the present invention may be implemented by an individual utility provider, or a third party monitoring service that tracks and manages power loading for one or more utilities. This application describes the necessary methods and generally describes software subsystems for both a host function (e.g., an active load director (ALD) server) and a companion active load client (ALC).
One embodiment of the present invention controls power distribution for a variety of electric utility companies or any other electric power grid operator(s) by actively monitoring the amount of power needed by each utility and supplying the required power by redirecting power from participating customers. In this embodiment, customers agree to allow the power management system to disable certain power-consuming devices during peak loading times of the day. Smart breakers, which have the ability to be switched on or off remotely, are installed for specific devices in an electric service control panel accessed by a known IP address. Alternatively, IP-addressable smart appliances may be used. The power management system determines the amount of steady-state power each device consumes when turned on and logs the information in a database for each subscriber. For example, a current sensor on each smart appliance or within each smart breaker may measure the amount of current consumed by each monitored device. An active load client then multiplies the amount of current consumed by the operating voltage of the device to obtain the power consumption, and transmits the power consumption to the ALD server. When the serving utility needs more power than it is currently able to supply, the power load management system automatically adjusts the power distribution by turning off specific loads on an individual subscriber basis. Because the amount of power consumed by each specific load is known, the system can determine precisely which loads to turn off and tracks the power savings generated by each customer as a result of this short-term outage.
Furthermore, based upon the reduction in consumed power, the systems and methods of the present invention provide for generating at the control center a power supply value (PSV) corresponding to the reduction in consumed power by the power consuming device(s). Importantly, the PSV is an actual value that includes measurement and verification of the reduction in consumed power; such measurement and verification methods may be determined by the appropriate governing body or authority for the electric power grid(s). Power Supply Value (PSV) is calculated at the meter or submeter or at building control system or at any device or controller that measures power within the standard as supplied by the regulatory body(ies) that govern the regulation of the grid. PSV variations may depend on operating tolerances, operating standard for accuracy of the measurement. The PSV enables transformation of curtailment or reduction in power at the device level by any system that sends or receives an IP message to be related to or equated to supply as presented to the governing entity that accepts these values and award supply equivalence, for example of a power generating entity or an entity allowed to control power consuming devices as permitted by the governing body of the electric power grid, e.g., FERC, NERC, etc.
PSV may be provided in units of electrical power flow, monetary equivalent, and combinations thereof. Thus, the PSV provides an actual value that is confirmed by measurement and/or verification, thereby providing for a curtailment value as a requirement for providing supply to the power grid, wherein the supply to the power electric power grid is provided for grid stability, voltage stability, reliability, and combinations thereof, and is further provided as responsive to an energy management system or equivalent for providing grid stability, reliability, frequency as determined by governing authority for the electric power grid and/or grid operator(s).
The present invention can be more readily understood with reference to
Each active load client 300 is accessible through a specified address (e.g., IP address) and controls and monitors the state of individual smart breaker modules or intelligent appliances 60 installed in the business or residence 20 to which the active load client 300 is associated (e.g., connected or supporting). Each active load client 300 is associated with a single residential or commercial customer. In one embodiment, the active load client 300 communicates with a residential load center 400 that contains smart breaker modules, which are able to switch from an “ON” (active) state to an “OFF” (inactive), and vice versa, responsive to signaling from the active load client 300. Smart breaker modules may include, for example, smart breaker panels manufactured by Schneider Electric SA under the trademark “Square D” or Eaton Corporation under the trademark “Cutler-Hammer” for installation during new construction. For retro-fitting existing buildings, smart breakers having means for individual identification and control may be used. Typically, each smart breaker controls a single appliance (e.g., a washer/dryer 30, a hot water heater 40, an HVAC unit 50, or a pool pump 70).
Additionally, the active load client 300 may control individual smart appliances directly (e.g., without communicating with the residential load center 300) via one or more of a variety of known communication protocols (e.g., IP, Broadband over PowerLine (BPL) in its various forms, including through specifications promulgated or being developed by the HOMEPLUG Powerline Alliance and the IEEE, Ethernet, Bluetooth, ZigBee, Wi-Fi, WiMax, etc.). Typically, a smart appliance 60 includes a power control module (not shown) having communication abilities. The power control module is installed in-line with the power supply to the appliance, between the actual appliance and the power source (e.g., the power control module is plugged into a power outlet at the home or business and the power cord for the appliance is plugged into the power control module). Thus, when the power control module receives a command to turn off the appliance 60, it disconnects the actual power supplying the appliance 60. Alternatively, a smart appliance 60 may include a power control module integrated directly into the appliance, which may receive commands and control the operation of the appliance directly (e.g., a smart thermostat may perform such functions as raising or lowering the set temperature, switching an HVAC unit on or off, or switching a fan on or off).
Referring now to
Using the web browser interface 114, in one embodiment, customers interact with the ALD server 100 and subscribe to some or all of the services offered by the power load management system 10 via a customer sign-up application 116. In accordance with the customer sign-up application 116, the customer specifies customer personal settings 138 that contain information relating to the customer and the customer's residence or business, and defines the extent of service to which the customer wishes to subscribe. Additional details of the customer sign-up application 116 are discussed below. Customers may also use the web browser interface 114 to access and modify information pertaining to their existing accounts.
The ALD server 100 also includes a UCC security interface 102 which provides security and encryption between the ALD server 100 and a utility company's control center 200 to ensure that no third party is able to provide unauthorized directions to the ALD server 100. A UCC command processor 104 receives and sends messages between the ALD server 100 and the utility control center 200. Similarly, an ALC security interface 110 provides security and encryption between the ALD server 100 and each active load client 300 on the system 10, ensuring that no third parties can send directions to, or receive information from, the active load client 300. The security techniques employed by the ALC security interface 110 and the UCC security interface 102 may include conventional symmetric key or asymmetric key algorithms, such as Wireless Encryption Protocol (WEP), Wi-Fi Protected Access (WPA and WPA2), Advanced Encryption Standard (AES), Pretty Good Privacy (PGP), or proprietary encryption techniques.
In one embodiment, the commands that can be received by the UCC command processor 104 from the electric utility's control center 200 include a “Cut” command, a “How Much” command, an “End Event” command, and a “Read Meters” command. The “Cut” command instructs the ALD server 100 to reduce a specified amount of power for a specified amount of time. The specified amount of power may be an instantaneous amount of power or an average amount of power consumed per unit of time. The “Cut” command may also optionally indicate general geographic areas or specific locations for power load reduction. The “How Much” command requests information for the amount of power (e.g., in megawatts) that can be reduced by the requesting utility control center 200. The “End Event” command stops the present ALD server 100 transaction. The “Read Meters” command instructs the ALD server 100 to read the meters for all customers serviced by the requesting utility.
The UCC command processor 104 may send a response to a “How Much” command or an “Event Ended” status confirmation to a utility control center 200. A response to a “How Much” command returns an amount of power that can be cut. An “Event Ended” acknowledgement message confirms that the present ALD server transaction has ended.
The master event manager 106 maintains the overall status of the power load activities controlled by the power management system 10. The master event manager 106 maintains a separate state for each utility that is controlled and tracks the current power usage within each utility. The master event manager 106 also tracks the management condition of each utility (e.g., whether or not each utility is currently being managed). The master event manager 106 receives instructions in the form of transaction requests from the UCC command processor 104 and routes instructions to components necessary to complete the requested transaction, such as the ALC manager 108 and the power savings application 120.
The ALC manager 108 routes instructions between the ALD server 100 and each active load client 300 within the system 10 through an ALC interface 112. For instance, the ALC manager 108 tracks the state of every active load client 300 serviced by specified utilities by communicating with the active load client 300 through an individual IP address. The ALC interface 112 translates instructions (e.g., transactions) received from the ALC manager 108 into the proper message structure understood by the targeted active load client 300 and then sends the message to the active load client 300. Likewise, when the ALC interface 112 receives messages from an active load client 300, it translates the message into a form understood by the ALC manager 108 and routes the translated message to the ALC manager 108.
The ALC manager 108 receives from each active load client 300 that it services, either periodically or responsive to polling messages sent by the ALC manager 108, messages containing the present power consumption and the status (e.g., “ON” or “OFF”) of each device controlled by the active load client 300. Alternatively, if individual device metering is not available, then the total power consumption and load management status for the entire active load client 300 may be reported. The information contained in each status message is stored in the ALD database 124 in a record associated with the specified active load client 300. The ALD database 124 contains all the information necessary to manage every customer account and power distribution. In one embodiment, the ALD database 124 contains customer contact information, such as names, addresses, phone numbers, email addresses, and associated utility companies for all customers having active load clients 300 installed at their residences or businesses, as well as a description of specific operating instructions for each managed device (e.g., IP-addressable smart breaker or appliance), device status, and device diagnostic history.
There are several types of messages that the ALC manager 108 may receive from an active load client 300 and process accordingly. One such message is a security alert message. A security alert message originates from an optional security or safety monitoring system installed in the residence or business and coupled to the active load client 300 (e.g., wirelessly or via a wired connection). When a security alert message is received, the ALC manager 108 accesses the ALD database 124 to obtain routing information for determining where to send the alert, and then sends the alert as directed. For example, the ALD manager 108 may be programmed to send the alert or another message (e.g., an electronic mail message or a pre-recorded voice message) to a security monitoring service company and/or the owner of the residence or business.
Another message communicated between an active load client 300 and the ALC manager 108 is a report trigger message. A report trigger message alerts the ALD server 100 that a predetermined amount of power has been consumed by a specific device monitored by an active load client 300. When a report trigger message is received from an active load client 300, the ALC manager 108 logs the information contained in the message in the ALD database 124 for the customer associated with the information-supplying active load client 300. The power consumption information is then used by the ALC manager 108 to determine the active load client(s) 300 to which to send a power reduction or “Cut” message during a power reduction event.
Yet another message exchanged between an active load client 300 and the ALC manager 108 is a status response message. A status response message reports the type and status of each device controlled by the active load client 300 to the ALD server 100. When a status response message is received from an active load client 300, the ALC manager 108 logs the information contained in the message in the ALD database 124.
In one embodiment, upon receiving instructions (e.g., a “Cut” instruction) from the master event manager 106 to reduce power consumption for a specified utility, the ALC manager 108 determines which active load clients 300 and/or individually controlled devices to switch to the “OFF” state based upon present power consumption data stored in the ALD database 124. The ALC manager 108 then sends a message to each selected active load client 300 containing instructions to turn off all or some of the devices under the active load client's control.
In another embodiment, a power savings application 120 may be optionally included to calculate the total amount of power saved by each utility during a power reduction event (referred to herein as a “Cut event”), as well as the amount of power saved for each customer whose active load client 300 reduced the amount of power delivered. The power savings application 120 accesses the data stored in the ALD database 124 for each customer serviced by a particular utility and stores the total cumulative power savings (e.g., in megawatts per hour) accumulated by each utility for each Cut event in which the utility participated as an entry in the utility Power and Carbon (“P&C”) database 134.
In a further embodiment, an optional carbon savings application 132 uses the information produced by the power savings application 120 to determine the amount of carbon saved by each utility and by each customer for every Cut event. Carbon savings information (e.g., type of fuel that was used to generate power for the customer set that was included in the just completed event, power saved in the prior event, governmental standard calculation rates, and/or other data, such as generation mix per serving utility and geography of the customer's location and the location of the nearest power source) is stored in the ALD database 124 for each active load client 300 (customer) and in the utility P&C database 134 for each utility. The carbon savings application 132 calculates the total equivalent carbon credits saved for each active load client 300 (customer) and utility participating in the previous Cut event, and stores the information in the ALD database 124 and the utility P&C database 134, respectively.
Additionally, the ALC manager 108 automatically provides for smooth operation of the entire power load management system 10 by optionally interacting with a service dispatch manager 126. For example, when a new customer subscribes to participate in the power load management system 10, the service dispatch manager 126 is notified of the new subscription from the customer sign-up application 116. The service dispatch manager 126 then sends an activation request to the ALC manager 108. Upon receiving the activation request from the service dispatch manager 126, the ALC manager 108 may sends a query request for information to the new active load client 300 and, upon receipt of the information, provides it to the service dispatch manager 126. Additionally, if at any time the ALC manager 108 detects that a particular active load client 300 is not functioning properly, the ALC manager 108 may send a request for service to the service dispatch manager 126 to arrange for a service call to correct the problem.
In another embodiment, the service dispatch manager 126 may also receive requests for service from a call center manager 130 that provides support to an operations center (not shown), which receives telephone calls from customers of the power load management system 10. When a customer calls the operations center to request service, the call center manager 130 logs the service call in the ALD database 124 and sends a “Service” transaction message to the service dispatch manager 126. When the service call has been completed, the call center manager 130 receives a completed notification from the service dispatch manager 126 and records the original service call as “closed” in the ALD database 124.
In yet another embodiment, the service dispatch manager 126 may also instruct an ALC diagnostic manager 122 to perform a series of diagnostic tests for any active load client 300 for which the service dispatch manager 126 has received a service request. After the ALC diagnostic manager 122 has performed the diagnostic procedure, it returns the results to the service dispatch manager 126. The service dispatch manager 126 then invokes a trouble ticket generator 128 to produce a report (e.g., trouble ticket) that includes information (some of which was retrieved by the service dispatch manager 126 from the ALD database 124) pertaining to the required service (e.g., customer name, address, any special consideration for accessing the necessary equipment, and the results of the diagnostic process). A residential customer service technician may then use the information provided in the trouble ticket to select the type of equipment and replacement parts necessary for performing a service call.
A read meter application 136 may be optionally invoked when the UCC command processor 104 receives a “Read Meters” or equivalent command from the utility control center 200. The read meter application 136 cycles through the ALD database 124 and sends a read meter message or command to each active load client 300, or those active load clients 300 specifically identified in the UCC's command, via the ALC manager 108. The information received by the ALC manager 108 from the active load client 300 is logged in the ALD database 124 for each customer. When all the active load client meter information has been received, the information is sent to the requesting utility control center 200 using a business to business (e.g., ebXML) or other desired protocol.
The optional security device management block 140 includes program instructions for handling security system messages received by the security interface 110. The security device management block 140 includes routing information for all security system messages and may further include messaging options on a per customer or service company basis. For example, one security service may require an email alert from the ALD server 100 upon the occurrence of a security event; whereas, another security service may require that the message sent from the in-building system be passed on by the active load client 300 and the ALD server 100 directly to the security service company.
In a further embodiment, the ALD server 100 also includes a customer reports application 118 that generates reports to be sent to individual customers detailing the amount of power saved during a previous billing cycle. Each report may contain a cumulative total of power savings over the prior billing cycle, details of the amount of power saved per controlled device (e.g., breaker or appliance), power savings from utility directed events, power savings from customer directed events, devices being managed, total carbon equivalents used and saved during the period, and/or specific details for each Cut event in which the customer's active load client 300 participated. Customers may also receive incentives and awards for participation in the power load management system 10 through a customer rewards program 150. For example, the utilities or a third party system operator may enter into agreements with product and/or service providers to offer system participants discounts on products and services offered by the providers based upon certain participation levels or milestones. The rewards program 150 may be setup in a manner similar to conventional frequent flyer programs in which points are accumulated for power saved (e.g., one point for each megawatt saved or deferred) and, upon accumulation of predetermined levels of points, the customer can select a product or service discount. Alternatively, a serving utility may offer a customer a rate discount for participating in the system 10.
A communications interface 308 facilitates connectivity between the active load client 300 and the ALD server 100. Communication between the active load client 300 and the ALD server 100 may be based on any type of IP or other connection protocol, including but not limited to, the WiMax protocol. Thus, the communications interface 308 may be a wired or wireless modem, a wireless access point, or other appropriate interface.
A standard IP Layer-3 router 320 routes messages received by the communications interface 308 to both the active load client 300 and to any other locally connected device 440. The router 320 determines if a received message is directed to the active load client 300 and, if so, passes the message to a security interface 310 to be decrypted. The security interface 310 provides protection for the contents of the messages exchanged between the ALD server 100 and the active load client 300. The message content is encrypted and decrypted by the security interface 310 using, for example, a symmetric encryption key composed of a combination of the IP address and GPS data for the active load client 300 or any other combination of known information. If the message is not directed to the active load client 300, then it is passed to the IP device interface 330 for delivery to one or more locally connected devices 440. For example, the IP router 320 may be programmed to route power load management system messages as well as conventional Internet messages. In such a case, the active load client 300 may function as a gateway for Internet service supplied to the residence or business instead of using separate Internet gateways or routers.
An IP based communication converter 312 opens incoming messages from the ALD server 100 and directs them to the appropriate function within the active load client 300. The converter 312 also receives messages from various active load client 300 functions (e.g., a device control manager 314, a status response generator 304, and a report trigger application 318), packages the messages in the form expected by the ALD server 100, and then passes them on to the security interface 310 for encryption.
The device control manager 314 processes power management commands for various controllable devices logically connected to the active load client 300. The devices can be either smart breakers 402-412 or other IP based devices 420, such as smart appliances with individual control modules (not shown). The device control manager 314 also processes “Query Request” or equivalent commands or messages from the ALD server 100 by querying a status response generator 304 which maintains the type and status of each device controlled by the active load client 300, and providing the statuses to the ALD server 100. The “Query Request” message may include information other than mere status requests, such as temperature set points for thermally controlled devices, time intervals during which load control is permitted or prohibited, dates during which load control is permitted or prohibited, and priorities of device control (e.g., during a power reduction event, hot water heater and pool pump are turned off before HVAC unit is turned off). If temperature set points or other non-status information are included in a “Query Request” message and there is a device attached to the active load client 300 that can process the information, the temperature set points or other information are sent to that device 420 via a smart device interface 324.
The status response generator 304 receives status messages from the ALD server 100 and, responsive thereto, polls each controllable device 402-412, 420, 460 under the active load client's control to determine whether the controllable device 402-412, 420, 460 is active and in good operational order. Each controllable device 402-412, 420, 460 responds to the polls with operational information (e.g., activity status and/or error reports) in a status response message. The active load client 300 stores the status responses in a memory associated with the status response generator 304 for reference in connection with power reduction events.
The smart device interface 324 facilitates IP or other address-based communications to individual devices 420 (e.g., smart appliance power control modules) that are attached to the active load client 300. The connectivity can be through one of several different types of networks, including but not limited to, BPL, ZigBee, Wi-Fi, Bluetooth, or direct Ethernet communications. Thus, the smart device interface 324 is a modem adapted for use in or on the network connecting the smart devices 420 to the active load client 300. The smart device interface 324 also allows the device control manager 314 to manage those devices that have the capability to sense temperature settings and respond to temperature variations.
The smart breaker module controller 306 formats, sends, and receives messages, including power control instructions, to and from the smart breaker module 400. In one embodiment, the communications is preferably through a BPL connection. In such embodiment, the smart breaker module controller 306 includes a BPL modem and operations software. The smart breaker module 400 contains individual smart breakers 402-412, wherein each smart breaker 402-412 includes an applicable modem (e.g., a BPL modem when BPL is the networking technology employed) and is preferably in-line with power supplied to a single appliance or other device. The B1-BN counter manager 316 determines and stores real time power usage for each installed smart breaker 402-412. For example, the counter manager 316 tracks or counts the amount of power used by each smart breaker 402-412 and stores the counted amounts of power in a memory of the active load client 300 associated with the counter manager 316. When the counter for any breaker 402-412 reaches a predetermined limit, the counter manager 316 provides an identification number corresponding to the smart breaker 402-412 and the corresponding amount of power (power number) to the report trigger application 318. Once the information is passed to the report trigger application 318, the counter manager 316 resets the counter for the applicable breaker 402-412 to zero so that information can once again be collected. The report trigger application 318 then creates a reporting message containing identification information for the active load client 300, identification information for the particular smart breaker 402-412, and the power number, and sends the report to the IP based communication converter 312 for transmission to the ALD server 100.
The smart meter interface 322 manages either smart meters 460 that communicate using BPL or a current sensor 452 connected to a traditional power meter 450. When the active load client 300 receives a “Read Meters” command or message from the ALD server 100 and a smart meter 460 is attached to the active load client 300, a “Read Meters” command is sent to the meter 460 via the smart meter interface 322 (e.g., a BPL modem). The smart meter interface 322 receives a reply to the “Read Meters” message from the smart meter 460, formats this information along with identification information for the active load client 300, and provides the formatted message to the IP based communication converter 312 for transmission to the ALD server 100.
A security device interface 328 transfers security messages to and from any attached security device. For example, the security device interface 328 may be coupled by wire or wirelessly to a monitoring or security system that includes motion sensors, mechanical sensors, optical sensors, electrical sensors, smoke detectors, carbon monoxide detectors, and/or other safety and security monitoring devices. When the monitoring system detects a security or safety problem (e.g., break-in, fire, excessive carbon monoxide levels), the monitoring system sends its alarm signal to the security interface 328, which in turn forwards the alarm signal to the IP network through the ALD server 100 for delivery to the target IP address (e.g., the security monitoring service provider). The security device interface 328 may also be capable of communicating with the attached security device through the IP device interface to recognize a notification message from the device that it has lost its line based telephone connection. Once that notification has been received, an alert message is formatted and sent to the ALD server 100 through the IP based communication converter 312.
Operation of the power management system 10 in accordance with exemplary embodiments will now be described. In one embodiment, customers initially sign up for power load management services using a web browser. Using the web browser, the customer accesses a power management system provider's website through the web browser interface 114 and provides his or her name and address information, as well as the type of equipment he or she would like to have controlled by the power load management system 10 to save energy at peak load times and to accumulate power savings or carbon credits (which may be used to receive reward incentives based upon the total amount of power or carbon saved by the customer). The customer may also agree to allow management of power consumption during non-peak times to sell back excess power to the utility, while simultaneously accumulating power savings or carbon credits.
The customer sign up application 116 creates a database entry for each customer in the ALD database 124. Each customer's contact information and load management preferences are stored or logged in the database 124. For example, the customer may be given several simple options for managing any number of devices or class of devices, including parameters for managing the devices (e.g., how long each type of device may be switched off and/or define hours when the devices may not be switched off at all). In particular, the customer may also be able to provide specific parameters for HVAC operations (e.g., set control points for the HVAC system specifying both the low and high temperature ranges). Additionally, the customer may be given an option of receiving a notification (e.g., an email message, Instant Message, Text Message, or recorded phone call, or any combination thereof) when a power management event occurs. When the customer completes entering data, a “New Service” or equivalent transaction message or command is sent to the service dispatch manager 126.
In one embodiment, responsive to the service call notification, the service person obtains the new customer's name and address, a description of the desired service, and a service time from a service dispatch manager service log. The service person obtains an active load client 300, all necessary smart breaker modules 402-412, and all necessary smart switches to install at the customer location. The service person notes any missing information from the customer's database information (e.g., the devices being controlled, type make and model of each device, and any other information the system will need to function correctly). The service person installs the active load client 300 and smart breakers 402-412 at the new customer's location. A global positioning satellite (GPS) device may optionally be used by the service person to determine an accurate geographic location of the new customer building, which will be added to the customer's entry in the ALD database 124 and may be used to create a symmetric encryption key to facilitate secure communications between the ALD server 100 and the active load client 300. The physical location of the installed active load client 300 is also entered into the customer's entry. Smart switch devices may be installed by the service person or left at the customer location for installation by the customer. After the active load client 300 has been installed, the service dispatch manager 126 receives (508) a report from the service person, via a service log, indicating that the installation is complete. The service dispatch manager 126 then sends (510) an “Update” or equivalent transaction message to the ALC manager 108.
Returning to block 503, when a “Service” or similar transaction message or command is received, the service dispatch manager 126 schedules (512) a service person to make a service call to the specified customer. The service dispatch manager 126 then sends (514) a “Diagnose” or similar transaction to the ALC diagnostic manager 122. The ALC diagnostic manager 122 returns the results of the diagnostic procedure to the service dispatch manager 126, which then notifies (516) the service person of the service call and provides him or her with the results of the diagnostic procedure using a conventional trouble ticket. The service person uses the diagnostic procedure results in the trouble ticket to select the type of equipment and replacement parts necessary for the service call.
Returning to block 706, when the master event manager 106 receives a “How Much” or other equivalent power inquiry transaction message or command from the UCC command processor 104 (resulting from a “How Much” or equivalent power inquiry command issued by the utility control center 200), the master event manager 106 determines (712) the amount of power that may be temporarily removed from a particular utility's managed system by accessing the current usage information for that utility. The current usage information is derived, in one embodiment, by aggregating the total available load for the serving utility, as determined from the customer usage information for the utility stored in the ALD database 124, based on the total amount of power that may have to be supplied to the utility's customers in view of the statuses of each of the active load clients 300 and their respectively controllable load devices 402-412, 420, 460 during the load control interval identified in the “How Much” message.
Each utility may indicate a maximum amount of power or maximum percentage of power to be reduced during any power reduction event. Such maximums or limits may be stored in the utility P&C database 134 of the ALD server 100 and downloaded to the master event manager 106. In one embodiment, the master event manager 106 is programmed to remove a default one percent (1%) of the utility's current power consumption during any particular power management period (e.g., one hour). In alternative embodiments, the master event manager 106 may be programmed to remove other fixed percentages of current power consumption or varying percentages of current power consumption based on the current power consumption (e.g., 1% when power consumption is at system maximum and 10% when power consumption is at only 50% of system maximum). Based on the amount of power to be removed, the master event manager 106 sends (710) a “Cut” or equivalent event message to the ALC manager 108 indicating the amount of power (e.g., in megawatts) that must be removed from the utility's power system (e.g., 1% of the current usage), and notifies (711) all customers that have chosen to receive a notification that a power management event is in process. The master event manager 106 also sends a response to the utility control center 200 via the UCC command processor 104 advising the utility control center 200 as to the quantity of power that can be temporarily reduced by the requesting utility.
Returning once again to block 706, when the master event manager 106 receives an “End Event” or equivalent transaction message or command from the UCC command processor 104 (resulting from an “End Event” command issued by the utility control center 200), the master event manager 106 sets (714) the state of the current event as “Pending” and sends (716) an “End Event” or equivalent transaction message or command to the ALC manager 108. When the ALC manager 108 has performed the steps necessary to end the present event (e.g., a power reduction or Cut event), the master event manager 106 receives (718) an “Event Ended” or equivalent transaction from the ALC manager 108 and sets (720) the utility to a logical “Not Managed” state. The master event manager 106 then notifies (722) each customer that has chosen to receive a notification (e.g., through transmission of an email or other pre-established notification mechanism) that the power management event has ended. Finally, the master event manager 106 sends an “Event Ended” or equivalent transaction message or command to the power savings application 120 and the utility control center 200 (via the UCC command processor 104).
Turning now to
When the ALC manager 108 receives (806) a transaction message from the master event manager 106, the ALC manager 108 first determines (808) the type of transaction received. If the ALC manager 108 receives a “Cut” or equivalent transaction message or command from the master event manager 106, the ALC manager 108 enters (810) a “Manage” logical state. The ALC manager 108 then determines (812) which active load clients 300 and associated devices 402-412, 420 operating on the utility specified in the “Cut” message to switch to the “Off” state. If a location (e.g., list of GPS coordinates, a GPS coordinate range, a geographic area, or a power grid reference area) is included in the “Cut” transaction message, only those active load clients 300 within the specified location are selected for switching to the “Off” state. In other words, the ALC manager 108 selects the group of active load client devices 300 to which the issue a “Turn Off” transaction message based at least partially on the geographic location of each active load client 300 as such location relates to any location identified in the received “Cut” transaction message. The ALD database 124 contains information on the present power consumption (and/or the average power consumption) for each controllable device 402-412, 420 connected to each active load client 300 in the system 10. The ALC manager 108 utilizes the stored power consumption information to determine how many, and to select which, devices 402-412, 420 to turn off to achieve the power reduction required by the “Cut” message. The ALC manager 108 then sends (814) a “Turn Off” or equivalent transaction message or command to each active load client 300, along with a list of the devices to be turned off and a “change state to off” indication for each device 402-412, 420 in the list. The ALC manager 108 then logs (816) the amount of power (either actual or average), as determined from the ALD database 124, saved for each active load client 300, along with a time stamp indicating when the power was reduced. The ALC manager 108 then schedules (818) transactions for itself to “Turn On” each turned-off device after a predetermined period of time (e.g., which may have been set from a utility specified default, set by instructions from the customer, or otherwise programmed into the ALC manager 108).
Returning back to block 808, when the ALC manager 108 receives a “Turn On” or equivalent transaction message or command from the master event manager 106 for a specified active load client 300, and the ALC manager's state is currently in a “Manage” state, the ALC manager 108 finds (820) one or more active load clients 300 that are in the “On” state and do not have any of their managed devices 402-412, 420 turned off (and are in the specified location if so required by the original “Cut” transaction message), which, when one or more of such devices 402-412, 420 are turned off, will save the same or substantially the same amount of power that is presently being saved by the specified active load clients that are in the “Off” state. Upon identifying new active load clients 300 from which to save power, the ALC manager 108 sends (822) a “Turn Off” or equivalent transaction message or command to each active load client 300 that must be turned off in order to save the same amount of power as the active load client(s) to be turned on (i.e. to have its or their managed devices 402-412, 420 turned on) or to save an otherwise acceptable amount of power (e.g., a portion of the power previously saved by the active load client(s) to be turned back on). The ALC manager 108 also sends (824) a “Turn On” or equivalent transaction message or command to each active load client 300 to be turned back on. The “Turn On” message instructs all active load clients 300 to which the message was directed to turn on any controllable devices that have been turned off, and causes the affected active load clients 300 to instruct their controllable devices 402-412, 420 to enable the flow of electric power to their associated power consuming devices (e.g., appliance, HVAC unit, and so forth). Finally, the ALC manager 108 logs (826) the time that the “Turn On” transaction message is sent in the ALD database 124.
Returning once again to block 808, when the ALC manager 108 receives an “End Event” or equivalent transaction message or command from the master event manager 106, the ALC manager 108 sends (828) a “Turn On” or equivalent transaction message or command to every active load client 300 which is currently in the “Off” state and is served by the serving utility identified in the “End Event” message or to which the “End Event” message relates. Upon determining (830) that all the appropriate active load clients 300 have transitioned to the “On” state, the ALC manager 108 sends (832) an “Event Ended” or equivalent transaction message or command to the master event manager 106.
Referring now to
According to the logic flow of
As described above, the present invention encompasses a method for managing and distributing power within a power management system based on real-time feedback from addressable and remotely controllable devices including the actual amount of power currently being individually or collectively consumed by the addressable devices. With this invention, a power management system may pinpoint specific areas of high power usage and more accurately distribute power loads to utilities in need. Additionally, the present invention provides optional participation incentives for customers based on the amount of their actual participation in the power management system.
In the foregoing specification, the present invention has been described with reference to specific embodiments. However, one of ordinary skill in the art will appreciate that various modifications and changes may be made without departing from the spirit and scope of the present invention as set forth in the appended claims. For example, the present invention is applicable for managing the distribution of power from utility companies to subscribing customers using any number of IP-based or other communication methods. Additionally, the functions of specific modules within the ALD server 100 and/or active load client 300 may be performed by one or more equivalent means. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments of the present invention. However, the benefits, advantages, solutions to problems, and any element(s) that may cause or result in such benefits, advantages, or solutions to become more pronounced are not to be construed as a critical, required, or essential feature or element of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
This application relates to and claims priority from the following U.S. Patent Applications. This application is a continuation of U.S. patent application Ser. No. 16/549,509 filed on Aug. 23, 2019 and issued as U.S. Pat. No. 11,022,995, which is a continuation of U.S. Patent application Ser. No. 15/618,981 filed on Jun. 9, 2017 and issued as U.S. Pat. No. 10,394,268, which is a continuation of U.S. patent application Ser. No. 14/456,306 filed on Aug. 11, 2014 and issued as U.S. Pat. No. 9,678,522, which is a continuation of U.S. patent application Ser. No. 13/463,761 filed on May 3, 2012 and issued as U.S. Pat. No. 8,805,552, which is a continuation-in-part of U.S. patent application Ser. No. 13/172,389 filed on Jun. 29, 2011 and issued as U.S. Pat. No. 8,315,717, which is a continuation of U.S. patent application Ser. No. 12/715,195 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,032,233, which is a divisional of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951, all of which are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3906242 | Stevenson | Sep 1975 | A |
| 4023043 | Stevenson | May 1977 | A |
| 4589075 | Buennagel | May 1986 | A |
| 4799059 | Grindahl et al. | Jan 1989 | A |
| 4819180 | Hedman et al. | Apr 1989 | A |
| 4819229 | Pritty et al. | Apr 1989 | A |
| 5237507 | Chasek | Aug 1993 | A |
| 5361982 | Liebl et al. | Nov 1994 | A |
| 5388101 | Dinkins | Feb 1995 | A |
| 5462225 | Massara et al. | Oct 1995 | A |
| 5481546 | Dinkins | Jan 1996 | A |
| 5502339 | Hartig | Mar 1996 | A |
| 5544036 | Brown et al. | Aug 1996 | A |
| 5570002 | Castleman | Oct 1996 | A |
| 5592491 | Dinkins | Jan 1997 | A |
| 5640153 | Hildebrand et al. | Jun 1997 | A |
| 5644173 | Elliason et al. | Jul 1997 | A |
| 5675503 | Moe et al. | Oct 1997 | A |
| 5696695 | Ehlers et al. | Dec 1997 | A |
| 5721936 | Kikinis et al. | Feb 1998 | A |
| 5926776 | Glorioso et al. | Jul 1999 | A |
| 5973481 | Thompson et al. | Oct 1999 | A |
| 6018690 | Saito et al. | Jan 2000 | A |
| 6037758 | Perez | Mar 2000 | A |
| 6078785 | Bush | Jun 2000 | A |
| 6102487 | Oevreboe | Aug 2000 | A |
| 6107693 | Mongia et al. | Aug 2000 | A |
| 6115676 | Rector et al. | Sep 2000 | A |
| 6154859 | Norizuki et al. | Nov 2000 | A |
| 6216956 | Ehlers et al. | Apr 2001 | B1 |
| 6233327 | Petite | May 2001 | B1 |
| 6254009 | Proffitt et al. | Jul 2001 | B1 |
| 6304552 | Chapman et al. | Oct 2001 | B1 |
| 6366217 | Cunningham et al. | Apr 2002 | B1 |
| 6374101 | Gelbien | Apr 2002 | B1 |
| 6437692 | Petite et al. | Aug 2002 | B1 |
| 6519509 | Nierlich et al. | Feb 2003 | B1 |
| 6529839 | Uggerud et al. | Mar 2003 | B1 |
| 6535797 | Bowles et al. | Mar 2003 | B1 |
| 6577962 | Afshari | Jun 2003 | B1 |
| 6583521 | Lagod et al. | Jun 2003 | B1 |
| 6601033 | Sowinski | Jul 2003 | B1 |
| 6602627 | Liu et al. | Aug 2003 | B2 |
| 6621179 | Howard | Sep 2003 | B1 |
| 6622097 | Hunter | Sep 2003 | B2 |
| 6622925 | Carner et al. | Sep 2003 | B2 |
| 6633823 | Bartone et al. | Oct 2003 | B2 |
| 6636977 | Chen | Oct 2003 | B1 |
| 6671586 | Davis et al. | Dec 2003 | B2 |
| 6681154 | Nierlich et al. | Jan 2004 | B2 |
| 6687574 | Pietrowicz et al. | Feb 2004 | B2 |
| 6718761 | Merswolke et al. | Apr 2004 | B2 |
| 6732055 | Bagepalli et al. | May 2004 | B2 |
| 6747368 | Jarrett | Jun 2004 | B2 |
| 6778882 | Spool et al. | Aug 2004 | B2 |
| 6784807 | Petite et al. | Aug 2004 | B2 |
| 6832135 | Ying | Dec 2004 | B2 |
| 6834811 | Huberman et al. | Dec 2004 | B1 |
| 6836737 | Petite et al. | Dec 2004 | B2 |
| 6862498 | Davis et al. | Mar 2005 | B2 |
| 6865450 | Masticola et al. | Mar 2005 | B2 |
| 6868293 | Schurr et al. | Mar 2005 | B1 |
| 6879059 | Sleva | Apr 2005 | B2 |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6904336 | Raines et al. | Jun 2005 | B2 |
| 6906617 | Van der Meulen | Jun 2005 | B1 |
| 6909942 | Andarawis et al. | Jun 2005 | B2 |
| 6914533 | Petite | Jul 2005 | B2 |
| 6914893 | Petite | Jul 2005 | B2 |
| 6934316 | Cornwall et al. | Aug 2005 | B2 |
| 6944555 | Blackett et al. | Sep 2005 | B2 |
| 6961641 | Forth et al. | Nov 2005 | B1 |
| 6990593 | Nakagawa | Jan 2006 | B2 |
| 7003640 | Mayo et al. | Feb 2006 | B2 |
| 7019667 | Petite et al. | Mar 2006 | B2 |
| 7035719 | Howard et al. | Apr 2006 | B2 |
| 7039532 | Hunter | May 2006 | B2 |
| 7053767 | Petite et al. | May 2006 | B2 |
| 7088014 | Nierlich et al. | Aug 2006 | B2 |
| 7103511 | Petite | Sep 2006 | B2 |
| 7123994 | Weik et al. | Oct 2006 | B2 |
| 7133750 | Raines et al. | Nov 2006 | B2 |
| 7136725 | Paciorek et al. | Nov 2006 | B1 |
| 7141321 | McArthur et al. | Nov 2006 | B2 |
| 7142949 | Brewster et al. | Nov 2006 | B2 |
| 7177728 | Gardner | Feb 2007 | B2 |
| 7181320 | Whiffen et al. | Feb 2007 | B2 |
| 7184861 | Petite | Feb 2007 | B2 |
| 7200134 | Proctor et al. | Apr 2007 | B2 |
| 7206670 | Pimputkar et al. | Apr 2007 | B2 |
| 7209804 | Curt et al. | Apr 2007 | B2 |
| 7209840 | Petite et al. | Apr 2007 | B2 |
| 7233843 | Budhraja et al. | Jun 2007 | B2 |
| 7263073 | Petite et al. | Aug 2007 | B2 |
| 7263450 | Hunter | Aug 2007 | B2 |
| 7274975 | Miller | Sep 2007 | B2 |
| 7289887 | Rodgers | Oct 2007 | B2 |
| 7295128 | Petite | Nov 2007 | B2 |
| 7305282 | Chen | Dec 2007 | B2 |
| 7313465 | O'Donnell | Dec 2007 | B1 |
| 7343341 | Sandor et al. | Mar 2008 | B2 |
| 7345998 | Cregg et al. | Mar 2008 | B2 |
| 7346463 | Petite et al. | Mar 2008 | B2 |
| 7366164 | Habib et al. | Apr 2008 | B1 |
| 7397907 | Petite | Jul 2008 | B2 |
| 7406364 | Rissanen et al. | Jul 2008 | B2 |
| 7412304 | Uenou | Aug 2008 | B2 |
| 7424527 | Petite | Sep 2008 | B2 |
| 7440871 | McConnell et al. | Oct 2008 | B2 |
| 7451019 | Rodgers | Nov 2008 | B2 |
| 7468661 | Petite et al. | Dec 2008 | B2 |
| 7480501 | Petite | Jan 2009 | B2 |
| 7486681 | Weber | Feb 2009 | B2 |
| 7492617 | Petter et al. | Feb 2009 | B2 |
| 7528503 | Rognli et al. | May 2009 | B2 |
| 7536240 | McIntyre et al. | May 2009 | B2 |
| 7541941 | Bogolea et al. | Jun 2009 | B2 |
| 7565227 | Richard et al. | Jul 2009 | B2 |
| 7650425 | Davis et al. | Jan 2010 | B2 |
| 7697492 | Petite | Apr 2010 | B2 |
| 7698233 | Edwards et al. | Apr 2010 | B1 |
| 7711796 | Gutt et al. | May 2010 | B2 |
| 7715951 | Forbes et al. | May 2010 | B2 |
| 7738999 | Petite | Jun 2010 | B2 |
| 7739378 | Petite | Jun 2010 | B2 |
| 7747165 | Emery et al. | Jun 2010 | B2 |
| 7940901 | Paraskevakos et al. | May 2011 | B2 |
| 8010812 | Forbes et al. | Aug 2011 | B2 |
| 8032233 | Forbes et al. | Oct 2011 | B2 |
| 8032461 | Winter et al. | Oct 2011 | B2 |
| 8046110 | Mayor et al. | Oct 2011 | B2 |
| 8068938 | Fujita | Nov 2011 | B2 |
| 8131403 | Forbes et al. | Mar 2012 | B2 |
| 8145361 | Forbes et al. | Mar 2012 | B2 |
| 8260468 | Ippolito et al. | Sep 2012 | B2 |
| 8260470 | Forbes et al. | Sep 2012 | B2 |
| 8295989 | Rettger et al. | Oct 2012 | B2 |
| 8307225 | Forbes et al. | Nov 2012 | B2 |
| 8315717 | Forbes et al. | Nov 2012 | B2 |
| 8315743 | Sackman et al. | Nov 2012 | B2 |
| 8359124 | Zhou et al. | Jan 2013 | B2 |
| 8359215 | Robbins et al. | Jan 2013 | B1 |
| 8364609 | Ozog | Jan 2013 | B2 |
| 8396606 | Forbes et al. | Mar 2013 | B2 |
| 8407252 | Bennett et al. | Mar 2013 | B2 |
| 8417569 | Gross | Apr 2013 | B2 |
| 8428752 | Bennett et al. | Apr 2013 | B2 |
| 8442917 | Burke | May 2013 | B1 |
| 8457802 | Steven et al. | Jun 2013 | B1 |
| 8463449 | Sanders | Jun 2013 | B2 |
| 8473111 | Shankar et al. | Jun 2013 | B1 |
| 8527107 | Forbes et al. | Sep 2013 | B2 |
| 8570999 | Nguyen | Oct 2013 | B1 |
| 8571930 | Galperin | Oct 2013 | B1 |
| 8583520 | Forbes | Nov 2013 | B1 |
| 8588991 | Forbes, Jr. | Nov 2013 | B1 |
| 8600556 | Nesler et al. | Dec 2013 | B2 |
| 8684266 | Bennett et al. | Apr 2014 | B2 |
| 8761952 | Forbes | Jun 2014 | B2 |
| 8805552 | Forbes | Aug 2014 | B2 |
| 8806239 | Forbes | Aug 2014 | B2 |
| 8890505 | Forbes | Nov 2014 | B2 |
| 8983669 | Forbes, Jr. | Mar 2015 | B2 |
| 8996183 | Forbes | Mar 2015 | B2 |
| 9177323 | Forbes | Nov 2015 | B2 |
| 9461471 | Forbes, Jr. | Oct 2016 | B2 |
| 9651973 | Forbes, Jr. | May 2017 | B2 |
| 9766644 | Forbes, Jr. | Sep 2017 | B2 |
| 9952611 | Forbes, Jr. | Apr 2018 | B2 |
| 9989982 | Forbes, Jr. | Jun 2018 | B2 |
| 10394268 | Forbes, Jr. | Aug 2019 | B2 |
| 11022995 | Forbes, Jr. | Jun 2021 | B2 |
| 20010030468 | Anderson et al. | Oct 2001 | A1 |
| 20010038343 | Meyer et al. | Nov 2001 | A1 |
| 20020019758 | Scarpelli | Feb 2002 | A1 |
| 20020019802 | Malme et al. | Feb 2002 | A1 |
| 20020035496 | Fukushima et al. | Mar 2002 | A1 |
| 20020036430 | Welches et al. | Mar 2002 | A1 |
| 20020109607 | Cumeralto et al. | Aug 2002 | A1 |
| 20020138176 | Davis et al. | Sep 2002 | A1 |
| 20020143693 | Soestbergen et al. | Oct 2002 | A1 |
| 20020161648 | Mason et al. | Oct 2002 | A1 |
| 20020198629 | Ellis | Dec 2002 | A1 |
| 20030009401 | Ellis | Jan 2003 | A1 |
| 20030009705 | Thelander et al. | Jan 2003 | A1 |
| 20030036820 | Yellepeddy et al. | Feb 2003 | A1 |
| 20030083980 | Satake | May 2003 | A1 |
| 20030144864 | Mazzarella | Jul 2003 | A1 |
| 20030149937 | McElfresh et al. | Aug 2003 | A1 |
| 20030158632 | Nierlich et al. | Aug 2003 | A1 |
| 20030167178 | Jarman et al. | Sep 2003 | A1 |
| 20030176952 | Collins | Sep 2003 | A1 |
| 20030193405 | Hunt et al. | Oct 2003 | A1 |
| 20030225483 | Santinato et al. | Dec 2003 | A1 |
| 20030229572 | Raines et al. | Dec 2003 | A1 |
| 20030233201 | Horst et al. | Dec 2003 | A1 |
| 20040006439 | Hunter | Jan 2004 | A1 |
| 20040024483 | Holcombe | Feb 2004 | A1 |
| 20040044571 | Bronnimann et al. | Mar 2004 | A1 |
| 20040088083 | Davis et al. | May 2004 | A1 |
| 20040095237 | Chen et al. | May 2004 | A1 |
| 20040107025 | Ransom | Jun 2004 | A1 |
| 20040117330 | Ehlers et al. | Jun 2004 | A1 |
| 20040128266 | Yellepeddy et al. | Jul 2004 | A1 |
| 20040138834 | Blackett et al. | Jul 2004 | A1 |
| 20040153170 | Santacatterina et al. | Aug 2004 | A1 |
| 20040158478 | Zimmerman | Aug 2004 | A1 |
| 20040158541 | Notarianni et al. | Aug 2004 | A1 |
| 20040162793 | Scott et al. | Aug 2004 | A1 |
| 20040193329 | Ransom et al. | Sep 2004 | A1 |
| 20040225514 | Greenshields et al. | Nov 2004 | A1 |
| 20040230533 | Benco | Nov 2004 | A1 |
| 20040249775 | Chen | Dec 2004 | A1 |
| 20050021397 | Cui et al. | Jan 2005 | A1 |
| 20050033481 | Budhraja et al. | Feb 2005 | A1 |
| 20050055432 | Rodgers | Mar 2005 | A1 |
| 20050065742 | Rodgers | Mar 2005 | A1 |
| 20050080772 | Bem | Apr 2005 | A1 |
| 20050096856 | Lubkeman et al. | May 2005 | A1 |
| 20050096857 | Hunter | May 2005 | A1 |
| 20050096979 | Koningstein | May 2005 | A1 |
| 20050097204 | Horowitz et al. | May 2005 | A1 |
| 20050125243 | Villalobos | Jun 2005 | A1 |
| 20050127680 | Lof et al. | Jun 2005 | A1 |
| 20050138432 | Ransom | Jun 2005 | A1 |
| 20050192711 | Raines et al. | Sep 2005 | A1 |
| 20050192713 | Weik et al. | Sep 2005 | A1 |
| 20050197742 | Scott et al. | Sep 2005 | A1 |
| 20050216302 | Raji et al. | Sep 2005 | A1 |
| 20050216580 | Raji et al. | Sep 2005 | A1 |
| 20050234600 | Boucher et al. | Oct 2005 | A1 |
| 20050240314 | Martinez | Oct 2005 | A1 |
| 20050240315 | Booth et al. | Oct 2005 | A1 |
| 20050246190 | Sandor et al. | Nov 2005 | A1 |
| 20050267642 | Whiffen et al. | Dec 2005 | A1 |
| 20050276222 | Kumar et al. | Dec 2005 | A1 |
| 20050288954 | McCarthy et al. | Dec 2005 | A1 |
| 20060020544 | Kaveski | Jan 2006 | A1 |
| 20060020596 | Liu et al. | Jan 2006 | A1 |
| 20060022841 | Hoiness et al. | Feb 2006 | A1 |
| 20060025891 | Budike | Feb 2006 | A1 |
| 20060031934 | Kriegel | Feb 2006 | A1 |
| 20060064205 | Ying | Mar 2006 | A1 |
| 20060069616 | Bau | Mar 2006 | A1 |
| 20060106635 | Ulrich et al. | May 2006 | A1 |
| 20060142900 | Rothman et al. | Jun 2006 | A1 |
| 20060142961 | Johnson et al. | Jun 2006 | A1 |
| 20060161310 | Lal | Jul 2006 | A1 |
| 20060161450 | Carey et al. | Jul 2006 | A1 |
| 20060168191 | Ives | Jul 2006 | A1 |
| 20060190354 | Meisel et al. | Aug 2006 | A1 |
| 20060195334 | Reeb et al. | Aug 2006 | A1 |
| 20060212350 | Ellis et al. | Sep 2006 | A1 |
| 20060224615 | Korn et al. | Oct 2006 | A1 |
| 20060241244 | Soeda et al. | Oct 2006 | A1 |
| 20060241314 | Sullivan et al. | Oct 2006 | A1 |
| 20060271244 | Cumming et al. | Nov 2006 | A1 |
| 20060271314 | Hayes | Nov 2006 | A1 |
| 20060276938 | Miller | Dec 2006 | A1 |
| 20060282328 | Gerace et al. | Dec 2006 | A1 |
| 20070021874 | Rognli et al. | Jan 2007 | A1 |
| 20070038563 | Ryzerski | Feb 2007 | A1 |
| 20070043478 | Ehlers et al. | Feb 2007 | A1 |
| 20070058453 | Shaffer et al. | Mar 2007 | A1 |
| 20070058629 | Luft | Mar 2007 | A1 |
| 20070070895 | Narvaez | Mar 2007 | A1 |
| 20070085702 | Walters et al. | Apr 2007 | A1 |
| 20070091900 | Asthana et al. | Apr 2007 | A1 |
| 20070094043 | Bannai et al. | Apr 2007 | A1 |
| 20070100503 | Balan et al. | May 2007 | A1 |
| 20070100961 | Moore | May 2007 | A1 |
| 20070150353 | Krassner et al. | Jun 2007 | A1 |
| 20070155349 | Nelson et al. | Jul 2007 | A1 |
| 20070156621 | Wright et al. | Jul 2007 | A1 |
| 20070156887 | Wright et al. | Jul 2007 | A1 |
| 20070174114 | Bigby et al. | Jul 2007 | A1 |
| 20070192333 | Ali | Aug 2007 | A1 |
| 20070203722 | Richards et al. | Aug 2007 | A1 |
| 20070204176 | Shaffer et al. | Aug 2007 | A1 |
| 20070213878 | Chen | Sep 2007 | A1 |
| 20070214118 | Schoen et al. | Sep 2007 | A1 |
| 20070214132 | Grubb et al. | Sep 2007 | A1 |
| 20070255457 | Whitcomb et al. | Nov 2007 | A1 |
| 20070260540 | Chau et al. | Nov 2007 | A1 |
| 20070282495 | Kempton et al. | Dec 2007 | A1 |
| 20070286210 | Gutt et al. | Dec 2007 | A1 |
| 20070291644 | Roberts et al. | Dec 2007 | A1 |
| 20070299562 | Kates | Dec 2007 | A1 |
| 20080010212 | Moore et al. | Jan 2008 | A1 |
| 20080015976 | Sandor et al. | Jan 2008 | A1 |
| 20080040223 | Bridges et al. | Feb 2008 | A1 |
| 20080091625 | Kremen | Apr 2008 | A1 |
| 20080104026 | Koran | May 2008 | A1 |
| 20080109387 | Deaver et al. | May 2008 | A1 |
| 20080130673 | Cregg et al. | Jun 2008 | A1 |
| 20080147465 | Raines et al. | Jun 2008 | A1 |
| 20080154801 | Fein et al. | Jun 2008 | A1 |
| 20080165714 | Dettinger et al. | Jul 2008 | A1 |
| 20080172312 | Synesiou et al. | Jul 2008 | A1 |
| 20080177423 | Brickfield et al. | Jul 2008 | A1 |
| 20080177678 | Di Martini et al. | Jul 2008 | A1 |
| 20080186202 | Vaswani et al. | Aug 2008 | A1 |
| 20080195462 | Magdon-Ismail et al. | Aug 2008 | A1 |
| 20080224892 | Bogolea et al. | Sep 2008 | A1 |
| 20080231114 | Tolnar et al. | Sep 2008 | A1 |
| 20080234957 | Banhegyesi et al. | Sep 2008 | A1 |
| 20080238710 | Tolnar et al. | Oct 2008 | A1 |
| 20080249832 | Richardson et al. | Oct 2008 | A1 |
| 20080255899 | McConnell et al. | Oct 2008 | A1 |
| 20080263025 | Koran | Oct 2008 | A1 |
| 20080265799 | Sibert | Oct 2008 | A1 |
| 20080270223 | Collins et al. | Oct 2008 | A1 |
| 20080272934 | Wang et al. | Nov 2008 | A1 |
| 20080281473 | Pitt | Nov 2008 | A1 |
| 20080306824 | Parkinson | Dec 2008 | A1 |
| 20080306830 | Lasa et al. | Dec 2008 | A1 |
| 20080313632 | Kumar et al. | Dec 2008 | A1 |
| 20080319893 | Mashinsky et al. | Dec 2008 | A1 |
| 20090012996 | Gupta et al. | Jan 2009 | A1 |
| 20090018884 | McConnell et al. | Jan 2009 | A1 |
| 20090024718 | Anagnostopoulos et al. | Jan 2009 | A1 |
| 20090038343 | Gibson | Feb 2009 | A1 |
| 20090043519 | Bridges et al. | Feb 2009 | A1 |
| 20090043520 | Pollack et al. | Feb 2009 | A1 |
| 20090045804 | Durling et al. | Feb 2009 | A1 |
| 20090055031 | Slota et al. | Feb 2009 | A1 |
| 20090055032 | Rodgers | Feb 2009 | A1 |
| 20090062970 | Forbes et al. | Mar 2009 | A1 |
| 20090063228 | Forbes, Jr. | Mar 2009 | A1 |
| 20090088907 | Lewis et al. | Apr 2009 | A1 |
| 20090112701 | Turpin | Apr 2009 | A1 |
| 20090112758 | Herzig | Apr 2009 | A1 |
| 20090124241 | Krishnaswamy et al. | May 2009 | A1 |
| 20090125462 | Krishnaswamy et al. | May 2009 | A1 |
| 20090135836 | Veillette | May 2009 | A1 |
| 20090138362 | Schroedl et al. | May 2009 | A1 |
| 20090157529 | Ehlers et al. | Jun 2009 | A1 |
| 20090187344 | Brancaccio et al. | Jul 2009 | A1 |
| 20090187499 | Mulder et al. | Jul 2009 | A1 |
| 20090198384 | Ahn | Aug 2009 | A1 |
| 20090228335 | Niyogi et al. | Sep 2009 | A1 |
| 20090240381 | Lane | Sep 2009 | A1 |
| 20090240677 | Parekh et al. | Sep 2009 | A1 |
| 20090281673 | Taft | Nov 2009 | A1 |
| 20090281674 | Taft | Nov 2009 | A1 |
| 20090313034 | Ferro et al. | Dec 2009 | A1 |
| 20090313103 | Ambrosio et al. | Dec 2009 | A1 |
| 20090319415 | Stoilov et al. | Dec 2009 | A1 |
| 20100045232 | Chen et al. | Feb 2010 | A1 |
| 20100076835 | Silverman | Mar 2010 | A1 |
| 20100082464 | Keefe | Apr 2010 | A1 |
| 20100094981 | Cordray et al. | Apr 2010 | A1 |
| 20100106575 | Bixby | Apr 2010 | A1 |
| 20100106641 | Chassin et al. | Apr 2010 | A1 |
| 20100138452 | Henkin et al. | Jun 2010 | A1 |
| 20100163634 | Klein et al. | Jul 2010 | A1 |
| 20100169175 | Koran | Jul 2010 | A1 |
| 20100179862 | Chassin et al. | Jul 2010 | A1 |
| 20100191862 | Forbes et al. | Jul 2010 | A1 |
| 20100217452 | McCord et al. | Aug 2010 | A1 |
| 20100217549 | Galvin et al. | Aug 2010 | A1 |
| 20100217550 | Crabtree et al. | Aug 2010 | A1 |
| 20100217642 | Crubtree et al. | Aug 2010 | A1 |
| 20100218108 | Crabtree et al. | Aug 2010 | A1 |
| 20100222935 | Forbes, Jr. | Sep 2010 | A1 |
| 20100235008 | Forbes, Jr. | Sep 2010 | A1 |
| 20100274407 | Creed | Oct 2010 | A1 |
| 20100293045 | Burns et al. | Nov 2010 | A1 |
| 20100306033 | Oved et al. | Dec 2010 | A1 |
| 20100324748 | Voysey | Dec 2010 | A1 |
| 20100328849 | Ewing et al. | Dec 2010 | A1 |
| 20100332373 | Crabtree et al. | Dec 2010 | A1 |
| 20110007824 | Bridges et al. | Jan 2011 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110025556 | Bridges et al. | Feb 2011 | A1 |
| 20110029655 | Forbes et al. | Feb 2011 | A1 |
| 20110055036 | Helfan | Mar 2011 | A1 |
| 20110060474 | Schmiegel et al. | Mar 2011 | A1 |
| 20110080044 | Schmiegel | Apr 2011 | A1 |
| 20110106729 | Billingsley et al. | May 2011 | A1 |
| 20110115302 | Slota et al. | May 2011 | A1 |
| 20110130982 | Haag et al. | Jun 2011 | A1 |
| 20110133655 | Recker et al. | Jun 2011 | A1 |
| 20110138198 | Boss et al. | Jun 2011 | A1 |
| 20110145061 | Spurr et al. | Jun 2011 | A1 |
| 20110147360 | Hammerstrom | Jun 2011 | A1 |
| 20110161250 | Koeppel et al. | Jun 2011 | A1 |
| 20110172841 | Forbes, Jr. | Jul 2011 | A1 |
| 20110178610 | O'Connor et al. | Jul 2011 | A1 |
| 20110185303 | Katagi et al. | Jul 2011 | A1 |
| 20110196546 | Muller et al. | Aug 2011 | A1 |
| 20110196547 | Park et al. | Aug 2011 | A1 |
| 20110204717 | Shaffer | Aug 2011 | A1 |
| 20110204719 | Sackman et al. | Aug 2011 | A1 |
| 20110208366 | Taft | Aug 2011 | A1 |
| 20110208367 | Sackman et al. | Aug 2011 | A1 |
| 20110231028 | Ozog | Sep 2011 | A1 |
| 20110235656 | Pigeon | Sep 2011 | A1 |
| 20110251730 | Pitt | Oct 2011 | A1 |
| 20110257809 | Forbes et al. | Oct 2011 | A1 |
| 20110258022 | Forbes, Jr. et al. | Oct 2011 | A1 |
| 20110267202 | Efthymiou et al. | Nov 2011 | A1 |
| 20110270452 | Lu et al. | Nov 2011 | A1 |
| 20110270682 | Valin | Nov 2011 | A1 |
| 20120004872 | Oh et al. | Jan 2012 | A1 |
| 20120029897 | Cherian et al. | Feb 2012 | A1 |
| 20120059532 | Reifenhaeuser et al. | Mar 2012 | A1 |
| 20120078427 | Jang et al. | Mar 2012 | A1 |
| 20120089263 | Park et al. | Apr 2012 | A1 |
| 20120095841 | Luckerman et al. | Apr 2012 | A1 |
| 20120101652 | Shin et al. | Apr 2012 | A1 |
| 20120131100 | Van Olst et al. | May 2012 | A1 |
| 20120146799 | Bell et al. | Jun 2012 | A1 |
| 20120153888 | Jung | Jun 2012 | A1 |
| 20120154171 | Hurri et al. | Jun 2012 | A1 |
| 20120166011 | Oba et al. | Jun 2012 | A1 |
| 20120196482 | Stokoe | Aug 2012 | A1 |
| 20120205977 | Shin et al. | Aug 2012 | A1 |
| 20120221162 | Forbes | Aug 2012 | A1 |
| 20120223840 | Guymon et al. | Sep 2012 | A1 |
| 20120226384 | Forbes | Sep 2012 | A1 |
| 20120232816 | Oh et al. | Sep 2012 | A1 |
| 20120239218 | Forbes | Sep 2012 | A1 |
| 20120239219 | Forbes | Sep 2012 | A1 |
| 20120245753 | Forbes | Sep 2012 | A1 |
| 20120259760 | Sgouridis et al. | Oct 2012 | A1 |
| 20120271686 | Silverman | Oct 2012 | A1 |
| 20120296799 | Playfair et al. | Nov 2012 | A1 |
| 20120310800 | Xia et al. | Dec 2012 | A1 |
| 20120316691 | Boardman et al. | Dec 2012 | A1 |
| 20120316697 | Boardman et al. | Dec 2012 | A1 |
| 20130006435 | Berrios et al. | Jan 2013 | A1 |
| 20130031201 | Kagan et al. | Jan 2013 | A1 |
| 20130035802 | Khaitan et al. | Feb 2013 | A1 |
| 20130036311 | Akyol et al. | Feb 2013 | A1 |
| 20130038468 | Wang et al. | Feb 2013 | A1 |
| 20130079939 | Thomas et al. | Mar 2013 | A1 |
| 20130079943 | Darden | Mar 2013 | A1 |
| 20130090935 | Uselton | Apr 2013 | A1 |
| 20130110297 | Reichmuth et al. | May 2013 | A1 |
| 20130123998 | King et al. | May 2013 | A1 |
| 20130144768 | Rohrbaugh | Jun 2013 | A1 |
| 20130173360 | Thatcher | Jul 2013 | A1 |
| 20130191260 | Michael | Jul 2013 | A1 |
| 20140018969 | Forbes | Jan 2014 | A1 |
| 20140025486 | Bigby et al. | Jan 2014 | A1 |
| 20140039699 | Forbes, Jr. | Feb 2014 | A1 |
| 20140039701 | Forbes | Feb 2014 | A1 |
| 20140039703 | Forbes | Feb 2014 | A1 |
| 20140316876 | Silverman | Oct 2014 | A1 |
| 20150303691 | Forbes | Oct 2015 | A1 |
| 20170277214 | Forbes, Jr. | Sep 2017 | A1 |
| 20200050227 | Forbes, Jr. | Feb 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1729223 | Dec 2006 | EP |
| 2000078748 | Mar 2000 | JP |
| 2001306839 | Nov 2001 | JP |
| 2004180412 | Jun 2004 | JP |
| 2004248174 | Sep 2004 | JP |
| 2006060911 | Mar 2006 | JP |
| 2007132553 | May 2007 | JP |
| 20050045272 | May 2005 | KR |
| 20060036171 | Apr 2006 | KR |
| 20070008321 | Jan 2007 | KR |
| 100701298 | Mar 2007 | KR |
| 20070098172 | Oct 2007 | KR |
| 20080112692 | Dec 2008 | KR |
| 2007136456 | Nov 2007 | WO |
| 2008125696 | Oct 2008 | WO |
| Entry |
|---|
| B.J. Kirby, Spinning Reserve from Responsive Loads, Oak Ridge National Laboratory, United States Dept. of Energy, Mar. 2003 (54 pages). |
| Byers J. Risk Management and Monetizing the Commodity Storage Option. Natural Gas & Electricity [serial online]. Jul. 2005; 21 (12):1-8. Available from: Business Source Complete, Ipswich, MA. |
| C.W. Gellings and W.M. Smith, Integrating Demand-Side Management into Utility Planning, Proceedings of the IEEE, vol. 77, Issue: 6, Jun. 1989, pp. 908-918 (Abstract only). |
| Eric Hirst and Brendan Kirby, Opportunities for Demand Participation in New England Contingency-Reserve Markets, New England Demand Response Initiative, Feb. 2003 (15 pages). |
| Eric Hirst and Richard Cowart, Demand Side Resources and Reliability, New England Demand Response Initiative, Mar. 20, 2002 (32 pages). |
| Galvin Electricity Institute: Frequently Asked Questions, printed Apr. 23, 2014, same page available through archive.org unchanged Mar. 1, 2008. |
| GE Digital Energy Residential Electrical Metering Brochure. Sep. 12, 2012. https://web.archive.org/web/20120912144353/http://www.gedigitalenergry.com/products/brochures/1210-Family.pdf. |
| Illinois General Assembly: Public Act 094-0977, Effective Date: Jun. 30, 2006. |
| Kamat R., Oren S. Two-Settlement Systems for Electricity Markets under Network Uncertainty and Market Power Journal of Regulatory Economics [serial online]. Jan. 2004; 25(1):5-37. |
| Kathleen Spees and Lester B. Lave, Demand Response and Electricity Market Efficiency, The Electricity Journal, vol. 20, Issue 3, Apr. 2007 (online Mar. 27, 2007), pp. 69-85 (Abstract only). |
| L.T. Anstine, R.E. Burke, J.E. Casey, R. Holgate, R.S. John, and H.G. Stewart, Application of Probability Methods to the Determination of Spinning Reserve Requirements for the Pennsylvania-New Jersey-Maryland Interconnection; IEEE Transactions on Power Apparatus and Systems, vol. 82, Issue 68, Oct. 1963, pp. 726-735 (Abstract only). |
| Lobsenz G. Maryland Regulators Reject BG&E Smart Grid Proposal. Energy Daily [serial online]. Jun. 23, 2010; (118):3. Available from: Business Source Complete, Ipswich, MA. |
| M. Rashidi-Nejad, Y.H. Song, and M.H. Javidi-Dasht-Bayaz, Operating Reserve Provision in Deregulated Power Markets, IEEE Power Engineering Society Winter Meeting, vol. 2, 2002, pp. 1305-1310 (Abstract only). |
| Michael Ahlheim and Friedrich Schneider; “Allowing for Household Preferences in Emission Trading, A Contribution to the Climate Policy Debate”; Environmental and Resource Economics, vol. 21, pp. 317-342; Kluwer Academic Publishers; The Netherlands; 2002. |
| Olivier Rousse; “Environmental and economic benefits resulting from citizens' participation in CO.sub.2 emissions trading: An efficient alternative solution to the voluntary compensation of CO.sub.2 emissions”, Energy Policy 36(2008), pp. 388-397; Oct. 29, 2007 (online). |
| Pablo A. Ruiz and Peter W. Sauer, Valuation of Reserve Services, IEEE Proceedings of the 41 sup.st Hawaii International Conference on System Sciences, 2008 (9 pages). |
| Paul Darbee, Insteon Compared, SmartLabs, Inc., Jan. 2, 2006, 69 pages. |
| Paul Darbee, Insteon The Details, Smarthome, Inc., Aug. 11, 2005, 68 pages. |
| Zhu Jinxiang, G. Jordan, and S. Ihara, The Market for Spinning Reserve and Its Impacts on Energy Prices, IEEE Power Engineering Society Winter Meeting, vol. 2, 2000, pp. 1202-1207 (Abstract Only). |
| United States of America Federal Energy Regulatory Commission (FERC), Order No. 745, “Demand Response Compensation in Organized Wholesale Energy Markets”, 134 Ferc ¶ 61,187 (Docket No. RM10-17-000, issued Mar. 15, 2011) (entire document). |
| Number | Date | Country | |
|---|---|---|---|
| 20210278870 A1 | Sep 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11895909 | Aug 2007 | US |
| Child | 12715195 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16549509 | Aug 2019 | US |
| Child | 17329920 | US | |
| Parent | 15618981 | Jun 2017 | US |
| Child | 16549509 | US | |
| Parent | 14456306 | Aug 2014 | US |
| Child | 15618981 | US | |
| Parent | 13463761 | May 2012 | US |
| Child | 14456306 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13172389 | Jun 2011 | US |
| Child | 13463761 | US | |
| Parent | 12715195 | Mar 2010 | US |
| Child | 13172389 | US |
