Charging equipment, vehicle and charging management system

Abstract

The invention relates to a charging device, a vehicle and a charging management system, and the charging device comprises a charging terminal which is used for obtaining the vehicle information of the vehicle and executing the processing operation of the vehicle information; the information of the vehicle is obtained and processed through the charging equipment, and the state information of the vehicle can be known in real time conveniently.

Description

Technical Field

[0001] This application relates to the field of vehicle charging technology, and more particularly to a charging device, a vehicle, and a charging management system. Background Technology

[0002] As electric vehicles become more functional, it becomes essential to inspect them and assess their overall condition. Currently, users who wish to have their vehicles inspected need to take them to a repair shop or purchase specialized equipment, making inspections inconvenient and resulting in a poor user experience. Summary of the Invention

[0003] This application provides a charging device, a vehicle, and a charging management system, enabling the charging device to detect the vehicle's status while the vehicle is charging, thereby at least partially solving the aforementioned technical problems.

[0004] To achieve the above objectives, according to a first aspect of this application, a charging device (100) is provided, comprising: a charging terminal (110).

[0005] The charging terminal (110) is used to acquire vehicle information of the vehicle (200) and perform processing operations on the vehicle information.

[0006] Optionally, the vehicle information includes the target operating parameters of each controller in the vehicle (200).

[0007] Optionally, the charging terminal (110) is further configured to:

[0008] In response to a diagnostic request from a vehicle (200), the vehicle (200) sends the diagnostic request to each of the controllers and receives the target operating parameters fed back by each of the controllers.

[0009] Optionally, the charging terminal (110) is further configured to:

[0010] The vehicle (200) responds to the diagnostic request and sends it to the target device of the vehicle (200), so that the target device sends the diagnostic request of the vehicle (200) to each of the controllers via the vehicle network of the vehicle (200), and each of the controllers feeds back the target operating parameters to the target device via the vehicle network.

[0011] Optionally, the target operating parameters include at least one of the following: vehicle controller operating parameters, on-board charger operating parameters, and drive controller operating parameters.

[0012] Optionally, the processing operation includes at least one of the following: display operation, sending operation, and diagnostic operation.

[0013] Optionally, the sending object of the sending operation includes at least one of the following: vehicle (200), terminal device, cloud device (300), and after-sales service terminal.

[0014] Optionally, the charging device (100) further includes a charging host (120), which is connected to the charging terminal (110).

[0015] The charging host (120) is used to receive vehicle information sent by the charging terminal (110), and perform diagnostic operations on the vehicle information to obtain vehicle (200) diagnostic results.

[0016] Optionally, the charging host (120) is further configured to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), a terminal device, a cloud device (300), and an after-sales service terminal; and / or,

[0017] The charging host (120) is also used to send the diagnostic results of the vehicle (200) to the charging terminal (110), and through the charging terminal (110) send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal equipment, cloud equipment (300) and after-sales service terminal.

[0018] Optionally, the charging host (120) is adapted to communicate with the cloud device (300);

[0019] The charging host (120) is used to send the vehicle information to the cloud device (300).

[0020] Optionally, the charging host (120) is further configured to:

[0021] Receive the vehicle (200) diagnostic results fed back by the cloud device (300) based on the vehicle information.

[0022] Optionally, the charging host (120) is further configured to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), a terminal device, a cloud device (300), and an after-sales service terminal; and / or,

[0023] The charging host (120) is also used to send the diagnostic results of the vehicle (200) to the charging terminal (110), and the charging terminal (110) sends the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal equipment, cloud equipment (300) and after-sales service terminal.

[0024] Optionally, the charging device (100) further includes:

[0025] A transformer (130), one end of which is connected to the charging host (120), and the other end of which is adapted to be connected to the power grid;

[0026] The transformer (130) is used to process the electrical energy of the power grid and transmit it to the charging host (120).

[0027] Optionally, the charging device (100) further includes:

[0028] An energy storage cabinet (140) is connected to the charging host (120);

[0029] The energy storage cabinet (140) is used to discharge the charging host (120) and, together with the transformer (130), to charge the vehicle (200).

[0030] Optionally, the charging host (120) in the charging device (100) includes: a control unit (121),

[0031] The control unit (121) is used to process electrical energy and control the charging terminal (110) to charge the vehicle (200).

[0032] Optionally, the control component (121) includes: at least one charging module (1211) and at least one voltage regulating module (1212), wherein,

[0033] The charging module (1211) is used to convert the electrical energy output from the power grid into AC and DC power.

[0034] The voltage regulating module (1212) is used to adjust the voltage to charge the vehicle (200).

[0035] Optionally, the charging device (100) further includes: a communication module (150), wherein,

[0036] The communication module (150) is used to enable communication between the charging device (100) and the cloud device (300).

[0037] Optionally, the communication module (150) includes: a first communication module (151) and a second communication module (152), wherein,

[0038] The first communication module (151) is used to realize communication between the charging terminal (110) and the charging host (120) in the charging device (100);

[0039] The second communication module (152) is used to realize communication between the charging host (120) and the cloud device (300).

[0040] According to a second aspect of this application, a vehicle (200) is provided, the vehicle (200) comprising: a target device;

[0041] The target device is used to collect vehicle information of the vehicle (200) and send it to the charging device (100) to perform processing operations on the vehicle information.

[0042] Optionally, the target device is a battery manager and / or a vehicle controller.

[0043] Optionally, the vehicle information is the target operating parameters of each controller in the vehicle (200).

[0044] Optionally, the controller includes at least one of a vehicle controller, an on-board charger, and a drive controller.

[0045] Optionally, the target device and each of the controllers are connected via an in-vehicle network.

[0046] Optionally, the target device is further used for:

[0047] The vehicle (200) diagnostic request is sent to each of the controllers via the vehicle network, and the target operating parameters are received from each of the controllers via the vehicle network.

[0048] According to a second aspect of this application, a charging management system is provided, comprising: the aforementioned charging equipment (100), and the aforementioned vehicle (200), wherein,

[0049] The charging device (100) is electrically connected to the vehicle (200);

[0050] The vehicle (200) is used to send vehicle information to the charging device (100);

