Systems and methods for initializing, transmitting, and charging vehicle-to-load charging sessions.

Abstract

Various embodiments disclosed in this invention include an exemplary non-transitory computer-readable medium for a controller of a vehicle-to-load (V2X) charging device, a controller for a V2X charging device, and a V2X charging device. In an exemplary embodiment, the non-transitory computer-readable medium stores computer-executable instructions therein, which, when executed on a processor, are configured to cause the processor to: determine that the protocol to be followed in the charging session is a V2X charging session from a supplier vehicle; initialize the V2X charging session from the supplier vehicle; perform an isolation check on the V2X charging device from the supplier vehicle; and pre-charge the V2X charging device.

Description

[0001] introduction

[0002] This disclosure relates to electric vehicle charging.

[0003] DC fast charging (DCFC) stations can provide DC power to electric vehicles to charge their high-voltage batteries. The standard DIN 70121 addresses the transfer, establishment, and initialization of charging sessions to transfer energy from a DCFC charging station to an electric vehicle.

[0004] Electric vehicles can act as DC power sources to transfer energy to load devices via V2X devices that include DC / DC power converters (referred to as vehicle-to-load (V2X) charging). A V2X charging session should appear to the receiving end (i.e., the load) as if it were charging from a DC fast-charging station. However, no currently known standard has resolved the transmission, establishment, and initialization of charging sessions to transfer energy from an electric vehicle acting as a DC power source to a load device used for a V2X charging session.

[0005] The statements in this section are provided only as background information in connection with this disclosure and do not constitute prior art. Summary of the Invention

[0006] Various disclosed embodiments include exemplary non-transitory computer-readable media for a controller of a V2X charging device, a controller of a V2X charging device, and a V2X charging device. Therefore, various disclosed embodiments provide exemplary systems and methods for initializing, transmitting a V2X charging session, and charging a receiving load from a supplier vehicle during a V2X charging session.

[0007] In an exemplary embodiment, a non-transitory computer-readable medium stores computer-executable instructions therein, which, when executed on a processor, are configured to cause the processor to: determine that the protocol to be followed in the charging session is a vehicle-to-load (V2X) charging session from the supplier vehicle; initialize the V2X charging session from the supplier vehicle; perform an isolation check on the V2X charging device from the supplier vehicle; and precharge the V2X charging device.

[0008] In another exemplary embodiment, the controller includes a processor and a non-transitory computer-readable medium therein storing computer-executable instructions configured, when executed on the processor, to cause the processor to: determine that the protocol to be followed in the charging session is a vehicle-to-load (V2X) charging session from the supplier vehicle; initialize the V2X charging session from the supplier vehicle; perform an isolation check on the V2X charging device from the supplier vehicle; and precharge the V2X charging device.

[0009] In another exemplary embodiment, the V2X charging device includes a high-voltage DC-DC converter, a DC bus charging module, and a controller. The controller includes a processor and a non-transitory computer-readable medium storing computer-executable instructions therein, configured, when executed on the processor, to cause the processor to: determine that the protocol to be followed in the charging session is a V2X charging session from the supplier vehicle; initialize the V2X charging session from the supplier vehicle; cause the DC bus charging module to perform an isolation check on the V2X charging device from the supplier vehicle; and cause the DC bus charging module to pre-charge the DC-DC converter.

[0010] The above description of the invention is merely illustrative and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, other aspects, embodiments, and features will become apparent from the accompanying drawings and the following detailed description. Attached Figure Description

[0011] Exemplary embodiments are shown in the accompanying drawings. The embodiments and drawings disclosed herein are intended to be illustrative and not restrictive.

[0012] Figure 1A It is a block diagram in the form of a partial schematic diagram of an exemplary vehicle-to-load (V2X) charging device, a supplier vehicle, and a receiver load.

[0013] Figure 1B yes Figure 1A Block diagram of a V2X charging device.

[0014] Figure 1C yes Figure 1A and Figure 1B A block diagram detailing the V2X charging device.

[0015] Figure 2 It is a state diagram illustrating the methods for V2X initialization, transmission, and charging.

[0016] Figure 3 This is a sequence diagram of the stages in an exemplary V2X charging session.

[0017] Figure 4 This is a flowchart illustrating an exemplary V2X method.

[0018] Similar reference symbols in various diagrams generally indicate similar elements. Detailed Implementation

[0019] In the following detailed description, reference is made to the accompanying drawings, which form part of the detailed description. In the drawings, like reference numerals generally identify like parts unless the context otherwise indicates. The exemplary embodiments described in the detailed description, drawings, and claims are not intended to be limiting. Other embodiments may be utilized and other changes may be made without departing from the spirit or scope of the subject matter presented herein.

