Pre-charging using an on-board charger and electric vehicle high voltage architecture

Abstract

An electric vehicle pre-charge circuit is provided. In one or more embodiments, the electric vehicle pre-charge circuit can include a first contactor on a positive bus between a load and a battery. In various embodiments, the electric vehicle pre-charge circuit can include a second contactor on a negative bus between the load and the battery. In other embodiments, the electric vehicle pre-charge circuit can include an on-board charger connected to the positive bus and the negative bus on the battery side of the positive bus and the battery side of the negative bus, wherein a phase wire connects the on-board charger to the positive bus on the load side of the positive bus, and wherein a neutral wire connects the on-board charger to the negative bus on the load side of the negative bus.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 157,355, filed March 5, 2021, entitled “PRE-CHARGE OF THE HIGH-VOLTAGE DCCAPACITANCE USING AN ON-BOARD CHARGER AND ELECTRIC-VEHICLE HIGH-VOLTAGE ARCHITECTURE”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The disclosed topics relate to electric vehicle pre-charging, and more specifically to electric vehicle pre-charging using on-board chargers and electric vehicle high-voltage architecture. Background Technology

[0004] Electric vehicles (EVs) can utilize pre-charge circuits to limit inrush current, which can extend the lifespan of EV components and improve EV reliability. However, conventional pre-charge circuits are bulky, inefficient, and costly to implement, thus increasing the cost of the corresponding EV or other vehicles (such as hybrid electric vehicles or plug-in hybrid electric vehicles). Furthermore, conventional pre-charge circuits utilize mechanical relays and resistors, and conventional pre-charging typically occurs outside of the power conversion block. Summary of the Invention

[0005] The following overview is presented to provide a basic understanding of one or more embodiments of the invention. This overview is not intended to identify key or essential elements or to depict any scope of a particular embodiment or any scope of the claims. Its sole purpose is to present the concepts in a simplified form as a prelude to the more detailed description that follows. As described, there is a need for smaller, more efficient, and cheaper precharged architectures, and various embodiments are described herein for this purpose and / or other purposes.

[0006] According to an embodiment, an electric vehicle pre-charging circuit may include: a first contactor located on a positive bus between a load and a battery; a second contactor located on a negative bus between a load and a battery; and an on-board charger connected to the positive and negative buses on the battery side of the positive bus and the battery side of the negative bus, wherein the phase line connects the on-board charger to the positive bus on the load side of the positive bus, and wherein the neutral line connects the on-board charger to the negative bus on the load side of the negative bus.

[0007] According to another embodiment, an electric vehicle pre-charging circuit may include: a first contactor located on a positive bus between a load and a battery; a second contactor located on a negative bus between a load and a battery; an on-board charger connected to the positive bus and the negative bus on the load side of the positive bus and the load side of the negative bus; and a metal-oxide-semiconductor field-effect transistor (MOSFET) switch connected to the positive bus on the battery side of the first contactor and connected to the on-board charger.

[0008] According to an additional embodiment, a method may include: generating a precharge voltage and a precharge current through a system including a processor and using a DC-DC converter; closing a first pair of metal-oxide-semiconductor field-effect transistors (MOSFETs) of an on-board charger through the system; opening a second pair of MOSFETs of the on-board charger through the system; and opening the first pair of MOSFETs through the system in response to determining that the precharge operation is complete. Attached Figure Description

[0009] Figure 1 A block diagram of an example non-limiting precharge circuit according to one or more embodiments described herein is shown.

[0010] Figure 2 A block diagram of an example non-limiting precharge circuit according to one or more embodiments described herein is shown.

[0011] Figure 3 A block diagram of an example non-limiting precharge circuit according to one or more embodiments described herein is shown.

[0012] Figure 4 A block diagram of an example non-limiting precharge circuit according to one or more embodiments described herein is shown.

[0013] Figure 5 A block diagram of an example non-limiting precharge circuit according to one or more embodiments described herein is shown.

[0014] Figure 6 Example non-limiting timing diagrams are shown according to one or more embodiments described herein.

[0015] Figure 7 A flowchart of an example non-limiting pre-charge process according to one or more embodiments described herein is shown.

[0016] Figure 8 This is an example non-limiting computing environment in which one or more embodiments described herein may be implemented.

[0017] Figure 9 This is an example non-limiting networking environment in which one or more embodiments described herein may be implemented. Detailed Implementation

[0018] The following detailed description is illustrative only and is not intended to limit the embodiments and / or their application or use. Furthermore, it is not intended to be construed as being bound by any express or implied information provided in the foregoing Background or Summary of the Invention or Detailed Description sections.

[0019] One or more embodiments will now be described with reference to the accompanying drawings, wherein the same reference numerals are always used to refer to the same elements. In the following description, numerous specific details are set forth for purposes of explanation in order to provide a more thorough understanding of one or more embodiments. However, it will be apparent that one or more embodiments may be practiced without these specific details in various circumstances.

[0020] It should be understood that when an element is referred to as being "coupled" to another element, it can describe one or more different types of coupling, including but not limited to chemical coupling, communication coupling, capacitive coupling, electrical coupling, electromagnetic coupling, inductive coupling, operational coupling, optical coupling, physical coupling, thermal coupling, and / or another type of coupling. As mentioned herein, an "entity" can include a person, client, user, computing device, software application, agent, machine learning model, artificial intelligence, and / or another entity. It should be understood that such entities can facilitate the implementation of the subject matter disclosed according to one or more embodiments described herein.

[0021] The embodiments described herein more efficiently precharge high-voltage (HV) buses (e.g., HV DC bus 102). In this regard, the embodiments herein can integrate a bidirectional on-board charger (OBC) and a DC-DC converter into a single module or unit, thus utilizing existing EV components. It should also be noted that the various embodiments herein may comply with one or more standard safety requirements.

