WO2021068947A1

WO2021068947A1 - System and method for identifying charging pile fault

Info

Publication number: WO2021068947A1
Application number: PCT/CN2020/120248
Authority: WO
Inventors: 徐阳阳; 赵叶; 梁明
Original assignee: 北京嘀嘀无限科技发展有限公司
Priority date: 2019-10-10
Filing date: 2020-10-10
Publication date: 2021-04-15

Abstract

A system and method for identifying a charging pile fault. The method comprise: in response to a charging request, generating an order for the charging request (610); during the process of executing a current charging operation on a vehicle, acquiring charging state data (620); determining whether the charging state data comprises abnormal state data (630); in response to determining that the charging state data comprises abnormal state data, determining the order as an abnormal order, and generating for the abnormal order an identifier corresponding to the abnormal state data (640); and sending the abnormal order to a server connected to a charging pile (650).

Description

System and method for fault identification of charging pile

cross reference

This application claims the priority of the Chinese application filed on October 10, 2019 with the application number No. 201910958433.0, the priority of the Chinese application filed on December 31, 2019 with the application number No. 201911408140.1, and in 2020 The priority of the Chinese application with the application number No. 202010167714.7 filed on March 11, 2010, the entire content of which is incorporated herein by reference.

Technical field

The present application relates to a system and method for identifying the fault of a charging pile, and in particular to a system and method for determining the cause of a charging pile fault and monitoring the charging pile.

Background technique

With the development of the new energy industry, new energy vehicles are becoming more and more popular with people, which greatly meets people's daily travel needs. As an indispensable charging device for new energy vehicles, charging piles have a high utilization rate in daily life. Charging piles that are safe, durable and easy to operate play a key role in the charging of new energy vehicles. When the user uses the charging pile, the charging pile is usually in an unattended self-service state, and its working status cannot be guaranteed in a timely and effective manner. The user often encounters abnormal charging problems during the charging process, such as user violations. Operation, charging pile failure, charging vehicle failure, etc. However, the above-mentioned abnormal charging problem sometimes cannot be accurately identified by the charging station platform, which affects the user experience to a certain extent, reduces travel efficiency, and is not conducive to the development of social production. Therefore, it is desirable to provide a system and method for automatic identification and monitoring of charging pile faults.

Summary of the invention

One aspect of the present application relates to a method for identifying a fault of a charging pile. The method includes: in response to obtaining a charging request, generating an order for the charging request; obtaining charging state data during the current charging operation of the vehicle; determining whether the charging state data includes abnormal state data; responding to the determination If the charging state data includes the abnormal state data, it is determined that the order is an abnormal order, and an identifier corresponding to the abnormal state data is generated for the abnormal order; and the abnormal order is sent to the The server connected to the charging pile.

In some embodiments, the charging state data includes state data of operable parts of the charging pile. In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order includes: responding to determining the charging If the state data of the operable part of the pile is an abnormal state, a first identifier is generated for the abnormal order.

In some embodiments, the charging state data includes interaction data between a charging post and the vehicle. In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order includes: in response to determining the interaction If the data is in an abnormal state, a second identifier is generated for the abnormal order.

In some embodiments, generating an identifier corresponding to the abnormal state data for the abnormal order includes: obtaining a mapping relationship between the abnormal state data and the identifier; and determining the abnormal state data according to the mapping relationship and the abnormal state data. The identifier of the abnormal order.

The second aspect of the present application relates to a method for fault identification and monitoring of charging piles. The method includes: acquiring information of an abnormal order, the abnormal order reflecting the presence of abnormal state data during the charging operation of the charging pile, the information of the abnormal order including an identifier corresponding to the abnormal state data; and according to The identifier determines the reason for the abnormality of the abnormal order.

In some embodiments, the abnormal cause includes at least one of charging pile failure, vehicle failure, and abnormal operation.

In some embodiments, determining the reason for the abnormality of the abnormal order according to the identifier includes: obtaining charging pile information corresponding to the abnormal order; obtaining historical abnormalities corresponding to the charging pile information in a historical time period Order information; acquiring the historical identifier in the information of the historical abnormal order; and determining the abnormal reason of the abnormal order according to the proportion of the identifier in the historical identifier.

In some embodiments, the identifier is a first identifier, the first identifier indicates that the state data of the operable component of the charging pile is an abnormal state, and the abnormal order is determined according to the identifier. The reason for the abnormality includes: determining whether the proportion of the first identifier in the historical identifier is greater than a threshold.

In some embodiments, the method further includes: in response to determining that the proportion of the first identifier in the historical identifier is greater than the threshold, determining that the cause of the abnormality is a charging pile failure.

In some embodiments, the method further includes: in response to determining that the proportion of the first identifier in the historical identifier is less than the threshold, determining that the cause of the abnormality is an abnormal operation.

In some embodiments, the identifier is a second identifier, and the second identifier indicates that the interaction data between the charging post and the vehicle being charged is in an abnormal state, and the identifier is used to determine the The abnormal reason for the abnormal order includes: determining whether the proportion of the second identifier in the historical identifier is greater than a threshold.

In some embodiments, the method further includes: in response to determining that the proportion of the second identifier in the historical identifier is greater than the threshold, determining that the cause of the abnormality is a charging pile failure.

In some embodiments, the method further includes: in response to determining that the proportion of the second identifier in the historical identifier is less than the threshold, determining that the cause of the abnormality is a vehicle failure.

In some embodiments, the method further includes: generating a mapping relationship between abnormal state data and an identifier; and sending the mapping relationship to the charging pile.

In some embodiments, the method further includes: generating a mapping relationship between the reason for the abnormality and the processing personnel; and sending the reason for the abnormality to the terminal of the corresponding processing personnel.

In some embodiments, the abnormal cause of the abnormal order is a failure of the charging pile, and the method further includes: determining that the charging pile corresponding to the abnormal order is an abnormal charging pile; and performing a monitoring operation on the abnormal charging pile.

In some embodiments, determining that the charging pile corresponding to the abnormal order is an abnormal charging pile includes: if multiple consecutive charging orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is the charging pile If it fails, it is determined that the charging pile is an abnormal charging pile.

In some embodiments, the monitoring operation includes an isolation operation, and the isolation operation includes: in response to obtaining a charging request from a client, if the charging pile requested by the charging request is the abnormal charging pile, sending a request to the The client returns abnormal information about the abnormal charging pile, and/or provides the client with guidance information about other normal charging piles other than the abnormal charging pile.

In some embodiments, the monitoring operation includes a repair operation, and the repair operation includes: determining whether the version of the abnormal charging pile is the latest available version.

In some embodiments, the repair operation further includes: in response to determining that the version of the abnormal charging pile is the latest available version, sending a restart instruction to the abnormal charging pile.

In some embodiments, the repair operation further includes: in response to determining that the version of the abnormal charging pile is not the latest available version, sending an upgrade instruction to the abnormal charging pile.

In some embodiments, after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is still received within a preset time period, and the reason for the abnormality is the failure of the charging pile, the corresponding processing personnel The terminal sends a maintenance work order for the abnormal charging pile.

In some embodiments, after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is not received within a preset time period, the abnormal charging pile is set as a normal charging pile.

The third aspect of the present application relates to a method for identifying faults of charging piles. The method includes: acquiring the time point at which the server receives the current communication data, the communication data being sent by the charging pile; taking the time point as a starting point, determining whether the server receives a new communication within a preset first time threshold Data; and in response to determining that the server does not receive new communication data within a preset first time threshold, it is determined that the charging pile has an offline failure point.

In some embodiments, the method further includes: determining whether the charging pile has continuous offline fault points and the number of the continuous offline fault points exceeds a fault point threshold; and in response to determining that the charging pile has continuous If the number of offline fault points exceeds the fault point threshold, it is determined that the charging pile has a fault.

In some embodiments, the method further includes: using the time point as a starting point, determining whether the server has not received new communication data within a preset second time threshold, wherein the second time threshold is greater than the The first time threshold; and in response to determining that the server does not receive new communication data within the preset second time threshold, it is determined that the charging pile is faulty.

In some embodiments, the communication data includes a heartbeat signal or charging status data.

In some embodiments, the charging status data includes an abnormal order signal, and the method further includes: obtaining the number of historical abnormal orders and the total number of historical orders of the charging pile; and determining that the number of historical abnormal orders of the charging pile accounts for historical abnormal orders. Whether the proportion of the total number of orders exceeds the proportion threshold; and in response to determining that the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the proportion threshold, it is determined that the charging pile is faulty.

In some embodiments, the charging state data includes state data of the charging pile, and the method further includes: in response to determining that the server receives new communication data within a preset first time threshold, acquiring the charging pile Determine whether the state data of the charging pile is within a preset range; and in response to determining that the state data of the charging pile is not within the preset range, it is determined that the charging pile is faulty.

In some embodiments, the status data of the charging pile includes the temperature, current value, voltage value of the operable parts of the charging pile, the real-time output power of the charging pile, the accumulated charging time of the charging pile, and the accumulated charging amount of the charging pile. At least one item of.

In some embodiments, the communication data includes fault information, and the method further includes: determining that the charging pile has a fault.

In some embodiments, the method further includes: in response to determining that the charging pile is faulty, acquiring the device attribute of the charging pile and the first terminal attribute corresponding to the device attribute; and according to the first terminal The attribute sends fault reminder information to the first terminal, where the fault reminder information includes the device attribute of the charging pile.

In some embodiments, the method further includes: obtaining the proportion of charging piles determined to be faulty in the charging station to the total number of charging piles; determining whether the proportion exceeds a threshold; in response to determining that the proportion exceeds the threshold, Acquiring the site attribute of the charging station and the second terminal attribute corresponding to the site attribute; and sending alarm information to the second terminal according to the second terminal attribute, the alarm information including the site attribute of the charging station.

The fourth aspect of the application relates to a method for identifying and monitoring faults of charging piles. The method includes: acquiring the information of the charging order and analyzing the information of the charging order; if the charging order is abnormally stopped, and the reason for the abnormal stop is caused by the abnormal charging pile, determining that the charging pile is abnormal charging Pile; and monitoring the charging pile.

In some embodiments, determining that the charging pile is an abnormal charging pile includes: if a plurality of continuous charging orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is all charging pile failure, then determining The charging pile is an abnormal charging pile.

The fifth aspect of the present application relates to a system for identifying faults of charging piles. The system includes: one or more storage devices that store a set of instructions for identifying faults in the charging pile; and one or more processors that communicate with the one or more storage devices, wherein, when the set of instructions is executed, The one or more processors are configured to: in response to obtaining a charging request, generate an order for the charging request; obtain charging state data during the current charging operation of the vehicle; determine whether the charging state data includes abnormal state data In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order; and sending the abnormal order To the server connected to the charging pile.

The sixth aspect of the present application relates to a system for identifying and monitoring faults of charging piles. The system includes: one or more storage devices that store a set of instructions for charging pile fault identification and monitoring; and one or more processors that communicate with the one or more storage devices, wherein, when the set of instructions is executed When instructed, the one or more processors are used to: obtain information about an abnormal order, the abnormal order reflects the presence of abnormal state data during the charging operation of the charging pile, and the information of the abnormal order includes information related to the abnormal state data. Corresponding identifier; and, according to the identifier, determine the reason for the abnormality of the abnormal order.

The seventh aspect of the present application relates to a system for identifying faults of charging piles. The system includes: one or more storage devices that store a set of instructions for charging pile fault identification and monitoring; and one or more processors in communication with the one or more storage devices, wherein, when the set of instructions is executed When instructing, the one or more processors are used to: obtain the time point when the server receives the current communication data, the communication data is sent by the charging pile; taking the time point as the starting point, determine that the time is within the preset first time threshold Whether the server receives new communication data; and in response to determining that the server does not receive new communication data within a preset first time threshold, it is determined that the charging pile has an offline fault point.

The eighth aspect of the present application relates to a system for identifying and monitoring faults of charging piles. The system includes: one or more storage devices that store a set of instructions for charging pile fault identification and monitoring; and one or more processors in communication with the one or more storage devices, wherein, when the set of instructions is executed When instructing, the one or more processors are used to: obtain the information of the charging order and analyze the information of the charging order; if the charging order is abnormally stopped and the reason for the abnormal stop is caused by the abnormal charging pile, it is determined The charging pile is an abnormal charging pile; and a monitoring operation is performed on the charging pile.

The ninth aspect of the present application relates to a computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing a fault of a charging pile is implemented, the method comprising: responding To obtain a charging request, generate an order for the charging request; obtain charging state data during the current charging operation of the vehicle; determine whether the charging state data includes abnormal state data; in response to determining that the charging state data is If the abnormal state data is included, it is determined that the order is an abnormal order, and an identifier corresponding to the abnormal state data is generated for the abnormal order; and the abnormal order is sent to a server connected to the charging pile.

The tenth aspect of the present application relates to a computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for identifying and monitoring faults of a charging pile is realized, the method comprising : Acquire information about an abnormal order, the abnormal order reflects the presence of abnormal state data during the charging operation of the charging pile, the information of the abnormal order includes an identifier corresponding to the abnormal state data; and according to the identifier To determine the reason for the abnormal order.

The eleventh aspect of the present application relates to a computer-readable storage medium that stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing a fault in a charging pile is implemented, the method comprising: Acquiring the time point at which the server receives the current communication data, the communication data being sent by the charging pile; taking the time point as a starting point, determining whether the server receives new communication data within a preset first time threshold; and responding to It is determined that the server does not receive new communication data within the preset first time threshold, and then it is determined that the charging pile has an offline fault point.

The twelfth aspect of the present application relates to a computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing and monitoring faults of a charging pile is implemented. Including: obtaining the information of the charging order, and analyzing the information of the charging order; if the charging order is abnormally stopped and the reason for the abnormal stop is caused by the abnormal charging pile, determining that the charging pile is an abnormal charging pile; and Perform monitoring operations on the charging pile.

Some of the additional features of this application can be explained in the following description. Through the study of the following description and the corresponding drawings or the understanding of the production or operation of the embodiments, a part of the additional features of this application will be obvious to those skilled in the art. The features of the present application can be realized and achieved through the practice or use of the methods, means, and combinations of various aspects of the specific embodiments described below.

Description of the drawings

This application is further described through exemplary embodiments. These exemplary embodiments will be described in detail with the accompanying drawings. These embodiments are not restrictive. In these embodiments, the same numbers in the figures indicate similar structures, in which:

Fig. 1 is a schematic diagram of an exemplary charging monitoring system according to some embodiments of the present application;

Fig. 2 is a schematic diagram of exemplary hardware and/or software components of an exemplary mobile device on which a client terminal can be implemented according to some embodiments of the present application;

3 is a schematic diagram of exemplary hardware and software components of an exemplary computing device according to some implementations of the present application;

Fig. 4 is an exemplary module diagram of a charging pile according to some embodiments of the present application;

Fig. 5 is an exemplary block diagram of a processing device according to some embodiments of the present application;

FIG. 6 is a flowchart of an exemplary process 600 for identifying a fault of a charging pile according to some embodiments of the present application;

FIG. 7 is a flowchart of an exemplary process 700 for determining the abnormal cause of an abnormal order according to some embodiments of the present application;

FIG. 8 is a flowchart of an exemplary process 800 for monitoring charging piles according to some embodiments of the present application;

FIG. 9 is a flowchart of an exemplary process 900 for monitoring charging piles according to some embodiments of the present application;

FIG. 10 is a flowchart of an exemplary process 1000 of a charging pile monitoring method according to some embodiments of the present application;

FIG. 11 is a flowchart of an exemplary process 1100 for identifying a fault of a charging pile according to some embodiments of the present application;

FIG. 12 is a flowchart of an exemplary process 1200 for identifying a fault of a charging pile according to some embodiments of the present application;

FIG. 13 is a flowchart of an exemplary process 1300 for identifying a fault of a charging pile according to some embodiments of the present application;

Fig. 14 is a schematic diagram of an exemplary charging monitoring system according to some embodiments of the present application;

Fig. 15A is an exemplary schematic diagram of a data transmission process between a charging pile and a platform server according to some embodiments of the present application;

FIG. 15B is an exemplary schematic diagram of the bill transmission process between the charging pile and the platform server according to some embodiments of the present application; and

Fig. 15C is an exemplary schematic diagram of a signal transmission process between a charging pile and a platform server according to some embodiments of the present application.

Detailed ways

The following description is to enable those of ordinary skill in the art to implement and use this application, and the description is provided in a specific application scenario and its required environment. For those of ordinary skill in the art, it is obvious that various changes can be made to the disclosed embodiments, and without departing from the principles and scope of this application, the general principles defined in this application can be applied to other Embodiments and application scenarios. Therefore, this application is not limited to the described embodiments, but should be given the broadest scope consistent with the claims.

The terms used in this application are only used to describe specific exemplary embodiments and do not limit the scope of this application. As shown in the present application and claims, unless the context clearly indicates exceptions, the words "a", "an", "an" and/or "the" do not specifically refer to the singular, but may also include the plural. It should be understood that the terms "including" and/or "comprising" used in this application only suggest the clearly identified features, steps, operations, elements and/or components, but do not exclude the presence or addition of one or more Other features, steps, operations, elements, components, and/or combinations thereof.

Although this application makes various references to certain modules in the system according to the embodiments of this application, any number of different modules can be used and run on the client, charging pile, and/or server. These modules are intended to illustrate, not to limit the scope of this application. Different modules can be used in different aspects of the system and method.

According to the description of the following drawings, the features of the present application and the operation methods and functions of related structural elements, as well as the combination of components and the economics of manufacturing, may become more obvious. These drawings constitute a part of the specification of the present application. It should be understood that the drawings are only for the purpose of illustration and description, and are not intended to limit the scope of the application. It should be understood that the drawings are not drawn to scale.

A flowchart is used in this application to illustrate the operations performed by the system according to some embodiments of the application. It should be understood that the operations in the flowchart may be performed out of order. Instead, the various steps can be processed in reverse order or simultaneously. At the same time, you can also add one or more other operations to these flowcharts, or delete a step or several steps from these flowcharts.

The terms "requester", "service requester", "customer", "user" and "driver" in this application are used interchangeably and refer to the individual or entity that requests or subscribes to the service. In this application, the terms "driver", "driver terminal", "user equipment" and "client terminal" can be used interchangeably. In this application, the term "service request" means a request that can be initiated by a user (eg, passenger, requester, operator, service requester, customer, driver). For example, the service request may involve the use of a charging post to charge an electric vehicle. The system can find applications in many fields, such as taxi transportation services, driving applications, map applications or navigation applications.

In the process of using charging piles to charge vehicles, generally three parties are involved: users, charging piles, and vehicles. The occurrence of abnormal orders may be caused by any participant. For example, if the user fails to connect the charging gun after starting charging or forcibly unplugging the charging gun during the charging process, the order is abnormal; another example is that the vehicle battery management system does not respond in time when the charging pile interacts with the vehicle during the charging process. Order abnormalities caused by forcibly ending orders; another example is an order abnormality caused by a malfunction of the charging pile itself, such as a network communication failure between the charging pile and the server or a loose connection device of the charging gun. In the prior art, for abnormal orders, all the reasons for the abnormality are usually attributed to the failure of the charging pile, and then maintenance personnel will be dispatched to repair the failure of the charging pile. However, in some cases, the state of the charging pile is normal. Such a treatment method often results in maintenance personnel who did not find the problem after inspecting the charging pile, which caused a waste of human and material resources and still did not solve the problem. .

In addition, in some cases, the charging pile monitoring alarm method is mainly the communication between the charging pile and the platform, allowing the charging pile to actively report the fault and diagnose, but if the charging pile itself is abnormal and does not actively upload fault abnormal information, the platform will not be able to sense in time To failure. At the same time, even if the charging pile is normal at the time of uploading information, it cannot be completely guaranteed that the pile will have no abnormal faults during charging. Existing methods for detecting abnormalities of charging piles are often manually discovered, which means that only after the user feedbacks the abnormality of the equipment, the relevant maintenance personnel will rush to the site to perform maintenance operations. From failure to repair, there is a long delay. And the failure of some charging piles may be "hidden failure", for example, the connection of the charging gun is loose, which often results in abnormal orders during the charging process. This type of problem is often not intuitively observed through surface phenomena, and it is relatively difficult to find.

In view of the foregoing problems, some embodiments of the present application provide systems and methods for automatic fault identification and monitoring of charging piles.

One aspect of the present application relates to a system and method for charging pile fault identification. The system and method can be applied at the end of a charging pile. The charging pile can respond to charging requests and generate orders. The charging post can obtain charging state data during the charging operation of the vehicle, and determine whether the charging state data includes abnormal state data. The charging pile may determine an abnormal order based on the abnormal state data, and generate an identifier corresponding to the abnormal state data for the abnormal order. The charging pile may send the abnormal order to a server connected to the charging pile. According to some embodiments of the present application, the charging pile can collect charging status data in real time during the charging process of the vehicle. According to the charging status data, the cause of the abnormal charging order can be determined. For order abnormalities caused by different reasons, different identifications can be configured. symbol. Therefore, when the server receives the abnormal order information, it can determine the reason for the abnormal order according to the identifier.

Another aspect of this application relates to a system and method for charging pile fault identification and monitoring. The system and method can be applied to a server connected to a charging pile (for example, a charging pile operator platform server). The server can obtain the information of the abnormal order, and determine the reason for the abnormal order according to the identifier in the abnormal order information. According to some embodiments of the present application, the server can obtain abnormal information from the order information instead of obtaining abnormal information from the device, and can more accurately determine the actual cause of the abnormal order, thereby improving the efficiency of subsequent troubleshooting. There is no need to send maintenance personnel to the site to check and repair the charging pile due to the failure of the charging pile, so it can avoid the waste of resources. In addition, it is possible to automatically isolate and repair the charging piles that have failed, thereby improving the operating efficiency of the charging piles.

Another aspect of the present application relates to a system and method for charging pile fault identification. The system and method can be applied to a server connected to a charging pile (for example, a charging pile operator platform server). The server can obtain the time point when the server receives the current communication data. The server may use the time point as a starting point to determine whether the server receives new communication data within a preset first time threshold. In response to determining that the server does not receive new communication data within the preset first time threshold, the server may determine that the charging pile has an offline failure point. According to some embodiments of the present application, it is possible to automatically identify whether the charging pile has an offline fault point, which not only can detect and prevent the offline fault of the charging pile in time, but also improve the comprehensiveness and accuracy of the charging pile fault identification.

Fig. 1 is a schematic diagram of an exemplary charging monitoring system according to some embodiments of the present application. For example, the charging monitoring system 100 (referred to as the system 100 for short) can be applied to an online-to-offline service platform, such as a transportation service platform. Exemplary transportation services may include taxi call service, agent driving service, express service, car sharing service, bus service, driver rental service, shuttle service, and the like. The system 100 may include a server 110, a network 120, one or more client terminals 130, one or more electric vehicles 140, a storage device 150, and a charging station 170 including one or more charging piles 160. It should be noted that the system 100 is only an example and is not limiting.

In some embodiments, the server 110 may be a single server or a server group. The server group may be centralized or distributed (for example, the server 110 may be a distributed system). In some embodiments, the server 110 may be local or remote. For example, the server 110 may access information and/or data stored in the client terminal 130 and/or the storage device 150 via the network 120. For another example, the server 110 may be directly connected to the client terminal 130, the storage device 150 and/or the charging pile 160 to access the stored information and/or data. In some embodiments, the server 110 may be implemented on a cloud platform. For example only, the cloud platform may include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-layer cloud, etc., or any combination thereof. In some embodiments, the server 110 may be executed on the computing device 300 including one or more components shown in FIG. 3 in the present application. In some embodiments, the server 110 may be a charging pile operator service platform.

In some embodiments, the server 110 may include one or more processing devices 112. The processing device 112 may process information and/or data related to charging requests, charging pile fault identification, and charging pile monitoring to perform one or more functions described in this application. For example, the processing device 112 may obtain information about abnormal orders. The processing device 112 may obtain the identifier corresponding to the abnormal state data in the abnormal order. The processing device 112 may determine the reason for the abnormality of the abnormal order based on the identifier. For another example, the processing device 112 may perform a monitoring operation on the abnormal charging pile. For another example, the processing device 112 may obtain the time point of the current communication data, and the communication data is sent by the charging pile 160. The processing device 112 may use the time point of the current communication data as a starting point to determine whether new communication data is received within a preset first time threshold. The processing device 112 may determine that there is an offline fault point in the charging pile in response to determining that no new communication data is received within the preset first time threshold.

In some embodiments, the processing device 112 may include one or more processing engines (for example, a single-chip processing engine or a multi-chip processing engine). For example only, the processing device 112 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), an application specific instruction processor (ASIP), an image processor (GPU), a physical processor (PPU), a digital signal processor ( DSP), Field Programmable Gate Array (FPGA), Programmable Logic Circuit (PLD), Controller, Microcontroller Unit, Reduced Instruction Set Computer (RISC), Microprocessor, etc. or any combination thereof.

The network 120 may facilitate the exchange of information and/or data. In some embodiments, one or more components in the system 100 (for example, the server 110, the client terminal 130, the storage device 150, and the charging pile 160) may send information and/data to other components in the system 100 through the network 120. For example, the server 110 may obtain a service request (for example, a charging request) from the client terminal 130 or the charging pile 160 via the network 120. For another example, the charging pile 160 may send charging order information or charging status data to the server 110 via the network 120. In some embodiments, the network 120 may be any type of wired or wireless network, etc., or any combination thereof. For example only, the network 120 may include a cable network, a wired network, an optical fiber network, a telecommunications network, an internal network, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), and a metropolitan area network (MAN) , Public Switched Telephone Network (PSTN), Bluetooth network, ZigBee network, Near Field Communication (NFC) network, etc. or any combination thereof. In some embodiments, the network 120 may include one or more network access points. For example, the network 120 may include wired or wireless network access points, such as base stations and/or Internet exchange points 120-1, 120-2, ..., which may be connected to the network through one or more components of the system 100 120 to exchange data and/or information.

In some embodiments, the client terminal 130 may include a mobile device 130-1, a tablet computer 130-2, a laptop computer 130-3, a motor vehicle built-in device 130-4, etc., or any combination thereof. In some embodiments, the client terminal 130 may facilitate communication and/or interaction between the processing device 112 and users associated with the client terminal 130. For example, the client terminal 130 may generate a charging request based on the user's input via the user interface. The processing device 112 may receive a charging request from the client terminal 130. For another example, the processing device 112 may send information related to one or more charging stations and/or charging piles to the client terminal 130 for display to the user.

In some embodiments, the mobile device 130-1 may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, etc., or any combination thereof. In some embodiments, the smart home equipment may include smart lighting equipment, smart electrical appliance control devices, smart monitoring equipment, smart TVs, smart cameras, walkie-talkies, etc., or any combination thereof. In some embodiments, the wearable device may include a smart bracelet, smart footwear, smart glasses, smart helmets, smart watches, smart clothing, smart backpacks, smart accessories, etc., or any combination thereof. In some embodiments, the smart mobile device may include a smart phone, a personal digital assistant (PDA), a gaming device, a navigation device, a point of sale (POS), etc., or any combination thereof. In some embodiments, the virtual reality device and/or the augmented reality device may include a virtual reality helmet, virtual reality glasses, virtual reality goggles, augmented reality helmets, augmented reality glasses, augmented reality goggles, etc., or any combination thereof. For example, the virtual reality device and/or the augmented reality device may include Google Glass, Oculus Rift, HoloLens, GearVR, or the like. In some embodiments, the in-vehicle device 130-4 may include a vehicle-mounted computer or a vehicle-mounted TV. In some embodiments, the client terminal 130 may be a device with positioning technology for locating the location of the service requester and/or the client terminal 130.

The one or more electric vehicles 140 may include one or more electric vehicles (for example, electric vehicles 140-1, electric vehicles 140-2, etc.), one or more electric motorcycles 140-3, one or more electric bicycles 140-4, etc., Or a combination. The electric vehicle 140 may include an identification for distinguishing from other electric vehicles. The identification of the electric vehicle 140 may include vehicle information, such as vehicle type, vehicle brand, vehicle license plate number, vehicle number, etc., or a combination thereof.

