Charging vehicle electric energy consumption determination method, medium and electronic equipment

Abstract

The invention provides a charging vehicle electric energy consumption determination method, a medium and electronic equipment, and relates to the field of vehicle charging, and the method comprises the steps that a working charging vehicle executes a charging task at a first preset power; if the mobile terminal is disconnected with the cloud platform, reconnection request information is sent, and the power is adjusted to second preset power; if the reconnection is not successful, the connection module is controlled to be restarted; if the reconnection is successful in the first time window, continuing to execute the charging task at a first preset power until the charging is completed; sending a charging completion signal to the cloud platform; the cloud platform obtains the GYT; and generating the electric energy consumption of the working charging vehicle corresponding to the charging completion signal according to the GYT, the first preset power and the second preset power. According to the invention, on one hand, a certain reconnection time is reserved for the disconnected working charging vehicle, the failure rate of the order is reduced, on the other hand, the charging power is reduced in the period of waiting for reconnection, and even if the final charging fails, accurate billing can be realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of vehicle charging, in particular to a method for determining the electric energy consumption of a charging vehicle, a medium and an electronic device. BACKGROUND

[0002] In a vehicle charging system, after the cloud platform receives a charging order of a user, the corresponding charging task is sent to the corresponding charging vehicle. After the charging vehicle receives the corresponding charging task, due to unstable network or equipment damage, etc., the charging vehicle may be disconnected from the cloud platform. When the charging vehicle is disconnected from the cloud platform, the cloud platform directly ends the order. If the user wants to continue charging, the user needs to place an order again, which has a high order failure rate and poor user experience. Therefore, there is an urgent need for a method for reducing the order failure rate and realizing accurate charging. SUMMARY

[0003] To solve the above technical problems, the present application provides a method for determining the electric energy consumption of a charging vehicle, a medium and an electronic device, which at least partially solves the problems in the prior art.

[0004] In the first aspect of the present application, a method for determining the electric energy consumption of a charging vehicle is provided, which is applied to a vehicle charging system. The vehicle charging system includes a plurality of working charging vehicles performing charging tasks and a cloud platform. Each working charging vehicle sends connection confirmation information to the cloud platform every predetermined time interval. If the connection response information from the cloud platform is received, it is determined that the working charging vehicle is not disconnected. If the connection response information from the cloud platform is not received for a predetermined number of times in succession, it is determined that the working charging vehicle is disconnected from the cloud platform. The cloud platform is used to perform the following steps: S110, in response to receiving a charging task of a user, the charging task is assigned to the corresponding working charging vehicle according to a predetermined assignment rule; The working charging vehicle is used to perform the following steps: S210, in response to receiving the charging task assigned by the cloud platform, the corresponding charging task is performed at a first predetermined power. Each charging task includes a corresponding target electric quantity; S220, if disconnection from the cloud platform is detected during the execution of the charging task, a reconnection request information is sent to the cloud platform, and the working charging vehicle is adjusted to a second predetermined power to continue to perform the charging task within a first time window. The second predetermined power is less than the first predetermined power. The start time of the first time window is the time of disconnection from the cloud platform; S230, if no connection response information is received within a first response time period of the first time window, the connection module of the working charging vehicle is restarted. The connection module is used for communication with the cloud platform; S240, if the connection response information is received in a second response time period of the first time window, adjusting to the first preset power to continue to perform the charging task until a corresponding target electric quantity is reached; and sending a charging completion signal to the cloud platform; wherein a time length of the first response time period is less than a time length of the second response time period; and a time length of the first time window is equal to a sum of the time lengths of the first response time period and the second response time period. The cloud platform is further configured to perform the following steps: S120, in response to receiving the charging completion signal, obtaining a first working time set GYT=(GYT1, GYT2, GYT3, GYT4) corresponding to the charging completion signal; wherein GYT1 is a start time of the working charging vehicle performing the charging task at the first preset power corresponding to the charging completion signal; GYT2 is a time when the working charging vehicle corresponding to the charging completion signal is disconnected from the cloud platform; GYT3 is a time when the working charging vehicle corresponding to the charging completion signal receives the connection response information from the cloud platform; and GYT4 is a time when the working charging vehicle corresponding to the charging completion signal completes the charging task. S130, generating an electric energy consumption of the working charging vehicle corresponding to the charging completion signal according to the GYT, the first preset power and the second preset power.

[0005] In a second aspect of the present application, a non-transitory computer readable storage medium is provided, and the storage medium stores at least one instruction or at least one program. The at least one instruction or the at least one program is loaded and executed by a processor to implement the foregoing charging vehicle electric energy consumption determination method.

[0006] In a third aspect of the present application, an electronic device is provided, which includes a processor and the foregoing non-transitory computer readable storage medium.

[0007] The present application has at least the following beneficial effects: The charging car electric energy consumption determination method provided in the application, when the working charging car is disconnected from the cloud platform, preferentially uses a small cycle with shorter use time but relatively lower success rate to attempt to reconnect with the cloud platform (the Tbox module directly sends a reconnection request information to the cloud platform) in a first time window, and if the small cycle fails, a large cycle with longer use time but relatively higher success rate is used (the Tbox module is restarted) to reconnect with the cloud platform. Through the reasonable design of the sequence of the large cycle and the small cycle, the reconnection time is saved, and the success rate of reconnection is ensured. And at the time of disconnection, the corresponding charging power is adjusted from a first preset power to a lower second preset power, because in the related art, the cloud platform charges the working charging car according to the charging time and the charging power, and after the working charging car is disconnected from the cloud platform, the cloud platform stops timing the charging time, and the IBM module immediately stops charging, that is, the order is terminated, and if the user wants to continue charging, the user needs to place a new order to the cloud platform. In the application, in order to reduce the failure rate of the order, after the working charging car detects that it is disconnected from the cloud platform, the IBM module adjusts the charging power to a lower second preset power, and continues to perform the charging task in a set first time window. After disconnection, the fixed low-power charging is used, because compared with the high-power continuous charging, if the reconnection fails or the timing fails, a high-power charging time that cannot be charged will be formed, causing a loss, and the low-power continuous charging is used to wait for reconnection, reducing the loss caused to the corresponding merchant of the cloud platform due to the reconnection failure or the charging failure, and further, the fixed low-power charging time is set, in order to ensure accurate charging even if the final reconnection fails. The application attempts to reconnect while setting low-power charging after the charging car is disconnected from the cloud platform, and sets a fixed low-power charging time. On the one hand, a certain reconnection time is reserved for the disconnected working charging car, reducing the failure rate of the order, and on the other hand, the charging power is reduced during the waiting period for reconnection, so that accurate charging can be realized even if the charging fails finally. BRIEF DESCRIPTION OF DRAWINGS

[0008] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without any creative effort based on these drawings.

[0009] Fig. 1 The cloud platform execution step flow chart in one embodiment of the charging car electric energy consumption determination method provided by the application; Fig. 2 The working charging car execution step flow chart in one embodiment of the charging car electric energy consumption determination method provided by the application; Fig. 3Another embodiment of the cloud platform execution step flow chart of the charging vehicle electric energy consumption determination method provided in the embodiments of the present application is shown in the figure. DETAILED DESCRIPTION

[0010] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0011] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or server including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0012] It should be noted that various aspects of the embodiments described below are within the scope of the appended claims. It should be apparent that the aspects described herein can be embodied in a wide variety of forms and that any specific structure and / or function described herein is merely illustrative. Based on the present application, those skilled in the art should appreciate that one aspect described herein can be implemented independently of any other aspect and that two or more of these aspects can be combined in various ways. For example, an apparatus can be implemented and / or a method can be practiced using any number of the aspects set forth herein. In addition, such an apparatus can be implemented and / or such a method can be practiced using other structure and / or functionality in addition to or other than one or more of the aspects set forth herein.

