KR20240069751A - Battery-centric virtual grid (VG) system - Google Patents

Abstract

The battery-centric virtual grid system may include battery modules, each of which may acquire one or more battery cells, obtain performance information from one or more battery cells, and obtain performance information from the plurality of battery modules based on the individual performance information. is configured to identify an individual device driven by modules and determine characteristics of an individual device driven by an individual module from the plurality of battery modules based on performance information, or a plurality of battery modules. One or more processors configured to receive data from individual devices driven by modules from one or more processors, one configured to remotely receive and transmit data such that the individual devices become part of the IOT network through the respective modules It includes one or more transceivers, and an enclosure that at least partially surrounds one or more battery cells, one or more module processors, and one or more transceivers.

Description

Battery-centric virtual grid (VG) system

This application claims priority to U.S. Provisional Patent Application No. 63/242,819, entitled “BATTERY SYSTEM AND BATTERY POWERED VEHICLE,” filed on September 10, 2021, Incorporated herein by reference in its entirety.

The present invention relates to battery-powered devices, particularly battery-centric virtual grid (VG) systems.

Traditionally, electric vehicles (eg, battery powered) have been charged in a manner similar to that used to charge most rechargeable battery powered devices. That is, the operator plugs the vehicle's battery charger into an electrical outlet connected to the power company's power grid, and the vehicle's charger charges the vehicle's battery. A vehicle's charger may contain explicit logic or components to vary the charging rate to extend the life of the vehicle's battery, but may not contain other significant logic.

In another technology area, Internet of Things (IoT) devices provide opportunities for monitoring and tracking IoT devices and other associated devices. As the number of IoT devices increases, the use of technologies to track and monitor devices will become more important. Additionally, a significant portion of the number of IoT devices is expected to be battery-powered.

Although systems currently exist to monitor the charging and location of devices and batteries, significant challenges and opportunities remain.

This disclosure relates to a battery-centric virtual grid (VG) system that allows movement of battery modules instead of moving power through a wired grid like prior art grids. VG collects data from batteries and battery-powered devices within batteries, and interpolates the data to regulate a multi-user database. The system disclosed herein utilizes battery connectivity innovations to create a virtual grid (VG), an aggregate system of DC devices. VG serves as a power management system for all batteries and the battery-powered devices connected to these batteries. Currently, systems may exist that monitor the charging and location of corresponding devices and batteries, but these systems do not interpolate data in a way that can accommodate a multi-user database. The system disclosed herein can provide data and feedback to VG users. This allows VG users to leverage their own data as well as aggregate data to enlarge and/or reduce their portion of the grid as needed.

In one embodiment, the battery module may have wireless connectivity allowing the battery module to communicate in the VG Cloud. VG Cloud can allow end users or the grid to control the output and charging of individual batteries and report diagnostic information. The VG Cloud can enable end users or the grid to identify and control not only a specific battery, but also that battery-powered device and other batteries and devices that are logically close to the specific battery.

Widespread deployment of VG batteries as a system allows intercommunication between various types of devices, allowing for simplified, centralized control and monitoring of batteries and powered devices, a virtual grid. Environments in which VG batteries can be deployed include home or commercial device power storage, device power backup, and vehicle power.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various example systems, methods, etc. that illustrate various example embodiments of aspects of the present invention. It will be understood that element boundaries (eg, boxes, groups of boxes or other shapes) illustrated in the drawings represent one example of boundaries. Those skilled in the art will understand that one element can be designed as multiple elements, or multiple elements can be designed as one element. An element shown as an internal component of another element may be implemented as an external component, and vice versa. Additionally, elements may not be drawn to scale.

1 illustrates a schematic diagram of an example battery-centric virtual grid (VG) system.
FIG. 2A illustrates a block diagram of an example battery module for the system of FIG. 1.
2B illustrates a perspective view of an example battery module.
2C illustrates a perspective view of an example battery module and plug in base.
3 illustrates a flow diagram of an example method for a battery-centric virtual grid (VG) system.
Figure 4 illustrates a block diagram of an example computing environment for deploying portions of the system of Figure 1.

1 illustrates an example battery-centric virtual grid (VG) system 1. As will be explained in detail below, since battery modules 10 are used in the construction of the VG system 1, the VG system 1 is referred to herein as battery-centric. System 1 includes a number of battery modules 10.

2A-2C illustrate block diagram and profile drawings of an example battery module 10. Battery module 10 includes one or more battery cells 12, one or more module processors 14, a battery management system (BMS) 16, a wireless transceiver 18, a power port 24, and a data port 26. may include. The battery module includes at least partially one or more battery cells 12, one or more module processors 14, a battery management system (BMS) 16, a wireless transceiver 18, a power port 24, and a data port 26. It may further include an enclosure 20 for accommodating it.

