Battery discharge system

Abstract

Various systems and methods are presented for discharging electrical energy from a battery pack, where electrical energy can be discharged via a battery discharge system to a receiver system, such as a microgrid, grid, vehicle, or other suitable system configured to receive / store electrical energy. The battery pack may be discharged to facilitate testing of the battery pack. Discharge of the battery pack may be shared to a single receiver system or by two or more receiver systems. Discharging may be based on factors such as available receiving systems, time, power payment / compensation, and the like. Discharging may also be selected according to user preferences (e.g., a previous selection of a previous discharging operation). The discharges may be prioritized, for example, when a grid emergency occurs in the grid, the released electrical energy will be directed to the grid to assist the grid in recovering from the grid emergency.

Description

Technical Field

[0001] This application relates to enabling a battery pack to discharge to selected sources such as microgrids, vehicles, power grids, and the like. Background Technology

[0002] In order for the battery pack to be tested, the corresponding batteries in the battery pack may have to be depleted. In the example operating scenario, the battery pack may be depleted depending on the operation of the vehicle, device, etc., that includes the battery pack.

[0003] The background above is intended to provide only a contextual overview of the current problem and is not intended to be exhaustive. Further contextual information will become clearer by reading the following detailed description. Summary of the Invention

[0004] The following summary is presented to provide a basic understanding of one or more embodiments described herein. This summary is not intended to identify key or essential elements, or to depict any scope of different embodiments and / or any scope of the claims. The sole purpose of the summary is to present some concepts in a simplified form as a prelude to the more detailed description presented herein.

[0005] In one or more embodiments described herein, systems, apparatuses, computer-implemented methods, approaches, devices, and / or computer program products are proposed to facilitate the release of energy from a battery pack to a receiver system. In some embodiments, the battery pack may be airborne and positioned on a vehicle.

[0006] According to one or more embodiments, the system may include a memory storing computer-executable components and a processor executing the computer-executable components stored in the memory. The computer-executable components may include a battery discharge component configured to determine an amount of excess energy available for discharge from a battery pack, further determine at least one receiver system for the excess energy, and further control the transfer of excess energy from the battery pack to the at least one receiver system. In one embodiment, the battery may include at least one battery cell.

[0007] In one embodiment, at least one receiver system may include one of a microgrid, an onboard battery pack located on a vehicle, a wide-area synchronous grid, or other energy storage devices configured to receive electrical energy.

[0008] In one embodiment, the battery discharge component may also be configured to determine the operating status of the at least one receiver system.

[0009] In one embodiment, when the receiving system is a wide-area synchronous grid, the battery discharge component can also be configured to determine the operating status of the wide-area synchronous grid and, in response to determining that the wide-area synchronous grid is in a grid emergency, select the wide-area synchronous grid as the receiving system for excess energy.

[0010] In another embodiment, the battery discharge component may also be configured to further determine whether the wide-area synchronous grid is currently in a grid emergency, and in response to determining that the wide-area synchronous grid is not currently in a grid emergency, terminate the release of excess energy to the wide-area synchronous grid.

[0011] In another embodiment, the battery discharge assembly may also be configured to determine discharge parameters to be met during discharge operation, wherein the discharge parameters may include thermal conditions, voltage conditions, current, impedance, grid code, specifications or regulations, and to control the discharge of excess energy based on the discharge parameters.

[0012] In another embodiment, the system may further include a presentation component configured to present an option list to prioritize the selection of receiver systems, determine the option selected from the option list, further sort the receiver systems based on the selected options, and further present the receiver systems based on the sorting based on the selected options.

[0013] In another embodiment, the presentation component may also be configured to: (a) present a set of inputs, wherein the set of inputs facilitates the selection of a corresponding portion of excess energy to be released into a respective receiver system of at least one receiver system; (b) receive a first input regarding a first portion of excess energy to be released into a first receiver system; (c) receive a second input regarding a second portion of excess energy to be released into a second receiver system; and wherein the discharge component is further configured to: (a) control the release of the first portion of excess energy into the first receiver system; and (b) control the release of the second portion of excess energy into the second receiver system.

[0014] In one embodiment, the battery pack can be configured to be implemented in an electric vehicle and to provide power to the electric vehicle.

[0015] In other embodiments, the elements described in connection with the disclosed system may be embodied in various forms, such as computer-implemented methods, computer program products, or other forms. For example, in an embodiment, the computer-implemented method may be performed by a device operatively coupled to a processor, wherein the computer-implemented method may include determining, by the device, an amount of excess energy to be released from the battery pack, further determining, by the device, a set of receiver systems available for receiving the excess energy, and further controlling, by the device, the release of the excess energy to at least one receiver system in the set of receiver systems.

[0016] In an embodiment, the battery pack may include at least one battery cell, and at least one receiver system may include one of a microgrid, an onboard battery pack located on a vehicle, a wide-area synchronous grid, or other energy storage devices configured to receive electrical energy.

[0017] In another embodiment, the battery pack may be mounted on the vehicle and configured to provide power to the vehicle.

[0018] In another embodiment, the computer-implemented method may further include: presenting a list of options by the device for prioritizing the selection of receiver systems; further determining the options selected from the list by the device; further prioritizing the receiver systems by the device based on the selected options; further presenting the receiver systems by the device according to the prioritization based on the selected options; and further receiving the selected receiver systems by the device to receive excess energy.

[0019] In another embodiment, when the receiver system is a wide-area synchronous power grid, the computer-implemented method may further include the device determining the operating status of the wide-area synchronous power grid, and in response to determining that the wide-area synchronous power grid is in a grid emergency, the device selecting the wide-area synchronous power grid as the receiver system for excess energy.

[0020] Another embodiment may include a computer program product comprising a computer-readable storage medium having program instructions embodied therein to enable the release of excess energy from a battery pack. The program instructions are executable by a processor and may enable the processor to determine the amount of excess energy to be released from the battery pack, further determine a set of receiver systems available for receiving the excess energy, and further control the release of the excess energy to at least one receiver system in the set of receiver systems.

[0021] In another embodiment, the program instructions may also be executed by the processor to cause the processor to: (s) present a list of options for prioritizing the selection of receiver systems, (b) determine the option to be selected from the list of options, (c) sort the receiver systems based on the selected options, (d) present the receiver systems according to the sorting based on the selected options, and (e) receive an input instructing the selected receiver system to receive excess energy.

[0022] In another embodiment, the at least one receiver system may include a microgrid, an onboard battery pack located on a vehicle, a wide-area synchronous power grid, or other energy storage devices configured to receive electrical energy.

[0023] In another embodiment, the battery pack can be configured to provide electrical power to the vehicle.

[0024] In another embodiment, when the receiving system is a wide-area synchronous power grid, program instructions may also be executed by the processor to cause the processor to determine the operating status of the wide-area synchronous power grid, and in response to determining that the wide-area synchronous power grid is in a grid emergency, select the wide-area synchronous power grid as the receiver system for excess energy. Attached Figure Description

[0025] One or more embodiments are described below with reference to the accompanying drawings in the Detailed Description section.

[0026] Figure 1A A system is shown according to at least one embodiment, including various components and devices configured to realize, monitor and / or control the release of excess energy from a battery pack.

[0027] Figure 1B A system comprising various components and devices configured to realize, monitor and / or control the release of excess energy from a battery pack is further illustrated according to at least one embodiment.

[0028] Figure 2 A schematic diagram illustrating an example configuration of a first EV releasing power to a second EV according to one embodiment is presented.

[0029] Figure 3A An example of a screen / display that enables the selection of one or more energy receivers according to one embodiment is presented.

[0030] Figure 3B An example of a screen / display during a power grid emergency, according to one embodiment, is presented.

[0031] Figure 4 A flowchart is presented showing a computer-implemented method for releasing power from a battery pack according to one embodiment.

[0032] Figure 5 A flowchart is presented showing a computer-implemented method for prioritizing battery pack discharge according to one embodiment.

[0033] Figure 6 A flowchart is presented showing a computer-implemented method for recommending a battery pack discharge receiver / process according to one embodiment.

[0034] Figure 7 A flowchart is presented showing a computer-implemented method for prioritizing battery pack discharge according to one embodiment.

[0035] Figure 8A flowchart is presented, according to one embodiment, of a computer-implemented method for releasing excess energy from a battery pack to one or more receiver systems.

[0036] Figure 9 This is a block diagram illustrating an example computing environment in which the various embodiments described herein can be implemented.

[0037] Figure 10 This is a block diagram illustrating an example computing environment with which the disclosed subject matter can interact according to one embodiment. Detailed Implementation

[0038] The following detailed descriptions are illustrative only and are not intended to limit the embodiments and / or their application or use. Furthermore, they are not intended to be construed as being limited by any express or implied information presented in any of the foregoing Background, Summary, Detailed Description, and / or Summary sections.

[0039] One or more embodiments will now be described with reference to the accompanying drawings, in which similar reference numerals are used throughout to refer to similar elements. In the following description, numerous specific details are set forth for purposes of explanation in order to provide a more complete understanding of one or more embodiments. However, it will be apparent in various cases that one or more embodiments may be practiced without these specific details.

[0040] As used herein, “data” may include metadata. Furthermore, the range An is used herein to indicate a plurality of corresponding devices, components, signals, etc., where n is any positive integer.

[0041] In the various embodiments presented herein, the disclosed subject matter may relate to the construction and implementation of a battery discharge system (BDS) configured to release energy from a battery pack. In one embodiment, instead of relying on the normal operation (e.g., vehicle operation) of devices (e.g., battery packs onboard in a vehicle, battery packs included in a generator system, battery packs used as storage systems in wind turbines / solar systems, and the like) to naturally deplete the battery pack, the BDS may be utilized to deplete the battery pack. Furthermore, instead of depleting the battery pack in a normal usage manner (e.g., vehicle operation), the BDS may be configured to rapidly deplete the battery pack, such that the energy depletion operation can be completed in a shorter time period than that achievable by depleting the battery pack via normal operation.

[0042] the term

[0043] Backend System: A centralized system that communicates with the EV, EVSE, DSO, grid operator, charging point operator, and any of the like. In one embodiment, the backend system authorizes / approves the BDS to implement the appropriate grid code / parameter / specification of the grid / DSO at the vehicle-to-grid (V2G) operation location. The backend system can be configured to receive grid code / parameter / specification from the grid / DSO and forward it to the BDS. The backend system can control / authorize whether the BDS can perform V2G operations (multiple lines of V2G operations) at the current location / EVSE. The backend system may be a "cloud-based" system. The backend system may be operated by a third party authorized by the EV owner, the EV's original equipment manufacturer (OEM), fleet owners, rental vehicle owners, and such. Although not shown, the backend system may be included in the battery discharge system (BDS).

[0044] Battery pack: May include any medium / device for storing / releasing electrical energy. A battery pack may include a single battery cell, a group / set / collection of battery cells electrically connected / coupled together, a battery pack comprising two or more electrically coupled battery modules (where a battery module is formed by one or more battery cells), and any of the like. The terms battery cell, battery pack, battery module, and the like are used interchangeably herein. As further described, a battery pack may be a standalone device, such as a portable battery, which can be easily connected / disconnected to / from the device to which the battery pack is to provide power, up to an onboard battery pack located on a system (e.g., an EV), where the battery pack can provide electrical energy to the system and also receive electrical energy from the system. In an example scenario of operation / use, the battery pack may be onboard located on a vehicle, where removal / testing of the battery pack may be complex.

[0045] BEV: Battery Electric Vehicle.

[0046] BPT: Bidirectional power transfer, such as grid to EV / BDS, EV / BDS to grid, and the like.

[0047] DER: Distributed Energy Sources, which are small generating units that operate locally and are connected to the larger power grid at the distribution level. DERs can include electric vehicles, solar panels, etc.

[0048] DSO: Distribution System Operator, which is a company that distributes electricity to a given operating area. A first DSO operating across a first area may be permitted access to the energy grid (e.g., via a first billable account), while a second DSO operating in a second area may be permitted access to the same energy grid (e.g., via a second billable account). For example, more than a thousand DSOs operate in Europe and are able to feed energy back to the grid in their operating areas. EVs / BDSs operating as generators must be certified / compliant with any grid code / specification applicable to the area, and approval is also required for the DSO to provide grid access in that area. The terms "physical DSO" and "TSO" are used interchangeably herein.