[0013] Referring to Figs. 1-3 As shown in the figure, the embodiments of the present application provide a charging vehicle electric energy consumption determination method, applied to a vehicle charging system, the vehicle charging system comprising a plurality of working charging vehicles performing charging tasks and a cloud platform; each working charging vehicle sends connection confirmation information to the cloud platform every interval of a preset time period, if connection response information from the cloud platform is received, it is determined that the working charging vehicle is not disconnected; if connection response information from the cloud platform is not received for a preset number of times in succession, it is determined that the working charging vehicle is disconnected from the cloud platform.

[0014] Here, the cloud platform communicates with each working charging vehicle that is performing a charging task, and the working charging vehicle includes a Tbox module and an IBM module. The Tbox is an important component in a telematics system, and its full name is Telematics Box. It integrates remote communication and information science technology and is used to communicate with the cloud platform. The IBM module is used to control the start and stop of the working charging vehicle to perform a charging task and control the charging power. After the working charging vehicle is powered on, the Tbox module establishes communication with the cloud platform, and at the same time, stores the unique identifier of the working charging vehicle sent by the IBM module; the IBM module starts charging at a first preset power according to the charging task of the user issued by the cloud platform. The Tbox module sends a connection confirmation information to the cloud platform every interval preset time period, for example, the preset time period is 3 seconds, and the connection confirmation information is a heartbeat packet. After receiving the connection confirmation information sent by any working charging vehicle, the cloud platform returns corresponding connection response information, so as to determine that the cloud platform and the working charging vehicle are normally connected. If a working charging vehicle does not receive the connection response information of the cloud platform for a continuous preset number of times, it is determined that the working charging vehicle and the cloud platform are disconnected. If the cloud platform does not receive the connection confirmation information of the working charging vehicle within a preset connection time, it is determined that the working charging vehicle is disconnected.

[0015] The cloud platform is used to perform the following steps: S110, in response to receiving a charging task of a user, the charging task is issued to a corresponding working charging vehicle according to a preset allocation rule.

[0016] Specifically, the cloud platform receives a charging task of a user, and allocates the charging task according to the current working condition and the remaining power of each charging working vehicle. The preset allocation rule here can be to preferentially allocate the charging task to an idle working charging vehicle with high remaining power.

[0017] The working charging vehicle is used to perform the following steps: S210, in response to receiving a charging task issued by the cloud platform, a corresponding charging task is performed at a first preset power; each charging task includes a corresponding target power.

[0018] Specifically, each charging task includes a corresponding target power, for example, the target power can be 100% or 80%.

[0019] S220, if disconnection with the cloud platform is detected during the execution of the charging task, a reconnection request information is sent to the cloud platform, and adjusted to a second preset power to continue to execute the charging task within a first time window; the second preset power is less than the first preset power; the start time of the first time window is the time of disconnection with the cloud platform.

[0020] Specifically, if disconnection with the cloud platform is detected during the execution of the charging task, i.e., connection response information from the cloud platform is not received for a preset number of times in succession, the Tbox module of the working charging vehicle sends reconnection request information to the cloud platform, where the reconnection request information includes a unique identifier of the working charging vehicle.

[0021] On the other hand, the charging power of the working charging vehicle is adjusted from the first preset power to the second preset power when disconnection with the cloud platform is detected, because in the related art, the cloud platform charges the working charging vehicle according to the charging time and the charging power, and after the working charging vehicle is disconnected from the cloud platform, the cloud platform stops timing the charging time, and the IBM module immediately stops charging, i.e., the order is terminated, and if the customer wants to continue the order, the customer needs to place a new order with the cloud platform. In this application, after the working charging vehicle detects disconnection with the cloud platform, the IBM module adjusts the charging power to a lower second preset power and executes within a set first time window. After disconnection, charging at a fixed low power is used because, compared to continuing charging at a high power, if reconnection fails or timing fails, a period of high-power charging time that cannot be charged will be formed, resulting in a loss. Continuing charging at a low power to wait for reconnection reduces the loss caused to the corresponding merchant of the cloud platform due to reconnection failure or charging failure, and further, a fixed low-power charging time is set to ensure accurate charging even if reconnection ultimately fails.

[0022] S230, if connection response information is not received within the first response time period of the first time window, the connection module of the working charging vehicle is restarted; the connection module is used for communication with the cloud platform.

[0023] Specifically, if connection response information is not received within the first response time period of the first time window, i.e., reconnection with the cloud platform is not successful within the first response time period of the first time window, the connection module of the working charging vehicle is restarted, i.e., the Tbox module is restarted. Here, the time for the Tbox module to directly send reconnection request information to the cloud platform is less than the time for the Tbox module to restart, and the success rate of the Tbox module directly sending reconnection request information to the cloud platform is less than the success rate of the Tbox module restarting, so this application preferentially uses the small cycle (the Tbox module directly sends reconnection request information to the cloud platform) with shorter time, and if the small cycle fails, the large cycle (the Tbox module is restarted) is used to reconnect with the cloud platform. Through the reasonable design of the sequence of the large cycle and the small cycle, the reconnection time is saved while the success rate of reconnection is guaranteed.

[0024] S240, if the connection response information is received in the second response time period of the first time window, adjusting to the first preset power to continue the charging task until the corresponding target power is reached; and sending a charging completion signal to the cloud platform; wherein the time length of the first response time period is less than the time length of the second response time period; and the time length of the first time window is equal to the time length of the first response time period and the second response time period.

[0025] Specifically, if the connection response information is received in the second response time period of the first time window, i.e. the large cycle reconnection is successful, the charging power is adjusted to the first preset power to execute the charging task until the corresponding target power is reached. And send a charging completion signal to the cloud platform after charging is completed. As an example: the first time window can be 90 seconds.

[0026] The cloud platform is also used to execute the following steps: S120, in response to receiving the charging completion signal, obtaining the first working time set GYT=(GYT1, GYT2, GYT3, GYT4) corresponding to the charging completion signal; wherein GYT1 is the start time of the working charging car corresponding to the charging completion signal to execute the charging task with the first preset power; GYT2 is the disconnection time of the working charging car corresponding to the charging completion signal and the cloud platform; GYT3 is the time when the working charging car corresponding to the charging completion signal receives the connection response information of the cloud platform; GYT4 is the time when the working charging car corresponding to the charging completion signal completes the charging task.

[0027] S130, generating the electric energy consumption of the working charging car corresponding to the charging completion signal according to GYT, the first preset power and the second preset power.

[0028] Specifically, the cloud platform obtains the corresponding start time, disconnection time, reconnection time and end time, and obtains the actual charging time with the first preset power and the actual charging time with the second preset power according to GYT. And calculate the final electric energy consumption to obtain the corresponding charging fee.

[0029] In the embodiment, when the working charging vehicle is disconnected from the cloud platform, a small cycle with a relatively short time but a relatively low success rate is used to reconnect with the cloud platform (the Tbox module directly sends a reconnection request to the cloud platform) in a first time window. If the small cycle fails, a large cycle with a relatively long time but a relatively high success rate is used to reconnect with the cloud platform (the Tbox module is restarted). Through the reasonable design of the sequence of the large cycle and the small cycle, the reconnection time is saved, and the success rate of reconnection is ensured. At the same time of disconnection, the corresponding charging power is adjusted from a first preset power to a second preset power, because in the related art, the cloud platform charges the working charging vehicle according to the charging time and the charging power. After the working charging vehicle is disconnected from the cloud platform, the cloud platform stops timing the charging time, and the IBM module immediately stops charging, that is, the order is terminated. If the user wants to continue charging, the user needs to place a new order with the cloud platform. In the embodiment, in order to reduce the failure rate of the order, after the working charging vehicle detects disconnection from the cloud platform, the IBM module adjusts the charging power to the second preset power, and continues to perform the charging task in the set first time window. After disconnection, the fixed low power charging is used, because compared with the high power charging, if the reconnection fails or the timing fails, a high power charging time that cannot be charged will be formed, resulting in a loss. The low power charging is used to wait for reconnection, which reduces the loss caused to the corresponding merchant of the cloud platform due to the reconnection failure or the charging failure. Further, the fixed low power charging time is set, so that even if the reconnection fails finally, accurate charging can be ensured. In the embodiment, after the charging vehicle is disconnected from the cloud platform, the low power charging is set while the reconnection is attempted, and the fixed low power charging time is set. On the one hand, the working charging vehicle that is disconnected is reserved a certain reconnection time, and the failure rate of the order is reduced. On the other hand, the charging power is reduced during the waiting period for reconnection, so that even if the charging fails finally, accurate charging can be realized.

