Systems for determining vehicle fuel level

This application claims priority to U.S. Provisional Patent Application No. 63/693,409, titled “Methods and Systems for Determining Fuel Level”, filed on Sep. 11, 2024.

The present disclosure generally relates to systems, devices, methods, and models for determining fuel level in vehicles, and in particular relates to determining fuel level which is not accurately measurable.

Many types of vehicles consume fuel in order to operate. Such fuels include fossil fuels and derivatives thereof (e.g. gasoline, diesel etc.), but can also include alternative fuels such as biodiesel, ethanol, etc. Such fuel is carried by a tank attached to or integrated with a vehicle, and is consumed as the vehicle is utilized. It is desirable to know how much fuel is in a tank of a vehicle, to enable effective management of the vehicle.

According to a broad aspect, the present disclosure describes a system comprising: at least one processor; and at least one non-transitory processor-readable storage medium, the at least one non-transitory processor-readable storage medium storing processor-executable instructions which, when executed by the at least one processor cause the system to: access measured fuel level data for a vehicle, the measured fuel level data indicating a first measured fuel level f(t) for a fuel tank of the vehicle as measured by a fuel level sensor at an end tof a first period t; if the first measured fuel level f(t) is less than 100%, determine, by the at least one processor, a final fuel volume V(t) for the first period tas fuel volume corresponding to the first measured fuel level f(t); if the first measured fuel level f(t) is 100%: access further measured fuel level data for a vehicle, the measured fuel level data indicating a second measured fuel level f(t) for the fuel tank of the vehicle as measured by the fuel level sensor from a start tof a second period t, the start tof the second period tbeing after an end tof the first period t; after the second measured fuel level f(t) falls below 100% at a time tduring the second period t, determine, by the at least one processor, a fuel adjustment value fas fuel consumed between start tof the second period tand the time t, based on a fuel consumption rate of the vehicle; determine, by the at least one processor, an adjusted fuel volume Vas a measurable capacity Vof the fuel tank plus the fuel adjustment value f; and determine, by the at least one processor, the final fuel volume V(t) for the first period tas the adjusted fuel volume V; and trigger account rectification based on the final fuel volume V(t).

The system may further comprise the fuel level sensor which captures the measured fuel level data and the further measured fuel level data.

The system may further comprise: at least one telematics device installed at the vehicle to receive fuel consumption data indicating the fuel consumption rate of the vehicle during the second period.

The processor-executable instructions may further cause the system to: access an indication of initial fuel volume V(t) for start tof the first period t; and determine, by the at least one processor, a difference D between the initial fuel volume V(t) and the final fuel volume V(t). The first period tmay be a period where the vehicle is provided for use by a first user; the second period tmay be a period where the vehicle is provided for use by a second user different from the first user; and the processor-executable instructions may further cause the system to: access an account associated with the first user; and balance the account associated with the first user in accordance with the difference D. The processor-executable instructions may further cause the system to: compare, by the at least one processor, the difference D to a threshold; and if the difference D exceeds the threshold, send an alert to a system operator indicating the difference D exceeds the threshold.

The processor-executable instructions may further cause the system to: access the fuel consumption rate for the vehicle as a stored nominal fuel consumption rate.

The processor-executable instructions may further cause the system to, prior to the first period: access historic fuel level data for the vehicle as collected by the fuel sensor; access operational data for the vehicle as collected by a telematics device installed at the vehicle; and determine, by the at least one processor, the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data. The operational data for the vehicle may comprise location data for the vehicle; and the processor-executable instructions which cause the at least one processor to determine the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data, may cause the at least one processor to: determine distance travelled by the vehicle over each interval of a plurality of intervals based on the location data; determine fuel consumed for each interval of the plurality of intervals based on a respective difference in fuel level represented in the historic fuel level data over each interval; and determine the fuel consumption rate as a fuel consumption per distance travelled rate based on correlation between the distance travelled and the fuel consumed for each interval of the plurality of intervals. The operational data may comprise speed data for the vehicle; and the processor-executable instructions which cause the at least one processor to determine the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data, may cause the at least one processor to: determine speed of the vehicle over each interval of a plurality of intervals; determine fuel consumed for each interval of the plurality of intervals based on a respective difference in fuel level represented in the historic fuel level data over each interval; and determine the fuel consumption rate as a speed-dependent fuel consumption per time rate based on correlation between vehicle speed, fuel consumed, and interval length for each interval of the plurality of intervals.

