VEHICLE BATTERY MONITORING SYSTEM

Abstract

A battery monitoring system comprises a vehicle processor that stores battery data and a user device that communicates with the vehicle processor. The user device includes data processing hardware that stores a weather application, a navigation application, and a battery monitoring application. The battery monitoring application is designed to receive battery data from the vehicle processor and weather data from the weather application. The battery monitoring application is also designed to present battery efficiency options to the user based on the battery and weather data.

Description

INTRODUCTION

[0001] The information contained in this section is intended to provide a general context for the disclosure. Work by the presently named inventors, to the extent described in this section, as well as aspects of the description that may not otherwise be considered prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0002] The present disclosure generally relates to a vehicle battery monitoring system.

[0003] Electric vehicles use dedicated charging stations, which are increasingly being integrated into gas stations. Most electric vehicles display an available range before recommending charging. Available range can be affected by the battery's efficiency during operation. Battery efficiency can often be affected by weather and traffic conditions. Because both weather and traffic conditions are relatively unknown before starting a trip, drivers often rely on battery range monitoring to determine when to stop and recharge.

[0004] It is also common for drivers to use a navigation system to create a route to a destination. The route generated by the navigation system is typically the fastest route from the driver's position at the start of the journey to the destination. Similarly, drivers may use a weather system to monitor the weather while driving or to determine the weather conditions at their destination. While navigation and weather systems provide data related to navigation and weather, respectively, these systems are typically separate from the vehicle's battery data. SUMMARY

[0005] In some aspects, a battery monitoring system for a vehicle includes a vehicle processor that stores battery data, including battery capacity and range. The battery monitoring system also includes a user device communicatively coupled to the vehicle processor and including computing hardware. The computing hardware stores a weather application and a battery monitoring application configured to receive the battery data from the vehicle processor and the weather data from the weather application. A server is communicatively coupled to the vehicle processor and the user device. The server is configured to monitor battery efficiency data from one or more third-party processors.The server is further configured to transmit the battery efficiency data to the user device, and the battery monitoring application is configured to present battery predictions to the user based on the battery data and the battery efficiency data.

[0006] In some examples, the vehicle processor may store environmental data from the vehicle's environmental controls, and the battery monitoring application may be configured to adjust the battery predictions based on the environmental data. In other examples, the user device may include a navigation application configured to display a route. The battery monitoring application may be configured to communicate with the navigation application and present the battery range along the route. The server may be configured to determine one or more battery inefficiencies from one or more third-party processors along the route. Optionally, the battery monitoring application may be configured to determine an alternative route in response to one or more determined battery inefficiencies. The alternative route may be an efficiency route.In some cases, the battery monitoring application may be designed to predict battery efficiency for the vehicle based on weather data.

[0007] In another aspect, a battery monitoring system includes a vehicle processor that stores battery data and a user device communicatively coupled to the vehicle processor. The user device includes data processing hardware that stores a weather application, a navigation application, and a battery monitoring application. The battery monitoring application is configured to receive the battery data from the vehicle processor and the weather data from the weather application. The battery monitoring application is further configured to present battery efficiency options to the user based on the battery data and the weather data.

[0008] In some configurations, the battery efficiency options may include one or more of an alternative travel time, an alternative route, and efficient driving patterns. The efficient driving patterns may include recommendations for increased battery efficiency. In some examples, the battery monitoring application may be configured to determine an alternative route and the alternative travel time in response to navigation data from the navigation application. The battery monitoring application may be configured to determine the battery efficiency options based on the battery data, the weather data, and the navigation data. The navigation data may include a route and traffic data, and the battery monitoring application may be configured to determine the efficiency of the route based on the weather data and / or the traffic data.In some examples, the battery monitoring system may also include a server that may be configured to detect third-party processors along the route and may be configured to transmit third-party efficiency data to the battery monitoring application.

