Claims:1. A method detecting fuel theft in a vehicle (101), the method comprising:
receiving, by an Anti-Fuel Theft (AFT) system (105) associated with the vehicle (101), one or more input data packets corresponding to one or more connected fuel tanks (125A, 125B) in the vehicle (101), from a telematics unit (103) configured in the vehicle, wherein the one or more input data packets comprises processed telemetry data (209) related to the vehicle (101) and fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), captured in real-time;
determining, by the AFT system (105), values of one or more gradient parameters for the vehicle based on the processed telemetry data (209) received as part of the one or more input data packets;
determining, by the AFT system (105), an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks based on the processed telemetry data (209) and the values of the one or more gradient parameters;
determining, by the AFT system (105), difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks (125A, 125B); and
determining, by the AFT system (105), an occurrence of fuel theft in the vehicle (101) when the difference value exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks (125A, 125B), when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit.

2. The method as claimed in claim 1, wherein the processed telemetry data (209) comprises Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), Global Positioning System (GPS) data of the vehicle, speed of the vehicle (101), acceleration of the vehicle (101), ignition and crank state of the vehicle (101), and distance covered by the vehicle (101).

3. The method as claimed in claim 1, wherein the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101) is measured using a fuel sensor (127A, 127B) arranged in each of the one or more connected fuel tanks (125A, 125B) in the vehicle (101).

4. The method as claimed in claim 1, wherein the processed telemetry data (209) is obtained by processing and normalizing the one or more input data packets to reduce noise in telemetry data, prior to providing the telemetry data to the AFT system (105).

5. The method as claimed in claim 1, wherein one or more gradient parameters comprises roll and pitch of the vehicle (101).

6. The method as claimed in claim 1, wherein the determined average base fuel level remains constant for a predefined time interval before a new average base fuel level is determined.

7. The method as claimed in claim 1 further comprises determining, by the AFT system (105), need for refueling, when the difference value between the average base fuel level and one or more average contender fuel levels of the one or more connected fuel tanks (125A, 125B) exceeds a refuel threshold value in the predefined time period and is less than the predetermined fuel level depreciation threshold.

8. The method as claimed in claim 1 further comprises

receiving, by the AFT system (105), one or more historical data packets from the telematics unit (103), wherein the one or more historical data packets comprises accumulated processed telemetry data (209) related to the vehicle (101) and the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), during absence of desired network conditions;
determining, by the AFT system (105), relevancy of the one or more historical data packets to current time instance based on speed of the vehicle during data capture, and date and time of the data capture, received as part of the accumulated processed telemetry data (209); and
determining the values of the one or more gradient parameters for the vehicle (101), the average base fuel level and the one or more average contender fuel levels for each of the one or more connected fuel tanks (125A, 125B), based on the accumulated processed telemetry data (209) to determine the occurrence of fuel theft, when the one or more historical data packets are determined to be relevant to the current time instance.

9. The method as claimed in claim 8, wherein the one or more historical data packets are determined to be relevant to the current time instance, when the date and time of the data capture is less than a predefined threshold relevancy time, and the speed of the vehicle during data capture is greater than zero.

10. The method as claimed in claim 1 further comprises:
freezing, by the AFT system (105), the average base fuel level value from a first instance of determining that the difference value exceeds the predetermined fuel level depreciation threshold, when the deviation of the values of the one or more gradient parameters from the predetermined gradient threshold is within limit; and
determining, by the AFT system (105), quantity of fuel subjected to theft based on accumulation of the difference value between the average base fuel level and the one or more average contender fuel levels of the one or more connected fuel tanks (125A, 125B) for the predefined time period.

11. The method as claimed in claim 1 further comprises sending, by the AFT system (105), a theft alert to one or more user device (113) associated with users of the vehicle (101), upon determining the occurrence of theft, wherein the theft alert comprises notification of the occurrence of theft and quantity of fuel subjected to theft.

12. An anti-fuel theft (AFT) system (103) in a vehicle (101), the method comprising:
a processor (107); and
a memory (111) communicatively coupled to the processor (107), wherein the memory (111) stores the processor-executable instructions, which, on execution, causes the processor (107) to:
detect occurrence of one or more input data packets received from the AFT system 105 corresponding to one or more connected fuel tanks (125A, 125B) in the vehicle (101), from a telematics unit (103) configured in the vehicle (101), wherein the one or more input data packets comprises processed telemetry data (209) related to the vehicle (209) and fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), captured in real-time;
detect the values of one or more gradient parameters for the vehicle (101) based on the processed telemetry data (209) received as part of the one or more input data packets;
detect an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks (125A, 125B) based on the processed telemetry data (209) and the values of the one or more gradient parameters;
predict the difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks (125A, 125B); and
detect an occurrence of fuel theft in the vehicle (101) when the difference value exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks (125A, 125B), when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit.

13. The AFT system (105) as claimed in claim 12, wherein the processed telemetry data (209) comprises Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), Global Positioning System (GPS) data of the vehicle (101), speed of the vehicle (101), acceleration of the vehicle (101), ignition and crank state of the vehicle (101), and distance covered by the vehicle (101).

14. The AFT system (105) as claimed in claim 12, wherein the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101) is measured using a fuel sensor (127A, 127B) arranged in each of the one or more connected fuel tanks in the vehicle (101).

15. The AFT system (105) as claimed in claim 12, wherein the processed telemetry data (209) is obtained by processing and normalizing the one or more input data packets to reduce noise in telemetry data, prior to providing the telemetry data to the AFT system (105).

