Charging location selection of incoming electric vehicles for large EV bin infrastructure

Abstract

As the use of renewable energy resources within the charging infrastructure increases, the risk that charging additional loads within the charging infrastructure will result in violation of applicable grid guidelines also increases. In an embodiment, a charging location is selected for an incoming load based on a load flow analysis to thereby mitigate the risk of violation. The selection process may also take into account the charge schedule of the load and the capability of the available charging stations (e.g., fast charge over slow charge).

Description

[0001] Government licensing rights

[0002] This invention was made with U.S. Government support under Contract No. DOE-OE0000896 awarded by the U.S. Department of Energy. The U.S. Government has certain rights in this invention. Technical Field

[0003] Embodiments described herein relate generally to energy management systems, and more particularly to selection of charging locations for variable loads, such as electric vehicles (EVs), within a charging infrastructure, such as an EV bunker. Background Art

[0004] In an effort to reduce greenhouse gas emissions, the deployment of EV charging stations has been increasing due to the growing use of EVs. An EV warehouse may include a distribution network (which includes multiple EV charging stations), auxiliary loads, and distributed energy resources (DERs) (including energy storage). Each EV charging station includes one or more chargers configured to deliver power to a connected electric vehicle (e.g., a bus, a car, a utility truck, etc.).

[0005] The distribution network may be managed by an energy management system (EMS), which is typically configured to reduce the cost of electricity consumption. The distribution network should maintain certain voltage and current levels to avoid violations of applicable grid guidelines (multiple). Such violations may affect the stability of the connected loads and the grid to which the distribution network is connected. When distributed energy resources are integrated into the EV warehouse, the possibility of violations increases.

[0006] When the distributed energy resources include renewable energy resources (e.g., solar generators, wind turbines, geothermal generators, hydroelectric generators, fuel cells, etc.), the energy management system generally prefers to utilize the maximum power generation from the renewable energy resources because the renewable energy resources have a lower unit cost. However, as the use of renewable energy resources increases, the probability of over-limits such as overvoltage in the distribution network also increases. In addition, as the EV load increases, the probability of over-limits such as undervoltage in the distribution network also increases.

[0007] In existing EV warehouse distribution networks, electric vehicles are typically scheduled for charging based on a first-come, first-served approach or based on the type of EV charging required by the electric vehicle. These conventional approaches may result in violations of applicable grid codes by the distribution network. In turn, these violations may result in penalties and potentially may lead to a collapse of the distribution network. Summary of the invention

[0008] Thus, systems, methods, and non-transitory computer readable media for a novel method of selecting a charging location for a variable load within a charging infrastructure are disclosed. It is an object of an embodiment to select a charging location for a variable load within a load distribution network based on a charging schedule for the variable load. It is an additional object of an embodiment to use load flow analysis during the selection of a charging location to reduce the likelihood of voltage overruns during charging of the variable load. It is another object of an embodiment to consider the capabilities of the charging station during the selection of a charging location.

[0009] In an embodiment, a method includes using at least one hardware processor to perform the following operations for at least one variable load to be charged in a distribution network including multiple nodes, wherein each of the multiple nodes includes one or more charging stations: determining a charging time period associated with the variable load; performing a load flow analysis on a model of the distribution network based on a power scheduling for existing loads to be charged in the distribution network during the charging time period; determining a charging station at one of the multiple nodes in the distribution network, at which the variable load is to be charged, based on a result of the load flow analysis; and scheduling the variable load to be charged at the determined charging station during the charging time period.

[0010] The method may further include using at least one hardware processor to control the determined charging station to output power to the variable load during the charging time period.

[0011] The variable load may be an electric vehicle, and the power distribution network may include a charging bay for the electric vehicle.

[0012] The results of the load flow analysis may include an indication of whether a voltage violation will occur.A voltage violation may be a violation of a grid code that defines voltage requirements that the distribution network must meet.

[0013] The method may further include using at least one hardware processor to exclude any node of the plurality of nodes that will exceed a limit from determining a charging station to charge the variable load when the results of the load flow analysis indicate that a limit will be exceeded. The limit may include an undervoltage.

[0014] Determining the charging time period may include: receiving a schedule associated with a variable load; and deriving the charging time period from the schedule associated with the variable load. The variable load may be an electric vehicle, and the power distribution network may include a charging bay for the electric vehicle, wherein the schedule associated with the electric vehicle includes a time when the electric vehicle is scheduled to leave the charging bay.

[0015] Determining a charging station to charge a variable load may include: determining whether the variable load requires fast charging based on the charging time period; and based on the determination of whether the variable load requires fast charging, selecting a charging station as the determined charging station. Selecting a charging station may include: when it is determined that the variable load requires fast charging: determining whether at least one fast charging station is available during the charging time period; and when it is determined that at least one fast charging station is available during the charging time period, selecting a fast charging station available during the charging time period from the at least one fast charging station as the determined charging station. Selecting a fast charging station may include: when a plurality of fast charging stations are available at two or more of a plurality of nodes, selecting a fast charging station at one of the two or more nodes as the determined charging station, the node having the highest voltage among the two or more nodes. Selecting a charging station may further include: when it is determined that no fast charging station is available during the charging time period, selecting a charging station at one of the plurality of nodes as the determined charging station, the node having the highest voltage among the plurality of nodes within the load flow analysis. Selecting the charging station may include, when it is determined that the variable load does not require fast charging, selecting a charging station at a node among the plurality of nodes having a highest voltage among the plurality of nodes within the load flow analysis as the determined charging station.

[0016] The distribution network may include one or more distributed energy resources, wherein determining a charging station to charge a variable load includes: selecting a node from a plurality of nodes to charge the variable load in each of one or more iterations until it is determined that an over-limit will not occur, wherein a different node from the plurality of nodes is selected in each iteration; performing an economic dispatch for the distribution network; performing a load flow analysis on a model of the distribution network based on a power dispatch for existing loads to be charged in the distribution network during a charging time period and charging of the variable load at the selected node; and determining whether an over-limit will occur based on the load flow analysis. The over-limit may include an undervoltage at the selected node. The power dispatch may include set points for one or more of the plurality of nodes in the distribution network, and a load flow analysis may be performed for each of the set points in the power dispatch. The one or more distributed energy resources may include one or more of a photovoltaic generator, a wind generator, a fuel cell, a thermal power plant, a hydroelectric power plant, a gasoline generator, or a battery.

[0017] It should be understood that any of the features in the above methods may be implemented individually or in any combination with any subset of the other features. Therefore, to the extent that the attached claims would imply specific dependencies between features, the disclosed embodiments are not limited to these specific dependencies. On the contrary, any of the features described herein may be combined with any other feature described herein, or implemented in any combination of any features without any one or more of the other features described herein. In addition, any of the methods described above and elsewhere herein may be embodied in an executable software module of a processor-based system (such as a server) and / or in executable instructions stored in a non-transitory computer-readable medium, either individually or in any combination. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The details of the invention, both as to its structure and operation, may be gleaned in part by examination of the accompanying drawings, in which like reference numerals refer to like parts, and in which:

[0019] Figure 1 illustrates an example infrastructure in which one or more of the processes described herein may be implemented according to an embodiment;

[0020] Figure 2 An example processing system is illustrated according to an embodiment by which one or more of the processes described herein may be performed;

[0021] Figure 3 illustrates an example power distribution network according to an embodiment; and

[0022] Figure 4 A process for selecting a charging location for a variable load within a power distribution network is illustrated according to an embodiment. DETAILED DESCRIPTION

[0023] In an embodiment, a system, method, and non-transitory computer-readable medium for selecting a charging location for a variable load (such as an electric vehicle (EV)) within a charging infrastructure (such as an EV warehouse) are disclosed. The term "variable load" refers to any load that requires occasional charging (e.g., an onboard battery) and can be charged at any of a plurality of different locations within the distribution network of the charging infrastructure. The variable load may need to be charged according to flexible or inflexible scheduling. In other words, the term "variable load" implies flexibility in charging location, not flexibility in scheduling or any other characteristics. Although it is generally assumed that the variable load will be an electric vehicle and the charging infrastructure will be an EV warehouse, the disclosed method is not limited to electric vehicles in an EV warehouse. On the contrary, the disclosed method can be applied to any variable load within any type of distribution network. Alternative examples of variable loads include, but are not limited to, drones, robotic systems, mobile devices, mobile machines, power tools, and the like, and a single charging infrastructure can be configured to charge one or more types of variable loads. As used herein, the term "distribution network" refers to the interconnection of electrical components within a charging infrastructure (e.g., an EV warehouse) that distributes power to variable loads. These electrical components mainly include: distributed energy resources and charging stations, which can be considered as "nodes" of the distribution network; and electrical connectors, which can be considered as "edges" connecting the nodes within the distribution network. The disclosed method can be based on the voltage range of each node in the distribution network, the charging scheduling of variable loads, the capacity of the charging station, the energy management of existing distributed energy resources in the distribution network, and / or the like, to thereby prevent or reduce violations of (multiple) applicable grid codes.

[0024] After reading this description, it will become apparent to those skilled in the art how to implement the present invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it should be understood that these embodiments are presented only by way of example and illustration and not limitation. Thus, this detailed description of various embodiments should not be construed as limiting the scope or breadth of the present invention as set forth in the appended claims.

[0025] 1. System Overview

[0026] 1.1 Infrastructure

[0027] Figure 1An example infrastructure is illustrated in which one or more of the disclosed processes may be implemented according to an embodiment. The infrastructure may include an energy management system (EMS) 110 (e.g., including one or more servers) that hosts and / or executes one or more of the various functions, processes, methods, and / or software modules described herein. The EMS 110 may include a dedicated server, or may be implemented instead in a computing cloud in which the resources of one or more servers are dynamically and elastically allocated to multiple tenants based on demand. In either case, the servers may be co-located and / or geographically distributed. The EMS 110 may also include or be communicatively connected to software 112 and / or one or more databases 114. In addition, the EMS 110 may be communicatively connected to one or more user systems 130 and / or charging infrastructure 140 (e.g., EV warehouse) via one or more networks 120.

[0028] The network(s) 120 may include the Internet, and the EMS 110 may communicate with the user system(s) 130 and / or the charging infrastructure(s) 140 over the Internet using standard transmission protocols, such as Hypertext Transfer Protocol (HTTP), HTTP Secure (HTTPS), File Transfer Protocol (FTP), FTP Secure (FTPS), Secure Shell FTP (SFTP), Extensible Messaging and Presence Protocol (XMPP), Open Field Message Bus (OpenFMB), IEEE Smart Energy Profile Application Protocol (IEEE 2030.5), etc., as well as proprietary protocols. Although the EMS 110 is illustrated as being connected to various systems via a single set of network(s) 120, it should be understood that the EMS 110 may be connected to various systems via a different set of one or more networks. For example, the EMS 110 may be connected to a subset of the user systems 130 and / or the charging infrastructure 140 via the Internet, but may be connected to one or more other user systems 130 and / or the charging infrastructure 140 via an intranet. Furthermore, while only a few user systems 130 and charging infrastructure 140 , one instance of software 112 , and a set(s) of databases 114 are illustrated, it should be understood that the infrastructure may include any number of user systems, charging infrastructure, software instances, and databases.

[0029] The user system(s) 130 may include any one or more types of computing devices capable of wired and / or wireless communication, including, but not limited to, desktop computers, laptop computers, tablet computers, smartphones or other mobile phones, servers, game consoles, televisions, set-top boxes, kiosks, point-of-sale terminals, embedded controllers, programmable logic controllers (PLCs), and / or the like. However, it is generally contemplated that the user system(s) 130 will include a personal computer, mobile device, or workstation through which an agent of an operator of the charging infrastructure 140 may interact with the EMS 110. These interactions may include inputting data (e.g., parameters for configuring one or more of the processes described herein) and / or receiving data (e.g., output of one or more of the processes described herein) via a graphical user interface provided by the EMS 110 or a system between the EMS 110 and the user system(s) 130. A graphical user interface may include screens (e.g., web pages) that include a combination of content and elements such as text, images, video, animations, references (e.g., hyperlinks), frames, inputs (e.g., text boxes, text areas, check boxes, radio buttons, drop-down menus, buttons, forms, etc.), scripts (e.g., JavaScript), and the like, including elements that include or are derived from data stored in one or more databases (e.g., database(s) 114).

[0030] The EMS 110 may include executable software 112 that includes one or more software modules that implement one or more of the disclosed processes. In addition, the EMS 110 may include, be communicatively coupled to, or otherwise have access to one or more databases 114 that store data input to one or more of the disclosed processes and / or output from one or more of the disclosed processes. Any suitable database may be utilized, including, but not limited to, MySQL. TM 、Oracle TM 、IBM TM , Microsoft SQL TM 、Access TM , PostgreSQL TM and more, including cloud-based databases, proprietary databases, and unstructured databases.

[0031] After reading this description, it will become apparent to those skilled in the art how to implement the present invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it should be understood that these embodiments are presented only by way of example and illustration and not limitation. Thus, this detailed description of various embodiments should not be construed as limiting the scope or breadth of the present invention as set forth in the appended claims.

[0032] 1.2 Example Processing Device

[0033] Figure 2 is a block diagram illustrating an example wired or wireless system 200 that may be used in conjunction with the various embodiments described herein. For example, the system 200 may be used as or in conjunction with one or more of the functions, processes, or methods described herein (e.g., to store and / or execute software 112), and may represent components of the EMS 110, (multiple) user systems 130, (multiple) charging infrastructures 140, and / or other processing devices described herein. The system 200 may be a server or any conventional personal computer, or any other processor-enabled device capable of wired or wireless data communications. As will be apparent to those skilled in the art, other computer systems and / or architectures may also be used.

