Patent Description:
Telematics devices, commonly known as a telematics control unit (TCU), are used in the management of vehicle fleets. A TCU such as one of the LINK devices available from Webfleet Solutions may be installed in vehicles to track their positions and collect vehicle data for analysis. This enables a fleet manager to view real-time vehicle location for the complete fleet on a map, as well as being provided with information concerning driving behaviour and vehicle diagnostics.

By connecting a voltage monitoring unit of a telematics device to a vehicle battery, it is also possible to achieve remote insight into battery health. The health status of a vehicle battery may be used to determine whether the battery may not have enough charge to start the vehicle. The fleet manager may therefore be alerted to a no-start condition being predicted for an individual vehicle, for example as disclosed in <CIT>. This can prevent the driver from being confronted with a battery issue only when battery failure occurs, e.g. during the first cold days of winter. What is meant by battery failure is an event where the power train of a vehicle is no longer able to provide the necessary power to crank the combustion engine.

When assessing battery health, typically various parameters need to be input manually based on vehicle history, in particular the battery age or date of last battery replacement. This relies on manually keeping track of how old is each battery of the fleet and the last battery replacement date being provided by the driver, the garage staff, or the fleet manager. There remains a need for a way of automatically detecting when a vehicle battery is replaced.

Moreover, battery health assessments ideally take into account a variety of factors including driving behaviour and the vehicle charging system (alternator), as these factors are known to affect the state of charge of the battery. There remains a need for automatically detecting various health-related events and state-related events in general for a vehicle battery.

<CIT> discloses a battery monitor apparatus and method for an automotive battery system including a battery for supplying power to in-vehicle electrical equipment and sensors for detecting battery voltage, the charge/discharge current and the battery temperature.

<CIT> discloses a method for monitoring the condition of a battery of a marine propulsion system comprising measuring of a voltage characteristic of the battery, comparing the voltage characteristic to a preselected threshold value, and evaluating the condition of the battery as a function of the relative magnitudes of the voltage characteristic and the threshold value.

<CIT> discloses an apparatus, a device, methods and a system relating to a vehicular telemetry environment for monitoring vehicle components and providing indications towards the rating condition of the vehicle components and providing optimal indications towards replacement or maintenance of vehicle components before vehicle component failure.

According to the present invention there is provided a server according to claim <NUM>, a system according to claim <NUM>, and a method according to claim <NUM>.

In those examples using one or more machine learning or statistical analysis methods to identify one or more discernible changes in a voltage profile, standard methods may be applied. Some examples of standard methods include Gaussian-Mixture-Models, Multivariate-T-Student Test, Neural Networks, Cluster-based Local Outlier Factor, Histogram-based Outlier Detection, Isolation Forest, K - Nearest Neighbours, and the like. For example, the method may comprise performing a t-test identify one or more discernible changes in a voltage profile. Reference may be made to standard textbooks, such as: <NPL>; <NPL>; <NPL>.

In any of the aspects and embodiments disclosed herein, the method is a computer-implemented method.

In any of the examples disclosed herein, the methods may be used with any vehicle battery associated with an internal combustion engine (ICE), whether in a traditional ICE vehicle or a hybrid vehicle. The vehicle battery may be connected to an alternator to allow the battery to be recharged when the vehicle is driving. In hybrid vehicles, one or more combined motor/generator(s) may charge a storage battery and replace the separate alternator and starter motor usually found in ICE vehicles. In any of the aspects and embodiments disclosed herein, the methods may be used with any vehicle battery in a road vehicle.

In any of the examples disclosed herein, the method obtains voltage measurements from a voltage monitoring unit of a telematics device that is associated with the vehicle permanently or temporarily. As mentioned above, the telematics device may comprise a battery as an autonomous power source, or the telematics device may be connected to the vehicle battery to take a power supply from the battery. The voltage monitoring unit may take voltage measurements from the battery in any suitable way. For example, the voltage monitoring unit may be connected to a power wire of the vehicle, optionally via the Controller Area Network (CAN) bus commonly used as an in-vehicle data network. For example, the voltage monitoring unit may comprise an analogue to digital converter (ADC) of the telematics device. It will be understood that battery voltage measurements as disclosed herein can be any measurements indicative of the battery voltage. The battery voltage measurements may not be direct measurements of voltage.

Electric Vehicles (EVs) and Plug-In Hybrid Electric Vehicles (PHEVs) have two types of batteries: a high-voltage battery pack which is responsible for delivering power to the drivetrain, and a low-voltage (12V or 24V) battery which powers the electric components (lights, electronic systems, etc.). There are two types of batteries in EVs and PHEVs for cost and safety reasons. 12V batteries are much cheaper than high voltage battery packs which may have voltages of <NUM>-800V.

Starting an engine in traditional ICE vehicles is one of the largest stress factors for batteries in these vehicles. However, the low voltage batteries in EVs and PHEVs also age and degrade. Particularly during long periods where vehicles are not in use, the self-discharge of the low voltage battery in EVs/PHEVs may harm the integrity of this low voltage battery. Even when the EV/PHEV is plugged in, the low-voltage battery will discharge and may therefore require replacement at some point.

The server and/or the system according to the claimed aspects of the invention may optionally include any of the features described below in relation to embodiments of the corresponding method, for example one or more of the method steps disclosed below may be carried out by one or more processors of the server.

The engine may be the engine of an Electric Vehicle (EV)/Plug-in Hybrid Electric Vehicle (PHEV). Such a method is able to automatically identify when a vehicle battery (such as a low-voltage battery in an EV/PHEV) has been replaced without any need for input from the vehicle's driver or owner. By monitoring the battery voltage measurements in the first time window corresponding to an engine off state, the resting voltage profile of the battery is monitored. What is meant by the resting voltage profile is the vehicle battery voltage as a function of time as measured in an engine off state. When a battery is replaced with a different one, a step change in the resting voltage magnitude is observed. This step change may be positive or negative. As explained previously, different batteries may have different resting voltage profiles due to different ages (typically the resting voltage decays faster as the battery degrades over time) or two batteries of the same age may have different resting voltage profiles because they come from different manufacturers or have experienced different charging patterns during use. In at least some embodiments of the method described above, monitoring the voltage measurements in the first time window comprises determining a resting voltage profile as a function of time from voltage measurements in the first time window.

It will be appreciated that the voltage monitoring unit may be any suitable monitoring device connected, either directly or indirectly, to the vehicle battery to take measurements of the vehicle battery voltage. In some embodiments, the voltage monitoring unit may comprise electric circuity of the vehicle that is connected to the telematics device. In some embodiments, alternatively or in addition, the voltage monitoring unit may be incorporated into a telematics device. The telematics device may be physically connected to an appropriate data monitoring port in the vehicle such as an On-Board Diagnostics (OBD) port. The purpose of the telematics device is to channel the vehicle battery voltage measurements for processing, as is described further below.