The storage device 150 may store data and/or instructions. In some embodiments, the storage device 150 may store data acquired from the client terminal 130. For example, the storage device 150 may store a request for charging the electric vehicle 140 from the client terminal 130. For another example, the storage device 150 may store information related to the electric vehicle 140. For another example, the storage device 150 may store information related to the charging pile 160. For another example, the storage device 150 may store information related to the charging process (for example, charging state data). In some embodiments, the storage device 150 may store data and/or instructions used by the server 110 to execute or use to complete the exemplary methods described in this application. In some embodiments, the storage device 150 may include mass memory, removable memory, volatile read-write memory, read-only memory (ROM), etc., or any combination thereof. Exemplary mass storage devices may include magnetic disks, optical disks, solid state drives, and the like. Exemplary removable storage may include flash drives, floppy disks, optical disks, memory cards, compact disks, magnetic tapes, and the like. An exemplary volatile read-write memory may include random access memory (RAM). Exemplary RAM may include dynamic random access memory (DRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), static random access memory (SRAM), thyristor random access memory (T-RAM), and zero capacitance Random access memory (Z-RAM), etc. Exemplary read-only memory may include mask-type read-only memory (MROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM and digital versatile disk read-only memory, etc. In some embodiments, the storage device 150 may be implemented on a cloud platform. For example only, the cloud platform may include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-layer cloud, etc., or any combination thereof.

In some embodiments, the storage device 150 may be connected to the network 120 to communicate with one or more components in the system 100 (for example, the server 110, the client terminal 130, the charging pile 160, the electric vehicle 140). One or more components in the system 100 can access data and/or instructions stored in the storage device 150 via the network 120. In some embodiments, the storage device 150 may be directly connected to or communicate with one or more components in the system 100 (for example, the server 110, the client terminal 130, the charging pile 160, the electric vehicle 140). In some embodiments, the storage device 150 may be a part of the server 110, the client terminal 130, the charging pile 160, or the electric vehicle 140.

The charging station 170 may include one or more charging posts 160. The charging post 160 is configured to charge an electric vehicle (for example, the electric vehicle 140). In some embodiments, the charging post 160 may include a power supply device that provides power, a charging interface connected to an electric vehicle, a memory for storing data generated during the charging process, and a controller (for example, the controller 400 shown in FIG. 4). ), one or more sensors, etc. or any combination thereof. The charging pile 160 may further include one or more operable components, for example, a pile body, a charging gun, a cabinet door, an emergency stop button, etc., or any combination thereof.

In some embodiments, the controller may include an acquisition module (for example, the acquisition module 410 shown in FIG. 4), a generation module (for example, the generation module 420 shown in FIG. 4), and a determination module (for example, the acquisition module 410 shown in FIG. 4). The determination module 430) and the control module (for example, the control module 440 shown in FIG. 4) and so on. More description of the controller can be found elsewhere in this application (for example, Figure 4 and its description).

The sensor is used to detect the actual status data of the charging pile. The sensor may include a temperature sensor, a current sensor, a voltage sensor, a pressure sensor, etc., or any combination thereof. The temperature sensor is used to detect the real-time temperature of the components of the charging pile (for example, the pile body). The current sensor is used to detect the real-time current value of the component (for example, the charging gun) flowing through the charging pile. The voltage sensor is used to detect the real-time voltage value of the components of the charging pile (for example, the tip of the charging gun). The pressure sensor is used to detect the pressure value between the components of the charging pile (for example, between the tip of the charging gun and the body of the charging pile).

The above description of the system 100 is intended to be illustrative, and not to limit the scope of the application. For those skilled in the art, many alternatives, modifications and changes will be obvious. The features, structures, methods, and other features of the exemplary embodiments described in this application may be combined in various ways to obtain additional and/or alternative exemplary embodiments. However, these changes and modifications do not depart from the scope of this application. For example, the client terminal 130 may be omitted, and the user may directly initiate a charging request on the charging pile 160.

Fig. 2 is a schematic diagram of exemplary hardware and/or software components of an exemplary mobile device on which a client terminal can be implemented according to some embodiments of the present application. The mobile device 200 may include one or more central processing units (CPU) 240, one or more graphics processing units (GPU) 230, a display 220, a memory 260, a communication unit 210, a storage unit 290, and one or more input/output (I /O) Equipment 250. In addition, the mobile device 200 may also include, but is not limited to, any other suitable components of a system bus or a controller (not shown in FIG. 2). As shown in FIG. 2, the mobile operating system 270 (for example, IOS, Android, Windows Phone, etc.) and one or more application programs 280 may be loaded from the storage unit 290 into the memory 260 so as to be executed by the CPU 240. The application program 280 may include a browser or other mobile application programs for receiving and processing charging-related information input by the user in the mobile device 200. The user can obtain one or more charging-related information through the system I/O device 250, and provide the information to the server 110 and/or other modules or units of the system 100.

Figure 3 is a schematic diagram of exemplary hardware and software components of an exemplary computing device shown in accordance with some implementations of the present application. The functions of the server 110, the client terminal 130, or the charging pile 160 can be implemented on the computing device 300. The computing device 300 may be configured to perform one or more functions of the server 110, the client terminal 130, and the charging pile 160 disclosed in this application. For example, the processing device 112 may be implemented on the computing device 300 and configured to perform the functions of the processing device 112 disclosed in this application.

The computing device 300 may be a general-purpose computer or a special-purpose computer, both of which may be used to implement the system 100 of the present application. The computing device 300 can be used to implement any component of the system 100 as described in this application. For example, the processing device 112 may be implemented on the computing device 300 through its hardware, software programs, firmware, or a combination thereof. For convenience, only one computer is shown in the figure, but the computer functions related to the charging service described in this application can be implemented in a distributed manner on multiple similar platforms to distribute the processing load.

For example, the computing device 300 may include a communication port 350, which is connected to and/or from the network to implement data communication. The computing device 300 may also include one or more processors 320 in the form of processors for executing program instructions. An exemplary computer platform may include an internal communication bus 310, different types of program memory and data memory (for example, a magnetic disk 370, read only memory (ROM) 330, or random access memory (RAM) 340), processed by a computer, and/or Transmission of various data files. The exemplary computer platform also includes program instructions stored in the ROM 330, RAM 340, and/or other forms of non-transitory storage media to be executed by the processor 320. The method and/or process of the present application can be implemented in the form of program instructions. The computing device 300 may also include an input/output device 360, which may support input/output between the computer and other components. The computing device 300 may also receive programming and data through network communication.

The computing device 300 may also include a hard disk controller in communication with a hard disk, a keypad/keyboard controller in communication with a keypad/keyboard, a serial interface controller in communication with a serial interface device, and a parallel interface control in communication with a parallel interface device. A display controller, a display controller that communicates with the display, etc., or any combination thereof.

For illustration only, only one CPU and/or processor is exemplarily described in the computing device 300. However, it should be noted that the computing device 300 in this application may include multiple CPUs and/or processors, so the operations and/or methods implemented by one CPU and/or processor described in this application may also be implemented by multiple CPUs and/or processors. The CPUs and/or processors are implemented jointly or independently. For example, if in this application, the CPU and/or processor of the computing device 300 performs operation A and operation B, it should be understood that operation A and operation B can also be processed by two different CPUs and/or operations in the computing device 300. The processors execute jointly or independently (for example, the first processor executes operation A, the second processor executes operation B, or the first and second processors jointly execute operation A and operation B).

Fig. 4 is an exemplary module diagram of a charging pile according to some embodiments of the present application. The charging pile 160 may include a controller 400, and the controller 400 may include an acquisition module 410, a generation module 420, a determination module 430, and a control module 440.

The obtaining module 410 can obtain data or information. The acquisition module 410 may acquire data/signals from one or more components of the system 100 (for example, the client terminal 130, the electric vehicle 140, the storage device 150) or an external device (for example, a cloud database). For example only, the acquired data/signals may include charging requests, charging status data, etc., or any combination thereof. In some embodiments, the acquiring module 410 may acquire the charging state data during the current charging operation of the vehicle by the charging post. More descriptions on obtaining charging state data can be found elsewhere in this application (for example, Figure 6 and related descriptions).

The generating module 420 may generate data or information. In some embodiments, the generation module 420 may generate an order based on the charging request. For example, in response to obtaining a charging request, the generating module 420 may generate a charging order for the charging request. More descriptions on generating charging orders can be found elsewhere in this application (for example, Figure 6 and related descriptions).

The determination module 430 may determine data or information. In some embodiments, the determination module 430 may determine whether the charging state data includes abnormal state data. The abnormal state data may include abnormal state data of the operable parts of the charging pile, abnormal interaction data between the charging pile and the vehicle, and the like. The abnormal state data of the operable parts of the charging pile may include abnormally pulling out the charging gun, abnormally opening the charging cabinet door, abnormally pressing the emergency stop button, and so on. The abnormal interaction data between the charging pile and the vehicle may include abnormal communication connection between the charging pile and the charged vehicle (for example, connection timeout, connection failure), abnormal current battery data of the vehicle fed back to the charging pile by the charged vehicle, and the like. In some embodiments, in response to determining that the charging state data includes abnormal state data, the determining module 430 may determine that the order is an abnormal order, and generate an identifier corresponding to the abnormal state data for the abnormal order. More descriptions on determining whether abnormal state data is included in the charging state data and generating an identifier corresponding to the abnormal state data on the abnormal order can be found elsewhere in this application (for example, FIG. 6 and related descriptions).

The control module 440 may send data or information. In some embodiments, the control module 440 may send the abnormal order to the server connected to the charging pile. For example, the control module 440 may send the abnormal order and the identifier to the server 110 connected to the charging pile 160.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. For example, the generating module 420 and the determining module 430 may be integrated into one module.

Fig. 5 is an exemplary block diagram of a processing device according to some embodiments of the present application. The processing device 112 may include an acquisition module 510, a determination module 520, and a control module 530.

The obtaining module 510 can obtain data or information. The acquisition module 510 may acquire data/signals from one or more components of the system 100 (for example, the client terminal 130, the electric vehicle 140, the storage device 150, the charging pile 160) or an external device (for example, a cloud database). For example, the obtaining module 510 may obtain information about abnormal orders, which may reflect abnormal state data during the charging operation of the charging pile, and the information of abnormal orders may include an identifier corresponding to the abnormal state data. For another example, the acquiring module 510 can acquire information about an order and analyze the information about the order. For another example, the acquiring module 510 may acquire the time point when the server receives the current communication data, and the communication data is sent by the charging pile. For another example, the obtaining module 510 may obtain the historical abnormal order quantity and the total historical order quantity of the charging pile. For another example, the acquiring module 510 may acquire status data of the charging pile. For another example, the obtaining module 510 may obtain the proportion of the charging piles determined to be faulty in the charging station to the total number of charging piles.

The determination module 520 may determine data or information. For example, the determining module 520 may determine the abnormal reason of the abnormal order according to the identifier of the abnormal order. For another example, if the order is an abnormal order, and the abnormal reason of the abnormal order is a charging pile failure, the determining module 520 may determine that the charging pile corresponding to the abnormal order is an abnormal charging pile. For another example, if multiple consecutive orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is the failure of the charging pile, the determining module 520 may determine that the charging pile is an abnormal charging pile. For another example, the determining module 520 may use the time point as a starting point to determine whether the server receives new communication data within a preset first time threshold. For another example, the determining module 520 may, in response to determining that the server does not receive new communication data within a preset first time threshold, determine that the charging pile has an offline fault point. For another example, the determining module 520 may generate an order abnormality identifier for the abnormal order in response to determining that the server does not receive new communication data within the preset first time threshold and the charging status data includes order abnormality information. For another example, the determining module 520 may determine whether the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the proportion threshold. In response to determining that the ratio of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the ratio threshold, the determination module 520 may determine that the charging pile is faulty. In response to determining that the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders does not exceed the proportion threshold, the determining module 520 may determine that the charging pile is not faulty. For another example, the determining module 520 may determine whether the status data of the charging pile is within a preset range. In response to determining that the state data of the charging pile is not within the preset range, the determining module 520 may determine that the charging pile has a fault. For another example, the determining module 520 may determine whether the proportion of the charging piles determined to be faulty in the charging station to the total number of charging piles exceeds a threshold. In response to determining that the ratio exceeds the threshold, the determining module 520 may acquire the site attribute of the charging station and the second terminal attribute corresponding to the site attribute.

The control module 530 can send data or information. In some embodiments, the control module 530 can perform monitoring operations on abnormal charging posts. For another example, the control module 530 may perform an isolation operation on the abnormal charging pile. For another example, the control module 530 may perform repair operations on the abnormal charging pile. In some embodiments, after performing the repair operation, the control module 530 may set the abnormal charging pile as a normal charging pile. In some embodiments, the control module 530 may send reminder information to the terminal of the processing personnel. For example, the control module 530 may send a maintenance work order regarding the abnormal charging pile to the terminal of the corresponding processing personnel. For another example, the control module 530 may send fault reminding information to the first terminal according to the attributes of the first terminal, and the fault reminding information includes the device attributes of the charging pile. For another example, the control module 530 may send alarm information to the second terminal according to the attributes of the second terminal, where the alarm information includes the site attributes of the charging station.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. For example, the acquiring module 510 and the determining module 520 may be integrated into one module.

FIG. 6 is a flowchart of an exemplary process 600 for identifying a fault of a charging pile according to some embodiments of the present application. The process 600 can be executed by the system 100. In some embodiments, one or more operations of the process 600 shown in FIG. 6 may be implemented in the system 100 shown in FIG. 1. For example, the process 600 shown in FIG. 6 may be stored in a storage device in the form of instructions, and called and/or executed by the charging pile. The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 600 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 6 and described below is not restrictive.

In 610, in response to obtaining a charging request, an order is generated for the charging request. This step may be performed by the charging pile 160 (for example, the generating module 420).

In some embodiments, the charging request may be a service demand initiated by the user based on insufficient or lack of power of the electric vehicle. The charging request may include vehicle information related to the electric vehicle to be charged. The vehicle information related to the electric vehicle may include the license plate number of the electric vehicle, the model of the electric vehicle, the current power of the electric vehicle, the model of the charger of the electric vehicle, etc., or any combination thereof.

In some embodiments, a user (for example, a driver) may initiate a charging request through a client terminal (for example, the client terminal 130), and the charging pile may receive the charging request from the client terminal. For example, the user can initiate a charging request through the user interface (for example, an application) of the client terminal. For another example, the user can initiate a charging request by scanning the charging code of the charging pile head by using the client terminal. In some embodiments, the user can directly initiate a charging request through the charging pile. For example, when an electric vehicle is connected to a charging pile, the charging pile can automatically generate a charging request. For another example, the charging pile may include an operation interface, and the user may initiate a charging request through the operation interface of the charging pile.

