VEHICLE SYSTEM

Abstract

A vehicle system includes a vehicle processor for storing data including vehicle location data and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is stored based on vehicle location data and vehicle data, and then, upon determining that the vehicle is stored, to activate a storage operation.

Description

INTRODUCTION

[0001] The information provided in this section is intended to provide a general context for the disclosure. Neither the work of the presently named inventors, to the extent described in this section, nor those aspects of the description that do not otherwise qualify as prior art at the time of filing are expressly or implicitly admitted as prior art against the present disclosure.

[0002] The present disclosure generally relates to a vehicle system configured to account for state of charge constraints.

[0003] Today, many vehicles are electric vehicles powered by batteries. Batteries, especially fully charged batteries, can pose a fire risk under certain conditions. Therefore, electric vehicles being transported or stored are often kept below a maximum charge and ideally within a safe charge capacity window to contain any fire risks. The safe charge capacity window is often below the maximum charge but above a zero charge, as additional risks to the vehicle can arise when the vehicle battery runtime is at or near zero.

[0004] Some transport vehicles now require state-of-charge restrictions to mitigate the risks associated with transporting electric vehicles. While some vehicles include a mode of operation that limits charging to a certain percentage after leaving the manufacturing facility, the charging restriction is lifted once the vehicle arrives at its destination, such as a dealership. Therefore, there remains a need to safely and easily store and / or transport a vehicle while adhering to state-of-charge restrictions. SUMMARY

[0005] According to one configuration, a vehicle system includes a vehicle processor for storing vehicle data, including vehicle location data and vehicle event data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is stored based on the vehicle location data and the vehicle event data and, if it is determined that the vehicle is stored, to activate a storage operation.

[0006] The vehicle system may include one or more of the following optional features. For example, the server may be configured to notify a user that warehouse operation is being activated. Additionally, the server may be configured to monitor vehicle battery runtime during warehouse operation. The server may also be configured to notify a user of low vehicle battery runtime during warehouse operation. Additionally, the server may be configured to check for post-warehouse operation tasks that need to be performed before driving. Furthermore, the server may be configured to notify a user of post-warehouse operation tasks. Additionally, a vehicle may include the vehicle system.

[0007] According to another configuration, a vehicle system includes a vehicle processor for storing data including vehicle location data and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is being transported based on the vehicle location data and the vehicle event data and, if it is determined that the vehicle is being transported, to activate a transport operation.

[0008] The vehicle system may also include one or more of the following optional features. For example, the vehicle location may include global positioning system (GPS) location and track information. The server may also be configured to notify a user when it is determined that the vehicle is being transported. Additionally, the server may be configured to monitor vehicle battery runtime during transport operations. The server may also be configured to notify a user of low vehicle battery runtime during transport operations. Additionally, the server may be configured to precondition a temperature of a vehicle battery to enable faster charging after the transport operation is complete. Furthermore, the vehicle system may be included in a vehicle.

[0009] According to another configuration, a vehicle system includes a vehicle processor for storing data including a vehicle location, vehicle data, and a transport duration. Additionally, the vehicle system includes a server communicatively coupled to the vehicle processor. The server is communicatively coupled to the vehicle processor and configured to initiate battery drain activities based on the vehicle location, vehicle event data, and transport duration.Battery drain activities include enabling maximum auxiliary loads, including increasing cooling system operation, increasing coolant flow rate, and / or additional vehicle imaging, and / or enabling vehicle sensors to operate in high-load mode, and / or enabling cell bank discharge by activating cell balancing resistors, and / or enabling inefficient operation of vehicle components, including a vehicle engine and / or a vehicle inverter. The server is also configured to determine which battery drain activities to activate based on vehicle location, vehicle event data, and transit duration.

[0010] The vehicle system also includes one or more of the following optional features. For example, the vehicle location may include GPS location information and route information. Additionally, the server may be configured to notify a user when it is determined that the vehicle is being transported. The server may also be configured to monitor vehicle battery runtime during transport operations. Additionally, the server may be configured to precondition a temperature of a vehicle battery to enable faster charging after the completion of transport operations. Furthermore, a vehicle may include the vehicle system. 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; they show: Fig. 1 is a perspective view of a vehicle including a vehicle system according to one aspect of the present disclosure; and Fig. 2 illustrates an exemplary operational flow chart according to one aspect of the present disclosure.

