Charging control system for vehicle

Abstract

A charging control system for a vehicle includes a user device including a display and data processing hardware in communication with the display and executing a charging application storing a charging profile, a vehicle profile, and saved charging options. The charging control system also includes a vehicle controller communicatively coupled to the user device via a network. The vehicle controller stores at least one of battery power, battery life, and battery capacity of the vehicle battery, and is configured to update a vehicle profile of the charging application and provide charging options on the display. When the charging application is executed on the data processing hardware, the charging options include at least one of a charging time, a charging location, and a battery capacity.

Description

[0001] introduction

[0002] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section and in aspects of the description that may not qualify as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art against the present disclosure. Technical Field

[0003] The present disclosure generally relates to a charging control system for a vehicle. Background Art

[0004] Vehicles utilize communication systems to transmit data and power to various devices. Many conventional vehicles are equipped with ports or sockets configured to provide power to devices, while some vehicles utilize wireless charging through magnetic sensors. In some conventional vehicle systems, a user device can be plugged into the vehicle and display various user interface applications on the vehicle's display. These user interface applications may include navigation, music, and messaging. Other conventional vehicles are equipped with a navigation system alone, and may also include a temperature sensor to detect the ambient temperature around the vehicle.

[0005] While conventional vehicles may include various applications for use in operation of the vehicle or in combination with various internal and external devices, conventional vehicles do not typically provide real-time monitoring of the vehicle battery during use of each application. Additionally, if the vehicle's battery remains in use and / or connected to a device after the vehicle is used, the conventional vehicle may warn the occupants via an audio signal, or may automatically shut down the vehicle battery without taking further action. Summary of the invention

[0006] In one configuration, a charging control system for a vehicle includes a user device including a display and data processing hardware in communication with the display and executing a charging application storing a charging profile (configuration file), a vehicle profile, and saved charging options. The charging control system also includes a vehicle controller communicatively coupled to the user device via a network. The vehicle controller stores at least one of a battery power, a battery life, and a battery capacity of a vehicle battery, and is configured to update the vehicle profile of the charging application and provide charging options on the display. When the charging application is executed on the data processing hardware, the charging options include at least one of a charging time, a charging location, and a battery capacity.

[0007] In some aspects, the data processing hardware may be configured to execute a charging protocol for the external device in response to a user input selecting one of the saved charging options. The user input may include a charging time, and the vehicle controller may be configured to provide the battery power of the vehicle battery in response to the user input and provide the battery capacity in response to the charging time. The data processing hardware may be configured to provide a notification on a display indicating that the battery life is at a minimum battery life, and is configured to display nearby charging stations for the vehicle. In some examples, the charging profile may store the charging time, and the vehicle controller may be configured to communicate the battery capacity to the data processing hardware via a network based on the charging time.

[0008] The battery capacity may indicate a minimum battery range (minimum battery mileage), and the vehicle controller may be configured to stop the charging time at the minimum battery range. In other examples, the data processing hardware may store a weather application that communicates with the charging application, and the data processing hardware may be configured to issue a notification to the user in response to data received from the weather application. The data processing hardware may be configured to charge the utility external device in response to a weather notification from the weather application.

[0009] In another configuration, the charging control system includes a user device including a display and data processing hardware in communication with the display. The data processing hardware stores a weather application and a charging application that, when executed on the data processing hardware, causes the data processing hardware to perform operations in response to user input corresponding to a charging protocol and weather data received from the weather application. The charging control system also includes a vehicle controller that stores a battery capacity of a vehicle battery and is configured to receive a signal from the data processing hardware and provide the battery capacity to the data processing hardware. The data processing hardware is configured to determine a charging threshold of the vehicle battery based on the battery capacity, and to adjust a charging time of the charging protocol in response to the received weather data and the charging threshold of the vehicle battery.

[0010] In some examples, the battery capacity may include a first battery capacity of a first vehicle battery and a second battery capacity of a second vehicle battery. The first battery capacity may be selectively coupled to the second battery capacity. The user device may store a navigation application, and the data processing hardware may be configured to calculate a route battery threshold based on the battery capacity, the charging protocol, the starting location, and the ending location. The data processing hardware may be configured to determine whether the ending location exceeds the route battery threshold. In some examples, the vehicle controller may be configured to prompt the data processing hardware with a battery rationing option based on the battery capacity with a minimum battery range. In some aspects, the vehicle includes a charging control system.

