Charging and discharging interaction method, charging and discharging device, cloud server, system and medium

Abstract

A kind of charge-discharge interaction method, charge-discharge device, cloud server, system and medium belong to electric power technical field.Charge-discharge interaction method includes: charge-discharge device (11) sends vehicle-to-grid V2G function confirmation message to the battery management system of target vehicle (12) (step S201);Charge-discharge device (11) is not received in the preset time length after sending V2G function confirmation message V2G function feedback message that battery management system feedbacks, sends first indication message to cloud server (13), first indication message is used to indicate that target vehicle (12) does not support V2G function (step S202);Charge-discharge device (11) responds to non-V2G charging instruction received from cloud server, and carries out non-V2G charging to target vehicle (12) (step S203).It can improve the availability of charge-discharge device (11).

Description

Technical Field

[0001] This application belongs to the field of power technology, and in particular relates to a charging and discharging interaction method, a charging and discharging device, a cloud server, a system, and a medium. Background Technology

[0002] Vehicle-to-grid (V2G) technology refers to the technology that allows energy to flow bidirectionally between vehicles and the power grid. The power grid can charge vehicles using V2G-enabled charging and discharging devices, and vehicles can transmit electrical energy back to the power grid using V2G-enabled charging and discharging devices.

[0003] Because V2G technology is relatively new, not all vehicles currently in use support it. If a vehicle that does not support V2G is connected to a charging device that does, the V2G-enabled device will be unable to charge the vehicle, reducing the device's availability. Summary of the Invention

[0004] This application provides a charging and discharging interaction method, a charging and discharging device, a cloud server, a system, and a medium, which can improve the availability of the charging and discharging device.

[0005] In a first aspect, embodiments of this application provide a charging and discharging interaction method, comprising: a charging and discharging device sending a vehicle-to-grid (V2G) function confirmation message to the battery management system of a target vehicle; if the charging and discharging device does not receive a V2G function feedback message from the battery management system within a preset time period after sending the V2G function confirmation message, the charging and discharging device sending a first indication message to a cloud server, the first indication message being used to indicate that the target vehicle does not support the V2G function; and the charging and discharging device performing non-V2G charging on the target vehicle in response to a non-V2G charging command received from the cloud server.

[0006] By interacting with the charging and discharging device, the cloud server, and the target vehicle, the charging and discharging device that indicates V2G functionality can charge vehicles that do not support V2G functionality, thereby improving the availability of the charging and discharging device.

[0007] In some possible embodiments, the non-V2G charging command is sent by the cloud server in response to the first instruction message.

[0008] The cloud server sends non-V2G charging commands directly to the charging and discharging device, making the process of charging and discharging devices for target vehicles that do not support V2G functionality more convenient and faster.

[0009] In some possible embodiments, the non-V2G charging command is sent by the cloud server in response to the non-V2G charging mode selection command of the terminal device, and the terminal device communicates with the cloud server.

[0010] The cloud server can interact with the terminal device, allowing users to participate in the non-V2G charging process of the target vehicle that does not support V2G by operating the terminal device. It also enables users to be informed in a timely manner that the target vehicle does not support V2G, thus improving the user experience.

[0011] In some possible embodiments, before the charging / discharging device sends a V2G function confirmation message to the battery management system of the target vehicle, the method further includes: the charging / discharging device sending a wake-up signal to the battery management system, the wake-up signal being used to wake up the battery management system.

[0012] The charging and discharging device sends a wake-up signal to the battery management system so that the battery management system can be quickly woken up and put into working state.

[0013] In some possible embodiments, after the charging and discharging device sends a V2G function confirmation message to the battery management system of the target vehicle, the method further includes: if the charging and discharging device receives a V2G function feedback message from the battery management system within a preset time after sending the V2G function confirmation message, the charging and discharging device sends a second instruction message to the cloud server, the second instruction message being used to indicate that the target vehicle supports the V2G function; the charging and discharging device responds to the received grid dispatching command to perform V2G charging or V2G discharging on the target vehicle.

[0014] The charging and discharging device that supports V2G functionality can perform both V2G charging and discharging for vehicles that support V2G functionality and non-V2G charging for vehicles that do not support V2G functionality, thereby improving the availability and applicability of the charging and discharging device.

[0015] Secondly, embodiments of this application provide a charging and discharging interaction method, including: a cloud server receiving a first indication message from a charging and discharging device, the first indication message being sent by the charging and discharging device after it has not received a V2G function feedback message within a preset time period after sending a V2G function confirmation message to the battery management system of the target vehicle, and used to indicate that the target vehicle does not support the V2G function; the cloud server sending a non-V2G charging instruction to the charging and discharging device, the non-V2G instruction being used to instruct the charging and discharging device to perform non-V2G charging on the target vehicle.

[0016] By interacting with the charging and discharging device, the cloud server, and the target vehicle, the charging and discharging device that indicates V2G functionality can charge vehicles that do not support V2G functionality, thereby improving the availability of the charging and discharging device.

[0017] In some possible embodiments, the cloud server sends a non-V2G charging instruction to the charging device, including: the cloud server responding to a first instruction message by sending a non-V2G charging instruction to the charging device.

[0018] The cloud server sends non-V2G charging commands directly to the charging and discharging device, making the process of charging and discharging devices for target vehicles that do not support V2G functionality more convenient and faster.

[0019] In some possible embodiments, before the cloud server sends a non-V2G charging instruction to the charging and discharging device, the method further includes: the cloud server sending a third indication message to the terminal device, the third indication message being used to indicate that the target vehicle does not support V2G functionality; and the cloud server receiving a non-V2G charging mode selection instruction from the terminal device.

[0020] The cloud server sends a non-V2G charging command to the charging and discharging device, including: the cloud server responding to the non-V2G charging mode selection command and sending a non-V2G charging command to the charging and discharging device.

[0021] The cloud server can interact with the terminal device, allowing users to participate in the non-V2G charging process of the target vehicle that does not support V2G by operating the terminal device. It also enables users to be informed in a timely manner that the target vehicle does not support V2G, thus improving the user experience.

[0022] In some possible embodiments, the charge-discharge interaction method further includes: a cloud server receiving a second indication message from the charge-discharge device, the second indication message being sent by the charge-discharge device within a preset time period after sending a V2G function confirmation message to the battery management system of the target vehicle, and used to indicate that the target vehicle supports the V2G function; the cloud server responding to the second indication message sending a fourth indication message to the terminal device, the fourth indication message being used to indicate that the target vehicle supports the V2G function, and the cloud server and the terminal device establishing a communication connection.