16. The AFT system (105) as claimed in claim 12, wherein one or more gradient parameters comprises roll and pitch of the vehicle (101).

17. The AFT (105) system as claimed in claim 12, wherein the processor (107) retains the determined average base fuel level constant for a predefined time interval before a new average base fuel level is determined.

18. The AFT system (105) as claimed in claim 12, wherein the processor (107) is further configured to determine need for refueling, when the difference value between the average base fuel level and one or more average contender fuel levels of the one or more connected fuel tanks (125A, 125B) exceeds a refuel threshold value in the predefined time period and is less than the predetermined fuel level depreciation threshold.

19. The AFT (105) system as claimed in claim 12, wherein the processor (107) is further configured to:

receive one or more historical data packets from the telematics unit (103), wherein the one or more historical data packets comprises accumulated processed telemetry data related to the vehicle and the fuel level in each of the one or more connected fuel tanks (125A, 125B) of the vehicle (101), during absence of desired network conditions;
determine relevancy of the one or more historical data packets to current time instance based on speed of the vehicle (101) during data capture, and date and time of the data capture, received as part of the accumulated processed telemetry data (209); and
determine the values of the one or more gradient parameters for the vehicle (101), the average base fuel level and the one or more average contender fuel levels for each of the one or more connected fuel tanks (125A, 125B), based on the accumulated processed telemetry data (209) to determine the occurrence of fuel theft, when the one or more historical data packets are determined to be relevant to the current time instance.

20. The AFT system (105) as claimed in claim 19, wherein the processor (107) determines the one or more historical data packets to be relevant to the current time instance, when the date and time of the data capture is less than a predefined threshold relevancy time, and the speed of the vehicle during data capture is greater than zero.

21. The AFT (105) system as claimed in claim 12, wherein the processor (107) is further configured to:
Freeze the average base fuel level value from a first instance of determining that the difference value exceeds the predetermined fuel level depreciation threshold, when the deviation of the values of the one or more gradient parameters from the predetermined gradient threshold is within limit; and
determine quantity of fuel subjected to theft based on accumulation of the difference value between the average base fuel level and the one or more average contender fuel levels of the one or more connected fuel tanks (125A, 125B) for the predefined time period.

22. The AFT system (105) as claimed in claim 12, wherein the processor is further configured to send a theft alert to one or more user devices (113) associated with users of the vehicle (101), upon determining the occurrence of theft, wherein the theft alert comprises notification of the occurrence of theft and quantity of fuel subjected to theft.
, Description:TECHNICAL FIELD

Present disclosure generally relates to field of automobile engineering. Particularly but not exclusively, the present disclosure relates to a method and a system for detecting fuel theft in a vehicle.

BACKGROUND OF THE DISCLOSURE

Theft of fuel in vehicles without the knowledge of the fleet owner or the user has been a persisting problem. There are various ways of stealing the fuel from the vehicle such as by forced removal of tank caps, alterations in hose pipes of the vehicle, external pipe insertions etc. Existing technologies predict the fuel theft by calculating the average fuel level over successive periods of time, with any deviation in the fuel level by more than a predetermined amount. However, such deviation may be due to various reasons, for example due to banking condition of the vehicle, due to uneven roads and the like. Currently, the existing techniques do not consider various conditions of the vehicle while generating the fuel theft alert when there is decrease in the fuel level in the tanks, which leads to frequent false theft alerts.

One of the existing technologies provides a method for an authenticated user to remotely control lid of fuel tank through a control device mounted on the lid, and also a camera interface to detect any tampering and damaging activity on the control device. Another existing technology defines a method in which control module may receive data from one or more sensors across the Controlled Area network (CAN) and transmit information from one or more sensors to an end user via the mobile communications system transmitter. Though, the existing techniques disclose fuel theft alerting systems, these techniques do not consider various banking conditions of the vehicle. This in turn results in false and inaccurate fuel theft alerts.

The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms prior art already known to a person skilled in the art.

SUMMARY OF THE DISCLOSURE

One or more shortcomings of the conventional systems are overcome by system and method as claimed and additional advantages are provided through the provision of system and method as claimed in the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.

In one non-limiting embodiment of the present disclosure discloses a method of detecting fuel theft in a vehicle. The method includes receiving, by an Anti-Fuel Theft (AFT) system associated with the vehicle, one or more input data packets corresponding to one or more connected fuel tanks in the vehicle, from a telematics unit configured in the vehicle. The one or more input data packets includes processed telemetry data related to the vehicle and fuel level in each of the one or more connected fuel tanks of the vehicle, captured in real-time. Thereafter, the method includes determining values of one or more gradient parameters for the vehicle based on the processed telemetry data received as part of the one or more input data packets. Further, the method includes determines an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks based on the processed telemetry data and the values of the one or more gradient parameters. Subsequently, the method includes determining difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks. Finally, the method includes determining an occurrence of fuel theft in the vehicle when the difference value exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks, when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit.

In an embodiment of the disclosure, the processed telemetry data comprises Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks of the vehicle, Global Positioning System (GPS) data of the vehicle, speed of the vehicle, acceleration of the vehicle, ignition and crank state of the vehicle, and distance covered by the vehicle.

In an embodiment of the disclosure, the fuel level in each of the one or more connected fuel tanks of the vehicle is measured using a fuel sensor arranged in each of the one or more connected fuel tanks in the vehicle.

In an embodiment of the disclosure, the processed telemetry data is obtained by processing and normalizing the one or more input data packets to reduce noise in telemetry data, prior to providing the telemetry data to the AFT system.

