Vehicle system

Abstract

A vehicle system includes a vehicle processor for storing data including a vehicle location and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor and configured to transmit energy from the vehicle battery to the transfer station based on the vehicle location and the vehicle data.

Description

Technical Field

[0001] The present invention generally relates to vehicle systems configured to comply with state of charge constraints. Background Art

[0002] The information provided in this section is for the purpose of generally presenting the background of the present disclosure. To the extent described in this section, the work of the presently named inventors, as well as aspects of the description that may not qualify as prior art at the time of filing, are neither explicitly nor implicitly admitted to be prior art with respect to the present disclosure.

[0003] Many vehicles today are electric vehicles that use batteries to power their vehicles. Batteries, especially fully charged ones, can be a fire hazard in certain circumstances. Therefore, electric vehicles being transported are often maintained at a charge level below the maximum charge level, and ideally, within a safe charge capacity window, to mitigate any fire risk. For example, car ferry operators often impose a state of charge restriction on electric vehicles (e.g. 20-50% of full battery range) before they are allowed to be loaded onto the ferry.

[0004] To comply with the state of charge restrictions, the owner or other user may be required to drive the vehicle in an effort to reduce the drivable range of the vehicle battery, which may increase travel time and cause the user to miss their desired ferry. Therefore, there remains a need to safely and easily comply with state of charge restrictions without requiring the owner or user to unnecessarily drive the vehicle to reduce battery life. Summary of the invention

[0005] In one configuration, a vehicle system includes a vehicle processor for storing data, the data including vehicle event data, a vehicle mode, and a vehicle location. The vehicle location includes one or more of a current vehicle location, a desired vehicle destination, or route information. The vehicle system also includes a server that is communicatively coupled to the vehicle processor and configured to initiate a battery depletion activity based on the vehicle location, the vehicle location including one or more of the current vehicle location, the desired vehicle destination, or route information, and the vehicle event data. The battery depletion activity includes one or more of: enabling a maximum accessory load including one or more of an increase in cooler operation, an increase in coolant flow, additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of a battery cell group by activating a battery cell balancing resistor, and activating inefficient operation of a vehicle component including one or more of a vehicle motor or a vehicle inverter.

[0006] The vehicle system may also include one or more of the following optional features. For example, the vehicle location may include one or more of a global positioning system (GPS) location and traffic information. Additionally, the server may be configured to determine an amount of energy required for the vehicle to reach a destination to determine whether the vehicle battery will be below a particular battery level when the vehicle arrives at the vehicle destination. Additionally, the vehicle location may include route information indicating ferry transportation along the route. Additionally, the server may be configured to continue the battery depletion activity until the vehicle complies with ferry transportation regulations. Additionally, the server may be configured to continue the battery depletion activity until the vehicle battery life is between 20%-50% of a maximum charge. Additionally, a vehicle may include the vehicle system.

[0007] In another configuration, a vehicle system includes a vehicle processor for storing data including a vehicle location and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor and configured to transfer energy from a vehicle battery to a transfer station based on the vehicle location and the vehicle event data. The vehicle location includes one or more of a GPS location, a current vehicle location, a vehicle destination, route information, and traffic information.

[0008] The vehicle system may also include one or more of the following optional features. For example, the server may be configured to continue transferring energy from the vehicle battery until the vehicle complies with ferry transportation regulations. In addition, the server may be configured to continue transferring energy from the vehicle battery until the vehicle battery life is between 20%-50% of maximum charge. In addition, the transfer station may be configured to transfer energy from the vehicle battery to a battery of a second vehicle. In addition, the second vehicle may be a ferry. In addition, the second vehicle may be a land vehicle. In addition, a vehicle may include the vehicle system.

[0009] In another configuration, a vehicle system includes a vehicle processor for storing data including vehicle location and vehicle event data. The vehicle system also includes a server communicatively coupled to the vehicle processor and configured to transfer energy from a vehicle battery to a second vehicle based on the vehicle location and vehicle event data.