[0012] Corresponding reference numerals designate corresponding parts throughout the drawings. DETAILED DESCRIPTION

[0013] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that this disclosure will be thorough and will fully convey the scope of the disclosure to those skilled in the art. Specific details, such as examples of specific components, devices, and methods, are set forth in order to provide a thorough understanding of 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 certain example configurations only and is not intended to be limiting. As used herein, the singular articles "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. The terms "comprises," "including," "containing," 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 method steps, processes, and operations described herein should not be construed as necessarily requiring their performance in the particular order discussed or illustrated unless specifically identified as an order of performance. Additional or alternative steps may be employed.

[0015] When an element or layer is described as being "on," "engaging with," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, engaging with, connected to, attached to, or coupled to the other element or layer, or there may be intervening elements or layers. Conversely, when an element is described as being "directly on," "directly engaging with," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there need not be any intervening elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar way (e.g., "between," "adjacent," etc.).As used herein, the term “and / or” includes any combination of one or more of the associated 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 are not intended to be limited by these terms. These terms may be used solely 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 clearly indicated by the context.Thus, a first element, component, region, layer, or section discussed below may be referred to as a second element, component, region, layer, or section without departing from the teachings of the example configurations.

[0017] In this application, including the definitions below, the term "module" may be replaced with 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; memory (shared, dedicated, or group) that stores code executed by a 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.

[0018] The term "code" as used above may include software, firmware, and / or microcode and may refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor that, in combination with additional processors, executes some or all of the code from multiple modules. The term "shared memory" includes a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory that, in combination with additional memory, stores some or all of the code from one or more modules. The term "memory" may be a subset of the term "computer-readable medium."The term "computer-readable medium" encompasses non-transitory electrical and electromagnetic signals propagating through a medium and can therefore be considered tangible and non-transitory storage. 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, in part or in whole, 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 access 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 certain examples, a software application may be referred to as an "application," an "app," or a "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., program state information) 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, but are not limited to, 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) (which, for example, is typically used for firmware such as boot programs).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.

[0022] These computer programs (also known as programs, software, software applications, or code) contain machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented programming language and / or assembly / machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to a computer program product, a non-transitory computer-readable medium, an apparatus, and / or a device (e.g., magnetic disks, optical disks, memories, programmable logic devices (PLDs)) used to provide machine instructions and / or data to a programmable processor, which includes a machine-readable medium that embodies machine instructions as a machine-readable signal.The term “machine-readable signal” refers to a 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 realized in digital electronics and / or optical circuitry, integrated circuitry, 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 in a programmable system including 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 memory system, at least one input device, and at least one output device.

[0024] The processes and logic flows described in this application text may be performed by one or more programmable processors, also referred to as data processing hardware, executing one or more computer programs to perform functions by operating on input data and generating outputs. The processes and logic flows may also be performed by special-purpose logic circuitry, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit). Processors suitable for executing a computer program include, by way of example, both general-purpose and special-purpose microprocessors and one or more processors of any type of digital computer. Generally, a processor will receive instructions and data from read-only memory and / or random access memory.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 also includes, or is operatively coupled to, receive data from and / or send data to one or more mass storage devices for storing data, e.g., magnetic disks, magneto-optical disks, or optical disks. However, a computer need not include such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, by way of example, semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., 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 into special-purpose logic circuitry.

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

[0026] With reference to the example given in Fig. 1- Fig. 2, a vehicle system 100 is illustrated. The vehicle system 100 includes a vehicle processor 200 and a server 300 in communication with the vehicle processor 200. In certain examples, such as the example shown in Fig. 1, the vehicle system 100 is incorporated into a vehicle 10. The vehicle 10 may be an electric vehicle (EV), such that the vehicle 10 includes a battery 12 and may have autonomous or semi-autonomous capabilities. Alternatively, the vehicle 10 may be a hybrid electric vehicle (HEV), which includes components and capabilities of both an EV and an internal combustion engine (ICE). While the vehicle 10 could be an EV or an HEV, the vehicle 10 is described as including only EV components and capabilities.