[0049] EV: Electric vehicle, for example, having an onboard battery pack that includes a set of battery cells / cells.

[0050] EVSE: Electric Vehicle Power Supply Equipment, comprising: conductors, including phase conductors (multiphase conductors), neutral conductors and protective grounding conductors; BDS couplers; attached plugs; and all other accessories, devices, power outlets or specially installed equipment for the location / site transfer of energy between the BDS and the grid, and further enabling communication / data transfer between the BDS, the grid, the DSO, back-end systems and such as as needed during battery discharge operation.

[0051] Grid Code: A grid code is a technical specification that defines one or more operating conditions / parameters that systems connected to a grid (e.g., a public grid) must meet to ensure the safe, robust, and economical functioning of the grid, infrastructure, and / or connected systems. This system can be a power plant, an EV used as a power source / generator, a BDS, a consumer, or another network. Grid codes are assigned by agencies responsible for system integrity and network operation (e.g., grid operators, DSOs, TSOs). The interpretation of grid codes typically involves representatives of the network operator (DSO, TSO), users, and regulatory agencies, and varies across countries.

[0052] IEC: International Electrotechnical Commission (Commissionélectrotechnique internationale) is a Swiss-based international standards organization for electronic, electrical, electronic and related technologies.

[0053] ISO: International Organization for Standardization, a Swiss-based organization that develops standards for a wide range of industries, including food safety, healthcare, and the like.

[0054] Observation Time: During the initial phase of interaction and communication between the Battery Discharge System (BDS) and the power grid, as part of the BPT operation where the BDS is used as an energy source for the grid, an observation time needs to be met / expired before the BDS can perform power transfer (e.g., as defined in EN 50549-1). Communication between the BDS, EVSE, and the grid is specified, for example, by ISO 15118. During the observation time, the BDS, EVSE, and / or the grid can perform functions such as exchanging relevant technical information / parameters / data / limitations regarding the BPT (charging / discharging), and verifying that the corresponding operating conditions (e.g., frequency, voltage, power gradient, impedance, and the like) are required for energy transfer between the BDS, EVSE, and the grid without damaging, for example, the batteries attached to the BDS or the grid infrastructure / components. For example, the observation time can be used to ensure that the grid does not experience a grid emergency.

[0055] PHEV: Plug-in hybrid electric vehicle.

[0056] Third-party setpoint: This refers to the setting / adjustment of grid codes, specifications, regulations, and similar parameters. It can be provided by any entity associated with BDS, EVSE, the grid, etc., including, in the non-restricted list: DSO, charging point operators, entities associated with back-end systems, OEMs, home energy management systems, energy aggregators, energy flexibility providers, representatives of BDS owners / operators, and the like.

[0057] TSO: Transmission system operator, which is an entity entrusted with transmitting electricity through the power grid between a power source and a local distribution point (e.g., EVSE), and in the case of BPT, from the local distribution point (e.g., to which the BDS is connected) to the power source. TSO is also known as Independent System Operator (ISO), Regional Transmission Organization (RTO), and similar terms.

[0058] VDE (Verband der Elektrotechnik, Elektronik und Informationstechnik, an organization for electrical, electronic and information technology) is a German-based technical standards association responsible for developing electrical safety standards. VDE performs standardization work, product testing, and product certification.

[0059] Standards / Specifications / Regulations

[0060] It should be understood that while the following presents the relevant specifications / regulations for energy transfer during BPT operation of EVs connected to the grid, various embodiments are not limited thereto and the various embodiments presented herein can be used with any applicable specifications / regulations / grid codes.

[0061] A. ISO 15118

[0062] ISO 15118 Road Transport Vehicles is a specification concerning communication (multiple communications) between EVs and EVSEs. According to ISO 15118, EVs include BEVs and PHEVs. ISO 15118 details the communication between the Electric Vehicle Communication Controller (EVCC) (e.g., located on the EV) and the Power Supply Equipment Communication Controller (SECC) (e.g., located on the EVSE) and equipment at the grid / DSO. Communication between EVs, EVSEs, DSOs, etc., enables the identification / sharing of one or more specifications, regulations, grid codes, etc. (and associated parameters such as power limits, power values, charging circuit settings, and the like) for a specific location of the EV (e.g., as part of V2G operation). In one aspect, the BDS can function as an EV.

[0063] B.VDE-AR-n4105

[0064] Specification VDE-AR-n4105 relates to power generation systems connected to low-voltage distribution networks / grids, and in particular, provides minimum technical requirements for connection to and operation in parallel with low-voltage distribution networks.

[0065] C.EN 50549-1

[0066] Standard EN 50549-1 details the requirements for parallel connections between power plants and distribution networks / grids. Furthermore, Part 1 addresses low-voltage (LV) distribution networks, particularly connections up to and including type B power plants. To comply with EN 50549-1, the corresponding systems presented herein may include any necessary equipment / components / devices, such as hardware that may be required, including digital inputs / interfaces with the EVSE (e.g., in the BDS), whereby the digital inputs may be hardware digital inputs and / or inputs received directly from back-end systems, and the like. A digital interface (e.g., operated by the DSO) may be provided between the EV and the grid, enabling discharge commands and the like to be received at the EVSE to allow the EV's V2G operation to comply with the EN 50549 grid requirements, for example, enabling the EV to be certified as a generator under EN 50549. In one embodiment, the BDS may function as the EV.

[0067] D. ISO 3166-1 and 3166-2

[0068] ISO 3166-1 and ISO 3166-2 can be used to identify the location of EVs, EVSEs, BDSs, and / or energy grids, where the location can be based on codes identifying the corresponding country, region, sub-region, subdivision (e.g., province or state), etc., wherein ISO 3166-2 is referred to as the code for indicating the name of the country and its subdivisions - Part Two: Country Subdivision Code. In one aspect, Global Positioning System (GPS) coordinates / information regarding the location of EVs, EVSEs, energy grids, etc., can be used to determine the corresponding location according to ISO 3166-1 and 3166-2. In one embodiment, a BDS can function as an EV.

[0069] E.IEC 61851-1

[0070] IEC 61851 is a standard relating to conductive charging systems for electric vehicles. IEC 61851 addresses the hardware requirements for connections from the EV to the EVSE, and can thus be extended to comply with relevant grid specifications / requirements for EVs operating as energy sources, such as limiting active discharge power based on a received setpoint (e.g., in signals received from the DSO), digital I / O, or cloud backend to receive signals from the DSO. In one embodiment, the BDS can function as an EV.

[0071] The various embodiments presented herein can be used to control the discharge of any battery, which may be positioned on a vehicle, military vehicle, rail vehicle, marine vehicle (such as a small boat, transport ship, submarine, or marine drone), winged vehicle (such as an airplane or drone), and / or rotorcraft vehicle (such as a helicopter or drone). Similarly, one or more embodiments presented herein can be extended to control the charging of batteries positioned on robots and / or any suitable mobile or stationary device. Other applicable applications include scooters, electric balance scooters, etc. Electric bicycles, electric tricycles (E-rickshaws), and the like. Furthermore, one or more embodiments presented herein can be used to control the charging of a battery, wherein the battery is a separate device, for example, the battery is not located on a vehicle, device, etc.

[0072] Furthermore, the embodiments can be applied to any vehicle utilizing a battery discharge system, such as a battery electric vehicle (BEV) where the power unit is solely an electric motor powered by a battery, and the battery is recharged via an external charging station; a hybrid electric vehicle (HEV) having both a gasoline / gasoline engine and a fuel tank and an electric motor powered by a battery, wherein the operation of the HEV recharges the battery (e.g., via a regenerative braking system that captures kinetic energy); a plug-in hybrid electric vehicle (PHEV) having both a gasoline / gasoline engine and a fuel tank and an electric motor powered by a battery, wherein the battery can be charged via an external charging station; and the like.

[0073] It should be understood that although various embodiments and concepts are presented for lithium-ion battery technology, these embodiments and concepts can also be applied to any battery technology, including battery cells containing lithium-ion (Li-ion), lithium nickel cobalt aluminum (NCA), lithium nickel manganese cobalt (NMC), lithium manganese spinel (LMO), lithium titanate (LTO), lithium iron phosphate (LFP), lithium metal polymer (LMP), nickel manganese cobalt (NMC), nickel metal hydride (Ni-MH), lithium sulfur (Li-S), lead-acid batteries, as well as supercapacitors, supercapacitors, chemical batteries, solid-state batteries, fuel cells, etc.

[0074] Battery Health

[0075] The operational condition of a battery pack may be of concern based on an assessment of its battery cell / cell operational degradation. Operational degradation can be largely described by two terms: (a) charge cycle decay (cycle aging) and (b) calendar aging. Charge cycle decay is the operational degradation of a battery pack resulting from corresponding charge and discharge operations throughout its entire lifespan. Calendar aging is the deterioration that occurs during the operational lifespan of the battery pack, even when the battery pack is not in use, and due to environmental factors such as operating the battery pack at temperatures above or below its optimal operating temperature. Degraded modules can adversely affect the operational health of other modules in the battery pack due to degradation of module electrical coupling, rather than module isolation.