[0011] In another configuration, a charging control system for a vehicle includes a user device including a display and data processing hardware in communication with the display. The data processing hardware stores a weather application and a charging application that, when executed on the data processing hardware, causes the data processing hardware to perform an operation in response to receiving a user input corresponding to a charging protocol and receiving weather data from the weather application. The charging control system also includes a vehicle controller that stores a first battery capacity of a first vehicle battery and a second battery capacity of a second vehicle battery. The vehicle controller is configured to receive a signal from the data processing hardware and provide the first battery capacity and the second battery capacity to the data processing hardware. The data processing hardware is configured to adjust a charging time of a charging protocol based on one of the first battery capacity and the second battery capacity.

[0012] In some aspects, the vehicle controller may be configured to selectively draw from the second battery capacity to supplement the first battery capacity. The user input may include selecting a combined protocol stored by the charging application. The charging application may be configured to execute the combined protocol using the first battery capacity and the second battery capacity simultaneously. In some instances, the data processing hardware may be configured to prompt the user with the option of adjusting the charging protocol based on weather data received from the weather application. Optionally, the charging application may be configured to display the power consumption of at least one of the first battery capacity and the second battery capacity by at least one external device. The vehicle controller may be configured to redirect power from an unused power source to maximize at least one of the first battery capacity and the second battery capacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure.

[0014] Figure 1 is a perspective schematic diagram of a vehicle according to the present disclosure in communication with a user device;

[0015] Figure 2 is a schematic diagram of a user device with a charging application according to the present disclosure;

[0016] Figure 3 is a schematic diagram of a charging application displayed on a user device according to the present disclosure;

[0017] Figure 4 is a schematic diagram of a user device receiving weather notifications on a charging application of the present disclosure;

[0018] Figure 5 is a schematic diagram of a user device with a navigation application according to the present disclosure;

[0019] Figure 6is a schematic diagram of a user device with a notification of a charging profile according to the present disclosure;

[0020] Figure 7 is a schematic diagram of a charging application of the present disclosure in communication with a first vehicle controller and a second vehicle controller;

[0021] Figure 8 is a schematic diagram of a first vehicle and a second vehicle electrically coupled to a house according to the present disclosure;

[0022] Fig. 9 is an example flow chart of a charging control system according to the present disclosure;

[0023] Fig.10 yes Fig. 9 An example flow chart of a charging control system; and

[0024] Fig.11 yes Fig. 9 and Fig.10 An example flow chart of a charging control system.

[0025] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0026] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those of ordinary skill in the art 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 as limiting the scope of the present disclosure.

[0027] The terms used herein are only used for the purpose of describing specific exemplary configurations and are not intended to be limiting. As used herein, the singular articles "a", "an" and "the" may also be intended to include plural forms unless the context clearly indicates otherwise. The terms "comprises", "comprising", "including" and "having" are inclusive and therefore specify the presence of features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts and / or groups thereof. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or shown, unless specifically identified as an execution order. Additional or alternative steps may be adopted.

[0028] When an element or layer is referred to as being "on another element or layer," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, directly engaged with, connected to, attached to, or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on another element or layer," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there may be no intermediate elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more associated listed items.

[0029] The terms first, second, third, etc. can be used in this article to describe various elements, components, regions, layers and / or parts. These elements, components, regions, layers and / or parts should not be limited by these terms. These terms can only be used to distinguish an element, component, region, layer or part from another region, layer or part. Unless the context clearly indicates, terms such as "first", "second" and other numerical terms do not imply order or sequence. Therefore, without departing from the teaching of the example configuration, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part.

[0030] In this application, including 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 a chip.

[0031] The term code as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class and / or an object. The term shared processor encompasses a single processor that executes some or all codes from multiple modules. The term group processor encompasses a processor that executes some or all codes from one or more modules in combination with an additional processor. The term shared memory includes a single memory that stores some or all codes from multiple modules. The term group memory includes a memory that stores some or all codes from one or more modules in combination with an additional memory. The term memory may be a subset of the term computer-readable medium. The term computer-readable medium does not include transient electrical signals and electromagnetic signals propagated through the medium, and therefore can be considered to be tangible and non-transient memory. Non-limiting examples of non-temporary memory include tangible computer-readable media, which include non-volatile memory, magnetic storage, and optical storage.

[0032] The apparatus and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include and / or rely on stored data.

[0033] A software application (i.e., software resource) may refer to computer software that enables a computing device to perform tasks. 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.

[0034] Non-transitory memory may be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) 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, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.