[0027] The vehicle processor 200 stores vehicle data 202 of the vehicle 10. The vehicle data 202 includes a vehicle location 204, vehicle event data 206, a vehicle operating mode 208, and a haul duration 210. The vehicle location 204 generally refers to a location of the vehicle 10. The vehicle location 204 may include a current vehicle location and / or route information. The current vehicle location generally refers to the current location of the vehicle 10. The current vehicle location may be determined from a global positioning system (GPS) or other navigation system and may be communicated to the vehicle processor 200. Additionally or alternatively, the current vehicle location may be determined using vehicle cameras 14 and / or sensors 16.For example, the vehicle processor 200 may collect video data related to the current environment of the vehicle 10 to assist the vehicle processor 200 and / or the server 300 in determining the current vehicle location.

[0028] The route information generally relates to the route traveled by the vehicle 10, including origin and destination information. The route information may be collected from user input, a vehicle navigation system, or past driver activity and communicated to the vehicle processor 200. Additionally, the route information may include the route traveled by a transport vehicle. Transport vehicles may include, but are not limited to, a truck or trailer carrying vehicles, a train, or a cargo ship. The route information may also include information related to the transport vehicle, including a transport vehicle schedule and / or weather conditions that may impact a transport vehicle's travel. Further, the route information may include data related to traffic information or road closures.

[0029] Vehicle event data 206 generally relates to actions taken by vehicle 10. Vehicle event data 206 may be collected from any vehicle sensors 16 and / or vehicle cameras 14 and communicated to vehicle processor 200 for further processing. For example, vehicle event data 206 may include vehicle ignition state, Wi-Fi connections, vehicle speed, vehicle steering wheel angle, or other vehicle events. More specifically, vehicle ignition state may refer to the current ignition state (i.e., whether vehicle 10 is on or off) or may refer to the amount of time that has passed since the ignition state last changed. Additionally, Wi-Fi connections may refer to which Wi-Fi connections are paired with vehicle 10 and for how long.Vehicle speed may refer to the current speed of vehicle 10, whether vehicle 10 has stopped, whether vehicle 10 has changed speed, accelerated, or decelerated, and other events related to vehicle speed. Vehicle steering wheel angle may refer to the current angle of the steering wheel of vehicle 10. The steering wheel angle may provide information about whether vehicle 10 has made a turn or may be in a transport event. For example, if an angle of the steering wheel changes, this may indicate that vehicle 10 is moving and has made a turn. Similarly, if the steering wheel remains stationary while the location of vehicle 10 moves, such information may indicate that vehicle 10 is being transported.Furthermore, the vehicle event data 206 may be continuously changing such that the vehicle event data 206 may be continuously collected and / or determined during vehicle operation.

[0030] Vehicle operating mode 208 generally refers to which operating mode or modes of vehicle 10 are currently active. For example, vehicle operating mode 208 may refer to any vehicle operating mode or operation that may impact the battery life of vehicle 10. Vehicle operating mode 208 may include, but is not limited to, operating modes that include accessory modes, operation of individual vehicle components, including a vehicle engine or vehicle inverter, a resistance mode, vehicle sensor modes, or other vehicle operating modes that require use of battery 12. Additionally, vehicle operating mode 208 may refer to a storage operation or a transportation operation.The storage mode or the transport mode may be activated by a user through the vehicle dashboard or other vehicle component, through a third-party application, or through a user device such as a mobile phone or tablet. Additionally, it is contemplated that the storage mode or the transport mode may be activated by the server 300, as disclosed in more detail below. Furthermore, the vehicle operating mode 208 may be continuously changing, such that the vehicle operating mode 208 may be continuously sensed and / or determined during vehicle operation.

[0031] The transportation duration 210 generally refers to a distance or time of transportation. In some examples, the transportation duration 210 is entered by a user prior to transportation. However, it is also contemplated that the transportation duration 210 may be determined or collected using the route information and / or the destination information.

[0032] Transportation companies often impose state of charge restrictions on electric vehicles, such as vehicle 10, before vehicle 10 may be loaded onto a transportation vehicle. In some examples, the state of charge restriction requires that a vehicle battery runtime be less than 60% of a full charge. In other examples, the state of charge restriction requires that the vehicle battery runtime be between 10% and 55% of a full charge. In still other examples, the state of charge restriction requires that the vehicle battery runtime be between 20% and 50% of a full charge. In still other examples, the state of charge restriction requires that the vehicle battery runtime be between 20% and 40% of a full charge.Additionally, the state of charge constraint may be based on the specific chemical composition of the battery 12, such that the state of charge constraint may vary from vehicle to vehicle. Furthermore, the state of charge constraint may be collected, stored, and / or determined by the vehicle processor 200 and / or the vehicle server 300.