[0030] In an exemplary embodiment of the present application, after step S230, the working charging vehicle is further configured to perform the following steps: S250, if the connection response information of the cloud platform is not received in the first time window, stop performing the charging task; and determine the first time window as a low power time window.

[0031] Specifically, if the connection response information of the cloud platform is not received in the first time window, the IBM module controls the working charging vehicle to stop charging at the end of the first time window.

[0032] The cloud platform is further configured to perform the following steps: S140, obtaining a second working time set GET=(GYT1, GYT2).

[0033] S150, generating the power consumption of the working charging vehicle according to the GET, the length of the low-power time window, the first preset power and the second preset power.

[0034] Specifically, in the embodiment, (GYT2-GYT1) is the charging duration corresponding to the first preset power; the length of the first time window is the charging duration corresponding to the second preset power; the power consumption is calculated according to the charging duration corresponding to the first preset power, the charging duration corresponding to the second preset power, the first preset power and the second preset power, and then the corresponding charging fee is obtained.

[0035] In an exemplary embodiment of the present application, if there is at least one key charging vehicle performing a charging task in a range with the working charging vehicle as the center and a distance corresponding to a preset near-field communication protocol as the radius, the working charging vehicle is further used to perform the following steps after step S220: S260, obtaining a key time interval list set GT=(GT1, GT2, …, GTn) according to the preset near-field communication protocol; i=1, 2, …, n; wherein n is the number of key charging vehicles; GTi is the key time interval list of the ith key charging vehicle; GTi=(GTi,1, GTi,2, …, GTi,f(i)); j=1, 2, …, f(i); f(i) is the number of times that the ith key charging vehicle receives connection response information in the third time window; GTi,j is the time interval between the sending time of the connection response information and the corresponding connection confirmation information received by the ith key charging vehicle for the jth time in the third time window segment; the end time of the third time window is the start time of the first time window. i n i i i1 i2 ij if（i） ij

[0036] Specifically, the near-field communication mode in the preset near-field communication protocol can be Bluetooth, NFC, RFID, etc. In the embodiment, the distance between each key charging vehicle and the working charging vehicle is less than the distance corresponding to the preset near-field communication protocol, i.e., the working charging vehicle can communicate with each key charging vehicle using the preset near-field communication protocol.

[0037] ​​​​​​​​​Here, the time interval list of each key charging vehicle in a period of time before the disconnection time of the working charging vehicle (in the third time window) is obtained, where each time interval represents the time interval between the receiving time of the corresponding connection response information and the sending time of the corresponding connection confirmation information. The time interval between any two adjacent connection confirmation information is fixed, but due to network fluctuations and other conditions, the receiving time of the corresponding connection response information can be different.

[0038] S270, obtaining a set of key time fluctuation values GTB=(GTB1, GTB2, …, GTBn) according to GT; wherein GTBi is the time fluctuation value corresponding to the i-th key charging vehicle; GTBi=(∑i=1n(GTi-avg(GT1))) / f(i); avg() is a preset average value determination function. i , …, GTB n ); wherein GTBi is the time fluctuation value corresponding to the i-th key charging vehicle; GTBi=(∑i=1n(GTi-avg(GT1))) / f(i); avg() is a preset average value determination function. i i f（i） j=1 ij i 2

[0039] Specifically, the fluctuation value corresponding to the time interval list of each key charging vehicle in the third time window is obtained. The larger the fluctuation value, the greater the difference between the connection response information and the corresponding connection confirmation information corresponding to the key charging vehicle, that is, the key charging vehicle is unstable when connecting with the cloud platform in the third time window, and the network fluctuation is large, that is, the network connection can not be stable. Conversely, if the fluctuation value is smaller, it means that the time interval between each corresponding connection response information and the corresponding connection confirmation information of the key charging vehicle has a small difference, and the overall is stable. The smaller the fluctuation, the smaller the network fluctuation in this period of time (in the third time window), that is, the network connection is more stable.

[0040] S280, if (a / n)≥n0, and no connection response information is received in the first time window, then continue to perform the charging task in the second time window with the second preset power after the end of the first time window; wherein a is the number of time fluctuation values in GTB greater than the preset time fluctuation value threshold; n0 is a preset fluctuation value ratio; the start time of the second time window is the end time of the first time window.

[0041] S290, if the connection response information is received in the second time window, adjust to the first preset power to continue to perform the charging task until the target power is reached; and send a charging completion signal to the above-mentioned cloud platform.

[0042] The above-mentioned cloud platform is also used to perform the following steps: S160, jump to step S120.​​​​​​

[0043] Specifically, (a / n)≥n0, which means that most of the key charging vehicles are likely to have large network fluctuations in the third time window, i.e., the network connection in the third time window is likely to be less stable, so it may cause some working charging vehicles to be disconnected. Therefore, in order to further reduce the failure probability of the order, for the working charging vehicle that has not been connected successfully after the end of the first time window, the second preset power is used to continue to perform the charging task in the second time window. That is, the reconnection waiting time is prolonged, and the failure probability of the order is further reduced, and the length of the second time window is also pre-set. It is convenient for the cloud to charge.

[0044] In an exemplary embodiment of the present application, after step S280, the working charging vehicle is further configured to perform the following steps: S2100, if no connection response information is received in the second time window, stop performing the charging task, and determine the first time window and the second time window as the low-power time window.

[0045] Specifically, if no connection response information of the cloud platform is received in the second time window, it means that the reconnection fails in the second time window. At this time, the IBM module controls the working charging vehicle to stop charging at the end of the second time window.

[0046] S2110, broadcast the delay stop information and the corresponding sending request according to the pre-set short-distance communication protocol; the delay stop information includes the unique identifier of the working charging vehicle.

[0047] Specifically, at this time, since the actual low-power charging time of the working charging vehicle is the length of the first time window and the second time window, and since the working charging vehicle is disconnected from the cloud platform, the cloud platform cannot know the actual low-power charging time of the working charging vehicle. Therefore, the working charging vehicle broadcasts the delay stop information and the corresponding sending request according to the pre-set short-distance communication protocol, and the delay stop information includes the unique identifier of the working charging vehicle.

[0048] The key charging vehicle is further configured to perform the following steps: S310, in response to receiving any delay stop information and corresponding sending request, and not being disconnected from the cloud platform, the delay stop information is sent to the cloud platform.

[0049] Specifically, any key charging vehicle that is not disconnected from the cloud platform receives the delay stop information and the corresponding sending request, and then sends the delay stop information to the cloud platform.

[0050] The cloud platform is further configured to perform the following steps: S170, jump to step S140.

[0051] Specifically, after receiving the delay stop information, the cloud platform calculates the corresponding power consumption according to the unique identifier and the corresponding start time and disconnection time, and further charges.

[0052] In this embodiment, for the working charging vehicle whose reconnection time is extended and still fails to reconnect successfully, in order for the cloud platform to realize accurate charging, the cloud platform broadcasts the delay stop information and the corresponding sending request through the preset proximity communication protocol without network, and when any key charging vehicle that has not disconnected with the cloud platform receives the delay stop information, the cloud platform sends the delay stop information to the cloud platform. Since the delay stop information includes the unique identifier corresponding to the working charging vehicle, the cloud platform can obtain the low-power charging duration (the length of the first time window and the second time window) according to the delay stop information after receiving the delay stop information, and can determine the corresponding working charging vehicle according to the unique identifier to realize accurate charging.