[0051] The charging device (100) is used to acquire the vehicle information sent by the vehicle (200) and perform processing operations on the vehicle information.

[0052] Optionally, the charging management system further includes: a cloud device (300),

[0053] The cloud device (300) is used to receive vehicle information sent by the charging device (100), perform vehicle (200) diagnosis based on the vehicle information, and obtain vehicle (200) diagnosis results.

[0054] Optionally, the cloud device (300) is also used to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal device, and after-sales service terminal.

[0055] Optionally, the cloud device (300) is also used to receive diagnostic requests from the vehicle (200) and send them to the charging device (100);

[0056] The charging device (100) is used to receive diagnostic requests from the vehicle (200) and send them to the vehicle (200);

[0057] The vehicle (200) is configured to receive a diagnostic request from the vehicle (200) and obtain vehicle information based on the diagnostic request.

[0058] This application provides a charging device (100) including a charging terminal (110), which is used to acquire vehicle information of a vehicle (200) and perform processing operations on the vehicle information. This application allows the charging device (100) to acquire and process vehicle information during the charging process of the vehicle (200), enabling users to monitor the vehicle (200) status in real time without requiring the user to take the vehicle (200) to a repair shop or purchase specialized equipment for maintenance, thus improving the user's driving experience.

[0059] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description

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

[0061] To gain a more complete understanding of this application and its beneficial effects, the following description will be provided in conjunction with the accompanying drawings, wherein the same reference numerals in the following description denote the same parts.

[0062] Figure 1 This is a schematic diagram of an architecture of a charging management system provided in an exemplary embodiment of this application;

[0063] Figure 2 This is a schematic diagram of another architecture of the charging management system provided in an exemplary embodiment of this application;

[0064] Figure 3 This is a schematic diagram of a terminal device display provided in an exemplary embodiment of this application;

[0065] Figure 4 This is a schematic diagram of the charging management process provided in an exemplary embodiment of this application. Detailed Implementation

[0066] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0067] In the description of this application, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are used 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 of this application. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0068] "A and / or B" includes the following three combinations: A only, B only, and a combination of A and B.

[0069] The use of "applies to" or "configured to" in this application implies open and inclusive language, which does not preclude applicability to or configuration to devices performing additional tasks or steps. Furthermore, the use of "based on" implies openness and inclusivity, because processes, steps, calculations, or other actions "based on" one or more conditions or values ​​may in practice be based on additional conditions or values ​​beyond those conditions.

[0070] In this application, the term "exemplary" is used to mean "serving as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to implement and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be implemented without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0071] According to the above background technical description of this application, if users want to inspect their vehicles, they need to send the vehicles to a repair shop or purchase special equipment, which is inconvenient for vehicle inspection and results in a poor user experience.

[0072] To address the aforementioned issues, this application proposes a charging device, a vehicle, and a charging management system, designed to allow users to easily access real-time vehicle status information without requiring them to take their vehicles to a repair shop or purchase specialized equipment for maintenance, thereby improving the user's driving experience.

[0073] Specifically, embodiments of this application provide a charging device 100, such as... Figure 1 As shown, the charging device 100 includes a charging terminal 110.

[0074] The charging terminal 110 is used to acquire vehicle information of vehicle 200 and perform processing operations on the vehicle information.

[0075] In this embodiment, as Figure 1 As shown, the charging terminal 110 is electrically connected to the vehicle 200, enabling the charging terminal 110 to obtain vehicle information of the vehicle 200 and perform corresponding processing operations.

[0076] It should be noted that, in this embodiment, vehicle information may include, but is not limited to, battery information of vehicle 200, such as battery health status (used to measure the ratio of the battery to the maximum storage capacity of a new battery), battery electrical performance indicators (such as discharge capacity retention rate, discharge energy retention rate, energy efficiency retention rate, peak power retention rate, DC internal resistance change rate, etc.), battery cycle count (i.e., the number of cycles from full charge to empty and then full charge, used to assess the degree of battery aging); engine performance information of vehicle 200 (such as engine speed, etc.), transmission system performance information of vehicle 200 (such as transmission oil temperature, etc.), braking system performance information of vehicle 200 (such as braking system pressure, etc.), etc.

[0077] In this embodiment, the charging terminal 110 and the vehicle 200 can be connected via communication methods including but not limited to CAN, CANONE, and Ethernet. The charging terminal 110 and the vehicle 200 can also be connected via a power transmission method based on the principle of electromagnetic wave induction. Thus, the charging terminal 110 can charge the vehicle 200 and acquire vehicle information during the charging process, sending the vehicle information to the corresponding terminal device of the vehicle 200 via a charging network such as a CAN network. This embodiment does not limit the connection method between the vehicle 200 and the terminal device; for example, it can be a wireless connection method such as Bluetooth or WIFI.

[0078] In one embodiment, since the power battery of an electric vehicle will suffer some losses during use, the charging terminal 110 can also calibrate the battery health status information and expected driving range of the vehicle 200, so that the owner can monitor the real-time status of the vehicle 200 during the use of the vehicle.

[0079] Specifically, for example, such as Figure 1 As shown, vehicle 200 may include a battery manager (i.e., the target device in this embodiment) and multiple controllers connected to the battery manager via an in-vehicle network (such as a CAN network), such as a vehicle controller, an on-board charger, and a drive controller. In this way, the battery manager can forward vehicle information acquisition requests through the in-vehicle network. Each controller of vehicle 200 can respond to the acquisition request, collect vehicle information of vehicle 200, and transmit it back to the battery manager through the in-vehicle network. The battery manager can send the vehicle information to the charging terminal 110 through the CAN network. This embodiment does not limit the triggering method of the above-mentioned vehicle information acquisition request, such as triggering based on the charging terminal 110, triggering based on the terminal device, etc.

[0080] In one embodiment, the vehicle information includes target operating parameters for each controller in the vehicle 200.

[0081] In this embodiment, as described above, the controllers in the vehicle 200 include, but are not limited to, the vehicle controller, the on-board charger, and the drive controller. Correspondingly, the vehicle information includes, but is not limited to, the target operating parameters of each controller.

[0082] In one specific embodiment, the target operating parameters include, but are not limited to, at least one of the following: vehicle controller operating parameters, on-board charger operating parameters, and drive controller operating parameters.