In some embodiments, the charging post may generate a charging order based on the charging request. Alternatively, the charging request may be sent to a server (for example, the processing device 112), and the server may send a charging start signal to the charging pile according to the user's charging request, and at the same time allocate a charging order for the current charging operation. Order information can include user information (for example, identity information, user history charging request, user history charging record, user current geographic location), electric vehicle information (for example, vehicle model, license plate number, historical charging record, full charge required Power, current power), charging station information (for example, charging station number, charging status data, charging station charging power, charging station cumulative charging power, charging station historical maintenance records), etc., or any combination thereof. In some embodiments, the order information may include information reserved when the user registers (for example, user terminal information, information about charging vehicles) or information obtained in real time (for example, information about charging piles).

In 620, in the process of performing the current charging operation on the vehicle, the charging state data is acquired. This step may be performed by the charging pile 160 (for example, the acquisition module 410).

In some embodiments, during the charging operation of the vehicle by the charging pile, the charging pile may obtain charging state data. The charging status data can include the status data of the charging pile (for example, the status data of the operable parts of the charging pile), the interaction data between the charging pile and the vehicle, the reminder signal sent when the charging is started or ended, the charging process and the charging amount calculation Related signals, billing data sent after charging, etc. or any combination thereof. As used in this application, operable components may refer to components that can be manipulated by humans. For example, the operable components of the charging pile may include a pile body, a charging gun, a charging pile cabinet door, and a charging pile emergency stop button. The state data of the operable parts of the charging pile may include the temperature, current value, voltage value of the operable parts of the charging pile, the real-time output power of the charging pile, the accumulated charging time of the charging pile, and the accumulated charging amount of the charging pile. The interaction data between the charging pile and the vehicle may include the communication connection state between the charging pile and the charged vehicle, the current power data of the vehicle fed back to the charging pile by the charged vehicle, and the like.

In some embodiments, the charging pile can use sensors, communication modules, etc. installed inside the charging pile to detect charging status data in real time, perform data communication with the charged vehicle, and perform data communication with the server. For example, the sensors of the charging post may include a first temperature sensor, a second temperature sensor, a current sensor, a voltage sensor, a pressure sensor, etc., or any combination thereof. The first temperature sensor may be used to detect the real-time temperature value of the charging pile body as the actual state data of the pile body and send it to the controller of the charging pile. The second temperature sensor can be used to detect the real-time temperature value of the charging gun and send it to the controller. The current sensor can be used to detect the real-time current value flowing through the charging gun and send it to the controller. The voltage sensor can be used to detect the real-time voltage value at the tip of the charging gun and send it to the controller. The pressure sensor can be used to detect the pressure value between the tip of the charging gun and the body of the charging pile and send it to the controller.

In 630, it is determined whether the charging state data includes abnormal state data. This step may be performed by the charging pile 160 (for example, the determination module 430).

In the process of performing the charging operation, charging piles, users and vehicles being charged are involved in charging. Abnormal charging behaviors of any party (for example, abnormal user operation, charging pile failure, and charging vehicle failure) may cause abnormal status data The emergence of. The abnormal state data may include abnormal state data of the operable parts of the charging pile, abnormal interaction data between the charging pile and the vehicle, and the like. The abnormal state data of the operable parts of the charging pile may include abnormally pulling out the charging gun, abnormally opening the charging cabinet door, abnormally pressing the emergency stop button, and so on. The abnormal interaction data between the charging pile and the vehicle may include abnormal communication connection between the charging pile and the charged vehicle (for example, connection timeout, connection failure), abnormal current battery data of the vehicle fed back to the charging pile by the charged vehicle, and the like.

In some embodiments, the charging pile (for example, the storage device of the charging pile) may pre-store the standard range of the charging state data of the charging pile (for example, the standard state data table). The standard range of the charging state data of the charging pile refers to the standard range of the charging state data of the charging pile in the normal working state. For example, the standard state data table may include the standard range of the temperature of the pile body, the standard range of the current of the charging gun tip, the standard range of the voltage of the charging gun tip, and so on. After the controller of the charging pile receives the actual status data sent by the sensor, it can compare and inspect the actual status data sent by the sensor according to the standard status data recorded in the standard status data table, so as to determine whether the corresponding component of the sensor is faulty.

For example, the charging pile may include a sensor that detects the current of the charging gun. Under normal circumstances, after responding to the charging signal, if the user normally inserts the charging pile into the charged vehicle and the connection is successful, the current value of the charging gun will change. At this time, if the sensor detects that the current value does not change as normal, it can be considered that the user has not successfully connected the charging gun. During the charging process, the current of the charging gun also changes regularly. If the current value of the charging gun suddenly changes to zero during charging, it can be considered that the charging gun has disconnected from the vehicle, and the charging gun is considered to be abnormally pulled out. . Based on a similar principle, the corresponding sensor in the charging pile can detect whether the charging cabinet door is abnormally opened, whether the emergency stop button is abnormally pressed, and so on.

For another example, the charging pile can obtain the response time of the charged vehicle. If the response time of the charged vehicle exceeds a set threshold, it is considered that the communication connection between the charging pile and the charged vehicle is abnormal. In some embodiments, the response time of the charged vehicle is obtained by: sending a charging signal to the charged vehicle during the current charging operation; acquiring the response signal fed back by the charged vehicle according to the charging signal; The interval between the receiving time of the response signal and the sending time of the charging signal is the response time of the charged vehicle.

During the charging process, the charging pile needs to communicate with the charged vehicle to obtain battery information of the charged vehicle, so as to adjust the charging speed, output power, etc. according to the battery information. However, if the charging pile cannot successfully communicate with the vehicle at this time, and the vehicle battery data cannot be obtained, the order may not continue, and an abnormal order may occur. Similarly, the authentication result, relay voltage, communication function of the battery management system, the insulation of the power battery and the connector function of the charged vehicle can also be tested during the charging process.

In 640, in response to determining that the charging state data includes the abnormal state data, it is determined that the order is an abnormal order, and an identifier corresponding to the abnormal state data is generated for the abnormal order. This step may be performed by the charging pile 160 (for example, the determination module 430).

In some embodiments, the abnormal order may refer to an order in which the charging operation is not normally completed due to abnormal status data. For example, if the charging pile cannot be connected to the vehicle due to damage to the charging gun connection device, the order cannot be completed normally. In some embodiments, an abnormal order may also refer to an order in which the charging operation can still be completed normally although the charging state data includes abnormal state data. For example, during the charging process of the vehicle, the communication between the charging pile and the vehicle is interrupted for a period of time, and then the communication is resumed. At this time, the charging operation can still be completed.

In some embodiments, order abnormalities caused by different types of charging status data abnormalities are assigned different identifiers. For example, in response to determining that the state data of the operable component of the charging pile is an abnormal state, a first identifier is generated for the abnormal order. That is, the first identifier indicates that the order is abnormal due to the abnormality of the operable component. For another example, in response to determining that the interaction data is in an abnormal state, a second identifier is generated for the abnormal order. That is, the second identifier indicates that the order is abnormal due to abnormal communication between the charging pile and the charged vehicle. The identifier is used to identify the type of abnormal order. In some embodiments, the identifier may be Arabic numerals, letters, characters, codes, etc. or any combination thereof. For example, the identifier can be the letters A, B, C, etc. For another example, the identifier may be fault type 1, fault type 2, fault type 3, and so on.

In some embodiments, the charging pile may obtain the mapping relationship between the abnormal state data and the identifier, and determine the identifier of the abnormal order according to the mapping relationship and the abnormal state data. The mapping relationship between the abnormal state data and the identifier may be determined by a component of the system 100 (for example, the processing device 112) and stored in the storage device (for example, the storage device 150) of the system 100, and the charging pile may be retrieved from the storage device. To obtain the mapping relationship. For example, the mapping relationship may be defined and issued by the charging pile server, and determining the identifier according to the mapping relationship issued by the server can provide a data basis for accurately locating the cause of the abnormality.

In some embodiments, one abnormal order may correspond to multiple identifiers. For example, if the abnormal status data corresponding to a certain order includes the communication connection timeout between the charging pile and the charged vehicle, the charging gun is abnormally pulled out, and the emergency stop button is abnormally pressed, and the state data of the operable parts of the corresponding charging pile is The identifier of the abnormal state is set to A, and the identifier corresponding to the abnormal state of the interaction data between the charging pile and the vehicle is set to B, the charging pile can determine that the order is an abnormal order, and generate an identifier A+B for the abnormal order .

According to some embodiments of the present application, an identifier can be assigned to each abnormal order information, and different identifiers can represent different abnormal reasons. Therefore, the server can quickly locate the abnormal reason according to the identifier when determining the abnormal order.

In 650, the abnormal order is sent to a server connected to the charging pile. This step may be performed by the charging pile 160 (for example, the control module 440).

In some embodiments, the charging pile may send the abnormal order including the identifier to a server (for example, the server 110) connected to the charging pile via a network (for example, the network 120). After the server obtains the abnormal order, it can determine the reason for the abnormal order based on the identifier. More descriptions on determining the abnormal cause of abnormal orders can be found elsewhere in this application (for example, Figure 7 and related descriptions).

According to some embodiments of the present application, during the process of charging the vehicle by the charging pile, the reason for the abnormal charging order can be determined according to the charging state data, and different identifiers are configured for the abnormal order caused by different reasons. Therefore, when the server receives the abnormal order information, it can determine the reason for the abnormal order according to the identifier. Through some of the embodiments of the present application, the actual cause of the order abnormality can be determined, thereby improving the efficiency of subsequent troubleshooting, and there is no need to send maintenance personnel to the site to inspect and repair the charging pile for reasons that are not caused by the charging pile failure. Therefore, waste of resources can be avoided.

It should be noted that the above is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. For example, operation 620 and operation 630 may be combined into one operation. For another example, operation 610 may be omitted, and the server may generate a charging order based on the charging request, and send the charging order to the charging pile.

FIG. 7 is a flowchart of an exemplary process 700 for determining the abnormal cause of an abnormal order according to some embodiments of the present application. The process 700 can be executed by the system 100. In some embodiments, one or more operations of the process 700 shown in FIG. 7 may be implemented in the system 100 shown in FIG. 1. For example, the process 700 shown in FIG. 7 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 700 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 7 and described below is not restrictive.

In 710, the information of the abnormal order is obtained. The information of the abnormal order reflects that there is abnormal state data during the charging operation of the charging pile, and the information of the abnormal order includes an identifier corresponding to the abnormal state data. This step may be executed by the processing device 112 (for example, the acquisition module 510).

The processing device 112 may communicate with a charging pile (for example, the charging pile 160), so as to obtain information about abnormal orders from the charging pile. In some embodiments, once the charging pile determines the abnormal order, the charging pile may send the abnormal order information to the processing device 112 via the network 120 in real time. In some embodiments, the processing device 112 may periodically (for example, daily, weekly, monthly) obtain information about abnormal orders from the charging pile. In some embodiments, when the abnormal order determined by the charging pile reaches the preset threshold, the processing device 112 obtains the information of the abnormal order from the charging pile. In some embodiments, the charging pile may send the information of the abnormal order to the storage device (for example, the storage device 150) of the system 100, and the processing device 112 may obtain the information of the abnormal order from the storage device.

The abnormal order information can reflect the situation of abnormal state data when the charging pile is performing the charging operation. For example, the information of the abnormal order may include an identifier corresponding to the abnormal state data, that is, the identifier may indicate the type of the abnormal state. More descriptions of abnormal state data and identifiers can be found elsewhere in this application (for example, Figure 6 and related descriptions).

In 720, the abnormal cause of the abnormal order is determined according to the identifier. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, according to the parties involved in the charging process, the abnormal reasons for abnormal orders can be divided into three categories, including but not limited to the following: charging pile failure (pile responsibility), vehicle failure (car responsibility), and abnormal operation ( Human responsibility). Among them, charging pile failure (pile responsibility) can be understood as an order abnormality caused by charging pile failure, such as network module failure, charging gun connection device damage, cabinet door cannot be closed normally, emergency stop button failure, etc. Abnormal operation (personal responsibility) can be understood as an order abnormality caused by incorrect operation by the user, such as charging without inserting the gun, pulling the gun during charging, opening the cabinet door not as required, pressing the emergency stop button in violation of regulations, etc. Vehicle failure (car liability) can be understood as an order abnormality caused by the interaction between the vehicle and the pile, for example, the vehicle does not respond to the battery information query of the charging pile in time, and the charging information reported by the charging vehicle is inaccurate.

In some embodiments, the charging pile assigns identifiers to abnormal orders. Different identifiers can indicate different abnormal state data types. According to different abnormal state data types, it can be determined whether it is caused by charging pile failure, vehicle failure, or improper operation. Abnormal orders. Specifically, the processing device 112 may obtain charging pile information corresponding to the abnormal order. The charging pile corresponding to the abnormal order refers to the charging pile that generates the abnormal order, that is, the charging pile that charges the vehicle in the abnormal order. For example, the processing device may extract charging pile information (for example, the geographic location of the charging pile, the number of the charging pile) from the information of the abnormal order. Then, the processing device 112 may obtain the information of the historical abnormal order corresponding to the charging pile information in the historical time period, and obtain the historical identifier in the information of the historical abnormal order. The historical time period may be a default value stored in a storage device (for example, the storage device 150). Additionally or alternatively, the historical time period may be manually set according to different situations or determined by one or more components of the system 100. For example, the historical time period may be in the last week, in the last month, in the last three months, and so on. For example, the processing device may obtain information about all historical abnormal orders generated by charging piles corresponding to abnormal orders in the last week, and extract historical identifiers in the historical abnormal order information. Further, the processing device 112 may determine the abnormal reason of the abnormal order according to the proportion of the identifier (corresponding to the current abnormal state data) in the historical identifier.

In some embodiments, the identifier is a first identifier, and the first identifier may indicate that the state data of the operable component of the charging pile is an abnormal state. Such reasons may be improper operation by the user, such as unsuccessful connection of the charging gun, unplugging the gun during charging, failing to open the cabinet door according to regulations, pressing the emergency stop button in violation of regulations, etc., or the charging pile itself malfunctions, for example, the terminal of the charging gun is loose As a result, the normal connection cannot be made, the cabinet door cannot be closed normally, and the emergency stop button malfunctions. If the charging pile itself fails, then the order abnormality caused by this type of reason should account for a large proportion (for example, close to or even 100%) in the historical period of time, and if it is improper human operation, the order abnormality caused by this type of reason It should be sporadic and its proportion should be small. Therefore, it can be judged whether the charging pile is malfunctioning or man-made abnormal operation according to the proportion of the abnormal reason in the historical order.