[0009] In yet another aspect, a vehicle battery monitoring system includes a vehicle processor that stores battery data, and a user device communicatively coupled to the vehicle processor. The user device includes computing hardware that stores a navigation application and a battery monitoring application. The battery monitoring application is configured to receive the battery data from the vehicle processor and the navigation data from the navigation application. A server is communicatively coupled to the user device and is configured to receive the navigation data and monitor battery efficiency data from one or more third-party processors based on the navigation data.The server is further configured to transmit the battery efficiency data to the user device, and the battery monitoring application is configured to present revised efficiency options to the user based on the battery data and the battery efficiency data.

[0010] In some examples, the user device may include a weather application that may include weather data, and the battery monitoring application may be configured to determine a battery efficiency option in response to the weather data. The battery efficiency option may include an alternative departure time. In some aspects, the battery monitoring application may be configured to determine a first route and a second route based on the navigation data and the battery data. The battery monitoring application may be configured to compare the battery efficiency data from the server with each of the first and second routes. Optionally, the battery monitoring application may be configured to present the first route or the second route as an efficiency route in response to the battery efficiency data. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings described herein are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Fig. 1 is a perspective view of a vehicle having a vehicle processor in communication with a user device according to the present disclosure; Fig. 2 is a functional block diagram of a battery monitoring system according to the present disclosure; Fig. 3 is a schematic view of a battery monitoring application according to the present disclosure; Fig. 4 is a schematic view of a navigation application of a user device according to the present disclosure; Fig. 5 is a schematic view of a route planned on a navigation application according to the present disclosure; Fig. 6 is a schematic view of a battery monitoring application according to the present disclosure presenting an efficiency route; Fig. 7 is a schematic view of a message presented on a battery monitoring application according to the present disclosure; Fig. 8 is an exemplary flowchart of a battery monitoring application according to the present disclosure; and Fig. 9 is another exemplary flowchart of a battery monitoring application according to the present disclosure.

[0012] In the drawings, corresponding reference symbols designate corresponding parts. DETAILED DESCRIPTION

[0013] Example configurations will now be described in more detail with reference to the accompanying drawings. Because example configurations are provided, this is a thorough disclosure designed to convey the full scope of the disclosure to those skilled in the art. Specific details are set forth, such as examples of specific components, devices, and methods, to provide a thorough understanding of the configurations of the present disclosure. Those skilled in the art will appreciate that specific details need not be employed, that example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed to limit the scope of the disclosure.

[0014] The terminology used herein is for the purpose of describing particular example configurations only and is not intended to be limiting. As used herein, the singular articles “a,” “an,” and “the” can also include the plural forms, unless the context clearly indicates otherwise. The terms “comprise,” “comprising,” “including,” and “having” are inclusive and therefore specify the presence of features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The steps, processes, and operations described herein should not be construed as necessarily being performed in the particular order discussed or illustrated unless they are expressly identified as being in that order of performance.Additional or alternative steps may be applied.

