DESC:FIELD OF THE INVENTION
[001] The present invention generally relates to a management system, more particularly, relates to an electric vehicle management system.

BACKGROUND OF THE INVENTION
[002] In existing vehicles, predominantly for commercial purposes such as transporting passengers and goods for public transportation, plays a crucial role in employment across India and various other countries. Diesel is one of the primary fuel used in vehicles followed by Compressed Natural Gas (CNG), Liquefied Petroleum Gas (LPG), and petrol for commercial reasons. With a global shift towards creating a greener environment by minimizing vehicular emissions, the world is increasingly embracing renewable energy and focusing on electric mobility. This shift has led to a growing demand for battery-operated electric commercial vehicles.
[003] In the realm of Electric Vehicles (EVs), despite the evident advantages of lower operational costs in comparison to Internal Combustion Engine (ICE) models, prospective customers often exhibit reservations in embracing EV technology. This reluctance stems from several key reasons that impact the perceived affordability and convenience associated with electric vehicles.
[004] The upfront cost of purchasing the EV is notably higher than that of traditional ICE models, primarily due to the substantial expense incurred in acquiring the battery. Consequently, the Equated Monthly Instalment (EMI) for the EV is high. Secondly, the paradigm shift in fueling costs is a significant consideration for consumers. Unlike the conventional model where fossil fuel payments are made immediately during refueling, the fuel cost for EVs is reflected in the electric bill. However, this payment is deferred, occurring either on a monthly, bi-monthly, or instantaneous basis in certain regions. This change in payment structure, from the point of consumption to a subsequent billing cycle, poses a perceived financial challenge for some consumers. Moreover, maintenance costs for EVs introduce a unique aspect related to battery replacement. Typically occurring once every three to five years, depending on the manufacturer's warranty and agreement, the cost associated with replacing the battery constitutes a substantial lump sum. This creates a financial concern for potential EV buyers.
[005] Furthermore, in traditional systems, only rider of the vehicle has direct control over vehicle. Rider can operate vehicle in a preferred manner or configuration. The vehicle owner/ fleet manager does not have a direct control in the operation of the vehicle. Therefore, in a fleet management scenario, where vehicles are utilized around the clock, monitoring of performance of each vehicle and controlling the various vehicle functionalities is very crucial for efficient running of the vehicle. There is a need for a system which allows fleet managers to manage the vehicle functionalities and charging strategies.
[006] Thus, there is a need in the art for electric vehicle management system which can address at least the aforementioned problems.