[0034] The system 200 preferably includes one or more processors 210. The processor(s) 210 may include a central processing unit (CPU). Additional processors may be provided, such as a graphics processing unit (GPU), an auxiliary processor to manage input / output, an auxiliary processor to perform floating point math operations, a dedicated microprocessor with an architecture suitable for fast execution of signal processing algorithms (e.g., a digital signal processor), a processor that is subordinate to the main processing system (e.g., a back-end processor), an additional microprocessor or controller for a dual processor system or a multiple processor system, and / or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor 210. Examples of processors that may be used with the system 200 include, but are not limited to, processors available from Intel Corporation of Santa Clara, California (e.g., Pentium TM 、Core i7 TM , Xeon TM any of the processors available from Advanced Micro Devices, Inc. (AMD) of Santa Clara, California, any of the processors available from Apple Inc. of Cupertino (e.g., A-series, M-series, etc.), any of the processors available from Samsung Electronics Co., Ltd. of Seoul, South Korea (e.g., Exynos TM ) and / or etc.

[0035] The processor 210 is preferably connected to a communication bus 205. The communication bus 205 may include a data channel for facilitating information transfer between storage devices and other peripheral components of the system 200. In addition, the communication bus 205 may provide a set of signals for communicating with the processor 210, including a data bus, an address bus, and / or a control bus (not shown). The communication bus 205 may include any standard or non-standard bus architecture, such as, for example, a bus architecture that conforms to the following: Industry Standard Architecture (ISA), Extended Industry Standard Architecture (EISA), Micro Channel Architecture (MCA), Peripheral Component Interconnect (PCI) local bus, standards promulgated by the Institute of Electrical and Electronics Engineers (IEEE), including IEEE 488 General Purpose Interface Bus (GPIB), IEEE 696 / S-100, and / or the like.

[0036] The system 200 preferably includes a main memory 215, and may also include a secondary memory 220. The main memory 215 provides storage of instructions and data for programs executed on the processor 210, such as one or more of the functions and / or modules discussed herein (e.g., the software 112). It should be understood that the programs stored in the memory and executed by the processor 210 may be written and / or compiled according to any suitable language, including but not limited to C / C++, Java, JavaScript, Perl, Visual Basic, .NET, etc. The main memory 215 is typically a semiconductor-based memory, such as a dynamic random access memory (DRAM) and / or a static random access memory (SRAM). Other semiconductor-based memory types include, for example, synchronous dynamic random access memory (SDRAM), Rambus dynamic random access memory (RDRAM), ferroelectric random access memory (FRAM), etc., including read-only memory (ROM).

[0037] The secondary storage 220 may optionally include internal media 225 and / or removable media 230. The removable media 230 is read and / or written in any well-known manner. The removable storage medium 230 may be, for example, a tape drive, a compact disc (CD) drive, a digital versatile disc (DVD) drive, other optical drives, flash memory drives, and / or the like. The secondary storage 220 is a non-transitory computer-readable medium on which computer executable code (e.g., software 112) and / or other data is stored. The computer software or data stored on the secondary storage 220 is read into the main memory 215 for execution by the processor 210.

[0038] In alternative embodiments, the secondary memory 220 may include other similar devices for allowing computer programs or other data or instructions to be loaded into the system 200. Such devices may include, for example, a communication interface 240 that allows software and data to be transferred from an external storage medium 245 to the system 200. Examples of the external storage medium 245 may include an external hard drive, an external optical drive, an external magneto-optical drive, and / or the like. Other examples of the secondary memory 220 may include semiconductor-based memories such as programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), and flash memory (a block-oriented memory similar to EEPROM).

[0039] As mentioned above, the system 200 may include a communication interface 240. The communication interface 240 allows software and data to be transferred between the system 200 and an external device (e.g., a printer), a network, or other information source. For example, computer software or executable code may be transferred from a network server (e.g., platform 110) to the system 200 via the communication interface 240. Examples of the communication interface 240 include a built-in network adapter, a network interface card (NIC), a Personal Computer Memory Card International Association (PCMCIA) network card, a cardbus network adapter, a wireless network adapter, a universal serial bus (USB) network adapter, a modem, a wireless data card, a communication port, an infrared interface, an IEEE 1394 FireWire, and any other device capable of interfacing the system 200 with a network (e.g., network(s) 120) or another computing device. The communication interface 240 preferably implements industry-promulgated protocol standards, such as Ethernet IEEE 802 standards, Fibre Channel, Digital Subscriber Line (DSL), Asynchronous Digital Subscriber Line (ADSL), Frame Relay, Asynchronous Transfer Mode (ATM), Integrated Services Digital Network (ISDN), Personal Communications Service (PCS), Transmission Control Protocol / Internet Protocol (TCP / IP), Serial Line Internet Protocol / Point-to-Point Protocol (SLIP / PPP), etc., but may also implement custom or non-standard interface protocols.

[0040] Software and data transmitted via communication interface 240 are typically in the form of electrical communication signals 255. These signals 255 may be provided to communication interface 240 via communication channel 250. In embodiments, communication channel 250 may be a wired or wireless network (e.g., network(s) 120) or any of a variety of other communication links. Communication channel 250 carries signals 255 and may be implemented using a variety of wired or wireless communication means, including wire or cable, optical fiber, a conventional telephone line, a cellular telephone link, a wireless data communication link, a radio frequency ("RF") link, or an infrared link, to name a few.

[0041] Computer executable code (e.g., computer programs, such as software 112) is stored in the primary memory 215 and / or the secondary memory 220. Computer programs may also be received via the communication interface 240 and stored in the primary memory 215 and / or the secondary memory 220. Such computer programs, when executed, enable the system 200 to perform various functions of the disclosed embodiments, as described elsewhere herein.

[0042] In the specification, the term "computer-readable medium" is used to refer to any non-transitory computer-readable storage medium for providing computer executable code and / or other data to or within the system 200. Examples of such media include the main memory 215, the secondary memory 220 (including the internal memory 225 and / or the removable medium 230), the external storage medium 245, and any peripheral device (including a network information server or other network device) communicatively coupled to the communication interface 240. These non-transitory computer-readable media are devices for providing executable code, programming instructions, software and / or other data to the system 200.

[0043] In embodiments implemented using software, the software may be stored on a computer-readable medium and loaded into the system 200 by way of the removable media 230, the I / O interface 235, or the communication interface 240. In such embodiments, the software is loaded into the system 200 in the form of electrical communication signals 255. The software, when executed by the processor 210, preferably causes the processor 210 to perform one or more of the processes and functions described elsewhere herein.

[0044] In embodiments, the I / O interface 235 provides an interface between one or more components of the system 200 and one or more input and / or output devices. Example input devices include, but are not limited to, sensors, keyboards, touch screens or other touch-sensitive devices, cameras, biometric sensing devices, computer mice, trackballs, pen-based pointing devices, and / or the like. Examples of output devices include, but are not limited to, other processing devices, cathode ray tubes (CRTs), plasma displays, light emitting diode (LED) displays, liquid crystal displays (LCDs), printers, vacuum fluorescent displays (VFDs), surface conduction electron emitter displays (SEDs), field emission displays (FEDs), and / or the like. In some cases, input devices and output devices may be combined, such as in the case of a touch panel display (e.g., in a smartphone, tablet, or other mobile device).