[0076] Regarding the assessment of a battery pack's operating condition / health, the State of Charge (SOC) and State of Health (SOH) generally provide indicators of the battery pack's ability to store and release energy in a controlled manner. Different algorithms can be used to determine the SOC of a battery pack, utilizing measurements such as voltage, current, charge profiles, and discharge profiles. These algorithms (e.g., offline and / or indirect) include coulomb counting (the ratio of the module's total charge input to its maximum capacity), ampere-hours (Ah), open-circuit voltage (OCV), impedance / impedance ratio measurements, chemistry, voltage, current integration, and similar methods. Furthermore, machine learning-based algorithms such as neural networks, fuzzy logic, and support vector machines can be used. Another technique is the estimation using a state-space model with a Kalman filter.

[0077] According to Equation 1, using the Coulomb counting method:

[0078] SOC = Total charge input / Maximum capacity of the module (Equation 1)

[0079] The total charge input is based on current and time; however, the current can vary over time, which can be corrected, for example, by mathematical integration. Furthermore, the module's maximum capacity can vary over time.

[0080] The converse of SOC is Depth of Discharge (DOD), which indicates the percentage of charge already consumed in the battery pack / module. SOC is typically referenced when considering the module's current state of charge, while DOD is typically referenced when considering the module's lifetime after repeated use.

[0081] Over time, as the State of Health (SOH) decreases, the operating range of a battery-powered system decreases; for example, the range of EVs per charge also decreases. SOH can be based on module capacity, module charge, internal resistance, and similar factors. SOH can also be determined based on the number of charge / discharge cycles, operational life, and operational performance of the respective module and battery.

[0082] In one approach, the SOH can be determined using the ratio between the current maximum storable capacity and the module's rated capacity, according to Equation 2:

[0083]

[0084] Where C aged It is the maximum module capacity that the battery pack / module can currently store, while C rated This is the module's rated capacity. In an example scenario, when the SOH percentage drops to 70%, the lithium-ion battery module is considered to be faulty and should be replaced. Therefore, as the module's SOH percentage changes, the module's operational health condition changes from "good" (e.g., SOH = 100%) to "bad" (e.g., SOH = 70%).

[0085] To facilitate the determination of SOC, DOD, SOH, and operational health of battery packs / modules under various operating conditions, various mathematical models (e.g., through artificial intelligence components) can be utilized. Models can be operated using parameters such as charging voltage and current profiles, discharging voltage and current profiles, operating load, age, temperature, and similar parameters. Any suitable model can be used to determine SOC, DOD, SOH, etc., including, in the non-limiting list, lumped-parameter models, equivalent circuit models, electrochemical models, convolutional neural networks (CNNs), long short-term memory (LSTM) based on dropout regularized fully connected layers, and temporal convolutional memory neural networks (TCMNNs) combining CNNs and LSTMs, etc.

[0086] It should be understood that while the various embodiments presented herein relate to discharging the battery pack in preparation for battery health testing (e.g., SOC, SOH, capacity, and the like), these embodiments can also be applied to discharging electrical energy used while the battery pack is undergoing testing.

[0087] Battery discharge system

[0088] Now turn to the attached image. Figure 1A A system 100A according to at least one embodiment is illustrated. The system 100A includes various components and means configured to discharge a battery pack, and further provides selection of various battery discharge / depletion options. As shown, the system 100A includes a battery pack 105 connected to a battery discharge system (BDS) 110. The battery pack 105 may include any medium / device for storing / releasing discharged energy. In a non-limiting list of examples, the battery pack 105 may include a single battery cell, a battery pack comprising a group / set / collection of battery cells / modules electrically connected / coupled together, and any of the like, to facilitate the supply of electrical energy to systems, devices, equipment, and the like.

[0089] As further described, battery pack 105 can currently store excess energy 107 in its volume / amount. Excess energy 107 can be further referred to as excess energy 107A-n, wherein a first portion 107A of excess energy 107 can be released to a first receiver (e.g., microgrid 150), and a second portion 107B of excess energy 107 can be released to a second receiver (e.g., grid 160). Furthermore, battery state 108A-n information / data regarding the current operating state of battery pack 105 can be determined (e.g., via discharge assembly 120), wherein battery state 108A-n can indicate the electrochemical state of battery pack 105, the physical state of battery pack 105, etc. Battery state 108A-n can be used to determine, for example, how much excess energy 107A-n is available at battery pack 105, the discharge rate of excess energy 107A-n that can be utilized at battery pack 105 (e.g., by BDS 110) without physically / chemically damaging battery pack 105, etc.

[0090] BDS110 can be further connected to a series / groups / sets / collections of energy receiver systems / storages 163A-n (also referred to as receiver systems), such as microgrid 150, vehicle 155, grid 160, other energy receivers 162, etc. For readability, the various energy receivers / receiver systems / storages are grouped together under the general term receiver system 163A-n, where the application of the term "receiver system 163A-n" herein includes one or more of microgrid 150, vehicle 155, grid 160, other energy receivers 162, etc. Microgrid 150 can be a local grid, for example, located at a facility where the discharge and testing of battery pack 105 is performed, co-located with BDS110. Microgrid 150 can be configured to operate in isolation from extended / regional grid 160, such that microgrid 150 can operate in "island mode" and be electrically coupled to grid 160. Therefore, microgrid 150 can be configured to store electrical energy and supply it to equipment / systems / devices located / operable at the facility. Vehicle 155 may be an EV powered by an onboard battery pack (e.g., which may be equivalent to battery pack 105) located on vehicle 155. Grid 160 may be a large-scale grid, such as a wide-area synchronous grid, thereby serving an area larger than microgrid 150. Other energy receivers 162 may be equipment / systems / devices configured to receive and / or store excess energy 107A-n.

[0091] Storage device 151A-n can be located at any receiver system 163A-n, and storage device 151A-n can be any suitable equipment / system / device configured to receive excess energy 107A-n, such as a battery cell, battery pack, power grid system, etc. (According to...) Figure 1BThe microgrid 150 includes a storage device 151M, the vehicle 155 includes a storage device 151V, the power grid 160 includes a storage device 151G, and other energy receivers 162 include a storage device 151O.

[0092] like Figure 1A As shown, BDS110 may also include a discharge assembly 120, whereby the discharge assembly 120 can be configured to control the operation of the switching assembly 121 to allow excess energy 107A-n to be transferred from the battery pack 105 to one or more receiver systems in the receiver systems 163A-n. Therefore, according to, for example by utilizing the discharge configuration 109A-n, the discharge assembly 120 can control how excess energy 107A-n is released based on the control of the switching assembly 121, wherein the switching assembly 121 can have any suitable configuration, such as a physical switch / system, a digital switch / system, etc.

[0093] As further described, BDS110 can obtain / receive information / data regarding the operational status (receiver status 170A-n) of the respective energy receivers in receiver systems 163A-n. For example, if receiver status 170G indicates that energy grid 160 is experiencing a grid emergency, BDS110 can prioritize receiving excess energy 107 from energy grid 160 to help energy grid 160 recover from the emergency.

[0094] As described above, system 100A may include a discharge assembly 120. The discharge assembly 120 may be configured to analyze battery pack 105 to determine the current battery state 108A-n of battery pack 105. In one aspect, for example, battery state 108A-n may provide a measurement of excess energy 107 to be removed from battery pack 105 to prepare battery pack 105 for test conditions. Battery state 108A-n may also provide the discharge assembly 120 with information about how quickly excess energy 107 can be removed from battery pack 105 without damaging one or more battery cells in battery pack 105.

[0095] The discharge assembly 120 can also be configured to utilize battery states 108A-n, the operating condition of the battery pack 105, the volume of excess energy 107A-n available for discharge, and any parameters, data, values, etc., that can be used by the BDS 110 to configure the discharge of the battery pack 105 through discharge operation / configuration 109A-n. For example, the discharge assembly 120 can be configured to determine the discharge configuration 109A-n of the battery pack 105, wherein the discharge configuration 109A-n can be configured to maximize the discharge rate of excess energy 107A-n while ensuring that no physical / chemical damage is caused to the battery pack 105, for example, in accordance with the thermal regulation, voltage, impedance, power, etc. of the battery pack 105. Similarly, receiver state 170A-n information may include any parameters, data, values, etc., regarding any receiver system 163A-n, to be used by the discharge assembly 120 to configure the discharge operation for the corresponding receiver system 163A-n. For example, discharge assembly 120 can be configured to determine a discharge configuration 109A-n for implementation at the respective receiver system 163A-n, which maximizes the discharge rate of excess energy 107A-n while ensuring no physical damage to the respective receiver system 163A-n, such as meeting the charging voltage / charging rate requirements of the respective receiver system 163A-n. Battery state 108A-n and / or receiver state 170A-n can be determined based on any suitable sensor (not shown) measuring one or more operating conditions at battery pack 105 and / or the respective receiver system 163A-n, wherein the sensor can be configured to measure / monitor pressure, temperature, output voltage / current / capacity, operating / failure conditions of one or more sensors, and any one or more of other relevant issues / sources of concern (in a non-limiting list).

[0096] As further described, BDS110 may further include a computer system 180A, which is configured with memory, a computer processor, etc., as needed to facilitate the operation of BDS110 and its corresponding components (e.g., discharge assembly 120). As further described, the corresponding receiver systems 163A-n may also include computer systems 180B-n and associated processors, memory, etc.

[0097] In one respect, releasing energy 107 from battery pack 105 can be considered equivalent to net metering operations, for example, where the owner of a home-based solar panel / wind turbine system releases excess energy 107A-n generated into the energy grid 160 and receives compensation 104A-n (payment / incentive) for doing so (according to...). Figure 1B ).

[0098] In this embodiment, depending on the energy storage / operation of the battery pack 105 and the operation of the receiver systems 163A-n, excess energy 107 can be released in the form of alternating current (AC), direct current (DC), etc. As further described, the BDS 110 may also include appropriate devices to convert the excess energy 107 into a desired form, such as phase, voltage, etc., as needed, so that the excess energy 107 can be released to any receiver system 163A-n. As further described, the BDS 110 may also include any necessary devices to enable energy 107 to be released from the battery pack 105 to the corresponding energy receiver 163A-n.

[0099] On the other hand, when the battery pack 105 is mounted on a vehicle (e.g., an EV), the release of energy 107 can be considered equivalent to vehicle-to-grid (V2G) operation, whereby the battery pack 105, for example, releases excess energy 107 to the grid 160. In another example where the battery pack 105 is mounted on a vehicle (e.g., an EV), releasing energy 107 to another vehicle 155 can be considered equivalent to vehicle-to-vehicle (V2V) operation, whereby the first battery pack 105A (located on a first EV, not shown) releases excess energy 107 to a second battery pack 105B located on the vehicle 155 (e.g., where the vehicle 155 is a second EV) (e.g., according to...). Figure 2 In another embodiment, where the battery pack 105 is mounted on the vehicle, the discharge from the battery pack 105 to the microgrid 150 can be considered equivalent to vehicle-to-local (V2L) operation. In this embodiment, the other energy receiver system 162 may be a portable device with an onboard battery, such as a laptop computer, whereby the discharge from the battery pack 105 to receiver systems 163A-n is equivalent to vehicle-to-land (V2L) operation.

[0100] More than one discharge configuration 109A-n can be determined / utilized simultaneously. For example, discharge component 120 can utilize a first discharge configuration 109A configured to transfer energy 107 to microgrid 150, while a second discharge configuration 109B can be configured such that grid 160 is given discharge priority with respect to the battery pack 105 in the event of a grid emergency. For example, receiver state 170G indicates that grid 160 is experiencing a grid emergency, and the second discharge configuration 109B is prioritized for grid 160 (e.g., when a grid emergency exists), even if the first discharge configuration 109A is to be implemented by discharge component 120. Once the grid emergency is no longer present, excess energy 107 can be directed to another of the receiver systems 163A-n, such as microgrid 150. Discharge configurations 109A-n can be configured to reflect different prices of energy 107 based on the time of day when energy 107 is available to be supplied to receiver systems 163A-n, discharge rate, etc.

[0101] BDS110 can be located at any suitable location. For example, BDS110 can be located at a battery sales / repair / discharge center, vehicle repair facility, etc. In one embodiment, microgrid 150 can be co-located with BDS110, such that microgrid 150 can be configured to store any discharge energy 107, which can then be used to power a discharge facility. In an example embodiment, as previously described, microgrid 150 can be given priority as a receiver of energy 107A-n, with the intention that microgrid 150 is maintained with as much electrical energy as possible. However, during a grid emergency at grid 160, excess energy 107A-n from battery pack 105 is released into grid 160.

[0102] Go to Figure 1B System 100B provides information about Figure 1A Further details of the corresponding systems, components, devices, etc., are presented below. As shown, a battery pack 105 with excess energy 107 is connected to a BDS 110. The BDS 110 is further connected to one or more receiver systems 163A-n. As previously described, the BDS 110 may also include a discharge assembly 120 configured to analyze the battery state 108A-n, determine the excess energy 107A-n, further determine the receiver state 170A-n of one or more receivers 163A-n, and based thereon, determine a discharge configuration 109A-n to discharge the excess energy 107A-n to one or more receivers 163A-n.

[0103] As shown in the figure, entities 102A-n (e.g., owner, operator, user, etc.) can be associated with battery pack 105 such that, as further described, entities 102A-n can choose how to release excess energy 107A-n to receiver system 163A-n, etc. Account 103A-n can be associated with entity 102 such that account 103A-n can be configured (e.g., from discharge component 120) to receive payments, energy credits, etc., as compensation 104A-n for discharged energy 107A-n (e.g., as presented / selected on screen 310, as further described).

[0104] As further shown, each receiver system 163A-n may include a computer system 180C-n (described further below). As previously mentioned, each receiver system 163A-n may include a storage device 151A-n located at any receiver system 163A-n, whereby the storage device 151A-n can be any suitable equipment / system / device configured to receive excess energy 107A-n, such as a battery cell, battery pack, power grid system, etc. Figure 1B Microgrid 150 includes storage device 151M, vehicle 155 includes storage device 151V, power grid 160 includes storage device 151G, and other energy receivers 162 include storage device 151O. For example... Figure 1B As further shown, each of the receiver systems 163A-n may also include a control component (CC), which, in a non-limiting list, is configured to (a) control the operation of the receiver systems 163A-n to which the BDS110 is connected (e.g., in response to instructions in communications 197A-n with the BDS110), (b) communicate with the BDS110 in communications 197A-n (e.g., data transmission, receiver status 170A-n, etc.), and so on. Corresponding control components include a microgrid control component (MCC) 152M at microgrid 150; a vehicle control component (VCC) 152V at vehicle 155; a grid control component (GCC) 152G at grid 160; and other control components (OCC) 152O at other energy receivers 162; and so on.