SUMMARY OF THE INVENTION
[007] In one aspect, the present invention is directed towards electric vehicle management system. The system includes a Subscriber Identity Token (SIT) card disposed onto a vehicle. The system further includes a control unit of the vehicle. The control unit is communicatively coupled to the SIT card. The control unit is configured to verify a battery charger connection to the vehicle. The system includes a telematics control unit of the vehicle. The telematics control unit is communicatively coupled to the SIT card and the control unit. The telematics control unit is configured to receive charger data related to the battery charger in a real-time when the battery charger connection is verified by the control unit. The telematics control unit is configured to send the charger data and a vehicle data to a server in real-time through the SIT card. The server is communicatively coupled to the SIT card. The server is configured to validate the charger data and the vehicle data received from the telematics control unit. The server is configured to check payment confirmation from a user of the vehicle. The server is configured to check predefined conditions when the payment being confirmed from the user. Further, the server is configured to send charging request to the telematics control unit to enable the battery charger to charge the battery when the predefined conditions being satisfied.
[008] In an embodiment of the invention, the telematics control unit is configured to communicate the charging request to the control unit to enable the battery charger to charge the battery. The control unit is configured to enable the battery charger to charge the battery.
[009] In an embodiment of the invention, the predefined condition is any one of a time limit, a current limit, and a State of Charge (SOC) limit.
[010] In another embodiment of the invention, the server is configured to check payment confirmation from the user of the vehicle when the user performs the payment through a communication device, and control running mode of the vehicle based on the payment confirmation from the user of the vehicle.
[011] In another aspect, the present invention is directed towards a method for electric vehicle management. The method includes the step of verifying by a control unit of a vehicle, a battery charger connection to the vehicle. The method includes the step of receiving by a telematics control unit of the vehicle, charger data related to the battery charger in real-time when the battery charger connection is verified by the control unit. Further, the method includes the step of sending by the telematics control unit, the charger data and a vehicle data to a server in real-time through a SIT card. Further, the method includes the step of validating by the server, the charger data and the vehicle data received from the telematics control unit. Further, the method includes the step of checking by the server, payment confirmation from a user of the vehicle. Further, the method includes the step of checking by the server, predefined conditions when the payment being confirmed from the user. Further, the method includes the step of sending by the server, charging request to the telematics control unit to enable the battery charger to charge the battery based on predefined conditions when the payment being confirmed from the user.
[012] In an embodiment of the invention, the method includes the step of communicating by the telematics control unit, the charging request to the control unit to enable the battery charger to charge the battery. Further, the method includes the step of enabling by the control unit, the battery charger to charge the battery.
[013] In an embodiment of the invention, the method includes the step of checking by the server, payment confirmation from the user of the vehicle when the user performs the payment through a communication device, and controlling by the server, running mode of the vehicle based on the payment confirmation from the user of the vehicle.
[014] In another aspect, the present invention is directed towards fleet management system. The system includes a Subscriber Identity Token (SIT) card disposed onto a vehicle. The SIT card is communicatively coupled to a server. The system further includes a control unit of the vehicle. The control unit is configured to verify a battery charger connection to the vehicle. The system further includes a telematics control unit of the vehicle. The telematics control unit is communicatively coupled to the SIT card and the control unit (108). The telematics control unit is configured to receive charger data related to the battery charger in a real-time when the battery charger connection being verified by the control unit. The telematics control unit is configured to send the charger data and a vehicle data to the server in real-time through the SIT card. The system further includes a communication device. The communication device is communicatively coupled to the server. The communication device is configured to request the server to charge the battery of the vehicle. The communication device is configured to specify charging conditions of the battery of the vehicle to the server. The server is configured to validate the charging conditions upon receiving request to charge the battery of the vehicle from the communication device. The server is configured to validate the charger data and the vehicle data received from the telematics control unit. The server is configured to check payment confirmation from a user of the vehicle. The server is configured to check predefined conditions when the payment is confirmed from the user. The server is configured to send charging request to the telematics control unit to enable the battery charger to charge the battery when the predefined conditions being satisfied.
[015] In an embodiment of the invention, the charging condition of the battery of the vehicle is any one of a fleet-wide usage patterns, operational schedules of the vehicle.
[016] In another aspect, the present invention is directed towards a method for fleet management. The method includes the step of verifying by a control unit of a vehicle, a battery charger connection to the vehicle. The method includes the step of receiving by a telematics control unit of the vehicle, charger data related to the battery charger in real-time when the battery charger connection is verified by the control unit. The method includes the step of sending by the telematics control unit, the charger data and a vehicle data to a server in real-time through a SIT card. The method includes the step of requesting by a communication device, the server to charge the battery of the vehicle. The method includes the step of specifying by the communication device, charging conditions of the battery of the vehicle. The method includes the step of validating by the server, the charging conditions upon receiving request to charge the battery of the vehicle from the communication device. The method includes the step of validating by the server, the charger data and the vehicle data received from the telematics control unit. The method includes the step of checking by the server, payment confirmation from a user of the vehicle. The method includes the step of checking by the server, predefined conditions when the payment being confirmed from the user. The method includes the step of sending by the server, charging request to the telematics control unit to enable the battery charger to charge the battery based on predefined conditions when the payment being confirmed from the user.