[0022] Figure 1A block diagram of an example non-limiting pre-charge circuit 100 (e.g., a pre-charge architecture) according to one or more embodiments described herein is shown. In various embodiments, the pre-charge circuit 100 may include an HV DC bus 102 (e.g., positive bus 102a and negative bus 102b), a battery 106 (e.g., an HV battery, such as an 800-volt, 600-volt, 400-volt, or other suitable battery), a contactor 112 (e.g., a first contactor), a contactor 114 (e.g., a second contactor), a load 116, and / or a pre-charge module 118. In one or more embodiments, the pre-charge module 118 may include a pre-charge circuit 104, a low-voltage (LV) DC-DC converter 108, and / or an OBC 110.

[0023] According to one embodiment, the LV DC-DC converter 108 can be connected to the HV DC bus 102 before the main contactors (e.g., contactors 112 and 114) (e.g., on the battery side of the main contactors). In this respect, the on-board charger (OBC) 110 can be connected to the HV DC bus 102 after the main contactors (e.g., contactors 112 and 114) (e.g., on the load side of the main contactors). In other embodiments, the LV DC-DC converter 108 can be connected to the HV DC bus 102 after the main contactors (e.g., contactors 112 and 114) (e.g., on the load side of the main contactors). In this respect, the on-board charger (OBC) 110 can be connected to the HV DC bus 102 after the main contactors (e.g., contactors 112 and 114) (e.g., on the battery side of the main contactors). Furthermore, in this respect, the embodiments herein enable the use of an integrated module (e.g., pre-charge module 118) to perform the pre-charge function compared to conventional pre-charge circuits. It should be noted that this arrangement of the LV DC-DC converter 108 and / or OBC 110 allows for the removal or omission of the LV battery (e.g., a 12-volt battery) from the corresponding vehicle. It should be further noted that load 116 may include (e.g., connected in parallel) one or more of the various HV loads of the drive system (e.g., traction inverter, electric motor, or other drive system or drive system components) of the corresponding EV or other suitable vehicle (such as a hybrid electric vehicle or plug-in hybrid electric vehicle). It should also be noted that load 116 may include one or more of various loads, capacitors, or other components of the corresponding EV. For example, load 116 may additionally or alternatively include a traction inverter, OBC, and / or other suitable EV components. In this respect, although load 116 is depicted as a capacitor, this is merely representative and load 116 is not limited to capacitors. It should be noted that although... Figure 1The controller, pre-charge circuit 100 and / or any other pre-charge circuit (e.g., pre-charge circuit 200, pre-charge circuit 300, pre-charge circuit 400 or pre-charge circuit 500) are not depicted, but the architecture or embodiments herein may include a controller (e.g., controller 202 or similar, as discussed in more detail later).

[0024] Figure 2 A block diagram of an example non-limiting pre-charge circuit 200 (e.g., a pre-charge architecture) according to one or more embodiments described herein is shown. In various embodiments, the pre-charge circuit 200 may include a battery 106, a load 116, a contactor 112, a contactor 114, a controller 202, a switch 204, a resistor 206, and / or a pre-charge module 210. In one or more embodiments, the pre-charge module 210 may include the switch 204, the resistor 206, and / or the controller 202. In various embodiments, the pre-charge module 210 may be similar to the pre-charge module 118. It should be noted that in... Figure 2 For illustrative purposes, the LVDC-DC converter 108 and OBC 110 are omitted; however, it should be further noted that the precharge module 210 may include the LVDC-DC converter 108 and OBC 110. Additionally, it should be noted that the precharge circuit 104 may include one or more components of the precharge module 210.

[0025] According to embodiments, controller 202 can generate a signal that can open or close switch 204. It should be noted that controller 202 may include a processor, memory, one or more sensors (e.g., a voltmeter, current sensor, switch position sensor, and / or other suitable sensors), and / or other suitable components that enable controller 202 to open or close switches, contactors, relays, or otherwise control the various components described herein. In various embodiments, switch 204 may include a metal-oxide-semiconductor field-effect transistor (MOSFET) or another suitable switch or contactor. In this respect, controller 202 can open or close switch 204. Such MOSFETs occupy significantly less space and can be surface-mounted. Therefore, by utilizing MOSFETs instead of conventional pre-charge relays, space can be saved in the corresponding vehicle. However, it should be noted that when using MOSFETs, heat dissipation and unintended current flow through the corresponding body diode may occur and therefore need to be managed. Therefore, active cooling (e.g., for battery 106, LV DC-DC converter 108, or OBC 110) can be used for the thermal management of the MOSFETs and / or pre-charge module 118 herein. Additionally, when using MOSFETs, unintended currents (e.g., reverse current potential) can occur through the corresponding free-body diode of the MOSFET (e.g., Figure 2 (Reverse flow direction 208 in the middle). In this respect, there is a sufficiently large voltage difference between the normal path of current flow (in this case from left to right) when the main contactor (e.g., contactor 112 or contactor 114) is open. In addition, in this respect, when the voltage across load 116 is higher than the voltage of battery 106, the free-body diode (e.g., switch 204) can allow unintended current flow even though switch 204 is open.

[0026] The above can be remedied by implementing a second MOSFET (e.g., switch 302), wherein the corresponding body diode is oriented in the opposite direction to the body diode of switch 204 (see example...). Figure 3 ).in this regard, Figure 3 A block diagram of an example non-limiting pre-charge circuit 300 (e.g., a pre-charge architecture) according to one or more embodiments described herein is shown. In various embodiments, the pre-charge circuit 300 may include a battery 106, a load 116, contactors 112 and 114, and a controller 202, a switch 204, a resistor 206, and / or a pre-charge module 304. In one or more embodiments, the pre-charge module 304 may include switches 204 and 302, resistor 206, and / or controller 202. In various embodiments, the pre-charge module 304 may be similar to pre-charge module 118. Figure 3 For illustrative purposes, the LV DC-DC converter 108 and OBC 110 are omitted; however, it should be noted that the precharge module 304 may similarly include the LV DC-DC converter 108 and OBC 110. It should also be noted that the precharge circuit 104 may include one or more components of the precharge module 304.