In an embodiment of the disclosure, the one or more gradient parameters comprises roll and pitch of the vehicle.

In an embodiment of the disclosure, the determined average base fuel level remains constant for a predefined time interval before a new average base fuel level is determined.

In an embodiment of the disclosure, the method includes determining need for refueling, when the difference value between the average base fuel level and one or more average contender fuel levels of the one or more connected fuel tanks exceeds a refuel threshold value in the predefined time period and is less than the predetermined fuel level depreciation threshold.

In an embodiment of the disclosure, the method further includes receiving one or more historical data packets from the telematics unit. The one or more historical data packets includes accumulated processed telemetry data related to the vehicle and the fuel level in each of the one or more connected fuel tanks of the vehicle, during absence of desired network conditions. The method further includes determining relevancy of the one or more historical data packets to current time instance based on speed of the vehicle during data capture, and date and time of the data capture, received as part of the accumulated processed telemetry data. Thereafter, the method includes determining the values of the one or more gradient parameters for the vehicle, the average base fuel level and the one or more average contender fuel levels for each of the one or more connected fuel tanks, based on the accumulated processed telemetry data to determine the occurrence of fuel theft, when the one or more historical data packets are determined to be relevant to the current time instance.

In an embodiment of the disclosure, the one or more historical data packets are determined to be relevant to the current time instance, when the date and time of the data capture is less than a predefined threshold relevancy time, and the speed of the vehicle during data capture is greater than zero.

In an embodiment of the disclosure, the method further includes freezing the average base fuel level value from a first instance of determining that the difference value exceeds the predetermined fuel level depreciation threshold, when the deviation of the values of the one or more gradient parameters from the predetermined gradient threshold is within limit. Further, the method includes determining the quantity of fuel subjected to theft based on accumulation of the difference value between the average base fuel level and the one or more average contender fuel levels of the one or more connected fuel tanks for the predefined time period.

In an embodiment of the disclosure, the method further includes sending a theft alert to one or more user devices associated with users of the vehicle, upon determining the occurrence of theft. The theft alert includes notification of the occurrence of theft and quantity of fuel subjected to theft.
In another non-limiting embodiment of the disclosure, an Anti-Fuel Theft (AFT) system for detecting fuel theft in a vehicle is disclosed. The AFT system is associated with the vehicle and includes a processor and a memory communicatively coupled to the processor. The memory stores the processor-executable instructions, which, on execution, causes the processor to detect occurrence of one or more input data packets received from the AFT system corresponding to one or more connected fuel tanks in the vehicle, from a telematics unit configured in the vehicle. The one or more input data packets comprises processed telemetry data related to the vehicle and fuel level in each of the one or more connected fuel tanks of the vehicle, captured in real-time. Detect the values of one or more gradient parameters for the vehicle based on the processed telemetry data received as part of the one or more input data packets. Further, the processor detects an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks based on the processed telemetry data and the values of the one or more gradient parameters. Subsequently, the processor determines the difference value between the average base fuel level and one or more average contender fuel levels of each of the one or more connected fuel tanks. Finally, the processor determines an occurrence of fuel theft in the vehicle when the difference value exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks, when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit.

It is to be understood that aspects and embodiments of the disclosure described above may be used in any combination with each other. Several aspects and embodiments may be combined together to form a further embodiment of the disclosure.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING FIGURES

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 with reference to the accompanying figures, in which:

FIG.1 illustrates an exemplary architecture for detecting fuel theft in a vehicle, in accordance with some embodiments of the present disclosure;

FIG.2 shows a detailed block diagram for detecting fuel theft in a vehicle, in accordance with some embodiments of the present disclosure;

FIG.3A illustrates a flowchart of a method for detecting fuel theft in a vehicle, in accordance with some embodiments of the present disclosure;

FIG.3B illustrates a flowchart of a method for detecting quantity of fuel theft in a vehicle, in accordance with some embodiments of the present disclosure; and

FIG.4 is a block diagram of an exemplary computer system for implementing embodiments consistent with the 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 or not such computer or processor is explicitly shown.

The figures depict embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the system illustrated herein may be employed without departing from the principles of the disclosure described herein.

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 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 scope of the disclosure.
The terms “comprises”, “comprising”, “includes” 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 “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
Disclosed herein are a method and a system for detecting fuel theft in a vehicle. As an example, the vehicle may include, but not limited to, a car, a truck, a lorry, a bus and the like. The present disclosure envisages the aspect of detecting when the fuel has been stolen from the fuel tank. Initially, the Anti-Fuel Theft (AFT) system receives processed input data packets corresponding to one or more connected fuel tanks from a telematics unit configured in the vehicle. The processed input data packets may include, but not limited to, Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks of the vehicle, Global Positioning System (GPS) data of the vehicle, speed of the vehicle, acceleration of the vehicle, ignition and crank state of the vehicle, and distance covered by the vehicle. In some embodiments, receiving processed input data packets from the telematics unit may be dependent on network conditions where the vehicle is moving. For example, when there is an undesirable or no network condition, the AFT system may receive processed data packets from the telematics unit, when the network condition becomes desirable. Therefore, the AFT system may receive accumulated historical data packets instead of real-time processed data packets. On the contrary, when the network condition is desirable, the AFT system receives real-time processed input data packets from the telematics unit. Further, the AFT system may determine values of one or more gradient parameters which may include, but not limited to, pitch and roll of the vehicle, and the like. Further, the AFT system may determine average contender fuel levels which are real time values and measured against average base fuel level of each the one or more connected fuel tanks. The AFT system sends the fuel theft alert to the user device when the difference value exceeds a predetermined fuel level threshold for a predefined time period in at least one of the one or more connected fuel tanks, and when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit. The advantage of this is, the AFT system eliminates false fuel theft alerts that may arise due to difference in the fuel level in the one or more connected tanks based on the vehicle banking conditions that may be uphill, downhill or the slosh that the vehicle may face during travel.