According to the claimed invention, the telematics device is connected to the vehicle battery to take a power supply from the battery. It has been recognised that an interruption in the power supply from the battery can be used to verify when the voltage monitoring unit of the telematics device is disconnected from the vehicle battery during a battery replacement event. Thus, the method further comprises: registering an interruption in the power supply from the battery and assessing whether the step change at a given time coincides with the interruption in the power supply to verify the battery replacement event. It is verified that a battery replacement event has taken place if the step change at a given time coincides with the interruption in the power supply.

Optionally, the method may further comprise applying a time stamp upon detecting an interruption in the power supply and using the time stamp as the given time of the step change. This provides a reliable approach to automatically identifying a battery replacement event, even if the step change is relatively small. An interruption in the power supply may also arise if the telematics device is disconnected from the vehicle. However, when the telematics device is reconnected there should not be a step change in the resting voltage magnitude or resting voltage profile. The voltage measurements from before and after disconnection of the telematics device may be used to verify that a battery replacement event has not taken place.

It will be understood that a step change in voltage magnitude can be defined as a significant jump in magnitude compared to an average or mean value of the voltage magnitude in the first time window. For example, a step change may be assessed as a change of at least <NUM>%, <NUM>%, <NUM>%, <NUM>%, or more, as compared to the average or mean value of the voltage magnitude. In at least some embodiments, the step change in voltage magnitude is compared with a threshold value to determine whether to automatically identify a battery replacement event. The threshold value may be a preset value (e.g. <NUM> V or <NUM> V for a <NUM> V battery) or a value that is set dynamically based on the average or mean value of the voltage magnitude. As described above, in at least some embodiments the step change is a step change in the resting voltage magnitude (i.e. measured in an engine off state). The resting voltage typically varies between <NUM> V and <NUM> V for a <NUM> V vehicle battery, and between <NUM> V and <NUM> V for a <NUM> V vehicle battery, depending on the battery model and age.

However, it will be appreciated that the method may not be able to tell apart a battery replacement event from a battery recharge event, as both events involve a step change in the voltage magnitude. In order to assess whether a battery has been replaced by a different one, rather than simply recharged, the voltage measurements can be exploited further so as to build up a voltage profile before and after a suspected battery replacement event. It has now been recognised that comparing before and after voltage profiles can be a powerful way of verifying battery replacement.

In one or more embodiments, monitoring the voltage measurements in the first time window comprises determining a first voltage profile as a function of time from voltage measurements in multiple instances of the first time window. In other words, the first voltage profile is built up from voltage measurements taken during several engine off periods. The multiple instances of the first time window are likely to be temporally separate engine off periods, separated by engine on i.e. driving periods. This means that the first voltage profile can provide an accurate representation of how the battery voltage normally changes over time in the first time window, with statistical variations being smoothed out by determining the first voltage profile from voltage measurements in multiple instances of the first time window. It has been found that the first voltage profile is characteristic of any given battery, which means that comparing the first voltage profile before and after a suspected battery replacement event can verify whether the battery is the same one that has been recharged or whether the battery has been replaced by a different one (which may even be the same or similar age).

In one or more embodiments, the method further comprises: comparing the first voltage profile determined before the given time of the step change with the first voltage profile determined after the given time of the step change; and identifying a discernible change in the first voltage profile before and after the given time of the step change to identify a different battery and verify the battery replacement event. The identification of a discernible change in the first voltage profile therefore indicates that the battery has been replaced by a different battery rather than recharged.

In some embodiments, the method may comprise only monitoring the voltage measurements in the first time window corresponding to an engine off state. Such limited voltage monitoring can be sufficient for the purposes of automatically identifying a battery replacement event, as described above. Furthermore, limiting the time periods when voltage measurements are obtained can reduce the processing power required and avoid the unnecessary transmission of data (e.g. when the telematics device is transmitting the voltage measurements to a remote server for processing).

However, it has been recognised that determining one or more further voltage profiles in other time windows corresponding to different vehicle states can be highly informative when assessing whether a battery replacement event has occurred. In particular, if a battery were to be replaced with another of the same make and similar age then it may be difficult to tell such a replacement apart from a recharging event.

In one or more embodiments, the method further comprises: determining a second voltage profile as a function of time from voltage measurements in multiple instances of a second time window corresponding to an engine start-up state and/or determining a third voltage profile as a function of time from voltage measurements in multiple instances of a third time window corresponding to an engine on state; comparing the second and/or third voltage profile determined before the given time of the step change with the second and/or third voltage profile determined after the given time of the step change; and identifying a discernible change in the second and/or third voltage profile before and after the given time of the step change to identify a different battery and verify the battery replacement event. Thus any discernible change in the second and/or third voltage profile may be used to verify a suspected battery replacement event, either in combination with a before and after comparison of the first voltage profile, or as an alternative. The data for EV/PHEV voltage profiles does not include any engine cranking phase since, for EVs/PHEVs, there is no cranking phase and thus no cranking characteristics can be measured.

It has been further recognised that combining multiples one of the first, second and/or third voltage profiles can give an overview of the battery's characteristic behaviour and state of health which acts like a signature enabling one battery to be differentiated from another. In one or more embodiments, the method further comprises: aggregating the first voltage profile with the second and/or third voltage profile to determine an overall battery voltage profile; comparing the overall battery voltage profile before the given time of the step change with the overall battery voltage profile after the given time of the step change; and identifying one or more discernible changes in the overall battery voltage profile before and after the given time of the step change to identify a different battery and verify the battery replacement event. The overall battery voltage profile therefore represents how the battery voltage typically varies as a function of time across the different time windows, encompassing different engine states, to give a signature unique to the battery. This overall battery voltage profile can be fed into standard machine learning methods to distinguish whether the battery before and after a suspected replacement event is the same one, or whether the battery has been changed or exchanged. It will be appreciated that such machine learning or statistical analysis methods being applied for EVs or PHEVs may be different to those applied for ICE vehicles since there will be different input data (relating to the vehicle battery voltage measurements) for the different types of vehicles.

In one or more embodiments, the method further comprises: using one or more machine learning or statistical analysis methods to identify one or more discernible changes in a voltage profile before and after the given time of the step change to identify a different battery and verify the battery replacement event. Such machine learning or statistical analysis techniques may be applied when comparing any one or more of the first, second or third voltage profiles before and after the given time of the step change. If the voltage profiles before and after are statistically matched then a battery replacement event is not verified. It may be determined that the battery was recharged rather than replaced.