[0015] Where an element or layer is described as being "on" or "engaging with" another element or layer, or as being "connected" or "coupled" or "attached" to it, it may be directly on or engaging with, connected, coupled, or attached to the other element or layer, or there may be intervening elements or layers. Conversely, where an element is described as being "directly on" or "directly engaging with" another element or layer, or as being "directly connected" or "directly coupled" or "directly attached" to it, there must be no intervening elements or layers. Other words used to describe the relationship between elements should be interpreted similarly (e.g.,(e.g., "between" versus "directly between," "adjacent" or "contiguous" versus "directly adjacent" or "directly adjacent," etc.). As used herein, the term "and / or" includes all combinations of one or more of the related listed items.

[0016] The terms "first," "second," "third," etc., may be used herein to describe various elements, components, regions, layers, and / or sections. These elements, components, regions, layers, and / or sections should not be limited by these terms. These terms may only be used to distinguish one element, component, region, layer, or section from another region, layer, or section. Terms such as "first," "second," and other numerical terms do not imply a sequence or order unless the context clearly indicates otherwise.Thus, a first element, component, region, layer, or section discussed below could be referred to as a second element, component, region, layer, or section without departing from the teachings of the example configurations.

[0017] For the purposes of this application, which includes the definitions below, the term "module" may be replaced by the term "circuit." The term "module" may refer to, be part of, or include: an application-specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field-programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; a memory (shared, dedicated, or group) that stores code executed by the processor; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.

[0018] The term "code" as used above can include software, firmware and / or microcode and can refer to programs, routines, functions, classes and / or objects. The term "shared processor" includes a single processor that executes code from multiple modules in part or in whole. The term "group processor" includes a processor that, in combination with additional processors, executes code from one or more modules in part or in whole. The term "shared memory" includes a single memory that stores code from multiple modules in part or in whole. The term "group memory" includes memory that, in combination with additional memory, stores code from one or more modules in part or in whole. The term "memory" is a subset of the term "computer-readable medium".The term "computer-readable medium" does not encompass transitory electrical or electromagnetic signals propagating through a medium and can therefore be considered tangible and non-transitory. Non-limiting examples of non-transitory storage include tangible, computer-readable medium, including non-volatile memory, magnetic storage, and optical storage.

[0019] The devices and methods described in this application may be implemented partially or entirely by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions stored on at least one non-transitory, tangible, computer-readable medium. The computer programs may also include and / or be based on stored data.

[0020] A software application (i.e., a software resource) may refer to computer software that causes a computing device to perform a task. In some examples, a software application may be referred to as an "application," "app," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0021] Non-transitory memory may be physical devices used to store programs (e.g., sequences of instructions) or data (e.g., information about program state) on a temporary or permanent basis for use by a computing device. Non-transitory memory may be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, among others, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electronically erasable programmable read-only memory (EEPROM) (e.g., typically used for firmware such as boot programs). Examples of volatile memory include, among others, random-access memory (RAM), dynamic random-access memory (DRAM), static random-access memory (SRAM), phase-change memory (PCM), and floppy disks or tapes.

[0022] These computer programs (also referred to as programs, software, software applications, or code) comprise machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented language and / or assembly / machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., magnetic disks, optical disks, memories, programmable logic devices (PLDs)) used to deliver machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0023] Various implementations of the systems and techniques described herein may be embodied in digital electronic and / or optical circuits, integrated circuits, purpose-built ASICs (application-specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementation in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be a special-purpose or general-purpose processor, coupled to receive data and instructions from and communicate data and instructions to a memory system, at least one input device, and at least one output device.

[0024] The processes and logic flows described in this patent may be performed by one or more programmable processors, also referred to as data processing hardware, that execute one or more computer programs to perform functions by processing input data and generating output. The processes and logic flows may also be performed by special-purpose logic circuits, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). Processors suitable for executing a computer program include, for example, both general-purpose and special-purpose microprocessors and one or more processors of any type of digital computer. Generally, a processor receives instructions and data from read-only memory or random-access memory, or both.The essential elements of a computer are a processor for executing instructions, and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to, one or more mass storage devices for storing data, such as magnetic, magneto-optical, or optical disks, or to receive or transfer data to or from them, or both. However, a computer need not include these devices. Computer-readable media suitable for storing computer program instructions and data includes all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.The processor and memory can be supplemented by or integrated into special logic circuits.

[0025] To enable interaction with a user, one or more aspects of the disclosure may be implemented on a computer having a display device, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or a touch screen for displaying information to the user, and optionally a keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices may also be used to interact with a user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the user's input may be received in any form, including auditory, voice, or tactile input.In addition, a computer may interact with a user by sending and receiving documents to and from a device used by the user, for example, by sending web pages to a web browser on a user's client device in response to documents requested by the web browser.

[0026] With reference to Fig. 1-9, a battery monitoring system 100 for a vehicle 10 includes a vehicle processor 200 in communication with a user device 300. The monitoring system 100 may also include a server 400, described in more detail below, that is communicatively coupled to one or both the vehicle processor 200 and the user device 300. The vehicle 10, described below, is considered an electric vehicle (EV) with autonomous or semi-autonomous capabilities. Additionally or alternatively, the vehicle 10 may be a hybrid vehicle, incorporating components and capabilities of both an electric vehicle and an internal combustion engine (ICE) vehicle. Accordingly, the vehicle 10 is equipped with a battery 12 to, at least in part, provide propulsion assistance for the vehicle 10. The vehicle processor 200 stores the battery data 202 of the battery 12 of the vehicle 10.