[0023] The charging and discharging device that supports V2G functionality can perform both V2G charging and discharging for vehicles that support V2G functionality and non-V2G charging for vehicles that do not support V2G functionality, thereby improving the availability and applicability of the charging and discharging device.

[0024] Thirdly, embodiments of this application provide a charging and discharging device, comprising: a sending module, configured to send a V2G function confirmation message to the battery management system of a target vehicle, and, if no V2G function feedback message is received from the battery management system within a preset time after sending the V2G function confirmation message, to send a first indication message to a cloud server, the first indication message being used to indicate that the target vehicle does not support the V2G function; and an execution module, configured to perform non-V2G charging on the target vehicle in response to a non-V2G charging command received from the cloud server.

[0025] By interacting with a cloud server and the target vehicle, the charging and discharging device enables a V2G-enabled charging and discharging device to charge vehicles that do not support V2G functionality, thereby improving the availability of the charging and discharging device.

[0026] Fourthly, this application provides a cloud server, including: a receiving module, configured to receive a first indication message from a charging / discharging device, the first indication message being sent by the charging / discharging device after it has not received a V2G function feedback message within a preset time period following sending a V2G function confirmation message to the battery management system of the target vehicle, and used to indicate that the target vehicle does not support the V2G function; and a sending module, configured to send a non-V2G charging instruction to the charging / discharging device, the non-V2G instruction being used to instruct the charging / discharging device to perform non-V2G charging on the target vehicle.

[0027] Through the interaction between the charging / discharging device, the cloud server, and the target vehicle, the charging / discharging device that indicates V2G functionality can charge vehicles that do not support V2G functionality, thereby improving the availability of the charging / discharging device.

[0028] Fifthly, embodiments of this application provide a charging and discharging device, including: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the charging and discharging interaction method of the first aspect.

[0029] In a sixth aspect, embodiments of this application provide a cloud server, including: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the charging and discharging interaction method of the second aspect.

[0030] In a seventh aspect, embodiments of this application provide a charging and discharging system, including a charging and discharging device as described in the fifth aspect and a cloud server as described in the sixth aspect.

[0031] In some possible embodiments, the charging and discharging system further includes: a terminal device for receiving from a cloud server an indication message indicating that the target vehicle supports V2G functionality or an indication message indicating that the target vehicle does not support V2G functionality.

[0032] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the charging and discharging interaction method of the first aspect.

[0033] In a ninth aspect, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the charging and discharging interaction method of the second aspect.

[0034] This application provides a charging and discharging interaction method, a charging and discharging device, a cloud server, a system, and a medium. The charging and discharging device first sends a V2G function confirmation message to the battery management system of the target vehicle. If no V2G function feedback message is received from the battery management system within a preset time after sending the V2G function confirmation message, it indicates that the target vehicle does not support the V2G function. The charging and discharging device informs the cloud server that the target vehicle does not support the V2G function through a first indication message. Then, the cloud server instructs the charging and discharging device to perform non-V2G charging on the target vehicle through a non-V2G charging command. This enables the charging and discharging device that supports the V2G function to charge vehicles that do not support the V2G function, thereby improving the availability of the charging and discharging device. Attached Figure Description

[0035] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 A schematic diagram illustrating an application scenario of the charge-discharge interaction method provided in the embodiments of this application;

[0037] Figure 2 A schematic diagram illustrating another application scenario of the charge-discharge interaction method provided in the embodiments of this application;

[0038] Figure 3 A flowchart of an embodiment of the charge-discharge interaction method for a charge-discharge device provided in this application;

[0039] Figure 4 A flowchart illustrating an example of a non-V2G charging process between a charging / discharging device and a target vehicle provided in an embodiment of this application;

[0040] Figure 5 A flowchart of another embodiment of the charge-discharge interaction method for a charge-discharge device provided in this application;

[0041] Figure 6A flowchart illustrating an example of the V2G charging and discharging process between the charging and discharging device provided in this application embodiment and the target vehicle;

[0042] Figure 7 A flowchart illustrating an embodiment of the charging and discharging interaction method for a cloud server provided in this application;

[0043] Figure 8 A flowchart of another embodiment of the charging and discharging interaction method for cloud servers provided in this application;

[0044] Figure 9 A flowchart of yet another embodiment of the charging and discharging interaction method for a cloud server provided in this application;

[0045] Figure 10 A flowchart illustrating an example of the process by which the charging and discharging device provided in this application charges a target vehicle that does not support V2G functionality;

[0046] Figure 11 A flowchart illustrating another example of the process by which the charging and discharging device provided in this application charges a target vehicle that does not support V2G functionality;

[0047] Figure 12 A schematic diagram of the structure of an embodiment of the charging and discharging device provided in this application;

[0048] Figure 13 A schematic diagram of the structure of an embodiment of the cloud server provided in this application;

[0049] Figure 14 A schematic diagram of the hardware structure of an embodiment of the charging and discharging device provided in this application;

[0050] Figure 15 This is a schematic diagram of the hardware structure of an embodiment of the cloud server provided in this application. Detailed Implementation

[0051] The embodiments of this application will be described in further detail below with reference to the accompanying drawings and examples. The detailed description of the following embodiments and the accompanying drawings are used to illustrate the principles of this application by way of example, but should not be used to limit the scope of this application, that is, this application is not limited to the described embodiments.

[0052] In the description of this application, it should be noted that, unless otherwise stated, "a plurality of" means two or more; the terms "upper," "lower," "left," "right," "inner," and "outer," etc., indicating orientation or positional relationships, are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. Furthermore, the terms "first," "second," and "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. "Vertical" is not vertical in the strict sense, but within the allowable tolerance range. "Parallel" is not parallel in the strict sense, but within the allowable tolerance range.

[0053] The directional terms used in the following description refer to the directions shown in the figures and are not intended to limit the specific structure of this application. It should also be noted in the description of this application that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "joining" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0054] Vehicle-to-grid (V2G) technology refers to the technology that allows energy to flow bidirectionally between a vehicle and the power grid. The power grid can charge vehicles using V2G-enabled charging and discharging devices, and vehicles can transmit electrical energy back to the power grid using V2G-enabled charging and discharging devices. Vehicles can use batteries as their power source; specifically, V2G technology can be viewed as a technology that allows energy to flow bidirectionally between the vehicle's battery and the power grid.