[0105] The connections between battery pack 105 and BDS 110, and between BDS 110 and the corresponding receiver systems 163A-n (e.g., via connections 146 and 147), can utilize any desired technology / science, electrical connections, wiring, communication, etc. (e.g., according to the applicable standards / specifications / regulations / grid codes, as previously described). For example, in the case where battery pack 105 is airborne and positioned on vehicle 210 (according to... Figure 2The connection between vehicle 210 / battery pack 105 and BDS 110 can be via charging cable 116A-n, wherein cable 116A-n is connected via plug 117 (e.g., J1772, Combination Charging System (CCS), SAE Combo, Charging Mobility (CHAdeMO)) located at the end of cable 116A-n. The plug 117 is connected to vehicle 210. During charging / discharging, the plug 117 is located in the charging port (charging socket) 118 on vehicle 155, where port 118 is connected to the storage device / battery pack SD151V. Charging of SD151V can be controlled by BDS110 in conjunction with VCC152V (e.g., a battery management system), where VCC152V can be configured to operate in conjunction with computer system 180V, wherein various commands, instructions, data, etc. are transmitted between VCC152V and BDS110 (in communications 197A-n), as further described herein.

[0106] like Figure 1BAs further shown, BDS110 may also include a selection component 130, wherein the selection component 130 can be configured to provide a list 132A-n of options (e.g., according to FIG. 3) for receivers 163A-n that can be used to release excess energy 107 from battery pack 105. The list 132A-n of options can be presented to entity 102A, enabling entity 102A to select receiver systems 163A-n for energy 107. Any suitable selection can be utilized; for example, in a first example scenario, entity 102A can select that 100% of energy 107 will be discharged to a single receiver system, such as 100% of energy 107 being discharged to microgrid 150. In another example scenario, entity 102A can select that energy 107 is discharged to two or more of receiver systems 163A-n, such that entity 102A selects that 60% of energy 107 is discharged to microgrid 150 and 40% of energy 107 is discharged to grid 160. Selection component 130 can also be configured to provide various reasons 350A-n (e.g., according to FIG. 3), considerations, requirements, and similar factors regarding why a particular receiver system 163A-n can be selected, such as the amount of energy compensation 104A-n, the time of day when the receiver system 163A-n provides an increased amount of energy compensation (e.g., night versus day, windy versus cold, etc.), whether a particular receiver system 163A-n should be prioritized (e.g., the power grid 160 is experiencing a power grid emergency), etc. The corresponding reasons 350A-n can be captured as options 132A-n presented to entity 102A via an HMI 186 / display 187 included in / communically coupled to BDS 110. In an exemplary scenario, battery pack 105 may be airborne and positioned on a vehicle (e.g., vehicle 210), where selection component 130 presents the corresponding options 132A-n via an in-vehicle display / infotainment system (e.g., via HMI 186 / display 187, as further described). Entity 102A can be selected from the presented options 132A-n and can initiate / schedule discharge operations for subsequent discharge of energy 107A-n.

[0107] BDS110 may also include a presentation component 131, configured to present on HMI186A the current / previous / available discharge configuration 109A-n, previous / current cause 350A-n, previous / current type / configuration of battery pack 105A-n, previous / current excess energy to be discharged 107A-n, previous / current available receiver system 163A-n, previous / current receiver status 170A-n, historical data 190A-n, and similarity index S. 1-n Any one of the vectors, such as Vn (as further described).

[0108] BDS110 may also include a data history recorder 133, which is configured to utilize information on HMI186 regarding current / previous / available discharge configuration 109A-n, previous / current reasons 350A-n, previous / current type / configuration of battery pack 105A-n, previous / current excess energy to be discharged 107A-n, previous / current available receiver system 163A-n, previous / current receiver status 170A-n, historical data 190A-n, and similarity index S. 1-n Any information such as vector Vn can be used to generate / update historical data 190A-n (as further described). Process components 135 / one or more AI / ML processes 137A-n can utilize historical data 190A-n to determine / recommend potential discharge configurations 109A-n to release excess energy 107A-n.

[0109] Various communications 197A-n can be utilized across BDS110, between BDS110 and battery pack 105, and further between BDS110 and receiver systems 163A-n. Communication 197A-n may include notifications, instructions, selections, options 132A-n, receiver status 170A-n, priority reasons 360A-n, reasons 350A-n, the amount of selected energy 107A-n (e.g., All button 330A-n, slider 340A-n according to Figure 3), etc., generated, for example, as input to entity 102A-n by corresponding components in BDS110, components in any receiver system 163A-n, etc.

[0110] As mentioned, BDS110 may also include corresponding systems to enable the safe release of excess energy 107 to the respective receiver systems 163A-n via switching assembly 121, according to any requirements, standards, etc., which can be in place to enable connection and / or release to the respective receiver systems 163A-n. For example, to facilitate discharge to the grid 160, charge controller 168 may be co-located with switching assembly 121 such that the discharged energy 107A-n is under the desired conditions for discharge to any of the receiver systems 163A-n. Charge controller 168 may include any suitable technology / configuration to achieve the discharge energy 107A-n, such as voltage, current, phase, AC, DC, modulation, impedance, etc., and is also configured to operate according to any desired specifications, standards, etc. For example, the charging controller 168 may include an EVSE system, which can be configured to operate according to any requirements, local grid codes, etc., such as ISO 15118 Road Vehicles, VDE-AR-n4105, EN 50549-1, ISO 3166-1, ISO 3166-2, IEC 61851, applicable grid codes, etc. (e.g., implemented on grid 160).

[0111] like Figure 1B As further shown, BDS110 and receiver systems 163A-n can be communicatively coupled to / include computer systems 180A-n, respectively. For example, computer system 180A is located at BDS110, computer system 180M is located at microgrid 150, computer system 180V is located at vehicle 155, computer system 180G is located at grid 160, and computer system 180O is located at other energy receivers 162 (according to...). Figure 2Computer system 180B is located at the second vehicle 210, etc. The corresponding computer systems 180A-n may include corresponding memories 184A-n, which are configured to store corresponding computer-executable components (e.g., discharge component 120, selection component 130, presentation component 131, data history library 133, process component 135 at BDS 110; MCC 152M at microgrid 150; VCC 152V at vehicle 155; GCC 152G at grid 160; and OCC 152O at other energy receivers 162; etc.), and also include corresponding processors 182A-n, which are configured to execute the computer-executable components stored in memories 184A-n. The memory 184A-n can also be configured to store excess energy 107A-n, battery status 108A-n, receiver status 170A-n, discharge configuration 109A-n, options 132A-n, reasons 350A-n, selected receiver in the options list 132A-n, ALL selection 330A-n, settings 340A-n, reasons 350A-n, communication 197A-n and communication content 197A-n, process 137A-n, historical data 190A-n, and similarity index S. 1-n Any value in vector Vn, etc. (as further described herein).

[0112] According to the various embodiments presented herein, the corresponding computer system 180A-n may also include a human-machine interface (HMI) 186A-n (e.g., a display, a graphical user interface (GUI)), which can be configured to present various information, including current / previous / available discharge configuration 109A-n, previous / current cause 350A-n, previous / current type / configuration of battery pack 105A-n, previous / current excess energy to be discharged 107A-n, previous / current available receiver system 163A-n, previous / current receiver status 170A-n, historical data 190A-n, and similarity index S. 1-n Vectors such as Vn (as further described). The HMI186A-n may include an interactive display / screen 187A-n to present various information.

[0113] Computer system 180A-n may also include I / O components 188A-n for receiving and / or transmitting, respectively, the current / previous / available discharge configuration 109A-n, the previous / current cause 350A-n, the previous / current type / configuration of the battery pack 105A-n, the previous / current excess energy to be discharged 107A-n, the previous / current available receiver system 163A-n, the previous / current receiver status 170A-n, historical data 190A-n, and the similarity index S. 1-nVector Vn, etc. Any suitable technology can be used for the interaction / communication of I / O 188, such as File Transfer Protocol (FTP), Simple Radio Independent (SRS), etc. While the foregoing refers to the computer system 180A operating at BDS 110, the corresponding receiver systems 163A-n may also include the computer systems 180B-n as described above, such that each corresponding computer system 180B-n includes a corresponding processor 182B-n, memory 184B-n, HMI 186B-n, display 187B-n, and I / O 188B-n.

[0114] BDS110 may also include process component 135, which may be configured to implement artificial intelligence (AI) and machine learning (ML) processes 137A-n. It should be understood that process 137A-n may include any AI / ML model / technology / science / architecture for automatically monitoring / controlling the release of excess energy 107A-n between battery pack 105 and receiver system 163A-n. Process component 135 may be used in conjunction with any other components included in BDS110, discharge component 120, selection component 130, etc., to implement process 137A-n and further generate / determine / infer excess energy 107A-n, battery state 108A-n, discharge configuration 109A-n, available receiver system 163A-n, receiver state 170A-n, options 132A-n, reasons 350A-n, settings 340A-n, previous configurations / information in historical data 190A-n, etc. (as further described).

[0115] Figure 2Schematic diagram 200 illustrates an example configuration of a first EV discharging to a second EV according to an embodiment. As shown, the first vehicle 210 may be electrically coupled to BDS 110, wherein vehicle 210 includes a battery pack 105P. As previously described, the second vehicle 155 may also be electrically coupled to BDS 110, wherein the second vehicle 155 is included in one or more receiver systems 163A-n. The energy storage device 151V on vehicle 155 may be a battery pack equivalent to battery pack 105P. In the example embodiment, VCC 152V may include a battery management system (BMS) configured to monitor / control the operation of storage device 151V, monitoring parameters such as voltage, temperature, current, etc., as previously described, to prevent overcharging, overheating, etc. Vehicle 210 may similarly include a controller assembly, VCC 152B, and a computer system 180B. Vehicles 155 and 210 can be connected to BDS 110 via cables 116A-n and plugs 117A-n in ports 118A-n on the respective vehicles 155 and 210. Cables 116A-n, combined with VCC1 152B / VCC152V, enable the establishment / initiation of corresponding communication, handshake, charging protocols, etc. with BDS 110 / discharge assembly 120, so as to enable the release of energy 107A-n from vehicle 210 to vehicle 155.

[0116] Figure 3A Schematic diagram 300A illustrates an example of a screen / display according to an embodiment that enables selection of one or more energy receivers. Various screens 310A-n can utilize any suitable screen configuration to convey a list of options 132A-n and enable selection of one or more receiver systems 163A-n, etc. Screen 310A can be displayed on an HMI 186 / display 187A-n. As previously mentioned, the HMI 186 can be integrated into a BDS 110, incorporated as part of an infotainment system into a vehicle 155 / 210, etc.

[0117] Any suitable screen configuration can be used to convey a corresponding list of options 132A-n for the respective receiver system 163A-n, as well as any information related to the selection of a particular receiver system 163A-n. Information about the respective receiver system 163A-n can be presented as one or more reasons 350A-n, which may include considerations such as: payment / compensation 104A-n for the energy 107A-n provided by the respective receiver system 163A-n; enabling the selection of one or more receiver systems 163A-n (e.g., via button 320A-n); whether all energy 107A-n should go to a particular receiver system 163A-n (e.g., via button 330A-n); the appropriate amount of energy 107A-n to be provided to each selected receiver system 163A-n (e.g., via value slider 340A-n or similar function / feature), and so on.

[0118] like Figure 3A As further illustrated above, various reasons 360A-n can be presented, thereby enabling the initial determination (e.g., by discharge component 120) of whether entity 102 prefers to prioritize available receiver systems 163A-n based on factors such as price 360P, discharge rate 360R (e.g., can the discharge of energy 107A-n be performed while entity 102A waits, or will entity 102A return at a later time?), scheduling time 360T (e.g., can the discharge of energy 107A-n be performed immediately?, should it be scheduled?, etc.), or other concerns 360O of interest to entity 102. The priority reasons 360A-n can be buttons on screen 310, such that when selected, corresponding options can be sorted according to the appropriateness of the selected priority reason 360A-n. Therefore, when price 360P is selected, a first cause 350A related to microgrid 150 can be presented, and a second cause 350E related to energy grid 160 can be presented. The first cause 350A instructs microgrid 150 to pay less than the amount grid 160 pays for energy 107A-n. Therefore, the second cause 350E can be presented in green, while the first cause 350A is presented in amber, allowing entity 102 to easily determine a better payment 104A-n and thus select grid 160 to release energy 107A to it.

[0119] Figure 3BSchematic diagram 300B illustrates an example of a screen / display during a power grid emergency according to an embodiment. Screen 310B may be displayed on HMI 186 / displays 187A-n. As previously described, power grid 160 may be experiencing a power grid emergency, where BDS 110 is configured to prioritize releasing excess energy 107 to power grid 160 to help enable power grid 160 to recover from the power grid emergency. Therefore, messages 370A-n indicating the power grid emergency of power grid 160 and giving power grid 160 a discharge priority can be displayed on screen 310B. For example, approval by entity 102 to release energy 107A-n to power grid 160 can be provided via selecting the “Approve Energy Release” button 375.

[0120] Figure 4 Flowchart 400 presents a computer-implemented method for releasing energy from a battery pack according to an embodiment.

[0121] At 410, the battery pack (e.g., battery pack 105) may be connected to the BDS (e.g., BDS 110).

[0122] At 420, the discharge assembly (e.g., discharge assembly 120) may be configured to assess the current operating condition of the battery pack and is also configured to determine the amount of excess energy (e.g., energy 107A-n) that can be released from the battery pack.

[0123] At 430, the discharge component can also be configured to determine which energy receiver systems (e.g., one or more of energy receivers 163A-n, such as microgrid 150, vehicle 155, grid 160, other energy receivers 162, etc.) are available to receive excess energy released from the battery pack. Information about the available energy receivers (e.g., options 132A-n, reasons 350A-n, and similar lists via screens 310A-n) can be presented.

[0124] At 440, the discharge component can be configured to determine whether more than one receiver system is available. In response to a determination of no, that only one receiver system (e.g., microgrid 150) is available to discharge excess energy to, method 400 can proceed to step 450, whereby the discharge component can begin discharging excess energy to the available receiver system. Method 400 can further proceed to step 498 to complete the discharge.

[0125] At 440, in response to the discharge component determining "yes" that more than one receiver system is available, method 400 can proceed to step 460, whereby the available receivers can be displayed on a screen (e.g., according to example screen 310A).

[0126] At 470, the discharge component can also be configured to receive one or more inputs via the screen. For example, the discharge component can detect which receivers have been selected (e.g., via buttons 320A-n), whether all energy will be released to a single receiver (e.g., via ALL buttons 330A-n), and, for example, the appropriate amount of energy selected to be released to the appropriate receiver when a shared discharge operation is performed (e.g., via sliders 340A-n), etc.

[0127] At 480, the discharge component can be further configured to determine (from the selected input of step 470) whether to perform a shared discharge operation. In response to a determination of "No," indicating that shared discharge has not yet been selected (e.g., one of the ALL buttons has been selected), method 400 can proceed to step 490, whereby the discharge component can be configured to initiate the release of excess energy to the selected receiver. Method 400 can then proceed to step 498 to complete the discharge.

[0128] At 480, in response to a confirmation of "Yes," indicating that shared discharge has been selected (e.g., more than one receiver option button has been selected, e.g., button 320A-n) and / or the corresponding discharge percentage slider has been selected / set to the corresponding discharge amount of energy from the battery pack), method 400 can proceed to step 495, whereby the discharge assembly can be configured to initiate the discharge of excess energy to the selected receiver. In one embodiment, the discharge can be performed to the first receiver, and upon releasing the selected percentage of excess energy, the discharge terminates at the first receiver and initiates the discharge to the second receiver.