[0035] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. 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., disk, optical disk, memory, programmable logic device (PLD)) for providing 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 for providing machine instructions and / or data to a programmable processor.

[0036] Various implementations of the systems and techniques described herein can be realized in digital electronic and / or optical circuitry, integrated circuits, specially designed 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 that includes at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from and send data and instructions to a storage system, at least one input device, and at least one output device.

[0037] The processes and logic flows described in this specification can 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 operating on input data and generating outputs. The processes and logic flows can also be performed by dedicated logic circuits (e.g., FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits)). As an example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably coupled to receive data from it or transmit data to it or both. However, a computer does not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory 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 may be supplemented by, or incorporated in, special purpose logic circuitry.

[0038] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the 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 input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0039] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0040] refer to Figure 1-3, the charging control system 100 includes a user device 200 and connects the user device 200 with a vehicle controller 300 of the vehicle 10 via a network 400. The charging control system 100 is configured to receive user input 102 from a user interacting with the user device 200. As described in more detail below, the user device 200 is communicatively coupled to the vehicle controller 300 and is configured with a charging application 202 to communicate with the battery 12 of the vehicle 10. For example, the charging application 202 may send a signal 104 to the vehicle controller 300 in response to the user input 102 to establish communication between the user device 200 and the vehicle controller 300, as described herein.

[0041] In some aspects of the present disclosure, vehicle 10 is an electric vehicle (EV) having autonomous or semi-autonomous capabilities. Additionally or alternatively, vehicle 10 may be a hybrid vehicle combining EV and internal combustion engine (ICE) components and capabilities.

[0042] The vehicle controller 300 can control and monitor the vehicle battery 12. For example, the vehicle controller 300 includes a memory 302 that stores a battery life 304, a charging log 306, and a battery capacity 308 of the vehicle battery 12. The battery life 304 corresponds to the current operational life of the battery 12, which in some aspects can be represented by the duration of the remaining operational life of the battery 12. The vehicle controller 300 is configured to take regular, repeated readings of the vehicle battery 12 to maintain a representative battery life 304. As will be described in detail below, the vehicle controller 304 uses the representative battery life 304 when communicating with the charging application 202.

[0043] In determining the battery life 304, the vehicle controller 300 evaluates the battery power 310, which can be expressed as a percentage value. The controller 300 can convert the percentage value of the battery power 310 into a time value expressed as the battery life 304, which helps determine the battery capacity 308 with respect to charging other devices. The battery capacity 308 can be a reflection of both the battery power 310 and the battery life 304. For example, the battery capacity 308 can reflect the potential charging capability based on the expected battery life 304 and the current battery power 310.

[0044] Still reference Figure 1-3, the memory 302 may also store a charging threshold 312 that defines the maximum capacity of potential charging options based on the battery capacity 308. For example, the vehicle controller 300 may communicate the charging threshold 312 with the charging application 202 of the user device 200, and the charging application 202 may compare the charging threshold 312 with the battery capacity 308 to ultimately present the charging options to the user. In some aspects, the charging application 202 may present a first option to charge multiple devices in a short period of time and a second option to charge priority devices in a longer period of time compared to the first option. Although the battery capacity 308 depends on the battery life 304 and the battery power 310, it is also expected that the surrounding external environment may affect the battery capacity 308, as described below.

[0045] The vehicle controller 300 is communicatively coupled to the user device 200, which includes a display 204 and data processing hardware 206. The data processing hardware 206 is configured to execute the charging application 202, and also request and execute the charging protocol 208 in response to the user input 102. As further described below, the charging protocol 208 is executed according to the charging application 202, so that the information and data classified in the charging application 202 can be used by the data processing hardware 206 when executing the charging protocol 208. In other words, the charging application 202 can present a user-facing interface through which the signal 104 is sent based on the user input 102 to initiate and execute the selected charging protocol 208.

[0046] The charging application 202 is configured to charge the external device 500 using the vehicle battery 12. As further described below, the charging application 202 is a user-facing interface that receives user input 102 to set and adjust the charging protocol 208 when the charging protocol 208 is associated with the selected external device 500. For example, the charging protocol 208 can be configured to charge the selected external device to a predetermined battery percentage, so that once the external device 500 reaches the predetermined percentage, the charging application 202 can stop the charging protocol 208. Additionally or alternatively, the charging application 202 can stop the charging protocol 208 in order to prioritize the battery capacity 308 of the vehicle battery 12. In some aspects, the charging application 202 can apply prioritization to various external devices 500, so that some external devices 500 can be prioritized over other external devices. For example, the accessory external device 500a can have a lower priority than the utility external device 500b.