[0055] However, since V2G technology is relatively new, not all vehicles support V2G functionality. Charging devices that support V2G cannot charge vehicles that do not support V2G, thus reducing the availability of the charging devices.

[0056] This application provides a charging and discharging interaction method, a charging and discharging device, a cloud server, a system, and a medium, which enables a charging and discharging device that supports V2G functionality to charge vehicles that do not support V2G functionality.

[0057] In some cases, the charging and discharging interaction method in the embodiments of this application may involve a vehicle, a charging and discharging device, and a cloud server. Figure 1 This is a schematic diagram illustrating an example application scenario of the charge-discharge interaction method provided in the embodiments of this application. For example... Figure 1 As shown, the charging and discharging device 11 can communicate and interact with the vehicle 12 and exchange energy, and the charging and discharging device 11 can communicate and interact with the cloud server 13. Figure 1 Hollow arrows represent communication interactions, while solid arrows represent energy interactions.

[0058] In other cases, the charging and discharging interaction method in the embodiments of this application may involve vehicles, charging and discharging devices, cloud servers, and terminal devices. Figure 2 This is a schematic diagram illustrating another example of an application scenario for the charge-discharge interaction method provided in the embodiments of this application. Figure 2 and Figure 1 The difference lies in the fact that this application scenario also involves terminal device 14. Terminal device 14 can communicate and interact with cloud server 13. Figure 2 Hollow arrows represent communication interactions, while solid arrows represent energy interactions.

[0059] The charging and discharging device 11 is a charging and discharging device that supports V2G functionality. The charging and discharging device 11 may include charging piles, charging stations, and other devices that support V2G functionality and are capable of charging and discharging, but is not limited thereto.

[0060] The vehicle 12 is equipped with a power battery and a battery management system (BMS). The communication interaction between the charging and discharging device 11 and the vehicle 12 is specifically the communication interaction between the charging and discharging device 11 and the battery management system in the vehicle 12. The energy interaction between the charging and discharging device 11 and the vehicle 12 is specifically the energy interaction between the charging and discharging device 11 and the power battery in the vehicle 12.

[0061] The cloud server 13 communicates and interacts with the charging and discharging device 11. The cloud server 13 can obtain information from the charging and discharging device 11, and can also control the charging and discharging device 11 to perform operations corresponding to the instructions.

[0062] Terminal device 14 communicates and interacts with cloud server 13. Terminal device 14 can provide users with selectable energy exchange modes through display, sound, or other means. Terminal device 14 can be specifically implemented as a mobile phone, computer, tablet computer, etc. In some examples, terminal device 14 can be integrated with charging and discharging device 11.

[0063] The charging and discharging interaction method in the embodiments of this application will be described in detail below.

[0064] This application provides a charging and discharging interaction method, which can be executed by a charging and discharging device. Figure 3 A flowchart illustrating an embodiment of the charge-discharge interaction method applied to a charge-discharge device provided in this application. Figure 3 As shown, the charge-discharge interaction method may include steps S201 to S203.

[0065] In step S201, the charging and discharging device sends a V2G function confirmation message to the target vehicle's battery management system.

[0066] The target vehicle is the vehicle that is electrically connected to the charging / discharging device. For example, the charging / discharging device is a charging station, and the target vehicle is the vehicle whose charging gun is plugged into the charging station.

[0067] The V2G function confirmation message is used to confirm whether the target vehicle supports the V2G function. Specifically, the V2G function confirmation message can be implemented as a CDC message or other types of messages, which are not limited here.

[0068] V2G functionality refers to the ability of a vehicle to exchange energy bidirectionally with a charging / discharging device using V2G technology under the dispatch of a power grid such as the State Grid.

[0069] In step S202, if the charging and discharging device does not receive a V2G function feedback message from the battery management system within a preset time period after sending the V2G function confirmation message, it sends a first instruction message to the cloud server.

[0070] The preset duration is a threshold value used to determine when feedback timeout occurs. If the charging / discharging device does not receive a V2G function feedback message from the battery management system within the preset duration after sending the V2G function confirmation message, it indicates that no feedback has been received after the timeout, and it can be determined that the target vehicle does not support the V2G function. The preset duration can be set according to specific scenarios and needs, and is not limited here. For example, the preset duration can be 5 seconds.

[0071] If it is determined that the target vehicle does not support V2G functionality, the cloud server can be notified that the target vehicle does not support V2G functionality. The charging / discharging device can notify the cloud server via a first indication message. The first indication message is used to indicate that the target vehicle does not support V2G functionality.

[0072] In step S203, the charging and discharging device responds to the non-V2G charging command received from the cloud server and performs non-V2G charging on the target vehicle.

[0073] If the cloud server determines that the target vehicle does not support V2G functionality, it can send a non-V2G charging command to the charging device. The charging device responds to this non-V2G charging command and performs non-V2G charging on the target vehicle.

[0074] Non-V2G charging is conventional charging and does not require waiting for grid dispatch. Figure 4 This is a flowchart illustrating an example of a non-V2G charging process between a charging / discharging device provided in an embodiment of this application and a target vehicle. The target vehicle includes a battery management system and a power battery. Figure 4 As shown, when the target vehicle's battery management system is operational, the non-V2G charging process may include the following steps a1 to a6:

[0075] Step a1: The charging and discharging device sends a charger handshake message, i.e., a CHM message, to the battery management system.

[0076] Step a2: The battery management system sends a battery management system handshake message, i.e., a BHM message, to the charging and discharging device, i.e., the charging and discharging device receives the BHM message sent by the battery management system.

[0077] Step a3: The charging and discharging device sends a charger identification message, i.e., a CRM message, to the battery management system.

[0078] Step a4: The battery management system sends a battery management system identification message (BRM message) to the charging and discharging device, which means the charging and discharging device receives the BRM message sent by the battery management system.

[0079] Step a5: Configure the charging and discharging device with non-V2G charging parameters;

[0080] Step a6: The charging and discharging device charges the power battery in the target vehicle according to the configured charging parameters.

[0081] If the target vehicle's battery management system is in a dormant state, the charging and discharging device can send a dormant wake-up signal to the battery management system before executing step a1 to wake up the battery management system.