[0020] By way of overview, various disclosed embodiments include exemplary non-transitory computer-readable media for a controller of a V2X charging device, a controller of a V2X charging device, and a V2X charging device. Therefore, various disclosed embodiments provide exemplary systems and methods for initializing, transmitting a V2X charging session, and charging a receiving load from a supplier vehicle during a V2X charging session.

[0021] Still through overview and reference Figures 1A to 1C An exemplary vehicle-to-load (V2X) charging device 10 includes a high-voltage direct current (DC) to direct current converter 12. Figure 1B and Figure 1C ), DC bus charging module 18 ( Figure 1B and Figure 1C ) and controller 11. Controller 11 includes a processor 13 and a non-transitory computer-readable medium 15 therein storing computer-executable instructions, which, when executed on the processor 13, are configured to cause the processor 13 to: determine that the protocol to be followed in the charging session is from the supplier vehicle 20 ( Figure 1A and Figure 1B The system initiates a V2X charging session from the supplier vehicle 20; performs an isolation check on the V2X charging device 10 from the supplier vehicle 20 via the DC bus charging module 18; and pre-charges the DC-DC converter 12 via the DC bus charging module 18. A human-machine interface (HMI) 17, such as a control and display panel, is operatively coupled to the controller 11.

[0022] By way of a non-limiting overview, it should be understood that various implementations may help allow V2X charging devices (such as, but not limited to, V2X charging device 10) and supplier vehicles (such as, but not limited to, supplier vehicle 20) to act as equivalents of (composite unit) DC fast charging (DCFC) stations.

[0023] Since an overview has already been given in a non-limiting manner, the details of the various disclosed implementations will be illustrated below by non-limiting examples given only in an illustrative and non-limiting manner.

[0024] The exemplary V2X charging device will first be described by way of non-limiting examples given in an illustrative rather than restrictive manner. After the exemplary V2X charging device has been described, an exemplary process for controlling a V2X charging session will be described.

[0025] Still referencing Figures 1A to 1C In various embodiments, the exemplary V2X charging device 10 includes a high-voltage DC-DC converter 12, a charge storage device C1 electrically connectable to an input 16 of the DC-DC converter 12, and a DC bus charging module 18. In various embodiments, the DC bus charging module 18 includes any suitable DC boost converter required for a particular application, such as, but not limited to, a flyback converter. Those skilled in the art do not need an explanation of the details of the construction and operation of the DC boost converter to understand the disclosed subject matter.

[0026] The DC bus charging module 18 is configured to: apply an output DC voltage from the DC bus charging module 18 having a first voltage level to a DC bus cable 14 electrically connected to an input 16 of the DC-DC converter 12, wherein the DC bus cable 14 is disconnected from the first DC voltage source BT1; and charge the charge storage device C1 with an output DC voltage from the DC bus charging module 18 having a second voltage level different from the first voltage level, wherein the DC bus cable 14 is disconnected from the first DC voltage source BT1.

[0027] It should be understood that, in various embodiments, the insulation of the DC bus cable 14 can be verified without being electrically connected to the first DC voltage source BT1 (such as the high-voltage DC battery of the supplier vehicle 20), and in various embodiments, the DC-DC converter 12 can be pre-charged without being electrically connected to the first DC voltage source BT1.

[0028] It should be understood that V2X charging sessions associated with various publicly available implementations require the use of a V2X charging device 10 that is plugged between the supplier vehicle 20 and the receiver load 22. For example... Figure 1A and Figure 1B As shown, the exemplary V2X charging device 10 (sometimes referred to as a "V2X device" and / or a "V2V device") includes a DC-DC converter 12. A DC bus cable 14 is configured to electrically connect the V2X charging device 10 to the supplier vehicle 20, and a cable 24 electrically connects the V2X charging device 10 to the receiver load 22.

[0029] In various embodiments, DC bus cable 14 and cable 24 include any suitable cable configured to distribute high-voltage DC power (such as approximately 450V). Since DC bus cable 14 is configured to distribute high-voltage DC power from supplier vehicle 20, in various embodiments, DC bus cable 14 includes a suitable connector configured to electrically connect DC bus cable 14 to V2X charging device 10. In various embodiments, such suitable connectors may include, but are not limited to, Combined Charge System (CCS) Type 1 and / or Type 2 couplers, CHAdeMo couplers, GB / T couplers, Tesla connectors, etc. In various embodiments, cable 24 also includes a suitable connector configured to electrically connect cable 24 to V2X charging device 10. In various embodiments, such suitable connectors may also include, but are not limited to, Combined Charge System (CCS) Type 1 and / or Type 2 couplers, CHAdeMo couplers, GB / T couplers, Tesla connectors, etc.

[0030] In various embodiments, the V2X charging device 10 includes switches S4a and S4b inserted between the input terminals of the DC-DC converter 12 and the DC bus cable 14, and switches S5a and S5b inserted between the output terminals of the DC-DC converter 12 and the cable 24. The DC-DC converter 12 adjusts the DC voltage level of the DC power supplied by the supplier vehicle 20 as needed for charging the receiver load 22. That is, the DC-DC converter 12 can increase and / or decrease the DC voltage of the electrical energy supplied from the supplier vehicle 20 to match the operating voltage of the receiver load 22.

[0031] It should be understood that, in various implementations and as will be described below, the receiving load 22 may transmit charging limits, voltage limits and / or charging status, enabling the V2X charging device 10 to take desired actions to facilitate safe energy transfer, such as, for example, requiring the supply vehicle 20 to close contactors (such as, for example, switches S3a and S3b) to perform energy transfer, or searching for faults on the supply vehicle 20 or the receiving load 22.

[0032] Although the V2X charging device 10 may be referred to as a “V2V device” and the receiving load 22 may be referred to as a “receiving vehicle”, it should be understood that the receiving load 22 is not limited to a vehicle, but may be any load required, a battery or battery pack, any suitable energy storage device such as a capacitor or capacitor bank, an energy storage system with a battery and / or an energy storage system with a solar cell with associated electronics, etc.

[0033] In various embodiments, the V2X charging device 10 includes a high-voltage DC-DC converter 12. A DC bus cable 14 is electrically connected to an input 16 of the DC-DC converter 12. A charge storage device C1 is electrically connected to an input 16 of the DC-DC converter 12. A DC bus charging module 18 is configured to: apply an output DC voltage from the DC bus charging module 18 having a first voltage level to the DC bus cable 14, wherein the DC bus cable 14 is disconnected from the DC voltage source BT1; and charge the charge storage device C1 with an output DC voltage from the DC bus charging module 18 having a second voltage level different from the first voltage level, wherein the DC bus cable 14 is disconnected from the DC voltage source BT1.

[0034] In various embodiments, DC-DC converter 12 converts the input DC voltage from the DC voltage source BT1 of the supplier vehicle into the requested output DC voltage supplied to the receiver load 22. DC-DC converter 12 is any suitable DC-DC converter required for a particular application. Those skilled in the art need not explain the details of the construction and operation of DC-DC converter 12 to understand the disclosed subject matter.

[0035] In various embodiments, the DC-DC converter 12 includes a charge storage device C1, and the charge storage device C1 is electrically connected within the DC-DC converter 12 across the terminals of the input 16 of the DC-DC converter 12. In some embodiments, the charge storage device C1 may be provided separately from the DC-DC converter 12. In such embodiments, the charge storage device C1 is electrically connected across the terminals of the input 16 of the DC-DC converter 12 between switches S4a and S4b and the terminals of the input 16 of the DC-DC converter 12.

[0036] Regardless of the location of the charge storage device C1, as discussed herein, the charge storage device C1 is charged to the DC voltage of the DC voltage source BT1 by the DC bus charging module 18 before the DC voltage source BT1 is electrically connected to the DC-DC converter 12. Therefore, when the charge storage device C1 is charged to the DC voltage of the DC voltage source BT1, the input 16 of the DC-DC converter 12 is already at the DC voltage level of the DC voltage source BT1 when the DC voltage source BT1 is electrically connected to the V2X charging device 10. The charge storage device C1 is any suitable charge storage device as required, such as a capacitor.

[0037] In various embodiments, the DC boost converter 26 is configured to receive an input DC voltage from any suitable DC voltage source, such as, but not limited to, an auxiliary low-voltage source, a DC power source (such as those that convert alternating current (AC), light, heat, etc., into DC power), one or more batteries (rechargeable or disposable batteries), an electrical or electronic device capable of supplying DC power, etc. The input DC voltage has a voltage level lower than the output DC voltage of the DC boost converter (i.e., a first voltage level and a second voltage level). The input DC voltage can have any suitable voltage level required for a particular application. For example, in some embodiments, the input DC voltage can be 12V. In some other embodiments, the input DC voltage can be 4V or, in some cases, 3.65V. However, it is emphasized that the input DC voltage can have any suitable voltage level required for a particular application.

[0038] DC boost converter 26 is configured to convert an input DC voltage to an output DC voltage (having a voltage level greater than the input DC voltage). In various embodiments, DC boost converter 26 converts the input DC voltage to an output DC voltage with a voltage level of approximately 500V to be applied to DC bus cable 14 (before switches s4a and s4b) to verify the insulation of DC bus cable 14 (i.e., to perform an isolation check). However, any output DC voltage level suitable for verifying the insulation of DC bus cable 14 can be used. In various embodiments, DC boost converter 26 converts the input DC voltage to an output DC voltage with a voltage level of approximately 450V to charge charge storage device C1 to the DC voltage of DC voltage source BT1. However, any output DC voltage level corresponding to the DC voltage of DC voltage source BT1 can be used. In various embodiments, DC boost converter 26 is suitably a flyback converter. However, it should be understood that DC boost converter 26 can be any suitable boost converter as needed.

[0039] In various embodiments, connector 52 of DC bus cable 14 (as described above) is inserted into socket 54 of the supplier vehicle, which is electrically connected to DC voltage source BT1. Connector 56 of DC bus cable 14 (as described above) is inserted into socket 58 of V2X charging device 10. Connector 60 of cable 24 is inserted into socket 62 of receiver load 22. Connector 64 of cable 24 is inserted into socket 66 of V2X charging device 10. As described above, in various embodiments, connectors 52, 56, 60, and 64 and sockets 54, 58, 62, and 66 may include, but are not limited to, Combined Charging System (CCS) Type 1 and / or Type 2 connectors and sockets, CHAdeMo connectors and sockets, GB / T connectors and sockets, Tesla connectors and sockets, etc.

[0040] like Figure 1C As shown, in various disclosed embodiments, the V2X charging device 10 may include additional components, and the details listed below are for illustrative purposes only and are not intended to be limiting.

[0041] like Figure 1C As shown, in various embodiments, the V2X charging device 10 includes supplier and receiver cable sockets 58 and 66, an auxiliary low-voltage connector 67, a bootstrap power supply circuit 69, a bus charging module 18, and a controller 11.

[0042] In various embodiments, the V2X charging device 10 also includes a communication subsystem comprising a supplier vehicle communication device 80, such as a supplier modem like a power line communication (PLC) chip / board; a receiver vehicle communication device 82, such as a receiver modem like a power line communication (PLC) chip / board; and / or a radio frequency (RF) transceiver 83, such as a WiFi chip / board and / or a Bluetooth chip / board. In such embodiments, in response to the controller 11, the supplier vehicle communication device 80, the receiver vehicle communication device 82, and the RF transceiver 83 can electrically communicate with the supplier vehicle 20 and the receiver load 22, respectively. The communication subsystem can electrically communicate with the supplier vehicle 20 and the receiver load 22 via power line communication (PLC) and / or wireless communication for higher-level communication, and via a control pilot CP for lower-level communication. In various embodiments, the V2X charging device 10 also includes isolation monitoring devices 74 and 76 and a DC-DC converter 12.

[0043] In various embodiments, an auxiliary low-voltage source may be electrically connected to a low-voltage connector 67. The supplier vehicle 20 and the receiver load 22 are connected to the V2X charging unit 10 via cable receptacles 58 and 66, respectively. In various embodiments, the voltage supplied by the auxiliary low-voltage source charges the initial startup components of the V2X charging unit 10 (such as, for example, controller 11, isolation monitoring devices 74 and 76, supplier vehicle communication device 80, and receiver vehicle communication device 82) via a bootstrap power circuit 69. For example, in various embodiments, the auxiliary low-voltage source may provide approximately 4V (3.65V in some embodiments) DC voltage to a maximum of approximately 12VDC voltage to the bootstrap power circuit 69 and the bus charging module 18. The bootstrap power circuit 69 generates a 12V operating voltage from the voltage of the auxiliary low-voltage source. The bus charging module 18 generates an insulation check voltage of approximately 500VDC and a pre-charge voltage of approximately 400VDC-450VDC from the voltage of the auxiliary low-voltage source.

[0044] The bootstrap power supply circuit 69 converts the voltage output from the auxiliary low-voltage source into a voltage value acceptable to the initial startup components of the V2X charging device 10. After the initial startup components have been adequately powered, the controller 11 instructs the bus charging module 18 to convert the voltage from the auxiliary low-voltage source into a value suitable for preparing the DC-DC converter 12.

[0045] Now that the V2X charging device 10 has been described, an exemplary process for controlling a V2X charging session will be described below (controlled by the controller 11 via the processor 13).

[0046] For further reference Figure 2 and Figure 3 In various implementations, the reference control pilot (CP) states describe the process used to control a V2X charging session in a sequence of stages. The CP states are defined by SAE J1772.

[0047] During the unpaired or disconnected sequence phase in state A (standby), with switches s3a, s3b, s4a, and s4b open, cable 14 is connected to the supplier vehicle 20 via connector 52 (such as a CCS connector) and socket 54 (such as a CCS socket), and to the V2X charging device 10 via connector 56 (such as a CCS connector) and socket 58 (such as a CCS socket). With switches s5a and s5b open, cable 24 is connected to the receiver load 22 via connector 60 (such as a CCS connector) and socket 62 (such as a CCS socket), and to the V2X charging device 10 via connector 64 (such as a CCS connector) and socket 66 (such as a CCS socket).

[0048] When cable 14 is inserted into the supplier vehicle 20 and the V2X charging device 10, the CP state changes from state A (standby) to state B (vehicle detected). Various processes are executed during the initialization sequence phase of state B.

[0049] The Signal Line Attenuation Characterization (SLAC) protocol is executed to verify that the supplier vehicle 20 and the V2X charging unit are electrically connected to each other via cable 14.

[0050] Controller 11 determines that the protocol to be followed in the charging session is a vehicle-to-load (V2X) charging session from supplier vehicle 20. In various implementations and as... Figure 2As shown, a unique namespace is declared. In such embodiments, the instructions are further configured to cause the processor 13 to determine, in response to recognizing the namespace of the supported vehicle, that the protocol to be followed in the charging session is a V2X charging session from the supplier vehicle 20. The namespace indicates that the protocol to be followed is the protocol for charging from the vehicle (i.e., supplier vehicle 20), rather than the standard protocol for charging that vehicle. Using the namespace, supplier vehicle 20 is able to recognize that a V2X charging session from supplier vehicle 20 has been initiated.

[0051] After declaring the namespace, the V2X charging device 10 awaits a response from the supplier vehicle 20, and the supplier vehicle 20 awaits user input (or some other authorization) to establish a charging session. For example, in some implementations, authorization to establish a charging session may be provided from, for example, but not limited to, a technician or other authorized user, an offline server, etc.

[0052] Users provide input via human-machine interfaces (HMIs) such as the HMI 17 of the V2X charging device 10, the infotainment system of the supplier vehicle 20, lights on the charging port, etc., and the V2X charging device 10 initiates a V2X charging session from the supplier vehicle 20. In various embodiments, instructions are further configured to cause the processor 13 to initiate the V2X charging session from the supplier vehicle 20 via high-level communication between the V2X charging device 10 and the supplier vehicle 20 via power line communication (PCL) through the communication device 80 or wireless communication such as WiFi or Bluetooth through the RF transceiver 83.

[0053] Users can input any desired charging parameters. In various implementations, the instructions are further configured to cause processor 13 to initialize a V2X charging session from supplier vehicle 20 in response to at least one supplier vehicle parameter such as the end mileage of supplier vehicle 20, the charging period, and / or a certain amount of energy transferred from supplier vehicle 20. For example, in some implementations, supplier vehicle 20 may set its end mileage as the default parameter for energy transfer. In some such implementations, the end mileage may be set to the mileage required to complete the route (if a route has been entered), the distance to the nearest DC fast charging station, or a default value based on user settings to ensure the user has sufficient mileage. As another example, the user can input a certain amount of energy in units such as kilowatt-hours. However, it should be understood that any charging parameters can be input as needed.

[0054] If the V2X device delivers power to the energy storage system, the user can also set a desired state of charge (SOC) for the receiving load 22. In such implementations, instructions are further configured to cause the processor 13 to initiate a V2X charging session from the supplier vehicle 20 in response to the SOC of the receiving load 22.

[0055] In various implementations, charging parameters may be based at least in part on one or more parameters of one or more planned additional receiver loads 22. For example, if the supplier vehicle 20 is configured to deliver energy to multiple receiver loads 22 (e.g., if the supplier vehicle 20 is a rescue vehicle configured to provide energy to multiple receiver loads 22 in a one-way trip), the supplier vehicle 20 may set its final mileage and a certain amount of energy allocated to the additional planned receiver loads 22 as default parameters for energy delivery, wherein the certain amount of energy allocated to the additional planned receiver loads 22 may be transferred from the additional planned receiver loads 22 to the supplier vehicle 20, such as via cloud-based communication.

[0056] In various implementations, charging parameters are discovered as part of initializing the V2X charging session. That is, the user selection of the charging parameters discussed above is sent to V2X device 10. It should be understood that, in addition to the discovered charging parameters, higher-layer communication messages may be used for V2X purposes via discharge and charge-related limits.

[0057] like Figure 2 As shown, as part of initializing a V2X charging session, in various implementations, session establishment activities may be performed if necessary. For example, in various implementations, session establishment may include payment verification, membership verification of the user or receiver load in the serving network, availability of such serving network to receiver load 22 at the receiver load's location, etc.

[0058] After the user inputs the selection and the charging session is initialized, the supplier vehicle 20 sends the end state of charge (SOC) of the receiver load 22 to the V2X charging device 10, and the V2X charging device 10 monitors the supplier vehicle selection. For example, the V2X charging device may monitor current, voltage, and / or SOC to ensure compliance with the selection.

[0059] After initializing the charging session, to help ensure the safety of the V2X charging device initiating isolation checks and pre-charging the HV bus, as defined in DIN 70121 and explained above, in various embodiments, instructions are further configured to cause the processor 13 to cause the bus charging module 18 to perform isolation checks on the V2X charging device 10 from the supplier vehicle 20 as described above, in order to pre-charge the V2X charging device 10 as described above.

[0060] After the isolation check and pre-charging are completed, the output voltage of the bus charging module 18 becomes zero, and switches s3a, s3b, s4a and s4b are turned off, and the CP state changes from state B (vehicle detected) to state C (ready).

[0061] Switches S5a and S5b are closed, and energy transfer begins from the DC voltage source BT1 of the supplier vehicle 10 to the receiver load 22. Therefore, the supplier vehicle 20 acts as a DC power source. Charging is performed according to DIN 70121.

[0062] In various embodiments, the instructions are also configured to cause the processor 11 to transmit high-level communication between the V2X charging device 10 and the supplier vehicle 20 and / or the receiver load 22 via PCL and / or wireless communication. Therefore, in various embodiments, communication can be facilitated by using the built-in PLC chips / boards and WiFi chips / boards and / or Bluetooth chipsets of the supplier vehicle 20 and / or receiver load 22. Thus, various communication topologies can be used in various embodiments.

[0063] For example, a communication topology may include wireless communication of charging parameters on the supplier vehicle 20 and the receiver load 22. In such embodiments, the supplier vehicle 20 and the receiver load 22 are equipped to use wireless communication protocols, such as WiFi or Bluetooth, to exchange information about charging / discharging parameters from the supplier vehicle 20 and the receiver load 22 with the V2X charging device 10.

[0064] As another example, another communication topology may include wireless communication on the supplier vehicle 20 and a PLC / Controller Area Network (PLC / CAN) bus on the receiver load 22. In such an implementation, the supplier vehicle 20 is equipped to use wireless communication protocols, such as WiFi or Bluetooth, to exchange information about charging / discharging parameters with the V2X charging unit 10. The receiver load 22 uses a PLC charging protocol, such as a Combined Charging System (CCS). In such an implementation, the V2X charging unit 10 can handle both communication protocols and will arbitrate the energy transfer.

[0065] As another example, another communication topology could include wireless communication on the supplier vehicle 20 and PLC / CAN on the receiver load 22. In such an implementation, the supplier vehicle 20 and the receiver load 22 are equipped to use a PLC charging protocol, such as CCS. In such an implementation, the V2X charging device 10 can handle the communication between the two parties and will arbitrate the energy transfer.

[0066] During energy transfer (i.e., during a V2X charging session), mileage and SOC limits are monitored by the supplier vehicle 20 and transmitted to the controller 11 via PCL or wireless communication. The receiver load 22 can transmit charging limits, voltage limits, and charging status via PCL or wireless communication, allowing the V2X charging unit 10 to take desired actions to facilitate safe energy transfer, such as instructing the supplier vehicle 20 to close the contactor for energy transfer, or troubleshooting faults on the supplier vehicle 20 or receiver load 22. When applicable limits are reached, the V2X charging session is stopped according to DIN 70121.

[0067] In various implementation schemes and further reference Figure 4 An exemplary V2X method 400 is provided. Method 400 begins at block 402. At block 404, it is determined that the protocol to be followed in the charging session is a vehicle-to-load (V2X) charging session from the supplier vehicle. At block 406, the V2X charging session from the supplier vehicle is initialized. At block 408, an isolation check of the V2X charging device is performed from the supplier vehicle. At block 410, the V2X charging device is pre-charged. Method 400 ends at block 412.

[0068] In various implementations, the protocol to be followed in the charging session is determined in response to identifying the namespace of the supported vehicle, which is the V2X charging session from the supplier vehicle.

[0069] In various implementations, a V2X charging session from the supplier vehicle is initiated via high-level communication between the V2X charging device and the supplier vehicle using a communication protocol selected from power line communication (PCL) and wireless communication.

[0070] In various implementations, a V2X charging session from a supplier vehicle is initiated in response to at least one supplier vehicle parameter, such as the supplier vehicle's final mileage, charging period, and / or a certain amount of energy transferred from the supplier vehicle.

[0071] In various implementations, a V2X charging session from the supplier vehicle is initiated in response to the end-of-charge state of the receiver load.

[0072] In various implementation schemes, V2X charging devices transfer energy from the supplier vehicle to the receiver load.

[0073] In various implementations, high-level communication between the V2X charging device and the supplier vehicle and / or the receiver load is transmitted via at least one communication protocol selected from power line communication (PCL) and wireless communication.

[0074] It should be understood that the various implementations described herein can help allow communication and V2X charging sessions to be established and initialized by utilizing existing hardware and software on today's vehicles. It should also be understood that the various implementations described herein can help allow, for example, but not limited to, a supplier vehicle charging another vehicle, transferring power from a supplier vehicle to a home via a DC charging pin, or for supporting vehicles rescuing stranded vehicles without requiring any additional communication hardware from the supplier vehicle.

[0075] In some cases, one or more components may be referred to herein as “configured to,” “configured by,” “configurable to,” “operable / operating as,” “suitable / adaptable to,” “capable of,” “adaptable to,” etc. Those skilled in the art will recognize that, unless the context otherwise requires, such terms (e.g., “configured to”) generally cover active state components and / or passive state components and / or standby state components.

[0076] While specific aspects of the subject matter described herein have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made based on the teachings herein without departing from the subject matter and its broader aspects, and therefore all such changes and modifications are covered within its scope, as in the substance and scope of the subject matter described herein. Those skilled in the art will understand that, in general, the terminology used herein, particularly in the appended claims (e.g., the body of the appended claims), is intended to denote “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “at least having,” the term “including” should be interpreted as “comprising but not limited to,” etc.). Those skilled in the art will further understand that if the intent is a specific number of introduced claim statements, such intent will be explicitly stated in the claims, and if no such statements are present, such intent does not exist. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of such phrases should not be construed as implying that introducing a claim statement with the indefinite article "a" or "an" limits any particular claim containing such an introduced claim statement to a claim containing only one such statement, even when the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should generally be interpreted as meaning "at least one" or "one or more"); the same applies to the use of definite articles used to introduce a claim statement. Furthermore, even when a specific number of introduced claim statements are explicitly stated, those skilled in the art will recognize that such a statement should generally be interpreted as meaning at least the number stated (e.g., simply stating "two statements" without further modification generally means at least two statements, or two or more statements). Furthermore, in cases where conventions such as "at least one of A, B, and C" are used, generally speaking, such a construction is intended to mean that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, systems having only A, having only B, having only C, having A and B, having A and C, having B and C, and / or A, B, and C, etc.). A person skilled in the art will further understand that, unless the context otherwise requires, extractive terms and / or phrases that typically present two or more alternative terms (whether in the specification, claims, or drawings) should be understood to contemplate the possibility of including one, any, or both of the terms. For example, the phrase "A or B" will generally be understood to include the possibility of "A" or "B" or "A and B".

