Energy platform based on mechanical energy storage unit
Through a distributed mechanical energy storage unit system and energy-as-a-service platform, flywheel technology is used to solve the challenges of traditional power grids in the face of surge demand and renewable energy transformation, realize power management and dispersed output, and improve the reliability of the power grid. and efficiency.
Patent Information
- Application Number
- CN202380031219.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-01-27
- Filing Date
- 2023-01-27
- Publication Date
- 2024-11-15
AI Technical Summary
Traditional power grids face challenges such as surge in energy demand, climate change, natural disasters and renewable energy transitions, and have difficulty achieving large-scale power storage. and selective consumer control.
Using a distributed mechanical energy storage unit (MESU) system, interacts with independent power systems through the Energy-as-a-Service (EaaS) platform, uses flywheel technology to store and extract power, realize power management and dispersed output, and provide renewable energy and independent energy options. .
Improves the reliability and efficiency of the power grid, reduces the impact of power outages, provides affordable alternatives, supports the rapid transition of renewable energy, and achieves localized storage and decentralized output of electricity.
Smart Images

Figure CN118975085A_ABST
Abstract
Description
Background Art
[0001] The traditional electric grid, an interconnected network used to deliver electricity from electricity producers to consumers, has many shortcomings that make it nearly impossible for producers to both meet surging demand and address modern issues such as climate change, natural disasters, the shift to green energy, and energy affordability.
[0002] For example, existing transmission infrastructure is aging and expensive to maintain; is vulnerable to intrusion by hackers and other malicious actors; is susceptible to brownouts and blackouts, especially as the world's temperatures rise due to climate change; has increasingly been found to fail due to such rising temperatures, causing catastrophic wildfires; fails during major natural disasters such as hurricanes, leaving large populations without power when they are greatly needed; and is inefficient, resulting in energy loss and heat generation.
[0003] Furthermore, existing electricity infrastructure is largely incapable of storing energy when consumer demand is low for later use when energy demand surges. Instead, electricity is typically generated and provided to consumers instantly, and any excess energy is typically dumped into the ground and wasted.
[0004] Despite huge investments and the promotion of green alternatives, only about a third of global electricity is currently generated from renewable sources. This is partly because producers have already made huge investments in existing carbon-based infrastructure and have little incentive to change given their market dominance (often, energy producers are the only available supplier in a particular region). It is also because the existing infrastructure was not designed for alternative energy generation (such as residential generation using solar or wind technologies). In fact, many producers continue to lobby US state governments to rescind solar net metering policies due to the impact of residential solar generation on revenue and infrastructure, further hindering the transition to renewable energy.
[0005] Clearly, a new energy platform is needed for a rapid transition to renewable energy, affordable large-scale electricity storage (powerbanking), and selective consumer control and independence. Summary of the invention
[0006] In some aspects, the technology described herein relates to a system comprising: a first node having a first mechanical energy storage unit (MESU) located in a first geographic location, the first node being coupled to communicate with an energy as a service (EaaS) platform; and a second node having a second MESU located in a second geographic location different from the first geographic location, the second node being coupled to communicate with the EaaS platform, wherein the first MESU of the first node and the second MESU of the second node are each configured to send a power storage status to the EaaS platform, and extract power or store power based on a signal received from the EaaS platform.
[0007] In some aspects, the technology described herein relates to a system wherein each of the first MESU and the second MESU includes an electric motor coupled to one or more flywheels, the electric motor being capable of increasing or decreasing the rotation rate of the one or more flywheels to add power to or extract power from the one or more flywheels, respectively.
[0008] In some aspects, the technology described herein relates to a system wherein each of the first MESU and the second MESU is capable of storing between 3 kWh and 100 kWh of electricity.
[0009] In some aspects, the technology described herein relates to a system, further comprising: an Energy as a Service (EaaS) platform, the EaaS platform comprising: a power management application, the power management application coupled to a first MESU of the first node and a second MESU of the second node via a communication network, and one or more node application programming interfaces (application programming interfaces, APIs), the one or more node APIs coupled to the power management application and configured to receive the power storage status and provide the power storage status to the power management application; and one or more utility APIs, the one or more utility APIs coupled to the power management application and configured to receive one or more energy requests from a utility server via the communication network.
[0010] In some aspects, the technology described herein relates to a system wherein the one or more utility APIs are further configured to receive a signal that notifies the EaaS platform of a power surplus or power demand.
[0011] In some aspects, the technology described herein relates to a system wherein each of the first node and the second node includes an EaaS interface configured to receive a signal indicating that the first MESU or the second MESU is spinning up or spinning down.
[0012] In some aspects, the technology described herein relates to a system wherein: the power management application is configured to: receive user settings specifying a rotation rate of the first MESU, store the user settings in a data storage device, and send the user settings to the first node; and the first MESU is configured to limit the rotation rate of the first MESU based on the user settings.
[0013] In some aspects, the technology described herein relates to a system wherein: the power management application is configured to: receive user-specified power storage parameters for the first MESU; store the user-specified power storage parameters in a data storage associated with the first MESU; and transmit the user-specified power storage parameters to the first node; and the first MESU is configured to enable or disable the first MESU based on the user-specified power storage parameters.
[0014] In some aspects, the technology described herein relates to a system wherein: each of the first node and the second node includes an energy manager configured to interact with an independent power system that provides off-grid power to one or more of the first node and the second node; and each of the first MESU of the first node and the second MESU of the second node respectively includes MESU hardware electrically coupled to the independent power system.
[0015] In some aspects, the technology described herein relates to a system in which an energy manager selectively determines whether to use power from an independent power system or power from a power grid based on one or more of power capacity of the independent power system and power capacity of the power grid.
[0016] In some aspects, the technology described herein relates to a computer-implemented method comprising: receiving, by one or more processors, a signal indicating that one or more mechanical energy storage units (MESUs) are spinning up, each of the one or more MESUs comprising a mechanism for mechanically storing energy; receiving, by the one or more processors, power storage parameters for the one or more MESUs; and enabling the one or more MESUs to receive power based on the power storage parameters and the signal indicating that the one or more MESUs are spinning up.
[0017] In some aspects, the technology described herein relates to a computer-implemented method wherein each of the one or more MESUs includes an electric motor coupled to one or more flywheels, the electric motor being capable of increasing or decreasing the rotational rate of the one or more flywheels to add power to or extract power from the one or more flywheels, respectively.
[0018] In some aspects, the technology described herein relates to a computer-implemented method, further comprising generating, by the one or more processors, a signal instructing the one or more MESUs to spin up or spin down based on the determined power surplus or power demand.
[0019] In some aspects, the technology described herein relates to a computer-implemented method, further comprising: receiving, by the one or more processors, a user setting specifying a rotation rate of the one or more MESUs; storing, by the one or more processors, the user setting in a data storage device; and configuring, by the one or more processors, the one or more MESUs to limit the rotation rate based on the user setting in the data storage device.
[0020] In some aspects, the technology described herein relates to a computer-implemented method, wherein: the one or more MESUs are coupled to one or more nodes, the one or more nodes include an energy manager, the energy manager is configured to interact with an independent power system, the independent power system provides off-grid power to the one or more MESUs; and each of the one or more MESUs includes hardware electrically coupled to the independent power system.
[0021] In some aspects, the technology described herein relates to a computer-implemented method, further comprising: determining, by the one or more processors, to use power from the independent power system based on the power capacity of the independent power system; and configuring, by the one or more processors, the one or more nodes to spin up the one or more MESUs using power from the independent power system.
[0022] In some aspects, the technology described herein relates to a computer-implemented method, further comprising: determining to use power from the power grid based on one or more of the power capacity of the independent power system and the power capacity of the power grid; and configuring the one or more nodes, by the one or more processors, to spin up the one or more MESUs using power from the power grid.
[0023] In some aspects, the technology described herein relates to a computer-implemented method, further comprising: receiving, by the one or more processors, a signal indicating that the one or more MESUs are to slow down in rotation; and instructing the one or more MESUs to slow down in rotation based on the power storage parameter and the signal indicating the slow down in rotation.
[0024] In some aspects, the techniques described herein relate to a computer-implemented method wherein: the one or more MESUs receive current in response to a command to spin up; and the one or more MESUs output current in response to a command to spin down.
[0025] In some aspects, the techniques described herein relate to a computer-implemented method wherein the signal indicating a faster rotation of the one or more MESUs or the signal indicating a slower rotation of the one or more MESUs is based on one or more energy requests received from a utility server via a communication network. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] The present disclosure is illustrated by way of example, and not by way of limitation, with reference to the accompanying figures, in which like references are used to refer to similar elements.
[0027] Figure 1 A block diagram representing an example energy as a service platform is shown;
[0028] Figure 2 A block diagram representing exemplary components of and interactions between a utility server, node(s), and an EaaS manager is shown;
[0029] Figure 3A-3C A signal diagram representing an example method for storing and extracting energy for a utility to meet electricity needs is shown;
[0030] Figure 4 is a flow chart illustrating an example method for peer-to-peer power sharing;
[0031] Figure 5A is a flow chart illustrating an example method for providing a cyclic storage and release solution based on power demand, production, and / or other factors;
[0032] Figure 5B A diagram representing an example power cycle for a given day of the week for a house or grid is shown;
[0033] Figure 6A-6C An example user interface for configuring MESU(s) associated with a node and / or storage cluster is shown;
[0034] Figure 7A-7C An exemplary user interface indicating available power and other information about the MESU(s) is shown. DETAILED DESCRIPTION
[0035] The innovative energy technologies disclosed in this document offer novel advantages, including: the ability to integrate modern technologies with conventional power infrastructure; enable a rapid transition to renewable energy; use the grid 130 as a backup; store electricity locally at nodes and in regionalized storage clusters 160 of (one or more) nodes 140; isolate and minimize the effects of power outages (whether caused by natural disasters, infrastructure failures, or other factors); provide an affordable alternative to expensive and environmentally unfriendly electrochemical batteries; provide consumers with options independent of carbon-based energy sources; and decentralize power production.
[0036] like Figure 1 As shown, the innovative energy technology described herein may include an energy as a service platform (EaaS platform) 100. The EaaS platform 100 may include an EaaS manager 110; (one or more) user applications 172, which may be operated on a computing device accessible to and interacting with (one or more) users 170 of the EaaS platform 100, and are configured to send data to or receive data from the EaaS manager 110; a regionalized storage cluster 160 consisting of one or more nodes 140; and a power grid 130 including one or more power facilities 132 connected to a power transmission infrastructure 134.
[0037] The node 140 includes a power consuming entity and at least one MESU 150. The node 140 may be a consumer-powered entity or an entity coupled to a consumer-powered entity. Figure 1 , node 140 is represented as a house 142 (such as a residence), but it should be understood that any entity that consumes electricity is applicable, such as one or more appliances, a commercial structure such as a warehouse or office building, an electronic device or system (whether configured to be mobile or stationary), a transportation system and / or vehicle, a transportation charging system, a power source, a substation, a backup substation, etc. The storage cluster can provide power storage functionality as further discussed herein. Elements of node 140 include (one or more) MESUs 150, an independent power system 147, a power grid 130, and / or any appliances and / or other entities that may be electrically coupled via an electrical system 154, which includes wiring, connectors, switches, plugs, circuit breakers, transformers, inverters, controllers, and any other appropriate electrical components.
[0038] In the example shown, the node 140 is equipped with or coupled to power generation technology equipment, such as an independent power system 147 and / or a power grid 130. The independent power system 147 may include localized power generation technology equipment that allows independent power generation, such as renewable power generation technology equipment. Non-limiting examples include a solar power system 144 (including a solar array, a controller, an inverter, etc.), a wind turbine system 146 (including (one or more) turbines, controllers, inverters, etc.) and / or other energy sources 148 (such as hydroelectric systems, geothermal systems, nuclear systems and their components, etc.). The power generation technology equipment may additionally or alternatively be conventional carbon-based power generation technology equipment, such as the power grid 130 shown, but for carbon-negative or carbon-neutral embodiments, greener power generation technology equipment may be preferred.
[0039] Node 140 includes or is coupled to an energy storage unit capable of storing any excess power generated by the power generation technology. In some embodiments, the energy storage unit may include a mechanical energy storage unit (MESU) 150. MESU 150 includes one or more flywheels 152A, 152B ... 152N (also simply individually or collectively referred to as 152). MESU 150 converts power received from the power generation technology device into kinetic energy by accelerating (increasing the rotation rate) the rotation of flywheel 152.
[0040] Each flywheel 152 may be configured to store energy up to a certain maximum value. As a non-limiting example, the motor coupled to the flywheel 152 may be configured to rotate the flywheel 152 to between 15,000 revolutions per minute (RPM) and 25,000 RPM, so that the flywheel 152 can store between 18 kilowatt-hours (kWh) and 28 kWh of electricity. Three stacked flywheels 152 can be combined to store between 54 kWh and 84 kWh of electricity. During the time when the power generated by the power generation technology equipment (e.g., solar cells) is less than the power consumed by the electrical equipment (e.g., household appliances) of the house 142, the motor can operate as a generator, converting the kinetic (mechanical) energy stored in the flywheel 152 into electrical energy, thereby obtaining energy from the flywheel 152 to meet the local power needs of the node 140 (e.g., powering the electrical equipment of the house 142). In this example, advantageously, the node 140 may use an average of 15 kWh of electricity per day, and if local generation ceases to produce any electricity, the MESU 150 may be able to fully power the node 140 in approximately 4-6 days.
[0041] In another example, as discussed further elsewhere herein, a utility may have integrated with the EaaS manager 110, and its utility management application 122 signals to the power management application 111 via the storage cluster API(s) 112 that it is experiencing a surge in power demand, and the power management application 111 may signal the node 140 or a cluster of nodes 140 (e.g., storage cluster 160) to separate energy from the flywheel 152 and provide the energy back to the grid via the transmission infrastructure 134, which may be connected to the node(s) 140 via a connection point (e.g., a two-phase or three-phase power service line or buried power line connected to a service panel, which typically includes a power meter(s)). Conversely, the utility may be generating excess power and may wish to store / storage the power. The utility management application 122 may signal the power management application 111 via the storage cluster API(s) 112 that it needs to store a given amount of power, which may in turn signal the node 140 or cluster(s) of node(s) 140 (such as one or more regionalized storage clusters 160) to notify them of the storage need, and those nodes 140 in the storage cluster 160 that have excess capacity and are configured to receive power from the grid may receive the power via the transmission infrastructure 134 and store it as mechanical energy in the MESU for later retrieval. The EaaS platform 100 may charge the utility for power storage services, as further discussed elsewhere herein.
[0042] It should be understood that the RPM and kWh numbers provided in the previous paragraph are meant as non-limiting examples, and that the MESU 150 may be configured with a flywheel 152 that is capable of storing more or less power depending on the implementation. For example, the weight of the flywheel 152, the materials used for the flywheel 152, the size and configuration of the flywheel 152, the efficiency of the motor and bearings, etc. may all be adjusted based on the usage to provide the required backup power for the node 140. As a further example, the flywheel 152 may be made of steel, aluminum, carbon fiber, titanium, any suitable alloy, and / or any other material capable of handling the operation, vibration, radial and shear stresses and strains, and other conditions to which such a flywheel 152 will be subjected.
[0043] The power transmission infrastructure 134 includes the power network that couples power-consuming entities such as homes, offices, appliances, etc. to power facilities that generate electricity from carbon, nuclear, and / or natural resources. The transmission infrastructure 134 may include intermediate elements such as step-up transformers, substations, transmission lines, etc., which are interconnected to widely provide power to different geographic areas.
[0044] The electric utility 301 (also referred to as utility 301 for short) may own and operate one or more electric utilities and portions of the transmission infrastructure 134, and may operate a utility server configured to execute the utility management application 122. The utility management application 122 may perform various functions, such as load balancing, load management, and grid energy storage, to manage the supply of electricity based on real-time demand. However, given the limitations of existing grid technology, blackouts, brownouts, and expensive peak power costs remain the norm.
[0045] A user may use an instance of a user application 172 executing on a computing device (e.g., a user's mobile phone or personal computer) to configure and interact with the MESU(s) 150 that they are authorized to control (e.g., a MESU 150 installed in their home or business), as further discussed elsewhere herein.
[0046] like Figure 1 As shown, the EaaS manager 110, utility server 120, power facility 132, elements of the power grid 130, wind turbine system 146, solar power system 144, other energy sources 148, (one or more) nodes 140, regionalized storage cluster 160, user application 172 and associated computing devices, etc. can be coupled via wireless or wired connections (using network interfaces associated with the computing devices of the aforementioned elements) for communication and connected to the network 102. The network 102 may include any number of networks and / or network types. For example, the network 102 may include one or more local area networks (LANs), wide area networks (WANs) (e.g., the Internet), virtual private networks (VPNs), wireless wide area networks (WWANs), Network, personal area network (PAN) (e.g. communication networks), various combinations thereof, and the like. These private and / or public networks can have any number of configurations and / or topologies, and data can be sent via the networks using a variety of different communication protocols, including, for example, various Internet layer, transport layer, or application layer protocols. For example, data can be sent via a network using TCP / IP, UDP, TCP, HTTP, HTTPS, DASH, RTSP, RTP, RTCP, VOIP, FTP, WS, WAP, SMS, MMS, XMS, IMAP, SMTP, POP, WebDAV, or other known protocols.
[0047] The EaaS manager 110, utility server 120, node(s) 140, electric utilities, and user devices may have computer processors, memory, and other elements that provide them with non-transient data processing, storage, and communication capabilities. For example, each of the aforementioned elements may include one or more hardware servers, server arrays, storage devices, network interfaces, and / or other computing elements, etc. In some implementations, one or more of the aforementioned elements may include one or more virtual servers operating in a host server environment. Other variations are also possible and contemplated.
[0048] It should be understood that Figure 1 The EaaS platform 100 and Figure 2 The diagrams shown are representative of example systems, and a variety of different system environments and configurations can be envisioned, and all of these are within the scope of the present disclosure. For example, various actions and / or functions can be moved between entities (e.g., from a server to a client, vice versa, or between servers), data can be merged into a single data store or further divided into additional data stores, and some implementations can include additional or fewer computing devices, services, and / or networks, and various functions can be implemented client-side or server-side. In addition, the various entities of the system can be integrated into a single computing device or system, or divided into additional computing devices or systems, etc., without departing from the scope of the present disclosure.
[0049] Figure 2 A block diagram is depicted showing exemplary components of and interactions between a utility server 120, a node(s) 140, and an EaaS manager 110. The utility server includes an instance of a utility management application 122 and an EaaS interface 124. The EaaS manager 110 includes a power management application 111, a plurality of utility APIs 112, a plurality of node APIs 113, a plurality of MESU APIs 114, and a data store 210. The data store 210 may store and provide access to data related to the EaaS platform 100, such as cluster data 211, node data 212, user data 213, usage data 214, utility data 214, and analytics data 216.
[0050] The node 140 of the EaaS platform may include one or more MESUs 150. The MESU 150 may include an instance of a flywheel controller 254. The flywheel controller 254 may include a flywheel coupler 255, a flywheel selector 256, and a flywheel monitor 257. The MESU hardware 258 may include a base, one or more flywheels 152, a plurality of magnets and / or a plurality of bearings, a flywheel coupler 255, and / or a motor-generator. The motor-generator may be coupled to each flywheel 152 via a flywheel coupler 255. The flywheel coupler 255 may engage and disengage the motor-generator with the flywheel 152, so that each flywheel 152 may rotate freely when disengaged, and may be coupled to the motor-generator when engaged, so that the motor-generator may increase the speed of the flywheel 152 (spin the flywheel 152 faster), or the flywheel 152 may rotate the generator to generate electricity. Each flywheel 152 may be suspended using magnets to minimize the friction caused by the rotation of the flywheel 152. As an example, a magnetic levitation unit may be used to suspend and hold the flywheel 152 while rotating.
[0051] Additionally or alternatively, bearings (such as but not limited to ceramic bearings) may be used to support and hold the flywheel 152 as it rotates. The base may house and support the flywheel 152. The flywheel 152 may be arranged horizontally or vertically. In the horizontal direction, the flywheel 152 may have a wheel-like shape and may be stacked one on top of another in the same base, but still configured to rotate independently of each other. In this configuration, depending on the embodiment, a coupler is independently coupled to each flywheel 152, or more than one coupler and motor may be used. In the vertical direction, the flywheel 152 may have a roll-like shape and may be positioned parallel to each other in the base. In either direction, in some embodiments, the base may include a housing that encloses the MESU 150 and provides a vacuum environment in which the components of the MESU 150 may operate. This is advantageous because it prevents dirt, debris, and corrosion-causing elements from entering and allows the flywheel 152 and other components to operate optimally.
[0052] In some embodiments, the node 140 may include one or more MESUs 150, and may act as a manager of (one or more) MESUs, may receive and process information for two or more MESUs 150 from the Eaas manager 110, and may send signals to (one or more) MESUs 150 (e.g., via the flywheel controller 254 and / or MESU hardware 258), and receive and process signals from (one or more) MESUs 150 (e.g., via the flywheel controller 254 and / or MESU hardware 258) to control the functions and operations of (one or more) MESUs. In some further embodiments, the structure, actions and / or functions of the flywheel controller 254 and the node application 240 and their component parts may be combined, and the node 140 may represent the MESU 150 itself, and one or more devices that consume power may be coupled to the MESU to receive power. Other variations are also possible and contemplated.
[0053] The utility management application 122 , flywheel controller 254 , node application, node management application, multiple utility APIs, multiple node APIs, and multiple MESU APIs may each include hardware and / or software executable to provide the actions and functions disclosed herein.
[0054] Specifically, the utility management application 122 can be executed by a utility server to monitor the generation and distribution of one or more power utilities and the transmission infrastructure 134. The utility management application 122 can receive signals from various entities of the EaaS platform (e.g., the EaaS manager 110, nodes, the transmission infrastructure 134, other utility management applications associated with other suppliers, etc.). The utility management application 122 can communicate with the EaaS manager 110 via the EaaS interface 124 to access the services provided by the EaaS manager 110. In particular, the EaaS interface 124 can interact with the utility API of the EaaS manager 110 to request power storage, request to provide supplemental power, to provide usage data, performance data, and / or demand data, etc. In some embodiments, the EaaS interface 124 can generate a secure request and send the secure request to the utility API via the network. The power management application 111 can receive the request via the utility API and process it accordingly.
[0055] The power management application 111 may be coupled to a data store 210 to store and retrieve data. Any type of data stored in the data store (e.g., cluster ID, user ID, entity program ID, node ID, MESU ID, configuration data, etc.) may be used to organize and query the data stored by the data store 210. The data store 210 may include a file system, a database, a data table, a document, or other organized collection of data.
[0056] The cluster data 211 may include information about a cluster of more than two nodes (e.g., a regionalized storage cluster), such as the identity of (one or more) nodes 140, the storage capacity of the storage cluster 160, the availability of the storage cluster 160, the operational health of the storage cluster 160 and / or (one or more) constituent MESUs 150, the historical performance of the storage cluster 160, etc.).
[0057] The node data 212 may include information about the node, such as the number of MESUs installed at the node 140, the type of node 140, the operational health of the MESU(s) 150, any limitations or operating parameters of the MESU(s) 150, configuration data of the MESU(s) 150, an identifier of the MESU(s) 150, to whom the MESU(s) 150 belong, whether the MESU(s) 150 can be used to store grid power, whether the MESU(s) 150 have been deactivated, and the like.
[0058] User data 213 may include information about a user associated with storage cluster 160, node 140, or MESU 150, including user account information, login information, user preferences for managing MESU(s) (eg, schedule data, activation / deactivation data, etc.).
[0059] The usage data 214 may include information about usage of the cluster and / or MESU(s) 150, such as the rotation rate of the flywheel 152, power output levels, maintenance cycles, downtime, inactive periods, third-party usage (e.g., by a utility or neighboring node 140), and the like.
[0060] The utility data 215 may include information about the utility partnering with the EaaS platform 100, such as utility account information, utility capacity information, power storage requirements, contract parameters, performance requirements, grid 130 specifications, etc.
[0061] The analytical data 216 may include insights about the EaaS platform 100 , such as local versus grid power generation, aggregate usage data, aggregate performance data, etc. However, it should be understood that any other data suitable and applicable to the EaaS platform 100 may be stored and processed by the EaaS manager 110 .
[0062] The node application 240 and the flywheel controller 254 may communicate with the EaaS manager 110 via an EaaS interface 242 configured to interact with the node API(s) 113 exposed by the EaaS manager 110. The node API(s) 113 provide methods for accessing data related to the node 140 and the MESU(s) 150 associated with the node 140, as well as methods for performing various functions, such as signaling the unavailability / availability of stored power, requesting a functional upgrade (such as a higher rotation rate of one or more flywheels 152, or deactivating / activating previously active / inactive flywheels 152), reporting usage data and / or status information, and the like.
[0063] The flywheel manager 244 of the node application is configured to communicate with the flywheel controller 254 to provide operation control signals, such as power storage signals, power extraction signals, rotation rate adjustment signals, flywheel enable / disable signals, etc. The energy manager 246 is configured to communicate with the flywheel manager 244 and provide control signals to the flywheel manager according to energy requirements (generating energy for local use, generating energy for utility use, storing local energy, storing energy provided by the utility, etc.).
[0064] The flywheel coupler 255 is configured to control the mechanical coupling of the flywheel 152 with the motor-generator, the flywheel selector 256 is configured to select which flywheel 152 to control based on the received control signal, and the flywheel monitor 257 monitors the status of each flywheel 152 for safe operation and performance within defined operating parameters, and can control the functions of the MESU hardware 258, as well as shut down, slow down, pause, adjust, optimize or otherwise control the MESU hardware 258 based on the monitored status.
[0065] Figures 3A-3C A signal diagram 300 is depicted, illustrating an example method for storing and withdrawing energy to meet electricity needs for a utility 301 .
[0066] like Figure 3AAs shown, at block 305, the utility management application 122 detects 304 a power surplus and determines 305 (one or more) surplus parameters. The utility management application 122 generates and sends 306 a signal notifying the EaaS manager 110 of the surplus. The EaaS manager 110 determines 307 (one or more) energy storage requirements associated with the surplus based on the signal, and determines one or more storage clusters 160 based on the requirements at block 308. The EaaS manager 110 generates and sends a signal to the node(s) 140 of the cluster(s) 160 (as reflected in the cluster data) at block 309, the signal instructing the MESU(s) 150 of the cluster(s) to spin up.
[0067] The nodes 140 (e.g., via their node applications 240) determine 310 the rotational parameter(s) based on the requirement(s), and monitor and adjust 314 the MESU(s) 150(s) via the flywheel controller. The MESU(s) 150(s) of the node(s) 140 send 315 the power storage status to the EaaS manager 110, which records 316 the stored energy based on the storage status(es). The EaaS manager 110 monitors 317 whether the supply requirements have been met, and once the supply requirements have been met, signals the nodes via their node applications 240 to idle the MESU(s) 150(s) as needed. In response, the MESU(s) 150(s) may be idled 318 as needed (e.g., by the node application 240). In some embodiments, the MESU(s) 150(s) may be sequentially stepped down to ramp down the stored energy. In these or other embodiments, some or all of the MESUs 150 may be idled in parallel. Other variations are possible and contemplated.
[0068] The EaaS manager 110 and / or the utility management application 122 may detect a power demand 311 and determine parameter(s) 312 associated with the power demand. In some embodiments, the storage cluster (e.g., via the utility management application 122) generates and sends 313 a signal notifying the EaaS manager 110 of the demand, and in response thereto, the EaaS manager 110 determines 319 a demand for the requirement(s) based on the signal, and determines 320 a storage cluster(s) 160 based on the requirement(s). Next, the EaaS manager 110 generates and sends 321 a signal(s) to a node 140 of the storage cluster(s) 160 based on the requirement(s). The node(s) (e.g., via the node(s) 240) selects 322 a MESU(s) 150 from which to extract energy, and initiates 323 extraction of energy from the selected MESU(s) 150.
[0069] It should be noted that the node 140 and the MESU 150 may be separate devices, separate devices or components of a single device, or otherwise. For example, the operations and features of the node 140 and the MESU 150 may be combined, interchanged, or otherwise modified without departing from the scope of the present disclosure.
[0070] like Figure 3C As shown, the node(s) 140 (e.g., via the node application 240) monitors and regulates 324 energy extraction based on the requirements of the demand(s), and sends 325 the extraction status(es) to the EaaS manager 110, which records 326 the extracted energy in the data store 210 based on the extraction status. The EaaS manager 110 monitors 327 whether the requirements of the demand have been met based on the status. If so, the EaaS manager 110 signals the storage cluster(s) 160 of the node(s) 140 to stop energy extraction, and the node(s) 140 (e.g., via their node application 240) correspondingly stops 328 extracting power from the MESU. The EaaS manager 110 then generates and sends 329 a signal to the storage cluster notifying (e.g., via the utility management application 122) that the extraction is complete.
[0071] Figure 44 is a flow chart illustrating an example method 400 for end-to-end power sharing. At block 401, the energy manager 246 of a given node 140 monitors the power levels of the MESUs 150 of that node 140, and at block 402, signals the power management application 111 via the node API 113 to update the data store 210 with the power level(s) of the MESU(s) 150(s). In some embodiments, the flywheel monitor 257 monitors the operating state of the flywheels 152 (including their rotational rate), and based on the operating state, transmits the power level of each flywheel 152 to the energy manager 246. In other embodiments, the flywheel monitor 257 stores data reflecting the operating state in a local non-transitory memory of the MESU 150 for retrieval by the energy manager 246 (e.g., on an ongoing basis). Other variations are also possible and contemplated.
[0072] In some embodiments, the energy manager 246 sends data to the node API 113 via the EaaS interface 242 over the network 102 to notify the power management application 111 of the current power level of the MESU(s) 150, and the power management application 111 updates the user data 213 and / or node data 212 associated with the user and the applicable MESU(s) 150 to reflect the current power level(s). Additionally or alternatively, the node(s) 140 may store the updated power level(s) locally in a non-transitory storage device of the node(s) 140 or the MESU(s) 150, and may provide the data to the power management application 111 upon request. Other variations are possible and contemplated, such as the user application 170 connecting directly to the node(s) 140 or the MESU(s) 150 to receive the current power level(s).
[0073] At block 403, the power management application 111 may determine the available power of the MESU(s) 150 from which power may be used by the requesting user. This may be performed in response to a request for available power that is accessible. For example, the requesting user may require additional power (e.g., the storage power level of the requesting user's MESU(s) 150 may be low), and may access a digital power market interface served by an EaaS manager 110 (e.g., a server hosting digital services embodied by the power management application 111, storage cluster API 112, node API 113, etc.) and request available power from the MESU(s) 150 of other users of the service. In some embodiments, if the effective power level of certain flywheels becomes too low, the user may set an automatic replenishment setting to replenish those flywheels, etc. As described elsewhere herein, many other variations are possible and contemplated.
[0074] At block 404, a user application 170 associated with the power management application 111 (which in some embodiments may include an instance of the power management application 111) may include an application that interfaces with an API of the EAS manager 110, or may take some other suitable form, and may generate a user interface for presentation to the requesting user. The user interface may include user interface elements that reflect the available power that the requesting user may request from the EaaS platform 100. Fig. 7A , a graphical representation of a user interface 700 illustrates a non-limiting example of such an interface. As shown, the user interface 700 includes an overview area 704 that indicates the total amount of electricity available to the user, and may also include a detail area that lists the component MESUs 150 and the corresponding amount of electricity available to them (and may also include other information, such as cost per kWh, storage cluster 160, user 170, node 140, identifier of the MESU(s) 150, etc.). The user interface 700 may also include options for sorting and filtering the component MESU(s) 150 (e.g., selected at element 706), including by cost (per kWh), location, or other suitable parameters.
[0075] Reference again Figure 4At block 405, the user application 170 may receive input from a requesting user via an input device of a computing device on which the user application 170 is running. The input may include a user selection requesting a share of the available power (or shares). For example, the requesting user may select a portion of the total available amount from all storage clusters 160, a group of storage clusters 160, a specific storage cluster 160, a node 140 or a group of nodes 140, a MESU 150 or a group of (one or more) MESUs 150, any combination of the above, and the like. For example, depending on availability, the requesting user may select a portion or all of the available power from one or more specific MESUs 150 belonging to a specific user, or any available MESU 150 belonging to any user, or some other combination.
[0076] As a further example, Fig. 7A and Figure 7B As shown, in response to the user selecting one of the interface elements 702 or the item interface elements 704, the user application 170 can generate a user interface 720 for presentation, and the user can interact with the user interface via an input device to configure, submit, or cancel the power request. In the depicted example, the interface 720 can be a user-selectable interface element 722 for returning to the user interface 700, a user-selectable interface element 724 such as a slider or other incremental interface element for variably selecting a specific amount of electricity, and user-selectable interface elements 726, 728. For example, the user positions the user interface element 724 to an amount of 7.5 kilowatt-hours (kWh) at a cost of $0.90, and can select the request button 726 to finalize the request for the amount of electricity, or can cancel from the request table and return to the interface 700 by selecting the cancel button 728.
[0077] Reference again Figure 4 In response to receiving input at box 405, the power management application 111 may generate a notification and send the notification to one or more users from whom power is being requested. In some embodiments, the requesting user may request a specific amount of power from a first user. In further embodiments, the requesting user may request a power amount from a power pool that includes multiple users. In such an embodiment, the requesting user may not know the identity of the user from whom power is being requested. In this case, the power management application 111 notifies these users of the request in advance, or may simply proceed with the request based on prior authorization provided by these users to share with other users the power they have stored in their respective MSUs upon request, in which case the power management application 111 may passively provide notification of sharing power with the requesting user. Other variations are also contemplated and included herein.
[0078] Although Figure 7CAn example notification interface 740 is shown including an affirmative notification requiring approval, which includes a message area 748 notifying the user of the sharing request and including a link 748 to a profile of the requesting user, and user-selectable options 744, 746 (e.g., buttons 744, 746) for approving or denying the request, but notifications sent by the power management application 111 may include other forms and content, may be combined with other information, may not require explicit consent, and may be provided in different contexts and through various channels, including push notifications, text messages, in application messages, via an management dashboard, via pop-up windows, via electronic communications such as email, and the like.
[0079] It should be understood that in other embodiments, a user can set up a continuous request to obtain power from other users by setting certain parameters in the account management interface. In this case, the user will not need to interact with the user interface to request power, but can establish the necessary parameters, which once met, will trigger such a request, thereby creating a seamless experience for the user.
[0080] For example, a user may specify that when the cost of electricity from the grid 130 is higher than electricity from an energy pool that includes the available MESU(s) 150 (also referred to as the MESU pool) of the EaaS platform, one or more MESUs 150 or flywheels from those MESUs 150 belonging to the user are charged (e.g., spun up and / or maintained at a particular rotation rate) using electricity from (one or more) other MESUs 150. In another example, a user may specify that at certain times of the day, such as when the local production of the user's independent power system 147 (e.g., a solar power system 144 installed on the user's premises) is low, electricity available from the MESU pool is used to charge / maintain all or some of the user's (one or more) MESUs 150 or their flywheels 152. This example may be further expanded to factor in the cost of electricity from the grid 130 as in the previous example. Using the power management application 111, the user may advantageously set parameters on a flywheel-by-flywheel basis to optimize the user's preferences and experience. Many other variations are also possible and contemplated.
[0081] Reference again Figure 4At block 407, the power management application 111 may receive input (e.g., via the user application 170) reflecting a response from the requesting user (e.g., the first user) from whom power is being requested, and if approved, the request may continue as shown in block 408, or terminate the request as shown in block 413. In embodiments where the request is sent to multiple users drawn from a pool of MESUs, if any such user denies the request, the power management application 111 may select an alternate user from the available pool of MESUs 150, and may generate and send a notification to them. In this way, the request may continue even if some users deny the sharing request.
[0082] In further embodiments where the users forming the MESU pool have affirmatively chosen to share power without notification, the power management application 111 may omit or skip operations at blocks 406, 407, 408, and 413 (resulting in automatic approval of the request). Other variations may include a hybrid, where some users associated with a sharing request receive an explicit notification (requiring approval), while other users (due to their prior consent) do not require it. This advantageously facilitates a faster power sharing experience between users.
[0083] At block 409 , in response to determining that the request is approved (eg, automatically or based on an affirmative response), the power management application 111 may notify the requesting user (eg, via the user application 170 ) of the acceptance of the request.
[0084] At blocks 410, 411, 412, the power management application 111, in conjunction with an instance of the node application 240, redistributes power between the requesting user's MESU(s) 150 and the user from which power is provided. This may be accomplished in a variety of ways, depending on the configuration of the power infrastructure connected to the requesting user's MESU(s) 150. In some embodiments, these MESUs 150 may be directly electrically connected to other storage clusters 160 or nodes 140, and may therefore deliver power without using the grid 130. This may advantageously result in a more robust and cost-effective approach, as the direct delivery approach is more energy efficient than delivering power to / from the grid 130, and power does not need to be purchased / sold from or deducted from / to the utility 301 (and therefore lower or no conversion rates and fees may be applied).
[0085] In further embodiments, power may be delivered from the supplying MESU(s) 150 150 to the requesting MESU(s) 150 via the grid 130 at the most cost effective time of day or from the most power efficient area to ensure the lowest cost for the transfer. In still further embodiments, power may be stored from the supplying MESU(s) 150 to the grid 130 at an optimal time based on the applicable power cost / credits of the supplying MESU(s) 150 and then withdrawn from the grid 130 to the receiving MESU(s) 150 at a later optimal time based on the power cost / credits applied to the receiving MESU(s) 150. It should be appreciated that many further variations are possible and contemplated.
[0086] For any of these embodiments, at block 410, the power management application 111 updates the data store 210 to reallocate the share of available power. In some embodiments, the power management application 111 may update the user data 213 of the users of the MESU pool and the requesting user to reflect the amount of power that should be transferred from the one or more MESUs 150 of the provided user(s) (the provided MESUs 150) to the one or more MESUs 150 of the requesting user (the requested MESUs 150). In embodiments involving multiple users providing a portion of the power requested by the requesting user, the power management application 111 updates the user data 213 of those users to reflect the allocated amount of power that should be transferred from their respective (one or more) MESUs 150.
[0087] When reallocating power at blocks 410, 411, 412, and additionally or alternatively, when indicating available power at block 404, the power management application 111 may coordinate the requested amount of power with the flywheel limits and threshold limits such that (as reflected in the node data 212 associated with the MESU(s) 150 and flywheel 152, as further discussed elsewhere herein) power is provided by approved / approved / enabled flywheels and a minimum flywheel rotation rate is maintained as specified by the sharing user. The power management application 111 also determines the power available to a given user from the EaaS platform 100 with reference to expense limits and cost considerations.
[0088] At block 411, based on the updated settings in block 410, the power management application 111 signals the energy manager 246 of the node application 240 via the EaaS interface 242 of the provided MESU(s) 150 to extract power from the one or more flywheels 152 of the MESU(s) 150 (depending on their settings and configurations), and at block 412, instructs the energy manager 246 of the node application 240 via the EaaS interface 242 of the received MESU(s) 150 to increase the corresponding amount of energy (depending on their settings and configurations) by spinning the one or more flywheels of the MESU(s) 150. The stored user data 212 may indicate the specific MESU(s) 150 from which power should be transferred, the specific flywheel(s) of the specific MESU(s) 150 from which power should be transferred, etc.
[0089] Figure 5A is a flow chart illustrating an example method 500 for providing a solution for storage and release of cycles based on power demand, production, and / or other factors. It should be noted that the operation of the example method 500 may include additional or fewer components, a different order, and / or be combined or exchanged with other operations and features described herein. For example, the operation or parameters of the method 500 may be based on user settings, such as the selection of stored power, target cycle frequency, target charge or discharge amount, or other settings as described below. In some embodiments, the operation or parameters of the method 500 may be additionally or alternatively based on other factors such as local or utility power demand. For example, the operation or parameters may be modified statically or dynamically based on the power demand of the power grid, local power consuming devices, etc., based on cost-effective time (e.g., in the presence of usage time or other considerations).
[0090] It should also be noted that although the operations of method 500 are described as iterative and recursive, they may be performed at any frequency, continuously, and / or concurrently across multiple systems, power grids, storage units, etc.
[0091] The operations of method 500 are described as being performed or controlled by energy manager 246, but it should be noted that other embodiments are possible and are contemplated herein. For example, energy manager 246 may receive (one or more) communications from power management application 111, as described elsewhere herein, which may include grid information, instructions or requests to store power, instructions or requests to provide power to the grid, or other information. In some instances, the instructions of power management application 111 may be subject to constraints defined for node 140 or other storage units. For example, an administrator or other stakeholder may define settings to limit the amount or percentage of charge or discharge to a static or dynamic amount, although other settings, constraints, or preferences are possible.
[0092] In some embodiments, at block 501, the energy manager 246 may determine the capacity of the grid. For example, an industrial grid (e.g., provided by a utility service) may have excess power capacity or negative power capacity that may be received or filled by the node 140 and / or the independent power system 147. The energy manager 246 may communicate with the power management application 111, the utility management application 122, or the system, for example, using the EaaS interface 242 and / or the node API 113, to determine the power production, capacity, or consumption on the grid. In some cases, the energy manager 246 may determine the power production, capacity, or consumption on the grid based on predicted demand, such as based on a time period, predicted capacity, whether or not ... Figure 5B Other defined data shown in the exemplary duck curve of FIG. 1 to determine negative capacity or positive capacity.
[0093] For example, as shown below Figure 5B As illustrated and described, the grid may experience varying production and / or demand over time (e.g., based on solar production). To smooth out peak demand periods or low demand periods (e.g., as indicated at 564'), the utility management application 122 or power management application 111 may indicate positive or negative capacity that may be unloaded or requested to or from energy storage units based on whether the current production or demand of the grid is above / below average or desired levels.
[0094] return Figure 5A In some embodiments, at block 502, the energy manager 246 may determine, for example, the local grid capacity of an independent power system 147. For example, the energy manager 246 may determine whether an independent power system (e.g., using a solar power system 144, a wind turbine system 146, and / or other energy sources 148) has a positive or negative flow rate into or out of the grid, or an amount of power that needs to be added or removed to balance the system or otherwise reach a target storage rate or production rate.
[0095] For example, when the local grid (e.g., by solar power system 144) generates excess power, it is determined that the excess capacity should be unloaded to the grid to address the duck curve, or stored in node 140 to address the duck curve or store power, or based on other factors such as time of use rate, desired backup power storage, etc.
[0096] In some embodiments, in addition to or in lieu of current production or demand, at block 501 or block 502, method 500 may determine a target capacity, inflow or outflow rate, or otherwise set a threshold for using, storing, or providing power to a grid or local network. As described elsewhere herein, these values may be further modified based on the total possible storage capacity of the grid, local network, node(s), defined transmission rates, etc.
[0097] At block 503, the energy manager 246 may determine whether to store power and / or how much power to store, for example, based on whether the grid requests to unload or receive capacity, the local power demand or production of the local grid, and the available storage capacity of the node(s) 140. For example, if solar power generation causes both the grid and the local grid to have excess capacity (e.g., in excess of demand) in the afternoon, the energy manager 246 may determine to store power at the storage unit(s). Similarly, if the local grid and / or the grid has low capacity or production (e.g., demand for power during times of high demand or low production), the energy manager 246 may determine to release power (as described below).
[0098] In response to determining to store power at block 503, the energy manager 246 may select one or more storage units or nodes 140, which may include the MESU(s) 150 or flywheel(s) 152 described herein, to store power at block 504. The energy manager 246 and / or the power management application 111 may select one or more from the plurality of storage units to store power based on available energy storage capacity of the plurality of storage units, such as nodes, flywheels, etc., balance of the nodes 140, sequential use of the nodes 140, power cycling frequency or demand, etc. For example, block 503 may include determining which node has sufficient available storage capacity to receive power.
[0099] In some examples, at block 505, the energy manager 246 may select one or more flywheels of the energy storage unit or node 140 to receive power. The flywheel(s) may be selected based on their available storage capacity, safe or optimal capacity or rotational frequency, balanced wear, or other configurations. In some embodiments, the energy manager 246 may charge or balance the charge sequentially.
[0100] At block 506, the energy manager 246 may charge the selected one or more flywheels using the power for storage (e.g., as determined at block 501 or block 502). For example, the energy manager 246 may control the distribution of power to the selected flywheels to rotate them (e.g., via interaction with the flywheel manager 244).
[0101] At block 507, the energy manager 246 may determine whether a defined threshold has been met. The defined threshold may be based on the amount of electricity to be stored or the available capacity of the energy storage unit. For example, a flywheel may have a maximum or minimum storage capacity threshold that is hardware or software constrained.
[0102] If the determination at block 507 satisfies the threshold, method 500 may return to block 501. If the determination at block 507 is negative, method 500 may continue at blocks 504, 505, or 506 to store excess power based on available capacity or characteristics of a storage unit, flywheel, etc., as described above.
[0103] Returning to the operation at block 503, if the determination to store power is negative, the method 500 may proceed to block 508, where the energy manager 246 may determine whether to release power from a power storage device, such as node 140, into, for example, a power grid. As described with reference to block 503, the energy manager 246 may determine to release power based on whether the power grid and / or the local network is requesting power. The determination of whether to release power may be additionally or alternatively based on a target energy storage value or range defined or determined for the storage unit(s). For example, the energy manager 246 may determine the amount of power to release from the storage unit based on how much power is requested by the power grid(s), how much excess power is stored by the storage unit (e.g., above a threshold minimum storage, effective storage, or other available storage), and / or a threshold minimum or preferred power storage defined by a stakeholder setting.
[0104] In some cases, the storage unit may not have additional storage beyond a minimum threshold of hardware or software constraints (e.g., based on preference settings, physical configuration, etc.), so the determination at 508 may be negative and method 500 may, for example, return to box 501 or box 502.
[0105] In response to a positive determination at block 508, the energy manager 246 may release power to the grid or utility grid. For example, the energy manager 246, the power management application 111, the utility management application 122, or otherwise may perform blocks 509-512, which may be in parallel with blocks 504-507, to release power from the storage unit.
[0106] For example, at block 509, the energy manager 246 may select one or more energy storage units (e.g., node(s) 140) with available energy storage. At block 510, the energy manager 246 may select one or more flywheels associated with the energy storage units to discharge, for example, based on their available storage, power delivery characteristics (e.g., how fast they can supply power, maximum available current, current rotation frequency, etc.), or other factors. At block 511, the energy manager 246 may (e.g., via interaction with the flywheel manager 244) instruct one or more flywheels 511 to discharge and provide their power to the grid(s).
[0107] At block 512, the energy manager 246 determines whether a threshold discharge amount has been met. Similar to the determination at 507, the threshold may be based on a requested amount of grid capacity and / or an available amount of power stored in the energy storage unit(s) (e.g., based on total available power or a defined available range). If the threshold has not been met at block 512, the energy manager 246 may continue to discharge the flywheel until the threshold is met. If the threshold has been met or cannot be met (e.g., because no available power is remaining to be stored), the method may return to block 501 or block 502.
[0108] Thus, using the operation of the example method 500, the technique can automatically refill energy storage using locally or remotely generated electricity during low demand periods, such as Figure 5B Similarly, during periods of high demand, method 500 may release energy storage into the grid (or grids). Thus, as noted elsewhere herein, power production and demand may be smoothed, thereby increasing the efficiency of the grid and / or local network.
[0109] Figure 5B A graph 550 is shown representing an example power cycle for a given day of the week for a house 142, such as a residence. As shown, between midnight and 7:30 a.m. (561), local solar generation is low, so the node application uses power from the grid to spin up or maintain the rotation rate of the flywheel(s) 152 of the MESU(s) 150. Between 7:30 a.m. and 11 a.m. (562), power demand surges (reflecting the morning ramp-up 562'), so the node application 240 releases power from the flywheel(s) 152 of the MESU(s) 150 to meet the power requirements of the house 142 and / or (if so configured / if desired) to provide power to the grid 130. From 11 a.m. to 5 p.m. (i.e., 17:00) (563), demand is relatively flat, but local solar generation is strong, so the node application 240 spins up the flywheel(s) 152 of the MESU(s) 150 using power from the renewable energy source. From 5pm (17:00) to 8:30pm (i.e. 20:30) (564), the power demand peaks, so the node application 240 again draws power from the flywheel(s) 152 of the MESU(s) 150 to meet the demand. From 8:30pm (i.e. 20:30) to midnight (i.e. 24:00) (565), the demand drops, and the node application 240 again spins up the flywheel(s) 152 of the MESU(s) 150 using utility power.
[0110] Fig. 6A and Figure 6BExample user interfaces 600, 650 are shown for configuring the MESU(s) 150 associated with a node 140 and / or a storage cluster 160. Figure 5A As shown, a user may receive a power storage request from a storage cluster that permits power storage using one or more flywheels 152 of the user's MESU(s) 150. The user may accept or deny the request by providing input via an input device (e.g., a touch screen) of the user's computing device, thereby selecting a corresponding graphical element displayed in the interface (e.g., a "Yes" 602 or "No" 604 button).
[0111] exist Figure 6B , the user can configure preferences on a flywheel-by-flywheel basis. For example, the user can drag the flywheel 152 from the home to the Granite Power and Light, which will enable the Granite Power to store electricity to the flywheel 152, or vice versa. The user can also enable or disable the flywheels 152 to activate or deactivate them, as well as view analytics about each flywheel 152 by selecting one, which presents an interface showing usage, performance and other analytics about the flywheel 152, as well as cost savings, expenses, etc. For example, the interaction elements 652, 654, 656, 658 are illustrated as toggle switches that allow the flywheel to be activated or deactivated.
[0112] like Figure 6CAs shown in the example user interface 680 depicted in , a user can assign the flywheel 152 to another user so that the other user can store electricity by dragging the flywheel 152 to the corresponding position via the interface (Nate W can assign the flywheel 152 to Mike B for use, and vice versa). In addition, the flywheel 152 can be drilled in or enabled or disabled, as further shown. It should be understood that in some embodiments, the parameters of a given flywheel 152 (such as the allowed rotation rate) can be set via the interface. For example, the capacity of the flywheel 152 determined by the rotation rate can be locked at different levels by the EaaS platform, and the user can upgrade the flywheel 152 by "increasing" the rotation rate to a higher level (increasing the energy storage capacity of the flywheel 152). For example, the maximum rotation rate can be set to 10,000 RPM, and the user can choose to increase the rotation rate to 15,000 RPM to obtain an additional 30% storage capacity. In response to selecting this option in the corresponding user interface, the node application can generate a request and send a request to the EaaS manager 110 requesting authorization for the upgrade. The EaaS manager 110 may update the user's account reflecting the upgrade and may increase the user's subscription plan to reflect the upgrade (with the user's account additionally charged for the additional capacity). In response to upgrading the user's account, the EaaS manager 110 may send a signal to the node application that the upgrade was successful, and the node application may locally store configuration data reflecting the change and send a signal to the flywheel controller 254 to rotate one or more flywheels 152 at a speed of up to 15,000 RPM. As described in the above example, graphic elements 682, 684, 686, and 688 may be provided for the flywheels to enable or disable them.
[0113] It should be understood that the techniques and implementations described herein are provided by way of example, and variations and combinations of implementations can be envisioned. For example, in some embodiments, at least a portion of one or more of the methods represent various fragments of one or more larger methods, and can be connected, or the various steps of these methods can be combined to produce other methods covered by the present disclosure. In addition, it should be understood that in some cases, the various operations in the method can be iterative, and therefore repeated multiple times as needed to generate the results described herein. In addition, the order of the operations in the method is provided by way of example, and it should be understood that the various operations can occur earlier and / or later in the method without departing from its scope.
[0114] In addition, although some specific details are set forth in order to provide a thorough understanding of the present disclosure, it should be understood that the technology described herein can be practiced without these specific details. In some cases, various systems, devices and structures are shown in block diagram form to avoid making the description vague. For example, various embodiments are described as having specific hardware, software and / or user interfaces. However, the present disclosure is applicable to any suitable variation that can provide the described structure and / or function.
[0115] Therefore, without departing from the spirit or essential characteristics of the present specification, the present specification may be embodied in other specific forms. Likewise, the specific naming and division of modules, routines, features, attributes, methods, and other aspects may not be mandatory or important, and the mechanisms for implementing the present specification or its features may have different names, divisions, and / or formats.
[0116] Unless otherwise stated, as will be apparent from the following discussion, it should be understood that throughout this disclosure, discussions utilizing terms such as "processing," "computing," "computing," "determining," "displaying," "communicating," "transmitting," etc. may refer to actions and methods of a computer system that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission, or display devices.
[0117] Computing system or equipment (for example, data processing system) suitable for storing and / or executing program code, such as computing system and / or equipment discussed herein, can comprise at least one processor directly or indirectly coupled to memory element by system bus.Memory element can comprise local memory, mass storage device and provide temporary storage of at least some program codes to reduce the high-speed cache memory of the number of times that must retrieve code from mass storage device during execution.Input / output or I / O equipment can be coupled to system directly or by intermediate I / O controller.Data processing system can comprise the device that can be specially constructed for required purpose, or it can comprise the general-purpose computer that is selectively activated or reconfigured by the computer program stored in the computer.
[0118] In addition, the modules, routines, features, attributes, methods and other aspects of the present disclosure can be implemented as software, hardware, firmware or any combination of the foregoing. The present technology can also take the form of a computer program product that can be accessed from a computer-available or computer-readable medium, and the computer-available or computer-readable medium provides a program code used by a computer or any instruction execution system or used in combination with a computer or any instruction execution system. Regardless of whether the component (an example of which is a module or an engine) in the specification is implemented as software, the component can be implemented as an independent program, a part of a larger program, a plurality of separate programs, a static or dynamic link library, a kernel loadable module, firmware, resident software, microcode, a device driver and / or any other mode known now or in the future. In addition, the present disclosure is by no means limited to the embodiments of any specific programming language, or is not limited to the embodiments of any specific operating system or environment. Therefore, the present disclosure is intended to illustrate but not to limit the scope of the subject matter set forth in the appended claims.
Claims
1. A system, include: a first node having a first mechanical energy storage unit MESU located at a first geographical location, the first node being coupled to communicate with an Energy as a Service EaaS platform; as well as A second node having a second MESU located at a second geographical location different from the first geographical location, the second node being coupled for communicating with the EaaS platform, wherein the first MESU of the first node and the second MESU of the second node are each configured to send a power storage status to the EaaS platform, and extract power or store power based on a signal received from the EaaS platform.
2. The system according to claim 1, in, Each of the first MESU and the second MESU comprises an electric motor coupled to one or more flywheels, the electric motor being capable of increasing or decreasing the rotation rate of the one or more flywheels to respectively add power to or extract power from the one or more flywheels.
3. The system according to claim 2, in, Each of the first MESU and the second MESU is capable of storing between 3 kWh and 100 kWh of electricity.
4. The system according to claim 1, further comprising: include: Energy as a Service EaaS platform, the EaaS platform includes: a power management application coupled to a first MESU of the first node and a second MESU of the second node via a communication network, and one or more node application programming interfaces (APIs) coupled to the power management application and configured to receive the power storage status and provide the power storage status to the power management application; and One or more utility APIs are coupled to the power management application and configured to receive one or more energy requests from a utility server via a communication network.
5. The system according to claim 4, in, The one or more utility APIs are also configured to receive a signal notifying the EaaS platform of a power surplus or power demand.
6. The system according to claim 5, in, Each of the first node and the second node includes an EaaS interface configured to receive a signal indicating that the first MESU or the second MESU is rotating faster or slower.
7. The system according to claim 4, in: The power management application is configured to: receiving a user setting specifying a rotation rate of the first MESU; storing the user settings in a data store; and sending the user settings to the first node; as well as The first MESU is configured to limit a rotation rate of the first MESU according to the user setting.
8. The system according to claim 4, in: The power management application is configured to: receiving user-specified power storage parameters for the first MESU; storing the user specified power storage parameters in a data store associated with the first MESU, and transmitting the power storage parameters specified by the user to the first node; as well as The first MESU is configured to enable or disable the first MESU based on the user-specified power storage parameter.
9. The system according to claim 1, in: Each of the first node and the second node includes an energy manager configured to interact with an independent power system that provides off-grid power to one or more of the first node and the second node; as well as Each of the first MESU of the first node and the second MESU of the second node respectively includes MESU hardware electrically coupled to the independent power system.
10. The system of claim 9, wherein the energy manager selectively determines whether to use power from the independent power system or power from the grid based on one or more of power capacity of the independent power system and power capacity of the grid.
11. A computer-implemented method, include: Receiving, by one or more processors, a signal indicating that one or more mechanical energy storage units MESU are spinning up, each of the one or more MESUs including a mechanism for mechanically storing energy; receiving, by the one or more processors, power storage parameters for the one or more MESUs; as well as Based on the power storage parameter and the signal indicative of the one or more MESUs being spun up, the one or more MESUs are enabled to receive power.
12. The computer-implemented method of claim 11, in, Each of the one or more MESUs includes an electric motor coupled to one or more flywheels, the electric motor being capable of increasing or decreasing the rotation rate of the one or more flywheels to add power to or extract power from the one or more flywheels, respectively.
13. The computer-implemented method of claim 11, further comprising generating, by the one or more processors, a signal instructing the one or more MESUs to spin up or spin down based on the determined power surplus or power demand.
14. The computer-implemented method of claim 11 , further comprising: include: receiving, by the one or more processors, a user setting specifying a rotation rate of the one or more MESUs; storing, by the one or more processors, the user settings in a data storage; as well as The one or more MESUs are configured, by the one or more processors, to limit the rotation rate based on user settings in the data store.
15. The computer-implemented method of claim 11, in: The one or more MESUs are coupled to one or more nodes, the one or more nodes comprising an energy manager configured to interact with an independent power system, the independent power system providing off-grid power to the one or more MESUs; as well as Each of the one or more MESUs includes hardware electrically coupled to the independent power system.
16. The computer-implemented method of claim 15, further comprising: include: determining, by the one or more processors, to use power from the independent power system based on power capacity of the independent power system; as well as The one or more nodes are configured, by the one or more processors, to spin up the one or more MESUs using power from the independent power system.
17. The computer-implemented method of claim 15, further comprising: include: determining to use power from the grid based on one or more of a power capacity of the independent power system and a power capacity of the grid; as well as The one or more nodes are configured, by the one or more processors, to spin up the one or more MESUs using power from the grid.
18. The computer-implemented method of claim 11, further comprising: include: receiving, by the one or more processors, a signal indicating that rotation of the one or more MESUs is slowing; as well as Based on the power storage parameter and the signal indicative of slowing down the rotation, the one or more MESUs are instructed to slow down the rotation.
19. The computer-implemented method of claim 18, in: The one or more MESUs receive electrical current in response to a command to spin up; and The one or more MESUs output current in response to a command to slow down the rotation.
20. The computer-implemented method of claim 18, in, The signal instructing the one or more MESUs to rotate faster or the signal instructing the one or more MESUs to rotate slower is based on one or more energy requests received from a utility server via the communication network.