[0027] The battery data 202 includes a battery capacity 204 and a battery range 206 of the battery 12. It is also conceivable that the battery data 202 also includes a battery efficiency 208. However, in some examples, the battery efficiency 208 may be predicted or otherwise determined by the user device 300, as described below. The battery capacity 204 generally refers to the operating capacity of the battery 12, while the battery range 206 refers to an available distance that can be covered based on the current battery capacity 204. Thus, the vehicle processor 200 may use the battery capacity 204 to provide information about the battery range 206. Both the battery capacity 204 and the battery range 206 are included together as part of the battery data 202.For example, the vehicle processor 200 may communicate the battery capacity 204 and the battery range 206 to the user device 300 in the form of the battery data 202.

[0028] Battery efficiency 208 refers to the operating efficiency of battery 12. The efficiency of battery 12 may be affected by various external factors, including, but not limited to, weather, traffic patterns, road conditions, and driving patterns. Battery efficiency 208 may be determined, at least in part, by a change in battery capacity 204 and battery range 206 during operation of vehicle 10. It is conceivable that battery efficiency 208 may change during operation of vehicle 10, such that battery efficiency 208 may increase and decrease depending on the various external factors.

[0029] With reference to Fig. 1-3, the vehicle processor 200 may also be configured to control and / or monitor the environment within an interior 14 of the vehicle 10. For example, the vehicle processor 200 may include an environmental controller 210, which may be configured to collect environmental data 212 from the interior 14. The environmental controllers 210 are configured to adjust a cooling and heating system of the vehicle 10. The environmental controllers 210 may also include comfort settings within the vehicle 10, such as seat heating and / or massage functions. The environmental data 212 may include selected temperatures, fan speeds, seat heating or massage settings, and / or the selection of directional output. As described herein, the vehicle processor 200 transmits the environmental data 212 in conjunction with the battery data 202 to the user device 300 as part of the battery monitoring system 100.

[0030] The vehicle processor 200 may further collect operational data 214 from the vehicle 10, which may include functional operations. The operational data 214 may include, for example, the activation of windshield wipers, windows, sunshades, sunroof, and / or mirrors of the vehicle 10. The operational data 214 may be used by the vehicle processor 200 to inform and update the battery data 202 so that some of the functional operations may utilize the battery 12 and potentially deplete the battery capacity 204. Thus, the vehicle processor 200 may collect the environmental data 212 and the operational data 214 to adjust the battery data 202 communicated to the user device 300. In addition, the vehicle processor 200 may collect driving data 216, which may be communicated to the user device 300.The driving data 216 may provide information about the battery efficiency 208 so that the user device 300 can compare the battery data 202 with the driving data 216.

[0031] With reference to Fig. 2-5, the user device 300 includes a display 302 and data processing hardware 304 configured to execute a battery monitoring application 306. The battery monitoring application 306 is configured to present the battery data 202 received from the vehicle processor 200 to an occupant of the vehicle 10. For example, the battery monitoring application 306 may display the current battery capacity 204 and the current battery range 206 on the display 302 of the user device 300. It is also contemplated that, as in Fig. 3 illustrates that the occupant or user can adjust the environmental controls 210 via the battery monitoring application 306 and that the battery monitoring application 306 can display the driving data 216.

[0032] The user device 300 is also configured with a weather application 308 and a navigation application 310, each communicatively coupled to the battery monitoring application 306. The weather application 308 includes weather data 312 including the predicted weather patterns 314 described below. The weather data 312 may include location weather data 316 based on the current position of the vehicle 10 and route weather data 318. The battery monitoring application 306 is configured to utilize the weather data 312 in combination with the battery data 202 to determine various battery forecasts 320 of the battery 12, which are described below. Additionally or alternatively, the battery monitoring application 306 utilizes the battery data 202 and the weather data 312 to present the user with battery efficiency options 322 based on the battery data 202 and the weather data 312.