[0047] The prioritization protocol that may be executed by the charging application 202 may be considered a rationing option based on conserving battery capacity 308 as a result of the prioritization performed. For example, the vehicle controller 300 may be configured to provide a battery rationing option of a minimum battery range 308a to the data processing hardware 206 based on the current battery capacity 308. Thus, the charging application 202 may be configured to charge various external devices using the vehicle battery 12, and may actively monitor energy consumption in conjunction with the vehicle controller 300 to prioritize the vehicle battery 12 for vehicle drivability.

[0048] Still reference Figure 1-3 , charging application 202 includes charging profile 210 and vehicle profile 212. Charging profile 210 may include user preferences regarding device 500 that may be used with charging application 202. Charging profile 210 may also include information regarding a preferred charging mode and home settings corresponding to the user's home.

[0049] The charging application 202 also includes a vehicle profile 212 that includes vehicle identification information 212a and displays information received from the vehicle controller 300. It is generally contemplated that the vehicle profile 212 can be established by a user manually entering the vehicle identification information 212a and / or by communication with the vehicle controller 300. In particular, the vehicle controller 300 sends battery data to the user device 200 via the network 400. For example, the vehicle profile 212 can present the user with a battery life 304, a battery power 310, and a battery capacity 308, each obtained from the vehicle controller 300, to assist in selecting a charging protocol 208. In some aspects, the presented battery life 304 can include a minimum battery life 304a, such that the charging protocol 208 can be set to warn the user via a notification 214 when the battery life 304 of the vehicle 10 approaches the minimum battery life 304a. For example, data processing hardware 206 is configured to provide notification 214 on display 204 of user device 200 indicating that battery life 304 is at minimum battery life 304 a and to display nearby charging stations 502 for vehicle 10 .

[0050] The minimum battery life 304a is defined as the minimum battery capacity at which the vehicle 10 can operate between locations. The user can adjust or set the minimum battery life 304a to adjust or adapt to specific trip information. For example, the user can adjust the minimum battery life 304a to a larger value corresponding to a larger value of the battery life 304 to accommodate the return trip of the vehicle 10 after using the charging application 202. Additionally or alternatively, the charging application 202 can be configured to communicate with the vehicle controller 300 to automatically adapt and adjust the minimum battery life 304a based on the location of the vehicle 10 relative to the nearby charging station 502 or the user's home location.

[0051] Further references Figure 1-3 , the vehicle profile 212 also displays information related to the charging log 306, so that the vehicle profile 212 can present to the user the last full charge 306a of the vehicle 10. The data obtained from the charging log 306 can be utilized by the data processing hardware 206 to inform the user of the minimum battery life 304a in an alternative form. For example, the data processing hardware 206 can evaluate that the last full charge 306a occurred before the trip was set off, and can evaluate the data from the charging log 306 to determine whether any additional charging occurred between the last full charge 306a and the instantaneous battery capacity 308.

[0052] Based on the data from the charging log 306, the data processing hardware 206 can determine the minimum battery life 304a before recommending that the user stop the charging protocol 208 to reserve sufficient battery life 304 for the return trip. The data processing hardware 206 can alternatively present the user with the option of a nearby charging station 502, which can extend the charging protocol 208 based on the location of the vehicle 10. The notification 214 can also include information related to the direction to the nearest charging station 502, as described below. Therefore, the user can choose via the user input 102 whether to continue the charging protocol 208 until the minimum battery range 308a is met and then continue to the nearest charging station 502, or to stop the charging protocol 208 at an earlier time period to reserve sufficient battery power (battery power) 310 for the return trip.

[0053] Additionally or alternatively, the notification 214 may include information regarding the minimum range 308a of the battery 12 based on the battery capacity 308. Thus, the charging protocol 208 may be adjusted based on the minimum battery life 304a and / or the minimum range 308a of the battery 12 so that the user may selectively preserve the battery capacity 308 for the return trip after executing the charging protocol 208.

[0054] Still reference Figure 1-3, the charging application 202 also includes saved charging options 218. The saved charging options 218 may include, but are not limited to, device profiles 220 and customized profiles 222. For example, the device profile 220 may include various external devices 500 compatible with the charging application 202, such as accessory external devices (i.e., mobile devices) 500a and utility external devices (i.e., home generators) 500b. The user may selectively add and remove external devices 500 from the charging application 202, and may select which external device 500 to charge via the charging protocol 208. For example, the user may add or remove external devices 500 in the device profile 220, and may add or remove external devices in the customized profile 222. Each device profile 220 may have specific settings that may be added to the customized profile 222, and each device profile 220 may have a customized charging time 222a, as described below. Therefore, the user may adjust the charging settings of one of the external devices 500 from the customized profile 222 in the saved charging options 218.

