DESC:CROSS REFERENCE TO RELATED APPLICATION
This Application is based on and derives the benefit of Indian Provisional Application IN202321032913 filed on 9th May 2023, the contents of which are incorporated herein by reference.

TECHNICAL FIELD
[001] Embodiments disclosed herein relate to Zinc ion rechargeable batteries (ZIRB), and more particularly to charging and discharging profiles for ZIRBs.

BACKGROUND
[002] The conventional charge and discharge profile for lead acid batteries and lithium-ion batteries which are used in applications (examples of the application can be, but not limited to, Uninterruptible Power Supplies (UPSs), inverters, and so on) are unreliable and unsuitable for ZIRBs, due to the unique chemistry of the ZIRBs. Commercial UPSs and inverters have charging profiles like constant current-constant voltage and float voltage, absorption-based lead- acid chemistry, and lithium-ion chemistries. When using commercial UPS and inverters with the available charging protocols, performance of ZIRBs (including capacity and life cycle) can drastically drop.
[003] Hence, there is a need in the art for solutions which will overcome the above-mentioned drawback(s), among others.

OBJECTS
[004] The principal object of embodiments herein is to disclose methods and systems for improving the charging performance of Zinc ion rechargeable batteries (ZIRBs), wherein a charging and discharging profile for the ZIRBs are disclosed, which can be applicable to a plurality of battery configurations and serial and parallel connections and combinations.
[005] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF FIGURES
[006] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:
[007] FIG. 1 depicts a system for controlling the charging and/or discharging a ZIRB, according to embodiments as disclosed herein;
[008] FIG. 2 depicts one or more components of the controller, according to embodiments as disclosed herein;
[009] FIG. 3 is a flowchart depicting the process of managing charging and discharge of a ZIRB, according to embodiments as disclosed herein; and
[0010] FIG. 4 is an example flowchart depicting the process of managing charging and discharge of a ZIRB, according to embodiments as disclosed herein.