[0077] The above-described specific embodiments have illustrated various implementations of the apparatus and / or process using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide range of hardware.

[0078] With respect to the appended claims, those skilled in the art will understand that the operations enumerated herein can generally be performed in any order. Furthermore, although the various operational flows are presented sequentially, it should be understood that the various operations can be performed in any order other than that shown, or can be performed simultaneously. Unless the context otherwise requires, examples of such alternative orderings may include overlapping, interleaving, interruption, reordering, ascending, preparatory, supplementary, simultaneous, reverse, or other variations of ordering. Moreover, unless the context otherwise requires, terms such as “in response to,” “related to,” or other past tense adjectives are generally not intended to exclude such variations.

[0079] Although the subject matter disclosed herein has been described with reference to exemplary embodiments, those skilled in the art will understand that various modifications may be made to the subject matter without departing from the scope of the claimed subject matter set forth in the claims.

Claims

1. A non-transitory computer-readable medium storing computer-executable instructions therein, which, when executed on a processor, are configured to cause the processor to: The protocol to be followed in the charging session is determined to be the vehicle-to-load V2X charging session from the supplier's vehicle. Initialize the V2X charging session from the supplier vehicle; The insulation of the cable is verified by applying an output DC voltage from the DC bus charging module of the vehicle-to-load V2X charging device, having a first voltage level, to the DC bus cable electrically connected to the input of the DC-DC converter of the V2X charging device, in order to perform an isolation check of the V2X charging device from the supplier vehicle; and The V2X charging device is precharged using an output DC voltage from the DC bus charging module that has a second voltage level different from the first voltage level.

2. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to: The V2X charging session from the supplier vehicle is initialized in response to the namespace declared by the supplier vehicle; and In response to identifying the namespace of the supported vehicle, it is determined that the protocol to be followed in the charging session is the V2X charging session from the supplier vehicle.

3. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to initiate the V2X charging session from the supplier vehicle via a high-level communication between the V2X charging device and the supplier vehicle via a communication protocol selected from power line communication (PCL) and wireless communication.

4. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to initialize the V2X charging session from the supplier vehicle in response to at least one supplier vehicle parameter selected from the supplier vehicle's end mileage, charging period, and a certain amount of energy delivered from the supplier vehicle.

5. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to initiate the V2X charging session from the supplier vehicle in response to the end-of-charge state of the receiver load.

6. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to cause the V2X charging device to transfer energy from the supplier vehicle to the receiver load.

7. The non-transitory computer-readable medium of claim 1, wherein the instructions are further configured to cause the processor to transmit high-level communication between the V2X charging device and at least one device selected from the supplier vehicle and the receiver load via at least one communication protocol selected from power line communication (PCL) and wireless communication.

8. A controller for a vehicle-to-load (V2X) charging device, the controller comprising: processor; and A non-transitory computer-readable medium storing computer-executable instructions therein, which, when executed on the processor, are configured to cause the processor to: The protocol to be followed in the charging session is determined to be the vehicle-to-load V2X charging session from the supplier's vehicle. Initialize the V2X charging session from the supplier vehicle; The insulation of the cable is verified by applying an output DC voltage from the DC bus charging module of the V2X charging device, having a first voltage level, to the DC bus cable electrically connected to the input of the DC-DC converter of the V2X charging device, in order to perform an isolation check on the V2X charging device from the supplier vehicle. as well as The V2X charging device is precharged using an output DC voltage from the DC bus charging module that has a second voltage level different from the first voltage level.

