Passenger electric vehicles are powered on electricity from an on-board battery, which requires regular charging. The charging is accomplished through the charging port located on the electric vehicle. In order to charge the battery, an electrical source is required, typically from a charging station. The electric vehicle (EV) comes equipped with an external charger interface to connect the EV's charging port to the charging station. As illustrated in
When charging with AC, an industry standard connector is used, e.g., a J-Connector, depending on the manufacturer and the geographical region. The connector 104 is inserted into the EV charging port 103 for the purpose of recharging the battery. Similarly, when charging with DC, a connector 104 is inserted into the EV charging port 103.
However, when the EV's battery requires recharging, a charging station 102 may not be available or may not be reachable before the EV's battery is too depleted to operate the EV battery. Even when the charging station 102 is portable, the charging station 102 must be connected to a grid line 106 in order to charge the EV. If the EV battery becomes too depleted to operate the EV 101, then the EV 101 will need to be towed to a charging station 102 that is already connected to a grid line 106 or to a location where the charging station 102 can connect to a grid line 106. This may be problematic when the EV 101 or its operator is involved in an emergency situation. Therefore, there is a need for an alternative to recharging an EV battery using a charging station that requires a connection to a grid line.
Disclosed herein is an electric vehicle to electric vehicle charger as specified in the independent claims. Embodiments of the present invention are given in the dependent claims. Embodiments of the present invention can be freely combined with each other if they are not mutually exclusive.
According to one embodiment of the present invention, a battery charger includes an input port configured to physically and electrically couple to an electrical port of a source electric vehicle. A power control circuit of the battery charger receives a source power signal from the source electric vehicle through the input port. A converter circuit of the battery charger converts the source power signal to an output power signal according to power requirements of a recipient electric vehicle. The battery charger further includes an output port configured to physically and electrically couple to a charging port of a recipient electric vehicle. A microcontroller of the battery charger is configured to manage a transfer of the output power signal to the recipient electric vehicle through the output port.
In one aspect, the output port of the battery charger includes a direct current (DC) connection and an alternating current (AC) connection. The battery charger includes a split circuit configured to route the source power signal to the DC connection or the AC connection according to the power requirements of the recipient electric vehicle.
In another aspect, the battery charger includes a dedicated DC output port or a dedicated AC output port.
According to another embodiment of the present invention, a method for charging a battery includes: detecting physical and electrical connections to a source electric vehicle and a recipient electric vehicle; receiving a direct current (DC) power signal directly from a battery of the source electric vehicle; converting the DC power signal from the battery of the source electric vehicle to an output power signal according to power requirements of the recipient electric vehicle; and outputting the output power signal to a charging port of the recipient electric vehicle, the charging port electrically coupled to a battery of the recipient electric vehicle.
The present invention provides an electric vehicle to electric vehicle charger. The following description is presented to enable one of ordinary skill in the art to make and use the present invention and is provided in the context of a patent application and its requirements. Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
Reference in this specification to “one embodiment,” “an embodiment,” “an exemplary embodiment,” “some embodiments,” or “a preferred embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments. In general, features described in one embodiment might be suitable for use in other embodiments as would be apparent to those skilled in the art.
Embodiments of the present invention provide an electric vehicle to electric vehicle charger (EV to EV charger), where a source EV can provide electrical charge to a recipient EV to recharge the recipient EV's battery, without requiring a connection to a grid line. The EV to EV charger provides a smart link between the two EVs. The EV to EV charger monitors the flow rate of the electricity from the source EV to the recipient EV and manages the charging process to prevent depletion of the source EVs onboard battery.
The microcontroller 301 of the charger 200 executes program code stored on a computer readable medium (see the description below with reference to
The microcontroller 301 further performs safety checks prior to beginning the charging process. Once the required safety checks are successfully completed without identifying any issues (i.e., clear), the charging process may begin. The charger 200 receives the DC signal from the source EV 201 at the input port 220. When the recipient EV 211 is configured to receive DC power, the converter circuit 304 maintains or adjusts the level of the DC signal from the input port 220 to a power level based on the power requirements of the recipient EV 211. For example, a DC power signal may be output at a level between 200V and 600V. When the recipient EV 211 is configured to receive AC power, the converter circuit 304 converts the DC signal from the input port 220 to an AC signal and adjusts the power level based on the power requirements of the recipient EV 211. For example, an AC power signal may be output at an AC Level 1 of 120V or an AC Level 2 of 208V-240V. The split circuit 302 routes the DC or AC signals to the DC connection 222 or AC connection 223, respectively, depending on whether the recipient EV 211 is configured to receive DC or AC power signals. Referring again to
Although
In the charging process, the converter circuit 304 converts the DC signal from the source EV 201 to the required AC or DC output signal, depending on the recipient EV 211's requirements (910). If the output signal is an AC signal, the split circuit 302 routes the output signal to the AC connection 223 (911). If the output signal is a DC signal, the split circuit 302 routes the output signal to the DC connection 222 (912). Periodically throughout the charging process, the microcontroller 301 monitors the process and performs safety checks according to industry standards (915). If any safety issues are identified (916), the microcontroller 301 aborts the charging process (917). When the charge of the recipient EV 211's battery 215 is complete (913), the microprocessor 301 ends the charging process (914).
It should be understood that the exemplary embodiments described herein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects within each embodiment should typically be considered as available for other similar features or aspects in other embodiments. While one or more embodiments have been described with reference to the figures, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from their spirit and scope.
The present invention can take the form of an embodiment containing both hardware and software elements. The present invention can include a computer readable storage medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer usable or computer readable storage medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Input/output or I/O devices (including but not limited to keyboards, displays, point devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified local function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.
This patent application claims the benefit of U.S. Provisional Patent Application No. 63/373,639 filed Aug. 26, 2022, the disclosure of which is incorporated by reference herein in its entirety.
Number | Date | Country | |
---|---|---|---|
63373639 | Aug 2022 | US |