DETAILED DESCRIPTION
[0011] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0012] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.
[0013] The words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.
[0014] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
[0015] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts/sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components/modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0016] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components/elements/steps is for the purposes of this description and should not be construed as sequential ordering/placement/occurrence unless specified otherwise.
[0017] The embodiments herein achieve methods and systems for improving the charging performance of Zinc ion rechargeable batteries (ZIRBs), wherein a charging and discharging profile for the ZIRBs are disclosed, which can be applicable to a plurality of battery configurations and serial and parallel connections and combinations. Referring now to the drawings, and more particularly to FIGS. 1 through 4, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0018] FIG. 1 depicts a system 100 for controlling the charging and/or discharging of a ZIRB 102. The system 100, as depicted, comprises a controller 101, and at least one ZIRB 102. In an embodiment herein, the controller 101 can be a dedicated unit, which can be connected to the ZIRB 102 using at least one of a wired connection means (such as, but not limited to, a power cable). In an embodiment herein, the controller 101 can be integrated within another unit (such as an inverter or any other unit which can control the charging and/or discharging the ZIRB 102), which can be connected to the ZIRB 102 using at least one of a wired connection means (such as, but not limited to, a power cable). In an embodiment herein, the controller 101 can be integrated with the ZIRB 102. In an embodiment herein, the controller 101 can be connected to a plurality of ZIRBs 102, wherein the controller 101 can control the plurality of ZIRBs 102.
[0019] The at least one ZIRB 102 can be rechargeable Zn-ion batteries. In an example herein, the at least one ZIRB 102 can be Zinc-Manganese Dioxide (Zn-MnO2) battery(ies). In an example herein, the at least one ZIRB 102 can operate from 0V to 2V. In an example herein, the at least one ZIRB 102 can operate from 0V to 1.75V. The at least one ZIRB 102 can be in various battery configurations, such as, but not limited to, 12V, 24V, and so on. The at least one ZIRB 102 can be configured in at least one of a series combination or a parallel combination.
[0020] The controller 101 can apply a constant current (CC) to the at least one ZIRB 102 to raise the voltage in steps to a pre-defined voltage level. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.5C Amperes (A), 0.33C A, 0.25C A, 0.2C A, 0.125C A, and 0.08C A. In an embodiment herein, C is the rated capacity of the battery (i.e., the ZIRB 102). In an embodiment herein, the pre-defined voltage level can be the maximum operating voltage of the at least one ZIRB 102. In an example herein, the controller 101 can apply a constant current of 0.25C A to the at least one ZIRB 102 to raise the voltage from 1.55V/cell to 1.65V/cell, to 1.7V/cell, wherein 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102.
[0021] On the at least one ZIRB 102 reaching the pre-defined voltage level, then the controller 101 can cut the current flow, so that the voltage of the at least one ZIRB 102 drops from the pre-defined voltage level to a lower threshold voltage value naturally. The threshold value can be the voltage at which the voltage drop is minimum when compared with continuous cycles. In an example herein, consider that the pre-defined voltage level (i.e., the maximum operating voltage) of the at least one ZIRB 102 is 1.7V. On the voltage of the at least one ZIRB 102 reaching 1.7V, the controller 101 can cut the current flow, so that the voltage of the at least one ZIRB 102 drops from 1.7V/cell to 1.6V/cell in steps of 1.7V -> 1.65V -> 1.6V.
[0022] On the at least one ZIRB 102 reaching the lower threshold voltage value, then the controller 101 can apply the half of the constant current (CC/2) to the at least one ZIRB 102 to raise the voltage in steps from the lower threshold voltage value to the maximum operating voltage. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.25C A, 0.16C A, 0.125C A, 0.1C A, and 0.0625C A respectively. In an example herein, the controller 101 can apply a constant current of 0.125C A to the at least one ZIRB 102 to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell, wherein 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102 and the controller 101 had applied a constant current of 0.25C A to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell previously.
[0023] The controller 101 can perform the above steps, after every discharge condition and even on non-discharge condition.
[0024] FIG. 2 depicts one or more components of the controller 101. The controller 101, as depicted, comprises a processor 201, at least one memory module 202, and at least one communication module 203. The processor 201 can be coupled with the communication module 203 and the memory module 202.
[0025] The processor 201 can be implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.
[0026] The processor 201 may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). The processor 201 may include multiple cores and is configured to execute the instructions stored in the memory module 202.
[0027] Further, the processor 201 is configured to execute instructions stored in the memory module 202 and to perform various processes. The communication module 203 can be configured for communicating internally between internal hardware components of the controller 101, and with external devices (such as one or more ZIRBs 102) via one or more networks. The memory module 202 also stores instructions to be executed by the processor 201. The memory module 202 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory module 202 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory module 202 is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
[0028] The processor 201 can apply a constant current (CC) to the at least one ZIRB 102 to raise the voltage in steps to the pre-defined voltage level. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.5C A, 0.33C A, 0.25C A, 0.2C A, 0.125C A, and 0.08C A. In an embodiment herein, the pre-defined voltage level can be the maximum operating voltage of the at least one ZIRB 102. In an example herein, the processor 201 can apply a constant current of 0.25C A to the at least one ZIRB 102 to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell, wherein 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102. ‘C’ is the rated capacity of the at least one ZIRB 102.
[0029] On the at least one ZIRB 102 reaching the pre-defined voltage level, then the processor 201 can cut the current flow, so that the voltage of the at least one ZIRB 102 drops from the pre-defined voltage level to a lower threshold voltage value naturally. In an example herein, consider that the pre-defined voltage level is 1.7V. On the voltage of the at least one ZIRB 102 reaching 1.7V, the processor 201 can cut the current flow, so that the voltage of the at least one ZIRB 102 drops from 1.7V/cell to 1.6V/cell in steps of 1.7V -> 1.65V -> 1.6V.
[0030] On the at least one ZIRB 102 reaching the lower threshold voltage value of the at least one ZIRB 102, then the processor 201 can apply the half of the constant current (CC/2) to the at least one ZIRB 102 to raise the voltage in steps from the lower threshold voltage value to the maximum operating voltage. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.25C A, 0.16C A, 0.125C A, 0.1C A, 0.0625C A respectively. In an example herein, the controller 101 can apply a constant current of 0.125C A to the at least one ZIRB 102 to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell, wherein 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102 and the processor 201 had applied a constant current of 0.25C A to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell previously.
[0031] The processor 201 can perform the above steps, after every discharge condition and even on non-discharge condition.
[0032] Although FIG. 2 shows various hardware components of the controller 101, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the controller 101 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the embodiments disclosed herein. One or more components can be combined together to perform the same or substantially similar function(s) in the controller 101.
[0033] FIG. 3 is a flowchart depicting the process 300 of managing charging and discharge of a ZIRB 102. In step 301, the controller 101 applies a constant current (CC) to the at least one ZIRB 102 to raise the voltage in steps to the pre-defined voltage level. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.5C A, 0.33C A, 0.25C A, 0.2C A, 0.125C A, and 0.08C A. In an embodiment herein, the pre-defined voltage level can the maximum operating voltage of the at least one ZIRB 102. On the at least one ZIRB 102 reaching the pre-defined voltage level, in step 302, the controller 101 cuts the current flow, so that the voltage of the at least one ZIRB 102 drops from the pre-defined voltage level to a lower threshold voltage value naturally. On the at least one ZIRB 102 reaching the lower threshold voltage value of the at least one ZIRB 102, in step 303, the controller 101 applies the half of the constant current (CC/2) to the at least one ZIRB 102 to raise the voltage in steps from the lower threshold voltage value to the maximum operating voltage. In an embodiment herein, the constant current that can be applied can be, but not limited to, 0.25C A, 0.16C A, 0.125C A, 0.1C A, and 0.0625C A respectively. The controller 101 performs the above steps, after every discharge condition and even on non-discharge condition. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.
[0034] FIG. 4 is an example flowchart depicting the process 400 of managing charging and discharge of a ZIRB 102. In step 401, the controller 101 can applies a constant current of 0.25C A to the at least one ZIRB 102 to raise the voltage from 1.6V/cell to 1.65V/cell, to 1.7V/cell, wherein 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102. 1.7V/cell is the maximum operating voltage of the at least one ZIRB 102. On the at least one ZIRB 102 reaching 1.7V/cell, in step 402, the controller 101 cuts the current flow, so that the voltage of the at least one ZIRB 102 drops from 1.7V/cell to 1.6V/cell in steps of 1.7V -> 1.65V -> 1.6V naturally. On the at least one ZIRB 102 reaching the lower threshold voltage value of the at least one ZIRB 102, in step 403, the controller 101 applies a constant current (0.125C A) to the at least one ZIRB 102 to raise the voltage in steps from 1.6V/cell to 1.65V/cell, to 1.7V/cell. The controller 101 performs the above steps, after every discharge condition and even on non-discharge condition. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
[0035] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0036] The embodiments disclosed herein describe methods and systems for improving the charging performance of Zinc ion rechargeable batteries (ZIRBs), wherein a charging and discharging profile for the ZIRBs are disclosed, which can be applicable to a plurality of battery configurations and serial and parallel connections and combinations. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high-speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.
[0037] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.
,CLAIMS:We claim:

1. A method (300) for controlling the charging of a Zinc ion rechargeable battery (ZIRB) (102), the method (300) comprising:
applying (301), by a controller (101), a constant current to the ZIRB (102) to raise voltage of the ZIRB (102) in a plurality of steps to a pre-defined voltage level;
cutting (302), by the controller (101), the constant current, on the ZIRB (102) reaching the pre-defined voltage level, wherein the voltage of the ZIRB (102) drops from the pre-defined voltage level to a lower threshold voltage value; and
applying, by the controller (101), a half of the constant current to the ZIRB (102), on the voltage of the ZIRB (102) reaching the lower threshold voltage value.

2. The method, as claimed in claim 1, wherein the controller (101) applies 0.5C Amperes (A), 0.33C A, 0.25C A, 0.2C A, 0.125C A, and 0.08C A as the constant current, wherein C is rated capacity of the ZIRB (102).

3. The method, as claimed in claim 1, wherein the pre-defined voltage level is the maximum operating voltage of the at least one ZIRB (102).

4. The method, as claimed in claim 1, wherein the method comprises controlling, by the controller (101), charging of the ZIRB (102), after every discharge condition and even on non-discharge condition.

5. A controller (101) comprising:
a processor (201);
at least one memory module (202); and
at least one communication module (203),
wherein the processor (201) is coupled with the at least one memory module (202), and the at least one communication module (203), wherein the processor (201) is configured to:
apply a constant current to a Zinc ion rechargeable battery (ZIRB) (102) to raise voltage of the ZIRB (102) in a plurality of steps to a pre-defined voltage level;
cut the constant current, on the ZIRB (102) reaching the pre-defined voltage level, wherein the voltage of the ZIRB (102) drops from the pre-defined voltage level to a lower threshold voltage value; and
apply a half of the constant current to the ZIRB (102), on the voltage of the ZIRB (102) reaching the lower threshold voltage value.

6. The controller (101) as claimed in claim 5, wherein the processor (201) is configured to apply 0.5C Amperes (A), 0.33C A, 0.25C A, 0.2C A, 0.125C A, and 0.08C A as the constant current, wherein C is rated capacity of the ZIRB (102).

7. The controller (101) as claimed in claim 5, wherein the pre-defined voltage level is the maximum operating voltage of the at least one ZIRB (102).

8. The controller (101) as claimed in claim 5, wherein the processor (201) is configured to control charging of the ZIRB (102), after every discharge condition and even on non-discharge condition.

Dated this 8th day of May 2023

Gitanjali Bhatnagar
Deputy General Manager
Godrej & Boyce Mfg. Co. Ltd.