[0010] The vehicle system may also include one or more of the following optional features. For example, the server may be configured to transfer energy from the vehicle battery to a transfer station before the energy is transferred to a second vehicle. In addition, the server may be configured to transfer energy from the vehicle battery until the vehicle complies with ferry transportation regulations. In addition, the server may be configured to transfer energy from the vehicle battery until the vehicle battery life is between 20%-50% of the maximum charge. In addition, a vehicle may include the vehicle system. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 1 is a perspective view of a vehicle incorporating a vehicle system according to an aspect of the present invention;

[0013] Figure 2 is coupled to the battery transfer station Figure 1 A perspective view of a vehicle;

[0014] Figure 3 yes Figure 1 A perspective view of the vehicle and the ferry connected to the battery transfer station;

[0015] Figure 4 yes Figure 1 A perspective view of a vehicle and a second land vehicle coupled to the battery transfer station;

[0016] Figure 5 is an exemplary functional block diagram according to an aspect of the present disclosure; and

[0017] Figure 6 is an exemplary operational flow chart according to one aspect of the present disclosure.

[0018] Corresponding reference characters indicate corresponding parts throughout the several views. DETAILED DESCRIPTION

[0019] 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 implemented in many different forms, and that the specific details and exemplary configurations should not be construed as limiting the scope of the present disclosure.

[0020] The terms used herein are only for describing specific exemplary configurations, not for 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 "comprise", "include", "contain" and "have" are inclusive, thus specifying 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.

[0021] 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, engaged, connected, 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 of the associated listed items.

[0022] The terms first, second, third, etc. can be used here 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 are only used to distinguish each element, component, region, layer or part. Terms such as "first", "second" and other numerical terms do not imply order or sequence unless the context clearly indicates. Therefore, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part, without departing from the teaching of the example configuration.

[0023] In this application, including the definitions below, the term module may be replaced by the term circuit. The term "module" may refer to or be part of an application specific integrated circuit (ASIC), 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 functionality; or a combination of some or all of the above, such as in a system on a chip.

[0024] The term code 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 includes a single processor that executes some or all of the code from multiple modules. The term group processor includes a processor that executes some or all of the code from one or more modules in combination with an additional processor. The term shared memory includes a single memory that stores some or all of the code from multiple modules. The term group memory includes a memory that stores some or all of the code 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 can therefore be considered to be tangible non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, including non-volatile memory, magnetic memory, and optical memory.

[0025] 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.

[0026] Software applications (i.e., software resources) may refer to computer software that enables a computing device to perform tasks. In some examples, software applications may be referred to as "applications," "apps," or "programs." 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.

[0027] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., instruction sequences) or data (e.g., program state information) for use by a computing device. Non-transitory memory can 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.

[0028] 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.

[0029] Various implementations of the systems and techniques described herein can be realized in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system comprising at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from a storage system, and to send data and instructions to the storage system.

[0030] The processes and logic flows described in this specification can be performed by one or more programmable processors, also known as data processing hardware, executing one or more computer programs to perform functions by operating on input data and generating outputs. These processes and logic flows can also be performed by dedicated logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits). For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, and any one or more processors of any kind 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 storage devices for storing instructions and data. Typically, a computer will also include or be operably connected to one or more large-capacity storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from the large-capacity storage device or to 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 non-volatile memory, media and storage devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated in special purpose logic circuitry.

[0031] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen, and an optional keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices may also be used to 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.

[0032] refer to Figure 1-6 , the vehicle system 100 includes a vehicle processor 200 and a server 300 communicatively coupled to the vehicle processor 200. Figure 1, a vehicle system 100 is incorporated into a vehicle 10. The vehicle 10 may be an electric vehicle 10 (EV), and may include autonomous or semi-autonomous capabilities. Alternatively, the vehicle 10 may be a hybrid vehicle 10 that combines EV and internal combustion engine (ICE) components and capabilities. The vehicle 10 also includes a vehicle battery 12 configured to provide power to the vehicle 10. The vehicle battery 12 is rechargeable and includes a vehicle battery life between 0% and 100%, where 0% indicates that the vehicle battery 12 is not charged and 100% indicates that the vehicle battery 12 is fully charged. In addition, the vehicle 10 may include a plurality of vehicle sensors 14 and / or a vehicle camera 16 configured to provide data to the vehicle processor 200.