[0129] At point 498, when the corresponding discharge operation is performed and excess energy has been released to one or more receiver systems, the discharge can be terminated when the battery pack (e.g., battery pack 105) is under the conditions required for testing (e.g., having the energy level required for testing the battery pack to be tested (e.g., zero, 5% energy, etc.)). In one embodiment, the battery testing system may be included in the BDS for use with the connected battery pack, or the battery testing system may be detached from the BDS. Upon completion of the discharge, a compensation payment (e.g., compensation 104A-n) may be made to the account (e.g., user accounts 103A-n).

[0130] Figure 5 Flowchart 500 presents a computer-implemented method for prioritizing battery pack discharge according to an embodiment.

[0131] At 510, the battery pack (e.g., battery pack 105) may be connected to the BDS (e.g., BDS 110).

[0132] At 520, the discharge assembly (e.g., discharge assembly 120) may be configured to assess the current operating condition of the battery pack and is also configured to determine the amount of excess energy (e.g., energy 107A-n) available for discharge from the battery pack.

[0133] At 530, the discharge component can also be configured to determine which energy receiver systems (e.g., one or more of energy receivers 163A-n, such as microgrid 150, vehicle 155, grid 160, other energy receivers 162, etc.) are available to receive excess energy released from the battery pack. Information about the available energy receivers can be presented (e.g., options 132A-n, reasons 350A-n, and similar lists presented via screens 310A-n).

[0134] At 540, the discharge component can also be configured to determine the current operating condition of the power grid (e.g., grid 160) and whether the grid is experiencing a grid emergency. In response to determining "yes," indicating that the grid is experiencing a grid emergency, method 500 can proceed to step 550, whereby the discharge component can be configured to prioritize the grid for discharging the battery pack and further initiate the discharge of excess energy to the grid. Method 500 can proceed to 590, where the discharge to the grid can be terminated.

[0135] At 540, in response to determining "No", the power grid is not in an emergency, method 500 can proceed to step 560, whereby the available receivers (e.g., via screens 310A-n, a list of options 132A-n, reasons 350A-n, and similar options) can be presented on the screen in conjunction with the corresponding options available for discharge (e.g., microgrid, vehicle, power grid, other systems).

[0136] At 570, the discharge component can also be configured to receive one or more inputs via the screen. For example, the discharge component can detect which receivers have been selected (e.g., via buttons 320A-n), whether all energy will be released to a single receiver (e.g., via ALL buttons 330A-n), and, for example, the appropriate amount of energy selected to be released to the appropriate receiver when a shared discharge operation is performed (e.g., via sliders 340A-n), etc.

[0137] At 580, the discharge component can be configured to initiate the discharge of excess energy to a selected receiver. Method 500 can further proceed to step 590 to complete the discharge and compensation (e.g., compensation 104A-n).

[0138] Figure 6 Flowchart 600 presents a computer-implemented method for recommending a battery pack discharge receiver / process according to an embodiment.

[0139] At 610, the previous discharge history (e.g., historical data 190) of a receiver system (e.g., receiver system 163A-n) that has been previously selected to release excess energy (e.g., energy 107A-n) from a battery pack (e.g., battery pack 105) via a BDS (e.g., BDS 110) can be compiled (e.g., via discharge component 120). For example, the previous discharge may have been directed to a microgrid, or a power grid, or other vehicles, etc.

[0140] At 620, the discharge component can also be configured to determine the currently available receivers (e.g., receiver system 163A-n connected to the BDS), operating status, etc.

[0141] At 630, the discharge assembly can also be configured to compare previous discharge history with currently available receiver systems, the operating condition of currently available receiver systems, the current operating condition of the battery pack, etc. AI and ML technologies (e.g., applicable to process assemblies 135 and processes 137A-n) can be used to assist the discharge assembly in comparing previous discharge history with the current operating condition of the battery pack / available receiver systems, for example, to identify preferred receiver systems, where discharge is based on immediate availability rather than cost, timing, etc.

[0142] At 640, the discharge component (e.g., combining process component 135 and process 137A-n) can be configured to generate a recommendation for one or more receiver systems to release excess energy thereto. In one embodiment, the recommendation can be presented on a display (e.g., HMI 186, display 187).

[0143] Figure 7 Flowchart 700 presents a computer-implemented method for prioritizing battery pack discharge according to an embodiment.

[0144] At 710, information about the corresponding receiver system (e.g., receiver system 163A-n, receiver status 170A-n, etc.) can be obtained / received (e.g., at BDS110).

[0145] At 720, one or more priority reasons (e.g., priority reasons 360A-n) may be presented on a screen (e.g., HMI 186 / display 187) (e.g., via presentation component 131), wherein the one or more priority reasons may be used to help determine / select the receiver system (e.g., receiver system 163A-n) to which excess energy (e.g., excess energy 107A-n) of the battery pack (e.g., battery pack 105) can be released. Any suitable parameters may be used for the one or more priority reasons, thereby in a non-limiting list, such parameters may be the amount of energy paid / compensated (e.g., compensation 104A-n), the time for releasing excess energy, etc.

[0146] At 730, input (e.g., any selected priority reason 360A-n) can be received via the screen (e.g., detected via presentation component 131) (e.g., from entity 102A-n).

[0147] At 740, inputs can be analyzed (e.g., via discharge component 120, presentation component 131), and reasons can be prioritized based on selected inputs, such as ranking the receiver system from high to low based on payment, discharge time, energy credit, etc.

[0148] At 750, the sorted systems can be displayed on the screen in conjunction with associated causes (e.g., cause 360A-n). For example, the first cause associated with the first receiver system, combined with the first payment amount, is displayed in green; the second cause associated with the second receiver system, combined with the second payment amount, is displayed in amber; the third cause associated with the third receiver system, combined with the third payment amount, is displayed in yellow, and so on, where the first payment amount is greater than the second payment amount, and the second payment amount is greater than the third payment amount, and so on. Therefore, it is evident which receiver system provides the highest compensation for excess energy and which receiver system provides the worst compensation, for example, for a given cause.

[0149] At 760, input (e.g., button 320A-n) can be received at a screen (e.g., from entity 102A-n). The input can be a selection of which receiver system has been chosen to receive the released excess energy.

[0150] At 770, the selected options can be implemented, such as (e.g., paying excess energy to account 103A associated with entity 102A-n), (e.g., crediting excess energy to account 103A associated with entity 102A-n), scheduling discharge immediately, as quickly as possible, at a later time, and similar (e.g., as scheduled by discharge component 120).

[0151] At 780, excess energy can be initiated / dispatched (e.g., via discharge component 120) to discharge to the selected receiver system.

[0152] Figure 8 A flowchart 800 presents a computer-implemented method for releasing excess energy from a battery pack to one or more receiver systems according to an embodiment.

[0153] At 810, process 800 may include a system (e.g., BDS 110) including a memory (e.g., memory 184, a computer-readable storage medium having program instructions embodied therein) storing computer-executable components and a processor (e.g., processor 182 for executing program instructions) configured to execute the computer-executable components stored in the memory. The computer-executable components may include a battery discharge component (e.g., battery discharge component 120) configured to determine the amount of excess energy (e.g., excess energy 107A-n) available for discharge from a battery pack (e.g., battery pack 105).

[0154] At 820, the battery discharge assembly can also be configured to determine at least one receiver system (e.g., receiver system 163A-n) for excess energy.

[0155] At 830, the battery discharge assembly can also be configured to control the transfer of excess energy from the battery pack to at least one receiver system.

[0156] Applications / Implementations of AI & ML

[0157] As described above, the various embodiments presented herein can utilize various artificial intelligence / machine learning (AI / ML) models / technologies / architectures (e.g., process component 135 implementing processes 137A-n). AI / ML technologies and techniques can be configured to determine information regarding the release of energy 107A-n from the battery pack 105, to make inferences, predictions, etc. Processes 137A-n may include AI, ML, and inference technologies / technologies that employ probability- and / or statistical analysis to predict or infer actions that an entity expects to automatically perform to execute its various aspects, such as determining battery state 108A-n, determining excess energy 107A-n, determining discharge configuration 109A-n, determining options 132A-n, determining receiver state 170A-n, etc., which, as described above, can be facilitated via an automated classifier system and process.

[0158] As used herein, the terms “prediction,” “inference,” “presumption,” “determination,” etc., generally refer to the process of reasoning or inferring the state of a system, environment, and / or user from a set of observations captured via events and / or data. For example, inference can be used to identify specific contexts or actions, or to generate probability distributions over states. Inference can be probabilistic, i.e., calculating probability distributions over states of interest based on considerations of data and events. Presumption can also refer to techniques used to compose higher-level events from a set of events and / or data. Such presumptions result in the construction of new events or actions from a set of observed events and / or stored event data, regardless of whether the events are closely related in time or whether the events and data come from one or several event and data sources.

