DESC:CROSS-REFERENCE TO RELATED APPLICATIONS
The present application is based on and claims priority from an Indian Provisional Application Number 202441045271 filed on 12-06-2024, the disclosure of which is hereby incorporated by reference herein.
BACKGROUND
Technical Field
The embodiments herein generally relate to managing one or more firmware updates of a vehicle, and more particularly, to a system and method to manage the one or more firmware updates of the vehicle in operation.
Description of the Related Art
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
Nowadays, electric vehicle manufacturers have introduced one or more battery packs to reduce range anxiety and enhance range of their electric vehicles. The one or more battery packs include one or more Battey Management Systems (BMS) to manage the one or more battery packs.
The electric vehicle manufacturers often replace existing firmware packages (that are currently running on the one or more BMSs) with one or more new firmware packages. The one or more new firmware packages are objected to fixing bugs and adding/improving features. In addition to that, the one or more new firmware packages can also fix bugs that could cause safety and performance issues. Updating the one or more BMSs is important because it can improve the performance of the one or more BMSs in specific, and the electric vehicle as a whole.
In a conventional approach, updating the one or more BMSs includes a verification process, a download process, and an installation process. Downloading and installing the one or more new firmware packages will be a time-consuming and complicated process. At the same time, the user cannot perform the installation process of the one or more new firmware packages while the electric vehicle is in running condition which will increase the downtime of the electric vehicle.
Accordingly, there remains a need for an improved system and method to manage one or more firmware updates of the vehicle in operation.
SUMMARY
It will be understood that this disclosure is not limited to the particular systems, and methodologies described, as there can be multiple possible embodiments of the present disclosure which are not expressly illustrated in the present disclosure. It is also to be understood that the terminology used in the description is to describe the particular versions or embodiments only, and is not intended to limit the scope of the present disclosure.
Accordingly, embodiments herein disclose a system to manage one or more firmware updates on a vehicle in operation. The system includes a server and a vehicle. The vehicle includes at least two battery packs, a server, an interaction unit, and a controller unit. The at least two battery packs distribute power to the vehicle and include at least two BMSs. The server is configured to generate one or more firmware update notifications upon identifying the one or more firmware updates. The server is configured to transmit the one or more firmware update notifications to an interaction unit. The one or more firmware updates correspond to one or more vehicle information that is received from the interaction unit. The interaction unit includes a processor, a memory, and is configured to download the one or more firmware updates upon receiving the one or more firmware update notifications from the server via a wireless communication network. The interaction unit is configured to collect the one or more vehicle information from the vehicle. The interaction unit is configured to transfer the one or more vehicle information to the server. The interaction unit is configured to generate a trigger signal to turn a controller unit into an install mode when one or more battery parameters of the at least two battery packs are equal to or higher than a predetermined value. The interaction unit is configured to transmit the trigger signal to the controller unit. The controller unit is configured to receive the trigger signal from the interaction unit and check whether one or more preconditions are true or not. The controller unit is configured to turn into the install mode and transfer a positive acknowledgment signal to the interaction unit when the one or more preconditions are true, else transfer a negative acknowledgment signal to the interaction unit. The controller unit transfers the positive acknowledgment signal to the interaction unit to receive the one or more firmware updates on the at least two BMSs. The controller unit detects at least one passive BMS and an active BMS from the at least two BMSs in real time to install the one or more firmware updates on the at least one passive BMS. The controller unit switches the power distribution among the at least two battery packs. The controller unit detects at least one passive BMS and an active BMS from the at least two BMSs in real-time to install the one or more firmware updates on the at least one passive BMS.
In some embodiments, the one or more vehicle information includes a model of the vehicle and a variant and version of the vehicle.
In some embodiments, the one or more battery parameters include a state of charge of the at least two battery packs or one or more temperature levels of the at least two battery packs.
In some embodiments, the one or more preconditions include at least one of availability of the at least two battery packs, availability of switching, availability of communication between the control unit and the at least two BMSs, and one or more driver behaviors.
In some embodiments, the controller unit is configured to restart the at least one passive BMS when the installation of the one or more firmware updates is completed.
In some embodiments, the interaction unit includes a Human Machine Interface (HMI), an Internet of Things (IoT) device, or a user computing device. The interaction unit is communicatively connected to the vehicle, and the server.
In some embodiments, the one or more firmware updates include a set of instructions corresponding to the at least two BMSs, and the controller unit.
In one aspect, a method for managing one or more firmware updates on a vehicle in operation. The method includes generating, by a server, one or more firmware update notifications upon identifying the one or more firmware updates. The one or more firmware updates correspond to one or more vehicle information that is received from the interaction unit. The method includes transmitting, by the server, the one or more firmware update notifications to an interaction unit. The method includes downloading, by the interaction unit, the one or more firmware updates upon receiving the one or more firmware update notifications from the server via a wireless communication network. The method includes collecting, by the interaction unit, the one or more vehicle information from the vehicle.
The method includes transferring, by the interaction unit, the one or more vehicle information to the server. The method includes generating, by the interaction unit, a trigger signal to turn a controller unit into an install mode when one or more battery parameters of at least two battery packs are equal to or higher than a predetermined value. The method includes transmitting, by the interaction unit the trigger signal to the controller unit. The method includes receiving, by the controller unit, the trigger signal from the interaction unit. The method includes checking, by the controller unit, whether one or more preconditions are true or not. The method includes turning, by the control unit, into the install mode and transferring a positive acknowledgment signal to the interaction unit when the one or more preconditions are true. The method includes transferring, by the controller unit, the positive acknowledgment signal to the interaction unit to receive the one or more firmware updates on the at least two BMSs. The method includes detecting, by the controller unit at least one passive BMS and an active BMS from the at least two BMSs in real time to install the one or more firmware updates on the at least one passive BMS. The method includes switching, by the controller unit, the power distribution among the at least two battery packs. The method includes detecting, by the controller unit, at least one passive BMS and an active BMS from the at least two BMSs in real-time install the one or more firmware updates on the at least one passive BMS.
In some embodiments, the one or more vehicle information includes a model of the vehicle and a variant and version of the vehicle.
In some embodiments, one or more battery parameters include a state of charge of the at least two battery packs or one or more temperature levels of the at least two battery packs.
In some embodiments, the one or more preconditions include at least one of availability of the at least two battery packs, availability of switching, availability of communication between the control unit and the at least two BMSs, and one or more driver behaviors.
In some embodiments, the wherein the controller unit is configured to restart the at least one passive BMS when the installation of the one or more firmware updates is completed.
In some embodiments, the interaction unit includes a Human Machine Interface (HMI), an Internet of Things (IoT) device, or a user computing device. The interaction unit is communicatively connected to the vehicle, and the server.
In some embodiments, one or more firmware updates include a set of instructions corresponding to the at least two BMSs, and the controller unit.
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 preferred embodiments 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 THE DRAWINGS
This invention is 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 drawings, in which:
FIG. 1A and 1B illustrate a system to manage one or more firmware updates of a vehicle in operation in accordance with an embodiment of the present disclosure; and
FIG. 2A and 2B illustrate a method for managing one or more firmware updates of the vehicle in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
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.
As mentioned, there remains a need for an improved system to manage one or more firmware updates of the vehicle in operation. Referring now to the drawings, and more particularly FIGS. 1A, 1B, 2A, and 2B, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
FIG. 1A and 1B illustrate a system 100 to manage one or more firmware updates on a vehicle 102 in operation in accordance with an embodiment of the present disclosure. Referring to the FIG. 1, the system 100 includes a server 104, and the vehicle 102. The vehicle 102 includes an interaction unit 106, a controller unit 108, at least two battery packs 110, and a load 112. The at least two battery packs 110 includes at least two BMSs 118.
In one embodiment, the at least two battery packs 110 include a first battery pack 114 with a first capacity, and a second battery pack 116 with a second capacity. In another embodiment, the at least two BMSs 118 include a first BMS 120 and a second BMS 122. In yet another embodiment, the first battery pack 114 includes the first BMS 120. The second battery pack 116 includes the second BMS 122. In one embodiment, the first battery pack 114 and the second battery pack 116 may have equal capacities. In another embodiment, the first battery pack 114 and the second battery pack 116 may have different capacities. In yet another embodiment, the first battery pack 114 may be fixed. In yet another embodiment, the first battery pack 114 may be portable. In yet another embodiment, the second battery pack 116 may be fixed. In yet another embodiment, the second battery pack 116 may be portable. In yet another embodiment, the both first battery pack 114 and the second battery pack 116 are fixed battery packs. In yet another embodiment, the both first battery pack 114 and the second battery pack 116 are portable battery packs.
The at least two battery packs 110 configured to distribute power to the load 112, and a subsystem of the vehicle 102. The load 112 is configured to propel the vehicle 102. In one embodiment, the vehicle 102 may include, but not limited to, an electric vehicle. In another embodiment, the electric vehicle may include, but limited to, a Battery Electric Vehicle (BEV), a Hybrid Electric Vehicle (HEV), a Plug-in Hybrid Electric Vehicle (PHEV), and a Fuel Cell Electric Vehicle (FCEV). The load 112 may include an electric motor and the like.
The interaction module 106 is connected to the server 104. In one embodiment, the interaction module 106 is communicatively connected to the server 104 using a wireless communication network. In another embodiment, the wireless communication network may include, but not limited to, a light fidelity, (Li-Fi) network, a wireless fidelity (Wi-Fi) network, a wide area network (WAN), a metropolitan area network (MAN), a satellite network, the Internet, a coaxial cable network, an infrared (IR) network, Bluetooth, a fiber optic network, (RF) network, a local area network (LAN), a radio frequency, and a combination thereof. In yet another embodiment, the server 104 may be a cloud.
The vehicle manufacturer feeds one or more firmware updates into the server 104 in a predetermined interval. In one embodiment, the predetermined interval may vary based on the requirements of the vehicle manufacturers. As used herein, the firmware is defined as a microcode or program embedded into hardware devices to help them operate effectively. As used herein, the firmware updates typically involve some form of program alteration that fixes a known bug or patches against specific vulnerabilities. Vehicle manufacturers constantly update their devices with the latest firmware version.
The server 104 is configured to generate one or more firmware update notifications upon identifying the one or more firmware updates. The one or more firmware updates correspond to one or more vehicle information that is received from the interaction unit. The server 104 checks frequently for the one or more firmware updates from the vehicle manufacturers.
The server 104 is configured to transmit the one or more firmware update notifications to an interaction unit 106. In one embodiment, the one or more firmware update notifications include, but not limited to, a push notification, or message, or an E-Mail. The one or more firmware updates correspond to one or more vehicle information that is received by the server 104 from the interaction unit 106. The interaction unit 106 collects the one or more vehicle information from the vehicle and shares the same with the server 104. In one embodiment, the one or more vehicle information includes a model of the vehicle 102, and a variant and version of the vehicle 102.
For example: the server 104 requests on the one or more vehicle information from the interaction unit 106. Then the server 104 generates the one or more vehicle information based on received one or more vehicle information. In other scenario, the interaction unit 106 transfers the one or more vehicle information to the server 104, then the server 104 generates the one or more vehicle information based on received one or more vehicle information.
The interaction unit 106 is configured to download the one or more firmware updates upon receiving the one or more firmware update notifications from the server 104 via a wireless communication network. In one embodiment, the interaction unit 106 automatically downloads the one or more firmware updates upon receiving the one or more firmware update notifications from the server 104. In another embodiment, the interaction unit 106 downloads the one or more firmware updates upon receiving the one or more firmware update notifications from the server 104 based on a user's approval. In yet another embodiment, the user can initiate a download process immediately, or postpone the download process to a later specified time. The interaction unit 106 is positioned on the vehicle 102.
The interaction unit 106 includes a Human Machine Interface (HMI), an Internet of Things (IoT) device, and/or a user computing device. The interaction unit 106 is communicatively connected to the vehicle 102 and the server 104. In one embodiment, the Human Machine Interface (HMI) may be a smart display. In another embodiment, the interaction unit 106 includes a processor and a memory. In one embodiment, the memory may include, but not limited to, a CISC processor, a read-only memory (ROM), random-access memory (RAM), a removable storage drive, a flash memory, a solid-state memory, a hard disk drive (HDD), a database, or the like. In another embodiment, the processor may include, but not limited to, a RISC processor, an FPGA processor, and an ASIC processor.
The computing device is connected to the vehicle 102 and the server 104 using the wireless communication. The wireless communication includes, but not limited to, infrared Communication, Wi-Fi, Radio Frequency, Bluetooth, Satellite communication, Cellular communication, and Microwave. In yet another embodiment, the computing device may include, but not limited to, desktop, laptop, smartphone, and tablet. In yet another embodiment, the computing device may be a handheld device or wearable device. The computing device allows the user to initiate or postpone the downloading process
The IoT device of the interaction module 106 is configured to receive the one or more notifications from the server 104 using the wireless communication network. The display arrangement of the interaction module 106 displays the one or more notifications to the user of the vehicle 102. In one embodiment, the user of the vehicle 102 may be a driver. The display arrangement of the interaction module 106 allows the user to initiate, postpone, or hold a downloading process.
The interaction unit 10610 is configured to generate a trigger signal to turn a controller unit 108 into an install mode when one or more battery parameters of the at least two battery packs 110 are equal to or higher than a predetermined value. In one embodiment, the predetermined value varies based on capacity of the at least two battery packs 110. In one embodiment, the controller unit 108 may be a body control unit (BCM). In one embodiment, the one or more battery parameters include a state of charge of the at least two battery packs 110 or one or more temperature levels of the at least two battery packs 110. The interaction unit 106 is configured to transmit the trigger signal to the controller unit 108.
The interaction module 106 is connected to the controller unit 108 via communication means. In one embodiment, the communication means may include, but not limited to, a controller area network (CAN) protocol, Universal Asynchronous Receiver/Transmitter (UART) protocol, Serial Peripheral Interface (SPI) protocol, and Inter-Integrated Circuit (I2C) protocol.
The controller unit 108 is configured to receive the trigger signal from the interaction unit 106, and check whether one or more preconditions are true or not. In one embodiment, the one or more preconditions include at least one of availability of the at least two battery packs 110, availability of switching, availability of communication between the control unit and the at least two BMSs 118, and one or more driver behaviors. In one embodiment, one or more driver behaviors include, but not limited to, fluctuation in throttle, pattern in applying brake, and power surge. The controller unit 108 is configured to turn into the install mode and transfer a positive acknowledgment signal to the interaction unit 106 when the one or more preconditions are true. Else the controller unit 108 transfers a negative acknowledgement to the intersection unit 106.
The controller unit 108 transfers the positive acknowledgment signal to the interaction unit 106 to receive the one or more firmware updates on the at least two BMSs 118.
The controller unit 108 detects at least one passive BMS and an active BMS from the at least two BMSs 118 in real time to install the one or more firmware updates on the at least one passive BMS. During discharging of the at least two battery packs 110, the active BMS performs discharging operations in the vehicle 102 in real-time. The at least one passive BMS is the BMS that does not perform discharging operations in the vehicle 102 in real-time. During charging of the at least two battery packs 110, the active BMS performs charging operations in the vehicle 102 in real-time. The at least one passive BMS is the BMS that does not perform charging operations in the vehicle 102 in real time.
Since the at least one passive BMS and an active BMS are identified, the control unit 108 installs the one or more firmware updates on the at least one passive BMS. Then the controller unit 108 switches the power distribution among the at least two battery packs 110. Again the controller unit 108 detects at least one passive BMS and an active BMS from the at least two BMSs 118 in real-time to install the one or more firmware updates on the at least one passive BMS in real-time.
In one exemplary aspect, the vehicle 102 includes the first battery pack 114, and a second battery pack 116 with the first BMS 120, and the second BMS 122 respectively. The controller unit 108 detects an active BMS and a passive BMS between the first BMS 120, and the second BMs 122. Since the controller unit 108 identified the active BMS and the passive BMS, the controller unit 108 downloaded the one or more firmware updates on the passive BMS, and the active BMS. Further, the controller unit 108 installs the one or more firmware updates on the passive BMS
Then the controller unit 108 performs switching operation to switch power distribution. Again the controller unit 108 detects an active BMS and a passive BMS between the first BMS 120, and the second BMs 122. Since the controller unit 108 identified the active BMS and the passive BMS, the controller unit 108 installed the one or more firmware updates on the passive BMS. The identification of the active BMS and the passive BMs between the first BMS 120, and the second BMs 122 is performed by the controller unit 108. In addition to that, the controller unit 108 monitors one or more installation statuses of the at least two BMSs 118. The one or more installation statuses include installation in progress, installation on hold, installation completed, or installation stopped.
In one embodiment, the controller unit 108 is configured to restart the at least one passive BMS when the installation of the one or more firmware updates is completed.
In one embodiment, the interaction unit 106 is configured to install the one or more firmware updates on the at least two BMSs 118 when a firmware running on the controller unit 108 is compatible to handle the one or more firmware updates downloaded on the at least two BMSs 118.
The one or more firmware updates comprise a set of instructions corresponding to the at least two BMSs 118, and the controller unit 108, wherein the interaction unit 106 downloads the set of instructions at least one of the at least two BMSs 118, and the controller unit 108 based on availability.
The interaction unit 106 is configured to check the one or more firmware updates once a download and an installation process is completed for the at least two BMSs 118 to verify accuracy of the one or more firmware updates.
In one embodiment, at least one BMS of the at least two BMSs 118 may temporarily act as the controller unit 108 during the system 100 updates the controller unit 108. For instance, the system 100 designate the at least one BMS of the at least two BMSs 118 to act as the controller 108 for a predetermined time. The system 100 downloads and installs one or more firmware updates of the controller unit 108 with assistance of the interaction unit 106. Once the one or more firmware updates of the controller unit 108 are downloaded, the system 100 allows the at least one BMS of the at least two BMSs 118 to act as the controller 108 for the predetermined time to install the one or more firmware updates of the controller unit 108 that are downloaded, and stored in the controller unit 108.
FIG. 2A and 2B illustrate a method 200 for managing firmware updates of the one or more BMS 118 of the vehicle 102 in accordance with an embodiment of the present disclosure.
In step 202, the method 200 includes generating one or more firmware update notifications upon identifying the one or more firmware updates. In one specific embodiment of the present disclosure, generating the one or more firmware update notifications upon identifying the one or more firmware updates by a server 104.
In step 204, the method 200 includes transmitting the one or more firmware update notifications to an interaction unit 106. In one specific embodiment of the present disclosure, transmitting the one or more firmware update notifications to the interaction unit 106 by the server 104.
In step 206, the method 200 includes downloading the one or more firmware updates upon receiving the one or more firmware update notifications from the server 104 via a wireless communication network. In one specific embodiment of the present disclosure, downloading the one or more firmware updates upon receiving the one or more firmware update notifications from the server 104 via the wireless communication network by the interaction unit 106.
In step 208, the method 200 includes collecting the one or more vehicle information from the vehicle. In one specific embodiment of the present disclosure, collecting the one or more vehicle information from the vehicle by the interaction unit 106.
In step 210, the method 200 includes transferring the one or more vehicle information to the server 104. In one specific embodiment of the present disclosure, transferring the one or more vehicle information to the server 104 the interaction unit 106.
In step 212, the method 200 includes generating a trigger signal to turn a controller unit 108 into an install mode when one or more battery parameters of at least two battery packs 110 are equal to or higher than a predetermined value. In one specific embodiment of the present disclosure, generating the trigger signal to turn the controller unit 108 into the install mode when the one or more battery parameters of the at least two battery packs 110 are equal to or higher than the predetermined value by the interaction unit 106.
In step 214, the method 200 includes transmitting the trigger signal to the controller unit 108. In one specific embodiment of the present disclosure, transmitting the trigger signal to the controller unit 108 by the interaction unit 106.
In step 216, the method 200 includes receiving the trigger signal from the interaction unit 106. In one specific embodiment of the present disclosure, receiving the trigger signal from the interaction unit 106 by the controller unit 108.
In step 218, the method 200 includes checking whether one or more preconditions are true or not. In one specific embodiment of the present disclosure, checking whether the one or more preconditions are true or not by the controller unit 108.
In step 220, the method 200 includes turning into the install mode and transferring a positive acknowledgment signal to the interaction unit 106 when the one or more preconditions are true. In one specific embodiment of the present disclosure, turning into the install mode and transferring the positive acknowledgment signal to the interaction unit 106 when the one or more preconditions are true by the control unit 108.
In step 222, the method 200 includes transferring the positive acknowledgment signal to the interaction unit 106 to receive the one or more firmware updates on the at least two BMSs. In one specific embodiment of the present disclosure, transferring the positive acknowledgment signal to the interaction unit 106 to receive the one or more firmware updates on the at least two BMSs by the controller unit 108.
In step 224, the method 200 includes detecting at least one passive BMS and an active BMS from the at least two BMSs 118 in real time. In one specific embodiment of the present disclosure, detecting the at least one passive BMS and the active BMS from the at least two BMSs 118 in real-time by the controller unit 108.
In step 226, the method 200 includes installing the one or more firmware updates on the at least one passive BMS in real-time. In one specific embodiment of the present disclosure, installing the one or more firmware updates on the at least one passive BMS in real-time by the controller unit 108.
In step 228, the method 200 includes switching the power distribution among the at least two battery packs. In one specific embodiment of the present disclosure, switching the power distribution among the at least two battery packs by the controller unit 108.
In step 230, the method 200 includes detecting at least one passive BMS and an active BMS from the at least two BMSs 118 in real-time. In one specific embodiment of the present disclosure, detecting the at least one passive BMS and the active BMS from the at least two BMSs 118 in real-time by the controller unit 108.
In step 232, the method 200 includes installing the one or more firmware updates on the at least one passive BMS. In one specific embodiment of the present disclosure, installing the one or more firmware updates on the at least one passive BMS by the controller unit 108.
The proposed approaches provide a solution to reduce downtime of the Vehicle 102 by updating the firmware over while the vehicle 102 is in running condition.
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 preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the appended claims. Improvements and modifications may be incorporated herein without deviating from the scope of the invention.