BRIEF DESCRIPTION OF THE DRAWINGS
[017] Reference will be made to embodiments of the invention, examples of which may be illustrated in accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Figure 1 illustrates a schematic block diagram of electric vehicle management system, in accordance with an embodiment of the invention.
Figure 2 illustrates a schematic block diagram of a control unit of an electric vehicle, in accordance with an embodiment of the invention.
Figure 3 illustrates a method flow diagram for electric vehicle management, in accordance with an embodiment of the invention.
Figure 4 illustrates another method flow diagram for fleet management, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[018] Various features and embodiments of the present invention here will be discernible from the following further description thereof, set out hereunder.
[019] The present invention generally relates to a management system, more particularly, relates to an electric vehicle management system. In the ensuing exemplary embodiments, the vehicle 112 is a three-wheeled vehicle. However, it is contemplated that the disclosure in the present invention may be applied to any automobile like a motorcycle, a scooter or any other saddle type vehicle capable of accommodating the present subject matter without defeating the scope of the present invention.
[020] In some embodiments, the vehicle may be a two-wheeled vehicle, a three-wheeled vehicle, a four-wheeled vehicle or a multi-wheeled vehicle. The vehicle may be powered by an internal combustion engine or an electric motor 114 through one or more batteries or a hybrid-electric motor as per requirement. It should be understood that the scope of present invention is not limited to the illustrated three-wheeled vehicle having powered by the electric motor 114 through one or more batteries or a hybrid-electric motor. The vehicle 112 includes a prime mover (not shown) that is adapted to provide motive force for movement of the vehicle 112. In an embodiment, the prime mover can be the electric motor 114.
[021] Figure 1 illustrates the electric vehicle management system 100. The present electric vehicle management system 100 is also used to manage vehicle fleets.
[022] The system 100 includes a Subscriber Identity Token (SIT) card 104 disposed onto a vehicle 112. The system 100 includes a control unit 108 of the vehicle 112. In an embodiment, the control unit is a vehicle control unit or electronic control unit. In another embodiment, as shown in Figure 2, the control unit 108 is configured to control any one of a motor control unit 122 and a charger control unit 124. Further, as illustrated in figure 1, the control unit 108 of the vehicle 112 is communicatively coupled to the SIT card 104. The control unit 108 communicate with the SIT card 104 for exchanging data and instructions. The control unit 108 is configured to verify a battery charger 116 connection to the vehicle 112. In an embodiment, the battery charger 116 is connected to the vehicle 112 through a Controller Area Network (CAN) bus. The system 100 includes a telematics control unit 106 of the vehicle 112. The telematics control unit 106 is communicatively coupled to the SIT card 104 and the control unit 108. The telematics control unit 106 communicates with the SIT card 104 and the control unit 108 for exchanging data and instructions. The telematics control unit 106 is configured to receive charger data related to the battery charger 116 in a real-time when the battery charger 116 connection is verified by the control unit 108.
[023] In an embodiment, the charger data includes, but not limited to, type of charger, configuration of charger. In an embodiment, the vehicle data includes, but not limited to, the data related to the vehicle 112 such as ‘distance covered by the vehicle 112’, State of Charge (SOC), State of Health (SOH) of the battery of the vehicle 112, duration for which the vehicle 112 was in running state, different ride modes of the vehicle 112 in which it was running in the past few rides. A Battery Management System (BMS) of the vehicle 112 determines the SOC and SOH of the battery and communicates it to the control unit 108 through CAN bus.
[024] Further, the system includes a server 102. The server 102 is communicatively coupled to the SIT card 104. The server 102 communicates with the SIT card 104 for exchanging data and instructions. The server 102 communicates with the telematics control unit 106 through the SIT card 104. The telematics control unit 106 is configured to send the charger data and a vehicle data to the server 102 in real-time through the SIT card 104.
[025] The system also includes a communication device 118. The communication device 118 is communicatively coupled to the server 102. The communication device 118 communicates with the server 102 for exchanging data and instructions. The communication device 118 is configured to request the server 102 to charge the battery of the vehicle 112. The communication device 118 is also configured to specify charging conditions of the battery of the vehicle 112 to the server 102. The user of the vehicle 112 can send request to charge the battery of the vehicle 112 to the server 102 through the communication device 118 using interfaces such as a web application or a mobile application installed on the communication device 118 or in the vehicle 112. In a non-limiting example, the user is a fleet manager who manages a large number of vehicles. Fleet managers initiate requests or instruct for multiple vehicles within the fleet by using the communication device 118. The user or the fleet manager can customise the charging conditions depending upon the requirement through the communication device 118. The communication device 118 is configured to specify charging conditions of the battery of the vehicle 112 to the server 102.
[026] Further, upon receiving request to charge one or more battery of the vehicle 112 from the communication device 118, the server 102 is configured to validate the charging conditions. In an embodiment, the charging conditions of the battery of the vehicle 112 is predefined or scenario-based control logic set specifically for the fleet of the vehicles. In an embodiment, in a non-limiting example, the charging condition of the battery of the vehicle 112 is any one of a fleet-wide usage patterns, operational schedules of the vehicle 112 and overall charging optimization strategies. In an embodiment, "fleet-wide usage patterns" refer to the collective behaviour of electric vehicles (EVs) within the fleet over time. This includes analysing historical data to understand when and how vehicles are typically utilized throughout the day. By examining factors such as peak usage hours, average trip durations, and frequency of charging sessions, the system can identify patterns that influence charging demands. For example, if certain vehicles consistently experience high usage during specific times of the day, the server 102 can prioritize charging for those vehicles during off-peak hours to avoid charging bottlenecks and ensure availability during peak demand periods. Understanding these usage patterns enables the server 102 to predict charging needs more accurately and optimize charging schedules accordingly. In another embodiment, "operational schedules" include the planned activities and routines of the fleet, including shifts, routes, and service requirements. Fleet managers typically establish operational schedules to ensure efficient deployment of vehicles and meet service demands. The server 102 integrates with these schedules to coordinate charging activities in alignment with operational requirements. For instance, if certain vehicles are scheduled for maintenance or off-duty periods, the server 102 can prioritize charging those vehicles during downtimes to minimize disruptions to service. Additionally, by considering operational schedules, the server 102 can optimize charging times to coincide with periods of low vehicle demand, thereby reducing downtime and maximizing fleet availability. Overall, incorporating operational schedules into the charging strategy ensures that charging activities are synchronized with fleet operations, enhancing efficiency and minimizing disruptions.
[027] Further, the charging conditions include a range of factors aimed at ensuring efficient, safe, and cost-effective charging operations. For instance, the system may take into consideration the Battery State of Health (SOH) to prevent overcharging and prolong battery life, grid demand to optimize charging times and costs based on energy availability, charger availability to minimize wait times and maximize utilization of charging infrastructure, and user preferences to tailor charging experiences to individual needs. Each of these conditions plays a vital role in shaping the charging strategy, impacting aspects such as charging rates, timing, and prioritization.
[028] The validation of charging conditions by the server 102 involves a process of data collection, analysis, and decision-making to ensure adherence to predefined parameters and constraints. The server 102 continuously gathers data from various sources, including vehicle telemetry, charging infrastructure status, grid energy availability, and user inputs. This data is then subjected to validation rules and algorithms designed to evaluate compliance with charging conditions. For example, if a vehicle's battery SOH falls below a specified threshold, the server 102 may adjust the charging rate to mitigate further degradation. Similarly, if renewable energy generation is abundant, the server 102 may prioritize charging during those periods to capitalize on clean energy sources. Real-time monitoring allows the server 102 to dynamically adjust charging parameters and strategies based on changing conditions and user requirements. Feedback mechanisms provide users and fleet managers with insights into charging progress, any deviations from predefined conditions, and recommendations for optimizing charging strategies. Through this rigorous validation process, the server 102 ensures that charging activities are conducted safely, efficiently, and in alignment with the specified charging conditions, ultimately enhancing the overall performance and sustainability of the fleet.
[029] In a non-limiting example, the user through communication device 118, can limit the power mode to certain kilometres for the first shift rider, ensuring that there is ample charge left for the subsequent shift rider. The fleet managers can also suggest when, where, and how much to charge based on predictive analyses of orders, optimizing charging infrastructure and minimizing downtime. This not only streamlines operations for fleet managers but also enhances overall efficiency by making charging infrastructure more manageable and available for a larger number of vehicles, thereby reducing waiting times and improving the overall fleet performance.
[030] In an embodiment, the server 102 is configured to validate the charging conditions by comparing the charging conditions with a prestored set of data related to charging conditions of the vehicle 112. In an embodiment, the prestored set of data related to charging conditions is stored in the server 102. In alternate embodiment, the prestored set of data related to charging conditions is stored in a memory unit (not shown) of the vehicle 112.
[031] Further, once the server 102, receives the charger data and the vehicle data from the telematics control unit 106 through the SIT card 104. The server 102 is configured to validate the charger data and the vehicle data received from the telematics control unit 106. In an embodiment, the server 102 is configured to validate the charger data and the vehicle data by comparing the charger data and the vehicle data with a prestored set of data related to the vehicle 112 and the battery charger 116. Further, upon validation of the charger data and the vehicle data by the server 102, the server 102 is configured to check payment confirmation from a user of the vehicle 112. The server 102 checks whether the user has cleared the payments related to the vehicle 112. In an embodiment, if the user fails to confirm the payment, the server 102 is configured to control running mode of the vehicle 112. In another embodiment, if the user fails to confirm the payment, the server 102 is configured to restrict the vehicle 112 running conditions to economy mode. Thus, the server 102 restricts the vehicle 112 to economy mode, limiting the power mode usage until financial obligations are met or limiting any other features (such as entertainment unit of the vehicle) of the vehicle. This control mechanism adds an extra layer of accountability and ensures responsible usage.
[032] In an embodiment, the server 102 is configured to check payment confirmation from the user of the vehicle 112 through the SIT card 104 when the user performs the payment through the communication device 118. In an embodiment, the communication device 118 include, but not limited to, any one of a mobile phone, a tablet, a Personal Digital Assistant (PDA) and a wearable device.
[033] Further, the server 102 is configured to check predefined conditions when the payment being confirmed from the user. In an embodiment, the predefined condition is, but not limited to, any one of a time limit, a current limit, and a State of Charge (SOC) limit. In an embodiment, the time limit is set to restrict the duration for which the vehicle 112 is allowed to be connected to a charging station. In a non-limiting example, the user wants to charge the vehicle 112 for a maximum of 2 hours. In this case, a time limit of 2 hours would be set, and the charging process would automatically stop once this time limit is reached, regardless of whether the battery is fully charged or not. Further, current limit refers to a maximum allowable electric current that can be supplied to the vehicle's battery during charging. This limit is usually set to ensure safe and efficient charging without overloading the charging infrastructure or damaging the battery. In a non-limiting example, if the vehicle's battery is designed to handle a maximum charging current of 50 ampere, a current limit of 50 ampere would be imposed to prevent the charging system from supplying a higher current that could potentially damage the battery or cause safety hazards. Furthermore, SOC represents the current level of charge stored in the battery as a percentage of its total capacity. An SOC limit refers to a predefined threshold of battery charge level, beyond which charging is either stopped or limited to prevent overcharging. In a non-limiting example, suppose the SOC limit is set to 80%. Once the battery reaches an SOC of 80%, charging may be either paused or slowed down to prevent overcharging, which can degrade the battery's lifespan and performance. This helps to maintain the battery within a safe and optimal operating range.
[034] Further, the server 102 is configured to send charging request to the telematics control unit 106 to enable the battery charger 116 to charge the battery when the predefined conditions being satisfied. Further, in an embodiment, upon receiving the charging request, the telematics control unit 106 is configured to communicate the charging request to the control unit 108 to enable the battery charger 116 to charge the battery. Thereafter, the control unit 108 is configured to enable the battery charger 116 to charge the battery. The control unit 108 act as a central command unit of the vehicle 112 which facilitates the charging of the battery. It communicates with the battery charger 116, adhering to an established standard protocol and executing the charging process based on the predefined conditions set by the server 102 controlled charging logic. This synchronized and intelligent approach ensures that the charging process is not only secure and efficient but also tailored to the unique requirements and circumstances of the user and contributes to a user-centric and reliable electric mobility experience.
[035] Figures 3 illustrates a flow diagram of a method 300 for electric vehicle management, in accordance with an exemplary embodiment of the present invention.
[036] At step 302, the control unit 108 of the vehicle 112 verifies the battery charger 116 connection to the vehicle 112. At step 304, the telematics control unit 106 of the vehicle 112 receives charger data related to the battery charger 116 in real-time when the battery charger 116 connection is verified by the control unit 108. At step 306, the telematics control unit 106 sends the charger data and the vehicle data to the server 102 in real-time through the SIT card 104. At step 308, the server 102 validates the charger data and the vehicle data received from the telematics control unit 106. At step 310, the server 102 checks payment confirmation from the user of the vehicle 112. In an embodiment, the server 102 checks payment confirmation from the user of the vehicle 112 through the SIT card 104 when the user performs the payment through the communication device 118. In an embodiment, if the user fails to confirm the payment, the server 102 is configured to control running mode of the vehicle 112. In another embodiment, the server 102 checks payment confirmation from the user of the vehicle 112 through the SIT card 104 and restricts the vehicle 112 running conditions to economy mode if the user fails to confirm the payment. At step 312, the server 102 checks predefined conditions when the payment is confirmed from the user. At step 314, the server 102 sends charging request to the telematics control unit 106 to enable the battery charger 116 to charge the battery based on predefined conditions when the payment being confirmed from the user. In an embodiment, the method includes the step of communicates the charging request to the control unit 108 to enable the battery charger 116 to charge the battery. Further, the control unit 108 enables the battery charger 116 to charge the battery.
[037] Figures 4 illustrates a flow diagram of a method 400 for fleet management, in accordance with an exemplary embodiment of the present invention.
[038] At step 402, the control unit 108 of the vehicle 112 verifies the battery charger 116 connection to the vehicle 112. At step 404, the telematics control unit 106 of the vehicle 112 receives charger data related to the battery charger 116 in real-time when the battery charger 116 connection is verified by the control unit 108. At step 406, the telematics control unit 106 sends the charger data and the vehicle data to the server 102 in real-time through the SIT card 104. At step 408, the communication device 118 request the server 102 to charge the battery of the vehicle 112. At step 410, the communication device 118 specify charging conditions of the battery of the vehicle 112. At step 412, the server 102 validates the charging conditions upon receiving request to charge the battery of the vehicle 112 from the communication device 118. At step 414, the server 102 validates the charger data and the vehicle data received from the telematics control unit 106. At step 416, the server 102 checks payment confirmation from the user of the vehicle 112.
[039] In an embodiment, the server 102 checks payment confirmation from the user of the vehicle 112 through the SIT card 104 when the user performs the payment through the communication device 118. In another embodiment, the server 102 checks payment confirmation from the user of the vehicle 112 through the SIT card 104 and restricts the vehicle 112 running conditions to economy mode if the user fails to confirm the payment. At step 418, the server 102 checks predefined conditions when the payment is confirmed from the user. At step 420, the server 102 sends charging request to the telematics control unit 106 to enable the battery charger 116 to charge the battery based on predefined conditions when the payment being confirmed from the user. In an embodiment, the method includes the step of communicates the charging request to the control unit 108 to enable the battery charger 116 to charge the battery. Further, the control unit 108 enables the battery charger 116 to charge the battery.
[040] Advantageously, in the present invention, the incorporation of the SIT token into the vehicle provides a seamless and secure method for payment, ensuring that the user has control over the operating costs. The present invention opens avenues for diverse incentive schemes, extended warranties, or retrofit product performance options, particularly catering to the needs of daily earners.
[041] Furthermore, the present invention offers a high degree of customization and control, enabling fleet managers and the users to manage their charging preferences remotely through the server. For instance, the user might choose to limit charging during peak electricity demand periods or schedule a prolonged charging session to take advantage of off-peak rates. This level of control not only enhances the user experience but also contributes to overall energy efficiency and grid management. The integration of these advanced communication and control features exemplifies a forward-thinking approach in the design of the vehicle systems, fostering efficiency, user convenience, and adaptability to varying charging scenarios. The present invention ensures proper monitoring of performance of each vehicle and controlling the various vehicle functionalities for efficient running of the vehicle.
[042] The present invention addressed failure modes of electric vehicles (EVs) and their batteries. The present invention encompasses a comprehensive approach aimed at enhancing performance, reliability, and overall efficiency of the vehicles. One crucial aspect of the present invention is the real-time monitoring of battery usage at any given point. By consolidating data on the battery's operational status, fleet managers and users gain valuable insights into its health and performance, which as a result enables the fleet managers and users to take proactive measures to address potential issues. This continuous monitoring is part of the Plan, Do, Check, Act (PDCA) cycle, ensuring that reliability is a dynamic and evolving aspect. Through the present invention, any emerging failure modes or mechanisms affecting the battery of the vehicle can be promptly identified, addressed, and corrected, contributing to the sustained reliability of the electric vehicle.
[043] The present invention ensures a proactive approach to mitigating potential issues, fostering a culture of continuous improvement in the battery's performance and longevity. The present invention allows the user and the fleet managers to understanding the direct impact of the battery on vehicle performance. By closely monitoring how the battery influences the overall functionality of the vehicle, manufacturers and users can optimize and fine-tune the system for efficient and consistent performance. This knowledge allows for adjustments or upgrades to enhance vehicle performance, ensuring a seamless and reliable driving experience. A significant benefit of addressing failure modes and implementing robust mechanisms is the reduction in overall maintenance costs. By staying ahead of potential issues through real-time monitoring, the need for reactive maintenance is minimized. Proactive measures, driven by the insights gained through the PDCA cycle, contribute to increased reliability, reducing the frequency and severity of maintenance requirements. This, in turn, results in cost savings for both fleet managers and users, making electric vehicles more economically viable and appealing.
[044] Further, the present invention ensures control over the charging and discharging of the vehicle's battery. This control extends to influencing the riding mode of the vehicle, allowing for dynamic adjustments based on user behaviour and requirements.
[045] Further, the present invention, by incorporating features that receives charging parameters based on the financial status of the user of the vehicle, the system creates a dynamic avenue for energy utilization aligned with specific needs. For instance, a system could be implemented where the charging process is tailored according to the user's repayment schedule, optimizing energy consumption in line with their financial commitments. This approach not only enhances the overall user experience but also contributes to a more efficient and economical use of energy resources. The integration of loan and amortization statuses into the charging control mechanism signifies a forward-thinking approach in the design of electric vehicle systems, allowing for a personalized and flexible energy management strategy that considers the unique financial circumstances of each user. This innovative architecture fosters a harmonious intersection of technology and finance, paving the way for more accessible and user-friendly electric mobility solutions.
[046] In light of the abovementioned advantages and the technical advancements provided by the disclosed method and system, the claimed steps as discussed above are not routine, conventional, or well understood in the art, as the claimed steps enable the following solutions to the existing problems in conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the system itself as the claimed steps provide a technical solution to a technical problem.
[047] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[048] While the present invention has been described with respect to certain embodiments, it will be apparent to those skilled in the art that various changes and modification may be made without departing from the scope of the invention as defined in the following claims.