[0082] In this embodiment, the charging / discharging device first sends a V2G function confirmation message to the target vehicle's battery management system. If no V2G function feedback message is received from the battery management system within a preset time period after sending the V2G function confirmation message, it indicates that the target vehicle does not support the V2G function. The charging / discharging device informs the cloud server that the target vehicle does not support the V2G function through a first indication message. Then, the cloud server instructs the charging / discharging device to perform non-V2G charging on the target vehicle through a non-V2G charging command. This enables the charging / discharging device that supports the V2G function to charge vehicles that do not support the V2G function, improving the availability of the charging / discharging device.

[0083] In some examples, the cloud server can respond to the first instruction message and directly send a non-V2G charging command to the charging / discharging device. That is, the non-V2G charging command is sent by the cloud server in response to the first instruction message.

[0084] The cloud server sends non-V2G charging commands directly to the charging and discharging device, making the process of charging and discharging devices for target vehicles that do not support V2G functionality more convenient and faster.

[0085] In other examples, the cloud server and the terminal device are communicatively connected. In response to a first indication message, the cloud server can send an indication message to the terminal device indicating that the target vehicle does not support V2G functionality, thus notifying the terminal device that the target vehicle does not support V2G. The terminal device can issue a prompt message through display, sound, or other means to inform the user that the target vehicle does not support V2G functionality. The terminal device can also provide the user with selectable energy exchange modes through display, voice control, buttons, or other means. For example, energy exchange modes may include a non-V2G charging mode and a V2G function mode. The user can select the desired energy exchange mode through input. In response to the user's input, the terminal device can send a mode selection command to the cloud server. In response to the mode selection command, the cloud server can send a corresponding indication command to the charging / discharging device. If it is determined that the target vehicle does not support V2G functionality, the terminal device, in response to the user's input of a non-V2G charging mode selection, sends a non-V2G charging mode selection command to the cloud server. In response to this non-V2G charging mode selection command, the cloud server sends a non-V2G charging command to the charging / discharging device. In other words, non-V2G charging commands are sent by the cloud server in response to the terminal device's non-V2G charging mode selection command.

[0086] The cloud server can interact with the terminal device, allowing users to participate in the non-V2G charging process of the target vehicle that does not support V2G by operating the terminal device. It also enables users to be informed in a timely manner that the target vehicle does not support V2G, thus improving the user experience.

[0087] To reduce power consumption, the battery management system (BMS) can be in a sleep state when not in use. To enable rapid interaction between the BMS and the charging / discharging device, the charging / discharging device can send a wake-up signal to the BMS before sending a V2G function confirmation message. The wake-up signal is used to wake up the BMS.

[0088] In some examples, the charging and discharging device is a charging station. When the charging gun of the charging station is plugged into the target vehicle, the charging station outputs an A+ signal to the target vehicle's battery management system. This A+ signal is the wake-up signal. Upon receiving the A+ signal, the battery management system exits its dormant state and enters its working state.

[0089] If the target vehicle supports V2G functionality, the charging and discharging device can perform V2G charging or V2G discharging on the target vehicle. Figure 5 A flowchart of another embodiment of the charge-discharge interaction method for a charge-discharge device provided in this application. Figure 5 and Figure 3 The difference is that, Figure 5 It may also include steps S204 and S205.

[0090] In step S204, if the charging and discharging device receives a V2G function feedback message from the battery management system within a preset time after sending the V2G function confirmation message, it sends a second instruction message to the cloud server.

[0091] If the charging / discharging device receives a V2G function feedback message from the battery management system within a preset time period after sending a V2G function confirmation message, it can determine that the target vehicle supports the V2G function. The V2G function feedback message is used to characterize that the target vehicle supports the V2G function. Specifically, the V2G function feedback message can be implemented as a BDC message or other types of messages, which are not limited here.

[0092] If it is determined that the target vehicle supports V2G functionality, the cloud server can be notified that the target vehicle supports V2G functionality. The charging / discharging device can notify the cloud server via a second indication message. The second indication message is used to indicate that the target vehicle supports V2G functionality.

[0093] In some examples, after sending a V2G function feedback message to the charging and discharging device, the battery management system can wait for a period of time before entering a sleep state to save energy. For example, the battery management system can power down and enter a sleep state 10 seconds after sending the V2G function feedback message.

[0094] In step S205, the charging and discharging device responds to the received grid dispatch command by performing V2G charging or V2G discharging on the target vehicle.

[0095] If the target vehicle is confirmed to support V2G functionality, the power grid, such as the State Grid, can send a grid dispatch command to the charging and discharging device. The charging and discharging device receives the grid dispatch command and can be dispatched by the grid, so that the grid can exchange energy with the target vehicle through the charging and discharging device.

[0096] Energy exchange can include V2G charging and V2G discharging. V2G charging refers to the power grid charging a target vehicle through a charging and discharging device; specifically, it refers to the power grid charging the power battery in the target vehicle through the charging and discharging device. V2G discharging refers to the target vehicle discharging back to the power grid through a charging and discharging device; specifically, it refers to the power battery in the target vehicle discharging back to the power grid through the charging and discharging device.

[0097] Upon receiving a grid dispatch command, if the battery management system (BMS) is in a dormant state, the charging / discharging device can send a dormant wake-up signal to the BMS to wake it up. For example, upon receiving a grid dispatch command, the charging / discharging device can send an A+ signal to the BMS; the A+ signal is the dormant wake-up signal.

[0098] For ease of explanation, V2G charging and V2G discharging will be collectively referred to as V2G charging and discharging below. V2G charging and discharging requires waiting for grid dispatch. Figure 6 This is a flowchart illustrating an example of a V2G charging / discharging process between a charging / discharging device provided in this application embodiment and a target vehicle. The target vehicle includes a battery management system and a power battery. Figure 6 As shown, with the target vehicle's battery management system in operation, the V2G charging and discharging process may include the following steps b1 to b7:

[0099] Step b1: The charging and discharging device receives the grid dispatching instruction;

[0100] Step b2: The charging and discharging device sends a charger handshake message, i.e., a CHM message, to the battery management system.

[0101] Step b3: The battery management system sends a battery management system handshake message (BHM message) to the charging / discharging device; that is, the charging / discharging device receives the BHM message sent by the battery management system.