[0033] 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, and a vehicle mode 208. The vehicle location 204 generally relates to the location of the vehicle 10. More specifically, the vehicle location 204 includes one or more of a current vehicle location, route information, and traffic information. The current vehicle location generally relates to the current location of the vehicle 10. The current vehicle location may be obtained from a global positioning system (GPS) or other navigation system, may be obtained from a user device such as a mobile phone or tablet, and / or may be obtained from a third-party processor 500 and transmitted to the vehicle processor 200. Route information generally relates to the route traveled by the vehicle 10, including origin and destination information. Route information may be obtained from user input, a vehicle navigation system, past driver activity, or a third-party processor 500, and transmitted to the vehicle processor 200. In addition, the route information may include data indicating ferry transportation along the route. In addition, the route information may additionally include information related to ferry transportation, including ferry schedules or water conditions, which may affect the travel of the ferry along the route.

[0034] Traffic information generally relates to information related to traffic along a route. Traffic information may include road closures, weather data, ferry wait times, or other information related to the time required to reach a destination and / or the amount of energy available from the vehicle battery 12. Additionally, the vehicle location 204 may be constantly changing, such that the vehicle location 204 may be continuously sensed and / or obtained during vehicle operation.

[0035] The vehicle event data 206 generally relates to actions taken by the vehicle 10 during operation. The vehicle event data 206 may be collected by any vehicle sensor 14 and / or vehicle camera 16 and may be transmitted to the vehicle processor 200 for further processing. In addition, the vehicle event data 206 may include vehicle speed, vehicle braking, or other movements of the vehicle 10 that require energy from the vehicle battery 12. More specifically, the vehicle speed may relate to the current speed of the vehicle 10, whether the vehicle 10 has stopped, whether the vehicle 10 has changed speed rapidly, and other events related to vehicle speed. In addition, vehicle braking may include the current braking state and / or predicted future braking state. In addition, the vehicle event data 206 may be constantly changing, so that the vehicle event data 206 may be continuously sensed and / or obtained during vehicle operation.

[0036] The vehicle mode 208 generally relates to the operation of the vehicle 10 that is currently active. More specifically, the vehicle mode 208 relates to any vehicle mode or operation that may affect the battery life of the vehicle 10. For example, the vehicle mode 208 may include, but is not limited to, operating loads including accessory loads, operation of individual vehicle components including a vehicle motor or a vehicle inverter, resistor modes, vehicle sensor modes, or other vehicle modes that require use of the vehicle battery 12, such as a sport mode. Furthermore, the vehicle mode 208 may be constantly changing, such that the vehicle mode 208 may be continuously sensed and / or obtained during vehicle operation.

[0037] Transportation companies such as ferry operators typically provide a vehicle 10 that is allowed to be loaded onto a transportation vehicle such as a ferry. Figure 3 ), a state of charge limit is imposed on an electric vehicle such as vehicle 10 before. In some examples, the state of charge limit requires that the vehicle battery life is less than 60% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 10%-55% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 20%-50% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 20%-40% of a full charge. In addition, the state of charge limit can be based on the specific chemistry of battery 12, so that the state of charge limit can vary from vehicle to vehicle. In addition, the state of charge limit can be collected, stored and / or determined by the vehicle processor 200 and / or the vehicle server 300.

[0038] The vehicle processor 200 is also configured to store vehicle battery life information. The vehicle battery life information generally relates to the amount of vehicle battery life remaining in the battery 12. In addition, the vehicle battery life information may be affected by one or more of the vehicle event data 206, the vehicle mode 208, and the vehicle location 204. In addition, the vehicle battery life information may include whether the vehicle 10 is within a state of charge limit that may be implemented by a transportation company along the route. For example, the vehicle battery life information may include whether the vehicle battery life is within an acceptable state of charge limit for a ferry along the route. As described in more detail below, the server 300 can determine the vehicle battery life information, which can be stored in the vehicle processor 200 and can also be displayed on the dashboard of the vehicle 10.