[0045] System 200 may also include optional wireless communication components that facilitate wireless communication over voice networks and / or data networks (e.g., in the case of user system 130 being a smartphone or other mobile device). The wireless communication components include antenna system 270, radio system 265, and baseband system 260. In system 200, radio frequency (RF) signals are transmitted and received over the air by antenna system 270 under the management of radio system 265.

[0046] In an embodiment, the antenna system 270 may include one or more antennas and one or more multiplexers (not shown) that perform a switching function to provide transmit and receive signal paths for the antenna system 270. In the receive path, the received RF signal may be coupled from the multiplexer to a low noise amplifier (not shown) that amplifies the received RF signal and sends the amplified signal to the radio system 265.

[0047] In an alternative embodiment, the radio system 265 may include one or more radios configured to communicate over various frequencies. In an embodiment, the radio system 265 may combine a demodulator (not shown) and a modulator (not shown) in an integrated circuit (IC). The demodulator and modulator may also be separate components. In the incoming path, the demodulator removes the RF carrier signal and leaves the baseband receive audio signal, which is sent from the radio system 265 to the baseband system 260.

[0048] If the received signal contains audio information, the baseband system 260 decodes the signal and converts it into an analog signal. Then, the signal is amplified and sent to the speaker. The baseband system 260 also receives analog audio signals from a microphone. These analog audio signals are converted into digital signals and encoded by the baseband system 260. The baseband system 260 also encodes the digital signal for transmission and generates a baseband transmission audio signal, which is routed to the modulator part of the radio system 265. The modulator mixes the baseband transmission audio signal with the RF carrier signal to generate an RF transmission signal, which is routed to the antenna system 270 and can pass through a power amplifier (not shown). The power amplifier amplifies the RF transmission signal and routes it to the antenna system 270, where the signal is switched to the antenna port for transmission.

[0049] The baseband system 260 is also communicatively coupled to the processor(s) 210. The processor(s) 210 have access to data storage areas 215 and 220. The processor(s) 210 are preferably configured to execute instructions (i.e., computer programs, such as the disclosed software) which may be stored in the main memory 215 or the secondary memory 220. Computer programs may also be received from the baseband processor 260 and stored in the main memory 210 or in the secondary memory 220, or executed upon receipt. Such computer programs, when executed, enable the system 200 to perform the various functions of the disclosed embodiments.

[0050] After reading this description, it will become apparent to those skilled in the art how to implement the present invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it should be understood that these embodiments are presented only by way of example and illustration and not limitation. Thus, this detailed description of various embodiments should not be construed as limiting the scope or breadth of the present invention as set forth in the appended claims.

[0051] 1.3 Example Charging Infrastructure

[0052] Figure 3 A single-line diagram of an example distribution network of an example charging infrastructure 140 according to an embodiment is illustrated. As an example, the charging infrastructure 140 can be an EV warehouse for charging electric vehicles as variable loads. The charging infrastructure 140 is connected to the power grid 310, from which electricity can be purchased. According to time-of-use electricity (ToU) rates, the cost of purchasing electricity can vary throughout each day (e.g., higher during the day than at night) and across days (e.g., higher in summer days than in winter days). ToU rates can assign peak rates, partial peak rates, and off-peak rates to various time periods (e.g., hourly intervals in a day), thereby representing the cost of electricity during those time periods.

[0053] The charging infrastructure 140 may include one or more distributed energy resources, including, for example, one or more battery energy storage (BES) systems 320 and / or one or more generators 330 (illustrated as generators 330A and 330B). The generator(s) 330 may include renewable energy resources (e.g., solar generators, wind generators, geothermal generators, hydroelectric generators, fuel cells, etc.) and / or non-renewable energy resources (e.g., diesel generators, natural gas generators, etc.). For example, generator 330A may be a solar generator including a plurality of photovoltaic cells that convert sunlight into electricity, and generator 330B may be a diesel generator that burns diesel gasoline to generate electricity.

[0054] The charging infrastructure 140 also includes a distribution network (which includes multiple nodes) and potentially one or more auxiliary loads. Each node may include a charging station 340 or be composed of a charging station 340, which is illustrated as charging stations 340A, 340B, 340C, 340D, 340E, 340F and 340G. Each charging station 340 may include one or more chargers 342. For example, charging station 340F is illustrated as having two chargers 342. Each charger 342 is configured to be electrically connected to a variable load 350 so as to supply power to one or more batteries of the variable load 350. At any given time, some chargers 342 may be connected to the variable load 350, while other chargers 342 may not be connected to the variable load 350 and may be used to receive incoming variable loads 350. One or more charging stations 340 or individual chargers 342 may be configured to switch on or off the power supply to the variable load 350 under the control of the EMS110 or another controller. For example, the charging station 340 and / or the charger 342 may include a processing system 200 that receives commands from a controller (e.g., EMS 110) via a communication interface 240, processes the commands using a processor 210 and a main memory 215, and controls an actuator (e.g., one or more switches) to turn on or off the power supply according to the processed commands. It should be understood that the distribution network of the charging infrastructure 140 may also include load types other than the variable load 350, such as auxiliary loads used to operate various functions of the charging infrastructure 140. It should also be understood that each BES system 320 can act as both a power source (i.e., when discharging) and a load (i.e., when charging).

[0055] The parameters (e.g., voltage, current, etc.) of each node within the distribution network of the charging infrastructure 140 may be monitored by the EMS 110 and / or simulated by the EMS 110 (e.g., during load flow analysis). Thus, the EMS 110 may monitor and / or simulate the parameters of the nodes within the distribution network and control one or more components of the charging infrastructure, such as charging station(s) 340, charger(s) 342, generator(s) 330, BES system(s) 320, and / or the like, based on those parameters. This control may be performed periodically or in real time.

[0056] One or more charging stations 340 may include one or more chargers 342 that are capable of significantly faster charging relative to other chargers 342. There are several mechanisms for implementing fast charging, primarily centered around increasing wattage by increasing the current and / or voltage in the electrical connections. It should be understood that the term "fast charging" or "fast-type charging" refers to charging that is relatively fast relative to the overall (e.g., average) charging in the charging infrastructure 140, while "slow charging" or "slow-type charging" refers to charging that is relatively slow relative to the overall charging in the charging infrastructure 140. Thus, a "fast charger" is a charger 342 that is capable of fast charging, while a "slow charger" is a charger 342 that is not capable of fast charging. The EMS 110 may maintain a record of which charging stations 340 and / or chargers 342 of each charging infrastructure 140 are capable of fast-type charging (e.g., maintained in a database 114). When selecting a charging location for a variable load 350 that may require fast charging, one or more of the disclosed processes may utilize this record to determine which charging stations 340 and / or chargers 342 are currently fast charging.

[0057] 2. Process Overview

[0058] An embodiment of a process for selecting a charging location for a variable load within a charging infrastructure will now be described in detail. It should be understood that the described process may be embodied in one or more software modules executed by one or more hardware processors, for example as software 112 executed by (multiple) processors 210 of the EMS 110. The described process may be implemented as instructions represented in source code, object code, and / or machine code. These instructions may be executed directly by (multiple) hardware processors 210, or alternatively, by a virtual machine or container operating between the object code and the hardware processor 210. In addition, the disclosed software may be built on top of or interfaced with one or more existing systems.