Correspondingly, the processing device 112 may determine whether the proportion of the first identifier in the historical identifier is greater than a threshold. The threshold may be a default parameter stored in a storage device (for example, the storage device 150). Additionally or alternatively, the threshold may be manually set according to different situations or determined by one or more components of the system 100. For example, the threshold can be set to 90%. In response to determining that the proportion of the first identifier in the historical identifier is greater than the threshold, it is determined that the cause of the abnormality is a failure of the charging pile. In response to determining that the proportion of the first identifier in the historical identifier is less than the threshold, it is determined that the cause of the abnormality is an abnormal operation.

For example only, suppose that the identifier of an abnormal order acquired by the processing device 112 is the first identifier, the charging pile corresponding to the abnormal order is the No. 1 charging pile, and the No. 1 charging pile extracted by the processing device 112 was generated in the past week The historical abnormal order information is: 8 times that the charging pile cabinet door is abnormally closed, 10 times that the charging gun is abnormally pulled out, and 2 times that the network connection fails. Accordingly, the historical identifier in the historical abnormal order information obtained by the processing device 112 may be: With 18 first identifiers and 2 second identifiers, the processing device 112 determines that the proportion of the first identifier in the historical identifiers is 90% (18/20=90%). Assuming that the threshold is set to 85%, the processing device 112 can determine that the abnormal cause of the abnormal order is the failure of the charging pile.

In some embodiments, the identifier is a second identifier, and the second identifier indicates that the interaction data between the charging post and the vehicle being charged is in an abnormal state. This type of reason may be a malfunction of the charging pile or a malfunction of the vehicle being charged. If the charging pile itself fails, the order abnormality caused by this type of reason should account for a large proportion (for example, close to or even 100%) in the historical time period, and if the charged vehicle fails, the order caused by this type of reason The abnormality should be sporadic and its proportion should be small. Therefore, it can be judged whether the charging pile is faulty or the vehicle is faulty according to the proportion of the abnormal reason in the historical order.

Correspondingly, the processing device 112 can determine whether the proportion of the second identifier in the historical identifier is greater than a threshold. In response to determining that the proportion of the second identifier in the historical identifier is greater than the threshold, it is determined that the cause of the abnormality is a failure of the charging pile. In response to determining that the proportion of the second identifier in the historical identifier is less than the threshold, it is determined that the cause of the abnormality is a vehicle failure.

According to some embodiments of the present application, after the server receives the abnormal order information reported by the charging pile, it automatically uses the charging station, the operator, etc., according to the predefined identifier according to a certain historical time period (for example, one day, one week). The aggregation algorithm performs statistical analysis on the abnormality of the order to determine the cause of the abnormality.

In some embodiments, the processing device 112 may generate a mapping relationship between the abnormal state data and the identifier, and send the mapping relationship to the charging pile. This can ensure that the identifier in the abnormal order information reported by the charging pile and the identifier defined by the platform server have a unified standard.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. In some embodiments, the process 700 may further include generating a mapping relationship between the reason for the abnormality and the processing personnel, and sending the reason for the abnormality to the terminal of the corresponding processing personnel. For example, the processing device 112 may determine the terminal corresponding to the reason for the abnormality according to the plan information, and send the reason for the abnormality to the terminal. The plan information may record the cause of the abnormality, the corresponding relationship between the processing personnel and the terminals of the processing personnel. For example only, the processing device 112 may send the reason for the abnormality to the processing personnel via SMS according to the mobile phone number reserved by the processing personnel. In other words, the server can take automated message push measures for abnormal reasons to promote follow-up and resolution by relevant responsible parties, thereby reducing the order abnormality rate.

In some embodiments, if the abnormal reason for the abnormal order is the failure of the charging pile. The server can push the charging pile fault to the charging pile maintenance personnel, which can locate the fault to the specific charging pile or even the charging gun, and help the maintenance personnel to quickly repair the charging pile. If, after statistics, it is found that the charging pile of a certain charging station frequently generates abnormal orders, the server can push the charging pile fault of the charging station to the person in charge of the charging station. Furthermore, if after statistics, it is found that a certain brand or even certain batches of charging piles frequently generate abnormal orders, then it can be suspected that the modules used by the charging piles of this batch are defective, and the server can automatically generate an alarm message, such as connecting the charging piles. The fault is reported to the person in charge of the charging pile brand, and they are asked to help troubleshoot the problem.

In some embodiments, if the abnormal reason for the abnormal order is abnormal operation, the server may push the abnormal reason to the user to help the user standardize the operation. Since operations that do not follow the prescribed procedures will cause great security risks, effective methods must be adopted to restrain users. For example, for unauthorized removal of a gun during charging, the server can push the cause of the abnormality to the user through the APP, and at the same time push the safety operation specification, or disable the account for 1 day and require the user to sign a safety operation manual, etc., to help users form a good safety concept and reduce Security Risk.

In some embodiments, if the abnormal cause of the abnormal order is a vehicle failure (for example, the abnormality caused by the vehicle communication module not responding to the request of the charging pile in time), the server may push the abnormal cause to the user to remind the user that the vehicle may be malfunctioning . For example, through aggregation analysis, once it is found that this situation frequently occurs in a user's vehicle, it can basically be concluded that the vehicle's communication module is malfunctioning. In order not to affect the user's use and ensure the user's safety, the server can automatically notify the user through APP notifications, text messages, etc., so that the user can repair the vehicle.

In some embodiments, the server may implement a monitoring alarm mechanism when counting the reasons for the abnormality of the order. For example, the maintenance personnel of charging piles can subscribe to the statistics of abnormal orders of specific piles according to their own maintenance area. The server needs to provide such message subscription channels, such as e-mail, IM messages, etc., through this way to form a unified This kind of active problem discovery and resolution mechanism breaks the previous dilemma of passively waiting to report problems, thereby improving the availability of equipment. At the same time, the person in charge of the charging station can also have an overall understanding of the situation of the station equipment he is responsible for by subscribing to the order summary of the charging station.

Through the above-mentioned abnormal statistics and notification mechanism, the situation of the responsible party can be clarified, and the root cause of the abnormality can be located automatically, quickly and accurately, and the relevant personnel can be promoted to implement improvement plans, which can greatly reduce the order abnormality rate and additionally improve the safety of user operations.

FIG. 8 is a flowchart of an exemplary process 800 for monitoring charging piles according to some embodiments of the present application. The process 800 can be executed by the system 100. In some embodiments, one or more operations of the process 800 shown in FIG. 8 may be implemented in the system 100 shown in FIG. 1. For example, the process 800 shown in FIG. 8 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 800 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 8 and described below is not restrictive.

In 810, obtain the information of the order and analyze the information of the order. This step may be executed by the processing device 112 (for example, the acquisition module 510).

In some embodiments, the charging pile may communicate with a server (for example, the processing device 112), upload a charging order to the server (for example, the processing device 112), and report the reason for stopping charging. For example, when a user uses a charging pile to charge, he can scan a code through a client terminal (for example, a mobile phone) to request charging, and in response to the charging request, the charging pile starts to charge the vehicle. After the charging is completed, the charging pile can communicate with the server for orders, and the charging pile uploads the charging order to the server and reports the reason for stopping charging. In some embodiments, the processing device 112 may obtain order information from the charging pile via the network 120 in real time. In some embodiments, the processing device 112 may periodically (for example, daily, weekly, monthly) obtain order information from the charging station through the network 120.

Reasons for stopping charging may include normal stopping and abnormal stopping. The normal stop of the charging order may be caused by the end of charging, insufficient user account fees, and other reasons. The abnormal stop of the charging order may be caused by charging pile failure, vehicle failure, abnormal operation, etc. If the reason for stopping charging is normal stopping, the corresponding order may be determined to be a normal order, and the processing device 112 may no longer analyze it. If the reason for stopping charging is an abnormal stop, the corresponding order may be determined to be an abnormal order, and the processing device 112 may further analyze the information of the abnormal order to determine the abnormal cause of the abnormal order. The description of determining the abnormal cause of the abnormal order can be found elsewhere in this application (for example, operation 720 and its description in FIG. 7).

In 820, if the order is an abnormal order, and the reason for the abnormality of the abnormal order is that the charging pile fails, it is determined that the charging pile corresponding to the abnormal order is the abnormal charging pile. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, if within a historical time period (for example, in the last day, in the last week, in the last month, in the last three months), the number of abnormally stopped charging orders associated with the charging pile The proportion of all orders related to the charging pile is greater than the proportion threshold, and the reason for the abnormal stop is the failure of the charging pile, then it is determined that the charging pile is an abnormal charging pile. In some embodiments, if within a historical time period (for example, in the last day, in the last week, in the last month, in the last three months), the number of abnormally stopped charging orders associated with the charging pile If it is greater than the number threshold, and the reason for the abnormal stop is the failure of the charging pile, it is determined that the charging pile is an abnormal charging pile. In some embodiments, if the multiple continuous charging orders associated with the charging pile are all abnormally stopped, and the reason for the abnormal stop is all charging pile failure, it is determined that the charging pile is an abnormal charging pile. More descriptions on determining abnormal charging posts can be found elsewhere in this application (for example, operation 920 and its description in FIG. 9).

Step 830: Perform a monitoring operation on the abnormal charging pile. This step may be performed by the processing device 112 (for example, the control module 530).

In some embodiments, the monitoring operations may include isolation operations and repair operations. More descriptions on the monitoring operation of the charging pile can be found elsewhere in this application (for example, as shown in Figure 9 and its description).

According to some embodiments of the present application, only the actual charging product order is analyzed. If the charging order is abnormal, then the charging pile is abnormal. If the actual charging is OK, it means that there is no problem with the charging pile at this time. Since the function of the charging pile is to charge, whether the charging order is abnormal can fully indicate whether the charging function of the charging pile is normal. Therefore, by analyzing the charging order generated by the charging pile during the actual charging process, the failure of the charging pile can be found in a timely and accurate manner. According to some embodiments of the present application, by analyzing the order generated during charging of the charging pile, the order analysis result is used as the basis for fault judgment, so that the fault detection of the charging pile is more accurate and timely.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. In some embodiments, the charging pile can determine the abnormal order according to the charging status data, and send the abnormal order to the server, as shown in Figure 6 and its related description; after the server receives the abnormal order, if the abnormal reason for the abnormal order is determined to be the charging pile failure , It can be determined that the charging pile corresponding to the abnormal order is an abnormal charging pile, and the monitoring operation of the abnormal charging pile is performed, as shown in Fig. 8 and related descriptions.

FIG. 9 is a flowchart of an exemplary process 900 for monitoring charging piles according to some embodiments of the present application. The process 900 may be executed by the system 100. In some embodiments, one or more operations of the process 900 shown in FIG. 9 may be implemented in the system 100 shown in FIG. 1. For example, the process 900 shown in FIG. 9 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 900 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 9 and described below is not restrictive.

In 910, obtain the order information from the charging pile and analyze the order information. This step may be executed by the processing device 112 (for example, the acquisition module 510).

The description about obtaining order information and analyzing the order information can be found elsewhere in this application (for example, operation 810 and its description in FIG. 8).

In 920, if the multiple consecutive orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is that the charging pile is faulty, it is determined that the charging pile is an abnormal charging pile. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, if the number of consecutive abnormally stopped charging orders exceeds a preset threshold, and the reason for the abnormal stop is that the charging pile is abnormal, then the charging pile is set as an abnormal charging pile. For example, if five consecutive charging orders are abnormally stopped, and the reason for the abnormal stop is the abnormal charging pile, then the charging pile is set as the abnormal charging pile.

In 930, an isolation operation is performed on the abnormal charging pile. This step may be performed by the processing device 112 (for example, the control module 430).

In some embodiments, after the processing device 112 determines the abnormal charging pile, in order to prevent other users from continuing to select the abnormal charging pile for charging operations, the processing device 112 may isolate the abnormal charging pile. The isolation operation includes: in response to obtaining a charging request from a client, if the charging pile requested by the charging request is the abnormal charging pile, returning the abnormal charging pile information to the client, and/ Or provide the client with the guidance information of other normal charging piles other than the abnormal charging pile. For example, when a driver scans and charges an abnormal charging pile, he proactively informs the driver that the charging pile is abnormal and prompts the driver to go to other charging piles at the current charging station to charge. This allows the driver to immediately perceive the abnormality of the charging pile, improve the operating efficiency of the overall charging station, and save the driver's time.

In 940, repair the abnormal charging pile. This step may be performed by the processing device 112 (for example, the control module 530).

In some embodiments, after the processing device 112 determines the abnormal charging pile, the charging pile may be repaired to realize the maintenance of the abnormal charging pile. The repair operation includes: determining whether the version of the abnormal charging pile is the latest available version, in response to determining that the version of the abnormal charging pile is the latest available version, sending a restart instruction to the abnormal charging pile; If the version of the abnormal charging pile is not the latest available version, an upgrade instruction is sent to the abnormal charging pile.

According to some embodiments of the present application, it is possible to perform isolation operations on charging piles that have failed, and to save time by promptly guiding the driver to other normal charging piles for charging, and to improve the operating efficiency of the entire charging pile. In addition, it can also provide an automatic repair function for abnormal charging piles, making the repairing of charging piles more efficient.

In 950, after performing the repair operation, if the abnormal order information sent by the abnormal charging pile is still received within the preset time period, and the cause of the abnormality is the failure of the charging pile, then the terminal of the corresponding processing personnel will be sent about the abnormal charging pile Maintenance work order. This step may be performed by the processing device 112 (for example, the control module 530).

The preset time period may be a default parameter stored in a storage device (for example, the storage device 150). Additionally or alternatively, the preset time period may be manually set according to different situations or determined by one or more components of the system 100. For example, the preset time period may be 12 hours, 24 hours, one week, and so on.