List of Reference Numerals
100 - System
102 - Server
104 – SIT
106 – Telematics control unit
108 – Control unit
110 – Battery Management System
112 – Vehicle
114 – Motor
116 – Battery Charger
118 – Communication device
,CLAIMS:1. Electric vehicle management system (100), the system (100) comprising:
a Subscriber Identity Token (SIT) card (104) disposed onto a vehicle (112);
a control unit (108) of the vehicle (112) being communicatively coupled to the SIT card (104), the control unit (108) being configured to verify a battery charger (116) connection to the vehicle (112);
a telematics control unit (106) of the vehicle (112), the telematics control unit (106) being communicatively coupled to the SIT card (104) and the control unit (108), the telematics control unit (106) being configured to:
receive charger data related to the battery charger (116) in a real-time when the battery charger (116) connection being verified by the control unit (108);
send the charger data and a vehicle data to a server (102) in real-time through the SIT card (104);
the server (102) being communicatively coupled to the SIT card (104), the server (102) being configured to:
validate the charger data and the vehicle data received from the telematics control unit (106);
check payment confirmation from a user of the vehicle (112);
check predefined conditions when the payment being confirmed from the user; and
send charging request to the telematics control unit (106) to enable the battery charger (116) to charge the battery when the predefined conditions being satisfied.

