FORM 2
THE PATENTS ACT 1970
[39 OF 1970]
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[See section 10; Rule 13]
TITLE: “METHOD AND SYSTEM FOR OPERATING VACCUM PUMP”
Name and Address of the Applicant:
TATA MOTORS LIMITED of Bombay House, 24 Homi Mody Street, Hutatma Chowk,
Mumbai, Maharashtra 400001, India
Nationality: India
The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
The present subject matter is related in general to an automobile, more particularly, but not exclusively the present subject matter relates to a method and a system for operating vacuum pump.
BACKGROUND
Currently, in automobiles, vacuum assisted brake boosters are used for applying brake. In the vacuum assisted brake boosters a constant vacuum is maintained by a vacuum pump driven by combustion engine or by alternator. These vacuum pumps are cooled continuously by engine oil thus allowing it to operate continuously along with engine or alternator. However, in Electric Vehicles (EV) since there is no combustion engine, electric vacuum pump is used which has no additional cooling mechanism. To avoid overheating and subsequent failure, the Electric vacuum pump is operated intermittently by switching ON and OFF as required.
At present, the vacuum level point (Cut-off) at which vacuum pump to be switched OFF and Vacuum level point (Cut-In) at which the vacuum pump to be switched ON is fixed. However, the limitation of the fixed cut-off and cut-in values is that at high speed of vehicle, high initial vacuum is required to give maximum brake output during sudden braking, which is not achieved by fixed cut-off and cut-in values. Further, in high traffic situation, fixed ON/OFF strategy cannot address frequent braking, and fail to provide best pedal feel and confident to customers. Further, the vacuum generation is dependent on altitude and atmospheric pressure as such in some instances the cut-off value may not be reached and causes the electric vacuum pump to run for longer time and this affect the health of vacuum pump. Thus, there is requirement/need for efficiently operating vacuum pump.
The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
SUMMARY

In an embodiment, the present disclosure relates to a method for operating vacuum pump. The method comprises receiving a first data and a second data from one or more sensors associated with a vehicle. The method comprises generating a vacuum curve based on the first data. The method comprises estimating a cut-off value for a vacuum pump of the vehicle based on the vacuum curve. The cut-off value is estimated based on change in slope of the vacuum curve with respect to a time period. The method comprises determining a cut-in value for the vacuum pump based on the second data and estimated cut-off value.
In an embodiment, the present disclosure relates to an Electronic Control Unit (ECU) for operating vacuum pump. The ECU includes a processor and a memory communicatively coupled to the processor. The memory stores processor-executable instructions, which on execution cause the processor to operate vacuum pump. The ECU receives a first data and a second data from one or more sensors associated with a vehicle. The ECU generates a vacuum curve based on the first data. The ECU estimates a cut-off value for a vacuum pump of the vehicle based on the vacuum curve. The cut-off value is estimated based on change in slope of the vacuum curve with respect to a time period. The ECU determines a cut-in value for the vacuum pump based on the second data and estimated cut-off value.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and regarding the accompanying figures, in which:

Figure 1a shows an exemplary environment of an Electronic control Unit (ECU) for operating vacuum pump, in accordance with some embodiments of the present disclosure;
Figure 1b shows an exemplary embodiment for operating vacuum pump, in accordance with some embodiments of present disclosure;
Figure 2 shows a detailed block diagram of an ECU for operating vacuum pump, in accordance with some embodiments of the present disclosure;
Figure 3a shows a graph illustrating determination of a cut-off value for operating vacuum pump, in accordance with some embodiments of present disclosure;
Figure 3b shows an embodiment demonstrating determination of a cut-in value for operating vacuum pump, in accordance with some embodiments of present disclosure; and
Figures 4a-4b illustrate a flowchart showing an exemplary method for operating vacuum pump, in accordance with some embodiments of present disclosure.
It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether such computer or processor is explicitly shown.
DETAILED DESCRIPTION
In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the spirit and the scope of the disclosure.
The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
The terms “includes”, “including”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that includes a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “includes… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
The present disclosure relates to an ECU and a method for operating vacuum pump. The proposed method is configured to receive vacuum data from one or more sensors associated with a vehicle. Further, the proposed method determines generation of vacuum curve based on the vacuum data.