[0053] In an example embodiment of the present application, after step S270, the working charging vehicle is further configured to perform the following steps: S2120, if (a / n) < n0 and no connection response information of the cloud platform is received within the first time window, stop performing the charging task; and determine the first time window as the low-power time window.

[0054] The cloud platform is further configured to perform the following steps: S180, jump to step S140.

[0055] Specifically, if (a / n) < n0, it indicates that most of the key charging vehicles may have small network fluctuations within the third time window, that is, the network connection within the third time window may be stable, so the disconnection reason of the disconnected working charging vehicle may not be network. At this time, if the working charging vehicle does not receive the connection response information of the cloud platform within the first time window, the charging task is stopped, that is, the low-power charging time is not extended.

[0056] In an example embodiment of the present application, after step S110, the cloud platform is further configured to perform the following steps: S190, in response to detecting that any working charging vehicle is disconnected, obtaining a first time interval list set NT=(NT1, NT2, …, NT g , …, NT h ); g=1, 2, …, h; h is the number of working charging vehicles that have not disconnected; NT g is the first time interval list of the gth working charging vehicle that has not disconnected; NT g =(NT g1 , NT g2 , …, NT gk , …, NTgf(g) ); k = 1, 2, …, f(g); f(g) is the number of times that the gth working charging vehicle which is not disconnected receives the connection response information in the first time window; NT gk is the first time interval between the time when the gth working charging vehicle which is not disconnected receives the connection response information and the time when the corresponding connection confirmation information is sent in the first time window; the working charging vehicle which is disconnected reconnects with the cloud platform in the first time window; Specifically, when the cloud platform detects that any working charging vehicle is disconnected, a first time interval list set NT is obtained, where each first time interval of each working charging vehicle which is not disconnected with the cloud platform in the first time window is included. Each first time interval represents the time interval between the time when the corresponding connection response information is received and the time when the corresponding connection confirmation information is sent. The time interval between any two adjacent connection confirmation information is fixed, but due to network fluctuations and other conditions, the time when the corresponding connection response information is received can be different.

[0057] S1100, if NT is not empty and the working charging vehicle which is disconnected is not successfully reconnected in the first time window, then according to NT, a first time fluctuation value set NTB = (NTB1, NTB2, …, NTB g , …, NTB h ) is obtained. g is the gth corresponding first time fluctuation value of the working charging vehicle which is not disconnected in the first time window; NTB g = (∑ f（g） k=1 (NT gk - avg(NT g )) 2 ) / f(g).

[0058] Specifically, if NT is not empty, it means that there is a working charging vehicle which is not disconnected with the cloud platform, and the working charging vehicle which is disconnected is not successfully reconnected in the first time window. At this time, the corresponding first time fluctuation value of each working charging vehicle is obtained. The greater the fluctuation value, the greater the difference between the corresponding connection response information and the corresponding connection confirmation information of the working charging vehicle, i.e., the connection of the working charging vehicle with the cloud platform in the first time window is less stable, which may be due to the larger network fluctuation, i.e., the network connection may not be stable. Conversely, the smaller the fluctuation value, the smaller the difference between each corresponding connection response information and the corresponding connection confirmation information of the working charging vehicle, which is more stable as a whole. The smaller the fluctuation, the smaller the network fluctuation in this period (in the first time window), i.e., the network connection is more stable.

[0059] S1200, if (b / h)≥n0, a broadcast task of sending a reconnection time extension instruction to the h unbroken working charging vehicles is performed; b is the number of the first time fluctuation values greater than the preset time fluctuation value threshold in the NTB; n0 is a preset fluctuation value ratio.

[0060] Specifically, if (b / h)≥n0, it indicates that most working charging vehicles may have a large network fluctuation in the first time window, i.e., the network connection in the first time window may be less stable, so that it may cause part of the working charging vehicles to fail to reconnect successfully in the first time window. Therefore, in order to further reduce the failure probability of the order, the working charging vehicles that have not connected successfully after the end of the first time window continue to perform the charging task in the second time window at a second preset power. That is, the reconnection waiting time is extended, the failure probability of the order is further reduced, and the length of the second time window is also preset. It is convenient for the cloud to perform billing. Since the working charging vehicle cannot receive the instruction of the cloud platform after being disconnected from the cloud platform, and the extension time set by the charging vehicle itself is the first time window, the broadcast task of sending the reconnection time extension instruction to each unbroken working charging vehicle is performed. That is, each unbroken working charging vehicle broadcasts the reconnection time extension instruction.

[0061] The unbroken working charging vehicle is used to perform the following steps: S310, in response to receiving the broadcast task of the reconnection time extension instruction, the above-mentioned reconnection time extension instruction is broadcasted according to a preset short-distance communication protocol.

[0062] Specifically, since the working charging vehicle disconnected from the cloud platform cannot receive the reconnection time extension instruction of the cloud platform, each unbroken working charging vehicle broadcasts the reconnection time extension instruction. Here, each unbroken working charging vehicle broadcasts the above-mentioned reconnection time extension instruction according to a preset short-distance communication protocol.

[0063] The working charging vehicle that is disconnected and has not successfully reconnected in the first time window is used to perform the following steps: S410, in response to receiving any reconnection time extension instruction broadcasted according to a preset short-distance communication protocol, the charging task is continued to be performed in the second time window at a second preset power; the start time of the second time window is the end time of the first time window; the above-mentioned second preset power is less than the first preset power; the working charging vehicle performs the charging task according to the first preset power when it is not disconnected; the above-mentioned first preset power is adjusted to the second preset power after the working charging vehicle is disconnected; each charging task has a corresponding target power.

[0064] Specifically, any working charging vehicle is not disconnected, using the first preset power to perform the charging task, and after disconnection, it attempts to reconnect with the cloud platform (to perform the charging task at the second preset power) within the first time window through the above steps S220-S230, and if it fails to reconnect within the first time window and receives any reconnection time extension instruction broadcast according to the preset short-distance communication protocol, it continues to perform the above charging task at the second preset power within the second time window. That is, the reconnection time is extended.

[0065] S420, if the connection response information is received within the second time window, the first preset power is adjusted to continue to perform the charging task until the target power is reached.

[0066] Specifically, if the connection response information is received within the second time window, i.e. the reconnection with the cloud platform is successful within the second time window, the first preset power is adjusted to continue to perform the charging task until the target power is reached.

[0067] In the embodiment, when the cloud platform detects that any working charging vehicle is disconnected, and is not successfully reconnected within the first time window, according to the fluctuation of each time interval between the connection response information and the corresponding connection confirmation information of each disconnected working charging vehicle, the greater the fluctuation value, the greater the difference between the connection response information and the corresponding connection confirmation information of the working charging vehicle, that is, the connection between the working charging vehicle and the cloud platform within the first time window is less stable, which may be due to the greater network fluctuation, that is, the network connection may not be stable. On the contrary, the smaller the fluctuation value, the smaller the difference between each corresponding connection response information and the corresponding connection confirmation information of the working charging vehicle, and the more stable the whole, the smaller the fluctuation, the smaller the network fluctuation within this period (within the first time window), that is, the more stable the network connection. Further, if (b / h)≥n0, it indicates that most of the working charging vehicles may have greater network fluctuation within the first time window, that is, the network connection within the first time window may be less stable, so it may cause some charging vehicles to be disconnected and still not successfully reconnected within the first time window. Therefore, in order to further reduce the failure probability of the order, the working charging vehicles that are still not connected successfully after the first time window ends continue to perform the charging task at a second preset power within a second time window. That is, the reconnection waiting time is extended, the failure probability of the order is further reduced, and the length of the second time window is also pre-set. It is convenient for the cloud platform to charge. Since the working charging vehicle cannot receive the instruction of the cloud platform after being disconnected from the cloud platform, and the extension time set by the charging vehicle itself is the first time window, a broadcast task of sending a reconnection time extension instruction to each disconnected working charging vehicle is performed. That is, each disconnected working charging vehicle broadcasts the reconnection time extension instruction. If the working charging vehicle is not successfully reconnected within the first time window and receives any reconnection time extension instruction broadcast according to the pre-set short-distance communication protocol, it continues to perform the above charging task at a second preset power within a second time window, that is, the reconnection time is extended. Finally, if the connection response information is received within the second time window, that is, the working charging vehicle is successfully reconnected with the cloud platform within the second time window, the charging task is continued at the first preset power until the target power is reached. In the embodiment, the cloud platform obtains the time interval fluctuation of each disconnected working charging vehicle within the first time window, thereby knowing the network fluctuation within the first time window and obtaining the network stability within the first time window. Further, if the network stability is low, it is considered that the disconnected working charging vehicle may not be successfully reconnected within the first time window due to network fluctuation. Therefore, the reconnection time of the disconnected working charging vehicle is extended. In this way, by setting reasonable reference factors, the order failure rate is further reduced, and the user experience is improved.