[0033] The vehicle processor 200 is also configured to store vehicle battery runtime information. The vehicle battery runtime information generally relates to the amount of vehicle battery runtime remaining in the battery 12. Additionally, the vehicle battery runtime information may be affected by the vehicle event data 206 and / or the vehicle operating mode 208 and / or the vehicle location 204 and / or the transport duration 210. Furthermore, the vehicle battery runtime information may include whether the vehicle 10 is within the state of charge constraint that may be implemented along the route by the transport vehicle. For example, the vehicle battery runtime information may include whether the vehicle battery runtime is within the allowable charge constraint of a particular transport vehicle.

[0034] As in the Fig. 1 and Fig. 2, the server 300 is further configured as a network and / or a cloud-based system that communicates with the vehicle processor 200. It is also contemplated that the vehicle processor 200 may communicate any or all of the vehicle data 202 to the server 300 for further processing and / or evaluation. Furthermore, the vehicle processor 200 and / or the server 300 may update continuously and / or regularly such that the vehicle data 202 is updated in real time.

[0035] The server 300 may also be configured to communicate with third-party processors 500 to collect data from third parties. For example, the third-party processors 500 may include, but are not limited to, vehicle processors 200 along the route. Additionally or alternatively, the third-party processors 500 may include third-party user devices such as mobile phones and / or tablets in vehicles along the route. Further, the third-party processors 500 may include third-party databases such as databases containing transportation vehicle schedules, weather information, and / or traffic conditions. It is generally contemplated that the third-party data may include information from the third-party processors 500 regarding the vehicle location 204, the vehicle event data 206, the vehicle operating mode 208, and / or the transportation duration 210.

[0036] In the example shown in the Fig. 1 and Fig. 2, the server 300 is further configured to determine when the vehicle 10 is in storage based on the vehicle location 204 and the vehicle event data 206. More specifically, the server 300 may use data collected by the vehicle processor 200, such as GPS data, vehicle camera data, vehicle ignition states, and / or a time since the last change in the vehicle ignition state, to determine whether the vehicle 10 is in storage. For example, if the vehicle 10 has been at the same GPS location for a predetermined period of time, which may be confirmed by data from the one or more vehicle cameras 14, and has not changed ignition status in the predetermined period of time, the server 300 may determine that the vehicle 10 is in storage.In other examples, the vehicle camera 14 may be capable of detecting vehicle coverage or other indicators that help the server 300 determine that the vehicle 10 may be stored. In other examples, the vehicle event data 206 may indicate that the vehicle 10 has been connected to the same Wi-Fi connection for a predetermined period of time.

[0037] If the server 300 determines that the vehicle 10 is in storage, the server 300 may enable storage mode. Storage mode may include enabling additional features, including, but not limited to, monitoring vehicle battery runtime and setting a low battery timer. Monitoring vehicle battery runtime may include maintaining battery life low enough to reduce the risk of fire, while setting a low battery timer may be used to prompt a vehicle owner or user to charge the battery 12 to prevent the vehicle battery runtime from becoming too low and causing damage to the battery 12. Therefore, enabling storage mode when the vehicle 10 is connected to a charging device may enable charging of the vehicle while in storage mode.Although the vehicle 10 may be charged during storage operation, the server 300 is configured to maintain the vehicle battery runtime within the state of charge constraints. Additionally, the server 300 may be configured to notify an owner or user that storage operation is being activated and / or when the battery 12 reaches a predetermined low vehicle battery runtime (i.e., near zero charge).

[0038] When storage operation is deactivated, either by a user manually ending storage operation or by changing the ignition state (i.e., turning on the vehicle), the server 300 is additionally configured to check for any post-storage operation tasks that need to be performed before driving. The storage operation tasks may include, but are not limited to, checking whether the vehicle 10 needs an oil change, checking a fuel level and fuel age, a tire rotation status, windshield fluid, and tire pressure monitoring. Additionally, the server 300 may be configured to notify the user of any post-storage operation tasks that require attention. For example, if the server 300When storage mode is enabled, server 300 monitors the vehicle battery runtime and, when connected to a vehicle charging device, maintains the vehicle battery runtime within the state-of-charge constraints. Additionally, when a user wishes to use the vehicle 10 again, the server 300 may power on the vehicle 10, prompting the server 300 to deactivate storage mode and notify the user of post-storage tasks that require attention. For example, if the tires are low on air pressure, server 300 sends a notification to a user device, such as a mobile phone or tablet, and / or to the vehicle dashboard, alerting the user to add more air to the tires as soon as possible.