[0159] A classifier is a function that maps an input attribute vector x = (x1, x2, x3, x4, xn) to a class label class(x). The classifier can also output the confidence that the input belongs to a class, i.e., f(x) = confidence(class(x)). Such classification can employ probability-based and / or statistical analysis (e.g., considering analytical utility and cost) to predict or infer actions that a user expects to perform automatically (e.g., selecting receiver system 163A-n to release energy 107A-n, etc.).

[0160] Support Vector Machines (SVMs) are an example of classifiers that can be employed. SVMs operate by finding a hypersurface in the space of possible inputs that optimally separates triggering input events from non-triggering events. Intuitively, this makes the classification correct for test data that is close to, but not identical to, the training data. Other directed and undirected model classification methods include, for example, Naive Bayes (…). The classification methods used include Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models that provide different modes of independence. For example, the classification methods used in this paper include statistical regression for developing priority models.

[0161] As will be readily understood from this specification, various embodiments may employ classifiers that are explicitly trained (e.g., via general training data) and implicitly trained (as further described below). For example, an SVM may be configured via a learning or training phase, for example, included within a classifier builder and feature selection module in process component 135. Thus, the classifier can be used to automatically learn and perform multiple functions, including but not limited to determining, according to predetermined criteria, such as selecting receiver systems 163A-n to release energy 107A-n to them.

[0162] In an example embodiment, process 137A-n can be trained / fine-tuned using previously acquired / generated data (e.g., in historical data 190A-n). Fine-tuning of process 137A-n may include applying the current / previous discharge configuration 109A-n / historical data 190A-n to process 137A-n incorporating any current considerations, adjusting process 137A-n accordingly by applying the current / previous discharge configuration 109A-n, such that, for example, the weights in process 137A-n are adjusted by applying the current / previous discharge configuration 109A-n / historical data 190A-n. During training, previous decisions, previous observations, determinations, etc., can be applied to process 137A-n, enabling process 137A-n to be trained with respect to various options available for selection and ultimately select which option for each scenario based on various conditions / situations / scenarios. Therefore, when new information is provided (e.g., the amount of excess energy 107A-n to be released from battery pack 105; receiver systems 163A-n available to receive excess energy 107A-n; operating state 108A-n of battery pack 105; operating state of the corresponding receiver systems 163A-n; previously utilized discharge configuration 109A-n; available and / or (e.g., selected by entity 102) options 132A-n; available and (e.g., selected by entity 102) priority reasons 360A-n; wherein energy 107A-n is shared among receiver systems 163A-n (e.g., via % selector 340A-n), and the corresponding % of energy 107A-n is shared with each selected receiver system 163A-n; etc.), process component 135 can be configured to:

[0163] (a) Using one or more related processes 137A-n,

[0164] (b) Apply / compare current conditions (e.g., the amount of excess energy to be discharged 107A-n, available receiver systems 163A-n, operating state 108A-n of battery 105, operating state 170A-n of the corresponding receiver system 163A-n, etc.) with previous conditions (e.g., in historical data 190A-n), and

[0165] (c) Generate an inference / determination about which of the one or more receiver systems 163A-n the excess energy 107A-n will be released to (e.g., the inferred discharge configuration 109A-n).

[0166] As previously mentioned, process component 135 can be used in conjunction with any component included in BDS 110 (e.g., discharge component 120, selection component 130, presentation component 131, data history library 133, charging controller 168, etc.) to implement process 137A-n.

[0167] It should be understood that the various processes 137A-n and operations presented herein are merely examples of the corresponding AI and ML operations and techniques, and any suitable techniques can be utilized according to the various embodiments presented herein. In example embodiments, process component 135 / process 137A-n can be applied to any of the corresponding previous / current / future battery states 108A-n, excess energy 107A-n, discharge configuration 109A-n, option 132A-n, receiver state 170A-n, historical data 190A-n, etc. Process component 135 / process 137A-n may include a vector component to apply any suitable vectorization technique, such as bag-of-words (BOW) text vectors in an unrestricted list, Euclidean distance, cosine similarity, vector representation of term frequency-inverse document frequency (tf-idf) via capturing term / token frequencies (e.g., common terms across previous / current / future knowledge), neural network embedding layer vector representation of terms / categories (e.g., common terms with different tenses), transformer neural networks, bidirectional and autoregressive transformer (BART) model architectures, bidirectional encoder representation (BERT) models from transformers, long short-term memory network (LSTM) operations, sentence state LSTM (S-LSTM), deep learning algorithms, sequential neural networks, sequential neural networks that implement persistent information, recurrent neural networks (RNN), convolutional neural networks (CNN), neural networks, capsule networks, machine learning algorithms, natural language processing (NLP) techniques, sentiment analysis, bidirectional LSTM (BiLSTM), stacked BiLSTM, regular pattern expression matching, etc. Language models can be formed using highly complex neural networks (e.g., those containing billions of weighted parameters), such as LSTM and BART.

[0168] Therefore, in the embodiments, the implementation of BDS110 and the included / associated components and processes 137A-n enables natural language processing (NLP) (e.g., using vectors) to generate and utilize the proposed discharge configuration 109A-n, wherein the determined discharge configuration 109A-n can be presented on HMI186 / screen 187A-n for entity 102 to view / select.

[0169] During the application process 137A-n, the vector representation V 1-nThis can be applied to any of the previous / current / future battery states 108A-n, excess energy 107A-n, discharge configuration 109A-n, options 132A-n, receiver states 170A-n, historical data 190A-n, etc., such that vector similarity operations (e.g., vector clustering / distance) can be applied to generate suggested discharge configurations 109A-n based on accrued prior knowledge of the generation and implementation of previous discharge configurations 109A-n from historical data 190A-n. The similarity between corresponding information can be determined, for example, based on a threshold (e.g., via a similarity index S). 1-n The threshold reflects the proximity of a first vector generated from information relating to the discharge of excess energy 107A-n to receiver system 163A-n and a second vector generated from information relating to previous discharge configurations 109A-n, thereby enabling, for example, the similarity of one or more proposed discharge configurations 109A-n to be ranked via vector quantization.

[0170] It should be understood that while any of the discharge component 120, selection component 130, presentation component 131, data history library 133, process component 135, etc., can be used as a separate component / independent implementation, the corresponding components and functions can be combined into a single component, such as the discharge component 120 operating as a single high-level component, wherein one or more of the selection component 130, presentation component 131, data history library 133, and presentation component 131 operate as sub-components of the discharge component 120.

[0171] Example operating environment and scenarios

[0172] Next, turn to Figure 9 and Figure 10 This provides a detailed description of the additional context of one or more embodiments described herein in conjunction with Figures 1-8.

[0173] To provide additional context for the various embodiments described herein, Figure 9 The following discussion is intended to provide a brief, general description of a suitable computing environment 900 in which the various embodiments described herein may be implemented. While embodiments have been described above in the general context of computer-executable instructions that can operate on one or more computers, those skilled in the art will recognize that embodiments may also be implemented in combination with other program modules and / or as a combination of hardware and software.

[0174] Typically, program modules include routines, programs, components, data structures, etc., that perform specific tasks or implement specific abstract data types. Furthermore, those skilled in the art will understand that these methods can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, IoT devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, each of which can be operatively coupled to one or more associated devices.

[0175] The embodiments shown herein can also be practiced in a distributed computing environment, where some tasks are performed by remote processing devices linked via a communication network. In a distributed computing environment, program modules can reside in both local and remote memory storage devices.

[0176] Computing devices typically include various media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, these two terms being used interchangeably herein as follows. A computer-readable storage medium or a machine-readable storage medium can be any available storage medium accessible by a computer, and includes volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, a computer-readable storage medium or a machine-readable storage medium can be implemented using any method or technique for storing information such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0177] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, optical disc read-only memory (CD-ROM), digital versatile disc (DVD), Blu-ray disc (BD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible and / or non-transitory media that can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” used herein to describe storage devices, memories, or computer-readable media should be understood to exclude the propagation of transient signals themselves as a modifier, without waiving the rights to all standard storage devices, memories, or computer-readable media that do not only propagate transient signals themselves.

[0178] Computer-readable storage media can be accessed by one or more local or remote computing devices, for example, via access requests, queries or other data retrieval protocols, for various operations concerning the information stored on the media.

[0179] Communication media typically embody computer-readable instructions, data structures, program modules, or other structured or unstructured data in data signals (such as modulated data signals, e.g., carrier waves or other transmission mechanisms), and include any medium for delivering or transmitting information. The term "modulated data signal" or multiple modulated data signals refers to a signal whose one or more characteristics are set or altered in a manner that encodes information in one or more signals. By way of example and not limitation, communication media include wired media, such as wired networks or direct wired connections, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0180] It should be understood that when a component is referred to as being “coupled” to another component, one or more different types of coupling can be described, including but not limited to chemical coupling, communication coupling, electrical coupling, electromagnetic coupling, operational coupling, optical coupling, physical coupling, thermal coupling, and / or another type of coupling. Similarly, it should be understood that when a component is referred to as being “connected” to another component, one or more different types of connection can be described, including but not limited to electrical connection, electromagnetic connection, operational connection, optical connection, physical connection, thermal connection, and / or other types of connection.

[0181] Refer again Figure 9 An example environment 900 for implementing various embodiments of the aspects described herein includes a computer 902, which includes a processing unit 904, system memory 906, and a system bus 908. The system bus 908 couples system components, including but not limited to the system memory 906, to the processing unit 904. The processing unit 904 can be any of a variety of commercially available processors and may include cache memory. Dual microprocessors and other multiprocessor architectures may also be used as the processing unit 904.

[0182] System bus 908 can be any of several types of bus architectures, which can be further interconnected to memory bus (with or without memory controller), peripheral bus, and local bus using any of a variety of commercially available bus architectures. System memory 906 includes ROM 910 and RAM 912. The Basic Input / Output System (BIOS) can be stored in non-volatile memory such as ROM, erasable programmable read-only memory (EPROM), or EEPROM, containing basic routines such as those that help transfer information between components within computer 902 during startup. RAM 912 may also include high-speed RAM, such as static RAM for caching data.

[0183] Computer 902 also includes an internal hard disk drive (HDD) 914 (e.g., EIDE, SATA), one or more external storage devices 916 (e.g., floppy disk drive (FDD) 916, memory stick or flash drive reader, memory card reader, etc.), and an optical disc drive 920 (e.g., capable of reading from or writing to CD-ROMs, DVDs, BDs, etc.). While the internal HDD 914 is shown as residing within computer 902, it can also be configured for external use in a suitable chassis (not shown). Additionally, although not shown in environment 900, a solid-state drive (SSD) may be used in addition to or in place of the HDD 914. The HDD 914, external storage devices 916, and optical disc drive 920 may be connected to system bus 908 via HDD interface 924, external storage interface 926, and optical drive interface 928, respectively. Interface 924 for the external drive implementation may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are envisioned in the embodiments described herein.

[0184] The drive and its associated computer-readable storage medium provide non-volatile storage of data, data structures, computer-executable instructions, etc. For computer 902, the drive and storage medium accommodate the storage of any data in a suitable digital format. Although the above description of computer-readable storage media refers to a corresponding type of storage device, those skilled in the art will understand that other types of computer-readable storage media (whether currently existing or developed in the future) may also be used in the example operating environment, and further, any such storage medium may contain computer-executable instructions for performing the methods described herein.

[0185] Multiple program modules can be stored in the drive and RAM 912, including an operating system 930, one or more application programs 932, other program modules 934, and program data 936. All or part of the operating system, applications, modules, and / or data can also be cached in RAM 912. The systems and methods described herein can be implemented using various commercially available operating systems or combinations of operating systems.

[0186] Computer 902 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate the hardware environment of operating system 930, and the emulated hardware may optionally be different from that of operating system 930. Figure 9The hardware is shown. In such an embodiment, the operating system 930 may include one of a plurality of virtual machines (VMs) hosted at the computer 902. Furthermore, the operating system 930 may provide an operating-time environment, such as a Java operating-time environment or the .NET Framework, for the application 932. An operating-time environment is a consistent execution environment that allows the application 932 to operate on any operating system that includes an operating-time environment. Similarly, the operating system 930 may support containers, and the application 932 may be in the form of a container, which is a lightweight, standalone, executable software package including, for example, code, operating time, system tools, system libraries, and application settings.