In one or more of the embodiments described above, the discernible change in the voltage profile may relate to one or more characteristics of the voltage profile. In various embodiments, the discernible change relates to one or more of: a change in minimum resting voltage, or a change in auto-discharge rate for the battery. The relevant voltage profile characteristics may be determined by the applicable time window. For example, in some embodiments the method comprising identifying a discernible change in minimum resting voltage for the first voltage profile determined in the first time window corresponding to an engine off state. For example, in addition or alternatively, in some embodiments the method comprising identifying a discernible change in auto-discharge rate for the battery. A change in auto-discharge rate may be relevant for the first voltage profile, determined in the first time window corresponding to an engine off state, and/or for the third voltage profile, determined in the third time window corresponding to an engine on state.

In various of the embodiments described above, the method comprises building up voltage profiles during engine off periods, and optionally during engine start-up/driving periods, and comparing voltage profiles before and after the given time of the step change. A statistical comparison can be made to identify discernible changes that verify a battery replacement event occurred at the given time. However, it has been found that determining one or more voltage profiles is not essential. The method may simply assess when the voltage measurements indicate a step change in voltage magnitude by determining a mean or average resting voltage in the first time window (i.e. when the vehicle is in an engine off state). Taking into account that the voltage measurements in the first time window typically fall in magnitude from an initial value to a minimal resting voltage after a certain rest period (as the surface charge accumulated during driving wears off), this approach may look at a mean value for the minimal resting voltage. What is meant by the minimal resting voltage is the minimum value measured for the resting voltage in any given instance of the first time period, i.e. in any given resting period when the engine is off.

Thus, in one or more embodiments, monitoring the voltage measurements in the first time window comprises: determining a minimal resting voltage in each instance of the first time window, calculating a mean value for the minimal resting voltage from multiple instances of the first time window, and assessing when there is a step change in the mean value. As is described above, a step change may be assessed as a change of at least <NUM>%, <NUM>%, <NUM>%, <NUM>%, or more. Optionally, the step change in the mean value is compared with a threshold value to determine whether to automatically identify a battery replacement event. The threshold value may be a preset value (e.g. <NUM> V or <NUM> V for a <NUM> V battery) or a value that is set dynamically based on the mean value at any given time.

In one or more embodiments of any aspect of the invention disclosed above, the method further comprises: transmitting the battery voltage measurements from the telematics device in a vehicle to an external server. The battery voltage measurements may be time-stamped by a processor of the telematics device before being transmitted. The battery voltage measurements are preferably transmitted in real time. The battery voltage measurements are preferably transmitted continually. In some embodiments, the battery voltage measurements comprise "raw" voltage data received directly from the voltage monitoring unit. In other embodiments, the battery voltage measurements are preprocessed or pre-classified by a processor of the telematics device before being transmitted to the external server.

In some embodiments, the battery voltage measurements transmitted from the telematics device to the server may be stored before being processed according to the methods disclosed herein. In embodiments the method may comprise receiving the battery voltage measurements from the telematics device, and storing battery voltage measurements in a database for use in the methods described herein. The step of obtaining battery voltage measurements may then comprise obtaining the data from the database. It will be appreciated that the battery voltage measurements may be received and stored in a database at a first server and then obtained from the database by another server which implements the methods described herein, or the first server may both receive and store the battery voltage measurements and then carry out the processing according to the methods disclosed herein.

The server (using one or more processors) may be configured to apply one or more algorithms to process the voltage measurements, which algorithm(s) may be easily improved and updated as more data is received at the server, as compared to updating software on a processor of the telematics device or in the vehicle. For example, an algorithm which is used to detect a battery replacement event may be continuously retrained on new incoming voltage measurement data. Over time, as more data is provided from multiple telematics devices, the accuracy of the algorithm for detecting a battery replacement event will improve, without the need to apply updates to software in the telematics devices, which may be costly and time-consuming. In some embodiments, the methods disclosed herein may further comprise: implementing an algorithm to process the vehicle battery voltage measurements in a server remote from the telematics device; and updating the algorithm from time to time.

In any of the aspects and embodiments disclosed herein, the step of processing the battery voltage measurements may be carried out by a set of one or more processors. A given step may be carried out using the same or a different set of processors to any other step. Any given step may be carried out using a combination of sets of processors. The processing may be shared between processors. In at least some embodiments, the telematics device comprises a transceiver for transmitting the battery voltage measurements to a server for processing. As mentioned above, the server may be better suited to running multiple algorithms, including machine learning algorithms, to assess discernible changes in the voltage measurements as described herein. Some preprocessing or pre-classification may be carried out by a processor in the telematics device. The telematics device may also comprise a memory for storing the battery voltage measurements.

In a set of embodiments, the telematics device comprises a location sensor e.g. a GPS receiver (or any other global navigation satellite system (GNSS) receiver, or equivalent location-determining device), arranged to monitor the location of the vehicle, optionally wherein the location of the vehicle is logged at the time of an identified battery replacement event. For example, the location of the vehicle is logged by a processor in the telematics device and/or by the one or more processors in the server. In some embodiments, the location sensor provides location data for the vehicle at all times when the telematics device is obtaining vehicle battery voltage measurements using the voltage monitoring unit. In one or more embodiments, the methods disclosed herein further comprise: transmitting the battery voltage measurements and vehicle location data from the telematics device in a vehicle to an external server. The battery voltage measurements may be location-stamped (an optionally time-stamped) by a processor of the telematics device before being transmitted.