In some embodiments, the storage device (for example, the storage device 150) of the system 100 may pre-store the mapping relationship between the charging pile and the processing personnel and/or the mapping relationship between the cause of the failure of the charging pile and the processing personnel. The processing device 112 can determine the corresponding processing personnel based on the information of the abnormal charging pile (for example, the number of the charging pile, the geographic location of the charging pile) and/or the cause of the malfunction of the abnormal charging pile (for example, the gun head failure, the cabinet door failure) . Further, the processing device may send a maintenance work order regarding the abnormal charging pile to the terminal of the corresponding processing personnel. The maintenance work order can include information about abnormal charging piles (for example, abnormal charging pile number, abnormal charging status data, abnormal charging pile historical maintenance records), information of charging stations where abnormal charging piles are located (for example, charging station geographic location, charging station number , The number of charging piles in the charging station), etc. After receiving the maintenance work order, the processing personnel can repair the abnormal charging pile based on the information of the abnormal charging pile.

Step 960: After performing the repair operation, if the abnormal order information sent by the abnormal charging pile is not received within a preset time period, set the abnormal charging pile as a normal charging pile. This step may be performed by the processing device 112 (for example, the control module 530).

In some embodiments, after the abnormal charging pile is set as a normal charging pile, the processing device 112 no longer performs an isolation operation on the charging pile, and the user can use the charging pile normally.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. For example, operation 930 and operation 940 may be performed in synchronization. For another example, operation 930 or operation 940 may be omitted. In some embodiments, for the abnormal stop of the charging order received from the abnormal charging pile within a preset time period, but the reason for the abnormal stop is not the failure of the charging pile, other methods can be used to deal with it (for example, remind the user, save the record) ). For example, if the abnormal cause of the abnormal order is a vehicle failure, a reminder about the vehicle failure can be sent to the user terminal. For another example, if the abnormal cause of the abnormal order is abnormal operation, a reminder of safe operation specifications may be sent to the user terminal. More descriptions about the handling of abnormal reasons for abnormal orders can be found elsewhere in this application (for example, FIG. 7 and its description).

FIG. 10 is a flowchart of an exemplary process 1000 of a charging pile monitoring method according to some embodiments of the present application.

In 1001, a user (e.g., a driver) initiates a charging request. For example, the driver can initiate a charging request to the charging pile through the user interface (for example, an application) of the client terminal. For another example, the driver can initiate a charging request by scanning the QR code on the charging pile using the client terminal.

In 1002, in response to the charging request initiated by the user, the server returns whether the charging pile is normal. If the charging pile is abnormal, step 1003 is executed to isolate the charging pile. If the charging pile is normal, step 1004 is executed.

In 1003, the user is guided to other charging piles to charge.

In 1004, the charging post performs charging operations on the vehicle.

In 1005, the charging pile stops charging.

In 1006, it is determined whether the charging post normally stops charging. If the charging is stopped normally, the process ends. If charging is stopped abnormally, operation 1007 is performed.

In 1007, it is determined whether the abnormal stop of charging is due to a problem with the charging pile (for example, a malfunction of the charging pile). If the abnormal stopping of charging is not caused by a problem with the charging pile, the process ends. If the abnormal stop of charging is caused by a problem with the charging pile, operation 1008 is performed.

In 1008, it is determined whether the number of abnormal charging stop orders related to the charging pile exceeds a certain threshold (for example, 5 consecutively accumulated), and the abnormal charging stops are all caused by the charging pile problem. If there are no accumulated 5 pens, the process ends. If 5 transactions have been accumulated, perform operation 1009 to repair the charging pile.

In 1009, it is judged whether the version of the charging pile is the latest available version. If the version of the charging pile is the latest version, perform operation 1010 to restart the charging pile. If the version of the charging pile is not the latest version, perform operation 1011 to upgrade the version of the charging pile.

After performing the repair operation on the charging pile, perform operation 1012 to determine whether the problem of the charging pile is recovered. If the problem of restoring the charging pile has been restored, the process ends. If there is still a problem with the charging pile, perform operation 1013 and send the work order to the personnel of the charging pile enterprise for further processing.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application.

FIG. 11 is a flowchart of an exemplary process 1100 for identifying a fault of a charging pile according to some embodiments of the present application. The process 1100 may be executed by the system 100. In some embodiments, one or more operations of the process 1100 shown in FIG. 11 may be implemented in the system 100 shown in FIG. 1. For example, the process 1100 shown in FIG. 11 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 1100 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 11 and described below is not restrictive.

In 1110, the time point when the server receives the current communication data is acquired, and the communication data is sent by the charging pile. This step may be executed by the processing device 112 (for example, the acquisition module 510).

The communication data can include heartbeat signals and charging status data. The heartbeat signal refers to the data sent to the server by the charging pile in the working state (including the charging process and the non-charging process) (for example, the cumulative charging amount, the pile power, the cumulative charging duration, the cumulative charging amount). For example, under normal circumstances, each charging pile will periodically or irregularly send communication data to the server in order to "prove" that it is working. This is generally called a "heartbeat packet" or "heartbeat signal". After the server receives the heartbeat signal reported by the charging pile, it can be considered that the charging pile is currently online. The charging status data refers to the data sent by the charging pile to the server during the charging process. The charging status data can include the status data of the charging pile (for example, the status data of the operable parts of the charging pile), the interaction data between the charging pile and the vehicle, the reminder signal sent when the charging is started or ended, the charging process and the charging amount calculation Relevant signals, billing data sent after charging, etc., are as described elsewhere in this application (for example, FIG. 6 and related descriptions). For example, in the process of charging a vehicle, the charging pile will report charging process data (for example, charging power, charging time) regularly or irregularly. After charging is completed, the charging pile will also report charging bill data to the server. Therefore, in theory, as long as the server receives the data reported by the charging pile at any stage reported by the charging pile, it can be considered that the charging pile is online at that moment.

Since the server and the charging pile are devices with communication connections in the Internet of Things, the charging pile can send communication data to the server (for example, the processing device 112). After the server receives the communication data, it can directly determine that the communication is received this time. The moment of data.

In 1120, using the time point as a starting point, it is determined whether the server receives new communication data within a preset first time threshold. This step may be executed by the processing device 112 (for example, the determination module 520).

The first time threshold may be a default value stored in a storage device (for example, the storage device 150). Additionally or alternatively, the first time threshold may be manually set according to different situations or determined by one or more components of the system 100. In some embodiments, the first time threshold may be determined according to the network stability of the location where the charging pile is located. The stability of the network can be related to the brand of the charging pile and the network operator. For example, for areas with strong network signal coverage, the first threshold can be set relatively short (for example, between 5-8 minutes). For areas with weak network signal coverage, the first threshold can be set relatively long (for example, about 15 minutes).

In some embodiments, the types of the new communication data and the current communication data may be the same or different, as long as they are the communication data obtained from the charging pile.

In 1130, in response to determining that the server does not receive new communication data within the preset first time threshold, it is determined that the charging pile has an offline failure point. This step may be executed by the processing device 112 (for example, the determination module 520).

The presence of an offline fault point in the charging pile may mean that the charging pile is offline at a certain point in time. The reason for the offline failure point of the charging pile may be the charging pile failure or the network instability (for example, the temporary disconnection caused by the network jitter). In some embodiments, the offline failure point may be associated with any time point between the current reception time point of the communication data and the time point after the current reception time plus the first time threshold. For example, the offline fault point can be associated with the receiving time point of the current communication data, or can be associated with the time point after the current receiving time plus the first time threshold. That is, it can be considered that the offline failure point is generated at the time of receiving the current communication data, or it can be considered that the offline failure point is generated at the time of receiving the current communication data plus the first time threshold, or the above two Generated between time points. For example only, suppose that the processing device 112 receives communication data from charging pile No. 1 at 8:00 on June 1, 2020, the first time threshold is 10 minutes, and the processing device 112 is at 8:10 on June 1, 2020. If the new communication data has not been received, the processing device 112 can consider that there is an offline fault point in the charging pile No. 1, and the generation time of the offline fault point can be considered to be any time point between 8:00 and 8:10.

After determining that the charging pile has an offline failure point, the processing device 112 may further determine whether the charging pile has a failure. In some embodiments, the processing device 112 may determine whether there are continuous offline fault points in the charging pile and whether the number of the continuous offline fault points exceeds a fault point threshold. The existence of continuous offline fault points of the charging pile can reflect that the charging pile is offline at multiple consecutive time points, and it can be determined that the reason for the charging pile offline is the failure of the charging pile rather than the unstable network. In response to determining that the charging pile has continuous offline failure points and the number of the continuous offline failure points exceeds the failure point threshold, it is determined that the charging pile has a failure. For example, if there are 5 consecutive offline fault points in the charging pile, it is determined that the charging pile is faulty.

In some embodiments, using the time point as a starting point, the processing device 112 may determine whether the server has not received new communication data within a preset second time threshold. The second time threshold is greater than the first time threshold. For example, the second time threshold may be selected as a multiple of the first time threshold. For example only, when the first time threshold is set to 15 minutes, the second time threshold may be set in the range of 1.5 hours to 2 hours. In response to determining that the server does not receive new communication data within the preset second time threshold, the processing device 112 may determine that the charging pile is faulty.

According to some embodiments of the present application, the server can always record the time track of the communication data reported by the charging pile to be identified. If no communication data is received after the first time threshold is exceeded, it can be determined that the charging pile has an offline fault. Point, the offline fault point can be associated with the receiving time of this communication data, or it can be associated with the time point after the first time threshold is added to the current receiving time. If multiple failure points (for example, more than four) occur continuously, it can be determined that the charging pile to be identified has an offline failure. This method can eliminate the misjudgment of an offline fault due to occasional signal jitter, and improve the accuracy of offline fault identification. The second preset time is already a long period of time. If the new communication data cannot be received after the second preset time, it can be directly determined that the charging pile has an offline fault.

In some embodiments, the process 1100 may further include other steps. For example, in response to determining that the charging pile has an offline fault point, the processing device 112 may obtain the device attribute of the charging pile and the first terminal attribute corresponding to the device attribute of the charging pile. The processing device 112 may send fault reminding information to the first terminal according to the attributes of the first terminal, where the fault reminding information includes the device attributes of the charging pile. For another example, the processing device 112 may obtain the proportion of the charging piles that are determined to have offline fault points in the charging station to the total number of charging piles, and the processing device 112 may determine whether the proportion exceeds a threshold, and in response to determining that the proportion exceeds the threshold , The processing device 112 may obtain the site attributes of the charging station and the second terminal attributes corresponding to the site attributes, and the processing device 112 may send alarm information to the second terminal according to the second terminal attributes, and the alarm information includes The site attributes of the charging station. More descriptions about sending fault reminder information and alarm information can be found elsewhere in this application (for example, Figure 13 and related descriptions).

In some embodiments, operation 1120 and operation 1130 may be omitted. For example, if the current communication data includes fault information, the processing device 112 may directly determine that the charging pile is faulty. As described elsewhere in this application, the sensors inside the charging pile can detect the actual status data of the charging pile. If the status data of a certain component is found to be abnormal, the charging pile can generate fault information and use the fault information as part of the communication data. Report to the server. After the server receives the fault information, it can determine that the charging pile has an offline fault. However, if the network fails and the server has been unable to successfully receive the failure information, at this time, the charging pile can be detected for failure through the process 1100. Therefore, according to some embodiments of the present application, it is possible to identify the fault of the charging pile by combining two methods of active reporting of the charging pile and passive detection by the server, so as to find the fault of the charging pile in a more timely manner.

FIG. 12 is a flowchart of an exemplary process 1200 for identifying a fault of a charging pile according to some embodiments of the present application. The process 1200 can be executed by the system 100. In some embodiments, one or more operations of the process 1200 shown in FIG. 12 may be implemented in the system 100 shown in FIG. 1. For example, the process 1200 shown in FIG. 12 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 1200 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 12 and described below is not restrictive.

In 1210, the time point when the server receives the current communication data is acquired, and the communication data is sent by the charging pile. This step may be executed by the processing device 112 (for example, the acquisition module 510).

A detailed description of the time point when the acquisition server receives the current communication data can be found elsewhere in this application (for example, operation 1110 in FIG. 11).

In 1220, using the time point as a starting point, it is determined whether the server receives new communication data within a preset first time threshold. This step may be executed by the processing device 112 (for example, the determination module 520).

The detailed description about determining whether the server receives new communication data within the preset first time threshold can be found elsewhere in this application (for example, operation 1120 in FIG. 11).

In 1230, in response to determining that the server does not receive new communication data within the preset first time threshold, and the charging status data includes order abnormality information, an order abnormality identifier is generated for the abnormal order. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, the processing device 112 may determine whether the charging state data in the current communication data includes abnormal state data. In response to determining that the charging state data includes abnormal state data, the processing device 112 may determine that the order is an abnormal order, and generate an order abnormality identifier (for example, a first identifier, a second identifier) for the abnormal order. In some embodiments, as shown in the related description of FIG. 6, the charging pile can determine whether the charging state data includes abnormal state data, and if it is determined that the charging state data includes abnormal state data, it is determined that the order is an abnormal order, and An identifier corresponding to the abnormal state data is generated for the abnormal order, and the identifier is further sent to the processing device 112. That is, in different application scenarios, the execution body of the operation of generating an identifier for an abnormal order may be the charging pile or the processing device 112, and this application does not make any restrictions. The description of generating identifiers for abnormal orders can be found elsewhere in this application (for example, Figure 6 and related descriptions).

In 1240, the number of historical abnormal orders and the total number of historical orders of the charging pile are obtained. This step may be executed by the processing device 112 (for example, the acquisition module 510).

In some embodiments, the processing device 112 may count the number of historical abnormal orders related to the charging pile in the first historical time period and the total number of historical orders related to the charging pile in the second historical time period. In some embodiments, the first historical time period and the second historical time period may be different. In some embodiments, the first historical time period and the second historical time period may be the same, thereby reducing the amount of data analysis and improving efficiency. In some embodiments, the historical time period (for example, the first historical time period, the second historical time period) may be a default value stored in the storage device (for example, the storage device 150). Additionally or alternatively, the historical time period (for example, the first historical time period, the second historical time period) may be manually set according to different situations or determined by one or more components of the system 100. For example, the historical time period may be the last three days, the last week, the last month, the last three months, and so on.

In 1250, it is determined whether the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the proportion threshold. This step may be executed by the processing device 112 (for example, the determination module 520).

In 1260, in response to determining that the ratio of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the ratio threshold, it is determined that the charging pile is faulty. This step may be executed by the processing device 112 (for example, the determination module 520). In response to determining that the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders does not exceed the proportion threshold, it is determined that the charging pile is not faulty.