[0068] In an exemplary embodiment of the present application, after step S190, the cloud platform is further configured to perform the following steps: S1210, if the NT is empty and any working charging vehicle is detected to reconnect successfully within the preset response time period, a broadcast task of sending a power adjustment instruction to each working charging vehicle that reconnects successfully within the preset response time period is performed.

[0069] Specifically, if the NT is empty, i.e., at the current time, all working charging vehicles are disconnected from the cloud platform, if all working charging vehicles are disconnected from the cloud platform, it is possible that it is caused by transient or phase network instability, at this time, it is highly probable that each working charging vehicle can reconnect successfully, so it can continue to charge at the first preset power, but according to the preset power setting, each working charging vehicle disconnected from the cloud platform is adjusted to the second preset power for charging after disconnection. Therefore, if any working charging vehicle is detected to reconnect successfully within the preset response time period, the time length of the preset response time period is less than the time length of the first time window, a broadcast task of sending a power adjustment instruction to each working charging vehicle that reconnects successfully within the preset response time period is performed.

[0070] The working charging vehicle that reconnects successfully within the preset response time period is used to perform the following steps: S510, in response to receiving the broadcast task of sending the power adjustment instruction, the power adjustment instruction is broadcasted according to the preset short-distance communication protocol.

[0071] Specifically, the working charging vehicle that reconnects successfully within the preset response time period receives the broadcast task of sending the power adjustment instruction, and the power adjustment instruction is broadcasted according to the preset short-distance communication protocol.

[0072] The working charging vehicle that does not reconnect successfully within the preset response time period is used to perform the following steps: S610, according to the preset reconnection method, the working charging vehicle is reconnected with the cloud platform within the first time window.

[0073] Specifically, step S610 includes: S611, a reconnection request information is sent to the cloud platform, and the charging task is continued to be performed at the second preset power within the first time window.

[0074] S612, if a connection response information is not received within the first response time period of the first time window, a corresponding connection module is restarted; the connection module is used for communication with the cloud platform.

[0075] Here, steps S611-S612 are the same as steps S220-S230 described above, which will not be described here.

[0076] S620, in response to not receiving the connection response information of the cloud platform and receiving any power adjustment instruction broadcast according to the preset short-distance communication protocol within the first time window, adjusting the second preset power to the first preset power and continuing to perform the corresponding charging task until the first time window ends; the preset response time period has a time length less than that of the first time window, and a start time of the preset response time period is equal to a start time of the first time window.

[0077] Specifically, if the connection response information of the cloud platform is not received and any power adjustment instruction broadcast according to the preset short-distance communication protocol is received within the first time window, the second preset power is adjusted to the first preset power, and the corresponding charging task is continued to be performed until the first time window ends.

[0078] S630, if the connection response information of the cloud platform is received within the first time window except for the preset response time period, the charging task is continued to be performed at the first preset power until the target power is reached; and a charging completion signal is sent to the cloud platform.

[0079] Specifically, if the connection response information of the cloud platform is received within the first time window except for the preset response time period, that is, the reconnection is successful, the charging task is continued to be performed at the first preset power until the target power is reached; and a charging completion signal is sent to the cloud platform.

[0080] In the embodiment, if the NT is empty, i.e., at the current time, all working charging vehicles are disconnected from the cloud platform. If all working charging vehicles are disconnected from the cloud platform, it is possible that it is caused by transient or periodic network instability. At this time, it is highly probable that each working charging vehicle can successfully reconnect. Therefore, it can continue to charge at the first preset power. However, according to the preset power setting, each working charging vehicle disconnected from the cloud platform adjusts to the second preset power for charging after disconnection. Therefore, if it is detected that any working charging vehicle successfully reconnects within the preset response time period, and the time length of the preset response time period is less than the time length of the first time window, a broadcast task of sending a power adjustment instruction to each working charging vehicle that successfully reconnects within the preset response time period is performed. Each working charging vehicle that successfully reconnects within the preset response time period broadcasts the power adjustment instruction. If a working charging vehicle that does not successfully reconnect within the preset response time period receives any power adjustment instruction broadcast according to the preset short-distance communication protocol within the first time window, the second preset power is adjusted to the first preset power, and the corresponding charging task is continuously performed until the first time window ends. If the connection response information of the cloud platform is received within the first time window except for the preset response time period, i.e., it is successfully reconnected, the charging task is continuously performed at the first preset power until the target power is reached. In the embodiment, all working charging vehicles are disconnected from the cloud platform. It is possible that it is caused by transient or periodic network instability. At this time, it is highly probable that each working charging vehicle can successfully reconnect. However, according to the preset power adjustment rule, each working charging vehicle charges at a lower second preset power within the first time window after disconnection and waits for reconnection. In the embodiment, it is highly probable that each working charging vehicle can successfully reconnect. In order to avoid slow charging speed, the charging power of all charging vehicles can be adjusted to the first preset power within the first time window. Therefore, the working charging vehicle that successfully reconnects within the preset response time period broadcasts the power adjustment instruction, so that each working charging vehicle that does not successfully reconnect within the preset response time period also adjusts to the first preset power for charging within the first time window according to the power adjustment instruction. Compared with continuously charging at the second preset power within the first time window, the charging time can be reduced. Compared with the related art in which disconnection directly closes the order, the embodiment reduces the probability of abnormal failure of the order due to the setting of the delayed reconnection time.

[0081] In an exemplary embodiment of the present application, after step S410, the working charging vehicle that is disconnected and does not successfully reconnect within the first time window is used to perform the following steps: S430, if the connection response information is not received within the second time window, the working charging vehicle stops performing the charging task.

[0082] Specifically, if the connection response information is not received in the second time window, i.e., the reconnection fails, the working charging vehicle stops performing the charging task.

[0083] In an example embodiment of the present application, after step S620, the working charging vehicle that fails to reconnect within the preset response time period is further configured to perform the following steps: S640, broadcast the power adjustment information and the corresponding sending request according to a preset proximity communication protocol; wherein the power adjustment information comprises a power adjustment time and a corresponding unique identifier.

[0084] Specifically, in order to facilitate the cloud to accurately obtain the power consumption of the working charging vehicle, the power adjustment information and the corresponding sending request are broadcasted according to the preset proximity communication protocol.

[0085] The working charging vehicle that reconnects successfully within the preset response time period is further configured to perform the following steps: S520, in response to receiving any power adjustment information and corresponding sending request, send the power adjustment information and the corresponding sending request to the cloud platform.

