Associating vehicle parameters with maintenance actions
Through communication between the equipment and accessories, BMS and servers, vehicle parameters are acquired and analyzed, maintenance actions are determined and triggered, solving the problem of insufficient failure prediction of vehicle systems and components, and achieving timely maintenance and safety improvement.
Patent Information
- Application Number
- CN202380093792.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-12-29
- Filing Date
- 2023-12-29
- Publication Date
- 2025-09-19
AI Technical Summary
Existing vehicle systems and components lack the ability to timely and accurately predict component and/or system failures and schedule repair and replacement of specific vehicle components and/or systems.
The device communicates with accessories, the battery management system (BMS), and the server to obtain vehicle parameters, battery parameters, and accessory parameters, determine maintenance parameters based on these parameters, and trigger corresponding maintenance actions, such as battery replacement or brake pad replacement.
It enables timely maintenance of vehicle systems and components, reduces unnecessary costs and safety hazards, and improves the operating efficiency and safety of vehicles.
Smart Images

Figure CN120677498A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates particularly to a method, apparatus, and system for associating parameters with various maintenance actions. Background Art
[0002] Motorized vehicles and / or electric vehicles rely on various systems and components within the vehicle so that the vehicle can operate efficiently, safely and correctly. Such vehicles can include one or more of aerial or marine vehicles, rail vehicles, street or road vehicles, etc., wherein street or road vehicles can refer to one or more of, for example, cars, trucks, buses, recreational vehicles, all-terrain vehicles, off-road vehicles, etc. Various systems and components are present in the vehicle to allow the vehicle to function in an efficient, safe and effective manner. However, when one or more of these systems and / or components fail to operate as expected, there may be negative consequences, including safety, efficiency and performance issues.
[0003] Various systems and components in a vehicle may require maintenance, care, and attention, and may include battery systems, belts and hoses, brake systems, exhaust systems, engine cooling systems, exhaust systems, oil and filters, fuel systems, lighting and wipers, steering and suspension systems, powertrain systems, and the like. A non-limiting example of other various systems and components that may also require maintenance, care, and attention is the battery system. Depending on the type of vehicle, there may be one or more battery systems to provide the vehicle with starting power (e.g., power for starting and cranking the engine) and / or at least a portion of the motor power. The type of battery system(s) used in a vehicle may depend on many factors, including the type of engine in the vehicle, the type of vehicle, the customization of the vehicle, and the operator's driving style. The battery system(s) may include a traction battery (for electric vehicles or hybrid vehicles) and a starter battery. The starter battery can be used to provide the necessary energy / power required to start the vehicle, and the traction battery can generally refer to the battery that provides power to the electric motor. Each type of battery system may have different requirements, maintenance, and other parameters in order for each battery system to operate efficiently and effectively. Further, battery manufacturers generally recommend replacing batteries after predetermined time intervals and may have specific maintenance recommendations associated with particular batteries.
[0004] However, some batteries may fail before the predetermined time interval for a variety of reasons, including manufacturing defects, environmental conditions, the type of driving that occurs on the vehicle, the customization of the vehicle, and the frequency of driving. If a battery in a vehicle fails for any reason, this may result in inconvenience, safety issues, and unexpected visits to a battery replacement center. Other systems and components of the vehicle may also fail before the specific predetermined time interval for a variety of reasons, also including manufacturing defects, environmental conditions, the type of driving that occurs on the vehicle, the customization of the vehicle, and the frequency of driving. Failure of these systems and components may also cause inconvenience and lead to safety issues. Further, failure to perform timely maintenance and repair of the vehicle related to the systems and components may result in unnecessary expenses and failure of systems, components, and / or the entire vehicle. Summary of the Invention
[0005] Existing vehicle systems and components lack the ability to timely and accurately predict component and / or system failures and schedule repair and replacement of specific vehicle components and / or systems.
[0006] Some embodiments advantageously provide a method, apparatus, and system for mobile applications that may be configured to associate parameters with various maintenance actions, such as associating vehicle maintenance and vehicle diagnostics with battery replacement.
[0007] According to one aspect, a device configured to communicate with one or more of an accessory, a battery management system (BMS), and a server is described. The device includes processing circuitry configured to obtain one or more of vehicle parameters, battery parameters, and accessory parameters from one or more of the accessory, the BMS, and the server. The processing circuitry is further configured to determine maintenance parameters based on one or more of the vehicle parameters, the battery parameters, and the accessory parameters. The processing circuitry is further configured to determine one or more maintenance actions based on the determined one or more maintenance parameters.
[0008] In some embodiments, the vehicle parameters can be received from one or both of the accessory and the server.
[0009] In some other embodiments, the battery parameters may be received from a BMS.
[0010] In some embodiments, battery parameters can be received from the accessory.
[0011] In some other embodiments, one or both of the vehicle parameters and the battery parameters may be received from the BMS via the accessory.
[0012] In some embodiments, one or both of the vehicle parameters and the battery parameters may include one or more original equipment manufacturer (OEM) maintenance schedules.
[0013] In some other embodiments, one or more OEM maintenance schedules are user customizable based on one or more of vehicle parameters, battery parameters, and accessory parameters.
[0014] In some embodiments, the vehicle parameter is one or more of vehicle spark plug performance, spark plug operation, and spark plug maintenance.
[0015] In some other embodiments, the battery parameter is one or more of battery performance, battery management, battery operation, battery maintenance, and battery health.
[0016] In some embodiments, the processing circuitry is further configured to assign a rating to each of the vehicle parameters, the battery parameters, and the accessory parameters.
[0017] In some embodiments, the rating is based on one or more of a predetermined battery life cycle, a battery parameter threshold, a service promotion, a maintenance schedule, a reminder, and a recall.
[0018] In some other embodiments, the determined one or more maintenance parameters include a recommended service visit time and a priority associated with one or more of a vehicle parameter, a battery parameter, and an accessory parameter.
[0019] In some embodiments, the determined one or more maintenance actions indicate a battery replacement.
[0020] In some other embodiments, the determined one or more maintenance actions further indicate at least one location to purchase the battery.
[0021] In some embodiments, the processing circuitry is further configured to identify a preset battery function and a preset vehicle parameter. The processing circuitry is further configured to trigger the determined one or more maintenance actions based on the preset battery function and the preset vehicle parameter, and the determined one or more maintenance actions indicate battery replacement.
[0022] In some other embodiments, the processing circuitry is further configured to identify a preset battery parameter and trigger the determined one or more maintenance actions based on the preset battery parameter. The determined one or more maintenance actions may indicate replacing at least one brake pad.
[0023] In some other embodiments, the determined one or more maintenance actions include at least two vehicle maintenance services.
[0024] In some embodiments, the processing circuitry is further configured to identify a preset vehicle parameter of the vehicle alternator and trigger one of the determined one or more maintenance actions based on the preset vehicle parameter. The determined one or more maintenance actions may indicate a remaining life cycle of the battery.
[0025] In some other embodiments, the processing circuitry is further configured to download one or more maintenance schedules from a server.
[0026] In some embodiments, the one or more processing circuit systems are further configured to generate a maintenance action indication. The maintenance action indication is one or more of: notifying a user of one or more maintenance actions; causing one or more of an accessory, a BMS, a server, and a vehicle system to perform another action; being included in a message transmitted by the device to one or more of the accessory, the BMS, the server, and the vehicle system; and causing the device to display a reminder for the user on the device. The another action includes one or both of scheduling a maintenance appointment and creating a record accessible to a service provider, the record indicating the one or more maintenance actions determined. The another action includes causing the BMS to switch to a predetermined operating mode. The another action includes causing the vehicle system to perform one or both of: displaying another reminder and disabling or enabling a driving mode.
[0027] According to one aspect, a device can be configured to communicate with one or more of an accessory, a battery management system (BMS), and a server. The device can include processing circuitry configured to obtain one or more of: vehicle parameters received from one of the accessory and the server, battery parameters received from one of the BMS and the accessory, and accessory parameters received from one or more of the accessory, the BMS, and the server. The processing circuitry can be further configured to obtain one or more of: vehicle capabilities received from one of the accessory and the server, battery capabilities received from one of the BMS and the accessory; and The processing circuitry may be configured to determine one or more maintenance parameters based on the vehicle parameters, the battery parameters, and the accessory parameters and one or more of the vehicle functions, the battery functions, and the accessory functions. The processing circuitry may be further configured to determine one or more maintenance actions based on the determined one or more maintenance parameters.
[0028] In some embodiments, one or both of the vehicle parameters and the battery parameters include one or more Original Equipment Manufacturer (OEM) maintenance schedules.
[0029] In some other embodiments, one or more OEM maintenance schedules are user customizable based on one or both of vehicle parameters and battery parameters.
[0030] In some embodiments, the vehicle parameter is at least one of vehicle spark plug performance, spark plug operation, and spark plug maintenance.
[0031] In some other embodiments, the battery parameter is one or more of battery performance, battery management, battery operation, battery maintenance, and battery health.
[0032] In some embodiments, the processing circuitry is further configured to assign a rating to each of the vehicle parameters, the battery parameters, and the accessory parameters.
[0033] In some other embodiments, the rating is based on one or more predetermined battery life cycles, battery parameter thresholds, service promotions, maintenance schedules, reminders, and recalls.
[0034] In some embodiments, the one or more maintenance parameters include a suggested service visit time and a priority associated with one or more of a vehicle parameter, a battery parameter, and an accessory parameter.
[0035] In some other embodiments, the determined one or more maintenance actions indicate a battery replacement.
[0036] In some embodiments, the determined one or more maintenance actions further indicate at least one location for battery replacement.
[0037] In some other embodiments, the processing circuitry is further configured to assign another level to each of the vehicle function, the battery function, and the accessory function.
[0038] In some embodiments, the one or more processing circuit systems are further configured to generate a maintenance action indication, and the maintenance action indication is one or more of: notifying a user of the one or more maintenance actions and causing one or more of the accessory, the BMS, the server, and the vehicle system to perform another action. Furthermore, the processing circuit system is further configured to cause the device to display a reminder on the device for the user, and the another action includes one or both of scheduling a maintenance appointment and creating a record accessible to a service provider, wherein the record indicates the determined one or more maintenance actions. The another action includes causing the BMS to switch to a predetermined operating mode, and the another action includes causing the vehicle system to perform one or both of: displaying another reminder and disabling or enabling a driving mode.
[0039] According to one aspect, a method in a device can be configured to communicate with one or more of an accessory, a battery management system (BMS), and a server. The method can include obtaining one or more of vehicle parameters, battery parameters, and accessory parameters from one or more of the accessory, the BMS, and the server. The method can include determining one or more maintenance parameters based on one or more of the vehicle parameters, the battery parameters, and the accessory parameters. The method can also include determining one or more maintenance actions based on the determined one or more maintenance parameters.
[0040] In some embodiments, the method further includes assigning a rating to each of the vehicle parameter, the battery parameter, and the accessory parameter.
[0041] In some other embodiments, the rating is based on one or more of a predetermined battery life cycle, a battery parameter threshold, a service promotion, a maintenance schedule, a reminder, and a recall.
[0042] In some embodiments, the method further includes identifying a preset battery function and a preset vehicle parameter, and triggering one or more determined maintenance actions based on the preset battery function and the preset vehicle parameter, the one or more determined maintenance actions indicating battery replacement.
[0043] In some other embodiments, the method further includes identifying a preset battery parameter and triggering the determined one or more maintenance actions based on the preset battery parameter, the determined one or more maintenance actions indicating replacement of at least one brake pad.
[0044] In some embodiments, the method further includes identifying a preset vehicle parameter of the vehicle alternator and triggering one of the determined one or more maintenance actions based on the preset vehicle parameter, the one maintenance action indicating a remaining life cycle of the battery. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] A more complete understanding of the embodiments described herein and their attendant advantages and features will be more readily appreciated by reference to the following detailed description considered in conjunction with the accompanying drawings, in which: Figure 1 is a simplified diagram of an example system according to the principles disclosed herein; Figure 2 An example battery constructed according to the principles of the present disclosure is shown; Figure 3 is a block diagram of some entities in a system according to some embodiments of the present disclosure; Figure 4 is a block diagram of an example server according to some embodiments of the present disclosure; Figure 5shows example screens according to some embodiments of the present disclosure; Figure 6 shows example navigation options according to some embodiments of the present disclosure; Figure 7A A first portion of an example navigation profile according to some embodiments of the present disclosure is shown; Figure 7B showing a second portion of an example navigation profile according to some embodiments of the present disclosure; Figure 8 shows example dashboard pages and features according to some embodiments of the present disclosure; Figure 9 shows an example battery settings page according to some embodiments of the present disclosure; Figure 10 shows an example battery screen according to some embodiments of the present disclosure; Figure 11 shows an example maintenance screen according to some embodiments of the present disclosure; Figure 12A shows an example first portion of a screen navigation structure according to some embodiments of the present disclosure; Figure 12B shows an example second portion of a screen navigation structure according to some embodiments of the present disclosure; Figure 13A shows another example of a first portion of screen navigation associated with a vehicle according to some embodiments of the present disclosure; and Figure 13B shows another example of a second portion of screen navigation associated with a vehicle according to some embodiments of the present disclosure; and Figure 13C shows another example of a third portion of screen navigation associated with a vehicle according to some embodiments of the present disclosure; and Figure 14 a flowchart illustrating an example process in a device according to some embodiments of the present disclosure; and Figure 15 Another example flow diagram illustrating an example process in a device according to some embodiments of the present disclosure. DETAILED DESCRIPTION
[0046] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in apparatus components and process steps and parameter combinations related to methods, apparatus, and systems for associating various parameters with various actions, including maintenance actions. Accordingly, system and method components are represented by conventional symbols in the drawings where appropriate, and only those specific details relevant to an understanding of the embodiments of the present disclosure are shown so as not to obscure the present disclosure with details that would be readily apparent to one of ordinary skill in the art having the benefit of the description herein.
[0047] In some embodiments, the term "smart battery" may be used and may refer to a battery having, for example, lead, lithium, or sodium chemistries that are enabled by electronics physically attached to the battery to monitor battery functional parameters, such as, but not limited to, state of charge, state of health, and / or trends thereof, or to transmit battery conditions from within or outside the battery environment. The electronics may generally be referred to as connected electronics and may include a battery management system or any other electronic components. Further, the electronics may utilize a wired or wireless transmission device or communication interface configured to transmit data and / or information (such as applicable battery information and / or derivatives of the battery information).
[0048] As used herein, relational terms such as "first" and "second", "top" and "bottom" may be used only to distinguish one entity or element from another entity or element, and do not necessarily require or imply any physical or logical relationship or order between these entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a / an" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that when the terms "comprise, consist of, include, have" are used herein, they specify the presence of the described features, wholes, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, parts and / or groups thereof.
[0049] In some embodiments, the term "smart battery" may be used and may refer to a battery having, for example, lead, lithium, or sodium chemistries that are enabled by electronics physically attached to the battery to monitor battery functional parameters, such as state of charge, state of health, and / or trends thereof, or to communicate battery conditions from within or outside the battery environment. The electronics may generally be referred to as connected electronics and may include a battery management system or any other electronic components. Further, the electronics may utilize a wired or wireless transmission device or communication interface configured to transmit data and / or information (such as applicable battery information and / or derivatives of the battery information).
[0050] The term "parameter" refers to any parameter associated with any system or component of a vehicle that can be set. As an example of a parameter in a vehicle, a parameter may be associated with the battery (and / or its components), battery performance, battery management, battery operation, battery maintenance, battery health, or battery replacement. Parameters associated with the battery may also be associated with other systems and / or components in the vehicle, including but not limited to vehicle diagnostic parameters, accessory system parameters, parameter changes, etc. Further, a parameter may be associated with multiple parameter values within a certain range within which a component and / or system functions and / or can be intended or expected to function. A parameter may refer to a quantity that defines a theoretical model. A maintenance parameter may refer to any parameter and / or more than one parameter from vehicle parameters, battery parameters, and / or accessory parameters that is set to indicate that a certain maintenance action may be required and / or expected for the vehicle in the near future.
[0051] For example, vehicle parameters can be any parameters associated with any system and / or component of the vehicle. For example, vehicle parameters can include any settings related to the powertrain, engine, ignition, electrical system, transmission / drivetrain, alternator, radiator, axle, steering and suspension system, catalytic converter, muffler / exhaust system, tailpipe, fuel system and tank, frame, and body.
[0052] For example, the battery parameter may be any parameter associated with any system and / or component of the battery. For example, the battery parameter may include electrical parameters (such as waveform, power, voltage, voltage, current, state of charge (SoC), state of health (SoH), open circuit voltage (OCV), voltage drop, time, resistance value) and / or any other parameters (such as temperature, pressure) and / or frequency parameters (such as the frequency of pulses, the frequency of operating mode turning on and / or off and / or activating and / or deactivating), etc.
[0053] For example, accessory parameters may include any parameters associated with any system and / or component of an accessory. Accessory parameters may include, but are not limited to, parameter settings related to, but not limited to, fuel and air metering, the vehicle's fuel mileage and emissions systems, the air-to-fuel ratio / ratio within the vehicle, oxygen sensed within the vehicle, fuel injectors (including fuel injector circuits), any engine failure including components such as spark plugs, ignition components, auxiliary emission controls (including evaporative emission control systems), vehicle speed control and idle control systems (including vehicle speed sensors), any computer output circuit issues and any malfunctioning computer system issues, the transmission system, and any associated components. Furthermore, accessory parameters may include, but are not limited to, settings related to, but not limited to, the front, side, rear, and any additional passenger air bag systems, seatbelt tensioning systems, body sensors around the vehicle, power door locks, ignition system, brake lights, keyless entry, driver and passenger seats, air conditioning system, power system (including windshield wipers and washer), circuit and power supply issues / problems, auxiliary heater and interior fan, air bag sensors, and transmission temperature. Furthermore, accessory parameters may include settings related to the braking system, steering system, suspension system, traction control system, vehicle speed sensor, brake pedal position sensor, pressure system, steering wheel position, anti-lock braking system (ABS) functionality, drive torque transfer from the engine to the wheels, vehicle mechanical systems (including ABS sensors, wheel sensors, parking brake, vehicle accelerometer circuits, and dynamic stability control systems), and monitoring of the air suspension system. Finally, accessory parameters may include settings related to low and / or high circuit voltages within the controller area network or vehicle area network, anti-lock braking system, transmission control module, navigation control system, network software and network data, control modules related to the braking system, shifting and steering effort, engine temperature control, ignition system, power window functionality, audio and infotainment systems (including audio speakers, Bluetooth system, and navigation system), and control modules and power distribution systems (including circuit issues, power control modules, ignition inputs, and switch systems). These are not meant to be limiting examples, but rather illustrative of accessory parameters.
[0054] When referring to any parameter associated with any system and / or component of a vehicle, a frequency parameter may refer to a setting associated with a time parameter (e.g., when a pulse is on or off, when an operating mode is turned on / off, and / or activated / deactivated). Furthermore, a parameter threshold may refer to a setting associated with a threshold value associated with a parameter. Furthermore, it will be understood that these parameters may be applied to other systems and / or components in a vehicle, including belts / hoses, brakes, filters, oil, emissions, engine cooling, exhaust, filters and oil, fuel systems, lighting and wipers, steering and suspension systems, and transmissions.
[0055] "Functionality" may refer to the way a system or component of a vehicle actually operates at a specific time or over a specific time period. Functionality may refer to any function related to the vehicle, battery, and / or accessories that can be measured and / or quantified. An example of a function in a vehicle may involve a battery (and / or its components), and the function may measure an electrical function of the battery, including waveform, power, voltage, voltage, current, SoC, SoH, OCV, resistance value, and / or any other function of the vehicle, such as temperature, pressure, and / or frequency (e.g., frequency of pulses, frequency of operating modes turning on and / or off and / or activating and / or deactivating), etc. The function may also involve any other component and / or system of the vehicle.
[0056] For example, a vehicle function can be any function associated with any system and / or component of a vehicle. For example, a vehicle function can include any function that can be measured, including the powertrain, engine, ignition, electrical system, transmission / drivetrain, alternator, radiator, axle, steering and suspension system, catalytic converter, muffler / exhaust system, tailpipe, fuel system and tank, frame, and body.
[0057] For example, a battery function can be any function associated with any system and / or component of a battery. As non-limiting examples, a battery function can include any function that can be measured, including electrical functions (such as waveform, power, voltage, voltage, current, SoC, SoH, OCV, voltage drop, time, resistance value) and / or any other function (such as temperature, pressure) and / or frequency function (e.g., frequency of pulses, frequency of operating modes turned on and / or off and / or activated and / or deactivated), etc.
[0058] For example, an accessory function can be any function associated with any system and / or component of an accessory. As non-limiting examples, an accessory function can include any function that can be measured, including but not limited to fuel and air metering, monitoring the vehicle's fuel mileage and emissions systems, monitoring the air-to-fuel ratio / ratio in the vehicle, sensing oxygen within the vehicle, monitoring fuel injectors (including fuel injector circuits), monitoring any engine misfires including components such as spark plugs, ignition components, monitoring auxiliary emission controls (including evaporative emission control systems), vehicle speed control and idle control systems (including vehicle speed sensors), monitoring any computer output circuit issues and any malfunctioning computer system issues, and monitoring the transmission system and any associated components. Additionally, accessory functions may include, but are not limited to, monitoring the front, side, rear, and any additional passenger air bag systems, monitoring the seat belt tensioning system, monitoring body sensors around the vehicle, monitoring the power door locks, monitoring the ignition system, monitoring the brake lights, monitoring the keyless entry function, monitoring the driver and passenger seats, monitoring the air conditioning system, monitoring the power system (including windshield wipers and washer), monitoring for circuit and power supply problems / issues, monitoring the auxiliary heater and interior fan, monitoring the air bag sensors, and transmission temperature. Furthermore, accessory functions may include monitoring the braking system, monitoring the steering system, monitoring the suspension system, monitoring the traction control system, monitoring the vehicle speed sensor, monitoring the brake pedal position sensor, monitoring the pressure system, monitoring the steering wheel position, monitoring the anti-lock braking system (ABS) function, monitoring the drive torque transfer from the engine to the wheels, monitoring the vehicle's mechanical systems (including the ABS sensors, wheel sensors, parking brake, vehicle accelerometer circuits, and dynamic stability control systems), and monitoring the air suspension system. Finally, accessory functions may include monitoring for low and / or high circuit voltages in a controller area network or vehicle area network, monitoring the anti-lock brake system, monitoring the transmission control module, monitoring the navigation control system, monitoring network software and network data, monitoring control modules related to the brake system, shifting, and steering effort, monitoring engine temperature control, monitoring the ignition system, monitoring power door and window functionality, monitoring the audio and infotainment system (including audio speakers, Bluetooth system, and navigation system), and monitoring control modules and power distribution systems (including circuit problems, power control modules, ignition inputs, and switching systems). These are not meant to be limiting examples, but rather illustrate accessory functions.
[0059] "Health" may refer to any condition associated with at least one system and / or component of a vehicle. As an example, a battery-related health condition and / or battery health condition may refer to any condition associated with a battery (and / or devices, systems, or components associated with the battery) (e.g., the health of the battery and / or the vehicle / vehicle system). Battery health conditions may include battery failure (e.g., catastrophic battery / system failure, latent failure, conditions associated with a latent failure, triggered system failure, battery pack failure, inability to start / operate the vehicle, etc.), degradation conditions (e.g., failure to meet user / functional / specification requirements, such as when a parameter is below / above a predetermined threshold), internal short circuit, internal resistance below a predetermined threshold (e.g., indicating a short circuit condition), etc. Furthermore, health conditions may also refer to any other system or component of the vehicle. A vehicle may have various health conditions associated with different components and / or systems of the vehicle. Further, health conditions may include conditions associated with the battery's SoH.
[0060] SoH can refer to a parameter that indicates the degree of degradation and / or remaining capacity of a battery. In some embodiments, SoH can indicate the difference between the health of a new battery and the health of an old battery. In some other embodiments, SoH can be defined as the ratio of the maximum battery charge to the rated capacity and can be expressed as a percentage.
[0061] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. It should be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0062] In the embodiments described herein, connection terms such as "in communication with..." may be used to indicate electrical communication or data communication, which may be achieved through, for example, physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate, and that modifications and changes to the implementation of electrical and data communication are possible.
[0063] In some embodiments, general descriptive elements of the form "one of A and B" correspond to A or B. In some embodiments, at least one of A and B corresponds to A, B, or AB, or one or more of A and B. In some embodiments, at least one of A, B, and C corresponds to one or more of A, B, and C, and / or A, B, C, or a combination thereof.
[0064] Referring to the drawings, wherein like elements are represented by like reference numerals, Figure 1 A simplified diagram of a system 10 according to an embodiment is shown, the system including one or more of a vehicle 12, a battery 14, an accessory 20, a device 24, and a server 28. The vehicle 12 can be any type of vehicle, such as a vehicle that can be used to transport people, animals, goods, products, etc. In non-limiting examples, the vehicle 12 can include an automobile, a motorcycle, a scooter, a truck, a golf cart, a bus, a motorized wheelchair, a light utility vehicle, a rail vehicle (such as a train and a tram), a watercraft (including ships, boats, and underwater vehicles), an aircraft (including airplanes and helicopters), a spacecraft, an autonomous vehicle, or any other type of vehicle.
[0065] Vehicle 12 includes at least one battery 14 for powering at least one function of vehicle 12. In some embodiments, battery 14 may be a lead-acid battery comprising one or more energy storage modules / cells. Although a lead-acid battery has been described, the teachings described herein are equally applicable to other battery types. Battery 14 may include, for example, one or more batteries electrically connected (e.g., in parallel, in series, etc.) as part of a battery pack, such as a first battery 14a, a second battery 14b, a third battery 14c, a fourth battery 14d, and so on. Battery 14 may also include a battery management system 16 configured to perform one or more battery management functions / battery functions described herein. BMS 16 may include a BMS management unit 18, which may be configured to perform any of the steps, tasks, processes, methods, and / or features described herein, such as BMS 16 functions. In some embodiments, BMS 16 may measure / determine certain battery parameters and functions and transmit / receive data (and / or signals, such as control signals) to / from another system / device. The BMS 16 is configured to include a BMS management unit 18 , which may be configured to perform one or more functions as described herein, such as battery management functions.
[0066] Accessory 20 may include accessory unit 22, which may be configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described herein, e.g., functions of accessory 20. For example, accessory unit 22 may be configured to perform one or more functions as described herein, such as determining, receiving, and / or transmitting one or more parameters, determining the functions of one or more components / systems of the vehicle, or any other information associated with vehicle 12, battery 14, server 28, any accessory 20, and / or another device 24. For example, where accessory 20 includes an on-board diagnostic (OBD) device, accessory unit 22 may be configured to determine the functions of one or more accessories 20, e.g., using the OBD device. The OBD device may be configured to monitor and / or control vehicle 12, battery 14, BMS 16, etc. Further, the OBD device may be capable of providing information regarding a variety of accessory functions and accessory parameters associated with various systems and components of vehicle 12. Accessory 20 can be physically and / or electrically connected to one or more components of system 10, including, for example, vehicle 12, battery 14, BMS 16, device 24, server 28, and provide one or more parameters and / or functions, including accessory parameters and functions monitored or controlled by accessory 20.
[0067] Device 24 may include a device management unit 26 that may be configured to perform any of one or more functions, tasks, processes, methods, and / or features described herein, such as device functions. For example, device management unit 26 may be configured to determine one or more functions, parameters, and / or common associations between certain functions and / or parameters. For example, vehicle maintenance and / or vehicle diagnostics may be associated with the battery life cycle and / or used to determine one or more actions associated with the battery life cycle and / or information associated with the vehicle 12, battery 14, and / or any accessories 20. Device 24 may also include software, such as a mobile application, configured to present one or more user interfaces that may facilitate performing one or more actions described herein. Further, device 24 may be a computing device (e.g., a personal computer, laptop, etc.) or a mobile device (e.g., a cell phone or tablet), either of which may be configured to perform one or more functions associated with device 24 as described herein.
[0068] The server 28 may include a server management unit 30 that may be configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, e.g., the functionality of the server 28. For example, the server management unit 30 may be configured to perform one or more functions as described herein, such as determining, receiving, and / or transmitting one or more parameters, conditions, functions, or any other information and / or data associated with the vehicle 12, battery 14, and / or any accessories 20.
[0069] It is contemplated that one or more entities of system 10 may communicate with one another via one or more of wireless communication, power communication, wired communication, and the like. For example, vehicle 12, battery 14, accessory 20, device 24, and server 28 may communicate with one another directly or indirectly using wireless communication, power communication, wired communication, and the like and / or any communication protocol. Further, while battery 14 is shown as part of vehicle 12, it may be a standalone battery that can be removably coupled to any component of system 10 (e.g., vehicle 12, etc.).
[0070] Figure 2 An example battery 14 constructed according to the principles of the present disclosure is shown. The battery 14 includes a housing 31 in which one or more battery components, such as battery cells 32, may be positioned. These components may be electrically interconnected, such as via a conductive bus bar system (not shown), which electrically interconnects the components in series, parallel, or a combination of series and parallel connections, depending on the expected voltage and current requirements. Although Figure 2 Six battery cells 32 are shown, but it should be understood that fewer or more than six battery cells may be used in the battery 14 depending on design requirements.
[0071] BMS 16 may be included as part of battery 14. BMS 16 may include a monitoring connector 34 that allows for removable external connection to any other components of system 10 (e.g., to the vehicle's data bus, to some other communication device, to accessory 20, etc.) and / or internal connection, such as internal connection to any components of battery 14 and / or BMS 16 and / or accessory 20. Connector 34 may communicate directly or indirectly with BMS 16, accessory 20, server 28, and / or device 24. In some embodiments, connector 34 may be configured to removably couple and / or connect (electrically or physically) to another connector. In some embodiments, monitoring connector 34 may be integrated with housing 31, such as within cover 36 of housing 31. BMS 16 may also be capable of wirelessly communicating with other devices to transmit / exchange information and / or data. The battery 14 also includes terminals, such as a positive terminal 38a and a negative terminal 38b (collectively, terminals 38), to provide contact points for electrical connection of the battery 14 (e.g., to the accessory 20 to power the accessory 20, to the vehicle 12 to provide power to the vehicle, and / or to the BMS 16 to power the BMS 16). The terminals 38 can be arranged to protrude through the housing 31, such as through the cover 36. The terminals 38 can be electrically connected to a bus bar inside the housing 31 and / or directly connected to the battery cells 32 (the bus bar and direct connection are not shown).
[0072] Furthermore, the battery 14 can be configured to provide power capacity to a variety of physical sizes and operate within a variety of preset parameters and parameter ranges. It should also be noted that embodiments of the battery 14 can be scaled to provide various capacities. For example, in some embodiments, the power capacity (e.g., battery power) of the battery 14 can range from 25 Ah to 75 Ah. However, it should be noted that this range is merely exemplary, and it is contemplated that embodiments of the battery 14 can also be configured to provide a capacity less than 25 Ah or a capacity greater than 75 Ah. Power capacity scaling can be achieved, for example, by using battery cells 32 with higher or lower power capacities within the housing 31 and / or by using fewer or more battery cells 32 within the housing 31. In some embodiments, the battery 14 can be incorporated as part of a vehicle requiring battery power. Other electrical parameters of the battery 14 can be adjusted / adapted by using battery cells 32 that can cumulatively possess desired operating characteristics, such as current, voltage, charge, charge capacity / rate, discharge rate, etc. Thermal properties can be managed based on the characteristics of the battery cells 32, using heat sinks and / or heat dissipation plates, etc., inside or outside the housing 31. Further, the BMS 16 and / or the accessory 20 can be connected to at least one of the battery cells to determine / measure at least one parameter of the battery 14 and / or the battery cell 32.
[0073] Now refer to Figure 3 and Figure 4 Example implementations of the BMS 16, accessories 20, devices 24, and server 28 discussed in the preceding paragraphs are described according to an embodiment. The BMS 16 may have hardware 40 that may include a communication interface 42 configured to communicate with one or more entities in or outside the system 10 via wired and / or wireless communications. The communication may be protocol-based communication.
[0074] The hardware 40 as part of the BMS 16 includes processing circuitry 46. The processing circuitry 46 may include a processor 48 and memory 50. In particular, in addition to or in lieu of a processor 48 (e.g., a central processing unit) and memory, the processing circuitry 46 may include an integrated circuit system for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit system) adapted to execute instructions. The processor 48 may be configured to access (e.g., write to and / or read from) the memory 50, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).
[0075] Thus, the BMS 16 may further include software 52 stored, for example, in the memory 50, or in an external memory (e.g., a database, etc.) accessible by the BMS 16. The software 52 may be executed by the processing circuitry 46. Further, the software 52 may include a mobile application configured to present one or more user interfaces that may facilitate performing one or more actions described in the present disclosure.
[0076] Processing circuitry 46 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by BMS 16. Processor 48 corresponds to one or more processors 48 configured to perform the BMS 16 functions described herein. BMS 16 includes memory 50 configured to store data, programming software code, and / or other information described herein. In some embodiments, software 52 may include instructions that, when executed by processor 48 and / or processing circuitry 46, cause processor 48 and / or processing circuitry 46 to perform the processes described herein with respect to BMS 16. For example, processing circuitry 46 of BMS 16 may include a BMS management unit 18 configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described herein, such as BMS functions and / or battery functions. This may include determining one or more parameters associated with battery 14 and / or measuring / evaluating one or more functions associated with battery 14. Although the BMS management unit 18 is shown as part of the BMS 16 , the BMS management unit 18 and related functions and parameters described herein may also be implemented in a device separate from the BMS 16 , such as in the battery 14 or another device.
[0077] Accessory 20 (e.g., an OBD device) may have hardware 54 that may include a communication interface 56 configured to communicate with one or more entities within system 10 (and / or external to system 10) via wired and / or wireless communications. This communication may be protocol-based. For example, accessory 20 may be configured to electrically connect to vehicle 12 and / or battery 14 and / or transmit / receive at least one parameter (and / or parameter data) and / or transmit / receive at least one function. Similarly, accessory 20 may be configured to wirelessly connect to any component of system 10 (such as device 24) and / or transmit / receive at least one parameter (and / or parameter data) and / or transmit / receive at least one function.
[0078] Hardware 54 associated with accessory 20 includes processing circuitry 58. Processing circuitry 58 may include a processor 60 and memory 62. In particular, processing circuitry 58 may include, in addition to or in lieu of a processor (e.g., a central processing unit) and memory, an integrated circuit system for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit system) adapted to execute instructions. Processor 60 may be configured to access (e.g., write to and / or read from) memory 62, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).
[0079] Accessory 20 can further include software 66 stored, for example, in memory 62 or in an external memory (eg, a database, etc.) accessible by accessory 20. Software 66 can be executed by processing circuitry 58.
[0080] Processing circuitry 58 can be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by accessory 20. Processor 60 corresponds to one or more processors 60 configured to perform the accessory 20 functions described herein. Accessory 20 includes memory 62 configured to store data, programming software code, and / or other information described herein. In some embodiments, software 66 can include instructions that, when executed by processor 60 and / or processing circuitry 58, cause processor 60 and / or processing circuitry 58 to perform the processes described herein with respect to accessory 20. For example, processing circuitry 58 of accessory 20 can include accessory unit 22, which can be configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described herein, for example, the accessory 20 functions. For example, accessory unit 22 can be configured to perform one or more functions as described herein, such as determining, receiving, and / or transmitting one or more parameters, one or more functions, or any other information / data associated with vehicle 12, battery 14, and / or any accessory 20. In some embodiments, accessory 20 and / or any components thereof may be included in and / or powered by BMS 16 (and / or battery 14 and / or vehicle 12 ).
[0081] Furthermore, the device 24 includes hardware 70, and the hardware 70 may include a communication interface 72 for performing wired and / or wireless communications with the BMS 16 and / or the accessory 20 and / or any other device or component of the system 10. For example, the communication interface 72 of the device 24 may communicate with the communication interface 56 of the accessory 20 via a communication link 90. Additionally, the communication interface 72 of the device 24 may communicate with the communication interface 42 of the BMS 16 via a communication link 92. Similarly, the communication interface 42 may communicate with the communication interface 56 via a communication link 94. At least one of the communication links 90, 92, 94 may be a wired / wireless connection (e.g., WiFi, Bluetooth, etc.).
[0082] In the illustrated embodiment, the hardware 70 of the device 24 includes processing circuitry 74. The processing circuitry 74 may include a processor 76 and a memory 78. In particular, in addition to or in lieu of a processor (e.g., a central processing unit) and memory, the processing circuitry 74 may include an integrated circuit system for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit system) adapted to execute instructions. The processor 76 may be configured to access (e.g., write to and / or read from) the memory 78, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).
[0083] Therefore, device 24 further includes software 80, which is stored internally, for example, in memory 78, or in external memory (e.g., a database, etc.) accessible to device 24 via an external connection. Software 80 may be executed by processing circuitry 74. Processing circuitry 74 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by device 24. Processor 76 corresponds to one or more processors 76 configured to perform the functions of device 24 described herein. Memory 78 is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 80 may include instructions that, when executed by processor 76 and / or processing circuitry 74, cause processor 76 and / or processing circuitry 74 to perform the processes described herein with respect to device 24. For example, processing circuitry 74 of device 24 may include device management unit 26, which may be configured to perform one or more functions, tasks, processes, methods, and / or features described herein, such as the functions of device 24. For example, the device management unit 26 can be configured to determine one or more parameters, one or more functions, and / or associate vehicle maintenance and vehicle diagnostics with the battery life cycle, and / or determine one or more actions associated with the battery life cycle or any other information associated with the vehicle 12, battery 14 and / or accessory 20.
[0084] Figure 4 An exemplary server 28 is shown, which may communicate with any component of the system 10, including but not limited to, Figure 3More specifically, the server 28 includes hardware 100, and the hardware 100 may include a communication interface 102 for performing wired and / or wireless communication with any one of the components of the system 10, such as the communication interface 42 of the BMS 16, the communication interface 56 of the accessory 20, and the communication interface 72 of the device 24, and / or the communication interface of any other device.
[0085] exist Figure 4 In the illustrated embodiment, the hardware 100 of the server 28 includes processing circuitry 104. Processing circuitry 104 may include a processor 106 and memory 108. In particular, in addition to or in lieu of a processor (e.g., a central processing unit) and memory, processing circuitry 104 may include an integrated circuit system for processing and / or control, such as, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit system) adapted to execute instructions. Processor 106 may be configured to access (e.g., write to and / or read from) memory 108, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).
[0086] Therefore, server 28 further includes software 110, which is stored, for example, in internal memory 108 or in external memory (e.g., a database, etc.) accessible by server 28 via an external connection. Software 110 may be executed by processing circuitry 104. Processing circuitry 104 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by server 28. Processor 106 corresponds to one or more processors 106 for performing the functions of server 28 described herein. Memory 108 is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 110 may include instructions that, when executed by processor 106 and / or processing circuitry 104, cause processor 106 and / or processing circuitry 104 to perform the processes described herein with respect to server 28. For example, the processing circuitry 104 of the server 28 may include a server management unit 30 that may be configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, e.g., the functionality of the server 28. For example, one or more servers 28 function as described herein. For example, the server management unit 30 may be configured to perform one or more functions as described herein, such as determining, receiving, and / or transmitting one or more parameters and / or one or more functions or any other information associated with the vehicle 12, the battery 14, and / or any accessories 20.
[0087] Although Figure 1 、 Figure 3 and Figure 4 One or more "units," such as the BMS management unit 18, the accessory unit 22, the device management unit 26, and the server management unit 30, are shown as being located within respective processors 48, 60, 76, 106, but it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, these units may be implemented in hardware, software, or a combination of hardware and software within the processing circuitry.
[0088] The general process flow of the arrangement of the present disclosure has been described, and examples of hardware and software arrangements for implementing the processes and functions of the present disclosure have been provided. The following sections provide details and examples of the association of parameters, functions and other information and / or data with various maintenance actions.
[0089] Figure 5 and Figure 61 is an exemplary display 112 associated with the software 80, which illustrates a fleet / list layout that provides information about a number of vehicles that can be viewed on the display 112 where images and data are shown. In some embodiments, the display 112 may refer to one screen and / or display or more than one screen and / or display. Additionally, the software 80 may include a mobile application configured to present one or more displays 112. Embodiments are not limited in this regard, and the functionality described herein may also be performed by any of the software 52, 66, 80, and 110. The display 112 may be any type of display 112 for visually presenting information, and in this embodiment is a cellular / smartphone screen. It will be understood that the display 112 may also display information related to one vehicle or more than one vehicle, including but not limited to displaying information related to a one-vehicle, a two-vehicle layout, a four-vehicle grid / layout, and a fleet / list layout. Display 112 may include a maintenance action indicator 114. Once system 10 synthesizes parameters, functions, and / or other information and / or data, the maintenance action indicator, when activated and turned on, will include information regarding any proposed maintenance actions that have occurred for a particular vehicle 12. Furthermore, maintenance action indicator 114 may include a number associated with how many maintenance actions are recommended for a particular vehicle 12. For example, maintenance actions may include brake pad replacement, battery replacement, and alternator inspection. The information readable on display 112 may be customizable, or there may be preset settings for the content displayed on display 112. Furthermore, display 112 may include at least one icon 116, and icons 116 may be customized with respect to which icons 116 are displayed on display 112 and which icons 116 are removed from the display. For example, a user may select which icons 116 are visible, and by accessing and turning on icons 116, detailed information about vehicle 12 may be provided. As one example, the icon 116 may have an image of a battery, and opening the battery icon 116 may provide details and information about the battery 14 in the vehicle 12 .
[0090] Figure 7A and Figure 7B An exemplary navigation profile that may be provided by software 80 and / or used with system 10 is shown. Figure 7A and Figure 7B An exemplary navigation profile is shown in FIG, but it will be understood that the navigation profile may be found in one profile. Figure 7A, the navigation profile includes a search feature 118 in which the user can search for a specific vehicle 12 and other specific information related to the vehicle 12. The navigation profile can include various options 120 related to each vehicle 12, and as shown, one exemplary option 120 can include a profile for the user of the specific vehicle 12. The profile can include information such as account information with a username and password and contact information with full name, email address, phone number, zip code, date of birth, country, etc. and other related information about the profile. The profile can also have two-factor authentication and indicate when the profile was last updated and the date the profile was created. Figure 7B As shown, the profile may also include an option 120, such as for "Maintain My Garage." As shown in this exemplary embodiment, the Maintain My Garage option 120 may include information about the garage name of the vehicle. By clicking on each vehicle listed in the "Maintain My Garage" option 120, the user can enter information about the vehicle, including the make, model, year, VIN number, license plate number, mileage, and other relevant information. The user may also choose to make certain information private, so that when the user views the Maintain My Garage option 120, the information is not displayed on the screen. Within the Maintain My Garage option 120, the user may further add and remove vehicles from the display, allowing the user to easily filter the profile. As shown in FIG. 7B , the user may enable the edit feature on the Maintain My Garage screen and may then edit / change information about a specific vehicle. Furthermore, a vehicle 12 may be added, and an add vehicle screen may be displayed to include additional information about another vehicle 12 to be included in "Maintain My Garage." The profile may also contain additional settings including, but not limited to, battery settings, OBD / maintenance settings, summary report information, and contact us information by which the user may contact the entity / company.
[0091] Figure 8Another exemplary embodiment of a display 112 with an OBD-based dashboard page is shown. When OBD is installed, for example, with accessory 20, system 10 can collect information about vehicle 12 from battery 14, accessory 20, server 28, and / or device 24. Using this information and data, display 112 can include a variety of information related to vehicle 12. For example, display 112 can include information about battery 14, maintenance actions, including maintenance action instructions 114, recall notifications, vehicle history information, parameter and function information, and diagnostic scan information. Vehicle history (which can be additional maintenance parameters such as history parameters) can allow a user to view data and information collected about a single vehicle. This data and information can include driving time, braking data, speed, driving style, crank profile history, acceleration data, mileage, accidents, recalls, warranty, repair records, wiper usage time, light activation time, number of previous owners of the vehicle, vehicle service and / or maintenance times, and other historical vehicle information. The information and data collected by system 10 can be used to determine whether a maintenance action is warranted and to display a maintenance action indication 114 on display 112. For example, at least one maintenance parameter can be combined with at least one other maintenance parameter and at least one function to determine whether any maintenance action is warranted. If a maintenance action is created, display 112 can include a maintenance action indication 114, which can include information regarding the maintenance parameter(s) and / or function(s), and / or any additional information and data used to create the specific maintenance action. Furthermore, maintenance action indication 114 can include the type of maintenance and / or further diagnostic work recommended for vehicle 12. The types of maintenance and / or diagnostic work that may be recommended can include any system and / or component of vehicle 12. If a user selects a battery, including the date the battery 14 was installed in vehicle 12, the brand, part number, and specific technical information related to the battery 14, detailed information about the battery can be displayed. Furthermore, the user can select a "Scan Diagnostics" option, which provides access to information from a diagnostic scan of the vehicle 12.
[0092] Figure 9An example battery settings page is shown. On the display 112, one of the icons 116 may include an image of a battery 14. Information and data about the battery 14 used in the vehicle 12 can be entered into the display 112. If the battery 14 is a smart battery, the information can also be automatically populated into the system 10 and does not require manual entry. The user can select the smart battery and then connect / add the battery to the system 10. Alternatively, if the battery 14 is a standard battery without smart technology capabilities, information about the battery 14 can be manually entered using the display 112 or another component of the system 10. Some of the information that can be included may include information about the brand, technology used as part of or with the battery 14, voltage, part number, installation date, and other relevant information about the battery 14. Furthermore, custom battery 14 information can also be included in the display 112. The display 112 may include information about when to replace the battery 14 based on certain parameters and / or functions measured by the system 10. If there is a maintenance action that recommends replacing the battery, the system 10 may include information that allows the user to shop for batteries and find and compare batteries that can be used in the vehicle 12, along with battery prices, battery availability, batteries that are best suited for the environment in which the vehicle 12 will be located, information about how a particular battery may affect the environment, and other relevant information. The user may also be able to actually purchase the batteries that are seen on the display 112 that are compatible with the vehicle 12.
[0093] Figure 10 Another example battery screen is shown with an OBD and / or smart battery installed. Figure 10In the exemplary embodiment shown, with an OBD or smart battery connected to system 10, information about battery 14 is available on display 112. For example, battery information may include information about the brand, part number, technology used in the battery, the charge level on the battery, and other additional information available to the user regarding battery 14. If the user clicks on a "Learn More" feature or "Additional Information" or similar items, the user may access significantly more information and data regarding a particular battery 14. Furthermore, depending on specific parameters detected using system 10, maintenance actions may include suggesting that it is time to replace the battery. Additionally or alternatively, maintenance actions may indicate battery health as "Good," "Fair," "Bad," "Check," "Replace," or a color-coded system where green represents good, yellow represents a warning, and red indicates it is time to replace the battery. Battery health indicator screen options may include a gauge representation on the battery icon on display 112 (e.g., a gauge representation on the lower half of the battery icon, a gauge representation on the upper half of the battery icon, respectively). The graphical display includes various colors to make it easier to use and identify when certain systems or components in vehicle 12 require attention, maintenance, and / or repair. This determination that it may be time to replace the battery may be based on one particular parameter and function or more than one parameter and function.If the maintenance action suggests that the battery 14 should be replaced, the user can also be connected to information to help find a replacement battery.
[0094] Figure 11An exemplary maintenance screen associated with certain parameters, enabled when an OBD and / or smart battery is installed, is shown. One or more parameters may indicate that the associated vehicle or battery item is due for replacement or maintenance based on functionality, conductivity, and / or parameters. For example, brake pads may be shown as indicating a concern, i.e., requiring brake pad maintenance based on a predetermined timeframe, such as thirty-four months having passed since the previous brake pad maintenance event, with a recommendation for scheduled maintenance on or before thirty-six months. In some embodiments, brake pads may be shown as recommended for replacement based on another parameter associated with the vehicle 12 and / or battery 14. Another example includes identifying a parameter other than a parameter associated with the brakes (i.e., exceeding a battery replacement window) as requiring a service provider visit. Device 24 may be configured to suggest a bundled service, i.e., battery replacement and brake pad replacement, based on one or more promotions, battery lifecycle parameters, brake parameters, etc., as well as certain functionality associated with the battery and / or brake pads. In other words, the device 24 can be configured to determine scheduled maintenance actions based on the values of other parameters and / or functions to maintain desired battery life cycle goals (e.g., warranty, continued product quality, goals associated with providing battery as a service, etc.) or vehicle condition goals. The maintenance action instructions 114 can include information about the battery, belts / hoses, brakes, filters, oil, lights, spark plugs, suspension system, tires, water pump, and wiper blades. This is not meant to be an exhaustive list, as information about any system and / or component that is part of the vehicle 12 can also be included. Moreover, the information can be customized, as some vehicles may have specific systems and / or components that are not available on other vehicles.
[0095] Figure 12A and Figure 12B An exemplary screen navigation structure is shown. Figure 12A shows a first portion of an exemplary screen navigation structure, and Figure 12B Shown Figure 12A The second part of the exemplary screen navigation structure. It will be understood that Figure 12A and Figure 12B can be combined to form a single exemplary screen navigation structure, but by FIG. 12A to FIG. 12B In this non-limiting example, Figure 12AAs shown, the Home screen provides on-screen navigation controls to navigate to the top navigation screen and the Vehicle screen. Each screen may further provide navigation controls to other screens, such as screens for adding and / or removing vehicles and providing menus / settings. An exemplary on-screen navigation structure may include a profile, which may include information about me, including first name, last name, username, password, email address, alternate email address, mobile number, zip code, date of birth, and preferred automotive retailer. Figure 12A and Figure 12B , such as Profile, Battery Settings, Maintain My Garage, OBD / Maintenance Settings, Settings, Summary Reports, Contacts screens, etc. Additional navigation may be configured to access other screens associated with each of these components. As an example, in the Battery Settings screen, a user may add / edit battery information, select a vehicle, and then view information related to the original battery and / or replacement battery. Information about the replacement battery may include the brand, place of purchase, warranty information, technology, pack size, quantity, installation date, sync / sync or pairing of the battery to the device, and optional additional information. This optional information may include, but is not limited to, custom information about the battery, including reminders and other battery information that the user may want to enter into the system 10. In the example shown in FIG. Figure 12A In another setting option shown, there may be a "Maintain My Garage" option, and the user can add / edit vehicle information. For example, the vehicle information may include VIN number, make, model, sub-model, year, mileage (which can be entered manually or read from OBD), vehicle nickname and vehicle icon and other relevant information. This information can also be customized. Figure 12B As shown, the menu / settings may also include OBD / maintenance settings, settings, summary reports, and contact us. In this exemplary embodiment, these settings may include notification settings (including push notifications and email notifications), appearance, language, privacy settings, and help.
[0096] 13A to 13C Another exemplary embodiment of a navigation screen associated with a vehicle is shown, showing exemplary embodiments in a first section, a second section, and a third section, e.g., a home screen, a vehicle, a dashboard, a bottom navigation, etc. It will be understood that Figure 13A 、 Figure 13B and Figure 13C can be combined to form a single exemplary screen navigation structure, but by 13A to 13C Shown in three separate parts. Figure 13AAs shown, the user can navigate to the Home screen / Garage and then select a specific vehicle of interest to view information for that vehicle in the dashboard. When viewing maintenance information, this information may include information about the battery 14, including battery life, battery health, and other information. Furthermore, the maintenance information may include information about the battery health bar, the belt / hose health bar, and the brake health bar. The "health bar" indicates the health status of specific components and / or systems of the vehicle 12. When viewing the maintenance information and battery health bar, as well as battery-related health information, if a battery replacement is recommended, information about potential battery replacements may be available, including facts about various batteries and potential replacement options that may be available. Allowing the user to compare various potential replacement options can help the user select which battery will be best suited for the vehicle, the specific environment, and the type of driving performed in the vehicle. Further details about the replacement battery may include information about the part number associated with the specific replacement battery. Once a replacement battery is selected, the user may also enter data and other custom information about the battery. For example, if a battery is in a cold environment, the battery's parameters may differ from those in an extreme environment, all of which can significantly affect the battery's lifespan and when it may need replacement. Further, on the "Enter Battery Information" screen, such as after performing a battery replacement, the user may be prompted to reset the battery health status. In some embodiments, this action may be performed automatically by receiving information from the BMS that the battery is a replacement battery.
[0097] Continue to refer 13A to 13C, referring to the maintenance section, there may be a health section to provide the health status of belts / hoses, brakes, filters, fluids, lights, spark plugs, suspension, tires, water pump, and wiper blades. Each of these maintenance areas provides the user with additional information about the vehicle 12. As a non-limiting example, brakes may include information about brake pads and rotors. Filters may have information about the oil filter, including facts and information about the oil filter, the mileage before the next change, and filter replacement options and certain brands and part numbers. Once the oil filter is replaced, the mileage before the next change can be reset and / or customized. For example, if the user is in a warm or cool climate, this may affect how often the oil filter in the vehicle should be replaced. Additional information and details may be provided about the engine air filter, cabin air filter, and fuel filter. The fluid health section may have information about engine oil, power steering fluid, and transmission fluid. Regarding engine oil, there may be additional information regarding oil-related facts and information, mileage until next change, oil type and / or capacity, and oil change options, including certain brands and associated numbers for specific products. Furthermore, once the engine oil has been changed, the mileage until next change can be reset and / or manually adjusted. For example, if there is a reason to change the engine oil earlier or later than generally recommended, this can be manually set. Regarding lights, there may be a Light Health column that may include information regarding the headlights, brake lights, turn signals, running lights, hazard / fog lights, and any other lights associated with the vehicle 12. There may also be a Spark Plug Health column that includes information regarding the health and any related conditions of any spark plugs associated with the vehicle 12. There may also be a Tire Health column that includes information regarding the health and any related conditions of any tires associated with the vehicle 12. Furthermore, if the tires are in warm or cold climates and / or are used for frequent off-road driving and other applications that may affect the tires, this information may be incorporated into the information regarding the health of the vehicle 12's tires. The suspension system may have a health column and include information related to the shocks and supports of the suspension system. There may be a water pump health column that has information about the health of the water pump associated with the vehicle 12 and any related conditions. Additionally, the wiper blades may have health column information that may include information about the front windshield as well as the rear windshield (if a rear windshield is present). It will be understood that these are intended as non-limiting examples of the options available on the maintenance column. There may also be information related to battery life, recall notices (including manufacturer's notices), vehicle history (history by date and history by category). In addition to detailed maintenance information, such as Figure 13AThe illustrated navigation screen may include recall notices from the manufacturer related to any component and / or system of the vehicle 12, a vehicle history including a history by date for the vehicle and a history by category for the vehicle 12, which may provide detailed historical information about the vehicle 12, including when tires were placed on the vehicle 12, when any and / or all tires on the vehicle 12 were replaced, any repairs related to the vehicle, any original and / or replacement components and / or systems on the vehicle, and other information regarding the history of parts and components of the vehicle 12. Finally, the navigation screen may include diagnostic scan information including whether a diagnostic scan has been installed on the vehicle or not installed on the vehicle.
[0098] Figure 14 is a flow chart of an example process (i.e., method) in device 24 according to some embodiments of the present invention. One or more blocks described herein may be performed by one or more elements of device 24, such as one or more of processing circuitry 74 (including device management unit 26), processor 76, and / or communication interface 72. Device 24 is configured to obtain (Block S100) one or more of vehicle parameters, battery parameters, and accessory parameters from one or more of accessory 20, BMS 16, and server 28. Device 24 is further configured to determine (Block S102) maintenance parameters based on one or more of the vehicle parameters, battery parameters, and accessory parameters.
[0099] Now refer to Figure 15 , which is another exemplary flow chart of an example process (i.e., method) in device 24 according to some embodiments of the present invention. One or more blocks described herein may be performed by one or more elements of device 24, such as one or more of processing circuitry 74 (including device management unit 26), processor 76, and / or communication interface 72. Device 24 is configured to obtain (Block S104) one or more of the following: vehicle parameters received from one of an accessory and a server, battery parameters received from one of BMS 16 and accessory 20, and accessory parameters received from one or more of accessory 20, BMS 16, and server 28. Device 24 is configured to determine (Block S106) one or more maintenance parameters based on one or more of the vehicle parameters, battery parameters, and accessory parameters. Device 24 is further configured to determine (Block S108) one or more maintenance actions based on the determined one or more maintenance parameters.
[0100] In some embodiments, the method further includes assigning a rating to each of the vehicle parameter, the battery parameter, and the accessory parameter.
[0101] In some other embodiments, the rating is based on one or more of a predetermined battery life cycle, a battery parameter threshold, a service promotion, a maintenance schedule, a reminder, and a recall.
[0102] In some embodiments, the method further includes identifying a preset battery function and a preset vehicle parameter, and triggering one or more maintenance actions based on the preset battery function and the preset vehicle parameter, the one or more maintenance actions indicating battery replacement.
[0103] In some embodiments, the method further includes identifying a preset battery parameter and triggering the one or more maintenance actions based on the preset battery parameter, the one or more maintenance actions indicating replacement of at least one brake pad.
[0104] In some other embodiments, the method further includes identifying a preset vehicle parameter of the vehicle alternator and triggering one of the one or more maintenance actions based on the preset vehicle parameter, the one maintenance action indicating a remaining life cycle of the battery 14 .
[0105] In some embodiments, any component of system 10 (e.g., device 24) may be configured to predict the life cycle of the battery based on one or more parameters and / or functions that are not related to battery 14 or not directly associated with the life cycle of battery 14. For example, a prediction of the life cycle of battery 14 or other component of system 10 may be performed based on parameters associated with another data collection area, such as predicting the life cycle of the battery based on parameters associated with the vehicle's alternator and functional information including the environment in which the vehicle is driven, the driving style of the vehicle, and other functional information associated with vehicle 12.
[0106] In some other embodiments, when the software 80 (e.g., a mobile application) is launched, the device 24 wirelessly connects to the BMS 16, such as via Bluetooth or another suitable wireless communication protocol. The device 24 can then receive data associated with the battery 14. This data can be displayed on one or more displays 112 having one or more navigational features described above. Additional data can be received from an accessory 20 (e.g., an OBD connected to the vehicle 12 and configured to monitor one or more vehicle parameters and / or functions) and transmitted to the device 24 (e.g., for display by the software 80). The parameters displayed by the software 80 can be customizable to adjust the vehicle maintenance schedule based on the specifications of one or more parts associated with the vehicle 12 (e.g., brake pads). For example, if the brake pads installed on the vehicle 12 require maintenance at a frequency different from the recommended maintenance schedule for the OEM brake pads, a user of the software 80 can customize the brake pad replacement frequency parameters. The OEM maintenance schedule can be downloaded from the server 28 (e.g., an OEM server). For example, device 24 can be configured to download data using vehicle information (e.g., VIN) and / or battery information. Part, component, and / or system intervals associated with the vehicle information and / or battery information can be included in the downloaded data. Data can be downloaded from server 28 (e.g., with a default OEM plan) and / or from any other device. In some embodiments, the downloaded data includes default intervals. Default intervals can be customized by a user (e.g., a user of software 80), such as based on the specific parts being used or other customizable parameters.
[0107] In some embodiments, the device 24 can be configured to determine one or more functions (e.g., displayed on the software 80, on the dashboard, etc.) based on whether the accessory 20 (e.g., OBD) is connected to the vehicle 12 and / or the battery 14 and / or the device 24 and / or the server 28. These functions may include, but are not limited to, battery functions, accessory functions, vehicle functions, device functions, and server functions. That is, in some embodiments, the software 80 can be configured to provide one or more functions associated with any component or system of the system 10 on a single user interface, thereby connecting all information and data together for the user in one place.
[0108] In some other embodiments, battery 14 is provided as a battery-as-a-service (BAS), in which the user of the battery does not own the battery but rather has the right to use it in a prescribed manner. Battery 14 will be replaced by the BAS service provider when needed. One or more parameters can be modified or indications triggered based on lifecycle requirements, the functionality of the battery as determined by system 10, and / or a set replacement schedule provided by the BAS service provider. For example, if a battery is experiencing a degraded condition and this functionality becomes apparent through system 10, an event can be triggered or a parameter modified so that the user of battery 14 receives a maintenance action. This maintenance action can then trigger a maintenance action indication 114, for example, via software 80, indicating that a battery maintenance visit has been scheduled based on the degradation condition. Lifecycle requirements may include a SoC level below a predetermined threshold that could potentially cause catastrophic failure of battery 14—i.e., if the SoC condition persists for a predetermined period of time, it would shorten the life of battery 14. Thus, if this functionality is measured in the SoC and compared to specific parameters, a maintenance action can be triggered.
[0109] In some embodiments, accessory 20 (e.g., an OBD) is also configured to obtain one or more parameters and functions associated with battery 14 (e.g., a smart battery via a BMS, a battery via sensors associated with the battery). For example, accessory 20 can be configured to obtain SoC information or other information about battery 14, such as determined by BMS 16. Based on the information obtained from accessory 20, a battery failure can be expected to occur within a certain time interval. The information obtained from accessory 20 can also be combined with information from battery 14 to determine the state of health of battery 14. Conventional OBD devices cannot obtain battery information.
[0110] Furthermore, one or more components of system 10 (such as BMS 16 and / or accessories 20 and / or device 24) can be configured to determine a crank curve (e.g., associated with starting an engine). A voltage curve associated with the crank curve can be used to predict battery failure. In a non-limiting example, a voltage change (e.g., a voltage drop) as a measured function compared to a predetermined voltage threshold as a preset parameter can be used to predict battery failure. The predicted battery failure can be communicated to any component of the system, such as device 24.
[0111] In some embodiments, battery failure can be predicted, or parameters can be modified based on multiple functions, which can have different hierarchical levels. For example, the hierarchy of functions can include functions such as a change in SoC greater than a predetermined threshold and the need to replace the air conditioner filter within the next six months. In this non-limiting example, the level of SoC change is greater than the level of the air conditioner filter. Device 24 can be configured to expedite battery maintenance scheduling and / or bundle it with the air conditioner maintenance (i.e., recommending both actions be performed during a single visit to the service provider). Bundling can be performed based on other parameters and / or conditions, such as promotions. In some embodiments, if the maintenance associated with the air conditioner has a lower level (e.g., a lower priority) than the level of SoC change, the air filter replacement is not bundled. In other words, device 24 can be configured to modify the OEM-recommended schedule or any other schedule based on other parameters and / or functions associated with vehicle 12 and / or battery 14. In one or more embodiments, maintenance can be automatically scheduled by device 24 (and / or server 28) based on information obtained by accessory 20 and / or BMS 16.
[0112] In some embodiments, a determination by device 24 that vehicle 12 should be taken to a service provider for maintenance may be based on more than one parameter and / or function indicating that attention is needed (and / or other items not so indicated). In some other embodiments, instead of each item triggering a separate maintenance visit, device 24 may be configured to comprehensively determine a maintenance schedule based on multiple parameters and / or functions, some of which may not require a maintenance visit. In some embodiments, the determination is made to provide maintenance that is as minimally disruptive to the customer as possible.
[0113] In some embodiments, server 28 is capable of accessing, accumulating, and synthesizing information, including, but not limited to, historical and real-time data from any other devices, including, but not limited to, historical data regarding the vehicle 12, battery 14, accessories 20, and data associated therewith, historical data regarding the vehicle / systems / or components, and / or devices 24 in communication with server 28, and using this data and information, alone or in combination with additional information / data, including, but not limited to, battery functionality, accessory functionality, BMS functionality, device functionality, and / or server functionality, to provide maintenance parameters. As a non-limiting example, server 28 can be configured to access information from various devices and, based on the information provided to server 28, can provide maintenance parameters to device 24 to assist in determining a course of action, including, but not limited to, a proposed maintenance action. Server 28 can be provided with historical data indicating, for example, the average time a particular vehicle may need its brake pads replaced, mileage information, and environmental information, which can be based in part on historical data for a particular make and model of vehicle. Server 28 may also communicate with other devices in vehicle 12, including accessories 20. These devices may have parameters and functionality related to vehicle 12, battery 14, BMS 16, accessories 20, and / or devices 24, as well as other information and data that can be merged and / or aggregated with historical information by server 28. Server 28 may determine maintenance actions based on this information. Information related to maintenance actions may relate to maintenance, diagnostic issues, and / or upkeep of the vehicle (including any systems and / or components of the vehicle). For example, certain maintenance actions may be determined based on parameters and functionality of battery 14, accessories 20, vehicle 12, and other devices. For example, an example of a maintenance action might be that the brake pads on vehicle 12 should be replaced, depending on the parameters, functionality, and other information and / or data provided. For example, server 28 may obtain information about the battery life of a specific battery in vehicle 12 based on the make and model of the battery, various environmental conditions that may affect the battery, how vehicle 12 is driven, how often vehicle 12 is started and shut down, any customizations to vehicle 12, and other information and data. The server 28 may also communicate with other devices in the vehicle 12, including the accessories 20 (which may include an OBD) and the BMS 16, the battery 14, and external devices, and the server 28 may aggregate information, and the server 28 may provide one or more maintenance actions based on this information regarding when the battery in the vehicle 12 may be replaced.
[0114] In some embodiments, one or both of the vehicle parameters and functions and the battery parameters and functions are received and obtained by the accessory 20 from the BMS 16 .
[0115] In some other embodiments, the vehicle parameters are received at least in part from server 28 .
[0116] In an embodiment, one or both of the vehicle parameters and the battery parameters include one or more OEM maintenance schedules.
[0117] In another embodiment, one or more OEM maintenance schedules are user customizable based on one or both of vehicle information (e.g., specifications of parts installed other than OEM parts) and battery information (e.g., information associated with battery service).
[0118] In another embodiment, the one or more OEM maintenance schedules are user customizable based on one or both of vehicle functionality and battery functionality.
[0119] In some embodiments, determining the maintenance parameter is based on a level associated with one or more of a vehicle parameter, a battery parameter, and an accessory parameter.
[0120] In some other embodiments, a rating is assigned to each of the vehicle parameters, battery parameters, and accessory parameters based on one or more predetermined battery life cycles, battery parameter thresholds, service promotions, maintenance schedules, reminders and recalls, and functionality of specific systems and / or components of the vehicle 12.
[0121] In an embodiment, the maintenance parameters include a recommended service visit time (eg, within the next three days) and a priority (eg, high priority) associated with one or more of the vehicle parameter, the battery parameter, and the accessory parameter.
[0122] In another embodiment, the service visit indicates a battery replacement.
[0123] In one or more embodiments, the accessory 20 (e.g., OBD II) and / or the BMS 16 of the smart battery 14 can be configured to connect to a device 24 (e.g., a customer's phone) via one or more communication links using one or more protocols such as Bluetooth. In one or more embodiments, the software 80 (e.g., a software application) can be configured to transmit (e.g., via the communication interface 72) one or more parameters (e.g., battery state of charge and / or vehicle information including mileage) to a server 28 (e.g., a cloud server). The transmission of the one or more parameters can be performed via the device 24 (e.g., a customer's phone). The server 28 can be configured to provide a state of health assessment of the battery 14. In some other embodiments, the software 80 (e.g., a software application) and / or the device management unit 26 can be configured to compare mileage (or time) with the vehicle manufacturer's recommended maintenance intervals to provide recommendations for replacing parts on the vehicle 12 (e.g., wipers, filters, brakes, etc.). In some embodiments, replacement purchases can be grouped and associated with retail partners. Additionally, based on the customer's location, the application can direct the customer to the nearest retail store.
[0124] Furthermore, for example, the server management unit 30 can be configured to retrieve information stored on the server 28 and also share information with the server 28. If the server 28 is enabled, the server 28 can be programmed to share information about the vehicle 12 and / or retrieve information about the make / model of the vehicle 12 or specific information about the vehicle 12, including the vehicle's operating history, including any recalls, accelerations, decelerations, speeds, any storage periods, the vehicle's surroundings, the location where the vehicle is parked, surrounding saltwater and / or freshwater, precipitation, etc. The server management unit 30 can have information including maintenance schedules associated with certain systems in the vehicle 12. For example, the server management unit 30 can have information from the manufacturer regarding specific maintenance expectations / requirements provided by the manufacturer, which can be integrated into the system 10 and used to determine whether maintenance actions are warranted. Additionally, the server management unit 30 can communicate with the server 28.
[0125] In one or more embodiments, unplanned downtime due to battery or maintenance item failure can be avoided because device 24 can be configured to predict one or more factors associated with battery life cycle and maintenance. In some embodiments, the prediction can include determining and / or recommending that the maintenance item be scheduled at a time different from the scheduled time. In some other embodiments, for example, where a customizable schedule is provided to the user based on one or more priority factors, the time may differ from the scheduled schedule recommended by the OEM. In some embodiments, the prediction is performed using artificial intelligence, machine learning, or the like.
[0126] In some embodiments, maintenance or parts purchases can be scheduled before a part fails. In some other embodiments, a consumer or user can track and take action on vehicle maintenance items for all vehicles in a single platform. In one embodiment, a consumer or user can monitor battery health on device 24 (e.g., a mobile phone). In another embodiment, battery and maintenance item purchases can be linked and grouped together for purchase.
[0127] In some embodiments, battery 14 can be configured to communicate its performance and / or when it needs to be replaced. In some other embodiments, device 24 and / or server 28 can be configured to predict the battery's state of health, which can provide for planning replacements, utilizing the full life of battery 14, preventing unexpected failure of battery 14, and the like. In some other embodiments, vehicle performance can be optimized because one or more components of system 10 provide complete knowledge of the battery's capacity. In some embodiments, knowledge of the battery's state (e.g., charge level) enables OEMs to optimize vehicle performance (e.g., fuel consumption, emissions, performance), which can improve the customer experience.
[0128] In some embodiments, battery 14 and battery health predictions can be provided as a service, where a dashboard and / or mobile application (such as software 80) can be provided, for example, via one or more communication links and / or a cloud platform, a network, and / or one or more communication interfaces. In some other embodiments, battery 14 can be a smart battery or a battery having at least one sensor for determining one or more parameters. In one or more embodiments, predictive analysis and / or trending data can be provided.
[0129] In one or more embodiments, a device 24 (e.g., having software 80 , such as a software application) and / or an accessory 20 (e.g., OBD II) may be provided. In some embodiments, for example, access to the software application (i.e., software 80 ) and / or data may be provided even without a connection to the vehicle 12 . In other embodiments, data collection may be provided without a connection to the vehicle 12 . In some embodiments, one or more of the following may be provided: maintenance scheduler functionality, maintenance reminders, replacement part identification, links to retail locations, links to retail incentive programs, battery diagnostics, battery maintenance reminders with recommended actions, vehicle diagnostic scans (e.g., diagnostic scans for error codes), clearing or resetting fault codes, trip information (mileage, speed, fuel economy), recall notifications, history reports, email reports, etc. In another embodiment, battery diagnostics may include internal combustion engine information, such as start and stop information and mild hybrid information. In some embodiments, battery diagnostics may include battery reminders and scheduled replacement information.
[0130] In some embodiments, the maintenance scheduler functionality may be customizable, adjustable, actionable, etc. In some other embodiments, battery diagnostics may include real-time health status, fault status, state of charge information. In some embodiments, history reports and / or trip information may be provided manually.
[0131] In one or more embodiments, software 80 (e.g., a software application) includes a home screen (e.g., on device 24) that may include information about one or more vehicles (e.g., a garage). The home screen may be a user interface and may be accessed with or without a connection to one or more devices. In some embodiments, software 80 may serve as a primary landing point for the user and may include icons at various locations on the user interface (e.g., at the bottom or top of all screens). Information provided by software 80 may include a dashboard, scans (OBD II), maintenance information, an advanced homepage, vehicle history, and battery health information. In some embodiments, a dashboard is provided and may include reminders, recalls, critical maintenance items, and battery health information. Information on the dashboard may be color-coded, for example, using a red / yellow / green color scheme for each critical area (e.g., green - good for next maintenance check, yellow - needs monitoring, red - requires immediate attention). Further, the information can be configured to provide access to error codes, such as links to a server or third-party entity that can provide error code details, and recall notices, such as links to the National Highway Traffic Safety Administration (NHTSA), such as via OBD II or manual vehicle identification number (VIN) entry. Further, the dashboard can be configured to provide maintenance reminders, such as links to maintenance item details and links to websites for purchased parts and instructions.
[0132] In some embodiments, accessory 20 (e.g., OBD II) can be configured to provide scans, such as a full system scan for error codes (e.g., using only OBD II). Each area can be provided with a link to access detailed information. Further, error codes can be provided via a link to a server or third-party entity that can provide error code details (e.g., using only OBD II), and / or recall notifications can be provided via a link to NHTSA (OBD II or manual VIN entry). In some other embodiments, maintenance information may begin with recommendations, for example. In some embodiments, maintenance can be customized. In some embodiments, each line of maintenance information may be actionable. In another embodiment, a red / yellow / green color is provided for each key area. Each line item may have a baseline for the manufacturer's recommended vehicle settings, and then allow for manual adjustment. In some embodiments, for example, when using accessory 20 and / or battery diagnostics and maintenance scheduling, each item is clickable and provides a link to a website for purchased parts and instructions.
[0133] In an embodiment, accessory 20 (e.g., an OBD II dongle) can be programmable and configured to communicate with other devices using one or more protocols, such as Bluetooth. Accessory 20 can provide battery diagnostics and vehicle diagnostics and be configured for data storage. Further, accessory 20 can be configured to communicate using other protocols or radio access technologies. In another embodiment, accessory 20 can be configured to provide one or more of the following data outputs: battery SoH, vehicle error codes, vehicle recall summary, Global Positioning System (GPS) data and / or speed, idle and / or start-stop time, tire pressure, etc.
[0134] In some embodiments, accessory 20 can be configured to communicate with device 24 (a consumer mobile device), which can be configured to communicate with a server 28 (e.g., on a cloud network) and / or provide data and / or information that can be made available to an application or web portal (e.g., software 80) on device 24.
[0135] Example information that can be provided via the software 80 of the device 24 includes logged maintenance for all vehicles. Information that can be provided can include scheduling maintenance and setting automatic maintenance reminders. Vehicle maintenance grouping can be used to facilitate better scheduling. Information can be customizable and can further include savings on purchased parts, such as discounts for bundled orders and timing to take advantage of promotions. Furthermore, the software 80 can be configured as "one-stop shopping" for maintenance, providing access to vehicle maintenance, replacement error code information (including installation instructions and videos), real-time, accurate assessment of vehicle health, and advanced fault detection and notifications to avoid difficulties.
[0136] In some embodiments, users of system 10 (e.g., service providers) can receive battery replacement information, connect directly to incentive programs, and access higher-fidelity consumer data, including driving behavior and actual maintenance needs. Furthermore, users can target, plan, and bundle promotions based on vehicle maintenance needs and improved customer insights. Device 24 can use this information to determine one or more actions associated with the lifecycle of battery 14 and / or vehicle 12. Furthermore, warranty actions can be based on battery SoH accuracy.
[0137] In some other embodiments, users of the system 10 (e.g., battery manufacturers) may receive access to high-fidelity data, consumer data (driving patterns, maintenance, and purchasing behavior), VIN-level vehicle information including fault codes and part issues, battery-level information, consumer behavior, etc. The information received by the user may be further used to determine demand forecasts—planned inventory based on actual customer demand—and warranty information based on battery SoH accuracy.
[0138] In some embodiments, the device 24 and / or the processing circuit system 74 can be configured to generate a maintenance action indication. The maintenance action indication can be used to notify any component of the system 10 to a user and / or cause any component of the system 10 to perform another action. For example, the maintenance action indication can notify the user of the maintenance action so that the user can take action accordingly. The maintenance action indication can also cause the BMS 16, the accessory 20, the server 28, and / or the vehicle system of the vehicle 12 to perform another action. For example, the device 24 can communicate with the vehicle system via Bluetooth or any other protocol and cause the vehicle system to perform another action.
[0139] Maintenance action indication 114 may be included in a message transmitted by device 24 to one or more of an accessory, a BMS, a server, and a vehicle system, for example, using any communication protocol. The maintenance action indication may also cause device 24 to display a reminder to the user on device 24 (e.g., in a software application associated with software 80). Another action may include one or both of scheduling a maintenance appointment (e.g., at a dealership or service center) and creating a record accessible to a service provider (e.g., by an agent at the dealership or service center). The record may indicate or include the maintenance action. Furthermore, another action may cause the BMS to switch to a predetermined operating mode (e.g., a power-saving operating mode, an operating mode that meets battery performance requirements, etc.).
[0140] Another action may also cause a vehicle system of vehicle 12 to display another reminder (on a display on the instrument panel, on an infotainment display, etc.). The vehicle system may also disable or enable a driving mode. For example, a driving mode may minimize and / or disable the use of predetermined components and / or systems of vehicle 12. A sport mode (e.g., in which gears are shifted at higher revolutions per minute) may be disabled. Any other action may also be performed.
[0141] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining hardware and software aspects, collectively referred to herein as a "circuit" or "module." Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.
[0142] Some embodiments are described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowcharts and / or block diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (thereby constructing a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device construct a means for implementing the functions / actions specified in one or more blocks of the flowcharts and / or block diagrams.
[0143] These computer program instructions may also be stored in a computer-readable memory or storage medium, which may direct a computer or other programmable data processing device to function in a particular manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction devices that implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0144] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be executed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0145] It should be understood that the functions / actions indicated in the blocks may not occur in the order indicated in the operational diagrams. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. Although some figures include arrows on communication paths to illustrate the primary direction of communication, it should be understood that communication may occur in the opposite direction of the arrows depicted.
[0146] The computer program code for the operation of the concepts described herein can be written in an object-oriented programming language (such as Python, Java® or C++). However, the computer program code for the operation of the present disclosure can also be written in a conventional procedural programming language (such as the "C" programming language). The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or completely on the remote computer. In the latter case, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider through the Internet).
[0147] Many different embodiments have been disclosed herein in conjunction with the above description and accompanying drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and obfuscating. Accordingly, all embodiments may be combined in any manner and / or combination, and this specification, including the accompanying drawings, should be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, as well as the manner and process of making and using them, and should support claims for any such combination or subcombination.
[0148] Those skilled in the art will appreciate that the embodiments herein are not limited to those specifically shown and described above. In addition, unless otherwise indicated above, it should be noted that all drawings are not drawn to scale. Various modifications and variations are possible based on the above teachings and the following embodiments.
Claims
1. A device (24) configured to communicate with one or more of an accessory (20), a battery management system (BMS) (16), and a server (28), the device (24) comprising processing circuitry (74) configured to: obtaining one or more of a vehicle parameter, a battery parameter, and an accessory parameter from one or more of the accessory (20), the BMS (16), and the server (28); determining one or more maintenance parameters based on said one or more of said vehicle parameters, said battery parameters, and said accessory parameters; and One or more maintenance actions are determined based on the determined one or more maintenance parameters.
2. The device (24) as claimed in claim 1, wherein The vehicle parameters are received from one or both of the accessory (20) and the server (28).
3. The device (24) as claimed in any one of claims 1 and 2, wherein The battery parameters are received from the BMS (16).
4. The device (24) as claimed in any one of claims 1 to 3, wherein The battery parameters are received from the accessory (20).
5. The device (24) as claimed in any one of claims 1 to 4, wherein One or both of the vehicle parameters and the battery parameters are received from the BMS (16) via the accessory (20).
6. The device (24) as claimed in any one of claims 1 to 5, wherein One or both of the vehicle parameters and the battery parameters include one or more Original Equipment Manufacturer (OEM) maintenance schedules.
7. The device (24) as claimed in claim 6, wherein The one or more OEM maintenance schedules are user customizable based on one or more of the vehicle parameters, the battery parameters, and the accessory parameters.
8. The device (24) as claimed in any one of claims 6 and 7, wherein The vehicle parameter is one or more of vehicle spark plug performance, spark plug operation, and spark plug maintenance.
9. The device (24) as claimed in any one of claims 6 to 8, wherein The battery parameters are one or more of battery performance, battery management, battery operation, battery maintenance, and battery health.
10. The device (24) as claimed in any one of claims 1 to 10, wherein The processing circuitry is further configured to: A rating is assigned to each of the vehicle parameter, the battery parameter, and the accessory parameter.
11. The device (24) according to claim 10, wherein The rating is based on one or more of a predetermined battery life cycle, a battery parameter threshold, a service promotion, a maintenance schedule, a reminder, and a recall.
12. The device (24) as claimed in any one of claims 1 to 11, wherein The determined one or more maintenance parameters include a recommended service visit time and a priority associated with one or more of the vehicle parameter, the battery parameter, and the accessory parameter.
13. The device (24) as claimed in claim 12, wherein The determined one or more maintenance actions indicate a battery replacement.
14. The device (24) as claimed in claim 13, wherein The determined one or more maintenance actions further indicate at least one location for purchasing the battery (14).
15. The device (24) as claimed in any one of claims 12 to 14, wherein The processing circuitry (74) is further configured to: identifying predetermined battery functions and predetermined vehicle parameters; and The determined one or more maintenance actions are triggered based on the preset battery function and the preset vehicle parameter, the determined one or more maintenance actions indicating battery replacement.
16. The device (24) as claimed in any one of claims 1 to 15, wherein The processing circuitry (74) is further configured to: Identify preset battery parameters; and The determined one or more maintenance actions are triggered based on the preset battery parameters, and the determined one or more maintenance actions indicate replacing at least one brake pad.
17. The apparatus (24) as claimed in any one of claims 1 to 16, wherein The determined one or more maintenance actions include at least two vehicle maintenance services.
18. The apparatus (24) as claimed in any one of claims 1 to 17, wherein The processing circuitry (74) is further configured to: identifying preset vehicle parameters for the vehicle alternator; and One of the determined one or more maintenance actions is triggered based on the preset vehicle parameter, the determined one or more maintenance actions indicating a remaining life cycle of the battery (14).
19. The apparatus (24) as claimed in any one of claims 1 to 17, wherein The processing circuitry (74) is configured to download one or more maintenance schedules from the server.
20. The apparatus (24) as claimed in any one of claims 1 to 19, wherein One or more of the following: The processing circuitry (74) is further configured to generate a maintenance action indication (114); The maintenance action indication (114) is one or more of the following: Notifying a user of the determined one or more maintenance actions (114); causing one or more of the accessory (20), the BMS (16), the server (28), and the vehicle system (10) to perform another action; included in a message transmitted by the device (24) to one or more of the accessory (20), the BMS (16), the server (28), and the vehicle system (10); causing the device (24) to display a reminder for the user on the device (24); The another action includes one or both of: scheduling a maintenance appointment and creating a record accessible to the service provider, the record indicating the determined one or more maintenance actions; The another action includes causing the BMS (16) to switch to a predetermined operating mode; and The other action includes causing the vehicle system (10) to perform one or both of the following operations: Display another reminder; and Disable or enable driving mode.
21. A device (24) configured to communicate with one or more of an accessory (20), a battery management system (BMS) (16), and a server (28), the device (24) comprising processing circuitry (74) configured to: Get one or more of the following: vehicle parameters received from one of the accessory (20) and the server (28); Battery parameters received from one of the BMS (16) and the accessory (20); and accessory parameters received from one or more of the accessory (20), the BMS (16), and the server (28); Get one or more of the following: a vehicle function received from one of the accessory (20) and the server (28); a battery function received from one of the BMS (16) and the accessory (20); and accessory functionality received from one or more of the accessory (20), the BMS (16), and the server (28); One or more maintenance parameters are determined based on: one or more of the vehicle parameters, the battery parameters, and the accessory parameters; and one or more of a vehicle function, a battery function, and an accessory function; and One or more maintenance actions are determined based on the determined one or more maintenance parameters.
22. The apparatus (24) of claim 21, wherein One or both of the vehicle parameters and the battery parameters include one or more Original Equipment Manufacturer (OEM) maintenance schedules.
23. The device (24) as claimed in claim 22, wherein The one or more OEM maintenance schedules are user customizable based on one or both of the vehicle parameters and the battery parameters.
24. The device (24) as claimed in any one of claims 22 and 23, wherein The vehicle parameter is at least one of vehicle spark plug performance, spark plug operation, and spark plug maintenance.
25. The apparatus (24) as claimed in any one of claims 21 to 24, wherein The battery parameters are one or more of battery performance, battery management, battery operation, battery maintenance, and battery health.
26. The apparatus (24) as claimed in any one of claims 21 to 25, wherein The processing circuitry (74) is further configured to: A rating is assigned to each of the vehicle parameter, the battery parameter, and the accessory parameter.
27. The apparatus (24) of claim 26, wherein The rating is based on one or more predetermined battery life cycles, battery parameter thresholds, service promotions, maintenance schedules, reminders, and recalls.
28. The apparatus (24) as claimed in any one of claims 21 to 27, wherein The determined one or more maintenance parameters include a recommended service visit time and a priority associated with the one or more of the vehicle parameter, the battery parameter, and the accessory parameter.
29. The apparatus (24) as claimed in any one of claims 21 to 28, wherein The determined one or more maintenance actions indicate a battery replacement.
30. The apparatus (24) of claim 29, wherein The determined one or more maintenance actions further indicate at least one location for battery replacement.
31. The apparatus (24) as claimed in any one of claims 21 to 30, wherein The processing circuitry (74) is further configured to: Another level is assigned to each of the vehicle function, the battery function, and the accessory function.
32. The apparatus (24) as claimed in any one of claims 21 to 31, wherein One or more of the following: The processing circuitry (74) is further configured to generate a maintenance action indication (114); The maintenance action indication (114) is one or more of the following: notifying a user of the one or more maintenance actions; causing one or more of the accessory (20), the BMS (16), the server (28), and the vehicle system (10) to perform another action; included in a message transmitted by the device (24) to one or more of the accessory (20), the BMS (16), the server (28), and the vehicle system (10); causing the device (24) to display a reminder for the user on the device (24); The another action includes one or both of: scheduling a maintenance appointment and creating a record accessible to the service provider, the record indicating the determined one or more maintenance actions; The another action includes causing the BMS (16) to switch to a predetermined operating mode; and The other action includes causing the vehicle system to perform one or both of the following operations: Display another reminder; and Disable or enable driving mode.
33. A method performed in a device (24) configured to communicate with one or more of an accessory (20), a battery management system (BMS) (16), and a server (28), the method comprising: obtaining (S104) one or more of vehicle parameters, battery parameters, and accessory parameters from one or more of the accessory (20), the BMS (16), and the server (28); and determining ( S106 ) one or more maintenance parameters based on the one or more of the vehicle parameter, the battery parameter, and the accessory parameter; as well as One or more maintenance actions are determined ( S108 ) based on the determined one or more maintenance parameters.
34. The method of claim 33, wherein: The method further comprises: A rating is assigned to each of the vehicle parameter, the battery parameter, and the accessory parameter.
35. The method of claim 34, wherein: The rating is based on one or more of a predetermined battery life cycle, a battery parameter threshold, a service promotion, a maintenance schedule, a reminder, and a recall.
36. The method of any one of claims 33 to 35, wherein The method further comprises: identifying predetermined battery functions and predetermined vehicle parameters; and The determined one or more maintenance actions are triggered based on the preset battery function and the preset vehicle parameter, the determined one or more maintenance actions indicating battery replacement.
37. The method of any one of claims 33 to 36, wherein The method further comprises: identifying preset battery parameters; and The determined one or more maintenance actions are triggered based on the preset battery parameters, and the determined one or more maintenance actions indicate replacement of at least one brake pad.
38. The method of any one of claims 33 to 37, wherein The method further comprises: identifying preset vehicle parameters for the vehicle alternator; and One of the determined one or more maintenance actions is triggered based on the preset vehicle parameter, the one maintenance action indicating a remaining life cycle of the battery (14).