The battery module 10 may include one or more battery cells 12 that are electrically configured to deliver a target range of voltage and current for a certain period of time for expected load scenarios. Depending on the number and capacity of battery cells, the capacity of the battery module 10 may range from 1.0 kWh to 5.0 kWh. In one embodiment, the capacity of the battery module 10 is 1.8 kWh, depending on the number and capacity of battery cells. In another embodiment, the capacity of the battery module 10 is 3.6 kWh, depending on the number and capacity of battery cells. In another embodiment, the capacity of the battery module 10 is 5.0 kWh, depending on the number and capacity of battery cells. In some embodiments, depending on the number and capacity of battery cells, the capacity of the battery module 10 may be lower than 1.0 kWh or higher than 5.0 kWh. Battery cells 12 may be lithium ion rechargeable cells, for example, but may also be other types of rechargeable cells.

Battery module 10 may include one or more module processors 14 operably coupled to one or more battery cells 12 to obtain performance information from the one or more battery cells 12 . In the illustrated embodiment of FIG. 2A , processor 14 is operably coupled to battery cells 12 via a battery management system (BMS) 16 . BMS 16 may, for example, monitor parameters (e.g. voltage, current, temperature, etc.), provide battery protection (e.g. overcurrent, short circuit, overheating, etc.), prevent operation of battery cells outside of their ratings. , may perform supervision of the battery cells 12, including estimating the operating state of the battery cell, continuously optimizing battery performance, and reporting the operating state to the processor 14. Processor 14 is operably coupled to BMS 16 to obtain performance information of battery cells 12. Performance information in this context includes, for example, voltage, current, temperature, abnormal conditions such as overcurrent, short circuit, overheating, operating status of the battery cell, etc. from the battery module 10 containing the battery cells 12. It includes all information that the BMS 16 can obtain.

In some cases, monitoring may be necessary as power passes through battery module 10 rather than as it is drawn from battery module 10. For example, in a scenario where the battery module 10 is fully charged and commercial grid power is low, a power company (e.g., via remote server 32) or a user (e.g., a computing device (e.g., CDs) may instruct the battery module 10 not to discharge but instead serve as a conduit for grid power to the load connected to the power port 24. BMS 16 or processor 14 (or a combination thereof) may still monitor power delivery and collect data accordingly. This data will be included in performance information.

Battery module 10 may further include a wireless transceiver 18 operably coupled to processor 14 for remotely transmitting data including performance information from battery cells 12. Wireless transceiver 18 may include a transmitter, a receiver, or both, such that it may only transmit information, only receive information, or may send and receive information. Wireless transceiver 18 may be a broadband cellular network (e.g., 3G, 4G, 5G, etc.) transceiver or a transceiver using other local area network (LAN) or wide area network (WAN) technologies. Wireless transceiver 18 may communicate in a network using, for example, Wi-Fi, Bluetooth, satellite communications, etc.

As best illustrated in FIGS. 2B and 2C , battery module 10 includes an enclosure 20 that at least partially includes one or more battery cells 12, one or more module processors 14, and a wireless transceiver 18. ) may further be included. The enclosure 20 may be mounted on or built on one or more handles 22 that a user can grasp to carry the module 10. The weight, size and form factor of module 10 are designed to be “human-sized” with ergonomics in mind. That is, the module 10 can be designed to be pluggable/unpluggable and transportable by a single person at such a size, shape and weight that a single person can carry it relatively comfortably and without injury. .

Regarding weight, the module may be designed to comply with guidelines or maximum lifting weight regulations, for example, the National Institute for Occupational Safety and Health (NIOSH) Lifting Equations (2021), Guidelines for Evaluation of Two-Handed Manual Lifting Tasks, Revised. You can. These guidelines define the recommended weight limit (RWL) as the amount of load that almost all healthy people (typically workers) can lift for a significant period of time (e.g., 8 hours) without increasing the risk of developing back pain. Some guidelines state that the maximum weight that can be lifted with both hands under ideal conditions is 51 pounds. Some guidelines state that the maximum weight that can be lifted with both hands under ideal conditions is 40 pounds. In one embodiment, battery module 10 is designed to weigh less than 51 pounds. In another embodiment, battery module 10 is designed to weigh less than 40 pounds. In another embodiment, battery module 10 is designed to weigh less than 25 pounds. In some embodiments, battery module 10 is designed to have a weight ranging from 40 pounds to 51 pounds. In some embodiments, battery module 10 is designed to have a weight ranging from less than 40 pounds to more than 51 pounds.

With respect to size and form factor, module 10 may be designed to have a generally “suit case” rectangular form factor, with handle 22 positioned at one end of module 10. ) can be installed or built on. The dimensions of module 10 may range from 12 inches to 24 inches in height, from 6 inches to 12 inches in width, and from 4 inches to 8 inches in depth. In one embodiment, module 10 may be 16 inches tall, 9.5 inches wide, and 5.5 inches deep. In some embodiments, battery module 10 can have a height ranging from less than 12 inches to longer than 24 inches, a width ranging from less than 6 inches to more than 12 inches, and a depth ranging from less than 4 inches to more than 8 inches. It is designed as