[0086] Specifically, if any power adjustment information and corresponding sending request is received, the power adjustment information and the corresponding sending request are sent to the cloud platform, so that the cloud platform can obtain the charging time of the working charging vehicle that fails to reconnect within the preset response time period (the difference between the time length of the first preset power charging time and the time length of the preset response time period, and the charging time before disconnection) and the charging time of the working charging vehicle that reconnects successfully within the preset response time period (the time length of the preset response time period), and further determine the power consumption of the working charging vehicle that fails to reconnect within the preset response time period.

[0087] In an example embodiment of the present application, after step S190, the cloud platform is further configured to perform the following steps: S1220, if NT is empty, obtain the current power of each disconnected working charging vehicle at the disconnection time to obtain a current power set CD=(CD1, CD2, …, CD r , …, CD s ); r=1, 2, …, s; s is the number of working charging vehicles disconnected from the cloud platform; CDr is the current power of the rth working charging vehicle disconnected from the cloud platform; each charging task has a corresponding target power; the disconnected working charging vehicle reconnects with the cloud platform within the first time window.

[0088] Specifically, the specific method of the disconnected working charging vehicle reconnecting with the cloud platform within the first time window in the present embodiment is the same as the above steps, which will not be described here.

[0089] S1230, if CD r CDY; and if the working charging vehicle corresponding to CDr is detected to reconnect successfully within a preset response time period, the working charging vehicle corresponding to CDr is determined as a first type of working charging vehicle; CDY is a preset power threshold; if CD r CDY; and if the working charging vehicle corresponding to CDr is not detected to reconnect successfully within a preset response time period, the working charging vehicle corresponding to CDr is determined as a second type of working charging vehicle. S1240, sending a broadcast task of a power adjustment instruction to the first type of working charging vehicle; wherein the working charging vehicle performs a charging task according to a first preset power when the working charging vehicle is not disconnected; the first preset power is adjusted to a second preset power when the working charging vehicle is disconnected; the first preset power is greater than the second preset power. The first type of working charging vehicle is configured to perform the following steps: S710, in response to receiving the broadcast task of the power adjustment instruction, broadcasting the power adjustment instruction according to a preset proximity communication protocol. The second type of working charging vehicle is configured to perform the following steps: S810, reconnecting with the cloud platform within a first time window according to a preset reconnection method. S820, in response to not receiving a connection response information of the cloud platform and receiving any power adjustment instruction broadcasted according to the preset proximity communication protocol within the first time window, adjusting the second preset power to the first preset power and continuing to perform the charging task until the first time window ends; a time length of the preset response time period is less than a time length of the first time window, and a start time of the preset response time period is equal to a start time of the first time window. S830, if the connection response information of the cloud platform is received within a time after the power adjustment within the first time window, the charging task is continued to be performed at the first preset power until a target power is reached; and a charging completion signal is sent to the cloud platform.

[0090] In the embodiment, if NT is empty, it indicates that the cloud platform is connected to each working charging vehicle which is disconnected. First, the power of each working charging vehicle at the disconnection time is obtained. If the power is greater than a preset power threshold, it indicates that the current power is close to the target power. Otherwise, if the power is less than the preset power threshold, it indicates that the current power is not close to the target power. If the cloud platform is disconnected at this time, the user is likely to need to continue charging.

[0091] When all the working charging vehicles are disconnected from the cloud platform, it is possible that the disconnection is caused by transient or periodic network instability, and in this case, each working charging vehicle can reconnect successfully with high probability. Therefore, the working charging vehicle can continue to charge at the first preset power, but according to the preset power setting, each working charging vehicle disconnected from the cloud platform adjusts to the second preset power for charging after disconnection. Therefore, if a working charging vehicle with an amount of electricity less than the preset amount of electricity threshold reconnects successfully (a first type of working charging vehicle) within a preset response time period, a broadcast task of sending a power adjustment instruction to the first type of working charging vehicle is sent. The first type of working charging vehicle broadcasts the power adjustment instruction. Here, the length of the preset response time period is less than the length of the first time window. If a working charging vehicle (a second type of working charging vehicle) that has not successfully reconnected within the preset response time period and has an amount of electricity less than the preset amount of electricity threshold receives any power adjustment instruction broadcast according to the preset short-distance communication protocol within the first time window, the second preset power is adjusted to the first preset power, and the charging task continues to be performed until the end of the first time window; if the connection response information from the cloud platform is received within the time after the power adjustment within the first time window, i.e., the reconnection is successful, the charging task continues to be performed at the first preset power until the target amount of electricity is reached. In this embodiment, all working charging vehicles are disconnected from the cloud platform, which may be caused by transient or periodic network instability, and in this case, each working charging vehicle can reconnect successfully with high probability, but according to the preset power adjustment rule, each working charging vehicle charges at a lower second preset power within the first time window after disconnection and waits for reconnection. In this embodiment, in order to avoid slowing down the charging speed, the charging power of all working charging vehicles is adjusted to the first preset power within the first time window. Therefore, the first type of working charging vehicle broadcasts the power adjustment instruction, so that each second type of working charging vehicle adjusts to the first preset power for charging within the first time window according to the power adjustment instruction. Compared with continuously charging at the second preset power within the first time window, the charging time can be reduced, and compared with the related art in which disconnection directly closes the order, the embodiment reduces the probability of abnormal failure of the order due to the setting of the delayed reconnection time.

[0092] In an exemplary embodiment of the present application, after step S820, the second type of working charging vehicle is configured to perform the following steps: S840, broadcast the power adjustment information and the corresponding sending request according to the preset short-distance communication protocol; wherein the power adjustment information includes the power adjustment time and the corresponding unique identifier.

[0093] The first type of working charging vehicle is configured to perform the following steps: S720, in response to receiving any power adjustment information and the corresponding sending request, the cloud platform sends the power adjustment information and the corresponding sending request.

[0094] In this embodiment, in order to enable the cloud platform to accurately charge, first, the second type of working charging vehicle disconnected with the cloud platform broadcasts the power adjustment information and the corresponding sending request according to the preset proximity communication protocol, and the first type of working charging vehicle receives any power adjustment information and the corresponding sending request, and then sends the power adjustment information and the corresponding sending request to the cloud platform. That is, the second type of working charging vehicle sends its power adjustment information (including the power adjustment time and the corresponding unique identifier) to the cloud platform through the first type of working charging vehicle, so that the cloud platform obtains the charging time corresponding to the first preset power (the sum of the charging time before disconnection and the time interval between the power adjustment time and the completion of charging) and the charging time corresponding to the second preset power (the time interval between the disconnection time and the power adjustment time). Further, the corresponding electric energy consumption and the charging fee are obtained.

[0095] In an exemplary embodiment of the present application, after step S1230, the cloud platform is further configured to perform the following steps: S1250, if any second type of working charging vehicle fails to reconnect successfully within the first time window, obtaining the sub-area identifier corresponding to the second type of working charging vehicle; each sub-area corresponding to each sub-area identifier has a corresponding preset reconnection time; the length of the preset response time period is less than the length of the first time window, and the start time of the preset response time period is equal to the start time of the first time window.

[0096] Specifically, the preset reconnection time corresponding to each sub-area is determined according to the following steps: S1251, according to the preset charging position, the area of the vehicle charging system is divided into sub-areas to obtain a set of sub-area identifiers QY=(QY1, QY2, …, QY x , …, QY y ); x=1, 2, …, y; y is the number of sub-areas obtained by dividing the area of the vehicle charging system; QY x is the area identifier of the xth sub-area in the vehicle charging system; each sub-area has a corresponding charging position.

[0097] Here, the area of the vehicle charging system is divided into sub-areas according to the preset charging position, so that each sub-area has a corresponding charging position. Each sub-area has a corresponding area identifier.