LIST OF REFERENCE NUMERALS
System-100.
Vehicle-102.
Server-104.
Interaction unit-106.
Controller unit-108.
At least two battery packs-110.
Load-112.
First battery pack-114.
Second battery pack-116.
At least two BMSs-118.
First BMS-120.
Second BMS-122.
Method-200.

,CLAIMS:CLAIMS
I/We claim:
1. A system (100) to manage one or more firmware updates on a vehicle (102) in operation, comprising:
at least two battery packs (110) distribute power to the vehicle (102) and comprise at least two BMSs (118);
a server (104) is configured to generate one or more firmware update notifications upon identifying the one or more firmware updates, wherein the server (104) is configured to transmit the one or more firmware update notifications to an interaction unit (106), wherein the one or more firmware updates correspond to one or more vehicle information that is received from the interaction unit (106);
the interaction unit (106) comprises a processor, a memory, and is configured to download the one or more firmware updates upon receiving the one or more firmware update notifications from the server (104) via a wireless communication network, wherein the interaction unit (106) is configured to collect the one or more vehicle information from the vehicle (102), wherein the interaction unit (106) is configured to transfer the one or more vehicle information to the server (104);
wherein the interaction unit (106) is configured to generate a trigger signal to turn a controller unit (108) into an install mode when one or more battery parameters of the at least two battery packs (110) are equal to or higher than a predetermined value, wherein the interaction unit (106) is configured to transmit the trigger signal to the controller unit (108); and
the controller unit (108) is configured to receive the trigger signal from the interaction unit (106), and check whether one or more preconditions are true or not, wherein the controller unit (108) is configured to turn into the install mode and transfer a positive acknowledgment signal to the interaction unit (106) when the one or more preconditions are true, else transfer a negative acknowledgment signal to the interaction unit (106),
wherein the controller unit (108) transfers the positive acknowledgment signal to the interaction unit (106) to receive the one or more firmware updates on the at least two BMSs (118);
wherein the controller unit (108):
detects at least one passive BMS and an active BMS from the at least two BMSs (118) in real time;
install the one or more firmware updates on the at least one passive BMS in real time;
switches the power distribution among the at least two battery packs (110); and
detects at least one passive BMS and an active BMS from the at least two BMSs (118) in real-time; and
install the one or more firmware updates on the at least one passive BMS.
2. The system (100) as claimed in claim 1, wherein the one or more vehicle information comprises a model of the vehicle (102) and a variant and version of the vehicle (102).
3. The system (100) as claimed in claim 1, wherein the one or more battery parameters comprise a state of charge of the at least two battery packs (110) or one or more temperature levels of the at least two battery packs (110).
4. The system (100) as claimed in claim 1, wherein the one or more preconditions comprise at least one of availability of the at least two battery packs (110), availability of switching, availability of communication between the control unit and the at least two BMSs (118), and one or more driver behaviors.
5. The system (100) as claimed in claim 1, wherein the controller unit (108) is configured to restart the at least one passive BMS when the installation of the one or more firmware updates is completed.