[0083] In this embodiment, vehicle information may include, but is not limited to, the operating parameters of the vehicle controller, the operating parameters of the on-board charger, and the operating parameters of the drive controller, and may also include, but is not limited to, engine performance parameters and transmission system performance parameters.

[0084] In one embodiment, the charging terminal 110 is further configured to:

[0085] The vehicle responds to the vehicle diagnostic request and sends it to vehicle 200. Vehicle 200 then sends the vehicle diagnostic request to each controller and receives the target operating parameters fed back by each controller.

[0086] In this embodiment, the triggering method of the vehicle diagnostic request is not limited. For example, the vehicle diagnostic request can be triggered actively by the user or automatically by the charging terminal 110.

[0087] The charging terminal 110 can respond to the vehicle diagnostic request and send the vehicle diagnostic request to the vehicle 200. The vehicle 200 can then send the vehicle diagnostic request to each controller and receive the target operating parameters fed back by each controller.

[0088] In one specific embodiment, the charging terminal 110 is further configured to:

[0089] The system responds to vehicle diagnostic requests and sends them to the target device in vehicle 200, so that the target device sends the vehicle diagnostic request to each controller via the vehicle network of vehicle 200, and each controller feeds back the target operating parameters to the target device via the vehicle network.

[0090] In this embodiment, the charging terminal 110 can receive a vehicle diagnostic request and send the vehicle diagnostic request to the vehicle 200 via the CAN network. The battery manager of the vehicle 200 (i.e., the target device in this embodiment) can forward the vehicle diagnostic request to each controller via the vehicle network. Each controller can respond to the vehicle diagnostic request, collect the target operating parameters of the vehicle 200, and send them back to the battery manager via the vehicle network. The battery manager can then feed back the vehicle information to the charging terminal 110 via the CAN network.

[0091] In one embodiment, the processing operation includes at least one of a display operation, a sending operation, and a diagnostic operation.

[0092] In this embodiment, after obtaining the vehicle information of the vehicle 200, the charging terminal 110 can perform at least one of the following operations: display operation, send operation, and diagnostic operation.

[0093] For example, the charging terminal 110 can display vehicle information on its screen; it can also send the vehicle information (vehicle 200) to at least one of the terminal device, cloud device 300, and after-sales service terminal; and it can also perform fault diagnosis on vehicle 200 based on the vehicle information.

[0094] In this embodiment, the terminal device can be a user terminal device, such as a mobile phone, tablet, computer, or vehicle display terminal. The terminal device can be connected to the vehicle 200 via Bluetooth, WIFI, or CAN bus, and there is no specific limitation on this.

[0095] In one specific embodiment, the sending object of the sending operation includes at least one of the following: vehicle 200, terminal device, cloud device 300, and after-sales service terminal.

[0096] In one embodiment, the charging device 100 further includes a charging host 120, which is connected to the charging terminal 110.

[0097] The charging host 120 is used to receive vehicle information sent by the charging terminal 110, perform diagnostic operations on the vehicle information, and obtain vehicle diagnostic results.

[0098] In this embodiment, as Figure 1 As shown, the charging host 120 and the charging terminal 110 are connected in communication. After the charging terminal 110 obtains the vehicle information of the vehicle 200, it can send the vehicle information to the charging host 120.

[0099] The charging host 120 can receive the vehicle information and perform diagnostic operations on the vehicle information to obtain the vehicle diagnostic results.

[0100] In addition, the charging host 120 can also send the vehicle information to the terminal device, so that the terminal device user can know the current status of the vehicle 200 in a timely manner and repair it in time when the vehicle 200 malfunctions, thus avoiding traffic accidents.

[0101] In one embodiment, the charging host 120 is further configured to send vehicle diagnostic results to at least one of the following: vehicle 200, terminal device, cloud device 300, and after-sales service terminal; and / or,

[0102] The charging host 120 is also used to send vehicle diagnostic results to the charging terminal 110, and through the charging terminal 110, send the vehicle diagnostic results to at least one of the following: vehicle 200, terminal equipment, cloud equipment 300, and after-sales service terminal.

[0103] In this embodiment, after the charging host 120 performs a diagnostic operation and obtains the vehicle diagnostic results, it can directly send the vehicle diagnostic results to the vehicle 200, the terminal device, the cloud device 300, and / or the after-sales service terminal.

[0104] In addition, the charging host 120 can first send the vehicle diagnostic results to the charging terminal 110, and the charging terminal 110 then sends the vehicle diagnostic results to the vehicle 200, the terminal equipment, the cloud equipment 300 and / or the after-sales service terminal.

[0105] For example, the charging host 120 can select the corresponding transmission path based on the network environment and / or the working status of the charging terminal 110 to ensure that the vehicle 200, terminal equipment, cloud equipment 300 and / or after-sales service can receive the vehicle diagnostic results normally. The vehicle diagnostic results may include, but are not limited to, detailed information on vehicle faults.

[0106] Among them, the charging device 100 can communicate with the after-sales service terminal. Figure 1(Not shown in the image). Thus, the charging host 120 can also send the vehicle diagnostic results to the after-sales service terminal. Upon receiving the vehicle diagnostic results, the after-sales service terminal can generate a corresponding fault repair strategy based on the results and send the strategy to the terminal device, reminding the user to have the vehicle 200 repaired promptly.

[0107] In one embodiment, the charging device 100 further includes a charging host 120, which is adapted to communicate with the cloud device 300;

[0108] The charging host 120 is used to: receive vehicle information sent by the charging terminal 110 and send the vehicle information to the cloud device 300.

[0109] In this embodiment, the charging host 120 can communicate with the cloud device 300, so that after the charging host 120 obtains the vehicle information of the vehicle 200, it can send the vehicle information to the cloud device 300, so that the cloud device 300 can perform vehicle diagnosis based on the vehicle information and obtain the corresponding vehicle diagnosis result.

[0110] In one embodiment, the charging host 120 is further configured to:

[0111] Receive vehicle diagnostic results from cloud device 300 based on vehicle information feedback.