[0098] S1252, according to QY, obtaining a set of historical reconnection time lists LT=(LT1, LT2, …, LT x , …, LT y ); wherein, LT x is the historical reconnection time list corresponding to QY x ; LTx = (LT x1 , LT x2 , …, LT xp , …, LT xq ) ; LT xp is the historical reconnection time of the working charging vehicle corresponding to the pth key event in the fourth time window in the sub-region where QY x is located; the key event is the event that all working charging vehicles are disconnected from the cloud platform and automatically reconnect successfully; the end time of the fourth time window is the time when all working charging vehicles connected are disconnected; Here, the historical reconnection time corresponding to each key event (the event that all working charging vehicles are disconnected from the cloud platform and automatically reconnect successfully) in the fourth time window before the current time is obtained for each sub-region to obtain the historical multiple reconnection times of each sub-region.

[0099] S1253, according to LT, clustering each historical reconnection time list to obtain a clustering list set JL = (JL1, JL2, …, JL x , …, JL y ); JL x is the clustering cluster list corresponding to QY x ; JL x = (JL x1 , JL x2 , …, JL xm , …, JL xf(x) ); m = 1, 2, …, f(x); f(x) is the number of clustering clusters corresponding to JL x ; JL xm is the mth clustering cluster corresponding to JL x ; each clustering cluster list contains at least one clustering cluster; each clustering cluster contains at least one historical reconnection time.

[0100] S1254, if the number of historical reconnection times in JL xm is greater than or equal to a preset number, the longest historical reconnection time in JL xm is determined as the preset reconnection time of the sub-region corresponding to QY x .

[0101] Here, for each sub-region, the multiple historical reconnection times corresponding to the historical multiple key events are clustered, and if the number of historical reconnection times in a certain clustering cluster is greater than a preset number, it means that the working charging vehicles in the sub-region mostly reconnect successfully within the time corresponding to the clustering cluster when the key event occurs in history. At this time, the longest historical reconnection time in this clustering cluster is determined as the preset reconnection time corresponding to the sub-region.

[0102] S1260, a broadcast task of sending each time extension instruction corresponding to each second type of charging vehicle which fails to reconnect successfully in the first time window to each first type of working charging vehicle; the time extension instruction includes a corresponding preset reconnection time and a unique identifier.

[0103] Specifically, when all working charging vehicles are disconnected from the cloud platform, it may be caused by transient or periodic network instability, at this time, each working charging vehicle can reconnect successfully with high probability. Therefore, for the second type of charging vehicle which fails to reconnect successfully in the first time window, the reconnection time is extended to reduce the failure rate of orders. However, since the second type of working charging vehicle is disconnected from the cloud platform, it needs to use the first type of working charging vehicle which has successfully reconnected as an information transmission medium. That is, a broadcast task of sending each time extension instruction corresponding to each second type of charging vehicle which fails to reconnect successfully in the first time window to each first type of working charging vehicle. Since each second type of working charging vehicle is in a different sub-region, although they are both extending the time, the application determines the corresponding extended reconnection time according to the preset reconnection time corresponding to the sub-region where each second type of working charging vehicle is located.

[0104] The first type of working charging vehicle is used to perform the following steps: S730, in response to receiving the broadcast task of each time extension instruction, broadcasting each time extension instruction according to a preset short-distance communication protocol; The second type of working charging vehicle which fails to reconnect successfully in the first time window is used to perform the following steps: S850, in response to receiving the corresponding preset reconnection time and the unique identifier, and the preset reconnection time being greater than the length of the first time window, reconnecting with the cloud platform in the extended time; the extended time is the difference between the preset reconnection time and the length of the first time window.

[0105] Specifically, as an example: if the preset reconnection time of the second type of working charging vehicle which fails to reconnect successfully in the first time window is 300s, and the time length of the first time window is 90s, then the extended time is 210s.

[0106] S860, if the connection response information of the cloud platform is received in the extended time, the charging task is continued to be performed at the first preset power until the target power is reached; and a charging completion signal is sent to the cloud platform.

[0107] In this embodiment, when all working charging vehicles are disconnected from the cloud platform, it is possible that the disconnection is caused by transient or periodic network instability, at this time, the probability of each working charging vehicle reconnecting successfully is high. Therefore, for the second type of charging vehicle that fails to reconnect within the first time window, the reconnection time is extended to reduce the order failure rate. However, since the second type of working charging vehicle is disconnected from the cloud platform, the first type of working charging vehicle that has successfully reconnected needs to act as an information transmission medium. That is, a broadcast task of sending a time extension instruction corresponding to each second type of charging vehicle that fails to reconnect within the first time window to each first type of working charging vehicle. Since each second type of working charging vehicle is in a different sub-region, although the time is extended, considering that the network situation may be affected by the location of each working charging vehicle, for example, some locations are blocked, and the network status may not be good. Therefore, in this embodiment, the extended reconnection time of each second type of working charging vehicle is determined according to the preset reconnection time of the sub-region corresponding to the second type of working charging vehicle. Compared with using the same extended reconnection time, considering the location factor of the sub-region where each second type of working charging vehicle is located, a more accurate extended reconnection time can be provided for the charging vehicle in each sub-region, and the order failure probability can be reduced more effectively.

[0108] In an exemplary embodiment of the present application, after step S1253, the above method further comprises: S1255, if JL x The number of historical reconnection times corresponding to any clustering cluster in JL x is less than the preset number, the longest historical reconnection time in JL x is determined as the preset reconnection time of the sub-region corresponding to JL

[0109] Specifically, if the number of historical reconnection times corresponding to any clustering cluster in JL x is less than the preset number, it indicates that the length distribution of the corresponding historical reconnection time in the sub-region is relatively uniform, and it may be affected by other factors in addition to the location. In order to maximize the reduction of the order failure rate, the longest historical reconnection time in JL x is determined as the preset reconnection time of the sub-region corresponding to JL x .

[0110] Embodiments of the present application also provide a computer program product comprising program code for causing an electronic device to perform the steps of the methods described above according to various exemplary embodiments of the present application when the program product is run on the electronic device.

[0111] Moreover, although individual steps of the methods in the present application are described in a particular order in the figures, this is not required or implied as to the order of execution of the steps, nor is it required that all of the steps be performed to achieve the desired result. Additionally or alternatively, certain steps can be omitted, combined into a single step, broken into multiple steps, and / or the like.

[0112] From the above description of the embodiments, those skilled in the art will easily understand that the example embodiments described herein can be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.

[0113] In the example embodiments of the present application, an electronic device capable of implementing the above method is also provided.

[0114] Those skilled in the art can understand that various aspects of the present application can be implemented as a system, a method, or a program product. Therefore, various aspects of the present application can be embodied in the form of a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, which can be collectively referred to as "circuitry", "module", or "system" herein.

[0115] The electronic device according to this embodiment of the present application. The electronic device is merely an example, and should not impose any limitation on the functions and use range of the embodiments of the present application.

[0116] The electronic device is in the form of a general computing device. The components of the electronic device can include, but are not limited to, the at least one processor described above, the at least one storage described above, and a bus connecting different system components (including the storage and the processor).

[0117] The storage stores program code that can be executed by the processor, so that the processor performs the steps according to various example embodiments of the present application described in the "example method" section of the present specification.

[0118] The storage can include a readable medium in the form of a volatile storage, such as a random access memory (RAM) and / or a cache memory, and can further include a read-only memory (ROM).

[0119] The storage can also include a program / utility, having a set of program modules that include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or a combination thereof, can include implementation of a networking environment.

[0120] The bus can represent one or more of several types of bus structures, including a storage bus or

[0121] The electronic device can also communicate with one or more external devices such as a keyboard or a pointing device, through an I / O interface. Additionally, the electronic device can communicate with one or more devices that enable a user to interact with the electronic device, and / or one or more devices that enable the electronic device to communicate with one or more other computing devices. Such communication can occur via an I / O interface. Still yet, the electronic device can communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or the Internet) through a network adapter. As an example, the network adapter can include a modem, a router, a switch or a combination thereof, for facilitating communication with one or more other computing devices. It will be appreciated that the network adapter can be collectively provided as a communication component, for communicating with one or more other computing devices.