[0039] Further references Figure 1-6 , the server 300 is configured as a network and / or cloud-based system in communication with the vehicle processor 200. It is also contemplated that the vehicle processor 200 may transmit any or all of the vehicle data 202 to the server 300 for further processing and / or evaluation. In addition, the vehicle processor 200 and / or the server 300 may be continuously and / or periodically updated so that the vehicle data 202 is updated in real time.

[0040] The server 300 may also be configured to communicate with a third-party processor 500 to collect third-party data. For example, the third-party processor 500 may include, but is not limited to, a vehicle processor 200 along the route. Additionally or alternatively, the third-party processor 500 may include a third-party user device, such as a cellular phone and / or tablet computer within a vehicle along the route. Furthermore, the third-party processor 500 may include a third-party database, such as a database including ferry schedules, weather information, and / or water conditions. It is generally contemplated that the third-party data may include information from the third-party processor 500 related to one or more of the vehicle location 204, the vehicle event data 206, and / or the vehicle mode 208.

[0041] Still refer to Figure 1-6, the server 300 is configured to determine whether the vehicle 10, and more specifically the vehicle battery 12, will comply with the state of charge restrictions when the vehicle 10 arrives at a transport vehicle that requires the state of charge restrictions. The determination of whether the vehicle battery 12 will comply with the state of charge restrictions may be based on one or more of the vehicle location 204, the vehicle event data 206, and the vehicle mode 208. For example, if a user enters their desired destination into the processor 200, and the route to the desired destination includes a ferry or other transport vehicle that requires a specific state of charge, the server 300 will calculate the vehicle battery life under normal operating conditions when the vehicle 10 arrives at the transport vehicle (i.e., the dock associated with the ferry). To make the calculation, the server 300 may also use vehicle data 202, such as traffic information and weather information, as factors in its determination, as increased traffic may require additional energy from the vehicle battery 12, and weather information may affect typical vehicle mode 208 operations during transportation, such as heat, air conditioning, windshield wipers, increased traction control required, etc. The calculated vehicle battery life information is then subtracted from the current vehicle battery life to determine if the vehicle battery 12 complies with the state of charge restrictions when the vehicle 10 arrives at the transport vehicle requiring the state of charge restrictions.

[0042] In addition, the server 300 is configured to initiate battery depletion activities if it is determined that the vehicle battery 12 will not be within the state of charge limits upon arrival at the transport vehicle. The battery depletion activities may be activated while traveling to the transport vehicle location to increase battery usage and thereby allow the vehicle 10 to be within the state of charge limits upon arrival at the transport vehicle location. The battery depletion activities may include one or more of: enabling maximum accessory load including one or more of increased cooler operation or increased coolant flow, additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of battery cell groups by activating cell balancing resistors, and activating inefficient operation of vehicle components including one or more of a vehicle motor or a vehicle inverter.

[0043] In addition, server 300 can be configured to select which battery draining activities to actuate. Determining which battery draining activities to actuate can be based on one or more of vehicle location 204, vehicle event data 206, and vehicle mode 208. For example, if server 300 determines that vehicle 10 arrives at a transport vehicle (i.e., Figure 3If the server 300 determines that the vehicle battery 12 will not be within the state of charge limit when the vehicle 10 arrives at the transport vehicle), the server 300 can calculate the additional energy used by each battery depletion activity and select one or more battery depletion activities to allow the vehicle battery 12 to be within the state of charge limit when it arrives at the transport vehicle. For example, if the server 300 determines that the vehicle battery 12 will not be within the state of charge limit when the vehicle 10 arrives at the transport vehicle, the server 300 can determine that increasing the coolant flow rate will allow the vehicle battery 12 to be within the state of charge limit when it arrives. If so, the server 300 can initiate an increase in the coolant flow rate until the vehicle 10 arrives at the transport vehicle, or until the server 300 determines that the vehicle battery 12 will be within the state of charge limit when it arrives at the transport vehicle.