Upon generating the vacuum curve, the proposed method estimates a cut-off value for a vacuum pump based on the vacuum curve. Further, the proposed method determines a cut-in value for the vacuum pump based on the cut-off value, and speed of the vehicle . In an embodiment, vacuum pump switches ON only when ignition is in ON state. Thus, the proposed ECU is able to dynamically determine the cut-off and cut-in value for operating the vacuum pump of the vehicle.
Figure 1a shows an exemplary environment 100 of an ECU 101 for operating vacuum pump of a vehicle. The exemplary environment 100 may include the ECU 101, and one or more sensors 102. The environment 100 may be interior of the vehicle. The vehicle may be a four-wheeler vehicle, a three-wheeler vehicle, electric vehicle and the like. The proposed ECU 101 may be implemented in any electric vehicle. The proposed ECU 101 may be used to operate vacuum pump by communicating with the one or more sensors 102. In an embodiment, the one or more sensors 102 may include, but is not limited to pressure sensor, speed sensor, altitude sensor, vacuum sensor and the like. Further, the ECU 101 may include a processor 103, I/O interface 104, and a memory 105. In some embodiments, the memory 105 may be communicatively coupled to the processor 103. The memory 105 stores instructions, executable by the processor 103, which, on execution, may cause the ECU 101 for operating vacuum pump in the vehicle, as disclosed in the present disclosure. In an embodiment, the memory 105 may include one or more modules 106 and data 107. The one or more modules 106 may be configured to perform the steps of the present disclosure using the data 107, for operating vacuum pump of the vehicle. In an embodiment, each of the one or more modules 106 may be a hardware unit which may be outside the memory 105 and coupled with the ECU 101. In an embodiment, the ECU 101 may be associated with multiple vehicles for operating the vacuum pump of the vehicle.
In an embodiment, the ECU 101 may communicate with the one or more sensors 102 via a communication network (not shown in Figure 1a). In an embodiment, the communication network may include, without limitation, a direct interconnection, Local Area Network (LAN), Wide Area Network (WAN), Controller Area Network (CAN), wireless network (e.g., using Wireless Application Protocol), the Internet, and the like.
In an embodiment, consider Figure 1b that shows an exemplary embodiment for operating vacuum pump, in accordance with some embodiments of present disclosure. Figure 1b shows a vacuum

booster 108 of the vehicle connected with the vacuum sensor 102a. The vacuum sensor 102a is further connected to an electric vacuum pump 109 that is to be operated by the ECU 101. Figure 1b shows a battery 110 for operating the ECU 101 of the vehicle. Initially, the ECU 101 of the vehicle is configured to receive a first data and a second data from the one or more sensors 102 associated with a vehicle. The first data comprises but not limited to a vacuum data. The second data comprises but not limited to speed of the vehicle. Upon receiving the first data and the second data, the ECU 101 determines generation of a vacuum curve based on the vacuum data. In another embodiment, the ECU 101 generates the vacuum curve by analysing rate in change of vacuum data with respect to time. Further, the ECU 101 estimates a cut-off value for the vacuum pump of the vehicle based on the vacuum curve or rate of vacuum generation. In an embodiment, the cut¬off value is estimated based on change in slope of the vacuum curve (generation) with respect to a time period. In an embodiment, the cut-off value is utilised to switched OFF the vacuum pump. Further, the ECU 101 determines a cut-in value for the vacuum pump based on the speed of the vehicle and the cut-off value. In an embodiment, the ECU 101 selects the cut-in value from a look¬up table based on the cut-off value and the speed of the vehicle. In an embodiment, the cut-in value is utilised to switch ON the vacuum pump of the vehicle.
In an embodiment, the ECU 101 determines a first altitude data based on the cut-off value. Further, the ECU 101 compares the first altitude data and a second altitude data. In an embodiment, the second altitude data is obtained from the one or more sensors 102 i.e., the altitude sensor (not shown in Figure 1b). The ECU 101 alerts a user indicating failure of the vacuum pump of the vehicle when a difference between the first altitude data and the second altitude data is greater than a predefined threshold value. In an embodiment, when the difference between the first altitude data and the second altitude data is greater than zero and less than or equal to the predefined threshold value, a Diagnostic Trouble Code (DTC) is generated. The DTC indicates or pinpoints a problem in the vehicle. In an embodiment, when the difference between the first altitude data and the second altitude data is less than zero, no action is taken.
Figure 2 shows a detailed block diagram of an ECU for operating vacuum pump, in accordance with some embodiments of the present disclosure.

