SYSTEM AND METHODS FOR SMART CHARGING TECHNIQUES

Abstract

A system and methods that enables smart charging techniques. A smart charging method may include periodically updated schedules. In addition, a smart charging method may include schedules with overrides. Further, a smart charging may involve a method for local load management in the presence of uncontrolled loads. A smart charging method for managing electric resources may also provide direct control over prices-to-devices enabled devices.

Description

This non-provisional patent application claims priority to, and incorporates herein by reference Provisional Patent Application No. 61/226,497 filed Jul. 17, 2009. This application also incorporates herein by reference the following: U.S. Provisional Patent Application No. 61/256,278 filed Oct. 29, 2009; U.S. patent application Ser. No. 12/751,837 filed on Mar. 31, 2010; U.S. patent application Ser. No. 12/751,845 filed on Mar. 31, 2010; U.S. patent application Ser. No. 12/751,851 filed on Mar. 31, 2010; U.S. patent application Ser. No. 12/751,852 filed on Mar. 31, 2010; U.S. patent application Ser. No. 12/751,853 filed on Mar. 31, 2010; U.S. patent application No. 12/751,862 filed on Mar. 31, 2010; U.S. patent application Ser. No. 12/252,657 filed Oct. 16, 2008; U.S. patent application Ser. No. 12/252,209 filed Oct. 15, 2008; U.S. patent application Ser. No. 12/252,803 filed Oct. 16, 2008; and U.S. patent application Ser. No. 12/252,950 filed Oct. 16, 2008.

This application includes material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office files or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

The present invention relates in general to the field of charging systems for electrical storage devices, and in particular to novel systems and methods for smart charging and charging distributed loads, such as a multitude of electric vehicle batteries.

BACKGROUND OF THE INVENTION

Low-level electrical and communication interfaces to enable charging and discharging of electric vehicles with respect to the grid is described in U.S. Pat. No. 5,642,270 to Green et al., entitled, “Battery powered electric vehicle and electrical supply system,” incorporated herein by reference. The Green reference describes a bi-directional charging and communication system for grid-connected electric vehicles.

Current power flow management systems have a number of drawbacks. Simple timer systems merely delay charging to a fixed off-peak time. There is a need for the implementation of charge patterns for electric vehicles that provide a satisfactory level of flexibility, control and convenience to electric vehicle owners. Purely schedule-based system cannot address unpredictable operational demands.

Significant opportunities for improvement exist in managing power flow at the customer level. Modern electric vehicles could benefit in a variety of ways from a smart charging program that provides electric vehicle owners with updates and overrides that assist vehicle owners while coordinating the charging activities of a number of vehicles in an efficient manner.

SUMMARY OF THE INVENTION

Electric vehicles could benefit in a variety of ways from a centrally controlled smart charging system administered by a smart charging server. These benefits may include a reduced cost of electricity, reduced congestion of the electric distribution network, and reduced greenhouse gas emissions.

To work effectively, a smart charging system requires the central control of an outside entity via an external network, such as a server. This server would be responsible for coordinating the charging activities of a large number of vehicles distributed over a wide area, such as a city.

While it would be desirable to establish direct low-latency communications links between the server and each device or vehicle in a smart charging network, practical considerations sometimes preclude such direct connections. By using the correct techniques, a smart charging server could still produce substantial benefits while working within the communications constraints present in a particular locale or installation.

An embodiment of a method for smart charging via periodically updated schedules includes periodically transmitting a charging schedule via a network from a server to electric resources. An electric resource receives the charging schedule via the network from the server. Further, the method includes replacing a prior charging schedule with the received charging schedule, where the replaced prior charging schedule previously controlled the charging behavior for the electric resource.

An embodiment of a method for smart charging via schedules with overrides includes periodically transmitting a default charging schedule via a network from a server to electric resources. An electric resource receives the default charging schedule via the network from the server. The method further includes transmitting a charging schedule override from the server to the a electric resource and overriding the default charging schedule with the charging schedule override. The charging schedule override modifies the charging behavior for electric resource.

An embodiment of a method for local load management in the presence of uncontrolled loads includes receiving, at a server, power levels for electric resources located at a site. The method further includes determining a total power level for electric resources, where the electric resources comprise controlled electric resources and uncontrolled electric resources, determining a controlled power level for the controlled electric resources, where the controlled power level is adjustable via the server; and determining an uncontrolled power level for the uncontrolled electric resources based on the total power level and the controlled power level, where the uncontrolled power level is unadjustable via the server. In addition, the method includes managing the total power level for the electric resources based on these determinations. The management of the total power level is performed on a particular machine, which may comprise a physical computing device.

An embodiment of a method for managing electric resources with direct control over prices-to-devices enabled devices including determining an energy price for electric resources, where the electric resources comprise prices-to-devices enabled electric resources. The prices-to-devices enabled electric resources may have configurable rules for determining charging behavior based an energy price. The method includes adjusting the energy price for a prices-to-devices enabled electric resource and transmitting, from a server, the adjusted energy price to the prices-to-devices enabled electric resource. In addition, the method includes managing the charging behavior for the prices-to-devices enabled electric resource based on the adjusted energy price. The management of the charging behavior is performed on a particular machine, which may comprise a physical computing device.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of embodiments as illustrated in the accompanying drawings, in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating principles of the invention.

FIG. 1 is a diagram of an example of a power aggregation system.

FIGS. 2A-2B are diagrams of an example of connections between an electric vehicle, the power grid, and the Internet.

FIG. 3 is a block diagram of an example of connections between an electric resource and a flow control server of the power aggregation system.

FIG. 4 is a diagram of an example of a layout of the power aggregation system.

FIG. 5 is a diagram of an example of control areas in the power aggregation system.

FIG. 6 is a diagram of multiple flow control centers in the power aggregation system and a directory server for determining a flow control center.

FIG. 7 is a block diagram of an example of flow control server.

FIG. 8A is a block diagram of an example of remote intelligent power flow module.

FIG. 8B is a block diagram of an example of transceiver and charging component combination.

FIG. 8C is an illustration of an example of simple user interface for facilitating user controlled charging.

FIG. 9 is a diagram of an example of resource communication protocol.

FIG. 10 is a flow chart of an example of smart charging via periodically updated schedules.

FIG. 11 is a flow chart of an example of smart charging via schedules with overrides.

FIG. 12 is a flow chart of an example of local load management in the presence of uncontrolled loads.

FIG. 13 is a flow chart of an example of direct load control over prices-to-devices enabled electric resources.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

Overview

Described herein is a power aggregation system for distributed electric resources, and associated methods. In one implementation, a system communicates over the Internet and/or some other public or private networks with numerous individual electric resources connected to a power grid (hereinafter, “grid”). By communicating, the system can dynamically aggregate these electric resources to provide power services to grid operators (e.g. utilities, Independent System Operators (ISO), etc).

“Power services” as used herein, refers to energy delivery as well as other ancillary services including demand response, regulation, spinning reserves, non-spinning reserves, energy imbalance, reactive power, and similar products.

“Aggregation” as used herein refers to the ability to control power flows into and out of a set of spatially distributed electric resources with the purpose of providing a power service of larger magnitude.

“Charge Control Management” as used herein refers to enabling or performing the starting, stopping, or level-setting of a flow of power between a power grid and an electric resource.

“Power grid operator” as used herein, refers to the entity that is responsible for maintaining the operation and stability of the power grid within or across an electric control area. The power grid operator may constitute some combination of manual/human action/intervention and automated processes controlling generation signals in response to system sensors. A “control area operator” is one example of a power grid operator.

“Control area” as used herein, refers to a contained portion of the electrical grid with defined input and output ports. The net flow of power into this area must equal (within some error tolerance) the sum of the power consumption within the area and power outflow from the area, less the power production within in the area.