The present disclosure provides a feature wherein, when the vehicle is in a location that encounters undesirable network conditions or no network condition, the AFT system receives accumulated data in the form of historical data packets, from the telematics unit of the vehicle, when the network condition is desirable, instead of ignoring the data that was collected during the undesirable network conditions or no network condition. and Based on the relevancy of accumulated data received as historical data packets, the AFT system may use the accumulated data to accurately determine the fuel consumption and fuel level related parameters. This in turn reduces generation of false fuel theft alerts.

The present disclosure enables a user to know the quantity of fuel subjected to theft by accumulating the difference in the fuel level from the first instance of determination of fuel level difference being greater than a predefined fuel depreciation threshold, upto a predefined time period.

The present disclosure determines the tanks. The present disclosure determines occurrence of fuel theft in the vehicle based on the difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel levels, and deviation of the values of the one or more gradient parameters. Therefore, the present disclosure not only monitors the difference in fuel level, but also monitors the reason behind the difference in the fuel level and eliminates the false alarms that may be generated due to difference in fuel level that arises from banking conditions of the vehicle or slosh caused due to terrain conditions. Therefore, the present disclosure increases the accuracy of determination of occurrence of theft and eliminates false alerts.

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 disclosure.

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.

FIG.1 illustrates an exemplary architecture for detecting fuel theft in a vehicle, in accordance with an embodiment of the present disclosure.

The architecture 100 includes a vehicle 101, a telematics unit 103, Anti-Fuel theft (AFT) system 105, a user device 113 and a user 115. As an example, the vehicle 101 may include, but not limited to, a car, a truck, a lorry, a bus and the like. The telematics unit 103 may be configured in the vehicle 101. In some embodiments, the telematics unit 103 is used to describe vehicle onboard communication services and applications that communicate with one another via GPS receivers and other telematics devices. In some embodiments, the telematics unit 103 collects telemetry data from one or more fuel level measuring sensors configured in the vehicle 101. FIG.1B illustrates connections within the vehicle 101 that enable the telematics unit 103 to receive telemetry data. For ease of understanding, FIG.1B is illustrated considering that the vehicle 101 is arranged with two connected fuel tanks, however, this should not be considered as a limitation of the present disclosure. More than two connected fuel tanks may be arranged in the vehicle 101 based on the design and model of the vehicle 101. As shown in the FIG.1B, the vehicle 101 may include a battery 117, an ignition switch 119, a power supply unit 121, a first control unit 123A, a second control unit 123B, a first connected fuel tank 125A, a second connected fuel tank 125B, a first fuel level sensor 127A, a first fuel level sensor 127B, a first controller 129A, a second controller 129B, a first interface 131A, a second interface 131B, a third interface 131C, cluster 133, an output buffer 135, a storage unit 137, the telematics unit 103, and a communication interface 139.

In some embodiments, the first connected fuel tank 125A and the second connected fuel tank 125B are configured with the first and second fuel level sensor (127A, 127B), respectively. The first fuel level sensor 127A arranged in first connected fuel tank 125A is connected to controller 129A and the second fuel level sensor 127B arranged in second connected fuel tank 127B is connected to the cluster 133. The power supply to the first and second fuel level sensors (127A, 127B), first and second controllers (129A, 129B) and other components in the vehicle 101 is provided by the vehicle’s battery 117. Power supply unit 121 manages and distributes across the components through ignition switch 119 and connected through wire harness. The first and second controllers (129A, 129B) may capture voltage data from the first and second fuel level sensors (127A, 127B) and transmit to the voltage data to the output buffer 135 that temporarily holds the voltage data and coverts into digital data. The data obtained from the sensors (127a, 127 B) are converted to digital format with the help of Controlled Area Network (CAN) message. The digital data is stored in storage device 137 and is then transmitted to the telematics unit 103. The telematics unit 103 appends other data such as location data, speed of the vehicle 101, distance covered by the vehicle 101 and the like, received from other units in the vehicle 101, to the digital data to form telemetry data. Thereafter, the telematics unit 103 may process and normalize the telemetry data in the one or more input data packets to reduce noise in the telemetry data, prior to providing the telemetry data to the AFT system 105, and thus generates the processed telemetry data. The processed telemetry data thus generated may be transmitted to the AFT system 105 through the communication interface 139. As an example, the communication interface 139 may be an Internet of Things (IoT) capable interface.

In some embodiments, the telematics unit 103 may be communicatively connected with an AFT system 105 associated with the vehicle 101. As an example, the AFT system 105 may be configured in a cloud infrastructure and communicatively connected to the telematics unit 103. In some other embodiments, the AFT system 105 may be configured in the vehicle 101 and communicatively connected to the telematics unit 103. The AFT system 105 may determine occurrence of fuel theft in the vehicle 101 based on the processed telemetry data received from the telematics unit 103 and may send a fuel theft alert to a user device 113 of a user 115 associated with the vehicle 101.

In some embodiments, the user of the vehicle 101 may interact with the AFT system 105 via a user portal. As an example, the user of the vehicle 101 may receive the fuel theft alert based on the deviation that may be detected in one or more connected fuel tanks of the vehicle 101.