[0027] In this respect, the two MOSFETs (e.g., switches 204 and 302) can be positioned back-to-back (e.g., adjacent and / or connected by wires), with the corresponding body diodes oriented in opposite directions. In various embodiments, switches 204 and 302 can be driven by the same control signal from controller 202 or by separate control signals from controller 202. While it should be noted that adding MOSFETs may increase heat dissipation, this heat dissipation can be remedied by utilizing pulse width modulation (PWM) signals (e.g., at 1 kHz or another suitable frequency). Using PWM enables pre-charging to occur without rapidly heating the MOSFETs (e.g., compared to full conduction). In this respect, controller 202 can generate PWM signals for rapidly opening or closing switches 204 and / or 302. According to an embodiment, once the load 116 is charged to a voltage equal to (or within) the voltage of the battery 106, controller 202 can disconnect switches 204 and 302. One or more embodiments may utilize a pulse pattern (e.g., switches 204 and 302 opening and closing with sharp internal features, such as defined millisecond intervals). Using such a pulse pattern can mitigate average power loss and temperature rise in switches 204 and 302. Once the voltage of load 116 equals the voltage of battery 106, or is within the voltage threshold of battery 106 (e.g., 90% or 95%), contactor 112 (e.g., a mechanical contactor) can close, and switches 204 and 302 can open, for example, during normal operation of the vehicle (e.g., during driving or charging).

[0028] According to one embodiment, load 116 may include a capacitor. In this regard, the capacitor can be charged slowly (e.g., 1 to 2 seconds, but other suitable charging times may also be used) by limiting the current flowing from battery 106 into the contactors (e.g., contactors 112 and / or 114). In this regard, load 116 (e.g., the capacitor) can be pre-charged (e.g., until 90% or 95% charged) before the main contactors (e.g., contactors 112 and / or 114) can be closed. In other embodiments, load 116 may include a traction inverter or an OBC capacitor. For example, controller 202 may pre-charge the traction inverter for driving before initiating a drive operation for the corresponding EV. Similarly, controller 202 may pre-charge the OBC capacitor of the corresponding EV before initiating a charging operation for battery 106.

[0029] Turn now Figure 4This document depicts a block diagram of an example non-limiting pre-charge circuit 400 (e.g., a pre-charge architecture) according to one or more embodiments described herein. In various embodiments, the pre-charge circuit 400 may include an HV DC bus 102 (e.g., positive bus 102a and negative bus 102b), a battery 106 (e.g., an HV battery, such as an 800-volt, 600-volt, 400-volt, or other suitable battery), a contactor 112 (e.g., a first contactor), a contactor 114 (e.g., a second contactor), a load 116, a contactor 406 (e.g., a positive fast-charging contactor), a contactor 408 (e.g., a negative fast-charging contactor), and / or a pre-charge module 404. In one or more embodiments, the pre-charge module 404 may include an LV DC-DC converter 108 and / or an OBC 110.

[0030] In the pre-charge circuit 400, both the LV DC-DC converter 108 and the OBC 110 can be connected to the HV DC bus 102 before the main contactors (e.g., contactors 112 and 114) (e.g., on the battery side of contactors 112 and 114). In one or more embodiments, the OBC AC line L1 (e.g., a phase line) and the neutral line (N) can be connected to the HV DC bus 102. Although L1 depicts only one input phase, other suitable input phases can also be combined (e.g., depending on the market), such as a three-phase AC power supply. In one or more embodiments, L1 and N can be connected to the HV DC bus 102 after contactors 112 and 408 (e.g., negative fast-charging contactors). In this respect, L1 can connect the OBC 110 to the positive bus on the load side of the positive bus, while N can connect the on-board charger to the negative bus on the load side of the negative bus. According to an embodiment, L1 can connect OBC 110 to the positive bus 102a on the load side of the positive bus 102a, while N can connect OBC 110 to the negative bus 102b on the load side of the negative bus 102b. In other embodiments, N can connect OBC 110 to the positive bus 102a on the load side of the positive bus 102a, while L1 can connect OBC 110 to the negative bus 102b on the load side of the negative bus 102b. In embodiments, OBC 110 (e.g., a bidirectional OBC) may be capable of having AC power output and / or DC power output. In this regard, OBC 110 may include a DC-DC converter and an inverter. In various embodiments, the DC power output may be used for the pre-charging operation described herein.

[0031] Figure 5A block diagram of an example non-limiting precharge circuit 500 (e.g., a precharge architecture) according to one or more embodiments described herein is shown. In various embodiments, the precharge circuit 500 may include an HV DC bus 102 (e.g., positive bus 102a and negative bus 102b), a battery 106 (e.g., an HV battery, such as an 800-volt, 600-volt, 400-volt, or other suitable battery), a contactor 112 (e.g., a first contactor), a contactor 114 (e.g., a second contactor), a load 116, contactors 406 and 408, an OBC 110, an electric vehicle inlet (EVI) 518, and contactor 506. In one or more embodiments, the OBC 110 may include sub-components (e.g., a DC-DC converter 504, an inverter / rectifier 502, and / or other suitable sub-components). In this embodiment, DC-DC converter 504 may be similar to LV DC-DC converter 108 and may be configured to output a defined and / or controlled (e.g., via controller 202) precharge voltage and current. Switches 508 and 514 may be closed for power flowing through the inverter stage, while switches 510 and 512 may remain open. To complete the precharge circuitry, contactor 408 (e.g., a negative fast-charging contactor) may be closed, thus allowing current to flow through load 116 (e.g., a DC link capacitor) represented by power flow path 516. Once precharge is complete, OBC 110 may stop outputting power by opening switches 508, 514, and contactor 408, while closing contactors 112 and 114. Figure 6 An exemplary timing diagram 600 depicts this sequence. In this respect, line 602 may correspond to the open or closed state of switch 508, line 604 may correspond to the open or closed state of switch 510, line 606 may correspond to the open or closed state of switch 512, line 608 may correspond to the open or closed state of switch 514, line 610 may correspond to the open or closed state of contactor 112, line 612 may correspond to the open or closed state of contactor 114, line 614 may correspond to the open or closed state of contactor 408, line 618 may correspond to the current across load 116, and line 620 may correspond to the voltage across load 116.