[0044] Still refer to Figure 1-6 In the example shown, the server 300 may also be configured to continue the battery depletion activity until the vehicle 10 meets the state of charge limit. Thus, if desired, the battery depletion activity may continue once the vehicle 10 has arrived at the transport vehicle. For example, if the vehicle battery 12 does not meet the state of charge limit when the vehicle 10 arrives at the transport vehicle's parking lot, the vehicle 10 may continue the battery depletion activity until the state of charge limit is met. The battery depletion activity may occur while the vehicle 10 is parked or idle waiting for a transport vehicle.

[0045] Reference now Figure 2-4 In the example shown in , the server 300 can be additionally and / or alternatively configured to transfer energy from the vehicle battery 12 to the transfer station 50. The transfer station 50 can be a fixed station disposed near the location of the transport vehicle. In addition, the transfer station 50 can be similar to a typical electric vehicle charging station, such that the transfer station 50 includes an energy storage device and a coupling mechanism for coupling the vehicle 10 to the transfer station 50 (see Figure 2 ). The transfer station 50 is configured to unload energy from the vehicle battery 12 and store the energy within the transfer station 50. More specifically, the transfer station 50 and / or one or more of the servers 300 are configured to unload energy from the vehicle battery 12 until the vehicle battery 12 meets the state of charge limit. Once received by the transfer station 50, the transferred energy can be sent back to the grid. Additionally or alternatively, the transfer station 50 can also be configured to transfer energy unloaded from the vehicle battery of one vehicle 10 to the battery of a second vehicle 52 (see Figure 3 and 4 ). For example, once the first vehicle 10 unloads energy from the vehicle battery 12, the transfer station 50 stores the energy. A second vehicle 52, such as a vehicle being unloaded from a transport vehicle, may require additional energy. Therefore, the second vehicle 52 may be coupled to the transfer station 50 to receive the stored energy from the vehicle 10 (see Figure 4 ). In addition, the second vehicle 52 may be a transport vehicle itself, such as a ferry (see Figure 3). It is also contemplated that, instead of using a transfer station 50, the first vehicle 10 could transfer energy from the vehicle battery 12 directly to a vehicle battery of a second vehicle 52, the second vehicle 52 comprising a second land vehicle or transport vehicle, such as a ferry.

[0046] In addition, the determination of whether to transfer energy from the vehicle battery 12 to the transfer station 50 is based on the vehicle location 204 and the vehicle event data 206. For example, the server 300 can be configured to determine that the battery depletion activity previously performed is insufficient to reach the charge state limit, and then the user can be notified that they still do not meet the charge state limit. In addition, the server 300 can also notify and / or help the user find the transfer station 50 when arriving at the transportation vehicle location.

[0047] In another example, the driver's destination may be unknown, such that the battery depletion activity has not been previously activated. However, the server 300 is configured to determine that the vehicle 10 has arrived at the transport vehicle location and then determine whether the vehicle 10 complies with the state of charge restrictions. If the vehicle 10 does not comply with the state of charge restrictions, the user will be notified of the nearby transfer station 50 and will be prompted to go to the transfer station 50 before attempting to enter the transport vehicle.

[0048] Reference now Figure 5 In the example shown, a vehicle 10 that has not yet boarded the ferry can unload energy from the vehicle battery 12 to the transfer station 50 in step 802 at step 800. The transfer station 50 can then send the excess energy back to the grid, or send the energy to another vehicle. In step 804, if the ferry is an electric vehicle, the other vehicle can be the ferry. Additionally or alternatively, in step 806, the transfer station 50 can transfer energy back to the vehicle leaving the ferry to increase its battery range for the upcoming drive.