Returning to FIG. 2A , module 10 may include a power port 24 for connecting battery module 10 to a powered device (PD). Powered devices (PDs) may correspond to vehicles, home appliances, etc., as described in detail below. Additionally, the power port 24 may serve as a charging port for the battery module 10. That is, since the battery module 10 is detachable and movable, the user plugs the power port 24 of the battery module 10 to, for example, the power port of the vehicle to supply power to the vehicle, and the battery module 10 (10) can be separated from the vehicle, the battery module (10) can be transported to a charging station, and the battery module (10) can be plugged into the charging station and charged through the power port (24).

Battery module 10 may further include a data port 26 for connecting battery module 10 to a data bus of a powered device (PD). For example, if the powered device (PD) is a vehicle, data port 26 may be connected to the vehicle's CAN bus (ISO 11898 standard). Likewise, data port 26 may be connected to other communication systems, such as, for example, wired standards (RS485, etc.) as well as wireless standard (Wi-Fi, Bluetooth, ZigBee, WiMAX, etc.) communication systems. Accordingly, data port 26 may be a wired port, a wireless port, or a combination thereof.

As best shown in FIG. 2C , battery module 10 may have a connector 11 for plugging into connector 15 of base 13 . Connector 11 may integrate power port 24 and data port 26. Base 13 may be a standalone charging/power distribution port connected to the building's power distribution system. The base 13 may also be a receiver for a vehicle (PD-V) or a vehicle battery dock.

Battery module 10 may further include a satellite position system (GPS) 28 receiver operably coupled to processor 14 for communicating the geographic location of battery module 10 to processor 14 . In some embodiments, battery module 10 may utilize technologies instead of or in addition to GPS 28 to obtain the geographic location of battery module 10 (e.g., a GPS-equipped mobile phone). Bluetooth communication, Wi-Fi Positioning System (WPS), etc.) can be adopted.

Returning to FIG. 1 , system 1 includes a population of battery modules 10 .

Some battery modules 10 are connected to vehicles (PD-V) to supply power to vehicles, serve as one-way or two-way vehicle wireless data transmission devices, and serve as a link between vehicles and IoT. can do. The power capacity of the battery module 10 makes it possible to supply power to the electric vehicle (PD-V) through the power port 24. The battery module's BMS 16 may also allow collection of vehicle and battery performance data. The GPS 28 may be used to obtain location data of the vehicle PD-V and whether the battery module 10 (and thus the vehicle PD-V) is stationary or moving. The battery module 10 can also be connected to the vehicle data system of the electric vehicle (PD-V) via the data port 26. The wireless transmitter 18 of the battery module 10 can transmit the collected data through the cloud (CL) and store it in the database 30. Vehicles (PD-V) may include any transportation device including two-wheeled, three-wheeled, four-wheeled, etc.

Some battery modules 10 may be connected to other powered devices (PD-O), such as home appliances. In the illustrated embodiment of Figure 1, the battery modules 10 are illustrated as being directly connected to the home appliances PD-O, but the battery modules 10 can be connected to the home appliances PD-O. It can be connected to any DC (or, through an inverter, AC) household power system. The battery modules 10 supply power to these devices (PD-O), serve as unidirectional or bidirectional device wireless data transmission devices, and can serve as a link between the devices and the IoT. The power capacity of the battery module 10 can supply power to devices (PD-O) through the power port 24. The battery module's BMS 16 may also allow collection of battery and device performance data. GPS 28 may be used to obtain location data of the device (PD-O). For some equipped devices, the battery module 10 may also be connected to the device data system of the devices PD-O via the data port 26. The wireless transmitter 18 of the battery module 10 can transmit the collected data through the cloud (CL) and store it in the database 30.

Some battery modules 10 may be in the process of being recharged by the charger CX. Although battery modules 10 are illustrated as connected directly to charger CX in the illustrated embodiment of FIG. 1 , battery modules 10 can be connected to DC (or, via a rectifier) to which charger CX can be connected. AC) can be connected to the household power system. The battery module 10 can be recharged by the charger CX, can serve as a one-way or two-way charger wireless data transmission devices, and can serve as a link between the charger and the IoT. BMS 16 of battery module 10 may also allow collection of battery and charger performance data. The GPS 28 may be used to obtain location data of the charger CX, etc. For some equipped chargers, battery module 10 may be connected to the charger data system of charger CX via data port 26. The wireless transmitter 18 of the battery module 10 can transmit the collected data through the cloud (CL) and store it in the database 30.