In some embodiments, the AFT system 105 may include, but not limited to, a processor 107 an Input/Output (I/O) interface 109 and a memory 111. The I/O interface 109 may be configured to receive one or more input data packets corresponding to one or more connected fuel tanks in the vehicle 101 from the telematics unit 103. In some embodiments, the telemetry data may include, but not limited to, Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks of the vehicle, Global Positioning System (GPS) data of the vehicle, speed of the vehicle, acceleration of the vehicle, ignition and crank state of the vehicle, and distance covered by the vehicle. The processed telemetry data is the data related to the vehicle and fuel level in each of the one or more connected fuel tanks of the vehicle, captured in real-time. In some embodiments, exemplary processed telemetry data is as shown in the below Table 1.

Speed of the Vehicle Capacity of fuel tank 1 Fuel level in fuel tank 1 Capacity of fuel tank 2 Fuel level in fuel tank 2 GPS altitude
0 365 291.5 192 153.3 17505
0 365 288.8 192 151.9 17505
8.8125 365 286.3 192 150.6 17972
11.3125 365 287.8 192 151.4 17738

Table 1

Further, based on the telemetry data, the processor 107 may determine values of one or more gradient parameters for the vehicle 101. As an example, the one or more gradient parameters may include, but not limited to, roll and pitch of the vehicle 101. In some embodiments, based on the processed telemetry data and the values of the one or more gradient parameters. the processor 107 may determine an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks. In some other embodiments, the average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks may be received from the telematics unit 103.
In some embodiments, based on the values of the one or more gradient parameters that is roll and pitch, the processor 107 may determine various vehicle conditions. As an example, various vehicle conditions may include at least one of uphill, downhill or slosh condition that may occur due to terrain condition along the route of the vehicle 101 and movement of the vehicle 101.

In some embodiments, upon determining an average base fuel level and one or more contender fuel levels, the processor 107 may determine difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks. In some embodiments, when the difference value exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks and when deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit, the processor 107 may determine an occurrence of fuel theft in the vehicle 101. Further, the processor 107 may determine quantity of fuel subjected to theft based on accumulation of the difference value between the average base fuel level and the one or more average contender fuel levels of the one or more connected fuel tanks for the predefined time period. In some embodiments, upon determining the occurrence of fuel theft and the quantity of fuel subjected to theft, the processor 107 may send a theft alert to one or more user devices 115 associated with users of the vehicle 101. The theft alert may include, but not limited to, notification of the occurrence of theft and quantity of fuel subjected to theft. In some embodiments, when the difference value between the average base fuel level and one or more average contender fuel levels of the one or more connected fuel tanks exceeds a refuel threshold value in the predefined time period and is less than the predetermined fuel level depreciation threshold, the processor 107 may determine need for refueling and may send a refuel alert to the one or more user devices 115 associated with users of the vehicle 101.

In some embodiments, when there is an undesirable network condition or a no network condition, the telematics unit 103 may accumulate processed telemetry data related to the vehicle 101 and the fuel level in each of the one or more connected fuel tanks of the vehicle 101 and transmit the accumulated telemetry data in the form of one or more historical data packets. However, in scenarios where the network conditions were undesirable for a long duration, for example more than 2 hours, the processed telemetry data present in the historical data packets may not be relevant to current scenario anymore. Therefore, the processor 107 may determine relevancy of the one or more historical data packets to current time instance based on speed of the vehicle 101 during data capture, and date and time of the data capture, received as part of the accumulated processed telemetry data. If the one or more historical data packets are determined to be relevant to the current time instance, the processor 107 may determine the values of the one or more gradient parameters for the vehicle 101, the average base fuel level and the one or more average contender fuel levels for each of the one or more connected fuel tanks, based on the accumulated processed telemetry data to determine the occurrence of fuel theft. In scenarios where the one or more historical data packets are determined to be not relevant, the processor 107 may discard the one or more historical data packets. In some other embodiments, the processor 107 may store the one or more historical data packets temporarily, when the one or more historical data packets are determined to be not relevant.

FIG.2 shows a detailed block diagram of a method detecting fuel theft in a vehicle 101, in accordance with some embodiments of the present disclosure.

In some implementations, the Anti-Fuel Theft (AFT) system 105 may include data 203 and modules 205. As an example, the data 203 is stored in the memory 111 configured in the AFT system 105 as shown in the FIG.2. In one embodiment, the data 203 may include fuel level data 207, telemetry data 209, gradient parameter data 211 and other data 213. In the illustrated FIG.2, modules 205 are described herein in detail.

In some embodiments, the data 203 may be stored in the memory 111 in form of various data structures. Additionally, the data 203 can be organized using data models, such as relational or hierarchical data models. The other data 213 may store data, including temporary data and temporary files, generated by the modules 205 for performing the various functions of the AFT system 105.

In some embodiments, the data 203 stored in the memory 111 may be processed by the modules 205 of the AFT system 105. The modules 205 may be stored within the memory 111. In an example, the modules 205 communicatively coupled to the processor 107 configured in the AFT system 105, may also be present outside the memory 111 as shown in FIG.2 and implemented as hardware. As used herein, the term modules refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor 107 (shared, dedicated, or group) and memory 111 that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

In some embodiments, the modules 205 may include, for example, a receiving module 221, a gradient parameter determining module 223, a value determining module 225, fuel-theft determining module 227, a notifying module 228, and other modules 229. The other modules 229 may be used to perform various miscellaneous functionalities of the AFT system 105. It will be appreciated that such aforementioned modules 205 may be represented as a single module or a combination of different modules.