[0032] According to an embodiment, the connection point between L1 and N (e.g., after contactors 112 and 408, respectively) (e.g., on the load side) can be used for safety precautions (e.g., to prevent electric shock or electrocution via EVI 518). According to an example, if both connection points (e.g., connection points 520 and 522) are placed after the main contactors (e.g., contactors 112 and 114) (e.g., on the battery side of the main contactors) and before the fast-charging contactors (e.g., contactors 406 and 408) (e.g., on the battery side of the fast-charging contactors), then EVI 518 can be energized when the corresponding EV is in an active mode (e.g., presenting an electric shock or electrocution problem via EVI 518 – only during pre-charging). Therefore, contactor 506 (and / or relay) can be located on L1 between OBC 110 and EVI 518, which can be disconnected during pre-charging operation to disconnect EVI 518 from L1 or another AC phase. Next, in response to (e.g., by controller 202) determining that the pre-charging operation is complete, controller 202 may close contactor 506. In one or more embodiments, by placing OBC 110 and battery 106 before the main contactors (e.g., contactors 112 and 114) (e.g., on the battery side of the main contactors), OBC 110 can access the battery, e.g., before the main contactors (e.g., contactors 112 and 114) are closed. Therefore, OBC 110 can accurately regulate current and voltage (e.g., via DC-DC converter 504). According to embodiments, inverter / rectifier 502 (e.g., OBC 110) can enable H-bridge operation (e.g., the corresponding switches repeatedly turn on and off). It should be noted that the inverter / rectifier 502 of OBC 110 can represent inverter and rectifier functionality (e.g., OBC 110 can perform bidirectional conversion between AC and DC). According to an embodiment, if switches 508 and 514 (e.g., the first pair of MOSFETs) are closed, and switches 510 and 512 (e.g., the second pair of MOSFETs) are open, power can flow steadily along power flow path 516. In various embodiments, OBC 110 may include one or more input phases, depending on the intended market. For example, OBC may include three input phases, one input phase, or other suitable input phases. In various embodiments, L1 may be connected after contactor 112 (e.g., on the load side of contactor 112). The neutral phase (N) may be connected to battery 106 on the return path after contactor 408. Power flow path 516, where power can flow to load 116 for pre-charging, can be achieved by regulating the current and voltage in DC-DC converter 504 and closing one or more switches or contactors herein.

[0033] The systems, circuits, controllers, and / or modules described herein may include memory that stores one or more computer / machine-readable and / or executable components and / or instructions that, when executed by a processor (e.g., a classical processor, a quantum processor, etc.), facilitate the execution of operations defined by the executable components and / or instructions. The memory may include volatile memory (e.g., random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), etc.) and / or non-volatile memory (e.g., read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), etc.), and may employ one or more memory architectures.

[0034] The systems, circuits, controllers, and / or modules described herein may include processors, which may include one or more types of processors and / or electronic circuits (e.g., classical processors, graphics processors, quantum processors, etc.) capable of implementing one or more computer- and / or machine-readable, writable, and / or executable components and / or instructions that can be stored in memory. For example, a processor may perform various operations that can be specified by such computer- and / or machine-readable, writable, and / or executable components and / or instructions, including but not limited to logic, control, input / output (I / O), arithmetic, etc. In some embodiments, the processor described herein may include one or more central processing units, multi-core processors, microprocessors, dual microprocessors, microcontrollers, systems-on-a-chip (SoCs), array processors, vector processors, quantum processors, and / or another type of processor.

[0035] Figure 7A flowchart of an example non-limiting pre-charge process 700 according to one or more embodiments described herein is shown. For brevity, repeated descriptions of similar elements and / or processes employed in corresponding embodiments are omitted. At 702, process 700 may include generating a pre-charge voltage and a pre-charge current via a system including a processor (e.g., via controller 202) and using a DC-DC converter (e.g., LV DC-DC converter 108). At 704, process 700 may include closing a first pair of metal-oxide-semiconductor field-effect transistors (e.g., switches 508 and 514) of the on-board charger (e.g., OBC 110) via the system (e.g., via controller 202). At 706, process 700 may include opening a second pair of metal-oxide-semiconductor field-effect transistors (e.g., switches 510 and 512) of the on-board charger (e.g., OBC 110) via the system (e.g., via controller 202). At 708, process 700 may include disconnecting the first pair of metal-oxide-semiconductor field-effect transistors (e.g., switches 508 and 514) via the system (e.g., via controller 202) in response to determining that the pre-charge operation is complete.

[0036] The system described herein can be coupled (e.g., communication ground, electrical ground, operational ground, optical ground, etc.) to one or more local or remote (e.g., external) systems, sources, and / or devices (e.g., electronic control systems (ECUs), classical and / or quantum computing devices, communication devices, etc.). For example, the system (or other systems, controllers, processors, etc.) described herein can be coupled to one or more local or remote (e.g., external) systems, sources, and / or devices using data cables (e.g., High Definition Multimedia Interface (HDMI), Recommended Standard (RS), Ethernet cables, etc.) and / or one or more wired networks (e.g., communication ground, electrical ground, operational ground, optical ground, etc.) as described below.

[0037] In some embodiments, the system described herein can be coupled via a network (e.g., communication ground, electrical ground, operational ground, optical ground, etc.) to one or more local or remote (e.g., external) systems, sources, and / or devices (e.g., electronic control units (ECUs), classical and / or quantum computing devices, communication devices, etc.). In these embodiments, such a network can include one or more wired and / or wireless networks, including but not limited to cellular networks, wide area networks (WANs) (e.g., the Internet), and / or local area networks (LANs). For example, the system described herein can communicate with one or more local or remote (e.g., external) systems, sources, and / or devices (e.g., computing devices using such a network), which can virtually include any desired wired or wireless technology, including but not limited to: Power Line Ethernet, Wireless Fidelity (Wi-Fi), etc. Fiber optic communication, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), WiMAX, Enhanced Universal Packet Radio Service (Enhanced GPRS), 3GPP Long Term Evolution (LTE), 3GPP2 Ultra Mobile Broadband (UMB), High-Speed ​​Packet Access (HSPA), Zigbee and other 802.XX wireless technologies and / or traditional telecommunications technologies, Session Initiation Protocol (SIP). RF4CE protocol, WirelessHART protocol, 6LoWPAN (IPv6 over low-power wireless LAN), Z-Wave, ANT, ultra-wideband (UWB) standard protocol and / or other proprietary and non-proprietary communication protocols. In this example, the system described herein may therefore include hardware such as a central processing unit (CPU), transceiver, decoder, and antenna (e.g., ultra-wideband (UWB) antenna). Low-power (BLE) antennas, quantum hardware, quantum processors, etc., software (e.g., a set of threads, a set of processes, running software, quantum pulse scheduling, quantum circuits, quantum gates, etc.), or a combination of hardware and software that facilitates communication of information between the system described herein and remote (e.g., external) systems, sources and / or devices (e.g., computing and / or communication devices, such as, for example, smartphones, smartwatches, wireless earbuds, etc.).