Some battery modules 10 may be temporarily separated from devices such as vehicles (PD-V), home appliances (PD-O), or chargers (CX). Even when power is not being supplied to other devices or charging, the battery modules 10 can collect their own data (location data, remaining charge of the battery, etc.). The BMS 16 of the battery module 10 may allow for collecting performance data of the battery. The GPS 28 may be used to obtain the location and whether the battery module 10 is stationary or moving. Therefore, even when the battery module 10 is not supplying power to other devices or is not charging, the battery module 10 provides one-way information about its own data (e.g., location data, whether the battery is in use (no), battery charge remaining amount, etc.). Alternatively, they can act as two-way wireless data transmission devices and serve as their own link to the IoT. The wireless transmitter 18 of the battery module 10 can transmit the collected data through the cloud (CL) and store it in the database 30.

In this way, the database 30 stores data from all battery modules 10 and their corresponding powered devices (PD-V, PD-O) and chargers (CX). Each battery module 10 manufactured so far can have a corresponding field in the database 30, whereby the system 1 can store all battery modules 10 in the fleet and the connected battery modules 10. You can have up-to-date detailed information about the corresponding devices.

System 1 may further include a remote server 32 that communicates with battery modules 10 or database 30, including receiving data including performance information. That is, the battery modules 10 can communicate data including performance information to the cloud (CL) using the wireless transceiver 18 of the battery modules 10, and the server 30 connected to the cloud (CL) ) receives data including performance information from the database 30 or from the battery modules 10. You can receive it directly.

2A, if the powered device (PD) has its own data port that is compatible with data port 26, that connection can be used to obtain data including performance information of the powered device (PD). there is. This connection can also be used to control a powered device (PD) via the battery module 10. For example, energy demand could exceed the supply capacity of the virtual grid, potentially causing a brownout or blackout. Grid operators can offset imbalances by reducing the amount of electricity consumed when demand exceeds supply. Remote server 32 (or user computing devices (CDs) as described below) may communicate with the powered device (PD) via battery module 10 to influence the powered device (PD) to control such demand response devices. It can go crazy.

If the powered device (PD) does not have a data port compatible with the data port 26, the system 1 of FIG. 1 can detect the power consumption of the powered device (PD) through analysis of the power consumption detected at the power port 24. Data including characteristics can be obtained. Characteristics in this context include, for example, the identity of powered devices (PDs) (type of device, model, etc.), settings, performance characteristics such as power consumption, abnormal conditions such as overcurrent, short circuit, etc. , may include all information that the BMS 16 can derive from analysis of power consumption detected at the power port 24.

In one embodiment, system 1 uses techniques to identify powered devices (PD) and determine information about changes in the state of the powered devices (PD), e.g., in a home. . One source of data for determining information about powered devices (PD) in the home may be the electrical connection at the power port 24. BMS 16 operably connected to power port 24 may use disaggregation techniques to determine information about individual powered devices (PD) within the home.

In one embodiment, the combination of processor 14 and BMS 16 is a powered device (PD) driven by a corresponding battery module 10 using current, voltage, or power signatures detected at power port 24. ) can be identified. More specifically, electrical events or short- or long-term waveforms or spectra, for example, voltage or load current, may be associated with an event type or device type. For example, electrical events can be specifically identified as corresponding to certain types of powered devices (PD), such as motors, heating elements, power supplies for consumer electronic devices, battery chargers, lamps, etc. Subsequent processing by BMS 16, processor 14, remote server 32, or some other computing device may use the event type to more efficiently and/or accurately identify powered devices (PD). .

For example, BMS 16 may process electrical signals (e.g., voltage and current) to decompose these signals or obtain information about individual devices (PD) within the home connected to power port 24. You can. For example, the BMS 16 may determine device events such as that the washing machine was turned on at 8:30 am or that the refrigerator compressor started running at 10:35 am and 11:01 am. BMS 16 may transmit this performance information about device events to remote server 32, database 30, or processor 14 via wireless transmitter 18. BMS 16 also determines raw real-time information about the power used by individual devices (PDs) in the home and transmits this real-time information to a remote server 32 or database via wireless transmitter 18 for further processing. It can be transmitted to (30). For example, the BMS 16 may be used by multiple devices (PDs) in the home at predetermined intervals, such as 10 second intervals, 3 second intervals, 1 second intervals or intervals of less than 1 second. The power can be determined, and the battery module 10 can transmit that information.

Information from electrical events can be used to identify the device type. Similar techniques may be used to obtain performance information (eg, event type) of powered devices (PD). In this way, the power port 24 can be used to obtain data containing performance information of the powered device (PD). Additionally, power port 24 may be used to control a powered device (PD) by, for example, regulating power to or turning off power to the PD using BMS 16. In this way, the power port can be used to effectively transform conventional (i.e., not “smart” or IoT-enabled) devices into IoT-enabled devices, enabling smart monitoring and control of such conventional devices. . In this way, remote server 32 (or user computing devices (CDs), as described below) can, for example, connect to powered devices (PDs) that do not have an explicit data port compatible with data port 26. Demand response device control for a powered device (PD) can also be performed through the battery module 10.