In some embodiments, the receiving module 221 may receive one or more input data packets corresponding to one or more connected fuel tanks in the vehicle 101 from the telematics unit 103 configured in the vehicle 101. The one or more input data packets may include, but not limited to, processed telemetry data 209 related to the vehicle and fuel level in each of the one or more connected fuel tanks of the vehicle 101, captured in real-time. In some embodiments, the processed telemetry data 209 may include, but not limited to, Vehicle Identification Number (VIN), and one or more values associated with the fuel level in each of the one or more connected fuel tanks of the vehicle 101, Global Positioning System (GPS) data of the vehicle 101, speed of the vehicle 101, acceleration of the vehicle 101, ignition and crank state of the vehicle 101, and distance covered by the vehicle 101. The telemetry data 209 is processed in order to normalize the one or more input data packets to reduce noise in telemetry data, prior to providing the telemetry data to the AFT system 105. In some embodiments, when the network condition is undesirable or when there is no network condition, the receiving module 233 may receive one or more historical data packets as input instead of the one or more input data packets in real-time. The one or more historical data packets are formed at the telematics unit 103 by accumulating the processes telemetry data 209 when there is undesirable or no network condition, to communicate with the AFT system 105. In some embodiments, the one or more historical data packets may include, but not limited to, accumulated processed telemetry data related to the vehicle 101 and the fuel level in each of the one or more connected fuel tanks of the vehicle 101. In some embodiments, initially, upon receiving the one or more historical data packets, the processor 107 may check relevancy of the one or more historical data packets to the current time instance, based on date and time of the data capture and speed of the vehicle during data capture, received as part of the one or more historical data packets. As an example, the one or more historical data packets may be considered to be relevant, when the date and time of data capture is less than a predefined threshold relevancy time, and the speed of the vehicle 101 during data capture is greater than zero. This method of determining relevancy of data packets is merely illustrative and should not be construed to be a limitation of the present disclosure, as any other method may be used to determine relevancy of the data packets. In some embodiments, when the processor 107 may consider the one or more historical data packets to be relevant to the current time instance, the content of the one or more historical data packets may be stored as the processed telemetry data 209.

In some embodiments, the gradient parameters determining module 223 may determine the values of the one or more gradient parameters of the vehicle 101, when the vehicle 101 is in motion. As an example, the one or more gradient parameters may include, but not limited to, pitch and roll of the vehicle 101, that indicate pitch and roll condition of the vehicle 101. The values of the one or more gradient parameters of the vehicle 101 may be stored as the gradient parameter data 211 in the AFT system 105. In some embodiments, the gradient parameters determining module 223 may compare the values of the one or more gradient parameters with a predetermined gradient threshold, to determine a deviation value. The deviation value determined in real-time may also be stored as part of the gradient parameter data 211.

In some embodiments, the value determining module 225 may determine an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks based on the processed telemetry data 209 and the values of the one or more gradient parameters. In some embodiments, the value determining module 225 may determine the difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks. In some embodiments, the fuel level in each of the one or more connected fuel tanks of the vehicle 101 is measured using a fuel sensor arranged in each of the one or more connected fuel tanks in the vehicle 101. In some embodiments, the value determining module 225 may determine average base fuel level and one or more average contender fuel levels based on one or more predefined rules and techniques. For each cycle i.e., for a predefined time interval, the average base fuel level remains constant before a new average base fuel level is determined. As an example, consider the predefined time interval is 2 mins. Therefore, for 2 mins the average base fuel level may be kept constant, and the one or more average contender fuel levels may be compared with the same average base fuel level until the end of 2 mins. In some embodiments, the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks thus determined, may be stored as the fuel level data 207.

In some embodiments, the fuel-theft determining module 227 may determine whether the difference value determined by the value determining module 225 exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks. Also, the fuel-theft determining module 227 may determine whether the deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit. As an example, when the value of pitch is less than 2 and value of roll is greater than -2.35, the deviation of the values of the one or more gradient parameters from a predetermined gradient threshold may be said to be within limit. However, these values of pitch and roll are merely exemplary and should not be construed as a limitation of the present disclosure. In some embodiments, the predetermined gradient threshold is determined based on extensive offline trials performed on the vehicle 101 under different terrain conditions. In some embodiments, when the fuel-theft determining module 227 determines that both the conditions are satisfied for the predefined time period, i.e. when the difference value exceeds a predetermined fuel level depreciation threshold and the deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit, then the fuel-theft determining module 227 determines occurrence of fuel theft in the vehicle 101. When the difference value between the average base fuel level and one or more average contender fuel levels of the one or more connected fuel tanks exceeds a refuel threshold value in the predefined time period and is less than the predetermined fuel level depreciation threshold, the fuel-theft determining module 227 may determine need for refueling. In some embodiments, upon determining the occurrence of the fuel theft in the vehicle 101, an notifying module 228 may send a theft alert to the one or more user devices 113 associated with users 115 of the vehicle 101. In some embodiments, upon determining the need for re-fueling, the notifying module 228 may send a re-fuel alert to the one or more user devices 113 associated with users 115 of the vehicle 101. In some embodiments, the theft alert may include, notification of the occurrence of theft and quantity of fuel subjected to theft.