[0187] Furthermore, computer 902 may include a security module, such as a Trusted Processing Module (TPM). For example, with a TPM, the boot component hashes the next boot component in time before loading it and waits for the result to match a security value. This process can occur at any layer of the computer 902's code execution stack, for example, at the application execution level or the operating system (OS) kernel level, thus achieving security at any code execution level.

[0188] Users can input commands and information into computer 902 through one or more wired / wireless input devices (e.g., keyboard 938, touchscreen 940, and pointing devices such as mouse 942). Other input devices (not shown) may include microphones, infrared (IR) remote controls, radio frequency (RF) remote controls or other remote controls, joysticks, virtual reality controllers and / or virtual reality headsets, gamepads, styluses, image input devices (e.g., cameras), gesture sensor input devices, visual motion sensor input devices, emotion or face detection devices, biometric input devices (e.g., fingerprint or iris scanners), etc. These and other input devices are typically connected to processing unit 904 via input device interface 944, which can be coupled to system bus 908, but can be connected via other interfaces such as parallel ports, IEEE 1394 serial ports, game ports, USB ports, IR interfaces, etc. Interfaces, etc.

[0189] The monitor 946 or other types of display devices can also be connected to the system bus 908 via an interface such as the video adapter 948. In addition to the monitor 946, the computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

[0190] Computer 902 can operate in a networked environment using logical connections to one or more remote computers (such as remote computer 950) via wired and / or wireless communications. Remote computer 950 can be a workstation, server computer, router, personal computer, laptop computer, microprocessor-based entertainment device, peer-to-peer device, or other public network node, and typically includes many or all of the elements described relative to computer 902, although for simplicity only memory / storage device 952 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 954 and / or a larger network (e.g., a wide area network (WAN) 956). Such LAN and WAN networking environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to global communication networks, such as the Internet.

[0191] When used in a LAN networking environment, computer 902 can connect to local network 954 via a wired and / or wireless communication network interface or adapter 958. Adapter 958 can facilitate wired or wireless communication to LAN 954, which may also include a wireless access point (AP) configured thereon for communicating with adapter 958 in wireless mode.

[0192] When used in a WAN networking environment, computer 902 may include modem 960, or may be connected to a communication server on WAN 956 via other means (such as via the Internet) for establishing communication over WAN 956. Modem 960 (which may be internal or external, wired or wireless) may be connected to system bus 908 via input device interface 944. In a networking environment, program modules depicted relative to computer 902 or parts thereof may be stored in remote memory / storage device 952. It should be understood that the network connection shown is an example, and other means of establishing communication links between computers may be used.

[0193] When used in a LAN or WAN networking environment, in addition to or replacing the external storage device 916 as described above, computer 902 can access cloud storage systems or other network-based storage systems. Typically, the connection between computer 902 and the cloud storage system can be established, for example, via adapter 958 or modem 960 through LAN 954 or WAN 956. When computer 902 is connected to an associated cloud storage system, external storage interface 926 can manage the storage provided by the cloud storage system with the help of adapter 958 and / or modem 960, just like other types of external storage. For example, external storage interface 926 can be configured to provide access to cloud storage sources as if these sources were physically connected to computer 902.

[0194] Computer 902 is operable to communicate with any wireless device or entity operably configured in wireless communication, such as printers, scanners, desktop and / or laptop computers, portable data assistants, communication satellites, any device or location associated with a wirelessly detectable tag (e.g., kiosks, newsstands, store shelves, etc.), and telephones. This can include Wi-Fi and Wireless technology. Therefore, communication can be a predefined structure like a regular network, or simply self-organizing communication between at least two devices.

[0195] The above description includes non-limiting examples of various embodiments. It is certainly not possible to describe every conceivable combination of components or methods for the purpose of describing the disclosed subject matter, and those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. The disclosed subject matter is intended to cover all such changes, modifications, and variations falling within the spirit and scope of the appended claims.

[0196] Now refer to Figure 10 The details of one or more components shown depict an illustrative cloud computing environment 1000. Figure 10 This is a schematic block diagram of a computing environment 1000 with which the disclosed subject can interact. System 1000 includes one or more remote components 1010. Remote components 1010 can be hardware and / or software (e.g., threads, processes, computing devices). In some embodiments, remote component 1010 can be a distributed computer system connected via a communication framework 1040 to a local autoscaling component and / or a program using the resources of the distributed computer system. Communication framework 1040 can include wired network devices, wireless network devices, mobile devices, wearable devices, radio access network devices, gateway devices, femtocell devices, servers, etc.

[0197] System 1000 also includes one or more local components 1020. Local components 1020 may be hardware and / or software (e.g., threads, processes, computing devices). In some embodiments, local components 1020 may include autoscaling components and / or programs that communicate with / use remote resources 1010 and 1020, etc., connected to a remote distributed computing system via a communication framework 1040.

[0198] One possible communication between remote component 1010 and local component 1020 could be in the form of data packets suitable for transmission between two or more computer processes. Another possible communication between remote component 1010 and local component 1020 could be in the form of circuit-switched data suitable for transmission between two or more computer processes in a radio time slot. System 1000 includes a communication framework 1040, which can be used to facilitate communication between remote component 1010 and local component 1020, and may include an air interface, such as the Uu interface of a UMTS network, via a Long Term Evolution (LTE) network, etc. Remote component 1010 can be operatively connected to one or more remote data storage devices 1050, such as hard disk drives, solid-state drives, SIM cards, device memory, etc., which can be used to store information on the remote component 1010 side of communication framework 1040. Similarly, local component 1020 can be operatively connected to one or more local data storage devices 1030, which can be used to store information on the local component 1020 side of communication framework 1040.

[0199] Regarding the various functions performed by the aforementioned components, devices, circuits, systems, etc., unless otherwise stated, the terminology used to describe such components (including references to "apparatus") is also intended to include any structure (e.g., functional equivalent) that performs the specified function of said component, even if it is not structurally equivalent to the disclosed structure. Furthermore, while specific features of the disclosed subject matter may have been disclosed with respect to only one of several embodiments, such features may be combined with one or more other features of other embodiments, as may be desired and advantageous for any given or particular application.

[0200] The terms “exemplary” and / or “illustrative” as used herein are intended to mean as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited to these examples. Furthermore, any aspect or design described herein as “exemplary” and / or “illustrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor does it imply exclusion of equivalent structures and techniques known to those skilled in the art. Moreover, the use of the terms “comprising,” “having,” “containing,” and other similar words in the detailed description or claims is intended to be inclusive—as an open transition word similar to the term “comprising”—without excluding any additional or other elements.

[0201] As used herein, the term “or” is intended to mean inclusive rather than exclusive. For example, the expression “A or B” is intended to include A, B, and the case of A and B simultaneously. Additionally, the articles “a” and “an” used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise stated or clearly indicated from the context to be in the singular form.

[0202] As used herein, the term "set" excludes an empty set, i.e., a set containing no elements. Therefore, a "set" as disclosed in this subject matter includes one or more elements or entities. Similarly, the term "group" as used herein refers to a collection of one or more entities.

[0203] Unless the context otherwise requires, the terms “first,” “second,” “third,” etc., used in the claims are for clarity only and do not indicate or imply any order of time. For example, “first determination,” “second determination,” and “third determination” do not indicate or imply that the first determination will precede the second determination, or vice versa.

[0204] As used in this disclosure, in some embodiments, the terms "component," "system," etc., are intended to refer to or include computer-related entities or entities associated with operating means having one or more specific functions, wherein the entity may be hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to, a process operating on a processor, a processor, an object, an executable file, a thread of execution, computer-executable instructions, a program, and / or a computer. By way of illustration and not limitation, applications running on a server and the server itself can both be components.

[0205] One or more components may reside within a process and / or execution thread, and components may be located on a single computer and / or distributed across two or more computers. Furthermore, these components may be executed from various computer-readable media on which various data structures are stored. Components may communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacting with another component in a local system, a distributed system, and / or with other systems across a network such as the Internet). As another example, a component may be a device having specific functions provided by mechanical components operated by circuitry or electronic circuitry, operated by a software application or firmware application executed by a processor, wherein the processor may be internal or external to the device and execute at least a portion of the software or firmware application. As yet another example, a component may be a device providing specific functions through electronic components without mechanical parts, the electronic components including a processor to execute software or firmware that at least partially endows the electronic components with the functions. While various components have been illustrated as separate components, it should be understood that multiple components may be implemented as a single component, or a single component may be implemented as multiple components, without departing from the exemplary embodiments.

[0206] As used herein, the term "facilitation" is used in the context of a system, device, or component "facilitating" one or more actions or operations, relating to the nature of a complex computing environment where multiple components and / or devices may be involved in some computational operations. Non-limiting examples of operations involving or not involving multiple components and / or devices include: sending or receiving data, establishing connections between devices, determining intermediate results to obtain results, etc. In this regard, a computing device or component can facilitate an operation by playing any role in completing the operation. Therefore, when describing the operation of a component herein, it should be understood that if an operation is described as being facilitated by that component, such operations may optionally be completed in cooperation with one or more other computing devices or components (e.g., but not limited to sensors, antennas, audio and / or video output devices, other devices, etc.).

[0207] Furthermore, various embodiments can be implemented using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter, methods, apparatus, or articles of art. As used herein, the term "article of art" is intended to cover a computer program accessible from any computer-readable (or machine-readable) device or computer-readable (or machine-readable) storage / communication medium. For example, computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., compact discs (CDs), digital multifunction discs (DVDs)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize that many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

[0208] Furthermore, terms such as “mobile device equipment,” “mobile station,” “mobile,” “subscriber station,” “access terminal,” “terminal,” “handheld device,” “communication equipment,” and “mobile device” (and / or terms denoteing similar terms) can refer to wireless equipment used by subscribers or mobile devices of a wireless communication service to receive or transmit data, control, voice, video, sound, gaming, or substantially any data or signaling stream. The foregoing terms are used interchangeably herein and with reference to the accompanying drawings. Similarly, the terms “access point (AP),” “base station (BS),” “BS transceiver,” “BS equipment,” “cell site,” “cell site equipment,” “g node B (gNB),” “evolved node B (eNB),” “home node B (HNB),” etc., refer to wireless network components or equipment that transmit and / or receive data, control, voice, video, sound, gaming, or substantially any data or signaling stream from one or more subscriber stations. Data and signaling streams can be packet streams or frame-based streams.

[0209] Furthermore, the terms “device,” “communication device,” “mobile device,” “subscriber,” “client entity,” “consumer,” “client entity,” and “entity,” etc., are used interchangeably throughout the text unless the context dictates a specific distinction between the terms. It should be understood that these terms can refer to human entities or automated components supported by artificial intelligence (e.g., the ability to reason based on complex mathematical forms), which can provide simulated visual, voice recognition, etc.

[0210] It should be noted that although various aspects and embodiments are described herein in the context of 5G or other next-generation networks, the disclosed aspects are not limited to 5G implementations and can be applied to other next-generation network implementations, such as sixth-generation (6G) or other wireless systems. In this regard, aspects or features of the disclosed embodiments can be utilized in substantially any wireless communication technology. Such wireless communication technologies may include Universal Mobile Telecommunications System (UMTS), Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Multi-Carrier CDMA (MC-CDMA), Single-Carrier CDMA (SC-CDMA), Single-Carrier FDMA (SC-FDMA), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT Extended OFDM), Filter Bank-Based Multi-Carrier (FBMC), Zero-Tail DFT-Extended OFDM (ZT DFT-s-OFDM), Generalized Frequency Division Multiplexing (GFDM), Fixed-Mobile Convergence (FMC), Universal Fixed-Mobile Convergence (UFMC), Unique Word OFDM (UW-OFDM), and Unique Word DFT Extended OFDM (UW DFT-Extended OFDM), Cyclic Prefix OFDM (CP-OFDM), Resource Block Filtered OFDM, Wi-Fi, Global Microwave Access Interoperability (WiMAX), Wireless Local Area Network (WLAN), General Packet Radio Service (GPRS), Enhanced GPRS, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5G, 3rd Generation Partnership Project 2 (3GP2), Ultra Mobile Broadband (UMB), High Speed ​​Packet Access (HSPA), Evolved High Speed ​​Packet Access (HSPA+), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Zigbee, or another organization of IEEE 802.12 technologies.