“Power grid” as used herein means a power distribution system/network that connects producers of power with consumers of power. The network may include generators, transformers, interconnects, switching stations, and safety equipment as part of either/both the transmission system (i.e., bulk power) or the distribution system (i.e. retail power). The power aggregation system is vertically scalable for use within a neighborhood, a city, a sector, a control area, or (for example) one of the eight large-scale Interconnects in the North American Electric Reliability Council (NERC). Moreover, the system is horizontally scalable for use in providing power services to multiple grid areas simultaneously.

“Grid conditions” as used herein, refers to the need for more or less power flowing in or out of a section of the electric power grid, in response to one of a number of conditions, for example supply changes, demand changes, contingencies and failures, ramping events, etc. These grid conditions typically manifest themselves as power quality events such as under- or over-voltage events or under- or over-frequency events.

“Power quality events” as used herein typically refers to manifestations of power grid instability including voltage deviations and frequency deviations; additionally, power quality events as used herein also includes other disturbances in the quality of the power delivered by the power grid such as sub-cycle voltage spikes and harmonics.

“Electric resource” as used herein typically refers to electrical entities that can be commanded to do some or all of these three things: take power (act as load), provide power (act as power generation or source), and store energy. Examples may include battery/charger/inverter systems for electric or hybrid-electric vehicles, repositories of used-but-serviceable electric vehicle batteries, fixed energy storage, fuel cell generators, emergency generators, controllable loads, etc.

“Electric vehicle” is used broadly herein to refer to pure electric and hybrid electric vehicles, such as plug-in hybrid electric vehicles (PHEVs), especially vehicles that have significant storage battery capacity and that connect to the power grid for recharging the battery. More specifically, electric vehicle means a vehicle that gets some or all of its energy for motion and other purposes from the power grid. Moreover, an electric vehicle has an energy storage system, which may consist of batteries, capacitors, etc., or some combination thereof. An electric vehicle may or may not have the capability to provide power back to the electric grid.