[0059] Alternatively, the described process may be implemented as a hardware component (e.g., a general purpose processor, an integrated circuit (IC), an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, etc.), a combination of hardware components, or a combination of hardware and software components. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits and steps are generally described in this article with respect to their functions. Whether such functions are implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. The technician can implement the described functions in a varying manner for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present invention. In addition, the functional grouping within components, blocks, modules, circuits or steps is for ease of description. Without departing from the present invention, a specific function or step can be moved from one component, block, module, circuit or step to another component, block, module, circuit or step.

[0060] Figure 4 A process 400 for selecting a charging location for a variable load 350 (e.g., an electric vehicle) within a distribution network of a charging infrastructure 140 (e.g., an EV warehouse) according to an embodiment is illustrated. The process 400 may be implemented as software 112 executed by one or more processors 210 of the EMS 110. Although the process 400 is illustrated as having a certain arrangement and order of subprocesses, the process 400 may be implemented with fewer, more, or different subprocesses and subprocesses of different arrangements and / or orderings. For example, the process 400 may omit any one or more of the illustrated subprocesses so as to include or consist of any subset of the illustrated subprocesses. In addition, any subprocess that is not dependent on the completion of another subprocess may be performed before, after, or in parallel with the other independent subprocess, even if the subprocesses are described or illustrated in a particular order.

[0061] Process 400 may be performed when an incoming variable load 350 needs to be scheduled for charging. Thus, initially, in subprocess 405, process 400 waits for a request to schedule charging for a newly incoming variable load 350. The request may be received from another process (e.g., within the same EMS 110) or another system that manages the scheduling or routing of variable loads 350, manual input via a graphical user interface (e.g., provided by the EMS 110 or the variable load 350), the variable load 350 itself (e.g., within an electric vehicle that is the variable load 350 and tracks the current route of the electric vehicle), and / or the like. In an alternative embodiment, process 400 may be performed periodically (e.g., every fifteen minutes) for a batch of newly incoming variable loads 350 that have accumulated since the last execution of process 400 so that these variable loads are scheduled for charging. In either case, as long as there is no new incoming variable load 350 (ie, "No" in subprocess 405), process 400 can continue to wait. When there is a new incoming variable load 350 (ie, "Yes" in subprocess 405), process 400 can continue to subprocess 410.

[0062] In subprocess 410, a charging time period during which the variable load 350 will be charged may be determined based on the schedule of the newly arrived variable load 350. The schedule may be received in the request in subprocess 405, stored in a database (e.g., 114) accessible to the system implementing process 400 (e.g., accessible to EMS 110), and / or retrieved from another system (e.g., via an API provided by the other system). The charging time period may be determined as a time period between the scheduled arrival of the newly arrived variable load 350 and the scheduled departure of the newly arrived variable load 350, or a portion of the time period (e.g., taking into account a buffer time period before and after charging). In other words, subprocess 410 may check the schedule of the newly arriving variable load 350 (including the scheduled arrival time of the variable load 350 at the charging infrastructure 140 and the scheduled departure time of the variable load 350 from the charging infrastructure 140), and determine the time period that can be used to charge the variable load 350 before the scheduled departure of the variable load 350 as the charging time period. In determining this time, subprocess 410 may also take into account other considerations, such as whether the departure time is flexible (in which case it can be postponed to increase the charging time period) or inflexible (in which case it cannot be postponed so that the charging time period is fixed), the charge level that the variable load 350 will require before its departure (e.g., based on how far or how long the variable load 350 will need to travel before its next charge, as determined by its schedule), the expected charge level that the variable load 350 will have when it arrives (e.g., based on its current charge level and remaining route), the expected delay between the arrival of the variable load 350 and the start of charging, changes to the scheduled arrival time of the variable load 350, and / or the like.

[0063] In subprocess 415, given an existing charging schedule, a load flow analysis is performed on the existing power usage schedule of the distributed energy resources within the charging infrastructure 140 to identify any limit violations (e.g., voltage limits such as overvoltage or undervoltage, current limits, etc.) during a relevant time period, which includes or consists of the charging time period determined in subprocess 410. The existing power usage schedule and / or charging schedule may be stored in a database (e.g., 114) accessible to the system implementing process 400 (e.g., accessible to EMS110) and / or retrieved from another system (e.g., via an application programming interface (API) provided by the other system). The distribution network of the charging infrastructure 140 may be modeled by a distribution network model that represents each node in the distribution network. For example, an IEEE 13 bus system may be used for the distribution network model. The load flow analysis may simulate the power usage schedule on the distribution network model during the relevant time period to determine whether any node in the distribution network generates a limit violation during the simulation. For example, the power schedule may include set points for nodes in the distribution network, and a load flow analysis may be performed for each of the set points in the power schedule during a relevant time period. In particular, the load flow analysis determines the operating steady state of each node in the distribution network for a given loading in the power schedule during the relevant time period (e.g., derived from a charging schedule). The steady state of each node may be represented as a set of parameters, such as voltage, phase angle, real power, reactive power, and / or the like. The load flow analysis may solve one or more of these parameters (e.g., voltage and phase angle) at each node in the distribution network as represented in the distribution network model based on the real power and reactive power set points for the nodes in the distribution network using a set of simultaneous algebraic power equations.

[0064] In subprocess 420, process 400 determines whether the results of the load flow analysis applied in subprocess 415 include or indicate any limit crossing. For example, an overvoltage limit crossing may occur when the voltage at the node steady state exceeds a predefined threshold. Similarly, an undervoltage limit crossing may occur when the voltage at the node steady state is less than a predefined threshold. Other parameters (such as current) can be detected in a similar manner (e.g., using predefined thresholds). These (multiple) predefined thresholds may be defined by a grid code, such as the IEEE 1547 standard for interconnection and interoperability of distributed energy resources with associated power systems. IEEE 1547 defines the operating region of sustained voltage operation of its abnormal operating performance category III as having a lower bound of 0.88 per unit and an upper bound of 1.1 per unit. Therefore, if IEEE 1547 is used for the grid code, a voltage above 1.1 per unit at the node will be determined as an overvoltage limit crossing, and a voltage below 0.88 per unit at the node will be determined as an undervoltage limit crossing. If any limit crossing is detected (i.e., "yes" in subprocess 420), process 400 proceeds to subprocess 425. Otherwise, if no limit crossing is detected (i.e., "no" in subprocess 420), process 400 proceeds to subprocess 445. It should be understood that a limit crossing may be detected (i.e., "yes" in subprocess 420) when the results of the load flow analysis include a limit crossing or otherwise indicate that a limit crossing will occur, and a limit crossing may not be detected (i.e., "no" in subprocess 420) when the results of the load flow analysis do not include a limit crossing or otherwise do not indicate that a limit crossing will occur. In an embodiment, subprocess 420 may only determine whether the results of the load flow analysis include a specific limit crossing (such as, undervoltage), while ignoring other types of limit crossings (such as, overvoltage).