[0112] In this embodiment, the cloud device 300 can perform vehicle 200 diagnosis based on vehicle information, obtain the corresponding vehicle diagnosis result, and return the vehicle diagnosis result to the charging host 120.

[0113] The charging host 120 can receive vehicle diagnostic results from the cloud device 300 based on vehicle information feedback.

[0114] In one embodiment, the charging host 120 is further configured to send vehicle diagnostic results to at least one of the following: vehicle 200, terminal device, cloud device 300, and after-sales service terminal; and / or,

[0115] The charging host 120 is also used to send vehicle diagnostic results to the charging terminal 110, which in turn sends the vehicle diagnostic results to at least one of the following: vehicle 200, terminal equipment, cloud equipment 300, and after-sales service terminal.

[0116] In this embodiment, after obtaining the vehicle diagnostic results through diagnostic operations, the charging host 120 can directly send the vehicle diagnostic results to the vehicle 200, the terminal device, the cloud device 300, and / or the after-sales service terminal. Alternatively, the charging host 120 can first send the vehicle diagnostic results to the charging terminal 110, and the charging terminal 110 can then send the vehicle diagnostic results to the vehicle 200, the terminal device, the cloud device 300, and / or the after-sales service terminal, as described in the above embodiment, which will not be repeated here.

[0117] In one embodiment, the charging device 100 further includes:

[0118] Transformer 130, one end of which is connected to the charging host 120, and the other end of which is adapted to be connected to the power grid;

[0119] Transformer 130 is used to process electrical energy from the power grid and transmit it to the charging host 120.

[0120] In this embodiment, as Figure 1 As shown, the charging device 100 may also include a transformer 130, the two ends of which can be connected to the charging host 120 and the power grid, respectively.

[0121] In this way, the transformer 130 can receive electrical energy transmitted from the power grid, and perform voltage transformation, isolation, phase conversion and other processing on the electrical energy, and transmit the processed electrical energy to the charging host 120, so that the charging host 120 can control the charging terminal 110 to charge the vehicle 200.

[0122] In one embodiment, the charging device 100 further includes:

[0123] Energy storage cabinet 140, which is connected to charging host 120;

[0124] The energy storage cabinet 140 is used to discharge the charging host 120 and, together with the transformer 130, to charge the vehicle 200.

[0125] In this embodiment, as Figure 1 As shown, the charging device 100 may also include an energy storage cabinet 140, which can be connected to the charging host 120.

[0126] In this way, the energy storage cabinet 140 can discharge the charging host 120 and work with the transformer 130 to charge the vehicle 200, thereby reducing the selection of the transformer 130.

[0127] In addition, in this embodiment, the energy storage cabinet 140 can store electrical energy to achieve peak shaving and valley filling of fluctuating electricity prices and realize the function of high-power charging. The energy storage cabinet 140 may include a battery module, a battery management module, a battery monitoring module, and an Ethernet communication module.

[0128] In one embodiment, the charging host 120 in the charging device 100 includes: a control component 121,

[0129] The control unit 121 is used to process electrical energy and control the charging terminal 110 to charge the vehicle 200.

[0130] The control unit 121 in the charging host 120 can process electrical energy and control the charging terminal 110 to charge the vehicle 200.

[0131] In addition to the control component 121, the charging host 120 may also include, but is not limited to, a communication interface module, a safety management module, etc., without any specific limitations.

[0132] In one specific embodiment, the control component 121 includes: at least one charging module 1211 and at least one voltage regulating module 1212, wherein,

[0133] The charging module 1211 is used to convert electrical energy output from the power grid into AC or DC power.

[0134] The voltage regulation module 1212 is used to adjust the voltage for charging the vehicle 200.

[0135] In this embodiment, the control unit 121 may include at least one charging module 1211 and at least one voltage regulating module 1212.

[0136] The charging module 1211 can convert electrical energy output from the grid into AC and DC power, while the voltage regulating module 1212 can adjust the voltage to charge the vehicle 200.

[0137] like Figure 2 As shown, the charging module 1211 can convert the electrical energy output from the power grid into AC and DC and send the converted electrical energy to the charging host 120; while the voltage regulating module 1212 can adjust the voltage of the electrical energy in the charging host 120 and use the adjusted electrical energy to charge the vehicle 200.

[0138] In one embodiment, the charging device 100 further includes a communication module 150, wherein,

[0139] The communication module 150 is used to enable communication between the charging device 100 and the cloud device 300.

[0140] The charging device 100 and the cloud device 300 can communicate through the communication module 150, so that the charging device 100 can send vehicle information or vehicle diagnostic results to the cloud device 300 through the communication module 150.

[0141] In another embodiment, such as Figure 2 As shown, if the communication module 150 and the control component 121 are within the same controller, they need to perform communication forwarding and control tasks separately, which can easily lead to mutual interference. Therefore, in this embodiment, the communication module 150 and the control component 121 can also be separated to perform the two tasks of communication and control independently, achieving physical isolation. This effectively isolates the mutual interference between the two tasks. Their independence can better meet different needs, enabling the signal sent by the cloud device 300 to the charging terminal 110 during operation to be directly transmitted to the charging terminal 110 via the high-speed network through the communication module 150.

[0142] In one specific embodiment, the communication module 150 includes: a first communication module 151 and a second communication module 152, wherein,

[0143] The first communication module 151 is used to realize communication between the charging terminal 110 and the charging host 120 in the charging device 100;

[0144] The second communication module 152 is used to realize communication between the charging host 120 and the cloud device 300.