[0033] The navigation application 310 is configured to provide a route 324 and collect navigation data 326. The navigation application 310 may, for example, include a map displaying various aspects of a region, including, but not limited to, terrain, road gradient, and traffic conditions. The navigation application 310 and the weather application 308 may be configured to exchange data. For example, the weather application 308 may receive the route 324 from the navigation application 310 to collect the route weather data 318 along the planned route 324. The weather application 308 may then send the weather data 312 corresponding to the route 324 to the navigation application 310 and / or the battery monitoring application 306. As described herein, both the weather application 308 and the navigation application 310 are configured to communicate and exchange data with the battery monitoring application 306.

[0034] With further reference to Fig. 2-5, the server 400 is configured as a network and / or cloud-based system that communicates with the vehicle processor 200 and / or the user device 300. The server 400 is also configured to communicate with third-party processors 500 to collect third-party data 502. The third-party processors 500 may include, for example, but are not limited to, vehicle processors along route 324 input via the user device 300. Additionally or alternatively, the third-party processors 500 may include third-party user devices in vehicles along route 320. In general, it is contemplated that the third-party data 502 may include battery efficiency data 504 of the third-party processors 500. The battery efficiency data 504 is configured to communicate to the server 400 third-party battery efficiency for each respective vehicle battery traveling along route 324.In some examples, server 400 may also determine battery inefficiencies 506 along route 324, which may be communicated to battery monitoring application 306. While battery monitoring application 306 of user device 300 is described herein as evaluating battery efficiency data 504, in some examples, server 400 may also evaluate battery efficiency data 504.

[0035] The battery monitoring application 306 may determine aspects of the route 324 that may impact the efficiency of the third-party batteries based on the battery efficiency data 504. In some cases, the battery monitoring application 306 may determine battery loss factors 328 along the route 324 based on the battery efficiency data 504. The battery loss factors 328 may include weather conditions 330, including, but not limited to, temperature, wind, rain, humidity, snow, and / or ice along the route 324. For example, the battery monitoring application 306 may compare a position of the third-party processors 500 along the route 324 with the weather data 312 from the weather application 308.Based on the weather conditions 330 at the location and the battery efficiency data 504 along the route 324, the battery loss factors 328 may be predicted or otherwise determined by the battery monitoring application 306 using the weather data 312.

[0036] Weather conditions 330 may impact the efficiency of battery 12 by reducing traction, increasing drag of vehicle 10, or reducing the operating efficiency of battery 12. For example, battery 12 may be affected by temperatures, such that battery 12 may be less efficient in extremely hot or cold temperatures, ultimately impacting battery range 206 of vehicle 10. In other examples, strong headwinds may increase drag of vehicle 10 and cause battery 12 to consume additional battery capacity 204 to maintain the set speed of vehicle 10. The increased drag may decrease overall battery efficiency 208 and, therefore, battery range 206 due to battery 12 compensating against the potential headwind.In further examples, rain may increase aerodynamic drag on vehicle 10 and decrease battery efficiency 208, while the use of windshield wipers and other electrical components, recorded as operational data 214, may also decrease battery efficiency 208 of battery 12. Other weather conditions 330, such as high humidity and / or snow or ice, may further decrease the overall efficiency 208 of battery 12. The effects of various weather conditions 330 may be evaluated by battery monitoring application 306 by comparing weather data 312 with battery efficiency data 506.

[0037] With continued reference to Fig. 2-5, the battery loss factors 328 may also be determined based on the navigation data 326. The navigation data 326 is used to determine the battery loss factors 328. In determining the battery loss factors 328, the battery monitoring application 306 may compare the navigation data 326 and one or more of the battery efficiency data 504 and / or the battery inefficiencies 506 collected by the third-party processors 500, the traffic data 332, and / or the information obtained from the navigation application 310. For example, the navigation application 310 may detect a slow traffic pattern and communicate the slow traffic pattern as traffic data 332. The battery monitoring application 306 may update the route 324 based in part on the battery loss factors 328.As described below, the battery monitoring application 306 may receive user input corresponding to a route 324 entered into the navigation application 310, and the battery monitoring application 306 may determine an efficient route 334 based on the battery loss factors 328, the weather data 312, the traffic data 332, and the efficiency data 504.