[0055] The custom profile 222 can be configured for various events and can include options related to the charging time 222a and the device selection 222b. The user can adjust the charging time 222a for the duration of the event, or can select a predetermined time period. Optionally, the data processing hardware 206 can determine the charging time 222a that will result in a full charge of the selected device 500. In this example, the data processing hardware 206 can set the charging time 222a to be completed when the selected device 500 is fully charged, and once the selected device 500 is fully charged, the charging protocol 208 can be stopped. The charging time 222a can be selected for each device 500 available from the device selection 222b, so that the data processing hardware 206 can execute a separate charging protocol for each device 500.

[0056] The device selection 222b may include an external device 500 saved in the saved charging options 218 of the charging application 202. In some aspects, the charging application 202 may be configured to detect external devices 500 in the surrounding area, and the detected external devices 500 may be presented to the user as part of the device selection 222b. The user may save the detected external device 500 to the device profile 220 for future use, or may choose to forget the detected external device 500 before completing the charging protocol 208. It is also contemplated that the charging protocol 208 may be configured with a power consumption 208a indicating the corresponding power consumption 208a of each external device 500. Thus, the user can track the various external devices 500 used with the charging application 202 to determine how much energy each external device uses.

[0057] Reference now Figures 2 to 5, the charging application 202 may present a notification 214 to the user in response to the selected charging time 222a when the selected charging time 222a approaches the battery capacity 308 of the vehicle battery 12. As generally mentioned above, the data processing hardware 206 is configured to determine the minimum battery range 308a based on the battery capacity 308 and the charging protocol 208 (including the selected charging time 222a). The charging application 202 may present the user with the option of continuing with the selected charging time 222a or adjusting the selected charging time 222a to maximize the battery capacity 308.

[0058] The user device 200 may also be configured with a weather application 240 communicatively coupled to the charging application 202 to provide weather data 242 that may affect or otherwise influence the charging protocol 208 of the charging application 202. The data processing hardware 206 may monitor the ambient temperature at the location of the vehicle 10 during the charging protocol 208. In some examples, weather may change the output of the vehicle battery 12 such that extreme temperatures may change the battery power 310, and ultimately the battery capacity 308. Thus, the charging application 202 may present options to adjust the charging protocol 208 in response to weather patterns detected by the weather application 240. Figure 4 As shown, weather data 242 is shown as notification 214, which presents an option to adjust the charging settings of charging protocol 208 based on the detected maximum temperature. In other words, data processing hardware 206 is configured to issue notification 214 in response to weather data 242 received from weather application 240. In other examples, weather data 242 may relate to reduced temperatures, rain, snow, hail, or other weather patterns that may affect battery power 310 of vehicle 10. In some aspects, data processing hardware 206 may adjust charging time 222a of charging protocol 208 in response to received weather data 242 and charging threshold 312 of vehicle battery 12.

[0059] While the user can adjust the charging protocol 208, it is also contemplated that the user can optionally ignore the weather notification 214 and proceed with the preselected settings. The data processing hardware 206 can execute the charging protocol 208 and present a later notification 214 that the vehicle battery 12 is approaching the minimum battery life 304a or the minimum battery range 308a, as described above. It is generally contemplated that the user can selectively adjust the autonomous functionality of the charging application 202 via the data processing hardware 206 to adjust the setting preferences for automatically or manually adjusting the charging protocol 208, optionally in response to weather patterns detected by the weather application 240.

[0060] Still reference Figure 2-5, the user device 200 may also include a navigation application 250. The navigation application 250 may also be communicatively coupled to the charging application 202 and provide information about the destination route 252, the route battery threshold 254, and nearby charging stations 502. The data processing hardware 206 may utilize the navigation application 250 in conjunction with data received from the vehicle controller 300 to determine the route battery threshold 254 based on the current battery capacity 308 and the destination route 252. In response to the determined route battery threshold 254, the data processing hardware 206 may update the charging application 202 to reflect the new minimum battery range 308a.