[0038] The systems described herein may include one or more computer and / or machine-readable, writable, and / or executable components and / or instructions that, when executed by a processor (e.g., a classical processor, a quantum processor, etc.), facilitate the performance of operations defined by such components and / or instructions. Furthermore, in many embodiments, any component associated with the systems described herein (such as the components described herein with or without reference to the various figures disclosed herein) may include one or more computer and / or machine-readable, writable, and / or executable components and / or instructions that, when executed by a processor, facilitate the performance of operations defined by such components and / or instructions. For example, any component associated with a system as disclosed herein (e.g., communicatively, electronically, operatively, and / or optically coupled to and / or employed by the systems described herein) may include such computer and / or machine-readable, writable, and / or executable components and / or instructions. Therefore, according to the numerous embodiments or systems described herein and / or any components associated therewith as disclosed herein, a processor may be employed to execute such computer and / or machine-readable, writable and / or executable components and / or instructions to facilitate the execution of one or more operations described herein with reference to the systems and / or any such components associated therewith.

[0039] The systems described herein can include any type of system, device, machine, apparatus, component, and / or equipment, including processors and / or capable of communicating with one or more local or remote electronic systems and / or one or more local or remote devices via wired and / or wireless networks. All such embodiments are contemplated. For example, the systems described herein can include computing devices, general-purpose computers, special-purpose computers, in-vehicle computing devices, communication devices, in-vehicle communication devices, server devices, quantum computing devices (e.g., quantum computers), tablet computing devices, handheld devices, server-type computing machines and / or databases, laptop computers, notebook computers, desktop computers, mobile phones, smartphones, consumer appliances and / or machinery, industrial and / or commercial equipment, digital assistants, telephones supporting multimedia internet, multimedia players, and / or another type of device.

[0040] To provide additional context for the various embodiments described herein, Figure 8 The following discussion is intended to provide a brief overview of a suitable computing environment 800 in which the various embodiments of the embodiments described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that these embodiments may also be implemented in combination with other program modules and / or as a combination of hardware and software.

[0041] Typically, program modules include routines, programs, components, and data structures that perform specific tasks or implement specific abstract data types. Furthermore, those skilled in the art will understand that the methods of this invention can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, each of which can be operatively coupled to one or more associated devices.

[0042] The embodiments illustrated in this document can also be practiced in a distributed computing environment, where certain tasks are performed by remote processing devices linked via a communication network. In a distributed computing environment, program modules can reside on both local and remote memory storage devices.

[0043] Computing devices typically include a variety of media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, these two terms being used differently from each other herein. A computer-readable storage medium or a machine-readable storage medium can be any available storage medium that can be accessed by a computer, and includes volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, a computer-readable storage medium or a machine-readable storage medium can be implemented in conjunction with any method or technique for storing information such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0044] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, optical disc read-only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible and / or non-transitory media that can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” used herein to refer to storage, memory, or computer-readable media should be understood to exclude only the propagation of transient signals as a modifier, and not to waive the rights of all standard storage, memory, or computer-readable media that are not only propagators of transient signals.

[0045] One or more local or remote computing devices may access a computer-readable storage medium, for example via an access request, query, or other data retrieval protocol, for various operations relating to the information stored on the medium.

[0046] Communication media typically embody computer-readable instructions, data structures, program modules, or other structured or unstructured data in data signals (such as modulated data signals, e.g., carrier waves or other transmission mechanisms), and include any medium for delivering or transmitting information. The term "one or more modulated data signals" refers to signals whose characteristics are set or altered in a manner that encodes information in one or more signals. By way of example and not limitation, communication media include wired media, such as wired networks or direct wired connections, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0047] Refer again Figure 8An example environment 800 for implementing various embodiments of the aspects described herein includes a computer 802, which includes a processing unit 804, system memory 806, and a system bus 808. The system bus 808 couples system components (including, but not limited to, system memory 806) to the processing unit 804. The processing unit 804 can be any of a variety of commercially available processors. Dual microprocessors and other multiprocessor architectures can also be used as the processing unit 804.

[0048] System bus 808 can be any of several types of bus architectures, which can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. System memory 806 includes ROM 810 and RAM 812. The Basic Input / Output System (BIOS) can be stored in non-volatile memory such as ROM, erasable programmable read-only memory (EPROM), or EEPROM, where the BIOS contains basic routines that facilitate, for example, the transfer of information between components within computer 802 during startup. RAM 812 may also include high-speed RAM, such as static RAM for caching data.

[0049] Computer 802 also includes an internal hard disk drive (HDD) 814 (e.g., EIDE, SATA), one or more external storage devices 816 (e.g., floppy disk drive (FDD) 816, memory stick or flash drive reader, memory card reader, etc.), and an optical disc drive 820 (e.g., capable of reading from or writing to CD-ROMs, DVDs, BDs, etc.). While the internal HDD 814 is shown as residing within computer 802, it may also be configured for external use within a suitable chassis (not shown). Additionally, although not shown in environment 800, a solid-state drive (SSD) may be used to supplement or replace the HDD 814. The HDD 814, external storage devices 816, and optical disc drive 820 may be connected to system bus 808 via HDD interface 824, external storage interface 826, and optical disc drive interface 828, respectively. Interface 824 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external driver connection technologies are within the scope of consideration for the embodiments described herein.