[0038] With reference now to Fig. 2 and 4-7 illustrate an example navigation application 310 having an input route 324. In some examples, the navigation application 310 may communicate the input route 324 to the battery monitoring application 306. The battery monitoring application 306, as mentioned above, is configured to compare the input route 324 with the battery efficiency data 504, the weather data 312, the navigation data 326, and the traffic data 332 to evaluate the efficiency of the input route 324.

[0039] In some cases, the battery monitoring application 306 may determine that the input route 324 includes inefficiencies and may suggest the efficient route 334 as an alternative route. The alternative route 334 may be referred to as the efficient route 334 because the alternative route 334 is determined to be more efficient than the input route 324. The efficiency is determined by the battery monitoring application 306 based on the optimized operation of the battery 12 along a route such that the battery loss factors 328 are minimal. For example, the server 400 may determine one or more battery inefficiencies 506 based on the third-party data 502 received from the third-party processors 500 along the input route 324 and communicate the battery inefficiencies 506 to the battery monitoring application 306. In response to the determined battery inefficiencies 506, the battery monitoring application 306 may determine the efficient route 334.Thus, the battery monitoring application 306 may determine a first route 324 and a second route 324 and, in response to the efficiency data 504, present either the first route 324 or the second route 324 as an efficiency route 334.

[0040] With further reference to Fig. 2 and 4-7, the battery monitoring application 306 evaluates the weather data 312 received from the weather application 308 when determining the efficiency route 334. In some examples, the battery monitoring application 306 is configured to determine a battery efficiency option 322 in response to the weather data 312. The battery efficiency option 322 may, for example, include an alternative departure time and / or an alternative travel time to optimize an outside temperature during the trip. The battery monitoring application 306 may determine from the weather data 312 that an entered departure time may decrease the total capacity 204 of the battery and, therefore, the battery range 206. In response, the battery monitoring application 306 may recommend an alternative departure time and / or an alternative travel time that is during a time of day when the temperature is optimal for the trip.In other examples, the battery monitoring application 306 may determine the weather conditions 330 along the input route 324 that may lead to inefficiencies along the route 324 that may be avoided by the efficient route 334. Thus, the battery monitoring application 306 may recommend the efficient route 334 to maximize battery efficiency, for example, based on the weather data 312.

[0041] For example, the battery monitoring application 306 evaluates the route weather data 318 for the input route 324 and compares the route weather data 318 to the predicted weather patterns 314 in the surrounding area. The battery monitoring application 306 may determine the alternate route 334 as a route that avoids the weather conditions 330 along the input route 324 and thus avoids potential battery loss factors 328. In some examples, the battery monitoring application 306 may display an icon or otherwise indicate the weather conditions associated with the respective route 324, 334 to provide a visual indication of the weather conditions 330. The icon may assist the user in visualizing the differences between the routes 324, 334 in the event that the weather data 312 informs the alternate route 334.

[0042] The battery monitoring application 306 is also configured to evaluate the navigation data 326 received from the navigation application 310 when evaluating the input route 324. For example, the traffic data 332 along the input route 324 may indicate that traffic along the route 324 may lead to inefficiencies when traveling the route 324. In some examples, the navigation data 326 may include terrain 336 along the route 324 that may impact the battery efficiency 208 while traveling. For example, the terrain 336 may include a steep incline that consumes a significant percentage of the battery capacity 204. Thus, the battery monitoring application 306 may determine the alternate route 334 to maximize the battery capacity 204 and the battery range 206. In the example of a steep incline, the alternate route 334 may avoid the steep incline and utilize flatter terrain 336.