[0061] In some examples, the route battery threshold 254 may be interchangeable with the minimum battery range 308a. In other examples, the minimum battery range 308a may be different from the route battery threshold 254, where the route battery threshold 254 is determined based on a specific route input into the navigation application 250 by the user. Thus, while the minimum battery range 308a may reflect a broad range of distances that the vehicle 10 may travel following the charging protocol 208, the route battery threshold 254 may reflect a threshold for the battery capacity 308 based on a specific route input. For example, the minimum battery range 308a may be a general mileage value indicating a general distance that the vehicle 10 may travel following the charging protocol 208 based on the predicted battery capacity 308. The route battery threshold 254 may be presented as a value of the battery capacity 308 that will be used to complete the selected route based on the starting location 252a and the ending location 252b.

[0062] Further references Figure 2-5 , the charging application 202 can update the charging protocol 208 based on any one or more of the minimum battery threshold 308a, the weather data 242, and the route battery threshold 254. For example, the charging application 202 can present a notification 214 to the user indicating that the current charging protocol 208 may deplete the battery life 304 and recommend adjusting, for example, the selected charging time 222a. Additionally or alternatively, the charging application 202 can recommend reducing the number of selected devices 500 to maximize the battery life 304.

[0063] In some aspects, the charging application 202 may present notifications 214 to the user of various data points related to the charging protocol 208, including, but not limited to, the minimum battery threshold 308a and the route battery threshold 254. Based on the current location 256 of the vehicle 10, the charging application 202 may present the nearest charging station 502. The user may adjust or add stops in the destination route 252 to include the charging station 502. Adding the nearby charging station 502 to the destination route 252 expands the route battery threshold 254 and the minimum battery threshold 308a that may be reached during the charging protocol 208. Thus, in response to detecting the nearby charging station 502 using the navigation application 250, the charging protocol 208 may be selectively adjusted by the data processing hardware 206 or the user.

[0064] Reference now Figure 2 and Figure 6-8 , the charging application 202 can be configured to detect multiple vehicles 10a, 10b. Each of the vehicles 10a, 10b is equipped with a vehicle battery 12a, 12b and a vehicle controller 300a, 300b. Each vehicle controller 300a, 300b is configured in the manner described herein, including each of the battery power 310, the battery life 304, the charging log 306, and the battery capacity 308. Similarly, the charging application 202 is configured to use each vehicle 10a, 10b to determine the minimum battery life 304a and the minimum battery range 308a. For example, the charging application 202 may include a drop-down menu for each vehicle 10a, 10b within the vehicle profile 212 to show the corresponding vehicle data.

[0065] In some examples, the charging application 202 can be configured to detect surrounding vehicles and notify the user of the feasibility of linking or otherwise electrically connecting the surrounding vehicles to the charging application 202. By connecting the vehicles 10a, 10b, the charging application 202 can be used to perform a larger charging capacity. For example, the charging application 202 can utilize battery data of multiple vehicles so that the battery power 310a, 310b of each vehicle 10a, 10b can be utilized in the charging protocol 208.

[0066] In some examples, the vehicles 10a, 10b may be electrically coupled to increase the total battery power 310a, 310b available for the charging protocol 208. Although described as two vehicles 10a, 10b electrically coupled, it is contemplated that more than two vehicles 10 may be electrically coupled to collectively increase the available battery power 310 for the charging protocol 208. The charging application 202 may present a notification such as Figure 6 As shown, the user is alerted to the availability of the auxiliary charging vehicle 10b. The data processing hardware 206 can detect the auxiliary charging vehicle 10b using any feasible detection method (including but not limited to Bluetooth® technology).

[0067] Additionally or alternatively, the user may manually input the auxiliary vehicle 10b into the vehicle profile 212 portion of the charging application 202. For example, the user may have two vehicles 10a, 10b that may be used in combination with the charging application 202. Thus, the user may reuse one or both of the vehicles 10a, 10b in combination with the charging application 202. In some aspects, the vehicles 10a, 10b may be used as part of the charging protocol 208 to provide power to the house 504 via the utility external device 500b. In this example, the user may store the utility external device 500b in the saved charging options 218 of the charging application 202 and may select to utilize one or both of the vehicles 10a, 10b stored in the vehicle profile 212.

[0068] Still reference Figure 2 and Figures 6 to 8 , the combination of vehicles 10a, 10b provides an increased charging duration for the charging protocol 208, such that the power output from the charging protocol 208 can be greater than the charging protocol 208 executed using a single vehicle 10a. The charging application 202 can be configured with a combination protocol 224, which can automatically combine the battery power 310a, 310b from each respective vehicle 10a, 10b. The combination protocol 224 can otherwise perform the same functions as the charging protocol 208, such that in addition to the weather application 240 and the navigation application 250, the combination protocol 224 can also operate in conjunction with various saved charging options.