2. The system (100) as claimed in claim 1, wherein the telematics control unit (106) being configured to communicate the charging request to the control unit (108) to enable the battery charger (116) to charge the battery; and the control unit (108) being configured to enable the battery charger (116) to charge the battery.

3. The system (100) as claimed in claim 1, wherein the predefined condition being any one of a time limit, a current limit, and a State of Charge (SOC) limit.

4. The system (100) as claimed in claim 1, wherein the server (102) being configured to check payment confirmation from the user of the vehicle (112) when the user performs the payment through a communication device (118); and control running mode of the vehicle (112) based on the payment confirmation from the user of the vehicle (112).

5. A method (300) for electric vehicle management, the method (300) includes the steps of:
verifying (302), by a control unit (108) of a vehicle (112), a battery charger (116) connection to the vehicle (112);
receiving (304), by a telematics control unit (106) of the vehicle (112), charger data related to the battery charger (116) in real-time when the battery charger (116) connection being verified by the control unit (108);
sending (306), by the telematics control unit (106), the charger data and a vehicle data to a server (102) in real-time through a SIT card (104);
validating (308), by the server (102), the charger data and the vehicle data received from the telematics control unit (106);
checking (310), by the server (102), payment confirmation from a user of the vehicle (112);
checking (312), by the server (102), predefined conditions when the payment being confirmed from the user; and
sending (314), by the server (102), charging request to the telematics control unit (106) to enable the battery charger (116) to charge a battery when the predefined conditions being satisfied.