[0102] Step b4: The charging and discharging device sends a charger identification message, i.e., a CRM message, to the battery management system.

[0103] Step b5: The battery management system sends a battery management system identification message (BRM message) to the charging and discharging device, which means the charging and discharging device receives the BRM message sent by the battery management system.

[0104] Step b6: Configure the charging and discharging parameters for V2G charging and discharging in the charging and discharging device;

[0105] Step b7: The charging and discharging device charges and discharges the power battery in the target vehicle according to the configured charging and discharging parameters.

[0106] If the target vehicle's battery management system is in a dormant state, the charging and discharging device can send a dormant wake-up signal to the battery management system before executing step b1 to wake up the battery management system.

[0107] In this embodiment, the charging and discharging device that supports V2G functionality can perform both V2G charging and discharging for vehicles that support V2G functionality and non-V2G charging for vehicles that do not support V2G functionality, thereby improving the availability and applicability of the charging and discharging device.

[0108] In some examples, if the charging / discharging device receives a V2G function feedback message from the battery management system within a preset time after sending a V2G function confirmation message, it can directly communicate and interact with the power grid, such as the State Grid, to request the power grid to perform V2G scheduling by interacting with the charging / discharging device through power grid scheduling commands.

[0109] In other examples, in response to the received second indication message, the cloud server sends an indication message to the terminal device indicating that the target vehicle supports V2G functionality. The terminal device can issue a prompt message via display, sound, or other means to inform the user that the target vehicle supports V2G functionality. If the target vehicle is confirmed to support V2G functionality, the terminal device, in response to the user's V2G charging mode selection input, sends a V2G charging mode selection command to the cloud server. In response to this non-V2G charging mode selection command, the cloud server sends a V2G charging command to the charging / discharging device, enabling the charging / discharging device to communicate and interact with the power grid, requesting the power grid to perform V2G scheduling through grid dispatch commands. Alternatively, in response to the non-V2G charging mode selection command, the cloud server sends a V2G charging command to the power grid, requesting the power grid to perform V2G scheduling through grid dispatch commands.

[0110] This application also provides a charging and discharging interaction method that can be applied to cloud servers. Figure 7 This is a flowchart of an embodiment of the charging and discharging interaction method for a cloud server provided in this application. Figure 7 As shown, the charge-discharge interaction method may include steps S301 and S302.

[0111] In step S301, the cloud server receives a first instruction message from the charging and discharging device.

[0112] The first indication message is sent by the charging / discharging device if it does not receive a V2G function feedback message within a preset time period after sending a V2G function confirmation message to the target vehicle's battery management system. This message indicates that the target vehicle does not support the V2G function. The specific content of the first indication message can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0113] In step S302, the cloud server sends a non-V2G charging command to the charging and discharging device.

[0114] The non-V2G command is used to instruct the charging and discharging device to perform non-V2G charging on the target vehicle. For details regarding the charging and discharging device performing non-V2G charging on the target vehicle, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0115] In this embodiment, the charging / discharging device first sends a V2G function confirmation message to the target vehicle's battery management system. If no V2G function feedback message is received from the battery management system within a preset time period after sending the V2G function confirmation message, it indicates that the target vehicle does not support the V2G function. The charging / discharging device informs the cloud server that the target vehicle does not support the V2G function through a first indication message. Then, the cloud server instructs the charging / discharging device to perform non-V2G charging on the target vehicle through a non-V2G charging command. This enables the charging / discharging device that supports the V2G function to charge vehicles that do not support the V2G function, improving the availability of the charging / discharging device.

[0116] The cloud server can send a non-V2G charging command directly to the charging and discharging device based on the first instruction message; or, the cloud server can interact with the terminal device and send a non-V2G charging command to the charging and discharging device when the terminal device issues a non-V2G charging mode selection command. Figure 8 A flowchart of another embodiment of the charging and discharging interaction method for cloud servers provided in this application. Figure 8 and Figure 7 The difference is that, Figure 7 Step S302 can be further refined as follows: Figure 8 Step S3021, or, Figure 8 The charge-discharge interaction method shown may further include steps S303 and S304. Figure 7 Step S302 can be further refined as follows: Figure 8 Step S3022 in the process.

[0117] In step S3021, the cloud server responds to the first instruction message by sending a non-V2G charging command to the charging and discharging device.

[0118] In response to the first instruction message, the cloud server directly sends a non-V2G charging command to the charging and discharging device, instructing the charging and discharging device to perform non-V2G charging for the target vehicle, making the charging and discharging device that supports V2G function more convenient and faster for charging and discharging devices that support V2G function to charge vehicles that do not support V2G.

[0119] In step S303, the cloud server sends a third instruction message to the terminal device.

[0120] For details regarding the terminal device, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0121] The third instruction message is used to indicate that the target vehicle does not support V2G functionality. The type and format of the third instruction message are not limited here. The cloud server informs the terminal device that the target vehicle does not support V2G functionality via the third instruction message, so that the terminal device can prompt the user that the target vehicle does not support V2G functionality.

[0122] In step S304, the cloud server receives a non-V2G charging mode selection instruction from the terminal device.

[0123] The terminal device can also provide users with selectable energy exchange modes. If the target vehicle does not support V2G functionality, the terminal device can offer a non-V2G charging mode. Users can select the non-V2G charging mode through input. In response to user input, the terminal device can send a non-V2G charging mode selection command to the cloud server. This command can be used to control the cloud server to instruct the charging and discharging device to perform non-V2G charging on the target vehicle.

[0124] In step S3022, the cloud server responds to the non-V2G charging mode selection command by sending a non-V2G charging command to the charging and discharging device.

[0125] Non-V2G charging commands can be used to instruct charging and discharging devices to perform non-V2G charging on the target vehicle.

[0126] If the target vehicle supports V2G functionality, the charging and discharging device can perform V2G charging or V2G discharging on the target vehicle. Figure 9 A flowchart of yet another embodiment of the charging and discharging interaction method for cloud servers provided in this application. Figure 9 and Figure 7 The difference is that, Figure 9 The charge-discharge interaction method shown may further include steps S305 and S306.

[0127] In step S305, the cloud server receives a second instruction message from the charging and discharging device.