System 1 may also provide a user interface accessible to users through computing devices (CDs), such as computers or mobile phones. Via the user interface of the computing devices (CD), system 1 provides data, including, for example, the characteristics of its battery modules 10 and powered devices (PD), to users of system 1. Can communicate. Through a user interface within computing devices (CD), system 1 may also allow a user to control battery modules 10 and powered devices (PD).

Accordingly, system 1 presents a novel battery-centric virtual grid (VG) system that allows movement of battery modules 10 instead of movement of power through a wired grid like prior art grids. The VG collects data from the battery module 10, including data from battery-powered devices (PDs) within the battery. System 1 uses battery connectivity innovations to create a virtual grid (VG), a collective system of devices. VG serves as a power management system for all batteries and battery-powered devices connected to those batteries. System 1 can provide data and feedback to VG users. This allows VG users to utilize aggregate data as well as their own data to enlarge and/or reduce portions of the grid as needed. VG can allow end users or the grid to control the output and charging of individual batteries as well as report diagnostic information. The VG can enable end users or the grid to identify and control any particular battery module, as well as the corresponding battery-powered device and other batteries and devices that are logically proximate to the particular battery module.

Extensive deployment of battery modules 10 may enable intercommunication between various types of devices, enabling simplified, centralized control and monitoring of batteries and powered devices as a virtual grid. Environments in which battery modules 10 may be deployed may include home or commercial device power storage, device power backup, and vehicle power.

System 1 can be used to map past power demand and predict future power demand at specific nodes in the grid at specific times. System 1 may also monitor certain times (e.g., the days and times a user commutes to a particular location, the days and times a user washes their clothes, the days and times people wash their clothes the most, etc.). It can be used to identify individual and community tendencies, habits, etc. as reflected by the power consumption of specific powered devices at specific locations. More specifically with respect to power transfer, system 1 may be used to ensure efficient power transfer by utilizing data in database 30.

In one embodiment, a user interface of computing devices (CDs) may communicate performance information of the battery module 10 related to the location of the battery module 10.