The system may further comprise: the fuel sensor at the vehicle; and a communication interface at the vehicle, the at least one processor may include a first processor at the vehicle, and the processor-executable instructions may further cause the system to: capture, by the fuel level sensor at the vehicle, raw fuel level data; generate, by the first processor, simplified fuel level data by selectively filtering data points of the raw fuel level data, the simplified fuel level data including the measured fuel level data and the further measured fuel level data; and transmit, by the communication interface, the simplified fuel level data. The processor-executable instructions which cause the first processor to generate the simplified fuel level data by selectively filtering data points of the raw fuel level data may cause the first processor to: identify select data points from the raw fuel level data for inclusion in the simplified fuel level data, based on differences between the select data points and iteratively-defined reference lines through portions of the raw fuel level data; and compile the select data points as the simplified fuel level data, excluding data points which are not identified as select data points. The processor-executable instructions may further cause the system to: identify, by the first processor, a threshold data point based on when the raw fuel level data indicates that fuel level of the vehicle has dropped below 100%; and include, by the first processor, the data corresponding to the threshold data point in the simplified fuel level data.

The system may further comprise a telematics device positioned at the vehicle, the at least one processor may include a first processor at the vehicle; and the processor executable instructions may further cause the system to: collect, by the telematics device, operation data representing kinetic operation of the vehicle; collect, by the telematics device, raw fuel level data indicative of a fuel level in a fuel tank of the vehicle; identify, by the first processor, data points of the operation data which are outside of stability criteria; and for operation data which is outside the stability criteria, exclude corresponding raw fuel level data from the measured fuel level data and the further measured fuel level data.

According to another broad aspect, the present disclosure describes a method comprising: accessing measured fuel level data for a vehicle, the measured fuel level data indicating a first measured fuel level f(t) for a fuel tank of the vehicle as measured by a fuel level sensor at an end tof a first period t; if the first measured fuel level f(t) is less than 100%, determining, by at least one processor, a final fuel volume V(t) for the first period tas fuel volume corresponding to the first measured fuel level f(t); if the first measured fuel level f(t) is 100%: accessing further measured fuel level data for a vehicle, the measured fuel level data indicating a second measured fuel level f(t) for the fuel tank of the vehicle as measured by the fuel level sensor from a start tof a second period t, the start tof the second period tbeing after an end tof the first period t; after the second measured fuel level f(t) falls below 100% at a time tduring the second period t, determining, by the at least one processor, a fuel adjustment value fas fuel consumed between start tof the second period tand the time t, based on a fuel consumption rate of the vehicle; determining, by the at least one processor, an adjusted fuel volume Vas a measurable capacity V, of the fuel tank plus the fuel adjustment value f; and determining, by the at least one processor, the final fuel volume V(t) for the first period tas the adjusted fuel volume V; and triggering account rectification based on the final fuel volume V(t).

The method may further comprise: capturing, by the fuel level sensor, the measured fuel level data and the further measured fuel level data.

The method may further comprise: receiving, by at least one telematics device installed at the vehicle, fuel consumption data indicating the fuel consumption rate of the vehicle during the second period.

The method may further comprise: accessing an indication of initial fuel volume V(t) for start tof the first period t; and determining, by the at least one processor, a difference D between the initial fuel volume V(t) and the final fuel volume V(t). The first period tmay be a period where the vehicle is provided for use by a first user; the second period tmay be a period where the vehicle is provided for use by a second user different from the first user; and the method may further comprise: accessing an account associated with the first user; and balancing the account associated with the first user in accordance with the difference D. The method may further comprise: comparing, by the at least one processor, the difference D to a threshold; and if the difference D exceeds the threshold, sending an alert to a system operator indicating the difference D exceeds the threshold.

The method may further comprise: accessing the fuel consumption rate for the vehicle as a stored nominal fuel consumption rate.