[0211] The description of the embodiments shown in the subject matter disclosed herein (including those described in the abstract) is not intended to be exhaustive or to limit the disclosed embodiments to the precise form disclosed. While specific embodiments and examples have been described herein for illustrative purposes, various modifications are possible within the scope of such embodiments and examples, as will be appreciated by those skilled in the art. In this regard, although the subject matter has been described herein in conjunction with various embodiments and corresponding drawings, it should be understood where applicable that other similar embodiments may be used, or modifications and additions may be made to the described embodiments to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the invention. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted in accordance with the breadth and scope of the appended claims.

[0212] Various non-limiting aspects of the various embodiments described herein are presented in the following terms.

[0213] Clause 1, a system comprising: a memory storing computer-executable components; and a processor executing the computer-executable components stored in the memory, wherein the computer-executable components include: a battery discharge component configured to: determine an amount of excess energy available for discharge from a battery pack; determine at least one receiver system for the excess energy; and control the transfer of the excess energy from the battery pack to the at least one receiver system.

[0214] Clause 2, a system according to any of the foregoing clauses, wherein the battery pack includes at least one battery cell.

[0215] Clause 3, a system according to any of the preceding clauses, wherein the at least one receiver system comprises one of a microgrid, a battery pack located on a vehicle, a wide-area synchronous grid, or other energy storage device configured to receive electrical energy.

[0216] Clause 4, the system according to any of the foregoing clauses, wherein the battery discharge component is further configured to determine the operating condition of the at least one receiver system.

[0217] Clause 5, a system according to any of the foregoing clauses, wherein the receiving system is a wide-area synchronous power grid, wherein the battery discharge component is further configured to: determine the operating status of the wide-area synchronous power grid; and, in response to determining that the wide-area synchronous power grid is in a grid emergency, select the wide-area synchronous power grid as the receiver system for the excess energy.

[0218] Clause 6, in any of the preceding clauses, wherein the battery discharge component is further configured to: further determine whether the wide-area synchronous power grid is currently in a grid emergency; and in response to determining that the operating condition of the wide-area synchronous power grid is not currently in a grid emergency, terminate the discharge of excess energy into the wide-area synchronous power grid.

[0219] Clause 7, in any of the preceding clauses, the system wherein the battery discharge assembly is further configured to: determine discharge parameters conforming during the discharge operation, wherein the discharge parameters may include thermal conditions, voltage conditions, current, impedance, grid code, specifications or regulations; and control the discharge of the excess energy according to the discharge parameters.

[0220] Clause 8, the system according to any of the foregoing clauses further includes a presentation component configured to: present a list of options to preferentially select a receiver system; determine an option selected from the list of options; sort the receiver systems based on the selected options; and present the receiver systems according to the sorting based on the selected options.

[0221] Clause 9, the system according to any of the foregoing clauses further includes a presentation component configured to: present a set of inputs, wherein the set of inputs facilitates selection of a corresponding portion of the excess energy to be released to a respective receiver system in the at least one receiver system; receive a first input regarding a first portion of the excess energy to be released to a first receiver system; receive a second input regarding a second portion of the excess energy to be released to a second receiver system; and wherein the discharge component is further configured to: control the discharge of the first portion of the excess energy to the first receiver system; and control the discharge of the second portion of the excess energy to the second receiver system.

[0222] Clause 10, a system according to any of the foregoing clauses, wherein the battery pack is configured to be implemented on and to provide power to the electric vehicle.

[0223] Clause 11, a computer-implemented method comprising: determining, by a device including a processor, an amount of excess energy to be released from a battery pack; determining, by the device, a set of receiver systems available for receiving the excess energy; and controlling, by the device, the release of the excess energy to at least one of the set of receiver systems.

[0224] Clause 12, a computer-implemented method according to any of the preceding clauses, wherein: the battery pack includes at least one battery cell; and at least one receiver system includes one of a microgrid, a battery pack located on a vehicle, a wide-area synchronous power grid, or other energy storage device configured to receive electrical energy.

[0225] Clause 13, a computer-implemented method according to any of the foregoing clauses, wherein the battery pack is located on the vehicle and the battery pack is configured to provide electrical power to the vehicle.

[0226] Clause 14, the computer-implemented method according to any of the foregoing clauses, further includes: the device presenting a list of options to preferentially select a receiver system; the device determining an option selected from the list of options; the device sorting the receiver systems based on the selected options; the device presenting the receiver systems according to the sorting based on the selected options; and the device receiving the selected receiver system to receive the excess energy.

[0227] Clause 15, a computer-implemented method according to any of the preceding clauses, wherein the receiver system is a wide-area synchronous power grid, the method further comprising: determining, by the device, the operating condition of the wide-area synchronous power grid; and, in response to determining that the wide-area synchronous power grid is in a grid emergency, selecting, by the device, the wide-area synchronous power grid as the receiver system for the excess energy.

[0228] Clause 16, a computer program product for releasing excess energy from a battery pack, the computer program product comprising a computer-readable storage medium having program instructions embodied therein, the program instructions being executable by a processor to cause the processor to: determine an amount of excess energy to be released from the battery pack; determine a set of receiver systems available for receiving the excess energy; and control the release of the excess energy to at least one of the set of receiver systems.

[0229] Clause 17, a computer program product pursuant to any of the foregoing clauses, wherein the program instructions are further executable by the processor to cause the processor to: present a list of options to preferentially select a receiver system; determine an option selected from the list of options; sort the receiver systems based on the selected options; present the receiver systems according to the sorting based on the selected options; and receive an input instructing the selected receiver system to receive the excess energy.

[0230] Clause 18, a computer program product pursuant to any of the preceding clauses, wherein the at least one receiver system comprises one of a microgrid, a battery pack located on a vehicle, a wide-area synchronous grid, or other energy storage device configured to receive electrical energy.

[0231] Clause 19, a computer program product pursuant to any of the foregoing clauses, wherein the battery pack is configured to provide electrical power to a vehicle.

[0232] Clause 20, a computer program product according to any of the foregoing clauses, wherein the receiving system is a wide-area synchronous power grid, and wherein the program instructions are further executable by a processor to cause the processor to: determine the operating condition of the wide-area synchronous power grid; and, in response to determining that the wide-area synchronous power grid is in a grid emergency, select the wide-area synchronous power grid as the receiving system for the excess energy.

[0233] In all circumstances, any suitable combination of clauses 1-10 can be achieved.

[0234] In all circumstances, any suitable combination of clauses 11-15 may be achieved.

[0235] In all circumstances, any suitable combination of clauses 16-20 may be achieved.

Claims

1. A system comprising: Memory, which stores computer-executable components; as well as A processor that executes the computer-executable component stored in the memory, wherein the computer-executable component includes: The battery discharge assembly is configured as follows: Determine the amount of excess energy that can be released from the battery pack; Determine at least one receiver system for the excess energy; and Control the transfer of excess energy from the battery pack to the at least one receiver system.

2. The system according to claim 1, wherein the battery pack comprises at least one battery cell.

3. The system of claim 1, wherein the at least one receiver system comprises one of a microgrid, an onboard battery pack located on a vehicle, a wide-area synchronous power grid, or other energy storage device configured to receive electrical energy.

4. The system of claim 3, wherein the battery discharge component is further configured to determine the operating status of the at least one receiver system.

5. The system of claim 4, wherein the receiver system is a wide-area synchronous power grid, and wherein the battery discharge assembly is further configured to: Determine the operating status of the wide-area synchronous power grid; and In response to determining that the wide-area synchronous power grid is in a power grid emergency, the wide-area synchronous power grid is selected as the receiver system for the excess energy.

6. The system of claim 5, wherein the battery discharge assembly is further configured to: Further determine whether the wide-area synchronous power grid is currently in a power grid emergency; and In response to determining that the current operating condition of the wide-area synchronous power grid is not in a grid emergency, the release of excess energy into the wide-area synchronous power grid is terminated.

7. The system of claim 1, wherein the battery discharge assembly is further configured to: Determine the discharge parameters to be met during the discharge operation, wherein the discharge parameters may include thermal conditions, voltage conditions, current, impedance, grid code, specifications or regulations; and The release of excess energy is controlled according to the discharge parameters.

8. The system of claim 1, further comprising a rendering component, the rendering component being configured to: Presents a list of options for prioritizing the selection of receiver systems; Determine the option to be selected from the list of options; The receiver systems are sorted based on the selected options; as well as The receiver system is presented according to the sorting based on the selected options.

9. The system of claim 1, further comprising a rendering component, the rendering component being configured to: A set of inputs is presented, wherein the set of inputs facilitates the selection of a corresponding portion of a corresponding receiver system to which the excess energy is to be released; Receive a first input regarding the first portion of the excess energy to be released into the first receiver system; Receive a second input regarding the second portion of the excess energy to be released into the second receiver system; and The discharge component is further configured to: Control the release of the first portion of the excess energy to the first receiver system; as well as The second portion of the excess energy is controlled to be released to the second receiver system.

10. The system of claim 1, wherein the battery pack is configured to be implemented in an electric vehicle and to provide power to the electric vehicle.

11. A computer-implemented method, comprising: The amount of excess energy to be released from the battery pack is determined by a device including a processor. The device determines a set of receiver systems that can be used to receive the excess energy; as well as The device controls the release of the excess energy to at least one of the receiver systems in the set of receiver systems.

12. The computer-implemented method according to claim 11, wherein: The battery pack includes at least one battery cell; and At least one receiver system includes a microgrid, an airborne battery pack located on a vehicle, a wide-area synchronous grid, or another energy storage device configured to receive electrical energy.

13. The computer-implemented method of claim 11, wherein the battery pack is onboard and positioned on a vehicle, and the battery pack is configured to provide electrical power to the vehicle.

14. The computer-implemented method according to claim 11, further comprising: The device presents a list of options for prioritizing the selection of the receiver system; The device determines the option selected from the list of options; The device sorts the receiver system based on the selected options; The receiver system is presented by the device according to the sorting based on the selected options; as well as The device receives the selected receiver system to receive the excess energy.

15. The computer-implemented method of claim 11, wherein the receiver system is a wide-area synchronous power grid, the method further comprising: The operating status of the wide-area synchronous power grid is determined by the device. as well as In response to determining that the wide area synchronous power grid is in a power grid emergency, the device selects the wide area synchronous power grid as the receiver system for the excess energy.

16. A computer program product for releasing excess energy from a battery pack, the computer program product comprising a computer-readable storage medium having program instructions embodied therein, the program instructions being executable by a processor to cause the processor to: Determine the amount of excess energy to be released from the battery pack; Identify a set of receiver systems that can be used to receive the excess energy; as well as Controlling the release of the excess energy to at least one of the receiver systems in the set of receiver systems.

17. The computer program product of claim 16, wherein the program instructions are further executable by the processor to cause the processor to: Presents a list of options for prioritizing the selection of receiver systems; Determine the option to be selected from the list of options; The receiver systems are sorted based on the selected options; The receiver system is presented according to the sorting based on the selected options; as well as The input of the selected receiver system is to receive the excess energy.

18. The computer program product of claim 16, wherein the at least one receiver system comprises one of a microgrid, an onboard battery pack located on a vehicle, a wide-area synchronous power grid, or other energy storage device configured to receive electrical energy.

19. The computer program product of claim 16, wherein the battery pack is configured to provide electrical power to a vehicle.

20. The computer program product of claim 16, wherein the receiver system is a wide-area synchronous power grid, and wherein the program instructions are further executable by the processor to cause the processor to: Determine the operating status of the wide-area synchronous power grid; and In response to determining that the wide-area synchronous power grid is in a power grid emergency, the wide-area synchronous power grid is selected as the receiver system for the excess energy.

Images