For example, the system 1 may communicate to the user information about the low charge of the battery module 10 and a fully charged battery module 10 located nearby. Based on this information, the user can find a fully charged battery module 10 (for example, at a neighbor's house or a local store) and replace the discharged battery module 10. Additionally, the user may manipulate the user interface within the computing devices (CD) to communicate to a second user associated with the fully charged battery module 10 that the first user needs the fully charged battery module 10, and the second user may The user may be provided with the opportunity to accept or refuse to exchange the battery module 10 with a low charge for a fully charged battery module 10.

In another example, when it is detected that the battery module 10 has a low charge, the system 1 can automatically communicate information about a nearby fully charged battery module 10 to the user. Based on the information, the user can find a fully charged battery module 10 and replace the discharged battery module 10. Additionally, when it is detected that the battery module 10 has a low charge, the system 1 automatically informs the second user associated with the fully charged battery module 10 that the first user needs the fully charged battery module 10. and may provide the second user with an opportunity to accept or reject the replacement of the fully charged battery module 10 with the first user.

In another example, a user may communicate travel plans along the route of a battery-powered vehicle (PD-V) using a user interface of computing devices (CD). Upon receiving the travel plans, system 1 may calculate appropriate locations along the route (e.g., based on the remaining charge of battery module 10) and place depleted battery modules 10 in a charged state. One or more locations of battery modules 10 along a route available to a user for exchanging battery modules 10 may be communicated.

In another example, a user whose home may be powered by one or more battery modules 10 (e.g., due to a residential power grid outage) may determine the charge of one or more of the battery modules 10. If this is low, you may find yourself in a situation where you don't have enough charge to power your home or at least essential devices. A user may use the user interface of the computing devices (CD) to find nearby battery modules 10 that are charged and replaceable.

These and other scenarios are possible due to the features of the battery-centric virtual grid (VG) of this disclosure.

Exemplary methods may be better understood with reference to the flow diagram of FIG. 3. For simplicity of explanation, the illustrated methodologies are shown and described as a series of blocks; however, some blocks may occur in different orders than shown and described or concurrently with other blocks, so the methodologies are organized by order of the blocks. You must understand that there are no restrictions. Additionally, to implement an example methodology, fewer blocks than all of the blocks illustrated may be needed. Additionally, additional methodologies, alternative methodologies, or both may use additional blocks not illustrated.

In flow diagrams, blocks represent “processing blocks” that can be implemented in logic. Processing blocks may represent method steps or device elements for performing method steps. Flow diagrams do not depict the syntax for any particular programming language, methodology, or style (e.g., procedural, object-oriented). Rather, the flow diagrams illustrate functional information that a person of ordinary skill in the art or artificial intelligence (AI) could use to develop logic to perform the illustrated processes. It will be appreciated that in some examples program elements such as temporary variables, routine loops, etc. are not displayed. It is further noted that electronic and software applications may involve dynamic and flexible processes, so the illustrated blocks may be performed in different sequences than those shown, or the blocks may be combined or separated into multiple components. It will be understood as It will be appreciated that these processes may be implemented using various programming approaches, such as machine language, procedural, object-oriented, or artificial intelligence or machine learning techniques.

FIG. 3 illustrates a flow diagram for an example method 300 for a battery-centric virtual grid (VG) system. At 310, method 300 includes obtaining performance information from one or more battery cells that are part of a battery module. At 320, method 300 includes the battery module wirelessly transmitting data including performance information. At 330, method 300 includes receiving data from an individual device powered by a battery module. In one embodiment, data from individual devices is derived from performance information. At 340, method 300 includes remotely receiving data including performance information and data from an individual device, such that the individual device becomes part of an IOT network through an individual battery module. At 350, method 300 includes determining characteristics of individual devices driven by each of the battery modules of the plurality of battery modules based on performance information of the individual battery module. In one embodiment, method 300, at 360, communicates portions of performance information of a battery module or portions of data from an individual device powered by the battery module related to the location of the battery module.

FIG. 4 illustrates a block diagram of an example computing environment 400 that may be used to deploy battery module 10 or remote server 32 of the present disclosure. Environment 400 includes a processor 402 (e.g., processor 14), memory 404, and I/O ports 410 operably coupled by bus 408. Environment 400 may include a database 30 or may communicate with database 30 via the cloud (CL).

Processor 402 (e.g., processor 14) may be a variety of processors, including dual microprocessors and other multi-processor architectures. Memory 404 may include volatile memory or non-volatile memory. Non-volatile memory may include (but is not limited to) ROM, PROM, EPROM, EEPROM, etc. Volatile memory may include, for example, RAM, synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

Storage 406 may be operably coupled to environment 400, for example, through I/O interfaces (e.g., card, device) 418 and I/O ports 410. Storage 406 includes, but is not limited to, devices such as magnetic disk drives, solid state disk drives, floppy disk drives, tape drives, zip drives, flash memory cards, or memory sticks. Storage 406 may also include optical drives, such as a CD-ROM, CD-recordable drive (CD-R drive), CD-rewritable drive (CD-RW drive), or digital video ROM drive (DVD ROM). . Memory 404 may store processes 414 or data 416, for example. Storage 406 or memory 404 may store an operating system that controls and allocates resources of environment 400. Database 30 may reside in storage 406 .

Bus 408 may be a single internal bus interconnect architecture or other bus or mesh architectures. Although a single bus is illustrated, environment 400 may use other buses not illustrated (e.g., PCIE, SATA, Infiniband, 1394, USB, Ethernet) to support various devices, logic, and You must be able to understand that you can communicate with devices and peripheral devices. Bus 408 can be of various types, including, but not limited to, a memory bus or memory controller, a peripheral bus or external bus, a crossbar switch, or a local bus. Local buses include the Industry Standard Architecture (ISA) bus, Microchannel Architecture (MCA) bus, Extended ISA (EISA) bus, Peripheral Component Interconnect (PCI) bus, Universal Serial (USB) bus, and Small Computer Systems Interface (SCSI) bus. ) can be of various types, including (but not limited to) buses.

Environment 400 can interact with input/output devices through I/O interfaces 418 and I/O ports 410. Input/output devices may include (but are not limited to) keyboards, microphones, pointing and selection devices, cameras, video cards, displays, storage 406, network devices 420, etc. I/O ports 410 may include (but are not limited to) serial ports, parallel ports, and USB ports.

Environment 400 (and battery module 10) may operate in a network environment, and thus may be connected to network devices 420 via I/O interfaces 418 or I/O ports 410. there is. Through network devices 420, environment 400 can interact with a network, such as the Internet or the cloud (CL). Via a network, environment 400 may be logically connected to remote computers, including, for example, a file server or network computer hosting database 30. Networks with which environment 400 may interact may include (but are not limited to) local area networks (LANs), wide area networks (WANs), and other networks. Network devices 420 include fiber-optic distributed data interface (FDDI), copper distributed data interface (CDDI), Ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communications (IEEE 802.11), and Bluetooth (IEEE 802.15.1). ), ZigBee (IEEE 802.15.4), etc. Similarly, network devices 420 include point-to-point links, circuit switching networks, such as integrated services digital networks (ISDN), packet switching networks, satellite communications, and digital subscriber lines (DSL). However, it is not limited thereto) and can connect to WAN technologies. Although individual network types are described, it should be understood that communications to, through, or through a network may include combinations and mixtures of communications.

definitions

The following includes definitions of selected terms used in this specification. These definitions include various examples or types of components that fall within the scope of the term and that may be used for implementation. The examples are not intended to be limiting. Both singular and plural forms of terms may be included in definitions.