6. The method (300) as claimed in claim 5 comprising steps of: communicating, by the telematics control unit (106), the charging request to the control unit (108) to enable the battery charger (116) to charge the battery; and
enabling, by the control unit (108), the battery charger (116) to charge the battery.

7. The method (300) as claimed in claim 5, wherein the predefined condition being any one of a time limit, a current limit, and a State of Charge (SOC) limit.

8. The method (300) as claimed in claim 5 comprising the step of checking, by the server (102), payment confirmation from the user of the vehicle (112) when the user performs the payment through a communication device (118); and
controlling, by the server (102), running mode of the vehicle (112) based on the payment confirmation from the user of the vehicle (112).

9. A fleet management system (100), the system (100) comprising:
a Subscriber Identity Token (SIT) card (104) disposed onto a vehicle (112), the SIT card (104) being communicatively coupled to a server (102);
a control unit (108) of the vehicle (112), the control unit (108) being communicatively coupled to the SIT card (104), the control unit (108) being configured to verify a battery charger (116) connection to the vehicle (112);
a telematics control unit (106) of the vehicle, the telematics control unit (106) being communicatively coupled to the SIT card (104) and the control unit (108), the telematics control unit (106) being configured to:
receive charger data related to the battery charger (116) in a real-time when the battery charger (116) connection being verified by the control unit (108);
send the charger data and a vehicle data to the server (102) in real-time through the SIT card (104);
a communication device (118) being communicatively coupled to the server (102); the communication device (118) being configured to:
request the server (102) to charge the battery of the vehicle (112);
specify charging conditions of a battery of the vehicle (112) to the server (102);
the server (102) being configured to:
validate the charging conditions upon receiving request to charge the battery of the vehicle (112) from the communication device (118);
validate the charger data and the vehicle data received from the telematics control unit (106);
check payment confirmation from a user of the vehicle (112);
check predefined conditions when the payment being confirmed from the user; and
send charging request to the telematics control unit (106) to enable the battery charger (116) to charge the battery when the predefined conditions being satisfied.