In some embodiments, the ratio threshold may be a default value stored in a storage device (eg, storage device 150). Additionally or alternatively, the ratio threshold may be manually set according to different situations or determined by one or more components of the system 100. In some embodiments, the ratio threshold can be set between 30%-50%. As an example only, assuming that the ratio threshold is set to 50%, if a charging pile has more than 50% of abnormal billing information in the past three days, it can be considered that the charging pile is faulty.

FIG. 13 is a flowchart of an exemplary process 1300 for identifying a fault of a charging pile according to some embodiments of the present application. The process 1300 may be executed by the system 100. In some embodiments, one or more operations of the process 1300 shown in FIG. 13 may be implemented in the system 100 shown in FIG. 1. For example, the process 1300 shown in FIG. 13 may be stored in a storage device in the form of instructions, and called and/or executed by the server 110 (for example, the processing device 112). The operation of the flow shown below is for illustrative purposes only. In some embodiments, the process 1300 may include one or more additional operations not described and/or one or more operations not discussed. In addition, the operation sequence of the flow shown in FIG. 13 and described below is not restrictive.

In 1310, the time point when the server receives the current communication data is acquired, the communication data is sent by the charging pile, and the communication data includes charging state data. This step may be performed by a processing device (for example, the acquisition module 510).

The description of the time point when the acquisition server receives the current communication data can be found elsewhere in this application (for example, operation 1110 in FIG. 11).

In 1320, using the time point as a starting point, it is determined whether the server receives new communication data within a preset first time threshold. This step may be executed by the processing device 112 (for example, the determination module 520).

The description about determining whether the server receives new communication data within the preset first time threshold can be found elsewhere in this application (for example, operation 1120 in FIG. 11).

In 1330, in response to determining that the server receives the new communication data within the preset first time threshold, obtain the status data of the charging pile. This step may be executed by the processing device 112 (for example, the acquisition module 510).

For example, if the communication data includes the status data of the charging pile, the processing device 112 may directly extract the status data of the charging pile from the communication data. For another example, if the communication data does not include the status data of the charging post, the processing device 112 may obtain the status data of the corresponding component from the charging post (for example, a sensor).

In 1340, it is determined whether the status data of the charging pile is within a preset range. This step may be executed by the processing device 112 (for example, the determination module 520).

The preset range of the state data of the charging pile refers to the standard range of the state data of the charging pile in a normal working state. In some embodiments, each state data of the operable parts of the charging pile has its corresponding preset standard range. For example, the state data of the charging gun tip may include the preset standard range of the current of the charging gun tip, the preset standard range of the temperature of the charging gun tip, the preset standard range of the voltage of the charging gun tip, and so on.

In some embodiments, the preset standard range may be pre-stored in a storage device (for example, the storage device 150) of the system 100, and the processing device 112 may obtain the preset standard range from the storage device. In some embodiments, the preset standard range may be set by a component of the system 100 (for example, the processing device 112), or may be set by a user of the system 100 according to the model of the charging pile.

In 1350, in response to determining that the state data of the charging pile is not within the preset range, it is determined that the charging pile has a fault. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, in response to determining that any type of state data of the charging post is not within its corresponding preset range, the processor 112 may determine that the charging post is faulty. In some embodiments, in response to determining that a certain preset type of state data of the charging pile is not within its corresponding preset range, the processor 112 may determine that the charging pile is faulty. For example, only when it is determined that the state data of the charging gun or the pile body of the charging pile is not within the corresponding preset range, it is determined that the charging pile has a fault.

In 1360, the fault reminder information is sent to the first terminal according to the attributes of the first terminal, and the fault reminder information includes the device attributes of the charging pile. This step may be performed by the processing device 112 (for example, the control module 530).

In some embodiments, in response to determining that the charging post has a fault, the processing device 112 may obtain the device attribute of the charging post and the first terminal attribute corresponding to the device attribute of the charging post. For example, the processing device 112 may determine the first terminal attribute corresponding to the charging pile device attribute according to the charging pile fault type and/or the correspondence between the charging pile device attribute and the first terminal attribute. The processing device 112 may send fault reminding information to the first terminal according to the attributes of the first terminal.

The device attributes of the charging pile may include the information of the charging pile, for example, the charging pile model, the charging pile brand, the charging pile number, and the geographic location of the charging pile. The first terminal may be a communication device (for example, a mobile phone) worn by a processing person (for example, a maintenance person). The first terminal attribute may include the information of the first terminal, for example, the information of the user associated with the first terminal (for example, the identity information of the processing personnel), the model of the first terminal, and so on. In some embodiments, the processing device 112 may send a fault reminder message according to a preset communication method, such as SMS, WeChat, and automatic dialing for voice calls, so that the maintenance personnel can repair the faulty charging pile in time. The fault information may include the fault of the charging pile, the information of the charging pile (for example, the number of the charging pile, the geographic location of the charging pile), and the like. The fault information can be text information, voice information, video information, picture information, etc.

In 1370, the proportion of the charging piles determined to be faulty in the charging station to the total number of charging piles is obtained. This step may be performed by the processing device 112 (for example, the acquisition module 510).

In some embodiments, the processing device 112 may determine the charging station where the faulty charging post is located based on the information of the faulty charging post (for example, the number of the charging post, the geographic location of the charging post). For example, the storage device (for example, the storage device 150) of the system 100 may store the corresponding relationship between the charging station number and the charging station number, and the processing device 112 may obtain the corresponding relationship between the charging station number and the charging station number from the storage device, and according to the existence The number of the faulty charging pile is to determine the number of the charging station where the faulty charging pile is located. Then, the processing device 112 may count the number of all charging piles determined to be faulty in the charging station and the total number of all charging piles in the charging station. Further, the processing device 112 may determine the proportion of all the charging piles determined to be faulty in the charging station to the total number of charging piles in the charging station.

In 1380, it is determined whether the ratio exceeds a threshold. This step may be executed by the processing device 112 (for example, the determination module 520).

In some embodiments, the threshold may be a default value stored in a storage device (eg, storage device 150). Additionally or alternatively, the threshold may be manually set according to different situations or determined by one or more components of the system 100. For example only, the threshold can be set to 30%, that is to say, when 30% of the charging piles in a charging station have a failure, it can be reported to the person in charge of the charging station.

In 1390, in response to determining that the ratio exceeds the threshold, a site attribute of the charging station and a second terminal attribute corresponding to the site attribute are acquired. This step may be executed by the processing device 112 (for example, the determination module 520).

When the proportion of charging piles determined to be faulty in the charging station to the total number of charging piles exceeds the threshold, it is likely that the collective failure is caused by network problems or service problems. At this time, the operator platform is required to intervene to solve the problem. In some embodiments, the processing device 112 may determine the second terminal attribute corresponding to the site attribute of the charging station according to the correspondence between the station attribute of the charging station and the second terminal attribute. The site attributes of the charging station may include information about the charging station, for example, the geographic location of the charging station, the number of the charging station, the historical order of the charging pile in the charging station, the historical maintenance record of the charging pile in the charging station, etc., or any combination thereof. The second terminal may be a communication device (for example, a mobile phone) worn by a processing person (for example, a person in charge of a charging station). The second terminal attribute may include information of the second terminal, for example, information of the user associated with the second terminal (for example, the identity information of the person in charge of the charging station), the model of the second terminal, and the like.

In 1391, sending alarm information to the second terminal according to the attributes of the second terminal, where the alarm information includes the site attributes of the charging station. This step may be performed by the processing device 112 (for example, the control module 530).

In some embodiments, the processing device 112 may send an alarm message according to a preset communication method, such as SMS, WeChat, automatic dialing for voice calls, etc., so that the person in charge of the charging station can handle the failure of the charging station in time. The alarm information may include the information of the charging station (for example, the number of the charging station), the failure of the charging pile in the charging station, the number of charging piles that have failed in the charging station, and the like. The alarm information can be text information, voice information, video information, picture information, etc.

According to some embodiments of the present application, when many charging piles in a certain charging station fail, the person in charge of the charging station can be notified in time, for example, by sending a short message, sending a WeChat, automatic dialing to make a voice call, etc. , In order to deal with the fault as soon as possible and shorten the time that the charging pile is not available.

It should be noted that the above description is provided for illustrative purposes only, and is not intended to limit the scope of this application. For those of ordinary skill in the art, various changes and modifications can be made based on the description of this application. However, these changes and modifications will not depart from the scope of this application. For example, operation 1370 and operation 1380 may be performed simultaneously. For another example, operations 1370 to 1391 or operation 1360 may be omitted.

Fig. 14 is a schematic diagram of an exemplary charging monitoring system according to some embodiments of the present application.

As shown in FIG. 14, the charging monitoring system may include a client terminal 1410, a charging pile 1420, a platform server 1430, an electric vehicle 1440, and a handler terminal 1450. The charging pile 1420 may include a plurality of sensors 1421 and a controller 1422. The driver of the electric vehicle 1440 can use the client terminal 1410 to scan the charging code to initiate a charging request to the charging post 1420. The charging pile 1420 may generate a charging order based on the charging request, or send the charging request to the platform server 1430, and the platform server 1430 may coordinate the resources of the charging pile in the charging station (for example, recommend other idle charging piles for the driver), and generate it based on the charging request Charge order. During the charging process, multiple sensors 1421 in the charging post 1420 can detect actual state data of the charging post 1420. For example, the sensor 1421 may include a temperature sensor 1, a current sensor 2, a pressure sensor 3, and so on. The sensor 1421 may send the detected actual state data to the controller 1422. The controller 1422 may determine whether the charging pile 1420 has a fault by determining whether the actual state data is within the corresponding preset standard range. If it is determined that the charging pile 1420 is faulty, the controller 1422 may generate fault information and send the fault information to the platform server 1430. In response to the fault information, the platform server 1430 may generate fault reminder information and send the fault reminder information to the corresponding processor terminal 1450.

Fig. 15A is an exemplary schematic diagram of a data transmission process between a charging pile and a platform server according to some embodiments of the present application. As shown in Figure 15A, the charging pile can periodically or irregularly send a heartbeat signal (also called a "heartbeat package") to the platform server (e.g., cumulative charging amount, pile power, cumulative charging duration, cumulative charging amount). After the platform server receives the heartbeat signal reported by the charging pile, it can be considered that the charging pile is currently online.

Fig. 15B is an exemplary schematic diagram of a bill transmission process between a charging pile and a platform server according to some embodiments of the present application. As shown in Figure 15B, when the charging is completed, the charging pile can report the charging bill to the platform server. Correspondingly, after receiving the charging bill, the platform server will send a response message to the charging pile.

If the charging process is completed normally, the charging bill is generated normally, and if the charging bill is interrupted due to some failure reasons (for example, the connection of the charging gun is loose) during the generation of the charging bill, and the charging bill cannot be generated normally, a bill abnormal signal is sent. In either case, the charging pile will always try to send bill-related information to the platform server until it receives a response signal from the platform server. If the platform server fails to receive successfully, the platform server can determine whether the charging pile has an offline fault according to the process 1100.

Fig. 15C is an exemplary schematic diagram of a fault signal transmission process between a charging pile and a platform server according to some embodiments of the present application.

The sensor set inside the charging pile can detect the actual status data of the charging pile. The sensor can send the detected actual state data to the controller of the charging pile, and the controller may determine whether the charging pile is faulty by determining whether the actual state data is within the corresponding preset standard range. If it is determined that the charging pile is faulty, the controller can generate fault information and send the fault information to the platform server. Correspondingly, after receiving the fault information, the platform server will send a response message to the charging pile.

The possible beneficial effects of the embodiments of the present application include, but are not limited to: (1) After determining the abnormal charging pile, by isolating and repairing the charging pile that has failed, the repair of the charging pile can be made more efficient and improve The operating efficiency of the entire charging pile; (2) The server can determine whether the charging pile has an offline failure based on the result of whether the new communication data is received within the time threshold after receiving the charging pile data, which can eliminate errors due to occasional signal jitter If it is judged as an offline fault, the accuracy of offline fault identification is improved; (3) The fault of the charging pile can be identified by combining the active reporting of the charging pile and the passive detection of the server, so that the fault of the charging pile can be found in a more timely manner. It should be noted that different embodiments may have different beneficial effects. In different embodiments, the possible beneficial effects may be any one or a combination of the above, or any other beneficial effects that may be obtained.

The basic concepts have been described above. Obviously, for those of ordinary skill in the art, the above application disclosure is only an example, and does not constitute a limitation to the application. Although it is not explicitly stated here, those of ordinary skill in the art may make various modifications, improvements and amendments to this application. Such modifications, improvements and amendments are suggested in this application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of this application.

At the same time, this application uses specific terms to describe the embodiments of the application. For example, "one embodiment", "an embodiment" and/or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment", "one embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification do not necessarily refer to the same embodiment. In addition, some features, structures, or characteristics in one or more embodiments of the present application can be appropriately combined.

In addition, those of ordinary skill in the art can understand that various aspects of this application can be illustrated and described through several patentable categories or situations, including any new and useful process, machine, product, or combination of substances, or Any new and useful improvements to it. Correspondingly, various aspects of the present application can be completely executed by hardware, can be completely executed by software (including solid, resident software, microcode, etc.), or can be executed by a combination of hardware and software. The above hardware or software can all be referred to as "units", "modules" or "systems". In addition, various aspects of the present application may take the form of a computer program product embodied in one or more computer-readable media, where the computer-readable program code is contained therein.

The computer-readable signal medium may include a propagated data signal containing computer program code, for example on baseband or as part of a carrier wave. Such propagated signals can take many forms, including electromagnetic forms, optical forms, etc., or any suitable combination. The computer-readable signal medium may be any computer-readable medium except a computer-readable storage medium, and the medium may be connected to an instruction execution system, apparatus, or device to realize communication, propagation, or transmission of a program for use. The program code located on the computer-readable signal medium can be transmitted through any suitable medium, including radio, cable, fiber optic cable, RF, etc., or a combination of any of the above media.

The computer program code required for the operation of each part of this application can be written in any one or more programming languages, including subject-oriented programming languages such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc. , Conventional programming languages such as C language, VisualBasic, Fortran2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code can run entirely on the user's computer, or as an independent software package on the user's computer, or partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter case, the remote computer can be connected to the user’s computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or can be connected to an external computer (for example, via the Internet), or in a cloud computing In the environment, or as a service (for example, software as a service (SaaS)).