An “operable connection” or a connection through which entities are “operably connected” is a connection capable of transmitting or receiving signals, physical communications, or logical communications. Typically, operable connections include physical interfaces, electrical interfaces, or data interfaces; however, it should be noted that operable connections may include different combinations of these or other types of connections sufficient to allow operable control. . For example, two entities may be operably coupled by being able to communicate signals with each other, either directly or through one or more intermediate entities, such as a processor, operating system, logic, software, or other entity. Logical or physical communication channels can be used to create a workable connection.

When the term “includes” or “including” is used in the description or claims, that term is to be construed as “comprising” when used as a transition word in the claims. It is intended to be inclusive in a similar way to the term . Additionally, when the term “or” is used in the description or claims (e.g., A or B), it is intended to mean “A or B or both.” will be. If applicants wish to indicate "only A or B but not both," the term "only A or B but not both" will use Accordingly, the use of the term “or” in this specification is an inclusive use, not an exclusive use. See also [Bryan A. Garner, A Dictionary of Modern Legal Usage 624 (2d. Ed. 1995)].

Although exemplary systems, methods, etc. have been illustrated by way of illustration, and the examples have been described in considerable detail, it is not Applicants' intention to limit or in any way limit the scope to such details. Of course, it is not possible to describe every combination of components or methodologies that could be assumed to describe the systems, methods, etc. described herein. Additional advantages and modifications will be readily apparent to those skilled in the art. Accordingly, the invention is not limited to the specific details, representative devices and illustrative examples shown and described. Accordingly, this application is intended to embrace changes, modifications and variations that fall within the scope of the appended claims. Additionally, the foregoing description is not intended to limit the scope of the present invention. Rather, the scope of the invention should be determined by the appended claims and their equivalents.

Claims (22)