10. The system (100) as claimed in claim 9, wherein the charging condition of the battery of the vehicle (112) being any one of a fleet-wide usage patterns, operational schedules of the vehicle (112).

11. A method (400) for fleet management, the method (400) includes the steps of: verifying (402), by a control unit (108) of a vehicle (112), a battery charger (116) connection to the vehicle (112);
receiving (404), by a telematics control unit (106) of the vehicle (112), charger data related to the battery charger (116) in real-time when the battery charger (116) connection being verified by the control unit (108);
sending (406), by the telematics control unit (106), the charger data and a vehicle data to a server (102) in real-time through a SIT card (104);
requesting (408), by a communication device (118), the server (102) to charge the battery of the vehicle (112);
specifying (410), by the communication device (118), charging conditions of the battery of the vehicle (112) to the server (102);
validating (412), by the server (102), the charging conditions upon receiving request to charge the battery of the vehicle (112) from the communication device (118);
validating (414), by the server (102), the charger data and the vehicle data received from the telematics control unit (106);
checking (416), by the server (102), payment confirmation from a user of the vehicle (112);
checking (418), by the server (102), predefined conditions when the payment being confirmed from the user; and
sending (420), by the server (102), charging request to the telematics control unit (106) to enable the battery charger (116) to charge the battery when the predefined conditions being satisfied.

12. The method (400) as claimed in claim 11, wherein the charging condition of the battery of the vehicle (112) being any one of a fleet-wide usage patterns, operational schedules of the vehicle (112).