[0043] Once the battery monitoring application 306 has determined the alternative efficiency route 334, the battery monitoring application 306 may issue a message 350 indicating the availability of the efficiency route 334. It is also conceivable that the battery monitoring application 306 may not determine the efficiency route 334 until the vehicle 10 is already traveling on the input route 324. In this example, the battery monitoring application 306 issues the message 350, which alerts the user to the availability of the efficiency route 334 and provides the option to switch to the efficiency route 334.

[0044] As the vehicle 10 travels along the route 324, 334, the battery monitoring application 306 continuously receives and monitors the driving data 216 from the vehicle processor 200. The driving data 216 includes driving patterns 218, including, but not limited to, speed and braking application. The battery monitoring application 306 may track and monitor the driving patterns 218 over a predetermined period of time. The battery monitoring application 306 may present efficient driving patterns 352. The efficient driving patterns 352 may, for example, include recommendations for increased battery efficiency based on the driving patterns 350. Thus, the battery monitoring application 306 may present various battery efficiency options 322 that include one or more of the alternative travel time, the alternative route 334, and the efficient driving patterns 352.

[0045] Each of the battery efficiency options 322 may be determined or otherwise based on the battery data 202, the weather data 312, and the navigation data 326. In addition to presenting recommendations for increasing battery efficiency 208, the battery monitoring application 306 may also display the battery range 206 along the route 324. Thus, the user may continuously monitor the battery range 206 during operation of the vehicle 10 and may adjust the driving patterns 218 in response to changes in the battery range 206. It is contemplated that the battery monitoring application 306 may continuously and / or periodically update the battery range 206 to reflect real-time data from the battery 202.

[0046] With reference now to Fig. 1-8 is an exemplary flowchart of the operation of the battery monitoring system 100 in Fig. 8 and Fig. 9. In a first step, at 800, the user enters a destination into the navigation application 310. Additionally or alternatively, the battery monitoring system 100 may detect the beginning of a route 324 based on communication with the vehicle processor 200 and the navigation application 310. The battery monitoring system 100 checks the weather conditions 330 along the route 324 at 802, and the battery monitoring system 100 determines various inefficiency or battery loss factors 328 along the route 324 at 804 based on, but not limited to, the weather data 312, the navigation data 326, the third-party data 502, and the battery data 202. If no inefficiencies are detected, the battery monitoring system 100 returns to step 804. If inefficiencies are detected, the battery monitoring system 100 searches for an alternative route 334 and / or alternative departure or travel times at 806.

[0047] If an alternative route 334 is determined, the battery monitoring application 306 evaluates the weather data 312 at 808 to determine predicted weather patterns 314 that may increase the battery efficiency 208. If no predicted weather patterns 314 are detected, the battery monitoring system 100 returns to step 804. If efficiency can be increased based on the alternative route 334 and the predicted weather patterns 314, the battery monitoring application 306 may suggest the alternative route 334, including a new departure time, at 810. It is conceivable that, when presenting the alternative route 334, the battery monitoring application 306 may also display a new estimated arrival time and the efficiency savings associated with selecting the alternative route 334.

[0048] Fig. 9 illustrates a flowchart of the battery monitoring system 100 determining an alternate route 334 based on the navigation data 326. The navigation application 310 determines a route 324 of the vehicle 10 at 900. The route 324 may be entered by the user or determined based on the operation of the vehicle 10. The battery monitoring system 100 determines the route weather data 318 at 902 to determine the efficiency or battery loss factors 328 at 904. If battery loss factors 328 are determined, the battery monitoring application 306 determines an alternate route 334 with a similar arrival time at 906. If no battery loss factors 328 are determined, the battery monitoring application 306 determines whether the route 324 has ended at 908. If the route has ended, the battery monitoring application 306 may end the evaluation process.If the route is not completed, the system 100 returns to step 902.

[0049] The battery monitoring application 306 determines at 910 whether an alternate route 334 has been determined from step 906, and if the alternate route 334 is available, then at 912 the battery monitoring application 306 determines whether there is new route weather data 318 that can be used to increase the efficiency of the alternate route 334. If higher efficiencies are available, the battery monitoring application 306 suggests a new efficient route 334 to the user at 914. The new efficient route 334 may also display a new estimated time of arrival as well as the efficiency savings associated with selecting the alternate route 334.