[0145] In this embodiment, as Figure 2 As shown, the first communication module 151 can provide communication between the charging terminal 110 and the charging host 120 (i.e., Figure 2 The host-terminal communication shown is provided, while the second communication module 152 can provide communication between the charging host 120 and the cloud device 300 (i.e., the host-terminal communication shown). Figure 2 (As shown in the host-cloud communication), in this way, by establishing a cloud-pile-vehicle-storage collaborative charging system, it is possible to diagnose vehicle 200 while charging vehicle 200.

[0146] In one embodiment, the communication network between the charging host 120 and the charging terminal 110 in the above-mentioned cloud-pile-vehicle-storage collaborative charging system can adopt star Ethernet, ring Ethernet, CAN and other communication methods. The communication between the charging host 120 and the energy storage cabinet 140 can adopt Ethernet, CAN and other communication methods. The communication between the charging host 120 and the cloud platform can adopt 4G, WiFi or direct Ethernet connection.

[0147] Accordingly, this application provides a vehicle 200, which includes: a target device;

[0148] The target device is used to collect vehicle information from vehicle 200 and send it to the charging equipment 100 to perform processing operations on the vehicle information.

[0149] In one embodiment, the target device is a battery manager and / or a vehicle controller.

[0150] In one embodiment, the vehicle information is the target operating parameters of each controller in vehicle 200.

[0151] In one embodiment, the controller includes at least one of a vehicle controller, an on-board charger, and a drive controller.

[0152] In one embodiment, the target device and each controller are connected via an in-vehicle network.

[0153] In one embodiment, the target device is further configured to:

[0154] Vehicle diagnostic requests are sent to each controller via the in-vehicle network, and target operating parameters are received from each controller via the in-vehicle network.

[0155] Based on the above embodiments, the controllers in vehicle 200 include, but are not limited to, vehicle controllers, on-board chargers, drive controllers, etc. Correspondingly, vehicle information includes the target operating parameters of each controller, including but not limited to at least one of the operating parameters of the vehicle controller, the on-board charger, and the drive controller.

[0156] In this embodiment, the charging terminal 110 can receive the vehicle diagnostic request and send it to the vehicle 200 via the CAN network. The battery manager of the vehicle 200 can forward the vehicle diagnostic request to each controller via the vehicle network. Each controller can respond to the vehicle diagnostic request, collect the target operating parameters of the vehicle 200, and transmit them back to the battery manager via the vehicle network. The battery manager can then feed back the vehicle information to the charging terminal 110 via the CAN network. Referring to the above embodiment, further details are omitted here.

[0157] In summary, when the charging device 100 is connected to the vehicle 200, the network diagram of the cloud-charging pile-vehicle-storage collaborative charging system can include at least five parts:

[0158] (1) Cloud device 300: Connects to the user's APP server. After scanning the code and making a payment, the cloud platform issues instructions to start / stop charging, stores the status and fault information during the charging process, and coordinates the information scheduling of various stations.

[0159] (2) Charging host 120: Rectifies and regulates the electrical energy of transformer 130 / energy storage cabinet 140 and transmits it to charging terminal 110 to charge vehicle 200 (such as electric vehicle). When the energy storage is insufficient, it charges energy storage cabinet 140 to meet the power requirements of charging terminal 110 and realizes the scheduling of different voltage regulation modules 1212. It serves as the interaction hub of cloud device 300, energy storage cabinet 140 and charging terminal 110. Charging host 120 includes, but is not limited to, rectification module, voltage regulation module 1212, power distribution module, 4G module, WiFi module and Ethernet communication module 150.

[0160] (3) Charging terminal 110: completes the charging interaction process with the electric vehicle, analyzes the power demand of the vehicle 200 and requires the charging host 120 to meet the power output, and monitors the vehicle 200 faults, its own faults and the status during the charging process; the charging terminal 110 includes but is not limited to Ethernet communication module 150, radio frequency card reader, power metering module, charging process controller, etc.

[0161] (4) Energy storage cabinet 140: Stores electrical energy to achieve peak shaving and valley filling for fluctuating electricity prices and realizes high-power charging function; Energy storage cabinet 140 includes but is not limited to battery module, battery management module, battery monitoring module and Ethernet communication module 150.

[0162] (5) Vehicle 200, which may be an electric vehicle: a receiver of charging power, interacting with charging terminal 110 to complete power replenishment. Vehicle 200 may contain two or more electronic controllers (not limited to battery manager, vehicle controller, on-board charger, etc.), and the battery manager that interacts with charging terminal 110 is connected to other controllers through an on-board network.

[0163] Through the connection method between the controller and the communication network described above, an integrated design of cloud device 300, charging host 120, charging terminal 110, energy storage cabinet 140, and vehicle 200 can be realized. This integrates vehicle 200 into the charging and energy storage system for collaborative management and intelligent scheduling. Furthermore, through the cloud-charging-vehicle-storage-collaborative design scheme described above, in addition to peak shaving and valley filling to achieve higher economic efficiency during electricity price fluctuations, the power in energy storage cabinet 140 can be used as backup energy for charging host 120 when grid power is insufficient, meeting the overcharging needs of vehicle 200.

[0164] Accordingly, this application also provides a charging management system, which may include the charging device 100 and the vehicle 200 in the above embodiments, wherein,

[0165] The charging device 100 is electrically connected to the vehicle 200;

[0166] Vehicle 200 is used to send vehicle information to charging equipment 100;

[0167] The charging device 100 is used to obtain vehicle information sent by the vehicle 200 and perform processing operations on the vehicle information.

[0168] In this embodiment, as Figure 1 As shown, the charging device 100 is connected to the vehicle 200. Thus, the vehicle 200 can collect vehicle information and send it to the charging device 100, and the charging device 100 can receive the vehicle information sent by the vehicle 200 and perform processing operations on the vehicle information.

[0169] In one embodiment, the charging management system further includes: a cloud device 300, wherein,

[0170] The cloud device 300 is used to receive vehicle information sent by the charging device 100, perform vehicle diagnosis based on the vehicle information, and obtain vehicle diagnosis results.

[0171] In this embodiment, after obtaining the vehicle information of the vehicle 200, the charging device 100 can send the vehicle information to the cloud device 300, and the cloud device 300 can perform a diagnosis on the vehicle 200 based on the vehicle information to obtain the corresponding vehicle diagnosis result.

[0172] In one embodiment, the cloud device 300 is also used to send vehicle diagnostic results to at least one of the vehicle 200, a terminal device, and an after-sales service terminal.

[0173] In this embodiment, after the cloud device 300 performs vehicle diagnosis based on the vehicle information and obtains the vehicle diagnosis result, it can feed back the vehicle diagnosis result to at least one of the vehicle 200, the terminal device, and the after-sales service terminal. See the above embodiment for details, which will not be repeated here.

[0174] In one embodiment, the cloud device 300 is also configured to receive vehicle diagnostic requests and send them to the charging device 100;

[0175] Charging device 100 is used to receive vehicle diagnostic requests and send them to vehicle 200;

[0176] Vehicle 200 is used to receive vehicle diagnostic requests and obtain vehicle information based on the vehicle diagnostic requests.

[0177] In this embodiment, the cloud device 300 can receive a vehicle diagnostic request and send it to the charging device 100. The charging device 100 can receive the vehicle diagnostic request and send it to the vehicle 200 via the CAN network. The battery manager of the vehicle 200 can forward the vehicle diagnostic request to each controller via the vehicle network. Each controller can respond to the vehicle diagnostic request, collect the target operating parameters of the vehicle 200, and transmit them back to the battery manager via the vehicle network. The battery manager can then feed back the vehicle information to the charging device 100 via the CAN network.

[0178] In summary, the cloud-charging pile-vehicle-storage collaborative supercharging system and communication scheme in this application embodiment can provide a series of services such as charging, discharging, and diagnostics for vehicle 200. Compared with most existing technologies that only realize the charging function of the charging pile without other diagnostic and calibration functions, this application can integrate diagnostic and calibration functions into the charging pile. Users can diagnose vehicle 200 themselves according to their needs and understand the usage of vehicle 200. Moreover, most current methods for achieving supercharging of vehicle 200 adopt the method of adding transformer substation, which will cause additional costs. However, the cloud-charging pile-vehicle-storage collaborative scheme in this application can achieve the supercharging function without adding transformer substation, improve the charging efficiency of vehicle 200, and save costs.

[0179] Accordingly, this application also provides a charging management method, which can be applied to a charging device 100, the charging device 100 being electrically connected to a vehicle 200, the method comprising:

[0180] S10: Obtain vehicle information of vehicle 200 and send it to the terminal device corresponding to vehicle 200.

[0181] It should be noted that, in this embodiment, vehicle information may include, but is not limited to, battery information of vehicle 200, such as battery health status (used to measure the ratio of the battery to the maximum storage capacity of a new battery), battery electrical performance indicators (such as discharge capacity retention rate, discharge energy retention rate, energy efficiency retention rate, peak power retention rate, DC internal resistance change rate, etc.), battery cycle count (i.e., the number of cycles from full charge to empty and then full charge, used to assess the degree of battery aging), and vehicle information may also include engine performance (such as engine speed, etc.), transmission system performance (such as transmission oil temperature, etc.), and braking system performance (such as braking system pressure, etc.).

[0182] The above are just some examples of possible vehicle information. In this embodiment, the charging device 100 can actually send comprehensive information about the vehicle 200 to the terminal device corresponding to the vehicle 200. In this embodiment, the terminal device can be a user device, such as a mobile phone, tablet, computer, or in-vehicle display, to send vehicle information to the user.

[0183] In one embodiment, in S10 above, "obtaining vehicle information of vehicle 200" may include:

[0184] S101 receives the target operating parameters collected by the devices in vehicle 200 from each controller, and sets each target operating parameter as vehicle information.

[0185] It should be noted that, in this embodiment, the target operating parameters of each controller include, but are not limited to, driving parameters, battery parameters, drive control parameters, etc., and the above operating parameters are sent to the charging device 100 through the CAN network.

[0186] The charging device 100 can set the received operating information as vehicle information to perform vehicle 200 diagnostics.

[0187] In one embodiment, the device is a battery manager and / or controller, and,

[0188] The controller includes at least one of the following: vehicle controller, on-board charger, and drive controller.

[0189] It should be noted that, in this embodiment, the devices include, but are not limited to, the battery manager and controller in the vehicle 200. Correspondingly, the controller in this embodiment may include multiple controllers connected to the battery manager via an in-vehicle network, such as the vehicle controller, the on-board charger, the drive controller, etc.

[0190] In one embodiment, the charging management method of this application may further include:

[0191] S20, receive vehicle diagnostic request and send it to vehicle 200, so that the devices in vehicle 200 send the vehicle diagnostic request to each controller via the vehicle network, and receive the target operating parameters fed back by each controller via the vehicle network.

[0192] It should be noted that, in this embodiment, the aforementioned vehicle diagnostic request can be triggered by the user based on a terminal device, for example, as... Figure 3 As shown, the terminal device can be an in-vehicle PAD. The PAD's display interface can show vehicle information and diagnostic options (not shown in the figure). In this way, the user can operate the diagnostic option to trigger the corresponding vehicle diagnostic request.

[0193] Thus, in this embodiment, the charging device 100 can receive the vehicle diagnostic request and send it to the vehicle 200 via the CAN network. The battery manager of the vehicle 200 can forward the vehicle diagnostic request to each controller via the vehicle network. Each controller can respond to the vehicle diagnostic request, collect the target operating parameters of the vehicle 200, and transmit them back to the battery manager via the vehicle network. The battery manager can then feed back the vehicle information to the charging device 100 via the CAN network.

[0194] Additionally, when the charging device 100 is charging the vehicle 200, the in-vehicle PAD display interface in this embodiment can also enter the charging process, displaying charging parameters such as the current charging current, voltage, and estimated charging time. When the user clicks the "End Charging" button displayed on this interface, such as... Figure 1 As shown, the PAD can send the charging end status to the controller of the charging host 120 that interacts with the charging terminal 110 via the CAN network. After receiving the corresponding signal, the controller can send a signal to the charging terminal 110 to end charging. After receiving the signal, the charging terminal 110 controls the charging to stop.

[0195] In one embodiment, the charging management method of this application may further include:

[0196] S30 performs vehicle diagnostics based on vehicle information, obtains vehicle diagnostic results, and outputs them.

[0197] In this embodiment, after obtaining the vehicle information of the vehicle 200, the charging device 100 can perform vehicle diagnosis based on the vehicle information, obtain vehicle diagnosis results and output them. For example, the vehicle diagnosis results can be sent to the terminal device, and the terminal device can display the vehicle diagnosis results.

[0198] In one embodiment, S30 above, "performing vehicle 200 diagnosis based on vehicle information and obtaining vehicle diagnosis results" may include:

[0199] S301, for each controller in the vehicle information, obtains the operating status based on the target operating parameters and the standard parameters of the controller;

[0200] S302, statistically analyzes the operating status of each control device to obtain vehicle diagnostic results.

[0201] In this embodiment, after the charging device 100 obtains the target operating parameters corresponding to the vehicle controller, on-board charger, and drive controller, it can compare the target operating parameters with the corresponding standard parameters. For example, it can compare the number of battery charge-discharge cycles of the vehicle 200 with the preset number of charge-discharge cycles. If the number of battery charge-discharge cycles exceeds the preset number of charge-discharge cycles, the operating state at this time is abnormal, and the vehicle diagnostic result can be determined that the vehicle 200 has a fault.

[0202] In one embodiment, S30 above, "performing vehicle 200 diagnosis based on vehicle information and obtaining vehicle diagnosis results" may include:

[0203] Send vehicle information to cloud device 300;

[0204] Receive vehicle diagnostic results from cloud device 300 based on vehicle information feedback.

[0205] In this embodiment, after obtaining the vehicle information of the vehicle 200, the charging device 100 can send the vehicle information to the cloud device 300. The cloud device 300 then performs a diagnosis on the vehicle 200 based on the vehicle information, obtains the corresponding vehicle diagnosis result, and feeds back the vehicle diagnosis result to the charging device 100.

[0206] The charging device 100 can receive vehicle diagnostic results from the cloud device 300 based on vehicle information feedback, and optimize the performance parameters of the vehicle 200 according to the vehicle diagnostic results. For example, the charging device 100 can adjust the charging and discharging rates according to the current state of the battery and environmental conditions to reduce the heat generation and loss of the battery, thereby extending the battery life.

[0207] In addition, the cloud device 300 can also send vehicle diagnostic results to the terminal device to remind users to pay attention to the vehicle's status.

[0208] As can be seen, in this application, the vehicle 200 diagnostic operation can be performed by the charging device 100 or by the cloud device 300. Even if the network environment is limited, the vehicle 200 can be diagnosed, which improves the diagnostic efficiency of the vehicle 200 and ensures the safety of the vehicle 200.

[0209] In one embodiment, the charging management method of this application may further include:

[0210] S30, if the vehicle diagnostic result indicates that vehicle 200 has a fault, sends the vehicle diagnostic result to the terminal device corresponding to vehicle 200 and / or the after-sales service terminal of vehicle 200.

[0211] In this embodiment, after the charging device 100 performs vehicle 200 diagnosis based on vehicle information and obtains the corresponding vehicle diagnosis result, it can determine whether the vehicle 200 currently has a fault based on the vehicle diagnosis result.

[0212] If vehicle 200 is currently malfunctioning, the diagnostic results can be sent to the terminal device corresponding to vehicle 200 and / or the after-sales service terminal of vehicle 200, reminding the user to pay attention to the malfunction of vehicle 200 and repair it in time.

[0213] In one embodiment, the vehicle diagnostic request includes at least one of a first vehicle diagnostic request, a second vehicle diagnostic request, and a second vehicle diagnostic request; wherein,

[0214] The first vehicle diagnostic request was sent by vehicle 200;

[0215] The second vehicle diagnostic request is sent by the terminal device corresponding to vehicle 200;

[0216] The third vehicle diagnostic request was sent by the charging device 100 and the associated cloud device 300.

[0217] In this embodiment, according to the above description, the terminal device can receive a vehicle diagnostic request, perform vehicle 200 diagnostics based on the vehicle information, and obtain the vehicle diagnostic results.

[0218] Specifically, for example, the vehicle diagnostic request in this embodiment can be at least one of a first vehicle diagnostic request, a second vehicle diagnostic request, and a second vehicle diagnostic request.

[0219] The first vehicle diagnostic request can be sent by vehicle 200; the second vehicle diagnostic request can be sent by the terminal device corresponding to vehicle 200; and the third vehicle diagnostic request can be sent by cloud device 300 communicating with charging device 100.

[0220] That is, in this embodiment, in addition to the user actively controlling the charging device 100 to perform vehicle 200 diagnosis, it can also be triggered by the vehicle 200 or the cloud device 300. For example, the vehicle 200 can periodically trigger a vehicle diagnosis request to perform vehicle 200 diagnosis, and there are no specific limitations on this.

[0221] In one specific embodiment, such as Figure 4As shown, during the charging process, if the user clicks "Start Diagnosis" on the terminal device's APP, the charging terminal 110 will perform diagnostic services on the vehicle 200. The charging terminal 110 first identifies the vehicle 200, reading information such as model and year of manufacture. Then, it sends the corresponding vehicle diagnostic request via the CAN network to the battery manager that interacts with the charging device 100. The battery manager forwards the vehicle diagnostic request to the vehicle network. After the controllers in the vehicle 200 respond to the diagnostic service command, the data is transmitted back to the CAN network via the battery manager and displayed on the user's APP via the host-terminal communication network and the host-cloud communication network. If a serious fault is found after diagnosis by the charging terminal 110, the APP will ask the customer if they want to notify after-sales service. After obtaining their consent, after-sales service will be notified.

[0222] Therefore, in this embodiment of the application, the charging device 100 can simultaneously monitor the health status of the vehicle 200 while charging the vehicle 200. This can not only eliminate vehicle 200 malfunctions and improve vehicle 200 safety, but also eliminate the need for additional hardware, saving construction costs. At the same time, it can also allow users on the terminal device to know the status of the vehicle 200 in a timely manner, improving the user's car use experience.

[0223] In the above descriptions of the charging device 100, vehicle 200, charging management system, and method, each embodiment has its own emphasis. Parts not detailed in a particular embodiment can be found in the relevant descriptions of other embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes and beneficial effects of the charging device 100, vehicle 200, charging management system, and method described above can be referred to the description of the charging management method in the above embodiments, and will not be repeated here.

[0224] The charging device 100, vehicle 200, charging management system and method provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A charging device, characterized in that, The charging device (100) includes: a charging terminal (110), The charging terminal (110) is used to acquire vehicle information of the vehicle (200) and perform processing operations on the vehicle information.

2. The charging device according to claim 1, characterized in that, The vehicle information includes the target operating parameters of each controller in the vehicle (200).

3. The charging device according to claim 2, characterized in that, The charging terminal (110) is also used for: In response to a diagnostic request from a vehicle (200), the vehicle (200) sends the diagnostic request to each of the controllers and receives the target operating parameters fed back by each of the controllers.

4. The charging device according to claim 3, characterized in that, The charging terminal (110) is also used for: The vehicle (200) responds to the diagnostic request and sends it to the target device of the vehicle (200), so that the target device sends the diagnostic request of the vehicle (200) to each of the controllers via the vehicle network of the vehicle (200), and each of the controllers feeds back the target operating parameters to the target device via the vehicle network.

5. The charging device according to claim 2, characterized in that, The target operating parameters include at least one of the following: vehicle controller operating parameters, on-board charger operating parameters, and drive controller operating parameters.

6. The charging device according to claim 1, characterized in that, The processing operations include at least one of the following: display operation, sending operation, and diagnostic operation.

7. The charging device according to claim 6, characterized in that, The sending object of the sending operation includes at least one of the following: vehicle (200), terminal device, cloud device (300), and after-sales service terminal.

8. The charging device according to claim 1, characterized in that, The charging device (100) further includes a charging host (120), which is connected to the charging terminal (110). The charging host (120) is used to receive vehicle information sent by the charging terminal (110), and perform diagnostic operations on the vehicle information to obtain vehicle (200) diagnostic results.

9. The charging device according to claim 8, characterized in that, The charging host (120) is also used to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), a terminal device, a cloud device (300), and an after-sales service terminal; and / or, The charging host (120) is also used to send the diagnostic results of the vehicle (200) to the charging terminal (110), and through the charging terminal (110) send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal equipment, cloud equipment (300) and after-sales service terminal.