In some embodiments, to determine the quantity of fuel subjected to theft, the fuel theft determining module 227 may initially freeze the average base fuel level value from a first instance of determining that the difference value exceeds the predetermined fuel level depreciation threshold, when the deviation of the values of the one or more gradient parameters from the predetermined gradient threshold is within limit. This means that, when the probability of occurrence of theft is predicted, the fuel theft determining module 227 may initially freeze the average base fuel level value. Thereafter, the fuel-theft determining module 227 may determine the quantity of fuel subjected to theft based on accumulation of the difference value between the average base fuel level and the one or more average contender fuel levels of the one or more connected fuel tanks for the predefined time period. The aspect of accumulation is detailed in flowchart FIG.3B.

FIG.3 shows a flowchart illustrating a method of detecting fuel theft in a vehicle in accordance with some embodiments of the present disclosure.

As illustrated in FIG.3, the method 300a includes one or more blocks illustrating a method of detecting fuel theft in a vehicle 101. The method 300a 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 functions or implement abstract data types.

The order in which the method 300a is described is 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 300a. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300a can be implemented in any suitable hardware, software, firmware, or combination thereof.

At block 301, the method 300a may include receiving, by a processor 107 of an Anti-Fuel Theft (AFT) system 105, one or more input data packets corresponding to one or more connected fuel tanks in the vehicle 101, from a telematics unit 103 configured in the vehicle 101.The one or more input data packets may include, but not limited to, processed telemetry data related to the vehicle 101 and fuel level in each of the one or more connected fuel tanks of the vehicle 101, captured in real-time.

At block 302, the processor 107 checks for a condition to see whether if it is a real time input packet. If the received input data packet is a real time input data packet, the method proceeds to block 303 via "Yes". If the received input data packet is not a real time input data packet i.e. if the data packet is a historical data packet, the method proceeds to block 309 via "No".

At block 303, the method 300a may include determining values of one or more gradient parameters for the vehicle 101 based on the processed telemetry data received as part of the one or more input data packets. At block 309, processor 107 checks for a condition to see whether the data packet is a relevant data packet. If the data packet is determined to be the relevant data packet, the method proceeds to block 311 via “Yes”. If the data packet is determined to be the not a relevant data packet, the method proceeds to block 310 via “No”. At block 310, the method 300 may discard the data packet that may be irrelevant for further analysis. At block 311, the method 300 may save the relevant data packet that may be used in the future cycles for analysis. As an example, the processed telemetry data 209 present in the relevant data packets may be used for determining the values of the one or more gradient parameters for the vehicle, the average base fuel level and the one or more average contender fuel levels for each of the one or more connected fuel tanks and the like, as determined for real-time input data packets from block 303.

At block 304, the method 300a may include determining an average base fuel level and one or more average contender fuel levels for each of the one or more connected fuel tanks based on the processed telemetry data and the values of the one or more gradient parameters

At block 305, the method 300a may include determining difference value between the average base fuel level and one or more average contender fuel levels of each the one or more connected fuel tanks.

At block 306, the processor 107 may check for a condition to see whether the difference value determined at block 305 exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks and whether deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit for the predefined time period. When the condition is true, i.e. when the difference value determined at block 305 exceeds a predetermined fuel level depreciation threshold for a predefined time period in at least one of the one or more connected fuel tanks and whether deviation of the values of the one or more gradient parameters from a predetermined gradient threshold is within limit for the predefined time period, the method proceeds to block 308 via “Yes”. Else, the method proceeds to block 307 via “No”.

At block 307, the method 300a may include sending a re-fuel alert to the user device 113 of the user 115 via a user portal installed in the user device 113.

At block 308, the method 300a may include sending the fuel theft alert to the user device 113 of the user 115 via the user portal. In some embodiments, as part of fuel theft alert, the processor 107 may also send quantity of fuel subjected to theft. The flow of determining quantity of fuel subjected to theft is indicated by flow B in FIG.3A, which is explained in detail in FIG.3B.

FIG.3B shows a flowchart illustrating a method of detecting quantity of fuel subjected to theft in a vehicle in accordance with some embodiments of the present disclosure.

As illustrated in FIG.3B, the method 300b includes one or more blocks illustrating a method of detecting quantity of fuel subjected to theft in a vehicle 101. The method 300b 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 functions or implement abstract data types.

The order in which the method 300b is described is 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 300b. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300b can be implemented in any suitable hardware, software, firmware, or combination thereof.

Initially, when the processor 107 determines that the average base fuel level value exceeds the predetermined fuel level depreciation threshold, when the deviation of the values of the one or more gradient parameters from the predetermined gradient threshold is within limit, the processor 107 freezes the average base fuel level value. This ensures that, the average contender fuel values are compared against the same average base fuel level value for determining difference, until the end of a predefined time period meant for observing the difference in fuel level. Upon freezing the average base fuel level value, the method 300b proceeds to block

At block 313 processor 107 checks for a condition to see whether difference value determined in block 305 of the FIG.3A is greater than fuel level depreciation threshold. If the difference value is greater than the fuel level depreciation threshold, the method proceeds to block 314 via "Yes". If the difference value is less than fuel level depreciation threshold, the method proceeds to block 315 via "No".

At block 314, the method 300b may include determining accumulated difference value by adding current difference value and a previous accumulated difference value.

At block 315, the method 300b may include sending, by the processor 107, a refuel alert to the user device 113 of the user 115.

At block 316, processor 107 checks for a condition to see whether the predefined time period for which the accumulated difference should be determined, has expired. If the predefined time period has expired, the method proceeds to block 317 via “yes”. If predefined time period has not expired, the method proceeds to block 318 via "No".