[0065] In subprocess 425, any nodes that experienced a specific limit violation during the load flow analysis in subprocess 415 as detected in subprocess 420 may be discarded from consideration. It should be understood that each node in the load flow analysis represents a specific charging station 340. In an embodiment, the only specific limit violation for which a node is discarded in subprocess 425 is an undervoltage at the charging station 340. In this embodiment, nodes that experienced an overvoltage were not discarded in subprocess 425. However, it should be understood that in alternative embodiments, nodes may be discarded based on any violation of a grid code that indicates that the node may not be a suitable charging location for a newly incoming variable load 350.

[0066] Prior to subprocess 425, process 400 may initialize a list with all available nodes (i.e., charging stations 340). The list may represent all available nodes from which a charging location for a newly-arrived variable load 350 may be selected. In subprocess 425, nodes that were crossed during the load flow analysis in subprocess 415 may be removed from the list, thereby preventing them from being selected as charging locations for newly-arrived variable loads 350. In other words, only those nodes remaining in the list will be considered in subsequent subprocesses, and all other nodes will be excluded from determining a charging location for a newly-arrived variable load 350. It should be understood that this is merely one embodiment of how a set of possible charging locations may be screened or narrowed during process 400, and that equally suitable alternative embodiments are possible.

[0067] In subprocess 430, process 400 determines whether the newly arrived variable load 350 requires fast charging. If the charging time period determined in subprocess 410 is too short to charge the newly arrived variable load 350 to the required level by slow charging, subprocess 430 may determine that the newly arrived variable load 350 requires fast charging. Otherwise, if the charging time period determined in subprocess 410 is sufficient to charge the newly arrived variable load 350 to the required level by slow charging, subprocess 430 may determine that the newly arrived variable load 350 does not require fast charging. For example, if the charging time period does not meet (e.g., is less than) a predefined threshold, subprocess 430 may determine that fast charging is required (i.e., "yes" in subprocess 430) and proceed to subprocess 435. Otherwise, if the charging time period meets (e.g., is greater than or equal to) the predefined threshold, subprocess 430 may determine that fast charging is not required (i.e., “No” in subprocess 430 , indicating that slow charging is sufficient) and proceed to subprocess 445 .

[0068] In subprocess 435, process 400 determines whether any fast chargers are available. The charging schedule may indicate which chargers 342 are being used (from which unused chargers 342 may be derived) and / or which chargers 342 are not being used. Thus, subprocess 435 may analyze the charging schedule to determine if there are any unused fast chargers 342 (i.e., fast chargers capable of fast charging) during a sufficient time period within the charging time period to charge the newly arrived variable load 350 to a sufficient charge level before it leaves the scene. If such fast chargers are available (i.e., "yes" in subprocess 435), process 400 may proceed to subprocess 440. Otherwise, if such fast chargers are not available (i.e., "no" in subprocess 435), process 400 may proceed to subprocess 445.

[0069] In subprocess 440, any nodes that do not have an available fast charger (as determined as a requirement in subprocess 435) may be discarded from consideration. For example, in an embodiment that uses a list of available nodes, those nodes that do not have such fast chargers may be removed from the list, thereby preventing them from being selected as charging locations for newly incoming variable loads 350. In other words, nodes that do not have an available fast charger will be excluded from determining charging locations for newly incoming variable loads 350.

[0070] In subprocess 445, among the remaining nodes under consideration, a node with a relatively high voltage during the previous load flow analysis may be selected as the charging location of the newly arrived variable load 350. In an embodiment using a list of available nodes, the remaining nodes under consideration will be the nodes remaining in the list when subprocess 445 is executed. In an embodiment, among the remaining nodes under consideration, subprocess 445 selects the node with the highest voltage during the most recent load flow analysis. Alternatively, among the nodes that meet one or more other criteria (e.g., connector type, sufficient space to accommodate the variable load 350, etc.), subprocess 445 may select the node with the highest voltage during the most recent load flow analysis. It should be understood that a node with a higher voltage during the load flow analysis generally means that the node serves less load than a node with a lower voltage during the load flow analysis. Therefore, in general, charging the newly arrived variable load 350 at a node with a higher voltage will minimize the possibility of undervoltage crossing in the distribution network of the charging infrastructure 140.

[0071] In subprocess 450, an economic dispatch is performed for the relative time period (the relative time period includes or consists of the charging time period) based on the charging schedule, which is modified by adding the newly arrived variable load 350 that is charged at the scheduled time and at the node selected in subprocess 445. The economic dispatch can be implemented as a software application that is integrated into the software that implements the other subprocesses of process 400. Alternatively, the economic dispatch can be implemented as a software application that is separate from the software that implements one or more other subprocesses of process 400 and provides its output (e.g., to subprocess 455) via an API. For example, the modified charging schedule can be pushed through the API of the software that implements subprocess 450, or alternatively, can be pulled by the software that implements subprocess 450 through the API.

[0072] Economic dispatch refers to allocating electricity demand from loads (e.g., variable loads 350) to distributed energy resources (e.g., BES systems 320 and / or generators 330) in order to achieve the most economical use of electricity. Typically, economic dispatch is formulated as an optimization problem, where the goal is to minimize the cost of purchasing electricity from the grid 310. The basic idea is to prioritize the use of distributed energy resources with lower marginal costs over the use of distributed energy resources and the grid 310 with higher marginal costs.

[0073] In an embodiment, an economic dispatch is performed for the relevant time period (the relevant time period includes the charging time period of the newly arrived variable load 350) based on a charging schedule that covers at least the relevant time period and includes charging the newly arrived variable load 350 at the scheduled time and at the node selected in the subprocess 445. For each of the one or more variable loads 350 to be charged during the relevant time period, the charging schedule may include the following: the location (e.g., node / charging station 340 and / or charger 342), the time when the charging of the variable load 350 is scheduled to begin, the duration of time that the variable load 350 is scheduled to be charged, the amount of charge to be supplied to the variable load 350 and / or the charge level to which the variable load 350 is to be charged (e.g., to have sufficient charge to complete the scheduled route), the time when the variable load 350 must be charged (e.g., to complete the route as scheduled), and / or the like. The charging schedule may be updated periodically (e.g., every fifteen minutes) to reflect the current or expected status of each variable load 350. It should be understood that the charging schedule may include a schedule for more than one time period to be considered (e.g., all future time periods for which charging has been scheduled) as long as it includes a schedule for a relevant time period during which the newly arriving variable load 350 will be charged.

[0074] The economic dispatch in subprocess 450 may generate an electricity usage schedule that specifies the power to be output from each of the distributed energy resources (e.g., BES system 310 and / or generator 330) in the charging infrastructure 140 during the relevant time period under consideration in order to satisfy the variable loads 350 in the charging schedule for the particular time period under consideration (including charging the newly incoming variable loads 350 at the nodes selected in subprocess 445) while minimizing the cost of electricity during the relevant time period under consideration. For each distributed energy resource to be used during the relevant time period under consideration, the electricity usage schedule includes the following: the identity of the distributed energy resource, the time span during which the distributed energy resource is scheduled to output power (e.g., discharge from the BES system 320 or generate by the generator 330), the amount of power to be output by the distributed energy resource, one or more set points for the distributed energy resource, and / or the like. During execution, economic dispatch may take into account equality constraints (e.g., power balance, state of charge balance of variable loads 350, etc.) and inequality constraints (e.g., maintaining the load at a certain value at the common connection point, maintaining a threshold level of the state of charge of the variable loads 350, pre-processing variable loads, availability of variable loads 350, etc.).