[0049] Reference now Figure 6In the example shown, the vehicle 10 begins normal operation at step 700. At step 702, the vehicle 10 detects a ferry on the desired route of the vehicle 10, or at step 704, the driver selects the ferry mode or enters the intention to use the ferry for vehicle transportation. Next, at step 706, the server 300 will use GPS, maps and / or traffic information to determine the energy required to reach the ferry. Then, at step 708, the server 300 determines whether the current vehicle battery life minus the energy required to reach the ferry allows the vehicle battery 12 to be within the state of charge limit of the ferry. If the vehicle battery 12 will be within the state of charge limit, the vehicle 10 operates normally at step 710. However, if the vehicle battery 12 will not be within the state of charge limit when arriving at the ferry, then at step 712, the server 300 will activate a battery depletion activity to reduce the vehicle battery life. At step 714, the server 300 continues to determine whether the current vehicle battery life minus the energy required to reach the ferry allows the vehicle battery 12 to be within the state of charge limit when arriving at the ferry. Additionally, at step 716, if the user is expected to arrive early and wait in the car, the server 300 may be configured to leave a buffer range above the state of charge limit. Additionally, the server 300 may also use weather conditions to determine the buffer range. Once the server 300 determines that the vehicle 10 will be within the state of charge limit upon arrival at the ferry, the server 300 is configured to shut down the battery depletion activity at step 718. The server 300 may continue to determine if the current vehicle battery life minus the energy required to arrive at the ferry allows the vehicle battery 12 to be within the state of charge limit of the ferry in the event that the vehicle data 202 changes.

[0050] As the number of electric vehicles using vehicle transports such as ferries increases, many ferry operators impose restrictions on the state of charge of electric vehicles before vehicles are allowed to be loaded onto the ferry. To avoid driving aimlessly around the ferry terminal to comply with the state of charge restrictions imposed by the ferry operator, the vehicle system 100 as described herein efficiently uses battery energy without increasing the time or hassle of the user on the route. The vehicle system 100 also enables the vehicle 10 to be coupled to a transfer station 50 to unload additional energy when needed. This energy can then be transferred to a second land vehicle 52 leaving the ferry or to the ferry itself, thereby providing efficient energy transfer.

[0051] 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 also within the scope of the following claims.

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

Claims

1. A vehicle system, comprising: a vehicle processor for storing vehicle data including vehicle event data, vehicle modes, and vehicle location, wherein the vehicle location includes one or more of current vehicle location, route information, or traffic information; as well as A server is communicatively coupled to a vehicle processor and configured to initiate a battery depletion activity based on the vehicle location and the vehicle event data, wherein the battery depletion activity includes one or more of: enabling a maximum accessory load including one or more of an increase in cooler operation or an increase in coolant flow, additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of a battery cell group by activating a battery cell balancing resistor, and activating inefficient operation of a vehicle component including one or more of a vehicle motor or a vehicle inverter.

2. The vehicle system according to claim 1, wherein: The vehicle location also includes one or more of a global positioning system (GPS) location and weather information.

3. The vehicle system according to claim 1, wherein: The server is configured to determine an amount of energy required to reach a vehicle destination to determine whether a vehicle battery will be below a certain battery charge level upon reaching the vehicle destination.

4. The vehicle system according to claim 1, wherein: The vehicle position includes route information indicating ferry transportation along the route.

5. The vehicle system according to claim 1, wherein: The server is configured to continue the battery depletion activity until the vehicle complies with the state of charge constraints of the transport vehicle.

6. The vehicle system according to claim 1, wherein: The server is configured to continue the battery depletion activity until the vehicle battery life is between 20%-50% of maximum charge.

7. The vehicle system according to claim 1, wherein: The server is configured to transfer energy from the vehicle battery to the transfer station based on the vehicle location and the vehicle event data.

8. The vehicle system according to claim 7, wherein: The transfer station is configured to transfer energy from the vehicle battery to a battery of a second vehicle.

9. The vehicle system according to claim 8, wherein: The second vehicle is one of a ferry or a land vehicle.

10. A vehicle comprising the vehicle system according to claim 1.

Images