[0050] Drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, etc. For computer 802, drives and storage media are adapted to store any data in a suitable digital format. Although the above description of computer-readable storage media refers to a corresponding type of storage device, those skilled in the art will understand that other types of computer-readable storage media (whether currently existing or developed in the future) may also be used in the example operating environment. Furthermore, any such storage media may contain computer-executable instructions for performing the methods described herein.

[0051] Multiple program modules, including an operating system 830, one or more application programs 832, other program modules 834, and program data 836, can be stored in the drive and RAM 812. All or part of the operating system, application programs, modules, and / or data can also be cached in RAM 812. The systems and methods described herein can be implemented using various commercial operating systems or combinations of operating systems.

[0052] Computer 802 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate the hardware environment of operating system 830, and the emulated hardware may optionally be different from that of operating system 830. Figure 8 The hardware shown is illustrated. In such an embodiment, the operating system 830 may include one of a plurality of virtual machines (VMs) hosted at the computer 802. Furthermore, the operating system 830 may provide a runtime environment for the application 832, such as the Java Runtime Environment or the .NET Framework. A runtime environment is a consistent execution environment that allows the application 832 to run on any operating system that includes a runtime environment. Similarly, the operating system 830 may support containers, and the application 832 may be in the form of a container, which is a lightweight, standalone, executable software package that includes, for example, code, runtime, system tools, system libraries, and application settings.

[0053] Furthermore, a security module, such as a Trusted Processing Module (TPM), can be used to enable computer 802. For example, when using a TPM, the boot component hashes the next boot component in the time-bound boot component before loading the next boot component and waits for the result to match a security value. This process can occur at any layer of the computer 802's code execution stack, for example, at the application execution level or the operating system (OS) kernel level, thereby enabling security at any code execution level.

[0054] Users can input commands and information into computer 802 through one or more wired / wireless input devices (e.g., keyboard 838, touchscreen 840, and pointing devices such as mouse 842). Other input devices (not shown) may include microphones, infrared (IR) remote controls, radio frequency (RF) remote controls or other remote controls, joysticks, virtual reality controllers and / or virtual reality headsets, gaming pads, styluses, image input devices (e.g., cameras, gesture sensor input devices, visual motion sensor input devices), emotion or face detection devices, biometric input devices (e.g., fingerprint or iris scanners), etc. These and other input devices are typically connected to processing unit 804 via input device interface 844, which can be coupled to system bus 808, but may also be connected via other interfaces (e.g., parallel ports, IEEE 1394 serial ports, gaming ports, USB ports, IR interfaces, etc.). (Interfaces, etc.) connections.

[0055] Monitor 846 or other types of display devices can also be connected to system bus 808 via an interface (such as video adapter 848). In addition to monitor 846, computers typically include other peripheral output devices (not shown), such as speakers, printers, etc.

[0056] Computer 802 can operate in a networked environment using logical connections via wired and / or wireless communications to one or more remote computers (such as remote computer 850). Remote computer 850 can be a workstation, server computer, router, personal computer, laptop computer, microprocessor-based entertainment device, peer-to-peer device, or other public network node, and typically includes many or all of the elements described relative to computer 802; however, for simplicity, only memory / storage device 852 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 854 and / or a larger network (e.g., a wide area network (WAN) 856). Such LAN and WAN networking environments are prevalent in offices and companies and facilitate enterprise-wide computer networks such as intranets, all of which can connect to global communication networks, such as the Internet.

[0057] When used in a LAN networking environment, computer 802 can connect to local network 854 via a wired and / or wireless communication network interface or adapter 858. Adapter 858 can facilitate wired or wireless communication to LAN 854, which may also include a wireless access point (AP) configured thereon for communicating with adapter 858 in wireless mode.

[0058] When used in a WAN networking environment, computer 802 may include modem 860, or may be connected to a communication server on WAN 856 via other means for establishing communication over WAN 856 (such as via the Internet). Modem 860 (which may be internal or external, wired or wireless) may be connected to system bus 808 via input device interface 844. In a networking environment, program modules depicted relative to computer 802 or parts thereof may be stored in remote memory / storage device 852. It should be understood that the network connections shown are exemplary, and other means of establishing communication links between computers may be used.

[0059] When used in a LAN or WAN networking environment, computer 802 can access cloud storage systems or other network-based storage systems to supplement or replace external storage device 816 as described above. Typically, the connection between computer 802 and the cloud storage system can be established on LAN 854 or WAN 856 via, for example, adapter 858 or modem 860. When computer 802 is connected to the associated cloud storage system, external storage interface 826 can manage the storage provided by the cloud storage system with the help of adapter 858 and / or modem 860, just as it would manage other types of external storage. For example, external storage interface 826 can be configured to provide access to cloud storage sources as if these sources were physically connected to computer 802.

[0060] Computer 802 may be operable to communicate with any wireless device or entity operatively configured to conduct wireless communication, such as a printer, scanner, desktop and / or laptop computer, portable data assistant, communications satellite, any equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, newsstand, shelf, etc.), and telephone. This may include Wi-Fi and Wireless technology. Therefore, the communication can be the same predefined structure as a regular network, or simply self-organizing communication between at least two devices.

[0061] Now for reference Figure 9 This diagram illustrates a schematic block diagram of a computing environment 900 according to this specification. System 900 includes one or more clients 902 (e.g., computers, smartphones, tablets, cameras, PDAs). Client 902 can be hardware and / or software (e.g., threads, processes, computing devices). For example, client 902 can utilize this specification to contain cache files and / or associated context information.

[0062] System 900 also includes one or more servers 904. Server 904 can also be hardware or a combination of hardware and software (e.g., threads, processes, computing devices). For example, server 904 can accommodate threads to perform transformations of media items by employing aspects of this disclosure. One possible communication between client 902 and server 904 can be in the form of data packets suitable for transmission between two or more computer processes, wherein the data packets may include encoded analysis headspace and / or input. For example, the data packets may include cached files and / or associated context information. System 900 includes a communication framework 906 (e.g., a global communication network such as the Internet) that can be used to facilitate communication between client 902 and server 904.