At block 317, the processor 107 continues to determine the accumulated difference with the subsequent values of the average contender fuel levels, until the expiry of the predefined time period. As an example, the predefined time period may be required time period for monitoring fuel level to determine the occurrence of theft.
At block 317, processor 107 checks for a condition to see whether the accumulated difference is greater than the predetermined fuel level threshold and whether the values of the one or more gradient parameters are within the limit, for the predefined time period. If the accumulated difference is greater than the predetermined fuel level threshold and if the values of the one or more gradient parameters are within the limit, for the predefined time period, the method proceeds to block 319 via “yes”. Else, the method proceeds to block 320 via "No".

At block 319, the processor 107 sends the fuel theft alert comprising the accumulated difference as the quantity of fuel subjected to theft, to the user device 113 of the user 115.

At block 320, the processor 107 sends the re-fuel alert to the user device 113 of the user 115.

FIG.4 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

In some embodiments, FIG.4 illustrates a block diagram of an exemplary computer system 400 for implementing embodiments consistent with the present invention. In some embodiments, the computer system 400 may be an Anti-Fuel theft (AFT) system 105 that is used for detecting fuel theft in a vehicle. The computer system 400 may include a central processing unit (“CPU” or “processor 107”) 402. The processor 402 may include at least one data processor 402 for executing program components for executing user or system-generated business processes. A user may include a person, a person using a device such as such as those included in this invention, or such a device itself. The processor 402 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

The processor 402 may be disposed in communication with input devices 411 and output devices 412 via I/O interface 401. The I/O interface 401 may employ communication protocols/methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS/2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE), WiMax, or the like), etc. Using the I/O interface 401, computer system 400 may communicate with input devices 411 and output devices 412.

In some embodiments, the processor402 may be disposed in communication with a communication network 409 via a network interface 403. The network interface 403 may communicate with the communication network 409. The network interface 403 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. Using the network interface 403 and the communication network 409, the computer system 400 may communicate with telematics unit 414 and user 415 The communication network 409 can be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN), Closed Area Network (CAN) and such within the vehicle 101. The communication network 409 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), CAN Protocol, Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the communication network 409 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc. The user device 113 may include, but not limited to, a mobile phone, a tablet, a laptop and the like. In some embodiments, the processor 402 may be disposed in communication with a memory 405 (e.g., RAM, ROM, etc. not shown in FIG.4) via a storage interface 404. The storage interface 404 may connect to memory 405 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fibre channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

The memory 405 may store a collection of program or database components, including, without limitation, a user interface 406, an operating system 407, a web browser 408 etc. In some embodiments, the computer system 400 may store user/application data, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.

The operating system 407 may facilitate resource management and operation of the computer system 400. Examples of operating systems include, without limitation, APPLE® MACINTOSH® OS X®, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION® (BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX® DISTRIBUTIONS (E.G., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM®OS/2®, MICROSOFT® WINDOWS® (XP®, VISTA®/7/8, 10 etc.), APPLE® IOS®, GOOGLETM ANDROIDTM, BLACKBERRY® OS, or the like. The User interface 406 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 400, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple® Macintosh® operating systems’ Aqua®, IBM® OS/2®, Microsoft® Windows® (e.g., Aero, Metro, etc.), web interface libraries (e.g., ActiveX®, Java®, Javascript®, AJAX, HTML, Adobe® Flash®, etc.), or the like.
In some embodiments, the computer system 400 may implement the web browser 408 stored program components. The web browser 408 may be a hypertext viewing application, such as MICROSOFT® INTERNET EXPLORER®, GOOGLETM CHROMETM, MOZILLA® FIREFOX®, APPLE® SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 408 may utilize facilities such as AJAX, DHTML, ADOBE® FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. In some embodiments, the computer system 400 may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as Active Server Pages (ASP), ACTIVEX®, ANSI® C++/C#, MICROSOFT®, .NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT® exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 400 may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE® MAIL, MICROSOFT® ENTOURAGE®, MICROSOFT® OUTLOOK®, MOZILLA® THUNDERBIRD®, etc.

Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor 402 may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processor 402, including instructions for causing the processor 402 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., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.

Advantages of the embodiment of the present disclosure are illustrated herein.

The present disclosure provides a method and a system for detecting fuel theft in a vehicle.
The present disclosure provides a feature wherein, when the vehicle is in a location that encounters undesirable network conditions or no network condition, the AFT system receives accumulated data in the form of historical data packets, from the telematics unit of the vehicle, when the network condition is desirable, instead of ignoring the data that was collected during the undesirable network conditions or no network condition. and Based on the relevancy of accumulated data received as historical data packets, the AFT system may use the accumulated data to accurately determine the fuel consumption and fuel level related parameters. This in turn reduces generation of false fuel theft alerts.

The present disclosure enables a user to know the quantity of fuel subjected to theft by accumulating the difference in the fuel level from the first instance of determination of fuel level difference being greater than a predefined fuel depreciation threshold, upto a predefined time period.

Referral Numerals:

Reference Number Description
100 Architecture
101 Vehicle
103 Telematics unit
105 Anti-fuel Theft (AFT) system
107 Processor
109 I/O interface
111 Memory
113 User device
115 User
203 Data
205 Modules
207 Fuel level data
209 Telemetry data
211 Gradient parameter data
213 Other data
221 Receiving module
223 Gradient parameter determining module
225 Value determining module
227 Fuel theft determining module
228 Notifying module
229 Other modules
400 Exemplary computer system
401 I/O Interface of the exemplary computer system
402 Processor of the exemplary computer system
403 Network interface
404 Storage interface
405 Memory of the exemplary computer system
406 User interface
407 Operating system
408 Web browser
409 Communication network
411 Input devices
412 Output devices