[0122] Those skilled in the art will readily understand that the example embodiments described herein can be implemented by software and / or by hardware coupled with software, as described above. Thus, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to perform the methods according to the embodiments of the present application.

[0123] In the example embodiments of the present application, a computer readable storage medium is also provided, which stores a program product capable of implementing the methods described above. In some possible embodiments, various aspects of the present application can also be implemented in the form of a program product, which includes program codes for causing a terminal device to perform the steps described in the above “example method” section according to various example embodiments of the present application when the program product is run on the terminal device.

[0124] A program product can take any combination of one or more computer-readable media. The computer-readable media can be a computer-readable storage medium or a computer-readable signal medium. The computer-readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specific examples (a non-exhaustive list) of the computer-readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0125] The computer-readable signal medium can include a computer-readable storage medium that is propagated as a carrier wave in a baseband or propagated as part of a propagated data signal in a carrier, such as a propagated signal. The propagated signal can take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport programming for use by or in connection with an instruction execution system, apparatus, or device.

[0126] The program code embodied on the computer-readable media can be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the above.

[0127] Program code used to carry out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider. The application program code can be embodied in any combination of data and / or computer-executable instructions that can be executed on the computing device.

[0128] In addition, the above-described flowcharts are merely illustrative of the processes included in the method according to the exemplary embodiments of the present application, and are not intended to limit the purpose. It is easily understood that the processes shown in the above-described flowcharts do not indicate or limit the time sequence of the processes. In addition, it is easily understood that the processes can be executed synchronously or asynchronously, for example, in a plurality of modules.

[0129] It should be noted that, although several modules or units of the devices for action execution are mentioned in the above detailed description, the division into these modules or units is not mandatory. Indeed, according to an embodiment of the application, the features and functionalities of two or more of the above-described modules or units can be embodied in one module or unit. Conversely, the features and functionalities of one of the above-described modules or units can be further divided into several modules or units.

[0130] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of determining the amount of electrical energy consumed by a charging trolley, characterized in that, The application is applied to a vehicle charging system, the vehicle charging system comprises a plurality of working charging vehicles performing charging tasks and a cloud platform; each working charging vehicle sends connection confirmation information to the cloud platform once every interval preset time period, and if connection response information of the cloud platform is received, it is determined that the working charging vehicle is not disconnected; if connection response information of the cloud platform is not received for a preset number of times continuously, it is determined that the working charging vehicle is disconnected from the cloud platform; The cloud platform is used to perform the following steps: S110, in response to receiving a charging task of a user, the charging task is assigned to a corresponding working charging vehicle according to a preset assignment rule; The working charging vehicle is used to perform the following steps: S210, in response to receiving a charging task assigned by the cloud platform, a corresponding charging task is performed at a first preset power; wherein each charging task comprises a corresponding target power; S220, if disconnection from the cloud platform is detected during the execution of the charging task, a reconnection request information is sent to the cloud platform, and the working charging vehicle is adjusted to a second preset power to continue to execute the charging task within a first time window; the second preset power is less than the first preset power; the start time of the first time window is the time of disconnection from the cloud platform; S230, if connection response information is not received within a first response time period of the first time window, the connection module of the working charging vehicle is restarted; the connection module is used for communication with the cloud platform; S240, if connection response information is received within a second response time period of the first time window, the working charging vehicle is adjusted to the first preset power to continue to execute the charging task until the corresponding target power is reached; and a charging completion signal is sent to the cloud platform; wherein the time length of the first response time period is less than the time length of the second response time period; and the time length of the first time window is equal to the sum of the time lengths of the first response time period and the second response time period; The cloud platform is also used to perform the following steps: S120, in response to receiving the charging completion signal, a first working time set GYT=(GYT1, GYT2, GYT3, GYT4) corresponding to the charging completion signal is obtained; wherein GYT1 is the start time of the working charging vehicle corresponding to the charging completion signal to execute the charging task at the first preset power; GYT2 is the time of disconnection of the working charging vehicle corresponding to the charging completion signal from the cloud platform; GYT3 is the time of receiving the connection response information of the cloud platform by the working charging vehicle corresponding to the charging completion signal; GYT4 is the time of completing the charging task by the working charging vehicle corresponding to the charging completion signal; S130, the power consumption of the working charging vehicle corresponding to the charging completion signal is generated according to GYT, the first preset power and the second preset power.

2. The method of claim 1, wherein After step S230, the working charging vehicle is also used to perform the following steps: S250, if the connection response information of the cloud platform is not received within the first time window, the execution of the charging task is stopped; and the first time window is determined as a low-power time window; The cloud platform is also used to perform the following steps: S140, a second working time set GET=(GYT1, GYT2) is obtained; S150, generating the power consumption of the working charging vehicle according to the GET, the length of the low-power time window, the first preset power and the second preset power.

3. The method of claim 2, wherein If there is at least one key charging vehicle performing a charging task in a range centered on the location of the working charging vehicle and having a distance corresponding to a preset proximity communication protocol as a radius, the working charging vehicle further performs the following steps after step S220: S260, according to the preset short-range communication protocol, obtains a list of key time intervals GT=(GT1, GT2, ..., GT...). i , ..., GT n ); i = 1, 2, ..., n; where n is the number of critical charging vehicles; GT i For the list of critical time intervals for the i-th critical charging vehicle; GT i =(GT i1 GT i2 , ..., GT ij , ..., GT if（i） ); j=1,2,…,f(i); f(i) is the number of times the i-th key charging vehicle receives connection response information within the third time window; GT ij The time interval between the time when the i-th key charging vehicle receives the connection response information and the time when the corresponding connection confirmation information is sent for the j-th time within the third time window; the end time of the third time window is the start time of the first time window; S270, based on GT, obtain the key time fluctuation value set GTB=(GTB1, GTB2, ..., GTB) i , ..., GTB n ); among which, GTB i GTB represents the time fluctuation value corresponding to the i-th critical charging vehicle. i =(∑ f（i） j=1 (GT ij -avg(GT i )) 2 ) / f(i); avg() is the preset function to determine the average value; S280, if (a / n)≥n0 and no connection response information is received in the first time window, continuing to perform the charging task in the second time window after the end of the first time window at the second preset power; wherein a is the number of time fluctuation values greater than a preset time fluctuation value threshold in the GTB; n0 is a preset fluctuation value proportion; the start time of the second time window is the end time of the first time window; S290, if connection response information is received in the second time window, adjusting to the first preset power to continue performing the charging task until the target power is reached; and sending a charging completion signal to the cloud platform; The cloud platform further performs the following steps: S160, jumping to step S120.

4. The method of claim 3, wherein After step S280, the working charging vehicle further performs the following steps: S2100, if no connection response information is received in the second time window, stopping performing the charging task and determining the first time window and the second time window as the low-power time window; S2110, broadcasting a delay stop information and a corresponding sending request according to a preset proximity communication protocol; the delay stop information includes a unique identifier of the working charging vehicle; The key charging vehicle further performs the following steps: S310, in response to receiving any delay stop information and a corresponding sending request and not being disconnected from the cloud platform, sending the delay stop information to the cloud platform; The cloud platform further performs the following steps: S170, jumping to step S140.

5. The method of claim 3, wherein After step S270, the working charging vehicle further performs the following steps: S2120, if (a / n)<n0 and no connection response information of the cloud platform is received in the first time window, stopping performing the charging task; and determining the first time window as the low-power time window; The cloud platform further performs the following steps: S180, jumping to step S140.

6. The method of claim 1, wherein The length of the first time window is 90 seconds.

7. A non-transitory computer-readable storage medium, comprising: The storage medium stores at least one instruction or at least one program, which is loaded and executed by the processor to realize the method of any one of claims 1-6.

8. An electronic device, comprising: The non-transitory computer-readable storage medium includes a processor and the non-transitory computer-readable storage medium of claim 7.

Images