[0063] Communication can be facilitated via wired (including fiber optic) and / or wireless technologies. Client 902 is operatively connected to one or more client data stores 908, which can be used to store information local to client 902 (e.g., cached files and / or associated context information). Similarly, server 904 is operatively connected to one or more server data stores 910, which can be used to store information local to server 904.

[0064] In one exemplary embodiment, client 902 may transmit an encoded file (e.g., an encoded media item) to server 904. Server 904 may store the file, decode the file, or send the file to another client 902. It should be understood that, according to this disclosure, client 902 may also transmit an uncompressed file to server 904, and server 904 may compress and / or transform the file. Similarly, server 904 may encode information and send it to one or more clients 902 via communication framework 906.

[0065] The aspects shown in this disclosure can also be practiced in a distributed computing environment, where certain tasks are performed by remote processing devices linked via a communication network. In a distributed computing environment, program modules can reside on both local and remote memory storage devices.

[0066] The above description includes non-limiting examples of the various embodiments. It is certainly not possible to describe every possible combination of components or methods in order to describe the disclosed subject matter, and those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. The disclosed subject matter is intended to cover all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

[0067] Regarding the various functions performed by the components, devices, circuits, systems, etc., described above, unless otherwise indicated, the terminology used to describe such components (including references to "part") is intended to also include any structure (e.g., functional equivalent) that performs the specified function of the described component, even if it is not structurally equivalent to the disclosed structure. Furthermore, while specific features of the disclosed subject matter may have been disclosed with respect to only one of several embodiments, such features may be combined with one or more other features of other embodiments, as this is desirable and advantageous for any given or particular application.

[0068] As used herein, the terms “exemplary” and / or “illustrative” are intended to mean as an example, instance, or illustration. For the avoidance of ambiguity, the subject matter disclosed herein is not limited to such examples. Furthermore, any aspect or design described herein as “exemplary” and / or “illustrative” is not necessarily to be construed as preferred or superior to other aspects or designs, nor does it exclude equivalent structures and techniques known to those skilled in the art. Moreover, to the extent that the terms “comprising,” “having,” “including,” and other similar words are used in the Detailed Description or any of the claims, such terms are intended to be inclusive—in a manner similar to the open transitional term “comprising”—and do not exclude any additional or other elements.

[0069] As used herein, the term “or” is intended to mean inclusive “or” rather than exclusive “or.” For example, the phrase “A or B” is intended to include instances of A, B, and both A and B. Additionally, unless otherwise specified or explicitly stated in the context for the singular form, the article “a” as used in this application and the appended claims should generally be interpreted as meaning “one or more”.

[0070] As used herein, the term "set" does not include an empty set, i.e., a set containing no elements. Therefore, "set" in this subject matter disclosure includes one or more elements or entities. Similarly, as used herein, the term "group" refers to a collection of one or more entities.

[0071] The description of the embodiments shown in the subject matter disclosure herein (including the description in the abstract) is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples have been described herein for illustrative purposes, various modifications are possible within the scope of such embodiments and examples, as will be appreciated by those skilled in the art. In this regard, although the subject matter has been described herein in conjunction with various embodiments and corresponding drawings, it should be understood where applicable that other similar embodiments may be used, or modifications and additions may be made to the described embodiments to perform the same, similar, alternative, or substitutive functions of the disclosed subject matter without departing from them. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted in accordance with the breadth and scope of the following appended claims.

[0072] Other aspects of the invention are provided by the subject matter of the following provisions:

[0073] 1. A pre-charging circuit for an electric vehicle, comprising:

[0074] The first contactor is located on the positive bus between the load and the battery;

[0075] A second contactor, the second contactor being located on the negative bus between the load and the battery; and

[0076] An on-board charger, wherein the on-board charger is connected to the positive bus and the negative bus on the battery side of the positive bus and the battery side of the negative bus, wherein the phase line connects the on-board charger to the positive bus on the load side of the positive bus, and wherein the neutral line connects the on-board charger to the negative bus on the load side of the negative bus.

[0077] 2. The electric vehicle pre-charging circuit according to any of the foregoing clauses further includes:

[0078] A switch located on the phase line between the on-board charger and the electric vehicle socket.

[0079] 3. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the on-board charger performs bidirectional conversion between AC and DC power.

[0080] 4. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the on-board charger includes one or more metal-oxide-semiconductor field-effect transistors.

[0081] 5. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the load includes a capacitor.

[0082] 6. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the load includes a traction inverter.

[0083] 7. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the battery includes an 800-volt battery.

[0084] 8. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the battery includes a 400-volt battery.

[0085] 9. The electric vehicle pre-charging circuit according to Clause 1 above, comprising a set of any combination of the electric vehicle pre-charging circuits 2 to 8.

[0086] 10. A pre-charging circuit for an electric vehicle, comprising:

[0087] The first contactor is located on the positive bus between the load and the battery;

[0088] The second contactor is located on the negative bus between the load and the battery;

[0089] An on-board charger, wherein the on-board charger is connected to the positive bus and the negative bus on the load side of the positive bus and the load side of the negative bus; and

[0090] A metal-oxide-semiconductor field-effect transistor (MOSFET) switch, the MOSFET switch being connected to the positive bus on the battery side of the first contactor and to the on-board charger.

[0091] 11. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the MOSFET switch includes a first MOSFET switch, and wherein the electric vehicle pre-charging circuit further includes:

[0092] A second MOSFET switch is located between the first MOSFET switch and the vehicle charger.

[0093] 12. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the body diodes of the first MOSFET switch and the second MOSFET switch are oriented in opposite directions.

[0094] 13. The electric vehicle pre-charging circuit according to any of the foregoing clauses further includes:

[0095] A DC-to-DC converter, wherein the DC-to-DC converter is connected to the positive bus on the battery side of the first contactor and to the negative bus on the battery side of the second contactor.

[0096] 14. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the load includes a capacitor.