[0050] With further reference to Fig.1-9, the battery monitoring application 306 is configured to receive the weather data 312 from the weather application 308, the navigation data 326 from the navigation application 310, and the third-party data 502 from the server 400. The third-party data 502 from the server 400 may inform or supplement the navigation data 326 and the route weather data 318. For example, the route weather data 318 may include the predicted weather patterns 314 along the route 324 and may include active route weather data 318. The battery monitoring application 306 may use the active route weather data 318 in combination with the predicted weather patterns 314 to potentially adjust, change, or otherwise update the route 324. It is conceivable that the weather data 312 together may inform the efficiency of the battery 12 along the original route 324 or otherwise influence the efficiency of the battery 12.It is also conceivable that the navigation data 326 can provide information about the efficiency of the battery 12 in a similar manner.

[0051] The battery monitoring application 306 may thus present the battery efficiency options 322 on the display 302. The battery efficiency options 322 may include, for example, an alternative departure time and / or an alternative route 334, each of which may be configured to avoid the traffic patterns 338 and / or weather conditions 330 determined by the weather data 312. Thus, the battery monitoring system 100 may advantageously support monitoring the battery efficiency 208 relative to external factors. By comparing the weather data 312, the navigation data 326, and the third-party data 502, the battery monitoring application 306 may determine efficiency savings in various ways. In some examples, the battery monitoring application 306 may recommend, among other things, adjusting driving behavior 218, selecting alternative routes 334 to avoid battery dissipation factors 328, and / or adjusting driving time.

[0052] A number of implementations have been described. However, it should be understood that various changes may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are also within the scope of the following claims.

[0053] The foregoing description is for purposes of illustration and description only. It is not intended to be exhaustive or limiting of the disclosure. Individual elements or features of a particular arrangement are generally not limited to that particular arrangement, but are interchangeable and may be used in a selected arrangement even if not specifically shown or described. They may also be modified in many ways. Such modifications are not to be regarded as a departure from the disclosure, and all such changes are intended to be included within the scope of the disclosure.

Claims

[1] Battery monitoring system, comprising: a vehicle processor that stores battery data; and a user device communicatively coupled to the vehicle processor and comprising data processing hardware storing a weather application, a navigation application, and a battery monitoring application configured to receive the battery data from the vehicle processor and weather data from the weather application, wherein the battery monitoring application is configured to present battery efficiency options to a user based on the battery data and the weather data. [2] The battery monitoring system of claim 1, wherein the battery efficiency options include one or more of an alternative travel time, an alternative route, and efficient driving patterns. [3] The battery monitoring system of claim 2, wherein the efficient driving patterns include recommendations for increased battery efficiency. [4] The battery monitoring system of claim 2, wherein the battery monitoring application is configured to determine the alternative route and the alternative travel time in response to navigation data from the navigation application. [5] The battery monitoring system of claim 4, wherein the battery monitoring application is configured to determine the battery efficiency options based on the battery data, the weather data, and the navigation data. [6] The battery monitoring system of claim 5, wherein the navigation data comprises a route and traffic data, and the battery monitoring application is configured to determine an efficiency of the route based on the weather data and / or the traffic data. [7] The battery monitoring system of claim 6, further comprising a server configured to detect third-party processors along the route and configured to communicate third-party efficiency data to the battery monitoring application. [8] The battery monitoring system of claim 7, wherein the server is communicatively coupled to the vehicle device and the user device and is configured to monitor battery efficiency data from one or more third-party processors, the server is configured to transmit the battery efficiency data to the user device, and the battery monitoring application is configured to present battery predictions to a user based on the battery data and the battery efficiency data. [9] The battery monitoring system of claim 8, wherein the server is configured to determine one or more battery inefficiencies from one or more third-party processors along the route. [10] The battery monitoring system of claim 9, wherein the battery monitoring application is configured to determine an alternative route in response to the one or more determined battery inefficiencies.

Images