9. The controller of claim 8, wherein the instructions are further configured to cause the processor to initiate the V2X charging session from the supplier vehicle in response to a namespace declared by the supplier vehicle and via a communication protocol selected from power line communication (PCL) and wireless communication, through high-level communication between the V2X charging device and the supplier vehicle.

10. The controller of claim 8, wherein the instructions are further configured to cause the processor to initialize the V2X charging session from the supplier vehicle in response to at least one supplier vehicle parameter selected from the supplier vehicle's end mileage, charging period, and a certain amount of energy delivered from the supplier vehicle.

11. The controller of claim 8, wherein the instructions are further configured to cause the processor to initiate the V2X charging session from the supplier vehicle in response to the end-of-charge state of the receiver load.

12. The controller of claim 8, wherein the instructions are further configured to cause the processor to cause the V2X charging device to transfer energy from the supplier vehicle to the receiver load.

13. The controller of claim 8, wherein the instructions are further configured to cause the processor to transmit high-level communication between the V2X charging device and at least one device selected from the supplier vehicle and the receiver load via at least one communication protocol selected from power line communication (PCL) and wireless communication.

14. A vehicle-to-load (V2X) charging device, the V2X charging device comprising: High-voltage DC-DC converter; DC bus charging module; and Controller, the controller includes: processor; and A non-transitory computer-readable medium storing computer-executable instructions therein, which, when executed on the processor, are configured to cause the processor to: The protocol to be followed in the charging session is the V2X charging session from the supplier's vehicle; Initialize the V2X charging session from the supplier vehicle; The DC bus charging module applies an output DC voltage with a first voltage level to the DC bus cable electrically connected to the input of the DC-DC converter to verify the insulation of the cable, thereby performing an isolation check on the V2X charging device from the supplier vehicle; and The DC bus charging module precharges the DC-DC converter with an output DC voltage having a second voltage level different from the first voltage level.