[0075] In subprocess 455, given the charging schedule (e.g., modified to have the newly arrived variable load 350 charged at the node selected in subprocess 445), a load flow analysis is performed on the power consumption schedule that has been generated by the economic dispatch in subprocess 450 for the relevant time (the relevant time period includes or consists of the charging time period determined in subprocess 410). The load flow analysis in subprocess 455 can be similar or identical to the load flow analysis in subprocess 415, except that the charging schedule has been modified to account for the newly arrived variable load 350 charged at the node selected in subprocess 445, and the power consumption schedule has been updated by the economic dispatch in subprocess 450. Therefore, any description of the load flow analysis with respect to subprocess 415 is equally applicable to the load flow analysis in subprocess 455.

[0076] In subprocess 460, process 400 determines whether the results of the load flow analysis applied in subprocess 455 include or indicate a specific limit crossing at the node selected as the charging location of the newly arrived variable load 350 in subprocess 445. In particular, subprocess 460 can determine whether an undervoltage occurs at the selected node during the load flow analysis. An undervoltage at the selected node can indicate that the selected node is not suitable for charging the newly arrived variable load 350 during the scheduled time. Conversely, the absence of an undervoltage at the selected node can indicate that the selected node is suitable for charging the newly arrived variable load 350 during the scheduled time. Therefore, if a specific limit crossing is detected at the selected node (i.e., "yes" in subprocess 460), process 400 proceeds to subprocess 465. Otherwise, if a specific limit crossing is not detected at the selected node (i.e., "no" in subprocess 460), process 400 proceeds to subprocess 470. It should be understood that when the results of the load flow analysis include an undervoltage crossing or otherwise indicate that an undervoltage will occur at the selected node, a crossing may be detected (i.e., a "yes" in subprocess 460), while when the results of the load flow analysis do not include an undervoltage crossing or otherwise do not indicate that an undervoltage crossing will occur at the selected node, a crossing may not be detected (i.e., a "no" in subprocess 460). Although the example of an undervoltage crossing is used as a specific crossing detected in subprocess 460, it should be understood that in alternative embodiments, any violation of the grid code may be detected in subprocess 460 that indicates that the selected node may not be a suitable charging location for the newly incoming variable load 350.

[0077] In subprocess 465, selected nodes facing a particular limit violation (e.g., undervoltage) as determined in subprocess 460 are discarded from consideration. For example, in an embodiment using a list of available nodes, a node selected in a previous iteration of subprocess 445 may be removed from the list, thereby preventing the node from being selected again as a charging location for a newly incoming variable load 350. In other words, the node will be excluded from determining a charging location for a newly incoming variable load 350. Therefore, process 400 may return to subprocess 445 to select a different available node.

[0078] In some cases, the list of available nodes may become empty, such that there are no remaining nodes for selection in subprocess 445. Process 400 may address such situations by initiating an exception handling process or other mechanism. For example, the exception handling process may modify the existing charging schedule to: move a load 350 with a flexible charging time to a different charging time in order to free up a charging station 340 for a newly arriving variable load 350 during the charging time period; move a variable load 350 that is scheduled for a fast charger but does not require fast charging to a slow charger in order to free up a fast charger for the newly arriving variable load 350; reroute the newly arriving variable load 350 or another variable load 350 in the charging schedule to another charging infrastructure 140 (e.g., under the management of the same EMS 110); relax the fast charging requirement for the newly arriving variable load 350 (i.e., if fast charging was originally determined to be required in subprocess 430); select a node with the least likelihood of an undervoltage violation for the newly arriving variable load 350 when the load flow analysis in subprocess 455 predicts that an undervoltage violation will occur at all possible nodes, and / or the like.

[0079] In subprocess 470, once a node is selected that does not produce any limit violations detected by the load flow analysis in subprocess 455, the charging of the newly arriving variable load 350 at the node selected in the most recent iteration of subprocess 445 is added to the existing charging schedule. This final charging schedule can be used to schedule various loads (including variable loads 350) during the relevant time period. In addition, the final power consumption schedule output by the most recent iteration of the economic dispatch in subprocess 450 can be used to schedule the power output by the distributed energy resources (e.g., (multiple) BEM system 320, (multiple) generator 330, etc.) during the relevant time period. The final charging schedule and / or the final power consumption schedule can be used to inform control decisions during the relevant time period.

[0080] In an embodiment, the final electricity scheduling is used to route the variable load 350. For example, the EMS 110 or another system may generate text, visual, and / or navigation commands to route an electric vehicle as a variable load 350 to a scheduled EV warehouse as the charging infrastructure 140, a scheduled charging station 340 and / or charger 342 within the EV warehouse 140, and / or other scheduled destinations. In particular, these commands may be provided to a console within the electric vehicle to display visual aids that guide the driver of the electric vehicle to the scheduled destination. In the case of an autonomous electric vehicle or drone as the variable load 350, the navigation commands may be provided to the control system (e.g., an electronic control unit (ECU)) of the electric vehicle or drone to automatically guide the autonomous electric vehicle or drone to the scheduled destination.

[0081] In an embodiment, the EMS 110 or another system may use the final electricity schedule to generate control commands for one or more BES systems 320, generators 330, charging stations 340, and / or other electrical components of the charging infrastructure 140. In particular, the EMS 110 may generate control commands and send the control commands to the relevant electrical components in the charging infrastructure 140 via the (multiple) networks 120, which may then execute the received control commands. For example, the EMS 110 may send control commands to distributed energy resources (e.g., BES systems 320, generators 330, etc.) to thereby control the distributed energy resources to generate and / or output electricity during one or more scheduled time periods and not output electricity outside the one or more scheduled time periods. As another example, the EMS 110 may send control commands to the charging station 340 to thereby control the charging station 340 to output electricity to the connected variable load 350 during one or more scheduled time periods and not output electricity outside the one or more scheduled time periods.

[0082] 3. Example Use Case

[0083] The charging infrastructure 140 may include EV bays for charging fleets of electric vehicles (e.g., operated by municipal mass transit systems, utility companies, trucking companies, construction companies, taxi companies, waste management companies, etc.), personal electric vehicles, and / or the like as variable loads 350. For example, in the case of a municipal mass transit system (such as a bus bay), each electric bus has a route that it must serve according to a route schedule. Thus, each electric bus must be charged to at least a sufficient charge level to complete its scheduled route and must leave the EV bay at a certain time in order to comply with the route schedule.