10. The charging device according to claim 1, characterized in that, The charging device (100) further includes a charging host (120) adapted to communicate with a cloud device (300); The charging host (120) is used to: receive vehicle information sent by the charging terminal (110) and send the vehicle information to the cloud device (300).

11. The charging device according to claim 10, characterized in that, The charging host (120) is also used for: Receive the vehicle (200) diagnostic results fed back by the cloud device (300) based on the vehicle information.

12. The charging device according to claim 11, characterized in that, The charging host (120) is also used to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal equipment, cloud equipment (300), and after-sales service terminal; and / or, The charging host (120) is also used to send the diagnostic results of the vehicle (200) to the charging terminal (110), and the charging terminal (110) sends the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal equipment, cloud equipment (300) and after-sales service terminal.

13. The charging device according to any one of claims 8 to 12, characterized in that, The charging device (100) also includes: A transformer (130), one end of which is connected to the charging host (120), and the other end of which is adapted to be connected to the power grid; The transformer (130) is used to process the electrical energy of the power grid and transmit it to the charging host (120).

14. The charging device according to claim 13, characterized in that, The charging device (100) also includes: An energy storage cabinet (140) is connected to the charging host (120); The energy storage cabinet (140) is used to discharge the charging host (120) and, together with the transformer (130), to charge the vehicle (200).