The method may further comprise, prior to the first period: accessing historic fuel level data for the vehicle as collected by the fuel sensor; accessing operational data for the vehicle as collected by a telematics device installed at the vehicle; and determining, by the at least one processor, the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data. The operational data for the vehicle may comprise location data for the vehicle; and determining the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data, may comprise: determining distance travelled by the vehicle over each interval of a plurality of intervals based on the location data; determining fuel consumed for each interval of the plurality of intervals based on a respective difference in fuel level represented in the historic fuel level data over each interval; and determining the fuel consumption rate as a fuel consumption per distance travelled rate based on correlation between the distance travelled and the fuel consumed for each interval of the plurality of intervals. The operational data may comprise speed data for the vehicle; and determining the fuel consumption rate as a dynamic fuel consumption rate based on changes in fuel level as indicated in the historic fuel level data, associated with the operational data, may comprise: determining speed of the vehicle over each interval of a plurality of intervals; determining fuel consumed for each interval of the plurality of intervals based on a respective difference in fuel level represented in the historic fuel level data over each interval; and determining the fuel consumption rate as a speed-dependent fuel consumption per time rate based on correlation between vehicle speed, fuel consumed, and interval length for each interval of the plurality of intervals.

The method may further comprise: capturing, by the fuel level sensor at the vehicle, raw fuel level data; generating, by a first processor of the at least one processor and positioned at the vehicle, simplified fuel level data by selectively filtering data points of the raw fuel level data, the simplified fuel level data including the measured fuel level data and the further measured fuel level data; and transmitting, by a communication interface at the vehicle, the simplified fuel level data. Generating the simplified fuel level data by selectively filtering data points of the raw fuel level data may comprise: identifying select data points from the raw fuel level data for inclusion in the simplified fuel level data, based on differences between the select data points and iteratively-defined reference lines through portions of the raw fuel level data; and compiling the select data points as the simplified fuel level data, excluding data points which are not identified as select data points. The method may further comprise: identifying, by the first processor, a threshold data point based on when the raw fuel level data indicates that fuel level of the vehicle has dropped below 100%; and including, by the first processor, the data corresponding to the threshold data point in the simplified fuel level data.

The method may further comprise: collecting, by a telematics device installed at the vehicle, operation data representing kinetic operation of the vehicle; collecting, by the telematics device, raw fuel level data indicative of a fuel level in a fuel tank of the vehicle; identifying, data points of the operation data which are outside of stability criteria; and for operation data which is outside the stability criteria, exclude corresponding raw fuel level data from the measured fuel level data and the further measured fuel level data.

According to yet another broad aspect, the present disclosure describes a method comprising: accessing a library of fuel level data for a vehicle; accessing a library of fuel consumption data for a vehicle; iteratively for a plurality of sets of data points in the library of fuel level data: identifying two points of the fuel level data which are indicative of a change in fuel level of the vehicle; identifying respective timestamps of the two points of fuel level data; determining fuel consumption of the vehicle between the respective timestamps based on the fuel consumption data; determine a difference between the determined fuel consumption of the vehicle based on the fuel consumption data and the change in fuel level based on the fuel level data; store the determined difference as a calibration factor; aggregating stored fuel level adjustment factors over a measurable range of a fuel level sensor which captures the fuel level data, to generate a fuel level calibration scheme.

The present disclosure details systems, devices, methods, and models for determining fuel level of vehicles. Accurate fuel level information for vehicles helps to effectively manage the vehicles, particularly in a fleet setting. As a non-limiting example, fuel level information can be used for a vehicle rental fleet, to determine whether a vehicle has been refueled on return, or to determine a difference in fuel level to charge, credit, or debit a user. It is desirable for accurate fuel level information to be made available to a management device which manages vehicles in the fleet, such as a central management server.

is a schematic view of a systemfor managing data for a plurality of vehicles.shows a management device, which includes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Although illustrated as one device, management devicecan include a plurality of devices, a plurality of processors, a plurality of non-transitory processor-readable storage mediums, and/or a plurality of communication interfaces. Further, such a plurality of management devices can be in close proximity (e.g. in a central server location), or can be distributed across different locations (e.g. as remote devices). Communication interfacecan be a wired or wireless interface, through which management devicecommunicates with other devices, such as a plurality of vehicles, vehicle devices, or user devices.