[0128] The second indication message is sent by the charging / discharging device upon receiving a V2G function feedback message within a preset time period after sending a V2G function confirmation message to the target vehicle's battery management system. It is used to indicate that the target vehicle supports the V2G function. The charging / discharging device informs the cloud server that the target vehicle supports the V2G function through the second indication message. The specific content of the second indication message can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0129] In step S306, the cloud server responds to the second instruction message and sends a fourth instruction message to the terminal device.

[0130] The fourth instruction message is used to indicate that the target vehicle supports V2G functionality. The cloud server informs the terminal device that the target vehicle supports V2G functionality through the fourth instruction message, so that the terminal device can prompt the terminal device to indicate that the target vehicle supports V2G functionality.

[0131] In some examples, if the target vehicle is determined to support V2G functionality, the terminal device, in response to the user's V2G charging mode selection input, sends a V2G charging mode selection command to the cloud server. In response to this non-V2G charging mode selection command, the cloud server sends a V2G charging command to the charging / discharging device, enabling the device to communicate with the power grid and request the grid to perform V2G scheduling through grid dispatch commands. Alternatively, the cloud server, in response to the non-V2G charging mode selection command, sends a V2G charging command to the power grid, requesting the grid to perform V2G scheduling through grid dispatch commands.

[0132] To facilitate understanding, the following two examples illustrate the process of charging a target vehicle that does not support V2G functionality using a charging and discharging device.

[0133] Figure 10 This is a flowchart illustrating an example of the process by which the charging and discharging device provided in this application charges a target vehicle that does not support V2G functionality. Figure 10 As shown, the process of charging a target vehicle that does not support V2G functionality using the charging and discharging device may include steps S401 to S412.

[0134] In step S401, the charging and discharging device sends a wake-up signal to the battery management system in the target vehicle to wake up the battery management system;

[0135] In step S402, the charging and discharging device sends a CDC message to the battery management system in the target vehicle;

[0136] In step S403, if the charging and discharging device does not receive a BDC message from the battery management system in the target vehicle within a preset time period, it is determined that the target vehicle does not support the V2G function.

[0137] In step S404, if it is determined that the target vehicle does not support V2G function, the charging and discharging device sends a first instruction message to the cloud server.

[0138] In step S405, the cloud server responds to the first instruction message and sends a third instruction message to the terminal device;

[0139] In step S406, the cloud server responds to the first instruction message by sending a non-V2G charging command to the charging and discharging device;

[0140] In step S407, the charging and discharging device sends a CHM message to the battery management system in the target vehicle;

[0141] In step S408, the battery management system in the target vehicle sends a BHM message to the charging and discharging device;

[0142] In step S409, the charging and discharging device sends a CRM message to the battery management system in the target vehicle;

[0143] In step S410, the battery management system in the target vehicle sends a BRM message to the charging and discharging device;

[0144] In step S411, the charging and discharging device is configured with non-V2G charging parameters;

[0145] In step S412, the charging and discharging device charges the power battery in the target vehicle according to the configured charging parameters until charging is complete.

[0146] Figure 11 A flowchart illustrating another example of the process by which the charging and discharging device provided in this application charges a target vehicle that does not support V2G functionality. For example... Figure 11 As shown, the charging and discharging device can charge a target vehicle that does not support V2G functionality through steps S501 to S515.

[0147] In step S501, the charging and discharging device sends a wake-up signal to the battery management system in the target vehicle to wake up the battery management system;

[0148] In step S502, the charging and discharging device sends a CDC message to the battery management system in the target vehicle;

[0149] In step S503, if the charging and discharging device does not receive a BDC message from the battery management system in the target vehicle within a preset time period, it is determined that the target vehicle does not support the V2G function.

[0150] In step S504, if it is determined that the target vehicle does not support V2G function, the charging and discharging device sends a first instruction message to the cloud server;

[0151] In step S505, the cloud server responds to the first instruction message by sending a third instruction message to the terminal device;

[0152] In step S506, the terminal device displays a prompt message and a mode icon. The prompt message is used to inform the user that the target vehicle does not support the V2G function. The mode icon includes a non-V2G charging mode icon and a V2G mode icon.

[0153] In step S507, the terminal device receives the user's input to select a non-V2G charging mode icon;

[0154] In step S508, the terminal device responds to the user's input by sending a non-V2G charging mode selection command to the cloud server;

[0155] In step S509, the cloud server responds to the non-V2G charging mode selection command by sending a non-V2G charging command to the discharge device.

[0156] In step S510, the charging and discharging device sends a CHM message to the battery management system in the target vehicle;

[0157] In step S511, the battery management system in the target vehicle sends a BHM message to the charging and discharging device;

[0158] In step S512, the charging and discharging device sends a CRM message to the battery management system in the target vehicle;

[0159] In step S513, the battery management system in the target vehicle sends a BRM message to the charging and discharging device;

[0160] In step S514, the charging and discharging device is configured with non-V2G charging and discharging charging parameters;

[0161] In step S515, the charging and discharging device charges and discharges the power battery in the target vehicle according to the configured charging parameters until the charging is completed.

[0162] This application also provides a charging and discharging device. Figure 12 This is a schematic diagram of an embodiment of the charging and discharging device provided in this application. Figure 12 As shown, the charging and discharging device 600 may include a transmitting module 601 and an execution module 602.

[0163] The sending module 601 can be used to send a V2G function confirmation message to the battery management system of the target vehicle, and, if no V2G function feedback message is received from the battery management system within a preset time after sending the V2G function confirmation message, send a first indication message to the cloud server. The first indication message is used to indicate that the target vehicle does not support the V2G function.

[0164] The execution module 602 can be used to perform non-V2G charging on the target vehicle in response to a non-V2G charging command received from the cloud server.

[0165] In this embodiment, the charging / discharging device first sends a V2G function confirmation message to the target vehicle's battery management system. If no V2G function feedback message is received from the battery management system within a preset time period after sending the V2G function confirmation message, it indicates that the target vehicle does not support the V2G function. The charging / discharging device informs the cloud server that the target vehicle does not support the V2G function through a first indication message. Then, the cloud server instructs the charging / discharging device to perform non-V2G charging on the target vehicle through a non-V2G charging command. This enables the charging / discharging device that supports the V2G function to charge vehicles that do not support the V2G function, improving the availability of the charging / discharging device.

[0166] In some examples, non-V2G charging instructions are sent by the cloud server in response to the first instruction message.

[0167] In other examples, non-V2G charging commands are sent by the cloud server in response to a non-V2G charging mode selection command from the terminal device. The terminal device communicates with the cloud server.