In a set of embodiments, the time and/or date of an identified battery replacement event is also logged (e.g. by a processor of the telematics device and/or by the one or more processors in the server). Alongside the location of the battery replacement event, this temporal information may be transmitted to a server, e.g. for display to the fleet manager. The fleet manger may therefore build up over time an overview of where and when battery replacement events occur. As mentioned above, any of the methods disclosed herein may further comprise: generating a notification of a battery replacement event or other state-related event. In at least some embodiments, the method further comprises: transmitting the notification to one or more display devices associated with the vehicle (optionally via the telematics device), with a driver of the vehicle (e.g. a driver's mobile device), and/or with a vehicle fleet manager (e.g. a fleet manager display device). When a battery replacement event occurs, the fleet manager may be provided with a notification via Mail/Web notification or via SMS. The fleet manager is therefore provided with real-time information as to the location of battery replacement events, and the fleet manager can therefore check that battery replacement events are taking place in approved facilities. Unwanted and unauthorised battery replacement events may therefore be detected in a location which deviates from a typical place, such as a garage or a roadside.

It will be appreciated that if the battery voltage measurements are stored at a server or database remote from the telematics device, the data are safely stored even if the telematics device is disconnected or stops working. Further to this, software at the server can be updated more easily than software used in a processor in the telematics device. If the bulk of the data processing and the more complex calculations are performed by the server, which will have higher processing power than the telematics device, processing of the voltage measurement data may be performed more quickly than processing at the telematics device.

The server may also use additional data, for example environmental data such as weather or temperature data relating to the vehicle, in the statistical analysis and machine learning processes which are used to automatically detect replacement of a vehicle battery. This additional data may not be available at the telematics device, but may be provided directly to the server, for example local temperature data may not be available at the telematics device but may be provided to the server from a weather service. Therefore, in some embodiments, the server is configured to receive environmental data relating to the vehicle which is further used to verify a battery replacement event.

In at least some embodiments, the methods disclosed herein may further comprise: generating a battery status notification, and optionally transmitting the notification to a display device associated with a vehicle fleet manager. If the server detects that a battery is failing and may need replacing soon, a warning may be provided to a user or fleet manager to inform them of the need for a battery change. If a subsequent battery replacement event is then detected, the server may correlate this with the warning which was issued. If the server stores the time/date of the last battery replacement, it may model the battery deterioration and then provide notifications as to when a battery may need replacing in the near future. The starting probability of a vehicle battery can be determined using battery voltage measurements according to known techniques, see e.g. <CIT>. Such calculations of the starting probability factor for a vehicle battery may benefit from taking into account the time/date of previous battery replacement event(s). Hence the methods disclosed herein may further comprise: determining a starting probability factor for the vehicle battery, indicative of the likelihood that the battery will be capable of starting the engine of the vehicle, based on the vehicle battery voltage measurements and a previously identified vehicle battery replacement event.

It will be understood that the server being arranged to remotely detect replacement of a vehicle battery means that the server is external to the vehicle, for example a server hosting a fleet management service. The external server is configured to receive vehicle battery voltage measurements from a telematics device in a vehicle, for example by receiving radio communications from a radio transceiver in the telematics device. In the systems disclosed herein, the external server may be arranged to receive vehicle battery voltage measurements from a radio transceiver in the telematics device.

The server and/or the system disclosed above may optionally include any of the features already described in relation to embodiments of the corresponding method.

It will be appreciated that the system and server disclosed above may therefore be used to remotely and automatically detect replacement of a vehicle battery associated with an engine in an EV or PHEV.

In a server as claimed, the telematics device in the vehicle is connected to the vehicle battery to take a power supply from the battery, the one or more processors being configured to assess whether the step change at a given time coincides with an interruption in the power supply to the telematics device to verify the vehicle battery replacement event. An interruption in the power supply from the battery may also be registered by a processor in the telematics device.

In a server as claimed, optionally monitoring the voltage measurements in the first time window comprises determining a first voltage profile as a function of time from voltage measurements in multiple instances of the first time window.

In a server as claimed, optionally the one or more processors are further configured to: compare the first voltage profile determined before the given time of the step change with the first voltage profile determined after the given time of the step change; and identify a discernible change in the first voltage profile before and after the given time of the step change to identify a different battery and verify the vehicle battery replacement event. Further optionally, wherein the discernible change relates to one or more of: a change in minimum resting voltage, a change in auto-discharge rate for the battery, or a change in at least one cranking or engine start-up characteristic.

In a server as claimed, optionally the server is configured to receive environmental data relating to the vehicle which is further used to verify a battery replacement event.

In a system as claimed, optionally the telematics device comprises a location sensor arranged to monitor the location of the vehicle and the location of the vehicle is logged at the time of an identified battery replacement event. The location of the vehicle may be logged by a processor in the telematics device and/or by the one or more processors in the server. Such embodiments are already described above.

In a system as claimed, optionally the time and/or date of an identified battery replacement event is logged (e.g. by a processor in the telematics device and/or by the one or more processors in the server). Such embodiments are already described above.

It will be appreciated that the methods disclosed herein may be implemented at least partially using software.

Some general features will now be described that apply equally to any of the aspects and embodiments described hereinabove.

The telematics devices will be understood to include at least the necessary electronic components to enable a telematics function. As already mentioned, the telematics device may comprise a location sensor, such as a GPS receiver (or any other global navigation satellite system (GNSS) receiver, or equivalent location-determining device), and a processor arranged to obtain location data based on measurements from the location sensor. In many embodiments, the telematics device may comprise a transceiver for external communications, for example configured to transmit the vehicle battery voltage measurements (and optionally location data) to a/the remote server. Further electronic components, such as an acceleration sensor or inertial measurement unit, may optionally be included in the telematics device.

It will be understood that the telematics device is mounted in the vehicle, but operates independently of the vehicle engine control unit (ECU) to obtain the vehicle battery voltage measurements. In some embodiments, the telematics device is a mobile device mounted in the vehicle. In some other embodiments, the telematics device is a fixed device mounted in the vehicle, for example plugged into an On-Board Diagnostics (OBD) port. The fixed device may include mechanical and/or electrical mounting means (e.g. for connecting to the power supply from an onboard battery). The telematics device being a fixed device means that it is not intended to be regularly removed and carried by a user in the form of a mobile device, however the fixed device may still be installable and removable rather than being a permanent fixture in the vehicle. In other words, the telematics device may be manufactured by a third party and installed in a vehicle subsequent to its manufacture, for example as part of a fleet management system. The telematics device can therefore be distinguished from any onboard data processing systems installed by the vehicle manufacturer. In various examples, the telematics device may be one of the LINK tracking devices available from Webfleet Solutions B.

<FIG> is a schematic overview of a system <NUM> which obtains and processes vehicle battery information from a vehicle <NUM>. The vehicle <NUM> includes an internal combustion engine or electric engine <NUM>, a battery <NUM> and an alternator (or DC-DC converter for an electric engine) <NUM> which can charge the battery <NUM> during operation of the vehicle <NUM>. The vehicle <NUM> further includes an On-board Diagnostics (OBD) port <NUM>. The OBD port <NUM> receives vehicle information from various vehicle sensors <NUM> as is well-known. One or more of the vehicle sensors <NUM> may be associated with the engine <NUM> e.g. to collect information such as engine RPM or temperature. The OBD port is connected directly or indirectly to the battery <NUM> to enable battery voltage measurements to be obtained. A telematics device in the form of a telematics control unit (TCU) <NUM> is plugged into the OBD port <NUM> and is in communication with an external server <NUM> which receives the vehicle battery information. The external server <NUM> comprises a processor <NUM>, communications device <NUM> and memory <NUM>. The server <NUM> is optionally in communication with distributed devices <NUM>, <NUM> that may be used to display (or otherwise communicate) notifications relating to a vehicle battery replacement event or other state-related event for the vehicle battery.

The TCU <NUM>, shown in more detail in <FIG>, further comprises a power supply <NUM> and plug <NUM>. The plug <NUM> connects the TCU <NUM> to the OBD port <NUM> such that the TCU <NUM> receives the vehicle information from the OBD port <NUM>. The power supply <NUM> may either be provided by the vehicle battery <NUM> via the plug <NUM> which connected the TCU <NUM> to the OBD port <NUM>, or the TCU <NUM> itself may have its own battery <NUM>. The TCU <NUM> also comprises a voltage monitoring unit <NUM>, processor <NUM>, memory <NUM>, GPS receiver <NUM>, and transceiver <NUM> for external communications. The transceiver <NUM> may, for example, be a radio transceiver configured to send vehicle data <NUM> (including battery voltage measurements) to the external server communications device <NUM>, where the data <NUM> may be analysed by the processor <NUM> in the server <NUM>. The radio transceiver may, for example, comprise a <NUM>/<NUM>/<NUM>/<NUM> modem. Alternately, data analysis may occur locally with the TCU processor <NUM>, or the analysis may be shared by the two processors <NUM>, <NUM>. Optionally, any notifications which result from this analysis are sent to a display <NUM> as shown in <FIG> which the vehicle's driver can access. The display <NUM> may be either fixed within a vehicle or remote e.g. a mobile phone. A fleet manager may also have access to a display <NUM> as shown in <FIG> which can be used to inform the fleet manager of vehicle battery replacement events or other battery state-related events. A location of the battery replacement event may be displayed together with the notification.

The TCU <NUM> may monitor vehicle device information, including battery-relevant information, provided by the vehicle sensors <NUM> via the OBD port <NUM>. For example, battery-relevant information may include battery current, battery temperature, vehicle speed, alternator/DC-DC converter current, alternator/DC-DC converter voltage etc. The TCU <NUM> transmits battery voltage measurements, along with any other vehicle information, as data <NUM> to the remote server <NUM>. The data <NUM> including battery voltage measurements may be collected during different phases of an engine cycle such as when the vehicle <NUM> is not in operation (engine off state), during cranking (for an ICE vehicle) or start-up (for EVs) of the engine <NUM>, or during normal operation whilst driving (engine on state). Ideally the battery voltage measurements are obtained regularly so as to monitor the vehicle battery at all times, regardless of vehicle use. Battery voltage measurements are obtained by the voltage monitoring unit <NUM>. In this example the voltage monitoring unit <NUM> is incorporated into the TCU <NUM>, but in other examples the voltage monitoring unit <NUM> may be part of the vehicle engine or its on-board diagnostics system, with the voltage measurements being transferred to the TCU <NUM> via the OBD port <NUM>. The voltage measurements may be collected at different rates depending on the state of the vehicle <NUM>. For example, when the vehicle is not in operation, or resting, the voltage data rate may be once every two hours, with a sampling rate of once every <NUM> minutes when the vehicle <NUM> is in operation and is being charged by the alternator (or DC-DC converter) <NUM>. An even higher sampling rate, such as <NUM>-<NUM>, may be used during engine start-up or cranking.

Once collected by the TCU <NUM>, the data <NUM> which is sent to the external server <NUM> may be processed and analysed using algorithms and machine learning to automatically identify a vehicle battery replacement event or other state-related event for the vehicle battery <NUM>. For example, the data <NUM> may be monitored over time to build up one or more voltage profiles for the battery <NUM>. Changes in the battery voltage profile may then be used to identify when the battery <NUM> in a vehicle <NUM> has been replaced or another state-related event has occurred. The battery voltage profile may include characteristics such as the minimum resting voltage (which is always the voltage closest to the OCV (Open Circuit Voltage)), the auto-discharge rate, one or more start-up or cranking voltage characteristics, etc. which are extracted from the data <NUM>. Additionally, the usage characteristics of the vehicle <NUM> and environmental conditions are also typically taken into consideration when assessing the battery voltage profile(s). A starting probability factor for the vehicle battery <NUM> is optionally calculated, e.g. as disclosed in <CIT>, to assist with generating an advance notification that the battery may need to be replaced.

The GPS receiver <NUM> may be used to determine the current location of the vehicle to which the TCU <NUM> is connected. This location data may also be sent from the TCU <NUM> to the external server <NUM>, and the location of any battery-related events may therefore also be determined, for example allowing a fleet manager to check if a battery was replaced at an approved location.

<FIG> is a schematic diagram illustrating a method of monitoring the voltage of a vehicle battery (e.g. in an ICE vehicle) before and after a power disconnect event. In this example the TCU <NUM> is powered by the vehicle battery <NUM>, in which case the TCU <NUM> will not send any data <NUM> to the external server <NUM> to be used for battery voltage profiling when the battery is removed. Upon replacement of the battery <NUM>, the TCU <NUM> will again begin to send data <NUM> to the sever <NUM>; there will therefore be a first battery voltage profile <NUM> prior to the power disconnect (i.e. interruption) and a second battery voltage profile <NUM> after the power disconnect (i.e. interruption) when the (same or different) battery <NUM> has been replaced.

These two battery voltage profiles <NUM>, <NUM> may therefore be compared at step <NUM>, as shown in <FIG>, in order to identify whether after the power disconnect event the same battery is in the vehicle, if the same battery as before has been re-charged, or if the battery has been replaced with a different one. This comparison step <NUM> may consist of a statistics/machine learning method such as Gaussian-Mixture-Models, Multivariate-T-Student Test, Neural Networks, Cluster-based Local Outlier Factor, Histogram-based Outlier Detection, Isolation Forest, K-Nearest Neighbours, etc. Alternatively, a mean value for the minimal resting voltage could be calculated from the battery data <NUM> when the vehicle was resting before and after the power disconnect event. The difference in the mean value could be calculated and a threshold applied to detect when there is a step change in the mean value, indicating a different battery. This threshold may be calculated based on battery usage and statistical properties.

Coinciding with a power disconnect event there is usually a step change <NUM> in resting voltage magnitude, as shown in <FIG> is a graph of voltage measurements with respect to time, showing resting voltage data <NUM> (measured in individual time windows each corresponding to an engine off state i.e. during individual "standstills"). Resting voltage data <NUM> is collected when the engine is off over a time period <NUM> corresponding to multiple instances of each individual engine off time window. During vehicle resting periods, the voltage of the battery will decrease due to auto-discharge. The resting voltage data <NUM> before the power disconnect is shown with the solid line, with the resting voltage data <NUM> after the power disconnect shown with a dashed line. The minimal resting voltage <NUM> in each instance of the engine off time window may be determined and a step change detection may be executed on the data points in order to identify battery replacement or recharge. The step change <NUM> in resting voltage before and after the power disconnect event is clear from <FIG>. The step detection window <NUM> over which the voltage data <NUM>, <NUM> is assessed to identify if there has been a step change <NUM> in resting voltage typically extends over several days (e.g. <NUM>-<NUM> days, for example a minimum of <NUM>-<NUM> days) however this may depend on the usage pattern prior to and after the disconnect. The resting voltage <NUM>, <NUM> typically varies between 11V and <NUM>. 5V for 12V batteries, and 22V and 28V for 24V batteries. These values may be used when setting a threshold to assess when there has been a step change in the resting voltage magnitude.

Even if a power disconnect is not detected, for example because the TCU <NUM> has its own power supply, the step change <NUM> in resting voltage data <NUM>, <NUM> can be used to automatically identify a vehicle battery replacement event. The TCU <NUM> registering an interruption in power supply can verify a battery replacement event but this is not required.

<FIG> provides an example of a first voltage profile 45a, 45b as a function of time in a first time window corresponding to an engine off state, for two different batteries. By monitoring the voltage measurements in multiple instances of the first time window, it is possible to build up a voltage profile 45a, 45b that represents the normal behaviour of the battery and its state of health during engine off i.e. resting periods. The battery resting voltage during each resting period is divided into phases, as shown in <FIG>. The first phase is influenced by the surface charge which will accumulate when driving the vehicle. The surface charge then reduces until it vanishes - this occurs over several hours e.g. <NUM>-<NUM> hours depending on the environment and usage. This loss of the surface charge marks the beginning of the second phase where the natural auto-discharging of the battery occurs. Through measurement of the slope of the second phase, different batteries and states of batteries may be identified. For example, the solid line in <FIG> shows a battery voltage profile 45a for a first battery in a time window corresponding to the engine off state. The dashed line shows a battery voltage profile 45b for a second, different battery in a time window corresponding to the engine off state. Both battery voltage profiles 45a, 45b can be built up from resting voltage measurements in multiple instances of the engine off time window, i.e. across a time period of several days or even months. With reference to <FIG>, if the profile 45a is a first profile <NUM> determined before power disconnect and the profile 45b is a second profile <NUM> determined after power disconnect, then comparing the two voltage profiles 45a, 45b there can be identified a discernible change to thereby identify a different battery and verify that a battery replacement event did coincide with the power disconnect. The same verification can be applied even if a power disconnect or interruption is not registered.

<FIG> is a graph showing a cranking voltage profile <NUM> with respect to time for two different batteries in ICE vehicles. <FIG> shows how the battery voltage prior to engine start has a magnitude corresponding to the open circuit voltage (OCV). Immediately following an engine start event, the voltage drops in magnitude from the OCV to a lower value, resulting in a voltage drop magnitude <NUM>. This initial voltage drop is instantaneous, and should be the lowest voltage measurement during cranking. The voltage drop may be taken to define the start of the engine cranking state. As the engine RPM increases, the load on the electromotor decreases and the battery voltage recovers. There can be seen some local voltage peaks corresponding to the high mechanical resistance induced by the compression process in a four-stroke engine. The cranking duration <NUM> is the time taken for the voltage to reach a steady state indicating the end of engine start-up. Beyond the period <NUM>, the alternator should start to recharge the battery. This is discussed further below with reference to <FIG>.

A voltage profile <NUM> determined from voltage measurements in a time window corresponding to an engine cranking state can indicate the state of health of the battery. The state of health of the battery may be identified from one or more cranking characteristics recognised in the cranking voltage profile. For example, the cranking characteristic comprises at least one of the voltage drop magnitude <NUM> and cranking duration <NUM>. The cranking duration <NUM> typically varies from sub-second to several seconds e.g. <NUM>-<NUM> seconds. As with the resting voltage data <NUM>, <NUM> of <FIG>, the cranking voltage profiles <NUM> are determined from voltage measurements collected in multiple instances of the cranking time window (i.e. several individual crankings). Further information regarding how a state of health may be assessed for a vehicle battery, based on cranking characteristics, may be found in <CIT>, the contents of which are hereby incorporated by reference.

The resting voltage data shown in <FIG> and <FIG>, alongside the state of health identified from the cranking voltage profile <NUM>, can then be further used in identifying the battery or battery state.

<FIG> shows the frequency of different characteristics <NUM>, <NUM>, <NUM>, <NUM> for two different batteries (e.g. in an ICE vehicle). An overall battery voltage profile <NUM> may be obtained using an aggregation of the characteristics such as the minimal resting voltage data <NUM>, auto-discharge rate <NUM>, and cranking voltage characteristics such as cranking duration data <NUM> and cranking drop magnitude <NUM>, alongside other factors. The aggregated data may be fed into standard machine learning methods to distinguish if the battery before and after a power disconnect (or otherwise suspected battery replacement event) is the same or if the battery has changed or been exchanged. One example is to execute a t-test to decide if the overall battery voltage profile <NUM> before, and the overall battery voltage profile <NUM> after, the power disconnect are statistically different. The t-test will look at the mean and variances to decide if the two distributions <NUM>, <NUM> are equal or different. The t-test may be tuned to be more or less aggressive to react to small or large changes in voltage profile through setting a lower threshold for the computer p-value to detect more clearly distinct values. An example of differing battery voltage profiles <NUM>, <NUM> is shown in <FIG> where at least some of the battery characteristics <NUM>, <NUM>, <NUM>, <NUM> diverge, i.e. there is a discernible change, such that the different overall battery voltage profiles <NUM>, <NUM> are clearly recognised and can be used to verify a battery replacement event.

While the description above has focused so far on automatically identifying a battery replacement event, it will be appreciated that assessing when a battery voltage profile undergoes a discernible change can be used to automatically identify other state-related events for the vehicle battery. With reference to <FIG>, it can be seen that voltage profiles determined for different time windows (corresponding to different engine states) have been aggregated to determine an overall battery voltage profile <NUM>, <NUM>. The overall battery voltage profile <NUM> may be determined from historical battery voltage measurements while the overall battery voltage profile <NUM> may be determined from current battery voltage measurements. By comparing the overall battery voltage profiles <NUM>, <NUM>, is possible to identify one or more discernible changes in the overall battery voltage profile to automatically identify a particular state-related event for the vehicle battery. Examples of identifiable state-related events include: a different battery; a different battery health state; a problematic engine start attempt event for the battery; a charging or discharging issue; an alternator malfunction; or a battery replacement event. These examples will be explained further below.

<FIG> is a graph showing voltage profiles <NUM>, <NUM> with respect to time for a working and malfunctioning ('failing') vehicle alternator, used to charge a battery in an ICE vehicle. Battery voltage measurements obtained during a driving phase (engine on state) are used to identify if the alternator is working. The voltage profile <NUM>, <NUM> is determined to identify how often and for how long the voltage magnitude raised over a certain threshold which will indicate a working alternator and to check for any continuous voltage decreases during the driving phase. The engine on/driving phase begins after a successful cranking which will be indicated by a raising voltage. If this value is not available, the beginning of the driving phase may be identified by movement of the vehicle while the ignition is on.

Initially, the algorithm used to process the battery voltage measurements waits for a defined period of time e.g. <NUM> minutes as the alternator does not charge the battery immediately after the engine is started. If the alternator is not working, then the driving voltage profile <NUM> will begin to decline over time (in the engine on state) as the battery is continually discharged. If the voltage profile <NUM> goes beneath a certain threshold Vthresh over a minimal period e.g. <NUM> minutes then an alternator malfunction warning may be generated (and optionally transmitted by the remote server <NUM> to the display <NUM> where the vehicle user can be warned). The threshold may be defined dynamically by using the voltage measurements of the resting period (engine off) before driving. If the alternator is working, the voltage profile <NUM> must increase over a value larger than the minimum voltage <NUM> of the last resting period. As such, every new voltage measurement in the profile <NUM> above this threshold which is collected during the driving phase indicated that the alternator is working properly.

<FIG> is a graph showing cranking voltage profiles <NUM>, <NUM> against time for a successful and failed engine cranking. Cranking problems may be detected through an examination of the success and frequency of crankings. The cranking traces shown in <FIG> may be initially classified into a 'succeeded' voltage profile <NUM>, a 'failed' voltage profile <NUM>, or 'unknown', e.g. by the server <NUM>. The classified crankings <NUM>, <NUM> may then be clustered into groups of engine start attempts. <FIG> shows clustering of different engine start attempts against time. Through statistical analysis of the cranking results in each group it is possible to evaluate the difficulty of the engine start attempt and detect a problem.

The cranking traces <NUM>, <NUM> shown in <FIG> are captured during the ignition event with a high sample rate e.g. <NUM>-<NUM>, with every cranking classified into multiple possible cranking result classes. A successful cranking voltage profile <NUM> (solid line) and failed cranking voltage profile <NUM> (dashed line) is shown in <FIG>. Failed cranking voltage profiles <NUM> typically have more variation in the lower voltage regions and a much lower voltage at the end of cranking than a successful cranking voltage profile <NUM>. However, this varies and as such, machine learning methods such as Gaussian Mixture Models, Extra Tree Classifiers, Convolutional Neural Networks, Recurrent Neural Networks, Principle Component analysis, Independent Component Analysis are applied to distinguish the result classes. The inputs used for the machine learning methods are the cranking voltage profiles <NUM>, <NUM> in the time domain and a filtered version of the traces in the frequency domain. A pre-classification on the TCU <NUM> may also be performed.

Once the cranking voltage profile <NUM>, <NUM> has been classified, crankings may be clustered into groups of engine start attempts. The clustering occurs in the time domain such that crankings which occur close in time are clustered together, as shown in <FIG>. This clustering may be carried out using e,g, density-based methods, K-Means etc. An examination of the clusters may be carried out to calculate the success rate per cluster, as shown in <FIG>, where cluster <NUM> includes four cranking traces <NUM> which have been previously classified into successful and failed crankings. As three of the cranking traces <NUM> in cluster <NUM> are failed crankings, and one is successful, cluster <NUM> has a success rate of <NUM>%.

The cluster success rate may then be compared against a threshold success rate e.g. <NUM>%. As cluster <NUM> has a success rate below <NUM>% then it can be identified as a problematic cluster and a "problematic engine start attempt event" may be generated, and optionally sent to the fleet manager display <NUM> or the vehicle user display <NUM>.

<FIG> shows battery resting voltage <NUM> with respect to time for multiple vehicle resting periods (engine off windows), labelled as "standstills". When drivers only use a vehicle regularly in short intervals, there may not be enough driving time to properly recharge the battery. The battery is only charged correctly after a minimum driving time e.g. <NUM> minutes. Batteries can have different capacities - vehicles with larger batteries typically have stronger alternators, vehicles with smaller batteries typically have weaker alternators, and the minimum driving time for recharge is therefore fairly constant across different capacity batteries.

A driver may only use their vehicle twice a day for <NUM> minutes e.g. driving a short distance to/from work. In this case, the battery would be constantly discharged over a longer time until there is insufficient charge to start the engine, or the health of the battery has degraded such that the engine cannot start.

Through measurements of the battery resting voltage <NUM> during resting periods, insufficient driving time can be identified which is an indication of problematic driving behaviour. The maximum voltage <NUM> of each resting voltage measurement <NUM> shown in <FIG> decreases over time. Resting voltage measurements <NUM> may be collected over a long time period P e.g. <NUM> weeks.

A problematic driving behaviour warning may be generated if both:.

Point <NUM> avoids generation of a warning when the voltage measured decays only due to the long resting period - this is shown in <FIG>. In point <NUM> the last measured resting voltage <NUM> of each resting period is compared to the resting voltage <NUM> at the start of the next n resting periods. The value of n is chosen dynamically such that at least the next five resting periods and at least the next two days are considered. If none of the next n resting periods begin with a considerably higher voltage e.g. +<NUM> V then the resting voltage <NUM> for that resting period may be considered as non-recovered. If all resting voltages <NUM> during a period P are considered as non-recovered then a problematic driving behaviour notification may be created (and e.g. sent to the fleet manager display <NUM> or the vehicle user display <NUM>). The driver may then take measures to avoid battery discharge such as recharging the battery or taking longer trips.

<FIG> shows a battery resting voltage profile <NUM> with respect to time, as determined from voltage measurements in multiple instances of the resting period time window. <FIG> further illustrates a predicted future battery resting voltage profile <NUM>. When a vehicle is not driving, the battery naturally auto-discharges over time. If this resting period exceeds weeks or months then the battery may be too discharged to start the engine of the vehicle. If the resting voltage <NUM> is measured during a resting period then it is possible to detect when the resting voltage <NUM> drops below a critical level e.g. <NUM> V for a <NUM> V battery.

Detecting when the resting voltage has passed this threshold <NUM> may not be useful, however, as at this time the battery will already be in a problematic state. An algorithm may therefore be used by the processors <NUM>, <NUM> to forecast the battery resting voltage <NUM> during resting periods of the vehicle.

If the vehicle is detected to be standing still for several days e.g. <NUM> days, the resting voltage measurements <NUM> taken during those days may be used to forecast the resting voltage profile <NUM> for a future time period e.g. the next four weeks.

There are at least two ways of forecasting the future resting voltage profile <NUM>:.

If the processor <NUM>, <NUM> calculates that the forecasted voltage values will drop below a critical level <NUM>, then a warning may be generated to be displayed on the fleet manager display <NUM> or the vehicle user display <NUM> that the vehicle must be moved, or the battery externally charged in order to avoid starting problems in a given period.

<FIG> is a flowchart showing a possible method of automatically identifying a battery replacement event through voltage monitoring. In step <NUM>, the battery voltage is monitored - this may be during resting, driving and/or cranking. This voltage data is then aggregated in step <NUM> to form a battery voltage profile for that specific battery. A power disconnect event is registered in step <NUM>, after which the battery voltage is again monitored in step <NUM> and used to build up a new battery voltage profile in step <NUM>. The battery voltage profiles before and after the power disconnect event are then compared in step <NUM>. If the voltage profiles are statistically the same, it is determined that the same battery is still in the vehicle. If the battery voltages profiles exhibit one or more discernible changes, as shown in step <NUM>, this may indicate the battery has been recharged or replaced - an appropriate notification may then be generated.

<FIG> is a schematic diagram illustrating a method of monitoring the voltage of an EV/PHEV vehicle battery before and after a power disconnect event. In this example the TCU <NUM> is powered by the electric vehicle battery <NUM>, in which case the TCU <NUM> will not send any data <NUM> to the external server <NUM> to be used for battery voltage profiling when the battery is removed. Upon replacement of the battery <NUM>, the TCU <NUM> will again begin to send data <NUM> to the sever <NUM>; there will therefore be a first battery voltage profile <NUM> prior to the power disconnect (i.e. interruption) and a second battery voltage profile <NUM> after the power disconnect (i.e. interruption) when the (same or different) battery <NUM> has been replaced.

Compared to the data <NUM> shown in <FIG> for an ICE vehicle, the data <NUM> does not include the cranking characteristics since for EV/PHEV there is no cranking phase, and thus no cranking characteristics can be measured.

<FIG> is a graph showing an engine start voltage profile <NUM> with respect to time for a battery in an EV/PHEV. <FIG> shows how the battery voltage prior to engine start (ON) has a magnitude corresponding to the open circuit voltage (OCV). The engine start-up phase has a duration <NUM>, which is the time taken for the voltage to reach a steady state indicating the end of engine start-up. Beyond the period <NUM>, the DC-DC converter should start to recharge the battery. This is discussed further below with reference to <FIG>. It is clear that for an EV/PHEV engine battery, there is no cranking phase, compared to the cranking voltage profiles shown in <FIG> for an ICE vehicle battery.

A voltage profile <NUM> determined from voltage measurements in a time window corresponding to an engine starting state can indicate the state of health of the battery. The state of health of the battery may be identified from engine starting characteristics recognised in the starting voltage profile. For example, the starting characteristic comprises the engine start-up duration <NUM>. The engine start-up duration <NUM> typically varies from sub-second to several seconds e.g. <NUM>-<NUM> seconds. As with the cranking voltage profiles <NUM> of <FIG>, the engine starting profiles are determined from voltage measurements collected in multiple instances of the engine start-up time window (i.e. several individual engine start-ups). The state of health identified from the engine start-up voltage profile <NUM> can then be further used in identifying the battery or battery state.

<FIG> is a graph showing voltage profiles <NUM>, <NUM> with respect to time for a working and malfunctioning ('failing') vehicle DC-DC converter (such as a 12V DC-DC converter), used to charge a battery in an EV/PHEV. Battery voltage measurements obtained during a driving phase (engine on state) are used to identify if the DC-DC converter is working. The voltage profile <NUM>, <NUM> is determined to identify how often and for how long the voltage magnitude raised over a certain threshold which will indicate a working DC-DC converter and to check for any continuous voltage decreases during the driving phase. The engine on/driving phase begins when the engine is turned on, which will be indicated by a rising voltage. If this value is not available, the beginning of the driving phase may be identified by movement of the vehicle while the ignition is on.

Initially, the algorithm used to process the battery voltage measurements waits for a defined period of time e.g. <NUM> minutes as the DC-DC converter does not charge the battery immediately after the engine is started. If the alternator is not working, then the driving voltage profile <NUM> will begin to decline over time (in the engine on state) as the battery is continually discharged. If the voltage profile <NUM> goes beneath a certain threshold Vthresh over a minimal period e.g. <NUM> minutes then a DC/DC converter malfunction warning may be generated (and optionally transmitted by the remote server <NUM> to the display <NUM> where the vehicle user can be warned). The threshold may be defined dynamically by using the voltage measurements of the resting period (engine off) before driving. If the DC/DC converter is working, the voltage profile <NUM> must increase over a value larger than the minimum voltage of the last resting period. As such, every new voltage measurement in the profile <NUM> above this threshold which is collected during the driving phase indicated that the alternator is working properly.

Claim 1:
A server (<NUM>) arranged to remotely and automatically detect replacement of a vehicle battery (<NUM>) associated with a vehicle engine (<NUM>), the server (<NUM>) comprising:
a communications device (<NUM>) configured to receive vehicle battery voltage measurements from a telematics device (<NUM>) in a vehicle (<NUM>), wherein the telematics device (<NUM>) is connected to the vehicle battery (<NUM>) to take a power supply from the battery (<NUM>), and is connected to or incorporates a voltage monitoring unit (<NUM>) for the vehicle battery (<NUM>); and
one or more processors (<NUM>) configured to process the vehicle battery voltage measurements by:
monitoring the voltage measurements in a first time window corresponding to an engine off state;
assessing when the voltage measurements in the first time window indicate a step change in voltage magnitude at a given time; and
using the step change to automatically identify a vehicle battery replacement event;
wherein the one or more processors (<NUM>) are further configured to:
register an interruption in the power supply from the battery (<NUM>) to the telematics device (<NUM>) and assess whether the step change at a given time coincides with the interruption in the power supply to verify the vehicle battery replacement event.