In addition, unless explicitly stated in the claims, the order of processing elements and sequences, the use of numbers and letters, or the use of other names in this application are not used to limit the order of the procedures and methods of this application. Although the foregoing disclosure uses various examples to discuss some of the invention application embodiments that are currently considered useful, it should be understood that such details are only for illustrative purposes, and the appended claims are not limited to the disclosed embodiments. On the contrary, The claims are intended to cover all modifications and equivalent combinations that conform to the essence and scope of the embodiments of the present application. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

For the same reason, it should be noted that, in order to simplify the expression disclosed in this application and help the understanding of one or more embodiments of the invention, in the foregoing description of the embodiments of this application, multiple features are sometimes combined into one embodiment and appendix. Figure or its description. However, this method of disclosure does not mean that the subject of the application requires more features than those mentioned in the claims. In fact, the features of the embodiment are less than all the features of the single embodiment disclosed above.

Claims

A method for identifying faults of a charging pile, which is characterized in that it includes:

In response to obtaining a charging request, generating an order for the charging request;

Obtain charging state data during the current charging operation of the vehicle;

Determining whether the charging state data includes abnormal state data;

In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order; and

Send the abnormal order to the server connected to the charging pile.
The method according to claim 1, wherein the charging state data includes state data of operable parts of the charging pile, and in response to determining that the charging state data includes the abnormal state data, it is determined that the order is An abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order includes:

In response to determining that the state data of the operable component of the charging pile is an abnormal state, a first identifier is generated for the abnormal order.
The method according to claim 1, wherein the charging state data includes interaction data between a charging pile and the vehicle, and in response to determining that the charging state data includes the abnormal state data, determining that the charging state data includes the abnormal state data The order is an abnormal order, and an identifier corresponding to the abnormal state data is generated for the abnormal order, including:

In response to determining that the interaction data is in an abnormal state, a second identifier is generated for the abnormal order.
The method according to claim 1, wherein generating an identifier corresponding to the abnormal state data for the abnormal order comprises:

Obtain the mapping relationship between the abnormal state data and the identifier; and

According to the mapping relationship and the abnormal state data, the identifier of the abnormal order is determined.
A method for recognizing and monitoring the fault of a charging pile, which is characterized in that it comprises:

Acquiring information about an abnormal order, the abnormal order reflecting the presence of abnormal state data during the charging operation of the charging pile, and the information about the abnormal order including an identifier corresponding to the abnormal state data; and

According to the identifier, the reason for the abnormality of the abnormal order is determined.
The method according to claim 5, wherein the reason for the abnormality includes at least one of a charging pile failure, a vehicle failure, and an abnormal operation.
The method according to claim 5, wherein determining the abnormal reason of the abnormal order according to the identifier comprises:

Acquiring charging pile information corresponding to the abnormal order;

Acquiring historical abnormal order information corresponding to the charging pile information in a historical time period;

Acquiring the historical identifier in the information of the historical abnormal order; and

The reason for the abnormal order of the abnormal order is determined according to the proportion of the identifier in the historical identifier.
7. The method according to claim 7, wherein the identifier is a first identifier, and the first identifier indicates that the state data of the operable part of the charging pile is an abnormal state, and according to the identifier To determine the reason for the abnormal order, including:

It is determined whether the proportion of the first identifier in the historical identifier is greater than a threshold.
The method according to claim 8, wherein the method further comprises:

In response to determining that the proportion of the first identifier in the historical identifier is greater than the threshold, it is determined that the cause of the abnormality is a failure of the charging pile.
The method according to claim 8, wherein the method further comprises:

In response to determining that the proportion of the first identifier in the historical identifier is less than the threshold, it is determined that the cause of the abnormality is an abnormal operation.
The method according to claim 7, wherein the identifier is a second identifier, and the second identifier indicates that the interaction data between the charging post and the charged vehicle is in an abnormal state. The identifier to determine the reason for the abnormal order, including:

It is determined whether the proportion of the second identifier in the historical identifier is greater than a threshold.
The method according to claim 11, wherein the method further comprises:

In response to determining that the proportion of the second identifier in the historical identifier is greater than the threshold, it is determined that the cause of the abnormality is a failure of the charging pile.
The method according to claim 11, wherein the method further comprises:

In response to determining that the proportion of the second identifier in the historical identifier is less than the threshold, it is determined that the cause of the abnormality is a vehicle failure.
The method according to claim 5, wherein the method further comprises:

Generate a mapping relationship between abnormal state data and identifiers; and

Sending the mapping relationship to the charging pile.
The method according to claim 5, wherein the method further comprises:

The mapping relationship between the cause of the exception and the processing personnel; and

Send the reason for the abnormality to the terminal of the corresponding processing personnel.
The method according to claim 5, wherein the abnormal cause of the abnormal order is a failure of the charging pile, and the method further comprises:

Determining that the charging pile corresponding to the abnormal order is an abnormal charging pile; and

Monitor the abnormal charging pile.
The method according to claim 16, wherein determining that the charging pile corresponding to the abnormal order is an abnormal charging pile comprises:

If the multiple continuous charging orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is the failure of the charging pile, it is determined that the charging pile is an abnormal charging pile.
The method according to claim 16, wherein the monitoring operation includes an isolation operation, and the isolation operation includes:

In response to obtaining a charging request from the client, if the charging pile requested by the charging request is the abnormal charging pile, return the abnormal information of the abnormal charging pile to the client, and/or to the client Provide guidance information for normal charging piles other than abnormal charging piles.
The method according to claim 16, wherein the monitoring operation includes a repair operation, and the repair operation includes:

It is determined whether the version of the abnormal charging pile is the latest available version.
The method according to claim 19, wherein the repair operation further comprises:

In response to determining that the version of the abnormal charging pile is the latest available version, a restart instruction is sent to the abnormal charging pile.
The method according to claim 19, wherein the repair operation further comprises:

In response to determining that the version of the abnormal charging pile is not the latest available version, an upgrade instruction is sent to the abnormal charging pile.
The method according to claim 19, wherein after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is still received within a preset time period, and the reason for the abnormality is a failure of the charging pile , The maintenance work order for the abnormal charging pile is sent to the terminal of the corresponding processing personnel.
The method according to claim 19, wherein after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is not received within a preset time period, the abnormal charging pile is set It is a normal charging pile.
A method for identifying faults of a charging pile, which is characterized in that it includes:

Acquiring the time point at which the server receives the current communication data, the communication data being sent by the charging pile;

Using the time point as a starting point, determine whether the server receives new communication data within a preset first time threshold; and

In response to determining that the server does not receive new communication data within a preset first time threshold, it is determined that the charging pile has an offline failure point.
The method according to claim 24, further comprising:

Determining whether the charging pile has continuous offline fault points and the number of the continuous offline fault points exceeds a fault point threshold; and

In response to determining that the charging pile has continuous offline failure points and the number of the continuous offline failure points exceeds the failure point threshold, it is determined that the charging pile has a failure.
The method according to claim 24, further comprising:

Using the time point as a starting point, determine whether the server has not received new communication data within a preset second time threshold, where the second time threshold is greater than the first time threshold; and

In response to determining that the server does not receive new communication data within the preset second time threshold, it is determined that the charging pile is faulty.
The method according to claim 24, wherein the communication data includes a heartbeat signal or charging status data.
The method according to claim 27, wherein the charging status data includes an order abnormality signal, and the method further comprises:

Acquiring the historical abnormal order quantity and the total historical order quantity of the charging pile;

Determine whether the proportion of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the proportion threshold; and

In response to determining that the ratio of the number of historical abnormal orders of the charging pile to the total number of historical orders exceeds the ratio threshold, it is determined that the charging pile is faulty.
The method according to claim 27, wherein the charging status data includes the status data of the charging pile, and the method further comprises:

In response to determining that the server receives new communication data within a preset first time threshold, acquiring state data of the charging pile;

Determine whether the status data of the charging pile is within a preset range; and

In response to determining that the state data of the charging pile is not within the preset range, it is determined that the charging pile is faulty.
The method according to claim 29, wherein the state data of the charging pile includes the temperature, current value, voltage value of the operable parts of the charging pile, the real-time output power of the charging pile, the accumulated charging time of the charging pile, and At least one item of the accumulated charging capacity of the charging pile.
The method according to claim 24, wherein the communication data includes fault information, and the method further comprises:

It is determined that the charging pile is faulty.
The method according to claim 25, wherein the method further comprises:

In response to determining that the charging pile is faulty, acquiring the device attribute of the charging pile and the first terminal attribute corresponding to the device attribute; and

Sending fault reminding information to the first terminal according to the attributes of the first terminal, where the fault reminding information includes the device attributes of the charging pile.
The method according to claim 32, wherein the method further comprises:

Obtain the proportion of charging piles determined to be faulty in the charging station to the total number of charging piles;

Determine whether the ratio exceeds a threshold;

In response to determining that the ratio exceeds the threshold, acquiring a site attribute of the charging station and a second terminal attribute corresponding to the site attribute; and

Sending alarm information to the second terminal according to the attributes of the second terminal, where the alarm information includes the site attributes of the charging station.
A method for recognizing and monitoring the fault of a charging pile, which is characterized in that it comprises:

Obtain the information of the charging order and analyze the information of the charging order;

If the charging order is abnormally stopped, and the reason for the abnormal stop is the abnormal charging pile, it is determined that the charging pile is an abnormal charging pile; and

Perform monitoring operations on the charging pile.
The method according to claim 34, wherein determining that the charging pile is an abnormal charging pile comprises:

If the multiple continuous charging orders related to the charging pile are all abnormally stopped, and the reason for the abnormal stop is the failure of the charging pile, it is determined that the charging pile is an abnormal charging pile.
The method according to claim 34, wherein the monitoring operation includes an isolation operation, and the isolation operation includes:

In response to obtaining a charging request from the client, if the charging pile requested by the charging request is the abnormal charging pile, return the abnormal information of the abnormal charging pile to the client, and/or to the client Provide guidance information for normal charging piles other than abnormal charging piles.
The method according to claim 34, wherein the monitoring operation includes a repair operation, and the repair operation includes:

It is determined whether the version of the abnormal charging pile is the latest available version.
The method according to claim 37, wherein the repair operation further comprises:

In response to determining that the version of the abnormal charging pile is the latest available version, a restart instruction is sent to the abnormal charging pile.
The method according to claim 37, wherein the repair operation further comprises:

In response to determining that the version of the abnormal charging pile is not the latest available version, an upgrade instruction is sent to the abnormal charging pile.
The method according to claim 37, wherein after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is still received within a preset time period, and the reason for the abnormality is a failure of the charging pile , The maintenance work order for the abnormal charging pile is sent to the terminal of the corresponding processing personnel.
The method according to claim 37, wherein after the repair operation is performed, if the abnormal order information sent by the abnormal charging pile is not received within a preset time period, the abnormal charging pile is set It is a normal charging pile.
A system for identifying faults of charging piles includes:

One or more storage devices that store a set of instructions used for charging pile fault identification; and

One or more processors in communication with the one or more storage devices, wherein, when executing the set of instructions, the one or more processors are configured to:

In response to obtaining a charging request, generating an order for the charging request;

Obtain charging state data during the current charging operation of the vehicle;

Determining whether the charging state data includes abnormal state data;

In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order; and

Send the abnormal order to the server connected to the charging pile.
A charging pile fault identification and monitoring system includes:

One or more storage devices to store a set of instructions for charging pile fault identification and monitoring; and

One or more processors in communication with the one or more storage devices, wherein, when executing the set of instructions, the one or more processors are configured to:

Acquiring information about an abnormal order, the abnormal order reflecting the presence of abnormal state data during the charging operation of the charging pile, and the information about the abnormal order including an identifier corresponding to the abnormal state data; and

According to the identifier, the reason for the abnormality of the abnormal order is determined.
A system for identifying faults of charging piles includes:

One or more storage devices to store a set of instructions for charging pile fault identification and monitoring; and

One or more processors in communication with the one or more storage devices, wherein, when executing the set of instructions, the one or more processors are configured to:

Acquiring the time point at which the server receives the current communication data, the communication data being sent by the charging pile;

Using the time point as a starting point, determine whether the server receives new communication data within a preset first time threshold; and

In response to determining that the server does not receive new communication data within a preset first time threshold, it is determined that the charging pile has an offline failure point.
A charging pile fault identification and monitoring system includes:

One or more storage devices to store a set of instructions for charging pile fault identification and monitoring; and

One or more processors in communication with the one or more storage devices, wherein, when executing the set of instructions, the one or more processors are configured to:

Obtain the information of the charging order and analyze the information of the charging order;

If the charging order is abnormally stopped, and the reason for the abnormal stop is the abnormal charging pile, it is determined that the charging pile is an abnormal charging pile; and

Perform monitoring operations on the charging pile.
A computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing a fault in a charging pile is implemented, the method comprising:

In response to obtaining a charging request, generating an order for the charging request;

Obtain charging state data during the current charging operation of the vehicle;

Determining whether the charging state data includes abnormal state data;

In response to determining that the charging state data includes the abnormal state data, determining that the order is an abnormal order, and generating an identifier corresponding to the abnormal state data for the abnormal order; and

Send the abnormal order to the server connected to the charging pile.
A computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing and monitoring faults of a charging pile is implemented, the method comprising:

Acquiring information about an abnormal order, the abnormal order reflecting the presence of abnormal state data during the charging operation of the charging pile, and the information about the abnormal order including an identifier corresponding to the abnormal state data; and

According to the identifier, the reason for the abnormality of the abnormal order is determined.
A computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing a fault in a charging pile is implemented, the method comprising:

Acquiring the time point at which the server receives the current communication data, the communication data being sent by the charging pile;

Using the time point as a starting point, determine whether the server receives new communication data within a preset first time threshold; and

In response to determining that the server does not receive new communication data within the preset first time threshold, it is determined that the charging pile has an offline failure point.
A computer-readable storage medium, the storage medium stores computer instructions, and when the computer instructions are executed by a processor, a method for recognizing and monitoring faults of a charging pile is implemented, the method comprising:

Obtain the information of the charging order and analyze the information of the charging order;

If the charging order is abnormally stopped, and the reason for the abnormal stop is the abnormal charging pile, it is determined that the charging pile is an abnormal charging pile; and

Perform monitoring operations on the charging pile.