The data 107 and the one or more modules 106 in the memory 105 of the ECU 101 is described herein in detail.
In one implementation, the one or more modules 106 may include, but are not limited to, a receiving module 201, a generating module 202, an estimating module 203, a determining module 204 and one or more miscellaneous modules 205, associated with the ECU 101.
In an embodiment, the data 107 in the memory 105 may include input data 206, switch ON/OFF data 207, look-up table data 208, and miscellaneous data 209 associated with the ECU 101.
In an embodiment, the data 107 in the memory 105 may be processed by the one or more modules 106 of the ECU 101. In an embodiment, the one or more modules 106 may be implemented as dedicated units and when implemented in such a manner, said modules may be configured with the functionality defined in the present disclosure to result in a novel hardware. As used herein, the term module may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Field-Programmable Gate Arrays (FPGA), Programmable System-on-Chip (PSoC), a combinational logic circuit, and/or other suitable components that provide the described functionality.
One or more modules 106 of the present disclosure function to operate vacuum pump of the vehicle. The one or more modules 106 may also include miscellaneous modules 205 to perform various miscellaneous functionalities of the ECU 101. It will be appreciated that such modules may be represented as a single module or a combination of different modules. The one or more modules 106 along with the data 107, may be implemented in any system, for operating the vacuum pump of the vehicle.
The input data 206 may include information regarding the first data and the second data. The first data includes, but is not limited to, the vacuum data. The second data includes, but is not limited to, speed of the vehicle. The first and the second data may be obtained from the one or more sensors 102. In an embodiment, the input data 206 may also include second altitude data that is obtained from an altitude sensor.

The switch ON/OFF data 207 may include information regarding the cut-off and the cut-in value that is utilised by switch OFF/ON the vacuum pump of the vehicle.
The look-up table data 208 may include information regarding the range of the cut-off value, speed of the vehicle and the corresponding cut-in value.
The miscellaneous data 209 may store data, including temporary data and temporary files, generated by modules for performing the various functions of the ECU 101.
Initially, consider a scenario where a driver drives an electric vehicle that comprises the one or more sensors 102. In an embodiment, the electric vehicle may be configured with the ECU 101 that comprises the receiving module 201. The receiving module 201 is configured to receive the first data and the second data from the one or more sensors 102. The one or more sensors 102 may be associated with the electric vehicle and the one or more sensors 102 may include, but is not limited to, pressure sensor, altitude sensor, speed sensor and the like. In an embodiment, the first data may include the vacuum data obtained from the pressure sensor. In an embodiment, the second data may include the speed of the electric vehicle obtained from the speed sensor. In an embodiment, the receiving moule 201 is configured to transmit the first data and the second data to the generating module 202. The ECU 101 comprises the generating module 202 that is configured to generate a vacuum curve based on the vacuum data. Further, the ECU 101 comprises the estimating module 203 configured to estimate a cut-off value for the vacuum pump of the electric vehicle based on the vacuum curve. The cut-off value is estimated based on change in slope of the vacuum curve with respect to the time period. For example, consider the graph shown in Figure 3a that illustrates determination of the cut-off value for operating vacuum pump of the electric vehicle. In Figure 3a, X-axis represents time period in seconds and Y-axis represents the vacuum data. In an embodiment, the generating module 202 generates the vacuum curve based on the vacuum data and the time period. In an embodiment, the estimating module 203 estimates the cut-off value based on the change in slope of the vacuum curve or rate of change in vacuum with respect to time as shown in Figure 3a. In Figure 3a, the cut-off value may be 480 mm of Hg, as the vacuum curve changes at that instance of time period. In an embodiment, the cut-off value is utilised for switching OFF the vacuum pump of the electric vehicle.

Returning back to Figure 2, the ECU 101 comprises determining module 204 configured to a cut-in value for the vacuum pump based on the second data and estimated cut-off value. In an embodiment, the cut-in value is determined by selecting the cut-in value from a look-up table based on the cut-off value and the speed of the electric vehicle. For example, consider Figure 3b that shows an embodiment demonstrating determination of the cut-in value for operating vacuum pump. In an embodiment, the cut-off value is estimated as 480 mm of Hg as explained above. Once, the cut-off value is estimated, the determining module 204 selects the cut-in value from the look-up table as shown in Figure 3b. In this case, for the cut-off value 480 mm of Hg, the determining module 204 checks the range of the cut-off value in the look-up table (i.e., it falls under the range of <= 400 mm of Hg and < 500 mm of Hg) and also checks the speed of the vehicle at that instance of time period (i.e., <= 60 Kmph). Thus, the cut-in value may be 380 mm of Hg. In an embodiment, the cut-in value is utilised for switching ON the vacuum pump of the electric vehicle.
Returning back to Figure 2, In an embodiment, the determining module 204 is configured to determine a first altitude data based on the cut-off value. Upon determining, the determining module 20 compares the first altitude data and the second altitude data. In an embodiment, the second altitude data is obtained from the altitude sensor or data of altitude from available sources such as GPS, google maps etc. Further, the determining module 204 is configured to alert the driver indicating failure of the vacuum pump of the electric vehicle, when a difference between the first altitude data and the second altitude data is greater than a predefined threshold value. In an embodiment, when the difference between the first altitude data and the second altitude data is greater than zero and less than or equal to the predefined threshold value, the determining module 204 is configured to generate a Diagnostic Trouble Code (DTC). In an embodiment, the DTC indicates a problem in the electric vehicle. In an embodiment, when the difference between the first altitude data and the second altitude data is less than zero, the determining module 204 is configured not to take any action.
Figures 4a-4b illustrate a flowchart showing an exemplary method for operating vacuum pump, in accordance with some embodiments of present disclosure.