[0168] In some examples, the sending module 601 described above can also be used to send a wake-up signal to the battery management system. The wake-up signal is used to wake up the battery management system.

[0169] In some examples, the sending module 601 described above can also be used to send a second instruction message to the cloud server if a V2G function feedback message is received from the battery management system within a preset time period after sending the V2G function confirmation message. The second instruction message is used to indicate that the target vehicle supports the V2G function.

[0170] The aforementioned execution module 602 can also be used to perform V2G charging or V2G discharging on the target vehicle in response to a received power grid dispatch command.

[0171] This application also provides a cloud server. Figure 13 This is a schematic diagram of the structure of an embodiment of the cloud server provided in this application. Figure 13 As shown, the cloud server 700 may include a receiving module 701 and a sending module 702.

[0172] The receiving module 701 can be used to receive a first indication message from the charging and discharging device.

[0173] The first indication message is sent by the charging / discharging device if it does not receive a V2G function feedback message within a preset time after sending a V2G function confirmation message to the target vehicle's battery management system. It is used to indicate that the target vehicle does not support the V2G function.

[0174] The transmitting module 702 can be used to send non-V2G charging commands to the charging and discharging device.

[0175] Non-V2G commands are used to instruct the charging and discharging device to perform non-V2G charging on the target vehicle.

[0176] In this embodiment, the charging / discharging device first sends a V2G function confirmation message to the target vehicle's battery management system. If no V2G function feedback message is received from the battery management system within a preset time period after sending the V2G function confirmation message, it indicates that the target vehicle does not support the V2G function. The charging / discharging device informs the cloud server that the target vehicle does not support the V2G function through a first indication message. Then, the cloud server instructs the charging / discharging device to perform non-V2G charging on the target vehicle through a non-V2G charging command. This enables the charging / discharging device that supports the V2G function to charge vehicles that do not support the V2G function, improving the availability of the charging / discharging device.

[0177] In some examples, the aforementioned sending module 702 can be used to send a non-V2G charging command to the charging / discharging device in response to a first indication message.

[0178] In other examples, the sending module 702 described above can also be used to send a third indication message to the terminal device, the third indication message being used to indicate that the target vehicle does not support V2G functionality.

[0179] The aforementioned receiving module 701 can also be used to receive non-V2G charging mode selection instructions from the terminal device.

[0180] The aforementioned sending module 702 can be used to send a non-V2G charging command to the charging and discharging device in response to a non-V2G charging mode selection command.

[0181] In some examples, the receiving module 701 described above can also be used to receive a second indication message from the charging and discharging device.

[0182] The second instruction message is sent by the charging / discharging device after receiving a V2G function feedback message within a preset time period following the sending of a V2G function confirmation message to the target vehicle's battery management system. It is used to indicate that the target vehicle supports the V2G function.

[0183] The aforementioned sending module 702 can also be used to send a fourth indication message to the terminal device in response to the second indication message.

[0184] The fourth instruction message is used to indicate that the target vehicle supports V2G functionality, and that the cloud server and terminal device communicate and connect.

[0185] This application also provides a charging and discharging device. Figure 14 This is a schematic diagram of the hardware structure of an embodiment of the charging and discharging device provided in this application. Figure 14 As shown, the charging and discharging device 800 includes a memory 801, a processor 802, and a computer program stored in the memory 801 and executable on the processor 802.

[0186] In one example, the processor 802 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0187] Memory 801 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the charge-discharge interaction method applied to a charge-discharge apparatus according to embodiments of this application.

[0188] The processor 802 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 801, so as to implement the charging and discharging interaction method applied to the charging and discharging device in the above embodiment.

[0189] In one example, the charging / discharging device 800 may further include a communication interface 803 and a bus 804. For example, Figure 14 As shown, the memory 801, processor 802, and communication interface 803 are connected through bus 804 and complete communication with each other.

[0190] The communication interface 803 is mainly used to enable communication between various modules, devices, units, and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 803.

[0191] Bus 804 includes hardware, software, or both, that couples the components of charging / discharging device 800 together. For example, and not limitingly, bus 804 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 804 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0192] This application also provides a cloud server. Figure 15 This is a schematic diagram of the hardware structure of an embodiment of the cloud server provided in this application. Figure 15 As shown, the cloud server 900 includes a memory 901, a processor 902, and a computer program stored on the memory 901 and capable of running on the processor 902.

[0193] In one example, the processor 902 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0194] Memory 901 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the charge-discharge interaction method applied to a cloud server according to embodiments of this application.

[0195] The processor 902 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 901, so as to implement the charging and discharging interaction method applied to the cloud server in the above embodiment.

[0196] In one example, the cloud server 900 may also include a communication interface 903 and a bus 904. For example, Figure 15 As shown, the memory 901, processor 902, and communication interface 903 are connected through bus 904 and complete communication with each other.

[0197] The communication interface 903 is mainly used to enable communication between various modules, devices, units, and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 903.

[0198] Bus 904 includes hardware, software, or both, that couples the components of cloud server 900 together. For example, and not limited to, bus 904 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 904 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0199] This application also provides a charging and discharging system. This system may include the charging and discharging device and cloud server described in the above embodiments. Specific details regarding the charging and discharging device, cloud server, the charging and discharging interaction method executed by the charging and discharging device, and the charging and discharging interaction method executed by the cloud server can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0200] In other embodiments, the charging and discharging system may further include a terminal device. The terminal device can be used to receive from a cloud server an indication message indicating that the target vehicle supports V2G functionality or an indication message indicating that the target vehicle does not support V2G functionality. Details regarding the terminal device and its interaction with other devices and equipment can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0201] This application also provides a computer-readable storage medium storing computer program instructions. When executed by a processor, these instructions can implement the charging and discharging interaction method applied to the charging and discharging device or the charging and discharging interaction method applied to the cloud server described above, achieving the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0202] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the embodiments of charging and discharging devices, cloud servers, charging and discharging systems, and computer-readable storage media, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0203] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0204] While this application has been described with reference to preferred embodiments, various modifications can be made thereto and components or steps can be replaced with equivalents without departing from the scope of this application. In particular, the technical features mentioned in the various embodiments can be combined in any manner, provided there is no conflict. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A charge-discharge interaction method characterized by, include: The charging and discharging device sends a vehicle-to-grid (V2G) function confirmation message to the target vehicle's battery management system. If the charging and discharging device does not receive a V2G function feedback message from the battery management system within a preset time after sending the V2G function confirmation message, it sends a first indication message to the cloud server. The first indication message is used to indicate that the target vehicle does not support the V2G function. The charging and discharging device responds to a non-V2G charging command received from the cloud server and performs non-V2G charging on the target vehicle. If the charging and discharging device receives a V2G function feedback message from the battery management system within a preset time after sending the V2G function confirmation message, it sends a second instruction message to the cloud server. The second instruction message is used to indicate that the target vehicle supports the V2G function. After receiving the second instruction message, the cloud server responds to the user's V2G charging mode selection instruction by sending a V2G charging instruction to the power grid, requesting the power grid to interact with the charging and discharging device through power grid dispatch instructions for V2G scheduling.