[0039] The server 300 is also configured to determine whether the vehicle 10 is being transported based on the vehicle location 204 and the vehicle data 202. For example, if the server 300 detects that the vehicle 10 is changing location based on the GPS location, but the vehicle 10 is not powered on or has no vehicle speed, the server 300 may determine that the vehicle 10 is being transported. Additionally, the server 300 may also be configured to notify the user that the vehicle 10 is currently being transported. Therefore, if the server 300 determines that the vehicle is being transported and the server 300 notifies the user of the transport, the user may prepare for vehicle delivery or become aware that the vehicle 10 is currently being towed.

[0040] If the server 300 determines that the vehicle is being transported, the server 300 may additionally be configured to activate the transport mode. During transport mode, the server 300 is configured to monitor the vehicle battery runtime and compare it to the maximum state of charge limitation of the transport vehicle. If the current vehicle battery runtime is higher than the maximum state of charge limitation, the server 300 may be configured to warn the user of the situation, limit charging capability if the vehicle 10 is coupled to a charging station, and / or initiate energy reduction activities. Additionally, the server 300 may be configured to notify the user of a potentially dangerous low vehicle battery runtime during the transport mode.The notification may be provided by a third-party application, a user device, the vehicle dashboard, or other vehicle systems. Furthermore, the server 300 may be configured to precondition a temperature of the battery 12 to enable faster charging upon completion of the transportation operation. The server 300 may be configured to use route information, such as destination information or user input, to determine when the preconditioning should occur. For example, during winter transportation in a cold climate, the server 300 may be configured to heat the battery 12 during the transportation operation to enable faster charging upon arrival at the destination.

[0041] Additionally, the server 300 may be configured to initiate battery drain activities based on the vehicle location 204, the vehicle event data 206, and the transport duration 210. For example, if the transport duration 210 is known, the server 300 may use the current vehicle location 204 and the vehicle event data 206 to determine how much battery drain is required and how long battery drain activities should be applied. Once transport operation is activated, the server 300 additionally checks the current battery life and determines whether it is within the state of charge constraint for transport on the specific transport vehicle. If the server 300 determines that the current battery life is above the state of charge constraint for transport, the server 300 immediately blocks any further charging operations and begins the battery drain activities.

[0042] The battery drain activities may include enabling maximum additional loads, including increasing cooling system operation, increasing coolant flow rate, and / or additional vehicle imaging, and / or enabling vehicle sensors to operate in high-load mode, and / or enabling cell bank discharge by activating cell balancing resistors, and / or enabling inefficient operation of vehicle components, including a vehicle engine and / or a vehicle inverter. Additionally, the server 300 may be configured to determine which battery drain activities to activate based on the vehicle location 204, the vehicle data 202, and the transit duration 210, since not all battery drain activities can operate simultaneously.It is further contemplated that battery draining activities may continue until server 300 determines that the current battery runtime is within the transportation state of charge constraint. For example, if server 300 determines that enabling inefficient operation of the vehicle engine should be enabled, server 300 may continue inefficient operation of the vehicle engine until the current vehicle battery runtime is within the state of charge constraint.

[0043] Additionally, server 300 may block charging of a vehicle if an upcoming transport event is known. For example, if a user has indicated that vehicle 10 will be transported the next day and begins charging vehicle 10, server 300 may completely block charging of vehicle 10 or only allow charging up to a certain vehicle battery runtime, such that battery 12 continues to meet state-of-charge constraints during transport the next day.