[0069] The combined protocol 224 can balance the use of the vehicle batteries 12a, 12b because the combined protocol 224 can operate the first vehicle battery 12a for a predetermined period of time and then switch to the second vehicle battery 12b for a second predetermined period of time. For example, the vehicle controller 300a in conjunction with the data processing hardware 206 can selectively draw from the battery capacity 308 of the second battery 12b to supplement the battery capacity 308 of the first battery 12a. The charging application 202 is configured to simultaneously utilize the battery capacity 308 of the first battery 12a and the battery capacity 308 of the second battery 12b to execute the combined protocol 224. The combined protocol 224 can alternate back and forth between the vehicle batteries 12a, 12a to manage the use of each respective battery 12a, 12b. Therefore, each vehicle 10a, 10b can be monitored relative to the respective minimum battery life 308a. It is also contemplated that the user can manually adjust the combined protocol 224 to utilize the first vehicle battery 12a until the minimum battery life 308a is reached before switching to the second vehicle battery 12b. Additionally, the vehicle controllers 300a, 300b may be configured to redirect power from unused power sources of the respective vehicles 10a, 10b to maximize the respective battery capacity 308. It is also contemplated that the vehicle controllers 10a, 10b may cooperate with the data processing hardware 206 to selectively prioritize the external devices 500 based on respective power consumption 208a to maximize the battery capacity 308 of the respective vehicle batteries 12a, 12b.

[0070] Specific reference Figure 9-11 , depicts a flow chart showing the operation of the charging control system 100. Initially, at 1000, a user can manage the vehicle profile 212 and the charging profile 210 of the charging application 202. At 1002, examples of managing the charging application 202 include, but are not limited to, selecting a charging time 222a, charging the selected device to a predetermined battery percentage, prioritizing the selected device, monitoring the battery capacity 308 of the vehicle 10, defining a battery capacity threshold 308a, and providing additional profile modes for the user. At 1004, the charging application 202 is configured to monitor the vehicle battery 12 in real time. At 1006, 1008, 1010, the real-time monitoring of the vehicle battery 12 includes, but is not limited to, the current power consumption, ambient temperature, and predicted temperature from the external device 500 to maximize the battery capacity 308 of the vehicle 10. During the monitoring process, at 1012, the charging application 202 determines whether adjustments to the charging protocol 208 should occur based on the charging parameters. If no adjustment is needed, the charging application 202 , and therefore the data processing hardware 206 , continues to monitor the battery capacity 308 of the vehicle 10 .

[0071] If the data processing hardware 206 determines that an adjustment may be beneficial, at 1014, the data processing hardware 206 determines a charging adjustment for each saved charging option 218 in operation. For example, at 1016, the data processing hardware 206 can evaluate the distance to the nearby charging station 502 and the route battery threshold 254 to determine how much battery capacity is needed to travel to the nearby charging station 502. Additionally or alternatively, the data processing hardware 206 can evaluate the distance from the starting location 252a to the ending location 252b and determine the corresponding route battery threshold 254. The charging application 202 can also be configured to prompt the user of the minimum battery range 308a and / or the minimum battery life 304a if the current battery capacity 308 and / or the battery life 304 are close to the corresponding minimum values.

[0072] The charging application 202 may also present the option of combining multiple vehicles 10a, 10b to optimize the charging protocol 208 for the external device 500, and may utilize user-customized prioritization of power allocation. Then, at 1018, 1020, 1022, the data processing hardware 206 and the charging application 202 may prioritize the vehicle batteries 12 in an indeterminate order to maintain the drivability of the vehicle 10, power down unused power sources, and combine multiple vehicles 10a, 10b to increase battery capacity 308. Then, at 1024, the charging application 202 may prompt the user with various battery rationing options. At 1026, the data processing hardware 206 determines whether the user accepts any changes to the charging protocol 208. If the user accepts the changes to the charging protocol 208, then at 1028, the data processing hardware may adjust the charging protocol 208 and return to real-time monitoring of the vehicle battery 12 at 1004. If the user rejects the change to the charging protocol 208 , then at 1030 , the charging application 202 continues to execute the charging protocol 208 until the termination period is reached.