As illustrated in Figure 4a, the method 400a may include one or more blocks for executing processes in the ECU 101. The method 400a may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.
The order in which the method 400a are described may not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 401, receiving, the first data and the second data from the one or more sensors 102 associated with the vehicle. The first data comprises vacuum data. The second data comprises speed of the vehicle.
At block 402, generating, the vacuum curve based on the first data. Particularly, the vacuum curve is generated by analyzing rate of change of vacuum with respect to time.
At block 403, estimating, the cut-off value for the vacuum pump of the vehicle based on the vacuum curve. The cut-off value is estimated based on change in slope of the vacuum curve with respect to the time period. The vacuum pump is switched OFF based on the estimated cut-off value.
At block 404, determining, the cut-in value for the vacuum pump based on the second data and the estimated cut-off value. The cut-in value is selected from the look-up table based on the cut-off value and the speed of the vehicle. The vacuum pump is switched ON based on the determined cut-in value.
Figure 4b illustrate a flowchart showing an exemplary method for operating vacuum pump, in accordance with some embodiments of present disclosure.

As illustrated in Figure 4b, the method 400b may include one or more blocks for executing processes in the ECU 101. The method 400b may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.
The order in which the method 400b are described may not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
At block 405, determining, the first altitude data based on the cut-off value and a look-up table.
At block 406, comparing, the first altitude data and the second altitude data. The second altitude data is obtained from the one or more sensors 102.
At block 407, alerting, the user indicating failure of the vacuum pump of the vehicle if the difference between the first altitude data and the second altitude data is greater than the predefined threshold value.
At block 408, generating, the DTC if the difference between the first altitude data and the second altitude data is greater than zero and less than or equal to the predefined threshold value.
At block 409, no action is taken if the difference between the first altitude data and the second altitude data is less than and equal to zero.
Advantages
An embodiment of the present disclosure helps in dynamically estimating the cut-off and cut-in value for switching ON/OFF the vacuum pump of the vehicle.

An embodiment of the present disclosure eliminates the need for altitude sensor and utilises the vacuum data to estimate the altitude and control the vacuum pump to provide optimum output to customer.
An embodiment of the present disclosure ensures operation of vacuum pump with low duty cycle thus increases the life of vacuum pump.
An embodiment of the present disclosure ensures availability of optimum vacuum in all different operating conditions.
An embodiment of the present disclosure avoids continuous operation of vacuum pump in higher altitudes which increases temperature of pump and leads to failure.
In an embodiment, if a Global Positioning System (GPS) is continuously ON, the present disclosure may utilise both estimated altitude data and altitude data obtained from the GPS to modify the ECU vacuum cut-off value.
In an embodiment, the present disclosure utilises artificial intelligence and machine learning to identify failures in the vacuum pump using vacuum generation data/vacuum data.
In an embodiment, the present disclosure may estimate the cut-off value based on traffic data.
In an embodiment, the present disclosure indirectly predicts the traffic data based on number of brake application per minute or kilometre and changes the cut-off value automatically.
In an embodiment, the present disclosure provides safety to the vacuum pump and optimum performance to the customer.
The described operations may be implemented as a method, system or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a “non-transitory computer readable medium”, where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable

medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, etc.), etc. Further, non-transitory computer-readable media may include all computer-readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.).
An “article of manufacture” includes non-transitory computer readable medium, and /or hardware logic, in which code may be implemented. A device in which the code implementing the described embodiments of operations is encoded may include a computer readable medium or hardware logic. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the invention, and that the article of manufacture may include suitable information bearing medium known in the art.
The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the invention(s)” unless expressly specified otherwise.
The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.
The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.
The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.
A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.
When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article.

Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article, or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.
The illustrated operations of Figure 4a show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Referral numerals:
Reference Number Description
100 Environment
101 ECU
102, 102a One or more sensors, vacuum sensor
103 Processor
104 I/O interface
105 Memory
106 Modules
107 Data
108 Vacuum booster
109 Electric vacuum pump
110 Battery
201 Receiving module
202 Generating module
203 Estimating module
204 Determining module
205 Miscellaneous modules
206 Input data
207 Switch on/off data
208 Look-up table data
209 Miscellaneous data