In the illustrated example, management deviceis shown as communicating with vehicle devices in four vehicles,,, and(collectively referred to as vehicles). However, management devicecould communicate with vehicle devices in any appropriate number of vehicles, such as one vehicle, dozens of vehicles, hundreds of vehicles, thousands of vehicles, or even more vehicles. In some exemplary implementations, management deviceis a telematics server, which collects and stores telematics data for a fleet of vehicles. In other exemplary implementations, management deviceis a location-specific device, which manages vehicles for a particular location (or vehicles for a plurality of locations). In any of these examples, management devicecan be used to monitor fuel level for vehicles.

Vehicleincludes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Together, the at least one processor, the at least one non-transitory processor-readable storage medium, and the communication interfacecan be referred to as “vehicle device”

Vehicleincludes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Together, the at least one processor, the at least one non-transitory processor-readable storage medium, and the communication interfacecan be referred to as “vehicle device”

Vehicleincludes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Together, the at least one processor, the at least one non-transitory processor-readable storage medium, and the communication interfacecan be referred to as “vehicle device”

Vehicleincludes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Together, the at least one processor, the at least one non-transitory processor-readable storage medium, and the communication interfacecan be referred to as “vehicle device”

Collectively, vehicle, vehicle, vehicle, and vehiclecan be referred to as “vehicles”. Collectively, the at least one processor, the at least one processor, the at least one processor, and the at least one processorcan be referred to as “processors”. Collectively, the at least one non-transitory processor-readable storage medium, the at least one non-transitory processor-readable storage medium, the at least one non-transitory processor-readable storage medium, and the at least one non-transitory processor-readable storage mediumcan be referred to as “non-transitory processor-readable storage mediums”. Collectively, communication interface, communication interface, communication interface, and communication interfacecan be referred to as “communication interfaces”. Collectively, vehicle device, vehicle device, vehicle device, and vehicle devicecan be referred to as “vehicle devices”.

Any of the communication interfacescan be a wired interface or a wireless interface, or a vehicle device can include both a wired communication interface and a wireless communication interface.

Each of vehicle devicescan be a monolithically packaged device (i.e. a device contained in a single housing) which is installed in a respective vehicle. For example, any of vehicle devicescould be a telematics device, which plugs into the respective vehicle (e.g. at the OBDII port). Such telematics devices can gather vehicle information from the vehicle, from sensors built into the telematics device itself, and communicate said information to management devices such as management device. An exemplary telematics device is discussed later with reference to. In some implementations, each vehicle devicecan instead refer to the collection of components installed in a vehicle (i.e. they do not have to be packaged in a single housing). As an example, a vehicle manufacturer could install processing, storage, and communication equipment in vehicles for the purpose of collecting, processing, and transmitting data. Further, components of any of the vehicle devicescan be multi-purpose components which serve other functions within the vehicle.

Management devicecan communicate with vehicle devicesover a communication network, which may include one or more computing systems and may be any suitable combination of networks or portions thereof to facilitate communication between network components. Some examples of networks include, Wide Area Networks (WANs), Local Area Networks (LANs), Wireless Wide Area Networks (WWANs), data networks, cellular networks, voice networks, among other networks, which may be wired and/or wireless. The communication network may operate according to one or more communication protocols, such as, General Packet Radio Service (GPRS), Universal Mobile Telecommunications Service (UMTS), GSM, Enhanced Data Rates for GSM Evolution (EDGE), LTE, CDMA, LPWAN, Wi-Fi, Bluetooth, Ethernet, HTTP/S, TCP, and CoAP/DTLS, or other suitable protocol. The communication network may take other forms as well.

also shows an optional device, which includes at least one processor, at least one non-transitory processor-readable storage medium, and a communication interface. Although illustrated as one device, devicecan include a plurality of devices, a plurality of processors, a plurality of non-transitory processor-readable storage mediums, and/or a plurality of communication interfaces. Further, such a plurality of devices can be in close proximity (e.g. in a central server location), or can be distributed across different locations (e.g. as remote devices). Communication interfacecan be a wired or wireless interface, through which devicecommunicates with other devices.