[0073] Reference again Figure 1-11 , the charging control system 100 optimizes the charging capabilities between the vehicle 10 and various external devices 500 via the user device 200. The charging control system 100 helps the user customize the charging profile 210 and the vehicle profile 212 to seamlessly execute the charging protocol 208 from the user device 200 via the charging application 202. For example, the charging application 202 can charge the selected device to a predetermined device battery percentage based on the user input 102. In some examples, the charging application 202 can charge the selected device for a predetermined time period based on the user input 102. Therefore, the charging application 202 can be used to customize the charging options of various external devices 500 while monitoring the status of the vehicle battery 12 by communicating with the vehicle controller 300 via the network 400.

[0074] Furthermore, the communication between the charging application and both the weather application 240 and the navigation application 250 helps the user track and monitor the battery capacity 308 of the vehicle battery 12 as it relates to the planned trip and charging of the external device 500. Additionally or alternatively, the integration of each of the charging application 202, the weather application 240, and the navigation application 250 with the data processing hardware 206 allows the data processing hardware 206 to monitor the status of the vehicle battery 12 independently of the user monitoring. Thus, the data processing hardware 206 can instruct the charging application 202 to prioritize the vehicle battery 12 based on the user's location and / or the forecasted weather.

[0075] In some aspects, the charging application 202 is configured to automatically detect and prompt the connection of multiple vehicles 10a, 10b to maximize charging output. The connection of multiple vehicle batteries 12a, 12b can extend the charging protocol 208. The combined protocol 224 utilizing the charging application 202 can provide a greater power output, so that the combined protocol 224 can be used with an external device 500 (i.e., a home generator) that utilizes a larger amount of power. In addition, the charging application 202 can prompt the user for various priority options, such as executing a charging protocol for a utility external device compared to an accessory external device. For example, the charging application 202 can present an option to charge a utility external device for a longer period of time compared to an accessory external device.

[0076] Prioritization may also be determined by the data processing hardware 206 based on data received from each of the weather application 240 and the navigation application 250. Thus, in addition to information manually input by the user into the charging application 202 to consolidate available charging options, the charging control system 100 utilizes information from various sources to assist the user in selecting various charging protocols 208 by collecting data from the vehicle controller 300, the weather application 240, and the navigation application 250.

[0077] The foregoing description is provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in a selected configuration, even if not specifically shown or described. It can also be varied in many ways. Such variations should not be considered as departing from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A charging control system for a vehicle, the charging control system comprising: a user device including a display and data processing hardware in communication with the display and executing a charging application that stores a charging profile, a vehicle profile, and saved charging options; and A vehicle controller communicatively coupled to the user device via a network, the vehicle controller storing at least one of a battery power, a battery life, and a battery capacity of a vehicle battery and configured to update a vehicle profile of the charging application and provide charging options on the display when the charging application is executed on the data processing hardware, the charging options including at least one of a charging time, a charging location, and a battery capacity.

2. The charging control system according to claim 1, wherein: The data processing hardware is configured to execute a charging protocol for the external device in response to user input selecting one of the saved charging options.

3. The charging control system according to claim 2, wherein: The user input includes a charging time, and the vehicle controller is configured to provide battery power of the vehicle battery in response to the user input and to provide battery capacity in response to the charging time.

4. The charging control system of claim 2, wherein the data processing hardware is configured to provide a notification on the display indicating that the battery life is at a minimum battery life, and is configured to display nearby charging stations for the vehicle. 5 . The charging control system of claim 1 , wherein a charging profile stores a charging time, and wherein the vehicle controller is configured to communicate the battery capacity to the data processing hardware via the network based on the charging time. 6 . The charging control system of claim 5 , wherein the battery capacity includes a minimum battery range, and the vehicle controller is configured to stop the charging time at the minimum battery range. 7 . The charging control system of claim 1 , wherein the data processing hardware stores a weather application that communicates with the charging application, the data processing hardware being configured to issue a notification to a user in response to data received from the weather application.

8. The charging control system of claim 7, wherein the data processing hardware is configured to charge a utility external device in response to a weather notification from the weather application. 9 . The charging control system of claim 1 , wherein the battery capacity comprises a first battery capacity of a first vehicle battery and a second battery capacity of a second vehicle battery, the first battery capacity being selectively coupled to the second battery capacity.

10. The charging control system of claim 9, wherein the vehicle controller is configured to selectively draw from the second battery capacity to supplement the first battery capacity. 11 . The charging control system of claim 10 , wherein the user input comprises selecting a combined protocol stored by the charging application, the charging application being configured to execute the combined protocol utilizing both the first battery capacity and the second battery capacity simultaneously.

Images