2. The charge-discharge interaction method according to claim 1, wherein The non-V2G charging command is sent by the cloud server in response to the first instruction message.

3. The charge-discharge interaction method according to claim 1, wherein The non-V2G charging command is sent by the cloud server in response to the non-V2G charging mode selection command of the terminal device, and the terminal device is communicatively connected to the cloud server.

4. The charge and discharge interaction method according to claim 1, characterized by, Before the charging / discharging device sends the V2G function confirmation message to the battery management system of the target vehicle, it also includes: The charging and discharging device sends a wake-up signal to the battery management system, which is used to wake up the battery management system.

5. The charge-discharge interaction method according to claim 1, wherein After receiving the second indication message, the cloud server, in response to the user's V2G charging mode selection command, sends a V2G charging command to the power grid to request the power grid to interact with the charging and discharging device through power grid dispatching commands for V2G scheduling. The method also includes: The charging and discharging device responds to the received grid dispatch command to perform V2G charging or V2G discharging on the target vehicle.

6. A charge-discharge interaction method characterized by, include: The cloud server receives a first indication message from the charging and discharging device. The first indication message is sent by the charging and discharging device if it does not receive a V2G function feedback message within a preset time after sending a V2G function confirmation message to the battery management system of the target vehicle. It is used to indicate that the target vehicle does not support the V2G function. The cloud server sends a non-V2G charging instruction to the charging and discharging device, which instructs the charging and discharging device to perform non-V2G charging on the target vehicle. The cloud server receives a second indication message from the charging and discharging device. The second indication message is sent by the charging and discharging device after receiving a V2G function feedback message within a preset time after sending a V2G function confirmation message to the battery management system of the target vehicle. It is used to indicate that the target vehicle supports the V2G function. The cloud server responds to the user's V2G charging mode selection command by sending a V2G charging command to the power grid, requesting the power grid to interact with the charging and discharging device through power grid dispatching commands to perform V2G dispatching.

7. The charge and discharge interaction method according to claim 6, wherein The cloud server sends non-V2G charging instructions to the charging and discharging device, including: In response to the first instruction message, the cloud server sends the non-V2G charging command to the charging and discharging device.

8. The charge-discharge interaction method according to claim 6, characterized in that, Before the cloud server sends a non-V2G charging command to the charging and discharging device, the method further includes: The cloud server sends a third indication message to the terminal device, the third indication message being used to indicate that the target vehicle does not support V2G functionality; The cloud server receives a non-V2G charging mode selection instruction from the terminal device; The cloud server sends non-V2G charging instructions to the charging and discharging device, including: In response to the non-V2G charging mode selection command, the cloud server sends the non-V2G charging command to the charging and discharging device.

9. The charge-discharge interaction method according to claim 6, characterized in that, Also includes: In response to the second instruction message, the cloud server sends a fourth instruction message to the terminal device. The fourth instruction message is used to indicate that the target vehicle supports V2G functionality, and the cloud server and the terminal device are in a communication connection.

10. A charging and discharging device, characterized in that, include: The sending module is configured to send a V2G function confirmation message to the battery management system of the target vehicle, and, if no V2G function feedback message is received from the battery management system within a preset time after sending the V2G function confirmation message, send a first indication message to the cloud server, the first indication message indicating that the target vehicle does not support the V2G function; and, if a V2G function feedback message is received from the battery management system within a preset time after sending the V2G function confirmation message, send a second indication message to the cloud server, the second indication message indicating that the target vehicle supports the V2G function. After receiving the second indication message, the cloud server, in response to the user's V2G charging mode selection command, sends a V2G charging command to the power grid to request the power grid to interact with the charging and discharging device through the power grid dispatch command for V2G scheduling. An execution module is configured to perform non-V2G charging on the target vehicle in response to a non-V2G charging command received from the cloud server; and to perform V2G charging or V2G discharging on the target vehicle in response to a received grid dispatch command.

11. A cloud server, characterized in that, include: The receiving module is configured to receive a first indication message and a second indication message from the charging and discharging device. The first indication message is sent by the charging and discharging device if it does not receive a V2G function feedback message within a preset time period after sending a V2G function confirmation message to the battery management system of the target vehicle, and is used to indicate that the target vehicle does not support the V2G function. The second indication message is sent by the charging and discharging device if it receives a V2G function feedback message within a preset time period after sending a V2G function confirmation message to the battery management system of the target vehicle, and is used to indicate that the target vehicle supports the V2G function. The sending module is used to send a non-V2G charging instruction to the terminal device, the non-V2G charging instruction being used to instruct the charging and discharging device to perform non-V2G charging on the target vehicle; and to send a V2G charging instruction to the power grid in response to the user's V2G charging mode selection instruction, so as to request the power grid to interact with the charging and discharging device through the power grid dispatching instruction to perform V2G dispatching.

12. A charging and discharging device, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the charge-discharge interaction method as described in any one of claims 1 to 5.

13. A cloud server, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the charge-discharge interaction method as described in any one of claims 6 to 9.

14. A charging and discharging system, characterized in that, It includes the charging and discharging device as described in claim 12 and the cloud server as described in claim 13.

15. The charging and discharging system according to claim 14, characterized in that, Also includes: A terminal device is configured to receive from the cloud server an indication message indicating that the target vehicle supports V2G functionality or an indication message indicating that the target vehicle does not support V2G functionality.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the charge-discharge interaction method as described in any one of claims 1 to 5.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the charge-discharge interaction method as described in any one of claims 6 to 9.

Images