[0044] In the example shown in Fig.2, the vehicle system 100 begins operation in step 700. In step 702, the server 300 determines whether the user has selected the storage mode. If the user has not selected the storage mode, the server 300 determines whether the user has selected the transport mode in step 704. If the user has not selected the transport mode, the vehicle 10 collects vehicle data 202 in step 706. The vehicle data 202 is then analyzed by the server 300 in step 708 to determine whether a storage event is detected in step 710. If no storage event is detected, the server 300 determines whether a transport event is detected in step 712.However, if a storage event is detected, either by the user selecting storage operation in step 702 or by the server 300 determining that the vehicle 10 is in storage in step 710, the vehicle system 100 begins a storage charge timer to determine how much battery runtime is available in step 714. The server 300 then determines whether the vehicle 10 is connected to a charging device in step 716. If the vehicle 10 is connected to the charging device, the server 300 is configured to maintain the battery 12 in the area for secure storage in step 718. Additionally, the server 300 is configured to monitor for any post-storage tasks that may be necessary prior to travel in step 720.If the vehicle 10 is not connected to the charging device, the server 300 is configured to monitor the vehicle battery runtime in step 722 and to determine whether the battery 12 is approaching low vehicle battery runtime in step 724. If the battery 12 is approaching low vehicle battery runtime, the user is warned of the low battery runtime and potential hazards in step 726.

[0045] If a user selects the transport mode in step 704 or if a transport event is detected in step 712, the server 300 is additionally configured to inhibit charging in step 728 until the vehicle 10 is outside of the transport mode. In addition, the server 300 is configured to analyze the composition of the battery 12 in step 730 to determine the state of charge constraint. The server 300 is then configured to determine in step 732 whether the current vehicle battery runtime is greater than the determined state of charge constraint. If the current vehicle battery runtime is greater than the determined state of charge constraint, the server 300 is configured to alert the user in step 734 that a transport operation is taking place and to display the current vehicle battery runtime.The server 300 is also configured to take mitigation actions to reduce the vehicle battery runtime below the state of charge constraint in step 736. If the time of the transport event is unknown in step 738, the program ends once the mitigation actions reduce the vehicle battery runtime below the state of charge constraint. However, if the time of the transport event is known in step 738, the server 300 determines when the transport event ends within a predetermined time period in step 740 and begins the battery temperature operations to enable rapid charging when the transport event ends in step 742.

[0046] Today, many vehicles are electric vehicles powered by batteries. Batteries, especially fully charged ones, pose a potential fire hazard under certain conditions.

[0047] Therefore, it is often advantageous to provide electric vehicles being transported or stored with a charge below the maximum charge safety level to mitigate any fire risks. The vehicle system 100, as described herein, provides a user-friendly way to safely and easily store and / or transport the vehicle 10 while adhering to the charge level restrictions.

[0048] Several implementations have been described. Nevertheless, it should be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.

[0049] The foregoing description has been provided for illustrative and descriptive purposes. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular configuration are generally not limited to that particular configuration, but are, where applicable, interchangeable and may be used in a chosen configuration even if not specifically shown or described. They may also be varied in many respects. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.

Claims

[1] Vehicle system for a vehicle, the vehicle system comprising: a vehicle processor for storing vehicle data including vehicle location data and vehicle event data; and a server that is communicatively coupled to the vehicle processor and is configured: determine when the vehicle is stored based on the vehicle location data and the vehicle event data; and to activate a storage operation when it is determined that the vehicle is being stored. [2] The vehicle system of claim 1, wherein the server is configured to notify a user that the storage operation is activated. [3] The vehicle system of claim 1, wherein the server is configured to monitor a vehicle battery runtime during storage operation. [4] The vehicle system of claim 3, wherein the server is configured to notify a user of low vehicle battery runtime during storage operation. [5] The vehicle system of claim 1, wherein the server is configured to check whether there are any tasks scheduled after the warehouse operation that would need to be performed before the trip. [6] The vehicle system of claim 5, wherein the server is configured to notify a user of tasks scheduled after the warehouse operation. [7] The vehicle system of claim 1, wherein the server is configured to activate battery drain activities based on the vehicle location, the vehicle event data, and the transport duration when the vehicle battery runtime is above a state of charge constraint. [8] The vehicle system of claim 7, wherein the battery draining activities include releasing maximum additional loads, including increasing a cooling system operation, increasing a coolant flow rate, and / or additional vehicle imaging, enabling vehicle sensors to high load operation, and / or enabling discharging of cell groups by activating cell balancing resistors, and / or enabling inefficient operation of vehicle components, including a vehicle engine or a vehicle inverter. [9] The vehicle system of claim 8, wherein the server is also configured to determine which battery drain activities should be activated based on the vehicle location, the vehicle event data, and the transport duration. [10] A vehicle including the vehicle system of claim 1.

Images