15. The charging device according to claim 1, characterized in that, The charging host (120) in the charging device (100) includes: a control component (121), The control unit (121) is used to process electrical energy and control the charging terminal (110) to charge the vehicle (200).

16. The charging device according to claim 15, characterized in that, The control component (121) includes: at least one charging module (1211) and at least one voltage regulating module (1212), wherein, The charging module (1211) is used to convert the electrical energy output from the power grid into AC and DC power. The voltage regulating module (1212) is used to adjust the voltage to charge the vehicle (200).

17. The charging device according to claim 7, characterized in that, The charging device (100) further includes: a communication module (150), wherein, The communication module (150) is used to enable communication between the charging device (100) and the cloud device (300).

18. The charging device according to claim 17, characterized in that, The communication module (150) includes: a first communication module (151) and a second communication module (152), wherein, The first communication module (151) is used to realize communication between the charging terminal (110) and the charging host (120) in the charging device (100); The second communication module (152) is used to realize communication between the charging host (120) and the cloud device (300).

19. A vehicle, characterized in that, The vehicle (200) includes: a target device; The target device is used to collect vehicle information of the vehicle (200) and send it to the charging device (100) as described in any one of claims 1-18 to perform processing operations on the vehicle information.

20. The vehicle according to claim 19, characterized in that, The target device is a battery manager and / or a vehicle controller.