Electric vehicle “energy storage systems” (batteries, super capacitors, and/or other energy storage devices) are used herein as a representative example of electric resources intermittently or permanently connected to the grid that can have dynamic input and output of power. Such batteries can function as a power source or a power load. A collection of aggregated electric vehicle batteries can become a statistically stable resource across numerous batteries, despite recognizable tidal connection trends (e.g., an increase in the total number of vehicles connected to the grid at night; a downswing in the collective number of connected batteries as the morning commute begins, etc.) Across vast numbers of electric vehicle batteries, connection trends are predictable and such batteries become a stable and reliable resource to call upon, should the grid or a part of the grid (such as a person's home in a blackout) experience a need for increased or decreased power. Data collection and storage also enable the power aggregation system to predict connection behavior on a per-user basis.

An Example of the Presently Disclosed System

FIG. 1 shows a power aggregation system 100. A flow control center 102 is communicatively coupled with a network, such as a public/private mix that includes the Internet 104, and includes one or more servers 106 providing a centralized power aggregation service. “Internet” 104 will be used herein as representative of many different types of communicative networks and network mixtures (e.g., one or more wide area networks—public or private—and/or one or more local area networks). Via a network, such as the Internet 104, the flow control center 102 maintains communication 108 with operators of power grid(s), and communication 110 with remote resources, i.e., communication with peripheral electric resources 112 (“end” or “terminal” nodes/devices of a power network) that are connected to the power grid 114. In one implementation, power line communicators (PLCs), such as those that include or consist of Ethernet-over-power line bridges 120 are implemented at connection locations so that the “last mile” (in this case, last feet—e.g., in a residence 124) of Internet communication with remote resources is implemented over the same wire that connects each electric resource 112 to the power grid 114. Thus, each physical location of each electric resource 112 may be associated with a corresponding Ethernet-over-power line bridge 120 (hereinafter, “bridge”) at or near the same location as the electric resource 112. Each bridge 120 is typically connected to an Internet access point of a location owner, as will be described in greater detail below. The communication medium from flow control center 102 to the connection location, such as residence 124, can take many forms, such as cable modem, DSL, satellite, fiber, WiMax, etc. In a variation, electric resources 112 may connect with the Internet by a different medium than the same power wire that connects them to the power grid 114. For example, a given electric resource 112 may have its own wireless capability to connect directly with the Internet 104 or an Internet access point and thereby with the flow control center 102.

Electric resources 112 of the power aggregation system 100 may include the batteries of electric vehicles connected to the power grid 114 at residences 124, parking lots 126 etc.; batteries in a repository 128, fuel cell generators, private dams, conventional power plants, and other resources that produce electricity and/or store electricity physically or electrically.

In one implementation, each participating electric resource 112 or group of local resources has a corresponding remote intelligent power flow (IPF) module 134 (hereinafter, “remote IPF module” 134). The centralized flow control center 102 administers the power aggregation system 100 by communicating with the remote IPF modules 134 distributed peripherally among the electric resources 112. The remote IPF modules 134 perform several different functions, including, but not limited to, providing the flow control center 102 with the statuses of remote resources; controlling the amount, direction, and timing of power being transferred into or out of a remote electric resource 112; providing metering of power being transferred into or out of a remote electric resource 112; providing safety measures during power transfer and changes of conditions in the power grid 114; logging activities; and providing self-contained control of power transfer and safety measures when communication with the flow control center 102 is interrupted. The remote IPF modules 134 will be described in greater detail below.

In another implementation, instead of having an IPF module 134, each electric resource 112 may have a corresponding transceiver (not shown) to communicate with a local charging component (not shown). The transceiver and charging component, in combination, may communicate with flow control center 102 to perform some or all of the above mentioned functions of IPF module 134. A transceiver and charging component are shown in FIG. 2B and are described in greater detail herein.

FIG. 2A shows another view of electrical and communicative connections to an electric resource 112. In this example, an electric vehicle 200 includes a battery bank 202 and a remote IPF module 134. The electric vehicle 200 may connect to a conventional wall receptacle (wall outlet) 204 of a residence 124, the wall receptacle 204 representing the peripheral edge of the power grid 114 connected via a residential powerline 206.

In one implementation, the power cord 208 between the electric vehicle 200 and the wall outlet 204 can be composed of only conventional wire and insulation for conducting alternating current (AC) power to and from the electric vehicle 200. In FIG. 2A, a location-specific connection locality module 210 performs the function of network access point—in this case, the Internet access point. A bridge 120 intervenes between the receptacle 204 and the network access point so that the power cord 208 can also carry network communications between the electric vehicle 200 and the receptacle 204. With such a bridge 120 and connection locality module 210 in place in a connection location, no other special wiring or physical medium is needed to communicate with the remote IPF module 134 of the electric vehicle 200 other than a conventional power cord 208 for providing residential line current at any conventional voltage. Upstream of the connection locality module 210, power and communication with the electric vehicle 200 are resolved into the powerline 206 and an Internet cable 104.

Alternatively, the power cord 208 may include safety features not found in conventional power and extension cords. For example, an electrical plug 212 of the power cord 208 may include electrical and/or mechanical safeguard components to prevent the remote IPF module 134 from electrifying or exposing the male conductors of the power cord 208 when the conductors are exposed to a human user.

In some embodiments, a radio frequency (RF) bridge (not shown) may assist the remote IPF module 134 in communicating with a foreign system, such as a utility smart meter (not shown) and/or a connection locality module 210. For example, the remote IPF module 134 may be equipped to communicate over power cord 208 or to engage in some form of RF communication, such as Zigbee or Bluetooth, and the foreign system may be able to engage in a different form of RF communication. In such an implementation, the RF bridge may be equipped to communicate with both the foreign system and remote IPF module 134 and to translate communications from one to a form the other may understand, and to relay those messages. In various embodiments, the RF bridge may be integrated into the remote IPF module 134 or foreign system, or may be external to both. The communicative associations between the RF bridge and remote IPF module 134 and between the RF bridge and foreign system may be via wired or wireless communication.

FIG. 2B shows a further view of electrical and communicative connections to an electric resource 112. In this example, the electric vehicle 200 may include a transceiver 212 rather than a remote IPF module 134. The transceiver 212 may be communicatively coupled to a charging component 214 through a connection 216, and the charging component itself may be coupled to a conventional wall receptacle (wall outlet) 204 of a residence 124 and to electric vehicle 200 through a power cord 208. The other components shown in FIG. 2B may have the couplings and functions discussed with regard to FIG. 2A.

In various embodiments, transceiver 212 and charging component 214 may, in combination, perform the same functions as the remote IPF module 134. Transceiver 212 may interface with computer systems of electric vehicle 200 and communicate with charging component 214, providing charging component 214 with information about electric vehicle 200, such as its vehicle identifier, a location identifier, and a state of charge. In response, transceiver 212 may receive requests and commands which transceiver 212 may relay to vehicle 200′s computer systems.

Charging component 214, being coupled to both electric vehicle 200 and wall outlet 204, may effectuate charge control of the electric vehicle 200. If the electric vehicle 200 is not capable of charge control management, charging component 214 may directly manage the charging of electric vehicle 200 by stopping and starting a flow of power between the electric vehicle 200 and a power grid 114 in response to commands received from a flow control server 106. If, on the other hand, the electric vehicle 200 is capable of charge control management, charging component 214 may effectuate charge control by sending commands to the electric vehicle 200 through the transceiver 212.

In some embodiments, the transceiver 212 may be physically coupled to the electric vehicle 200 through a data port, such as an OBD-II connector. In other embodiments, other couplings may be used. The connection 216 between transceiver 212 and charging component 214 may be a wireless signal, such as a radio frequency (RF), such as a Zigbee or Bluetooth signal. And charging component 214 may include a receiver socket to couple with power cord 208 and a plug to couple with wall outlet 204. In one embodiment, charging component 214 may be coupled to connection locality module 210 in either a wired or wireless fashion. For example, charging component 214 might have a data interface for communicating wirelessly with both the transceiver 212 and locality module 210. In such an embodiment, the bridge 120 may not be required.

Further details about the transceiver 212 and charging component 214 are illustrated by FIG. 8B and described in greater detail herein.

FIG. 3 shows another implementation of the connection locality module 210 of FIG. 2, in greater detail. In FIG. 3, an electric resource 112 has an associated remote IPF module 134, including a bridge 120. The power cord 208 connects the electric resource 112 to the power grid 114 and also to the connection locality module 210 in order to communicate with the flow control server 106.

The connection locality module 210 includes another instance of a bridge 120, connected to a network access point 302, which may include such components as a router, switch, and/or modem, to establish a hardwired or wireless connection with, in this case, the Internet 104. In one implementation, the power cord 208 between the two bridges 120 and 120′ is replaced by a wireless Internet link, such as a wireless transceiver in the remote IPF module 134 and a wireless router in the connection locality module 210.

In other embodiments, a transceiver 212 and charging component 214 may be used instead of a remote IPF module 134. In such an embodiment, the charging component 214 may include or be coupled to a bridge 120, and the connection locality module 210 may also include a bridge 120′, as shown. In yet other embodiments, not shown, charging component 214 and connection locality module 210 may communicate in a wired or wireless fashion, as mentioned previously, without bridges 120 and 120′. The wired or wireless communication may utilize any sort of connection technology known in the art, such as Ethernet or RF communication, such as Zigbee, or Bluetooth.

System Layouts

FIG. 4 shows a layout 400 of the power aggregation system 100. The flow control center 102 can be connected to many different entities, e.g., via the Internet 104, for communicating and receiving information. The layout 400 includes electric resources 112, such as plug-in electric vehicles 200, physically connected to the grid within a single control area 402. The electric resources 112 become an energy resource for grid operators 404 to utilize.

The layout 400 also includes end users 406 classified into electric resource owners 408 and electrical connection location owners 410, who may or may not be one and the same. In fact, the stakeholders in a power aggregation system 100 include the system operator at the flow control center 102, the grid operator 404, the resource owner 408, and the owner of the location 410 at which the electric resource 112 is connected to the power grid 114.

Electrical connection location owners 410 can include:

Rental car lots—rental car companies often have a large portion of their fleet parked in the lot. They can purchase fleets of electric vehicles 200 and, participating in a power aggregation system 100, generate revenue from idle fleet vehicles.

Public parking lots—parking lot owners can participate in the power aggregation system 100 to generate revenue from parked electric vehicles 200. Vehicle owners can be offered free parking, or additional incentives, in exchange for providing power services.

Workplace parking—employers can participate in a power aggregation system 100 to generate revenue from parked employee electric vehicles 200. Employees can be offered incentives in exchange for providing power services.

Residences—a home garage can merely be equipped with a connection locality module 210 to enable the homeowner to participate in the power aggregation system 100 and generate revenue from a parked car. Also, the vehicle battery 202 and associated power electronics within the vehicle can provide local power backup power during times of peak load or power outages.

Residential neighborhoods—neighborhoods can participate in a power aggregation system 100 and be equipped with power-delivery devices (deployed, for example, by homeowner cooperative groups) that generate revenue from parked electric vehicles 200.

The grid operations 116 of FIG. 4 collectively include interactions with energy markets 412, the interactions of grid operators 404, and the interactions of automated grid controllers 118 that perform automatic physical control of the power grid 114.

The flow control center 102 may also be coupled with information sources 414 for input of weather reports, events, price feeds, etc. Other data sources 414 include the system stakeholders, public databases, and historical system data, which may be used to optimize system performance and to satisfy constraints on the power aggregation system 100.

Thus, a power aggregation system 100 may consist of components that:

communicate with the electric resources 112 to gather data and actuate charging/discharging of the electric resources 112;

gather real-time energy prices;

gather real-time resource statistics;

predict behavior of electric resources 112 (connectedness, location, state (such as battery State-Of-Charge) at a given time of interest, such as a time of connect/disconnect);

predict behavior of the power grid 114/load;

encrypt communications for privacy and data security;

actuate charging of electric vehicles 200 to optimize some figure(s) of merit;

offer guidelines or guarantees about load availability for various points in the future, etc.

These components can be running on a single computing resource (computer, etc.), or on a distributed set of resources (either physically co-located or not).

Power aggregation systems 100 in such a layout 400 can provide many benefits: for example, lower-cost ancillary services (i.e., power services), fine-grained (both temporal and spatial) control over resource scheduling, guaranteed reliability and service levels, increased service levels via intelligent resource scheduling, and/or firming of intermittent generation sources such as wind and solar power generation.

The power aggregation system 100 enables a grid operator 404 to control the aggregated electric resources 112 connected to the power grid 114. An electric resource 112 can act as a power source, load, or storage, and the resource 112 may exhibit combinations of these properties. Control of a set of electric resources 112 is the ability to actuate power consumption, generation, or energy storage from an aggregate of these electric resources 112.

FIG. 5 shows the role of multiple control areas 402 in the power aggregation system 100. Each electric resource 112 can be connected to the power aggregation system 100 within a specific electrical control area. A single instance of the flow control center 102 can administer electric resources 112 from multiple distinct control areas 501 (e.g., control areas 502, 504, and 506). In one implementation, this functionality is achieved by logically partitioning resources within the power aggregation system 100. For example, when the control areas 402 include an arbitrary number of control areas, control area “A” 502, control area “B” 504, . . . , control area “n” 506, then grid operations 116 can include corresponding control area operators 508, 510, . . . , and 512. Further division into a control hierarchy that includes control division groupings above and below the illustrated control areas 402 allows the power aggregation system 100 to scale to power grids 114 of different magnitudes and/or to varying numbers of electric resources 112 connected with a power grid 114.

FIG. 6 shows a layout 600 of a power aggregation system 100 that uses multiple centralized flow control centers 102 and 102′ and a directory server 602 for determining a flow control center. Each flow control center 102 and 102′ has its own respective end users 406 and 406′. Control areas 402 to be administered by each specific instance of a flow control center 102 can be assigned dynamically. For example, a first flow control center 102 may administer control area A 502 and control area B 504, while a second flow control center 102′ administers control area n 506. Likewise, corresponding control area operators (508, 510, and 512) are served by the same flow control center 102 that serves their respective different control areas.

In various embodiments, an electric resource may determine which flow control center 102/102′ administers its control area 502/504/506 by communicating with a directory server 602. The address of the directory server 602 may be known to electric resource 112 or its associated IPF module 134 or charging component 214. Upon plugging in, the electric resource 112 may communicate with the directory server 602, providing the directory server 112 with a resource identifier and/or a location identifier. Based on this information, the directory server 602 may respond, identifying which flow control center 102/102′ to use.

In another embodiment, directory server 602 may be integrated with a flow control server 106 of a flow control center 102/102′. In such an embodiment, the electric resource 112 may contact the server 106. In response, the server 106 may either interact with the electric resource 112 itself or forward the connection to another flow control center 102/102′ responsible for the location identifier provided by the electric resource 112.

In some embodiments, whether integrated with a flow control server 106 or not, directory server 602 may include a publicly accessible database for mapping locations to flow control centers 102/102′.

Flow Control Server

FIG. 7 shows a server 106 of the flow control center 102. The illustrated implementation in FIG. 7 is only one example configuration, for descriptive purposes. Many other arrangements of the illustrated components or even different components constituting a server 106 of the flow control center 102 are possible within the scope of the subject matter. Such a server 106 and flow control center 102 can be executed in hardware, software, or combinations of hardware, software, firmware, etc.

The flow control server 106 includes a connection manager 702 to communicate with electric resources 112, a prediction engine 704 that may include a learning engine 706 and a statistics engine 708, a constraint optimizer 710, and a grid interaction manager 712 to receive grid control signals 714. Grid control signals 714 are sometimes referred to as generation control signals, such as automated generation control (AGC) signals. The flow control server 106 may further include a database/information warehouse 716, a web server 718 to present a user interface to electric resource owners 408, grid operators 404, and electrical connection location owners 410; a contract manager 720 to negotiate contract terms with energy markets 412, and an information acquisition engine 414 to track weather, relevant news events, etc., and download information from public and private databases 722 for predicting behavior of large groups of the electric resources 112, monitoring energy prices, negotiating contracts, etc.

Remote IPF Module

FIG. 8A shows the remote IPF module 134 of FIGS. 1 and 2 in greater detail. The illustrated remote IPF module 134 is only one example configuration, for descriptive purposes. Many other arrangements of the illustrated components or even different components constituting a remote IPF module 134 are possible within the scope of the subject matter. Such a remote IPF module 134 has some hardware components and some components that can be executed in hardware, software, or combinations of hardware, software, firmware, etc. In other embodiments, executable instructions configured to perform some or all of the operations of remote IPF module 134 may be added to hardware of an electric resource 112 such as an electric vehicle that, when combined with the executable instructions, provides equivalent functionality to remote IPF module 134. References to remote IPF module 134 as used herein include such executable instructions.

The illustrated example of a remote IPF module 134 is represented by an implementation suited for an electric vehicle 200. Thus, some vehicle systems 800 are included as part of the remote IPF module 134 for the sake of description. However, in other implementations, the remote IPF module 134 may exclude some or all of the vehicles systems 800 from being counted as components of the remote IPF module 134.

The depicted vehicle systems 800 include a vehicle computer and data interface 802, an energy storage system, such as a battery bank 202, and an inverter/charger 804. Besides vehicle systems 800, the remote IPF module 134 also includes a communicative power flow controller 806. The communicative power flow controller 806 in turn includes some components that interface with AC power from the grid 114, such as a powerline communicator, for example an Ethernet-over-powerline bridge 120, and a current or current/voltage (power) sensor 808, such as a current sensing transformer.

The communicative power flow controller 806 also includes Ethernet and information processing components, such as a processor 810 or microcontroller and an associated Ethernet media access control (MAC) address 812; volatile random access memory 814, nonvolatile memory 816 or data storage, an interface such as an RS-232 interface 818 or a CANbus interface 820; an Ethernet physical layer interface 822, which enables wiring and signaling according to Ethernet standards for the physical layer through means of network access at the MAC/Data Link Layer and a common addressing format. The Ethernet physical layer interface 822 provides electrical, mechanical, and procedural interface to the transmission medium—i.e., in one implementation, using the Ethernet-over-powerline bridge 120. In a variation, wireless or other communication channels with the Internet 104 are used in place of the Ethernet-over-powerline bridge 120.

The communicative power flow controller 806 also includes a bidirectional power flow meter 824 that tracks power transfer to and from each electric resource 112, in this case the battery bank 202 of an electric vehicle 200.

The communicative power flow controller 806 operates either within, or connected to an electric vehicle 200 or other electric resource 112 to enable the aggregation of electric resources 112 introduced above (e.g., via a wired or wireless communication interface). These above-listed components may vary among different implementations of the communicative power flow controller 806, but implementations typically include:

• • an intra-vehicle communications mechanism that enables communication with other vehicle components;
  • a mechanism to communicate with the flow control center 102;
  • a processing element;
  • a data storage element;
  • a power meter; and
  • optionally, a user interface.

Implementations of the communicative power flow controller 806 can enable functionality including:

• • executing pre-programmed or learned behaviors when the electric resource 112 is offline (not connected to Internet 104, or service is unavailable);
  • storing locally-cached behavior profiles for “roaming” connectivity (what to do when charging on a foreign system, i.e., when charging in the same utility territory on a foreign meter or in a separate utility territory, or in disconnected operation, i.e., when there is no network connectivity);
  • allowing the user to override current system behavior; and
  • metering power-flow information and caching meter data during offline operation for later transaction.

Thus, the communicative power flow controller 806 includes a central processor 810, interfaces 818 and 820 for communication within the electric vehicle 200, a powerline communicator, such as an Ethernet-over-powerline bridge 120 for communication external to the electric vehicle 200, and a power flow meter 824 for measuring energy flow to and from the electric vehicle 200 via a connected AC powerline 208.

Power Flow Meter

Power is the rate of energy consumption per interval of time. Power indicates the quantity of energy transferred during a certain period of time, thus the units of power are quantities of energy per unit of time. The power flow meter 824 measures power for a given electric resource 112 across a bidirectional flow—e.g., power from grid 114 to electric vehicle 200 or from electric vehicle 200 to the grid 114. In one implementation, the remote IPF module 134 can locally cache readings from the power flow meter 824 to ensure accurate transactions with the central flow control server 106, even if the connection to the server is down temporarily, or if the server itself is unavailable.

Transceiver and Charging Component

FIG. 8B shows the transceiver 212 and charging component 214 of FIG. 2B in greater detail. The illustrated transceiver 212 and charging component 214 is only one example configuration, for descriptive purposes. Many other arrangements of the illustrated components or even different components constituting the transceiver 212 and charging component 214 are possible within the scope of the subject matter. Such a transceiver 212 and charging component 214 have some hardware components and some components that can be executed in hardware, software, or combinations of hardware, software, firmware, etc.

The illustrated example of the transceiver 212 and charging component 214 is represented by an implementation suited for an electric vehicle 200. Thus, some vehicle systems 800 are illustrated to provide context to the transceiver 212 and charging component 214 components.

The depicted vehicle systems 800 include a vehicle computer and data interface 802, an energy storage system, such as a battery bank 202, and an inverter/charger 804. In some embodiments, vehicle systems 800 may include a data port, such as an OBD-II port, that is capable of physically coupling with the transceiver 212. The transceiver 212 may then communicate with the vehicle computer and data interface 802 through the data port, receiving information from electric resource 112 comprised by vehicle systems 800 and, in some embodiments, providing commands to the vehicle computer and data interface 802. In one implementation, the vehicle computer and data interface 802 may be capable of charge control management. In such an embodiment, the vehicle computer and data interface 802 may perform some or all of the charging component 214 operations discussed below. In other embodiments, executable instructions configured to perform some or all of the operations of the vehicle computer and data interface 802 may be added to hardware of an electric resource 112 such as an electric vehicle that, when combined with the executable instructions, provides equivalent functionality to the vehicle computer and data interface 802. References to the vehicle computer and data interface 802 as used herein include such executable instructions.

In various embodiments, the transceiver 212 may have a physical form that is capable of coupling to a data port of vehicle systems 800. Such a transceiver 212 may also include a plurality of interfaces, such as an RS-232 interface 818 and/or a CANBus interface 820. In various embodiments, the RS-232 interface 818 or CANBus interface 820 may enable the transceiver 212 to communicate with the vehicle computer and data interface 802 through the data port. Also, the transceiver may be or comprise an additional interface (not shown) capable of engaging in wireless communication with a data interface 820 of the charging component 214. The wireless communication may be of any form known in the art, such as radio frequency (RF) communication (e.g., Zigbee and/or Bluetooth communication). In other embodiments, the transceiver may comprise a separate conductor or may be configured to utilize a powerline 208 to communicate with charging component 214. In yet other embodiments, not shown, transceiver 212 may simply be a radio frequency identification (RFID) tag capable of storing minimal information about the electric resource 112, such as a resource identifier, and of being read by a corresponding RFID reader of charging component 214. In such other embodiments, the RFID tag might not couple with a data port or communicate with the vehicle computer and data interface 802.

As shown, the charging component 214 may be an intelligent plug device that is physically connected to a charging medium, such as a powerline 208 (the charging medium coupling the charging component 214 to the electric resource 112) and an outlet of a power grid (such as the wall outlet 204 shown in FIG. 2B). In other embodiments charging component 214 may be a charging station or some other external control. In some embodiments, the charging component 214 may be portable.

In various embodiments, the charging component 214 may include components that interface with AC power from the grid 114, such as a powerline communicator, for example an Ethernet-over-powerline bridge 120, and a current or current/voltage (power) sensor 808, such as a current sensing transformer.

In other embodiments, the charging component 214 may include a further Ethernet plug or wireless interface in place of bridge 120. In such an embodiment, data-over-powerline communication is not necessary, eliminating the need for a bridge 120. The Ethernet plug or wireless interface may communicate with a local access point, and through that access point to flow control server 106.

The charging component 214 may also include Ethernet and information processing components, such as a processor 810 or microcontroller and an associated Ethernet media access control (MAC) address 812; volatile random access memory 814, nonvolatile memory 816 or data storage, a data interface 826 for communicating with the transceiver 212, and an Ethernet physical layer interface 822, which enables wiring and signaling according to Ethernet standards for the physical layer through means of network access at the MAC/Data Link Layer and a common addressing format. The Ethernet physical layer interface 822 provides electrical, mechanical, and procedural interface to the transmission medium—i.e., in one implementation, using the Ethernet-over-powerline bridge 120. In a variation, wireless or other communication channels with the Internet 104 are used in place of the Ethernet-over-powerline bridge 120.

The charging component 214 may also include a bidirectional power flow meter 824 that tracks power transfer to and from each electric resource 112, in this case the battery bank 202 of an electric vehicle 200.

Further, in some embodiments, the charging component 214 may comprise an RFID reader to read the electric resource information from transceiver 212 when transceiver 212 is an RFID tag.

Also, in various embodiments, the charging component 214 may include a credit card reader to enable a user to identify the electric resource 112 by providing credit card information. In such an embodiment, a transceiver 212 may not be necessary.

Additionally, in one embodiment, the charging component 214 may include a user interface, such as one of the user interfaces described in greater detail below.

Implementations of the charging component 214 can enable functionality including:

• • executing pre-programmed or learned behaviors when the electric resource 112 is offline (not connected to Internet 104, or service is unavailable);
  • storing locally-cached behavior profiles for “roaming” connectivity (what to do when charging on a foreign system or in disconnected operation, i.e., when there is no network connectivity);
  • allowing the user to override current system behavior; and
  • metering power-flow information and caching meter data during offline operation for later transaction.

User Interfaces (UI)

Charging Station UI. An electrical charging station, whether free or for pay, can be installed with a user interface that presents useful information to the user. Specifically, by collecting information about the grid 114, the electric resource state, and the preferences of the user, the station can present information such as the current electricity price, the estimated recharge cost, the estimated time until recharge, the estimated payment for uploading power to the grid 114 (either total or per hour), etc. The information acquisition engine 414 communicates with the electric resource 112 and with public and/or private data networks 722 to acquire the data used in calculating this information.

The types of information gathered from the electric resource 112 could include an electric resource identifier (resource ID) and state information like the state of charge of the electric resource 112. The resource ID could be used to obtain knowledge of the electric resource type and capabilities, preferences, etc. through lookup with the flow control server 106.

In various embodiments, the charging station system including the UI might also gather grid-based information, such as current and future energy costs at the charging station.

User Charge Control UI Mechanisms. In various embodiments, by default, electric resources 112 may receive charge control management via power aggregation system 100. In some embodiments, an override control may be provided to override charge control management and charge as soon as possible. The override control may be provided, in various embodiments, as a user interface mechanism of the remote IPF module 134, the charging component 214, of the electric resource (for example, if electric resource is a vehicle 200, the user interface control may be integrated with dash controls of the vehicle 200) or even via a web page offered by flow control server 106. The control could be presented, for example, as a button, a touch screen option, a web page, or some other UI mechanism. In one embodiment, the UI may be the UI illustrated by FIG. 8C and discussed in greater detail below. In some embodiments, the override would be a one-time override, only applying to a single plug-in session. Upon disconnecting and reconnecting, the user may again need to interact with the UI mechanism to override the charge control management.

In some embodiments, the user may pay more to charge with the override on than under charge control management, thus providing an incentive for the user to accept charge control management. Such a cost differential may be displayed or rendered to the user in conjunction with or on the UI mechanism. This differential could take into account time-varying pricing, such as Time of Use (TOU), Critical Peak Pricing (CPP), and Real-Time Pricing (RTP) schemes, as discussed above, as well as any other incentives, discounts, or payments that might be forgone by not accepting charge control management.

UI Mechanism for Management Preferences. In various embodiments, a user interface mechanism of the remote IPF module 134, the charging component 214, of the electric resource (for example, if electric resource is a vehicle 200, the user interface control may be integrated with dash controls of the vehicle 200) or even via a web page offered by flow control server 106 may enable a user to enter and/or edit management preferences to affect charge control management of the user's electric resource 112. In some embodiments, the UI mechanism may allow the user to enter/edit general preferences, such as whether charge control management is enabled, whether vehicle-to-grid power flow is enabled or whether the electric resource 112 should only be charged with clean/green power. Also, in various embodiments, the UI mechanism may enable a user to prioritize relative desires for minimizing costs, maximizing payments (i.e., fewer charge periods for higher amounts), achieving a full state-of-charge for the electric resource 112, charging as rapidly as possible, and/or charging in as environmentally-friendly a way as possible. Additionally, the UI mechanism may enable a user to provide a default schedule for when the electric resource will be used (for example, if resource 112 is a vehicle 200, the schedule would be for when the vehicle 200 should be ready to drive). Further, the UI mechanism may enable the user to add or select special rules, such as a rule not to charge if a price threshold is exceeded or a rule to only use charge control management if it will earn the user at least a specified threshold of output. Charge control management may then be effectuated based on any part or all of these user entered preferences.

Simple User Interface. FIG. 8C illustrates a simple user interface (UI) which enables a user to control charging based on selecting among a limited number of high level preferences. For example, UI 2300 includes the categories “green”, “fast”, and “cheap” (with what is considered “green”, “fast”, and “cheap” varying from embodiment to embodiment). The categories shown in UI 2300 are selected only for the sake of illustration and may instead includes these and/or any other categories applicable to electric resource 112 charging known in the art. As shown, the UI 2300 may be very basic, using well known form controls such as radio buttons. In other embodiments, other graphic controls known in the art may be used. The general categories may be mapped to specific charging behaviors, such as those discussed above, by a flow control server 106.

Electric Resource Communication Protocol

FIG. 9 illustrates a resource communication protocol. As shown, a remote IPF module 134 or charging component 214 may be in communication with a flow control server 106 over the Internet 104 or another networking fabric or combination of networking fabrics. In various embodiments, a protocol specifying an order of messages and/or a format for messages may be used to govern the communications between the remote IPF module 134 or charging component 214 and flow control server 106.

In some embodiments, the protocol may include two channels, one for messages initiated by the remote IPF module 134 or charging component 214 and for replies to those messages from the flow control server 106, and another channel for messages initiated by the flow control server 106 and for replies to those messages from the remote IPF module 134 or charging component 214. The channels may be asynchronous with respect to each other (that is, initiation of messages on one channel may be entirely independent of initiation of messages on the other channel). However, each channel may itself be synchronous (that is, once a message is sent on a channel, another message may not be sent until a reply to the first message is received).

As shown, the remote IPF module 134 or charging component 214 may initiate communication 902 with the flow control server 106. In some embodiments, communication 902 may be initiated when, for example, an electric resource 112 first plugs in/connects to the power grid 114. In other embodiments, communication 902 may be initiated at another time or times. The initial message 902 governed by the protocol may require, for example, one or more of an electric resource identifier, such as a MAC address, a protocol version used, and/or a resource identifier type.

Upon receipt of the initial message by the flow control server 106, a connection may be established between the remote IPF module 134 or charging component 214 and flow control server 106. Upon establishing a connection, the remote IPF module 134 or charging component 214 may register with flow control server 106 through a subsequent communication 903. Communication 903 may include a location identifier scheme, a latitude, a longitude, a max power value that the remote IPF module 134 or charging component 214 can draw, a max power value that the remote IPF module 134 or charging component 214 can provide, a current power value, and/or a current state of charge.

After the initial message 902, the protocol may require or allow messages 904 from the flow control server 106 to the remote IPF module 134 or charging component 214 or messages 906 from remote IPF module 134 or charging component 214 to the flow control server 106. The messages 904 may include, for example, one or more of commands, messages, and/or updates. Such messages 904 may be provided at any time after the initial message 902. In one embodiment, messages 904 may include a command setting, a power level and/or a ping to determine whether the remote IPF module 134 or charging component 214 is still connected.

The messages 906 may include, for example, status updates to the information provided in the registration message 903. Such messages 906 may be provided at any time after the initial message 902. In one embodiment, the messages 906 may be provided on a pre-determined time interval basis. In various embodiments, messages 906 may even be sent when the remote IPF module 134 or charging component 214 is connected, but not registered. Such messages 906 may include data that is stored by flow control server 106 for later processing. Also, in some embodiments, messages 904 may be provided in response to a message 902 or 906.

Smart Charging Via Periodically Updated Schedules

In some environments, it is desirable to implement a centrally managed smart charging system or program without requiring continuous, real-time communication between the endpoint device and the central server. In these situations, a periodically updated schedule is beneficial. Because such a schedule can be frequently updated by the central server, the disclosed system presents significant advantages over a simple timer system which delays charging to a fixed off-peak time. Such a schedule would be transmitted from the server to the vehicles or endpoints and would allow individual vehicles or endpoints to operate in an intelligent but disconnected manner.

In an embodiment, every resource in the power flow management system maintains a persistent, current schedule of default charging behavior. This schedule is periodically transmitted to the resource over a communications network.

The schedule, in one embodiment, defines average power-level constraints for resources during each fixed length interval over the period of the schedule. For example, a one-day schedule could be subdivided into 96 fifteen-minute time slots. The average power-level is defined as the percent of time during the slot that the resource can charge at its maximum charge power. For example, 33% average power-level signifies that the resource should charge at maximum power for five minutes of a fifteen-minute time slot. The energy consumption can also take place at 33% of maximum power for the entirety of the fifteen-minute slot.

Upon receiving an updated schedule from the server, the client immediately replaces its old schedule with the updated schedule. If the client's current operating mode is a pre-scheduled operation, the client can immediately enact the new schedule.

At a fixed period, the client can send an update to the central energy management server. The fixed period may be specified as part of the schedule. The update can specify information about its current state including information about current power-level, battery state-of-charge (SOC), and energy transferred during each of the time slots that have not been previously reported. When an energy session terminates without the client being able to communicate with the server, the information about energy consumption and battery SOC by time interval is stored until the information can be communicated to the energy management system.

Because the server would have detailed knowledge of the charging schedule being followed by each vehicle, the server could include scheduled vehicle behavior in electrical load planning, even though the vehicles were not in constant communication with the server.

Since such a schedule can be updated at regular intervals by the central server, this system presents significant advantages over a simple timer system that always delays charging to a fixed off-peak time. For example, if a large population of vehicles were each configured to charge at a particular off peak time, the sudden increase in load from multiple vehicles simultaneously beginning charging would constitute a new peak. Through the use of centrally managed individual schedules, each vehicle can be configured to begin charging at a different time, thereby eliminating the new peak.

FIG. 10 shows an embodiment of smart charging via periodically updated schedules for a power management system. A charging schedule is periodically transmitted 1010 from a server.

The charging schedule is received 1020 by a device, such as an electric vehicle. The charging schedule replaces 1030 the device's prior schedule.

In a system for managing smart charging via periodically updated schedules, the electrical loads may be managed by a management system, such as the power aggregation system 100 as shown in FIG. 1 and described above. The server may be the flow control server 106 of the flow control center 102.

Smart Charging Via Schedule With Override

In some environments, it is be desirable to implement a centrally managed smart charging system or program where bandwidth utilization is minimized, but where real-time control of individual endpoints is still possible. In these situations, a periodically updated schedule with real-time override messages may be beneficial.

In this system, every resource in the power flow management system maintains a persistent, current schedule of default charging behavior. This schedule is periodically transmitted to the resource over a communications network. The schedule may represent the behavior that is, on average, beneficial in the local environment. For example, vehicles could be configured to charge slowly at peak times (perhaps 5:00-8:00 PM) and more rapidly and off peak times (perhaps 8:00 PM -2:00 AM).

While a schedule allows for charging behavior to be controlled without requiring continuous communications, a purely schedule-based system cannot address unpredictable grid or utility operational demands. While power capacity is generally in plentiful supply in the evening, unexpected events could cause a power shortage. Similarly, while power is usually in relatively short supply in the early evening, unexpected events could produce a surplus.

By issuing real-time override messages, the server has the ability to accommodate these unexpected “out of schedule” events. At times of surplus electricity, vehicles can be directed to increase energy consumption, at variance from their pre-programmed schedules. At times of energy shortage, vehicles can be directed to decrease energy consumption, at variance from their schedules. When energy availability is largely as predicted, no communication is required between the server and the endpoints/vehicles, even though the vehicles are following a generally beneficial smart charging schedule.

By selectively issuing real-time control messages, an energy management system can produce the effect of directly controlling an entire population of electric vehicles without directly communicating with each of them. Because the schedule transmitted to each vehicle is known by the optimization engine of the central energy management server, the scheduled behavior can be incorporated into the optimization process as if the vehicle was under direct control. Only necessary adjustment commands must be transmitted.

FIG. 11 shows an embodiment of smart charging via schedules with overrides for a power management system. A default charging schedule is periodically transmitted 1110 from a server. The default charging schedule is received 1120 by a device, such as an electric vehicle. A charging schedule override is transmitted from the server and overrides 1130 the default charging schedule.

In a system for managing smart charging via schedules with overrides, the electrical loads may be managed by a management system, such as the power aggregation system 100 as shown in FIG. 1 and described above. The server may be the flow control server 106 of the flow control center 102.

Local Load Management In The Presence Of Uncontrolled Loads

Energy management systems control the power draw of distributed electrical loads, such as electric vehicles. One of the benefits of such an system is the management of power-draw on feeder or premises circuits. For example, ten charging stations are installed on a branch circuit that only has the capacity to support five vehicles running at maximum power. An energy management system can be used to ensure that the total power consumed does not exceed the capacity of the branch circuit, while ensuring that the branch circuit is used to its fullest when sufficient cars are attached.

Similarly, facilities that are subject to utility demand charge (a surcharge based on the peak power consumed by the facility) may wish to keep total power consumption below a particular threshold.

While an energy management system can achieve a particular total load target by regulating the power drawn by each load on a circuit or in a site, there are many situations wherein some loads on the site or circuit are not under the control of the energy management system. In an embodiment, the power level of such uncontrolled loads or resources may not be controllable or adjustable by the energy management system.

In this situation, the energy management system may still be able to achieve a load-level goal for the entire site, provided it has access to information about the uncontrolled loads. For example, when the energy management system has real-time access to the total power level for a site under management (from a meter), it can infer the amount of uncontrolled load currently present in the site. This calculation is performed by subtracting the load under management from the total load reported for the entire site.

The energy management system could then adjust the target of the portion of load under control to be equal to the difference between the total desired load level and the amount of uncontrolled load.

As the uncontrolled increased, the controlled loads would be reduced. As the uncontrolled loads decreased, the controlled loads would increase. The result would be that total load remains under control, while the electric vehicles representing controlled loads have access to as much power as possible.

FIG. 12 shows an embodiment of local load management in the presence of uncontrolled loads for a power management system. A server receives 1201 power levels for electric resources at a site comprising controlled electric resources and uncontrolled electric resources. The total power level is determined 1202 and the controlled power level for the controlled electric resources is determined 1203. Based on the total power level and the controlled power level, the uncontrolled power level for the uncontrolled electric is determined 1204. The total power level is managed 1205 for the electric resources based on the said determinations. The management step may be performed on a particular machine, such as a physical computing device.

In a system for local load management in the presence of uncontrolled loads, the total power level may be managed by a management system, such as the power aggregation system 100 as shown in FIG. 1 and described above. The server may be the flow control server 106 of the flow control center 102.

Direct Load Control Via Prices To Devices

A prices-to-devices method for managing distributed power resources is to broadcast the current energy price to all such devices. Each device can have configurable rules that determine their behavior given an energy price. For example, according to one rule, an electric vehicle is charged if the energy price is less than X.

A direct-control method for managing distributed power resources is to send specific behavior instructions to specific devices. For example, an electric vehicle is commanded to either be charged immediately or not to be charged right now.

Direct load control offers benefits above those possible with prices-to-devices models. These benefits include the ability to deterministically curtail load, and the ability to precisely match load to an external signal. The external signal may be an AGC or a grid stabilization signal, or a signal indicating the ability of renewable energy.

While direct-control offers operation benefits, there may exist environments where prices-to-devices enabled endpoints have been deployed, and it is not practical to upgrade or replace them. If direct load control is desired in such an environment, it is necessary to retrofit direct-control over the prices-to-devices protocol.

Direct-control can be layered over prices-to-devices by dynamically adjusting the price transmitted to a set of devices in a way that is disconnected from the actual price of electricity, but that will achieve the desired behavior. For example, if there is a spinning reserves call, such that there is a sudden requirement that an electricity shortage be quickly made up through load curtailment, a price signal can be sent to a set of devices that is high enough to cause an appropriate number of devices to curtail charging.

In some circumstances, the server may have knowledge of the specific rules used by the controlled devices to determine the at what prices they will initiate and terminate charging. In such a circumstance, the server may deterministically control the behavior of devices by sending price signals known to trigger the desired behavior in the controlled devices.

In other circumstances, the server may not have knowledge of the specific rules used by the controlled devices. If smart metering or other similar technologies are present in such a circumstance, the server may still accomplish direct load control through an iterative process. Specifically, the server could adjust the price sent to all devices, monitor the resulting adjustment in electrical load, and then calculate a subsequent adjustment to the price sent to all devices. Through a series of progressive price adjustments, the specific desired load profile could be realized.

FIG. 13 shows an embodiment of direct load control via prices-to-devices for a power management system. An energy price is determined 1301 for electric resources comprising prices-to-devices enabled electric resources. The energy price is adjusted 1302 and transmitted 1303 from a server to a electric resource. The charging behavior of the prices-to-devices enabled electric resources are managed 1304.

In a system for managing electric resources with direct control over prices-to-devices enabled devices, the charging behavior may be managed by a management system, such as the power aggregation system 100 as shown in FIG. 1 and described above. The server may be the flow control server 106 of the flow control center 102.

CONCLUSION

Although systems and methods have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as examples of implementations of the claimed methods, devices, systems, etc. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims

1. A method for smart charging via periodically updated schedules, comprising the steps:

periodically transmitting a charging schedule via a network from a server to a plurality of electric resources;

receiving, by at least one of the plurality of electric resources, the charging schedule via the network from the server; and,

replacing a prior charging schedule with the received charging schedule, wherein the prior charging schedule controlled charging behavior for the at least one of the plurality of electric resources.

2. The method of claim 1, wherein the electric resources are distributed.

3. The method of claim 1, wherein the electric resources are electric vehicles.

4. The method of claim 1, wherein the server is a central energy management server.

5. The method of claim 1, wherein the charging schedule provides charging behavior for each one of the plurality of electric resources.

6. The method of claim 1, wherein the charging schedule defines average power-level constraints for the plurality of electrical resources.

7. The method of claim 1, wherein the average power-level constraints are based on a fixed time interval over a time period of charging schedule.

8. The method of claim 1, wherein the average power-level constraints are based on a percent of time during a time interval that at least one of the plurality of electrical resources charges at maximum charge power.

9. The method of claim 8, wherein the time interval is fixed.

10. The method of claim 1, wherein the at least one of the plurality of electrical resources consumes energy at a percent of the maximum charge power during the time interval that the at least one of the plurality of electrical resources charges at the maximum charge power, wherein the percent of the maximum charge power is equivalent to a percent corresponding to a percent of time during the time interval that the at least one of the plurality of electrical resources charges at the maximum charge power.

11. The method of claim 1, further comprising:

immediately enacting the received charging schedule.

12. The method of claim 1, further comprising:

storing unreported information in a database in the at least one of the plurality of electric resources, wherein the unreported information selected from a group consisting of the following: energy consumption, current power-level, battery state of charge, or energy transfers.

13. The method of claim 1, further comprising:

communicating the unreported information to the server when the at least one of the plurality of electric resources connects with the server.

14. The method of claim 1, further comprising:

transmitting, by at least one of the plurality of electric resources, a schedule update to the server.

15. The method of claim 14, wherein the schedule update is transmitted at a fixed time period.

16. The method of claim 15, wherein the fixed time period is determined by the charging schedule.

17. The method of claim 14, wherein the schedule update comprises current-state information.

18. The method of claim 17, wherein the current-state information comprises energy consumption, current power-level, battery state of charge, or unreported energy transfers.

19. The method of claim 1, further comprising:

scheduling charging of each of the plurality of electric resources at a time different from one another; and

preventing a sudden peak in load demand from the plurality of electric resources.

20. The method of claim 1, further comprising:

managing electrical loads for the plurality of electric resources based on charging schedules for the plurality of electric resources,

wherein the step of managing the electrical loads is performed on at least one particular machine, said at least one particular machine comprising at least one physical computing device.

21. A method for smart charging via schedules with overrides, comprising the steps:

periodically transmitting a default charging schedule via a network from a server to a plurality of electric resources;

receiving, by at least one of the plurality of electric resources, the default charging schedule via the network from the server;

transmitting a charging schedule override from the server to the at least one of the plurality of electric resources; and, overriding the default charging schedule with the charging schedule override, wherein the charging schedule override modifies charging behavior for the at least one of the plurality of electric resources.

22. The method of claim 21, wherein the charging schedule override is transmitted in real-time.

23. The method of claim 21, wherein the default charging schedule is beneficial in the local environment.

24. The method of claim 21, wherein the charging schedule override is transmitted in response to an unpredicted operational demand.

25. The method of claim 21, wherein the charging schedule override is transmitted in response to a power shortage.

26. The method of claim 21, wherein the charging schedule override is transmitted in response to a power surplus.

27. The method of claim 21, wherein the charging schedule override is transmitted in response to an unscheduled event.

28. The method of claim 21, wherein the charging schedule override increases energy consumption.

29. The method of claim 21, wherein the charging schedule override decreases energy consumption.

30. The method of claim 21, further comprising:

selectively transmitting real-time charging schedule overrides to the plurality of electric resources; and

managing electrical loads for the plurality of electric resources based on default charging schedules for the plurality of electric resources and the selective transmissions of charging schedule overrides,

wherein the step of managing the electrical loads is performed on at least one particular machine, said at least one particular machine comprising at least one physical computing device.

31. A method for local load management in the presence of uncontrolled loads, comprising the steps:

receiving, at a server, power levels for a plurality of electric resources, wherein the plurality of electric resources are located at a site;

determining a total power level for the plurality of electric resources, wherein the plurality of electric resources comprise controlled electric resources and uncontrolled electric resources;

determining a controlled power level for the controlled electric resources, wherein the controlled power level is adjustable via the server;

determining an uncontrolled power level for the uncontrolled electric resources based on the total power level and the controlled power level, wherein the uncontrolled power level is unadjustable via the server; and,

managing the total power level for the plurality of electric resources based on the said determinations, wherein the step of managing the total power level is performed on at least one particular machine, said at least one particular machine comprising at least one physical computing device.

32. The method of claim 31, wherein the electric resources are electric vehicles.

33. The method of claim 31, wherein the step of determining the uncontrolled power level is based on a power level variance between the controlled power level and the total power level.

34. The method of claim 31, wherein the step of determining the uncontrolled power level comprises subtracting the controlled power level from the total power level.

35. The method of claim 31, wherein the step of managing the total power level comprises adjusting the controlled power level based on a power level variance between the total power level and the uncontrolled power level.

36. The method of claim 31, wherein the step of managing the total power level comprises decreasing the controlled power level by an amount substantially equal to an increase in the uncontrolled power level.

37. The method of claim 31, wherein the step of managing the total power level comprises increasing the controlled power level by an amount substantially equal to a decrease in the uncontrolled power level.

38. The method of claim 35, 36, or 37, further comprising:

preventing the total power level from exceeding a threshold.

39. The method of claim 38, wherein the threshold is a maximum capacity of a branch circuit at the site.

40. The method of claim 31, wherein the step of managing the total power level comprises utilizing a branch circuit at the site at approximately maximum capacity.

41. The method of claim 31, wherein the step of managing the total power level comprises reducing an utility demand charge.

42. The method of claim 31, wherein the plurality of electric resources that are located at the site are on a single branch circuit.

43. The method of claim 31, wherein the server has real-time access to the plurality of electric resources.

44. A method for managing electric resources with direct control over prices-to-devices enabled devices, comprising the steps:

determining an energy price for a plurality of electric resources, wherein the plurality of electric resources comprise prices-to-devices enabled electric resources, wherein the prices-to-devices enabled electric resources have configurable rules for determining charging behavior based an energy price;

adjusting the energy price for at least one of the prices-to-devices enabled electric resources;

transmitting, from a server, the adjusted energy price to the at least one of the prices-to-devices enabled electric resources; and,

managing charging behavior of the at least one of the prices-to-devices enabled electric resources, wherein the step of managing the charging behavior is performed on at least one particular machine, said at least one particular machine comprising at least one physical computing device.

45. The method of claim 44, wherein the step of adjusting the energy price comprises:

determining a threshold price from the configurable rules for the at least one of the prices-to-devices enabled electric resources, wherein the at least one of the prices-to-devices enabled electric resources charges only when the energy price is below the threshold price, wherein the server has access to the configurable rules for determining charging of the at least one of the prices-to-devices enabled electric resources; and

increasing the energy price above the threshold price, whereby the at least one of the prices-to-devices enabled electric resources curtails charging.

46. The method of claim 44, wherein the step of adjusting the energy price comprises:

determining a threshold price from the configurable rules for the at least one of the prices-to-devices enabled electric resources, wherein the at least one of the prices-to-devices enabled electric resources charges only when the energy price is below the threshold price, wherein the server has access to the configurable rules for determining charging of the at least one of the prices-to-devices enabled electric resources; and

decreasing the energy price below the threshold price, whereby the at least one of the prices-to-devices enabled electric resources initiates charging.

47. The method of claim 44, wherein the step of adjusting the energy price comprises:

determining a profile of the at least one of the prices-to-devices enabled electric resources via a series of progressive price adjustments, wherein the profile comprises profile rules for determining charging behavior of the at least one of the prices-to-devices enabled electric resources, wherein the configurable rules for determining charging of the at least one of the prices-to-devices enabled electric resources are unaccessible to the server, wherein the at least one of the prices-to-devices enabled electric resources has a smart metering device or software;

determining a threshold price from the profile rules for the at least one of the prices-to-devices enabled electric resources, wherein the at least one of the prices-to-devices enabled electric resources charges only when the energy price is below the threshold price, increasing the energy price above the threshold price, whereby the at least one of the prices-to-devices enabled electric resources curtails charging.

48. The method of claim 44, wherein the step of adjusting the energy price comprises:

determining a profile of the at least one of the prices-to-devices enabled electric resources via a series of progressive price adjustments, wherein the profile comprises profile rules for determining charging behavior of the at least one of the prices-to-devices enabled electric resources, wherein the configurable rules for determining charging of the at least one of the prices-to-devices enabled electric resources are unaccessible to the server, wherein the at least one of the prices-to-devices enabled electric resources has a smart metering device or software;

determining a threshold price from the profile rules for the at least one of the prices-to-devices enabled electric resources, wherein the at least one of the prices-to-devices enabled electric resources charges only when the energy price is below the threshold price, decreasing the energy price above the threshold price, whereby the at least one of the prices-to-devices enabled electric resources initiates charging.

49. The method of claim 47 or 48, wherein the step of determining a profile comprises:

adjusting the energy price;

transmitting the adjusted energy price to the at least one of the prices-to-devices enabled electric resources;

monitoring a resulting charging behavior adjustment in the at least one of the prices-to-devices enabled electric resources, wherein the resulting charging behavior adjustment is based on a response of the at least one of the prices-to-devices enabled electric resources to the adjusted energy price;

determining a subsequent price adjustment based on resulting charging behavior adjustment; and,

iteratively repeating the said steps in order to determine profile rules for determining charging behavior of the at least one of the prices-to-devices enabled electric resources.

50. The method of claim 44, wherein the step of managing the charging behavior of the at least one of the prices-to-devices enabled electric resources comprises:

transmitting energy prices determined to trigger a desired charge behavior in the at least one of the prices-to-devices enabled electric resources, wherein the determined energy prices are based on the configurable rules for determining charging of the at least one of the prices-to-devices enabled electric resources.

51. The method of claim 44, wherein the step of managing the charging behavior of the at least one of the prices-to-devices enabled electric resources comprises:

transmitting energy prices determined to trigger a desired charge behavior in the at least one of the prices-to-devices enabled electric resources, wherein the determined energy prices are based on a profile of the at least one of the prices-to-devices enabled electric resources, wherein the profile is determined by an iterative process comprising price adjustments.

52. The method of claim 44, wherein the step of managing the charging behavior of the at least one of the prices-to-devices enabled electric resources comprises matching the charging behavior to an external signal, wherein the external signal is selected from a group consisting of the following: automated generation control (AGC) signals, grid stabilization signal, or a renewable energy signal.

53. The method of claim 44, wherein the energy price is adjusted in order to control charging behavior of the at least one of the prices-to-devices enabled electric resources, and wherein the adjusted energy price is different from a cost of electricity corresponding to the charging behavior of the at least one of the prices-to-devices enabled electric resources.