In the illustrated example, devicecommunicates with management devicevia communication interfacesand. Such communication can be direct or indirect (e.g. over the internet or any other network). Devicecan perform processing and provide data to management device, which management devicein turn uses to manage at least one fleet or group of vehicles (e.g. vehicles). As an example, management devicemay be owned by one entity, which manages a fleet of vehicles. Devicemay belong to another entity, which provides services to many fleets of vehicles. As a result, devicemay have access to more vehicle data (i.e. data from a larger quantity of vehicles) compared to management device. In an exemplary use case, devicemay generate metrics, models, or profiles for at least one plurality of vehicles, based on a large amount of vehicle data available to device. In this exemplary use case, devicecommunicates such metrics, models, or profiles to management device, which management devicethen uses to perform analysis, assessment, or prediction for similar vehicles in a fleet managed by management device(e.g. vehicles). In this way, management devicecan assess models for vehicles based on a large amount of statistical data that management deviceitself does not have access to. As another example, management devicemay be a management device for a specific location (e.g. vehicle lot, warehouse, or hub), such that management devicemanages vehicles which operate out of said location. In such an example, devicemay be a fleet management device, which manages vehicles in a fleet across multiple locations (e.g. all locations, or a subset of locations).

is a schematic diagram of a system, including a telematic devicewhich communicatively couples to a vehicle by a portof the vehicle. Telematic deviceis one exemplary implementation of a vehicle device, such as vehicle devicesdiscussed earlier with reference to. Telematic deviceincludes components which are, in the illustration of, grouped logically into sensor interface componentsand control components. No physical or spatial grouping of these components is necessary, but rather the grouping discussed herein is a logical delineation for ease of discussion.

Sensor interfaceis shown as including a communication interfaceconfigured to interface with matching portin a vehicle (such as any of vehiclesin). In an exemplary implementation, portis a diagnostic port (such as an OBDII port) of the vehicle, and communication interfaceis a matching diagnostic port plug (such as a plug which fits in an OBDII port). Other forms and standards of ports and communication interfaces are possible, as appropriate for a given application. Data from the vehicle (such as sensor data from one or more sensors of the vehicle) is provided to sensor interfaceof telematic devicevia portand communication interface. Vehicle sensors can include, as non-limiting examples, a speed sensor, an inertial sensor, an RPM sensor, a fuel level sensor, a battery temperature sensor, an ambient temperature sensor, a battery voltage sensor, a battery charge sensor, a location sensor, and any other appropriate sensors which collect vehicle-related data.

Sensor interfaceis also shown as including at least one sensor. In the illustrated example, two sensorsare illustrated, but any appropriate number of sensors could be included as appropriate for a given application. Data pertinent to the vehicle can be collected by sensors such as sensor. In this way, data can be collected which is not collected by sensors in the vehicle, or is not reported over an accessible port such as port. Sensorscould include, as non-limiting examples, a speed sensor, an inertial sensor, an ambient temperature sensor, a location sensor, an image sensor (e.g. camera), and any other appropriate sensors which collect vehicle-related data.

Sensor interfaceis also shown as including a communication interface, which communicates with an optional peripheral device. Peripheral deviceincludes at least one sensor, and can provide data collected by the at least one sensorto telematics devicevia communication interface. In this way, data can be collected which is not collected by sensors in the vehicle, is not reported over an accessible port such as port, or is not collected by sensors in telematic device. The at least one sensorcould include, as non-limiting examples, a speed sensor, an inertial sensor, an ambient temperature sensor, a location sensor, an image sensor (e.g. camera), a fuel level sensor, and any other appropriate sensors which collect vehicle-related data.

Optionally, peripheral devicecan also include at least one processorand at least one non-transitory processor-readable storage medium. Peripheral devicecan thus be used to perform acts of the methods discussed herein (by the at least one processorexecuting processor-executable instructions stored at the at least one non-transitory processor-readable storage medium).

Communication interface(and port), sensors, and communication interface(and sensor) show multiple means by which telematics devicecan collect sensor data. However, each of these components is not necessarily required. For example, any of communication interface, sensors, or communication interfacecan be omitted, as long as one means of collecting sensor data remains.

Telematics devicecan also include at least one processorand at least one non-transitory processor-readable storage medium. Telematics devicecan thus be used to perform acts of the methods discussed herein (by the at least one processorexecuting processor-executable instructions stored at the at least one non-transitory processor-readable storage medium).