[0084] The disclosed embodiments may be applied to a microgrid that includes one charging infrastructure 140 or a system of two or more different charging infrastructures 140. For example, a single EMS 110 may manage power scheduling and charging scheduling for multiple charging infrastructures 140 (e.g., operated by the same operator). In this case, the charging scheduling may cover charging at charging stations 340 across multiple charging infrastructures 140, and the power scheduling may cover power generation in distributed energy resources across the multiple charging infrastructures 140. In addition, in the case where a newly arrived variable load 350 can be easily charged at two or more different charging infrastructures 140, the available nodes to be considered by the process 400 for the charging location of the newly arrived variable load 350 may include nodes across two or more charging infrastructures 140.

[0085] The disclosed embodiments may select charging locations for incoming variable loads 350 within one or more charging infrastructures 140 while taking into account voltage ranges at various nodes within the distribution network (e.g., in subprocesses 415-425, 445, and 455-465), charging schedules for variable loads 350 (e.g., in subprocess 430), capabilities of charging stations 340 (e.g., in subprocesses 435-445), energy management of distributed energy resources in the distribution network (e.g., in subprocesses 415, 450, and 455), and / or the like. Advantageously, taking into account one or more of these factors helps the charging infrastructure 140 avoid violations of applicable grid codes by maintaining voltage and / or current levels within acceptable limits. This, in turn, enables the operator of the charging infrastructure 140 to avoid penalties resulting from over-limits and ensure compliance with the scheduling of variable loads 350.

[0086] The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles described herein may be applied to other embodiments without departing from the spirit or scope of the present invention. Therefore, it will be understood that the description and drawings presented herein represent currently preferred embodiments of the present invention, and therefore represent the subject matter broadly contemplated by the present invention. It should be further understood that the scope of the present invention fully encompasses other embodiments that may become apparent to those skilled in the art, and the scope of the present invention is accordingly not limited.

[0087] Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" described herein include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, and any such combination may include one or more members of its components A, B, and / or C. For example, the combination of A and B may include one A and multiple Bs, multiple A and one B, or multiple A and multiple Bs.

Claims

1. A method for charging at least one variable load in a power distribution network comprising a plurality of nodes, comprising using at least one hardware processor to perform the following operations, wherein: Each of the plurality of nodes comprises one or more charging stations: determining a charging time period associated with the variable load; performing a load flow analysis on a model of the distribution network based on a power usage schedule for existing loads to be charged in the distribution network during the charging time period; Based on the result of the load flow analysis, determining a charging station at one of the plurality of nodes in the distribution network, at which the variable load is to be charged; as well as The variable load is scheduled to be charged at the determined charging station during the charging time period.

2. The method according to claim 1, further comprising: The at least one hardware processor is used to control the determined charging station to output power to the variable load during the charging time period.

3. The method according to claim 1, wherein: The variable load is an electric vehicle, and wherein the power distribution network includes a charging bay for the electric vehicle.

4. The method according to claim 1, wherein: The results of the load flow analysis include an indication of whether a voltage violation will occur.

5. The method according to claim 4, wherein: The voltage violation is a violation of a grid code which defines voltage requirements that the power distribution network must meet.

6. The method according to claim 1, further comprising: The at least one hardware processor is used to exclude any one of the plurality of nodes that will exceed a limit from determining a charging station to charge the variable load when the results of the load flow analysis indicate that a limit will be exceeded.

7. The method according to claim 6, wherein: The over-limit includes under-voltage.

8. The method according to claim 1, wherein: Determining the charging time period includes: receiving a schedule associated with the variable load; and The charging time period is derived from a schedule associated with the variable load.

9. The method according to claim 8, wherein: The variable load is an electric vehicle, wherein the distribution network includes a charging bay for the electric vehicle, and wherein the schedule associated with the electric vehicle includes a time when the electric vehicle is scheduled to leave the charging bay.

10. The method according to claim 1, wherein: Determining a charging station for charging the variable load includes: determining whether the variable load requires fast charging based on the charging time period; and Based on the determination of whether the variable load requires fast charging, a charging station is selected as the determined charging station.

11. The method according to claim 10, wherein: Selecting the charging station includes: when determining that the variable load requires fast charging: determining whether at least one fast charging station is available during the charging time period; and When it is determined that at least one fast charging station is available during the charging time period, a fast charging station available during the charging time period is selected from the at least one fast charging station as the determined charging station.

12. The method according to claim 11, wherein: Selecting the fast charging station includes, when a plurality of fast charging stations are available at two or more of the plurality of nodes, selecting a fast charging station at one of the two or more nodes having a highest voltage among the two or more nodes as the determined charging station.

13. The method according to claim 11, wherein: Selecting the charging station further includes, when it is determined that no fast charging station is available during the charging time period, selecting a charging station at one of the plurality of nodes as the determined charging station, the node having a highest voltage among the plurality of nodes within the load flow analysis.

14. The method according to claim 10, wherein: Selecting the charging station includes, when it is determined that the variable load does not require fast charging, selecting a charging station at one of the plurality of nodes as the determined charging station, the node having a highest voltage among the plurality of nodes within the load flow analysis.

15. The method according to claim 1, wherein: The power distribution network includes one or more distributed energy resources, and wherein determining a charging station to charge the variable load includes: in each of one or more iterations until it is determined that a limit violation will not occur: selecting a node among the plurality of nodes to charge the variable load, wherein a different node among the plurality of nodes is selected in each iteration; performing economic dispatch of the distribution network; performing the load flow analysis on a model of the distribution network based on scheduling the use of existing loads in the distribution network to be charged during the charging time period and charging of the variable loads at selected nodes; and A determination is made based on the load flow analysis whether the limit crossing will occur.

16. The method according to claim 15, wherein: The limit violation includes an undervoltage at a selected node.

17. The method according to claim 15, wherein: The power schedule includes set points for one or more of the plurality of nodes in the power distribution network, and the load flow analysis is performed for each of the set points in the power schedule.

18. The method according to claim 15, wherein: The one or more distributed energy resources include one or more of a photovoltaic generator, a wind turbine, a fuel cell, a thermal power plant, a hydroelectric power plant, a gasoline generator, or a battery.

19. An energy management system, comprising: at least one hardware processor; as well as Software configured to, when executed by the at least one hardware processor, perform the following operations on at least one variable load to be charged in a power distribution network comprising a plurality of nodes, wherein each of the plurality of nodes comprises one or more charging stations: determining a charging time period associated with the variable load, performing a load flow analysis on a model of the distribution network based on a power usage schedule for existing loads to be charged in the distribution network during the charging time period, determining, based on the results of the load flow analysis, a charging station at one of the plurality of nodes in the distribution network, at which the variable load is to be charged, and The variable load is scheduled to be charged at the determined charging station during the charging time period.

20. A non-transitory computer readable medium having stored thereon instructions, wherein: The instructions, when executed by a processor, cause the processor to perform the following operations on at least one variable load to be charged in a power distribution network including a plurality of nodes, wherein each node of the plurality of nodes includes one or more charging stations: determining a charging time period associated with the variable load; performing a load flow analysis on a model of the distribution network based on a power usage schedule for existing loads to be charged in the distribution network during the charging time period; Based on the result of the load flow analysis, determining a charging station at one of the plurality of nodes in the distribution network, at which the variable load is to be charged; and The variable load is scheduled to be charged at the determined charging station during the charging time period.

Images