6. The system (100) as claimed in claim 1, wherein the interaction unit (106) comprises a Human Machine Interface (HMI), an Internet of Things (IoT) device, or a user computing device, wherein the interaction unit (106) is communicatively connected to the vehicle (102), and the server (104).
7. The system (100) as claimed in claim 1, wherein the one or more firmware updates comprise a set of instructions corresponding to the at least two BMSs (118), and the controller unit (108).
8. A method (200) for managing one or more firmware updates on a vehicle (102) in operation, comprising:
generating, by a server (104), one or more firmware update notifications upon identifying the one or more firmware updates, wherein the one or more firmware updates correspond to one or more vehicle information that is received from the interaction unit (106);
transmitting, by the server (104), the one or more firmware update notifications to an interaction unit (106);
downloading, by the interaction unit (106), the one or more firmware updates upon receiving the one or more firmware update notifications from the server (104) via a wireless communication network;
collecting, by the interaction unit (106), the one or more vehicle information from the vehicle (102);
transferring, by the interaction unit (106), the one or more vehicle information to the server (104);
generating, by the interaction unit (106), a trigger signal to turn a controller unit (108) into an install mode when one or more battery parameters of at least two battery packs (110) are equal to or higher than a predetermined value;
transmitting, by the interaction unit (106), the trigger signal to the controller unit (108);
receiving, by the controller unit (108), the trigger signal from the interaction unit (106);
checking, by the controller unit (108), whether one or more preconditions are true or not;
turning, by the control unit (108), into the install mode and transferring a positive acknowledgment signal to the interaction unit (106) when the one or more preconditions are true;
transferring, by the controller unit (108), the positive acknowledgment signal to the interaction unit (106) to receive the one or more firmware updates on the at least two BMSs (118);
detecting, by the controller unit (108), at least one passive BMS and an active BMS from the at least two BMSs (118) in real time;
installing, by the controller unit (108), the one or more firmware updates on the at least one passive BMS in real time;
switching, by the controller unit (108), the power distribution among the at least two battery packs (110); and
detecting, by the controller unit (108), at least one passive BMS and an active BMS from the at least two BMSs (118) in real-time; and
installing, by the controller unit (108), the one or more firmware updates on the at least one passive BMS.
9. The method (200) as claimed in claim 8, wherein the one or more vehicle information comprises a model of the vehicle (102) and a variant and version of the vehicle (102).
10. The method (200) as claimed in claim 8, wherein the one or more battery parameters comprise a state of charge of the at least two battery packs (110) or one or more temperature levels of the at least two battery packs (110).
11. The method (200) as claimed in claim 8, wherein the one or more preconditions comprise at least one of availability of the at least two battery packs (110), availability of switching, and availability of communication between the control unit and the at least two BMSs (118), and one or more driver behaviors.

12. The method (200) as claimed in claim 8, wherein the controller unit (108) is configured to restart the at least one passive BMS when the installation of the one or more firmware updates is completed.

13. The method (200) as claimed in claim 8, wherein the interaction unit (106) comprises a Human Machine Interface (HMI), an Internet of Things (IoT) device, or a user computing device, wherein the interaction unit (106) is communicatively connected to the vehicle (102), and the server (104).

14. The method (200) as claimed in claim 8, wherein the one or more firmware updates comprise a set of instructions corresponding to the at least two BMSs (118), and the controller unit (108).