As a battery-centric virtual grid (VG) system,
A plurality of battery modules - each battery module from the plurality of battery modules:
One or more battery cells totaling at least 1 kWh,
one or more modular processors operably coupled to the one or more battery cells to obtain performance information from the one or more battery cells;
a wireless transmitter operably connected to the one or more module processors and configured to remotely transmit data including the performance information; and
An enclosure that at least partially includes the one or more battery cells, the one or more module processors, and the wireless transmitter, and includes a handle for a user to grasp to carry the battery module weighing 40 lbs or less.
Contains -; and
A remote server configured to receive data including the performance information, wherein the remote server or the one or more module processors are configured to identify individual devices driven by each of the battery modules of the plurality of battery modules based on the performance information. ―
A battery-centric virtual grid (VG) system including. In claim 1,
The remote server or the one or more module processors are configured to determine characteristics of individual devices powered by each of the battery modules of the plurality of battery modules based on the performance information. In claim 1,
Includes a user interface,
The remote server or the one or more module processors are configured to determine characteristics of individual devices driven by each of the battery modules of the plurality of battery modules based on the performance information, and the user interface is configured to allow users of the system to A battery-centric virtual grid (VG) system configured to communicate some of the above characteristics to a battery-centric virtual grid (VG) system. In claim 1,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and the user interface is configured to display performance information of one or more battery modules from the plurality of battery modules. A battery-centric virtual grid (VG) system, configured to communicate portions to users of the system regarding the location. In claim 1,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and when the user interface detects that the battery module has a low charge, the plurality of battery modules A battery-centric virtual grid (VG) system configured to communicate one or more nearby locations of battery modules with medium or low charge. In claim 1,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the respective battery module, and the user interface includes a first battery module from the plurality of battery modules associated with a first user. When detecting that the charge level is low, the first user communicates to the second user associated with a second battery module whose charge level is not low among the plurality of battery modules that the first user needs a second battery, and to the second user. A battery-centric virtual grid (VG) system, configured to provide an opportunity to accept or reject sharing of the second battery. In claim 1,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and the user interface is configured to, upon receiving travel plans along the route of the vehicle, locate a location along the route. , A battery-centric virtual grid (VG) system configured to communicate one or more locations of battery modules from a plurality of battery modules. In claim 1,
The wireless or wired transmitter is configured to establish data communication with an individual device to which the individual battery module supplies power, and the wireless transmitter is configured to remotely transmit data from the individual device, whereby the wireless transmitter is configured to remotely transmit data from the individual device. A battery-centric virtual grid (VG) system in which each device becomes part of an IOT network through its respective battery module. As a battery-centric virtual grid (VG) system,
A plurality of battery modules - each battery module from the plurality of battery modules:
one or more battery cells,
one or more modular processors operably coupled to the one or more battery cells to obtain performance information from the one or more battery cells;
a wireless transceiver operably connected to the one or more module processors and configured to remotely transmit data including the performance information;
At least partially comprising the one or more battery cells, the one or more module processors, and the wireless transmitter, and comprising a handle for a user to hold to carry the battery module, and the wireless transceiver or wired transceiver is configured to include the plurality of batteries. An enclosure configured to receive data from individual devices powered by battery modules from the modules.
Contains -; and
remote server
Includes,
The remote server is,
network connection, and
operably connected to the network connection and to receivers for receiving data including the performance information and data from the individual devices, such that the individual devices become part of an IOT network through the individual battery modules. remote server
A battery-centric virtual grid (VG) system including. In claim 9,
The remote server or the one or more module processors determine characteristics of the individual devices driven by each of the battery modules of the plurality of battery modules based on the performance information and data from the individual devices derived from the performance information. A battery-centric virtual grid (VG) system configured to determine the In claim 9,
Includes a user interface,
The remote server or the one or more module processors are configured to determine characteristics of individual devices driven by each of the battery modules of the plurality of battery modules based on the performance information, and the user interface is configured to allow users of the system to A battery-centric virtual grid (VG) system configured to communicate some of the above characteristics to a battery-centric virtual grid (VG) system. In claim 9,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and the user interface is configured to display performance information of one or more battery modules from the plurality of battery modules. A battery-centric virtual grid (VG) system configured to communicate portions or portions of data from an individual device powered by a battery module from the plurality of battery modules associated with the location. In claim 9,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and when the user interface detects that the battery module has a low charge, the plurality of battery modules A battery-centric virtual grid (VG) system configured to communicate one or more nearby locations of battery modules with medium or low charge. In claim 9,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the respective battery module, and the user interface is configured to display a first battery from the plurality of battery modules associated with a first user. When detecting that the charge of the module is low, the first user communicates that the second battery is needed to a second user associated with a second battery module whose charge is not low among the plurality of battery modules, and the second user A battery-centric virtual grid (VG) system, configured to provide an opportunity to accept or reject sharing of the second battery. In claim 9,
Includes a user interface,
Each battery module from the plurality of battery modules includes a GPS receiver configured to communicate the location of the individual battery module, and the user interface is configured to, upon receiving travel plans along the route of the vehicle, locate a location along the route. , A battery-centric virtual grid (VG) system configured to communicate one or more locations of battery modules from the plurality of battery modules. As a battery-centric virtual grid (VG) system,
multiple modules
Includes,
Each module from the plurality of modules:
One or more battery cells totaling at least 1 kWh,
one or more modular processors operably coupled to the one or more battery cells to obtain performance information from the one or more battery cells;
One or more transceivers operably connected to the one or more module processors, the one or more module processors configured to configure individual devices driven by individual modules from the plurality of modules based on the individual performance information. configured to identify and determine characteristics of individual devices driven by an individual module from a plurality of modules based on the performance information, or data from an individual device driven by a module from the plurality of modules. configured to receive, wherein the one or more transceivers are configured to remotely receive and transmit data such that the respective device becomes part of an IOT network through the respective module; and
An enclosure at least partially containing the one or more battery cells, the one or more module processors, and the one or more transceivers, wherein the module weighs less than 40 lbs, and the enclosure includes a handle for a user to grasp to carry the module. Includes ―
A battery-centric virtual grid (VG) system including. In claim 16,
A battery-centric virtual grid (VG) system, comprising a remote server operably coupled to receivers to receive data including the performance information or data from the individual device. In claim 17,
Includes a user interface,
The remote server or the one or more module processors are configured to determine characteristics of individual devices driven by each of the modules of the plurality of modules based on the performance information, and the user interface is configured to provide the user of the system with the A battery-centric virtual grid (VG) system configured to communicate some of the characteristics. In claim 17,
Includes a user interface,
Each module from the plurality of modules includes a GPS receiver configured to communicate the location of the individual module, and the user interface includes portions of performance information of one or more modules from the plurality of modules or the location. A battery-centric virtual grid (VG) system configured to communicate portions of data from an individual device driven by a module from the plurality of modules associated with a battery-centric virtual grid (VG) system. In claim 17,
Includes a user interface,
Each module from the plurality of modules includes a GPS receiver configured to communicate the location of the individual module, and when the user interface detects that the charge level of the module is low, the charge level of any of the plurality of modules is not low. A battery-centric virtual grid (VG) system configured to communicate one or more nearby locations of modules. In claim 17,
Includes a user interface,
Each module from the plurality of modules includes a GPS receiver configured to communicate the location of the respective module, and the user interface is configured to display a lower charge level of a first module from the plurality of modules associated with a first user. When detecting that the first user needs a second battery, it communicates to the second user associated with the second module with a not low charge among the plurality of modules, and allows the second user to share the second battery. A battery-centric virtual grid (VG) system configured to provide an opportunity to accept or reject. In claim 17,
Includes a user interface,
Each module from the plurality of modules includes a GPS receiver configured to communicate the location of the respective module, and the user interface receives travel plans along the route of the vehicle located along the route. A battery-centric virtual grid (VG) system, configured to communicate one or more locations of modules from modules of.

Images