[0097] 15. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the load includes a traction inverter.

[0098] 16. The electric vehicle pre-charging circuit according to any of the foregoing clauses further includes a controller, the controller including a memory and a processor, wherein the controller disconnects or closes the MOSFET switch until the voltage of the battery is equal to the voltage of the load.

[0099] 17. The electric vehicle pre-charging circuit according to any of the foregoing clauses, wherein the controller sends a pulse width modulation signal to the MOSFET switch to open or close the MOSFET switch.

[0100] 18. The electric vehicle pre-charging circuit according to Clause 10 above, having a set of any combination of the electric vehicle pre-charging circuits 11 to 17 above.

[0101] 19. A method comprising:

[0102] The pre-charge voltage and pre-charge current are generated by using a system that includes a processor and a DC-to-DC converter.

[0103] The system closes the first pair of metal-oxide-semiconductor field-effect transistors of the on-board charger;

[0104] The system disconnects the second pair of metal-oxide-semiconductor field-effect transistors of the on-board charger; and

[0105] In response to determining that the pre-charge operation is complete, the first pair of metal-oxide-semiconductor field-effect transistors are disconnected by the system.

[0106] 20. The method described under any of the foregoing provisions further includes:

[0107] In response to disconnecting the first pair of metal-oxide-semiconductor field-effect transistors, the negative fast-charging contactor is closed by the system.

[0108] 21. The method described under any of the foregoing provisions further includes:

[0109] During the pre-charging operation, the contactor on the phase line located between the on-board charger and the electric vehicle socket is disconnected by the system.

[0110] 22. The method described under any of the foregoing provisions further includes:

[0111] In response to determining that the pre-charging operation is complete, the system closes the contactor on the phase line located between the on-board charger and the electric vehicle socket.

[0112] 23. The method described in accordance with Clause 19 above, having a set of any combination of methods 20 to 22 above.

Claims

1. A pre-charging circuit for an electric vehicle, comprising: The first contactor is located on the positive bus between the load and the battery; The second contactor is located on the negative bus between the load and the battery; as well as A pre-charging module, integrated into the electric vehicle pre-charging circuit between the load and the battery, wherein the pre-charging module includes a low-voltage DC-DC converter, an on-board charger, and a resistor. The low-voltage DC-to-DC converter is connected to the positive bus and the negative bus on the battery side of the positive bus and the battery side of the negative bus, respectively. The on-board charger is connected to the positive bus and the negative bus via the battery side of the positive bus and the battery side of the negative bus, respectively. The phase wire connects the on-board charger to the load side of the positive bus, and the neutral wire connects the on-board charger to the load side of the negative bus. The resistor is connected between the load and the battery.

2. The electric vehicle pre-charging circuit according to claim 1, further comprising: A switch located on the phase line between the on-board charger and the electric vehicle socket.

3. The electric vehicle pre-charging circuit according to claim 1, wherein the on-board charger performs bidirectional conversion between AC and DC power.

4. The electric vehicle pre-charging circuit according to claim 3, wherein the on-board charger comprises one or more metal-oxide-semiconductor field-effect transistors.

5. The electric vehicle pre-charging circuit according to claim 1, wherein the load includes a capacitor.

6. The electric vehicle pre-charging circuit according to claim 1, wherein the load includes a traction inverter.

7. The electric vehicle pre-charging circuit according to claim 1, wherein the battery comprises an 800-volt battery.

8. The electric vehicle pre-charging circuit according to claim 1, wherein the battery comprises a 400-volt battery.

9. The electric vehicle pre-charging circuit according to claim 1 further includes: A metal-oxide-semiconductor field-effect transistor (MOSFET) switch, wherein the MOSFET switch is connected to the positive bus on the battery side of the first contactor and to the on-board charger.

10. The electric vehicle pre-charging circuit according to claim 9, wherein the MOSFET switch includes a first MOSFET switch, and wherein the electric vehicle pre-charging circuit further includes: A second MOSFET switch is located between the first MOSFET switch and the vehicle charger.

11. The electric vehicle pre-charging circuit according to claim 10, wherein the body diodes of the first MOSFET switch and the second MOSFET switch are in opposite directions.

12. The electric vehicle pre-charging circuit according to claim 1, wherein the load includes a capacitor.

13. The electric vehicle pre-charging circuit according to claim 9, wherein the load includes a traction inverter.

14. The electric vehicle pre-charging circuit of claim 9, further comprising a controller including a memory and a processor, wherein the controller disconnects or closes the MOSFET switch until the voltage of the battery is equal to the voltage of the load.

15. The electric vehicle pre-charging circuit of claim 14, wherein the controller sends a pulse width modulation signal to the MOSFET switch to open or close the MOSFET switch.

16. A method for precharging an electric vehicle, comprising: The pre-charge voltage and pre-charge current are generated by using a system that includes a processor and a DC-to-DC converter. The system closes the first pair of metal-oxide-semiconductor field-effect transistors of the on-board charger; The system disconnects the second pair of metal-oxide-semiconductor field-effect transistors of the on-board charger, wherein the first pair of metal-oxide-semiconductor field-effect transistors and the second pair of metal-oxide-semiconductor field-effect transistors constitute a rectifier, and the rectifier is connected in parallel with the DC-DC converter; as well as In response to determining that the pre-charge operation is complete, the first pair of metal-oxide-semiconductor field-effect transistors are disconnected by the system.

17. The method of claim 16, further comprising: In response to disconnecting the first pair of metal-oxide-semiconductor field-effect transistors, the negative fast-charging contactor is closed by the system.

18. The method of claim 16, further comprising: During the pre-charging operation, the contactor on the phase line located between the on-board charger and the electric vehicle socket is disconnected by the system.

19. The method of claim 18, further comprising: In response to determining that the pre-charging operation is complete, the system closes the contactor on the phase line located between the on-board charger and the electric vehicle socket.

20. A system for precharging an electric vehicle, comprising: Memory, the memory storing computer-executable programs; as well as A processor that executes at least one computer-executable program to perform the method according to any one of claims 16-19.

Images