21. The vehicle according to claim 20, characterized in that, The vehicle information refers to the target operating parameters of each controller in the vehicle (200).

22. The vehicle according to claim 21, characterized in that, The controller includes at least one of a vehicle controller, an on-board charger, and a drive controller.

23. The vehicle according to claim 21 or 22, characterized in that, The target device and each of the controllers are connected via an in-vehicle network.

24. The vehicle according to claim 23, characterized in that, The target device is also used for: The vehicle (200) diagnostic request is sent to each of the controllers via the vehicle network, and the target operating parameters are received from each of the controllers via the vehicle network.

25. A charging management system, characterized in that, The charging management system includes: a charging device (100) as described in any one of claims 1-18, and a vehicle (200) as described in any one of claims 19-24, wherein, The charging device (100) is electrically connected to the vehicle (200); The vehicle (200) is used to send vehicle information to the charging device (100); The charging device (100) is used to acquire the vehicle information sent by the vehicle (200) and perform processing operations on the vehicle information.

26. The charging management system according to claim 25, characterized in that, The charging management system also includes: a cloud device (300), The cloud device (300) is used to receive vehicle information sent by the charging device (100), perform vehicle (200) diagnosis based on the vehicle information, and obtain vehicle (200) diagnosis results.

27. The charging management system according to claim 26, characterized in that, The cloud device (300) is also used to send the diagnostic results of the vehicle (200) to at least one of the vehicle (200), terminal device, and after-sales service terminal.

28. The charging management system according to claim 26, characterized in that, The cloud device (300) is also used to receive diagnostic requests from the vehicle (200) and send them to the charging device (100); The charging device (100) is used to receive diagnostic requests from the vehicle (200) and send them to the vehicle (200); The vehicle (200) is configured to receive a diagnostic request from the vehicle (200) and obtain vehicle information based on the diagnostic request.

Images