Telematic device(optionally in combination with peripheral device) can be implemented, for example, as any of vehicle devicesin. Telematic device(optionally in combination with peripheral device) can also be used in the context of any of the methods discussed herein (in particular, methodin).

As mentioned earlier, telematics device, in the form illustrated in, is not strictly required to implement the systems, methods, devices, and models discussed herein. In alternative implementations, the components of telematic devicecan be integrated within a vehicle (namely, any appropriate sensors, processors, non-transitory processor-readable storage mediums, communication interfaces, etc. can be components integrated in a vehicle, which serve similar functionality to telematic device.

As it regards particular sensor types and sensor data, several exemplary sensor types are of particular interest in this disclosure, and are discussed in detail below. The present disclosure is not limited to using data from these particular sensors (and several other sensor types are discussed above), nor is each of the particular sensors required in every implementation, but these particular sensors are called out as being especially valuable for the purposes discussed herein.

Any of the above discussed sensors or sensing modules (whether integrated in a vehicle or as part of a vehicle device or telematic device) can include a sensing module for determining vehicle location (also referred to as a location sensor). For instance, the sensing module may utilize Global Positioning System (GPS) technology (e.g., GPS receiver) for determining the geographic location (Lat/Long coordinates) of a vehicle. Alternatively, the sensing module utilizes another a global navigation satellite system (GNSS) technology, such as, GLONASS or BeiDou. Alternatively, the sensing module may further utilize another kind of technology for determining geographic location.

Alternatively, vehicle position information may be provided according to another geographic coordinate system, such as, Universal Transverse Mercator, Military Grid Reference System, or United States National Grid.

Any of the above discussed sensors or sensing modules can include a sensing module for determining an engine rotation speed for a vehicle (e.g. a tachometer). Engine rotation speed is typically expressed in revolutions per minute (RPM).

Any of the above discussed sensors or sensing modules can include a sensing module for determining movement speed for a vehicle. Vehicle movement speed can be expressed in any appropriate units, but is commonly expressed in miles per hour (mph), kilometers per hour (km/h), or meters per second (m/s). The speed sensor may be a sensor which measures data which is not directly movement speed of the vehicle, but is data from which movement speed of the vehicle can be derived. In some implementations, movement speed can be derived from location data measured by a location sensor (by determining change in location over time). In some implementations, movement speed can be derived from engine rotation speed data (based on a correlation in engine rotation speed and corresponding movement speed of the vehicle), or can be derived based on wheel rotation speed of the vehicle (which can itself be based on engine rotation speed, or measured by a specific wheel rotation speed sensor). For example, if wheels of a vehicle are of a known size, then distance travelled by the vehicle per wheel rotation (wheel circumference) is also known, such that a correlation can be established between time per wheel rotation and distance travelled per wheel rotation.

Any of the above discussed sensors or sensing modules can include a sensing module for determining acceleration of a vehicle, such as an accelerometer or IMU (inertial measurement unit).

Any of the above discussed sensors or sensing modules can include a fuel sensor or plurality of fuel sensors. Fuel sensors can be implemented and integrated within a vehicle. As a specific example, a fuel sensor can comprise a series of optical sensors positioned within a fuel tank of a vehicle. These optical sensors can detect the presence of fluid in front of the respective optical sensor. By positioning these optical sensors at specific heights in the fuel tank, fuel level can be measured by identifying which of the optical sensors have fluid in front, and which optical sensors do not. As another specific example, a float sensor could be integrated within a fuel tank of a vehicle. As yet another specific example, an ultrasonic fuel sensor can be positioned within a fuel tank of a vehicle. Fuel level as measured by such sensors can be reported to a vehicle control unit, and is used to inform a position of a fuel reading on a dashboard display of the vehicle. Further, such fuel data can also be reported over a diagnostic or communication interface of the vehicle (such as an OBDII port). A vehicle device (such as any of vehicle devicesor telematic device) can receive the fuel level data over the communication interface of the vehicle.

In other implementations, a fuel level sensor could be implemented which is not integrated with the vehicle. For example, a fuel level sensor could be implemented which communicates wirelessly with a vehicle device (e.g. as a peripheral device which communicates with telematic device). Such a fuel level sensor could be an optical or float sensor which is inserted into a vehicle fuel tank, as examples.