We claim:
1. A method for operating vacuum pump, the method comprising:
receiving, by an Electronic Control Unit (ECU) (101), a first data and a second data from one or more sensors (102) associated with a vehicle;
generating, by the ECU (101), a vacuum curve based on the first data;
estimating, by the ECU (101), a cut-off value for a vacuum pump of the vehicle based on the vacuum curve, wherein the cut-off value is estimated based on change in slope of the vacuum curve with respect to a time period; and
determining, by the ECU (101), a cut-in value for the vacuum pump based on the second data and estimated cut-off value.
2. The method as claimed in claim 1, wherein the first data comprises vacuum data.
3. The method as claimed in claim 1, wherein the second data comprises speed of the vehicle.
4. The method as claimed in claim 1, wherein the vacuum pump is switched OFF based on the estimated cut-off value.
5. The method as claimed in claim 1, wherein the vacuum pump is switched ON based on the determined cut-in value.
6. The method as claimed in claim 1, wherein the cut-off value is estimated based on vacuum data of the vacuum pump.
7. The method as claimed in claim 1, wherein the cut-in value is determined by:
selecting, by the ECU (101), the cut-in value from a look-up table based on the cut¬off value, and speed of the vehicle.
8. The method as claimed in claim 1, further comprises:

determining, by the ECU (101), a first altitude data based on the cut-off value and a look-up table;
comparing, by the ECU (101), the first altitude data and a second altitude data, wherein the second altitude date is obtained from the one or more sensors (102); and
alerting, by the ECU (101), a user indicating failure of the vacuum pump of the vehicle when a difference between the first altitude data and the second altitude data is greater than a predefined threshold value.
9. The method as claimed in claim 8, wherein when the difference between the first altitude data and the second altitude data is greater than zero and less than or equal to the predefined threshold value, a Diagnostic Trouble Code (DTC) is generated.
10. The method as claimed in claim 9, wherein the DTC indicates a problem in a vehicle.
11. The method as claimed in claim 8, wherein when the difference between the first altitude data and the second altitude data is less than zero, no action is taken.
12. An Electronic Control Unit (ECU) (101) for operating vacuum pump, comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
receive a first data and a second data from one or more sensors (102) associated with a vehicle;
generate a vacuum curve based on the first data;
estimate a cut-off value for a vacuum pump of the vehicle based on the vacuum curve, wherein the cut-off value is estimated based on change in slope of the vacuum curve with respect to a time period; and
determine a cut-in value for the vacuum pump based on the second data and estimated cut-off value.
13. The ECU (101) as claimed in claim 12, wherein the first data comprises vacuum data.

14. The ECU (101) as claimed in claim 12, wherein the second data comprises speed of the vehicle.
15. The ECU (101) as claimed in claim 12, wherein the vacuum pump is switched OFF based on the estimated cut-off value.
16. The ECU (101) as claimed in claim 12, wherein the vacuum pump is switched ON based on the determined cut-in value.
17. The ECU (101) as claimed in claim 12, wherein the cut-off value is estimated based on vacuum data of the vacuum pump.
18. The ECU (101) as claimed in claim 12, wherein the processor (103) is configured to determine the cut-in value by:
selecting the cut-in value from a look-up table based on the cut-off value, and speed of the vehicle.
19. The ECU (101) as claimed in claim 12, wherein the processor (103) is configured to:
determine a first altitude data based on the cut-off value and a look-up table;
compare the first altitude data and a second altitude data, wherein the second altitude date is obtained from the one or more sensors (102); and
alert a user indicating failure of the vacuum pump of the vehicle when a difference between the first altitude data and the second altitude data is greater than a predefined threshold value.
20. The ECU (101) as claimed in claim 19, wherein when the difference between the first altitude data and the second altitude data is greater than zero and less than or equal to the predefined threshold value, a Diagnostic Trouble Code (DTC) is generated.
21. The ECU (101) as claimed in claim 20, wherein the DTC indicates a problem in a vehicle.

22. The ECU (101) as claimed in claim 19, wherein when the difference between the first altitude data and the second altitude data is less than zero, no action is taken.