15. The V2X charging device according to claim 14, wherein the V2X charging device further comprises: A communication subsystem configured to transmit low-level and high-level communications.

16. The V2X charging device of claim 15, wherein the communication subsystem includes at least one communication device configured to transmit higher-level communication via power line communication (PLC) and a radio frequency (RF) transceiver configured to transmit higher-level communication.

17. The V2X charging device of claim 16, wherein the RF transceiver is further configured to transmit higher-level communications via at least one RF communication protocol selected from WiFi and Bluetooth.

18. The V2X charging device of claim 17, wherein the instructions are further configured to cause the processor to transmit high-level communication between the V2X charging device and at least one device selected from the supplier vehicle and the receiver load via at least one communication protocol selected from power line communication (PCL) and wireless communication.

19. The V2X charging apparatus of claim 14, wherein the instructions are further configured to cause the processor to initialize the V2X charging session from the supplier vehicle in response to a namespace declared by the supplier vehicle, in response to the end state of charge of the receiver load, and in response to at least one supplier vehicle parameter selected from the end mileage of the supplier vehicle, the charging period, and a certain amount of energy delivered from the supplier vehicle.

20. The V2X charging device of claim 14, wherein the instructions are further configured to cause the processor to cause the V2X charging device to transfer energy from the supplier vehicle to the receiver load.

Images