Disclosure of Invention
In view of the above, the present invention provides a system, a method and a device for charging an electric vehicle, which are intended to achieve the purpose of convenient charging of the electric vehicle.
In order to achieve the above object, the following solutions are proposed:
an electric vehicle charging processing system, comprising: a background server and a service client;
the service client is used for displaying charging service content;
the service client is further configured to acquire an operation event completed by a user for the charging service content, and send a corresponding instruction to the background server;
and the service client is also used for receiving and displaying the service information which is sent by the background server and corresponds to the corresponding instruction.
Preferably, the service client is specifically configured to:
when charging request content included in the charging service content is detected to be selected, acquiring a charging request operation event, and sending a charging request instruction to the background server;
when charging starting content included in the charging service content is detected to be selected, acquiring a charging starting operation event, and sending a charging starting instruction to the background server;
and when the charging stopping content included in the charging service content is detected to be selected, acquiring a charging stopping operation event, and sending a charging stopping instruction to the background server.
Preferably, the service client is further specifically configured to:
and when detecting that the charging monitoring content included in the charging service content is selected, acquiring a charging monitoring operation event, and sending a charging monitoring instruction to the background server.
An electric vehicle charging processing method is applied to a business client, and comprises the following steps:
displaying the charging service content;
acquiring an operation event finished by a user aiming at the charging service content, and sending a corresponding instruction to the background server;
and receiving and displaying the service information which is sent by the background server and corresponds to the corresponding instruction.
Preferably, the obtaining the operation event completed by the user for the charging service content and sending the corresponding instruction to the background server includes:
when charging request content included in the charging service content is detected to be selected, acquiring a charging request operation event, and sending a charging request instruction to the background server;
when charging starting content included in the charging service content is detected to be selected, acquiring a charging starting operation event, and sending a charging starting instruction to the background server;
and when the charging stopping content included in the charging service content is detected to be selected, acquiring a charging stopping operation event, and sending a charging stopping instruction to the background server.
Preferably, the obtaining an operation event completed by the user for the charging service content and sending a corresponding instruction to the background server further includes:
and when detecting that the charging monitoring content included in the charging service content is selected, acquiring a charging monitoring operation event, and sending a charging monitoring instruction to the background server.
An electric automobile charging processing device is applied to a business client, and the device comprises:
the first display unit is used for displaying the charging service content;
the event acquisition unit is used for acquiring an operation event finished by a user aiming at the charging service content and sending a corresponding instruction to the background server;
a content receiving unit, configured to receive service information corresponding to the corresponding instruction sent by the background server;
and the second display unit is used for displaying the service information.
Preferably, the event acquiring unit includes:
the first event acquiring subunit is configured to, when it is detected that charging request content included in the charging service content is selected, acquire a charging request operation event and send a charging request instruction to the background server;
the second event obtaining subunit is configured to, when it is detected that charging start content included in the charging service content is selected, obtain a charging start operation event, and send a charging start instruction to the background server;
and the third event acquiring subunit is configured to acquire a charging stop operation event and send a charging stop instruction to the background server when it is detected that the charging stop content included in the charging service content is selected.
Preferably, the event acquiring unit further includes:
and the fourth event acquiring subunit is configured to acquire a charging monitoring operation event and send a charging monitoring instruction to the background server when detecting that the charging monitoring content included in the charging service content is selected.
Compared with the prior art, the technical scheme of the invention has the following advantages:
according to the charging processing system, the charging processing method and the charging processing device for the electric automobile, the operation events finished by the user aiming at the charging service content are obtained through the service client, the corresponding instruction is sent to the background server, and the service information corresponding to the corresponding instruction sent by the background server is received and displayed. The service client is used as a starting and managing tool of the charging pile, so that a charging point card does not need to be carried about for an electric vehicle owner, multiple card swiping operations are not needed for completing charging of the electric vehicle, and the electric vehicle can be charged conveniently only through the operation of the service client; for the charging operation mechanism, fixed office places for handling charging card services can be reduced, and the cost of manpower and material resources is reduced.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, a schematic structural diagram of an electric vehicle charging processing system according to an embodiment of the present invention is shown, where the system includes: a background server 1 and a service client 2.
The service client 2 runs in an intelligent terminal. The smart terminal may be a mobile phone, a tablet computer, a laptop portable computer, a desktop computer, and the like. The intelligent terminal is connected with the background server 1 through a wired network or a wireless network. The background server 1 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center.
And the service client 2 is used for displaying the charging service content.
The displayed charging service content may specifically include charging request content, charging start content, and charging stop content. In order to facilitate the user to monitor the whole charging process, the displayed charging service content may also include charging monitoring content. The specific form of displaying the charging service content may be pictures and/or texts.
The service client 2 is further configured to acquire an operation event completed by the user for the charging service content, and send a corresponding instruction to the background server.
The operation event refers to an operation event completed by the user who logs in the service client 2 for the charging service content. Operational events include, but are not limited to, a charge request operational event, a charge start operational event, a charge stop operational event, and a charge monitor operational event.
Specifically, the service client 2 acquiring the operation event may include the following possible situations:
1. when the charging request content is detected to be selected, a charging request operation event is acquired, and a charging request instruction is sent to the background server 1.
The user can select a target charging pile according to the charging pile information displayed by the service client 2, and then select the charging request content. The charging request instruction sent by the service client 2 includes information such as a target charging pile identifier and a user identifier for logging in the service client 2, and the background server 1 determines whether to approve the charging request according to the information included in the charging request instruction. Preferably, the user can utilize the camera of the intelligent terminal to read the bar code or the two-dimensional code information of the target charging pile, and then the identification information of the target charging pile to be connected is obtained.
2. And when the charging starting content is detected to be selected, acquiring a charging starting operation event, and sending a charging starting instruction to the background server.
The charging initiation content may be selected only when the charging request command sent by the service client 2 is granted. Specifically, the service client 2 may display the charging start content after receiving the corresponding agreement instruction returned by the background server 1; or, after the service client 2 receives a corresponding agreement instruction returned by the background server 1, it starts to detect whether the charging start content is selected. After receiving the charging starting instruction sent by the service client 2, the background server 1 sends the charging starting instruction to the target charging pile, and the target charging pile charges the electric vehicle.
3. When the charging stop content is detected to be selected, a charging stop operation event is acquired, and a charging stop instruction is sent to the background server 1.
After receiving the charging stop instruction sent by the service client 2, the background server 1 sends the charging stop instruction to the target charging pile, and deducts the corresponding charging cost of the user logging in the service client 2. And after the target charging pile receives the charging stop instruction, stopping charging the electric automobile.
4. When the charging monitoring content is detected to be selected, a charging monitoring operation event is acquired, and a charging monitoring instruction is sent to the background server 1.
And the background server 1 acquires the running state of the target charging pile after receiving the charging monitoring instruction sent by the service client 2.
And the service client 2 is further configured to receive and display service information corresponding to the corresponding instruction sent by the background server 1.
After the background server 1 agrees with the charging request sent by the service client 2, an agreement instruction is sent to the service client 2, the agreement instruction comprises information prompting a user to connect a charging gun to the electric vehicle, and after the agreement instruction is received by the service client 2, text information of 'please connect the charging gun' is displayed, or picture or video information of the charging gun connected with the electric vehicle is displayed. After rejecting the charging request sent by the service client 2, the background server 1 sends a rejection instruction to the service client 2, wherein the rejection instruction contains user balance information or target charging pile state information. And after the service client receives the rejection instruction, displaying corresponding image-text information. For example, "you have insufficient balance, please recharge", "charge pile is working", or "charge pile failure" and other text messages.
And the background server 1 receives a charging starting instruction of the service client and then acquires the charging gun connection state of the target charging pile. When the charging gun is in a connected state, the background server 1 sends a charging starting instruction to the target charging pile and sends a connection success instruction to the service client 2, and the service client 2 displays corresponding image-text information, such as 'charging' text information. When the charging gun is in an unconnected state, the background server 1 sends a connection failure instruction to the service client 2, and the service client 2 displays corresponding image-text information, for example, text information of "please reconnect the charging gun".
After receiving the charging stop instruction sent by the service client 2, the background server 1 performs corresponding processing, and sends information such as the charging fee to be deducted to the service client 2. The service client 2 displays information such as charging fee.
After receiving the charging monitoring instruction sent by the service client 2, the background server 1 acquires the operating state of the target charging pile and sends the operating state to the service client 2. And the service client 2 displays the running state of the target charging pile. The operation state of the target charging pile comprises data such as output voltage and output current.
The following is an embodiment of the method of the present invention, and for details not disclosed in the embodiment of the method of the present invention, please refer to the embodiment of the system of the present invention.
Referring to fig. 2, a flowchart of an electric vehicle charging processing method according to an embodiment of the present invention is shown, where the electric vehicle charging processing method is applied to a service client, and the electric vehicle charging processing method may include the following steps:
step S11: displaying the charging service content;
step S12: acquiring an operation event finished by a user aiming at the charging service content, and sending a corresponding instruction to the background server;
step S13: and receiving and displaying the service information which is sent by the background server and corresponds to the operation event.
The embodiment provides a charging processing method for an electric vehicle, which includes acquiring, by a service client, an operation event completed by a user for charging service content, sending a corresponding instruction to a background server, receiving and displaying service information corresponding to the corresponding instruction sent by the background server. The service client is used as a starting and managing tool of the charging pile, so that a charging point card does not need to be carried about for an electric vehicle owner, multiple card swiping operations are not needed for completing charging of the electric vehicle, and the electric vehicle can be charged conveniently only through the operation of the service client; for the charging operation mechanism, fixed office places for handling charging card services can be reduced, and the cost of manpower and material resources is reduced.
The obtaining of the operation event completed by the user for the charging service content and sending the corresponding instruction to the background server optionally include:
when charging request content included in the charging service content is detected to be selected, acquiring a charging request operation event, and sending a charging request instruction to the background server;
when charging starting content included in the charging service content is detected to be selected, acquiring a charging starting operation event, and sending a charging starting instruction to the background server;
and when the charging stopping content included in the charging service content is detected to be selected, acquiring a charging stopping operation event, and sending a charging stopping instruction to the background server.
The acquiring an operation event completed by the user for the charging service content and sending a corresponding instruction to the background server may further include:
and when detecting that the charging monitoring content included in the charging service content is selected, acquiring a charging monitoring operation event, and sending a charging monitoring instruction to the background server.
Referring to fig. 3, a flowchart of an electric vehicle charging processing method according to another embodiment of the present invention is shown, and the electric vehicle charging processing method is exemplified by being applied to the implementation environment shown in fig. 1, and the electric vehicle charging processing method may include the following steps:
step S211: the service client displays charging service content;
step S212: a service client acquires a user charging request operation event;
step S213: the service client sends a charging request instruction to the background server;
step S214: the background server preliminarily judges whether to approve the charging request according to the charging request instruction, if not, the step S215 is executed, and if yes, the step S217 is executed;
the background server can store a user blacklist, a trade unsettled list and a normal charging pile list. After receiving the charging request instruction, the background server judges whether the user identifier included in the charging request instruction exists in a user blacklist or a transaction unsettled list, and judges whether the target charging pile identifier exists in a normal charging pile list. And if the user identification is not in the user blacklist, is not in the transaction unsettled list and the target charging pile identification is in the normal charging pile list, the charging request is agreed, and if the user identification is in the user blacklist or the transaction unsettled list or the target charging pile identification is not in the normal charging pile list, the charging request is not agreed. The user blacklist stores the logout user identification and the user identification of which the arrearage amount is greater than a preset threshold value. The list of outstanding transactions stores the identity of the user for which the transaction is outstanding. The charging pile identifier without faults is stored in a normal charging pile list.
And if the account balance corresponding to the user identification is greater than the preset account balance threshold value, the user identification is not in a user blacklist and a transaction unsettled list, and the target charging pile identification is in a normal charging pile list, the charging request is agreed, otherwise, the charging request is not agreed. For example, setting the account balance threshold to 50 dollars.
And whether the time interval between the sending time of the last charging request instruction corresponding to the user identification and the sending time of the current charging request instruction is larger than a preset time interval threshold value or not can be additionally judged in the judging condition, if the time interval is larger than the preset time interval threshold value, the user identification is not in a user blacklist and is not in a transaction unsettled list, and the target charging pile identification is in a normal charging pile list, the current charging request is agreed, otherwise, the current charging request is not agreed. For example, the set time interval threshold is set to 10 minutes. Avoid same user to occupy for a long time and fill electric pile.
The method can also be used for judging whether the time interval between the last charging request instruction sending time corresponding to the user identification and the current charging request instruction sending time is larger than a preset time interval threshold or not and judging whether the account balance corresponding to the user identification is larger than a preset account balance threshold or not, if the time interval between the last charging request instruction sending time corresponding to the user identification and the current charging request instruction sending time is larger than the preset time interval threshold, the account balance corresponding to the user identification is larger than the preset account balance threshold, the user identification is not in a user blacklist and is not in a transaction unsettled list and the target charging pile identification is in a normal charging pile list, the current charging request is agreed, otherwise, the current charging request is not agreed.
Step S215: the background server sends a rejection instruction to the service client;
step S216: the service client displays rejection information;
step S217: the background server sends a state acquisition request instruction to the target charging pile;
step S218: the target charging pile returns state information to the background server;
the state information of the target charging pile comprises idle state, warning state, charging state and unknown state. When the state information of the target charging pile is idle, the target charging pile can be normally charged, and the charging task can be received; when the state information of the target charging pile is an alarm, indicating that the target charging pile has a fault and cannot be normally charged, and not receiving the charging task; when the state information of the target charging pile is charging, the target charging pile indicates that the target charging pile is charging the electric automobile and cannot receive the charging task; if the state of the target charging pile is unknown, the target charging pile is in a disconnected network or other unknown conditions, and the charging task cannot be received.
Step S219: the background server judges whether to approve the charging request according to the state information of the target charging pile;
and when the state information of the target charging pile is idle, the charging request is agreed, and if the state information of the target charging pile is other (alarming, charging and unknown), the charging request is not agreed.
Step S220: and if the client side agrees, sending an agreement instruction to the client side, and if the client side disagrees, sending a rejection instruction to the client side.
Step S221: and the service client displays corresponding information.
Step S310: a service client acquires a user charging starting operation event;
step S311: the service client sends a charging starting instruction to the background server;
step S312: the background server sends a command for acquiring the connection state of the charging gun to the target charging pile;
step S313: the target charging pile sends charging gun connection state information to a background server;
the charging gun connection state information of the target charging pile includes connected and unconnected. If the charging gun connection state information of the target charging pile is connected, indicating that the charging gun of the target charging pile is connected with the electric automobile; and if the charging gun connection state information of the target charging pile is not connected, indicating that the charging gun of the target charging pile is not connected with the electric automobile.
Step S314: the background server judges whether the charging condition is met or not according to the charging gun connection state information, if not, the step S315 is executed, and if so, the step S317 is executed;
when the charging gun connection state information of the target charging pile is connected, determining that the charging condition is met; and when the charging gun connection state information of the target charging pile is not connected, determining that the charging condition is not met.
Step S315: the background server sends a connection failure instruction to the service client;
step S316: the service client displays the connection failure information;
step S317: the background server sends a charging starting instruction to the target charging pile;
step S318: the target charging pile sends a charging starting instruction to a background server;
step S319: the background server sends a connection success instruction to the service client;
step S320: and the service client displays the connection success information.
Step S410: a service client acquires a charging monitoring operation event of a user;
step S411: the service client sends a charging monitoring instruction to the background server;
step S412: the background server sends an instruction for acquiring the running state to the target charging pile;
step S413: the target charging pile sends running state information to a background server;
the preset rule may be that after receiving the operation state acquisition instruction, the target charging pile continuously sends operation state information to the background server until receiving a charging stop instruction or a monitoring stop instruction; and the background server processes the received running state information and continuously sends the running state information to the service client, and the service client displays the running state information of the target charging pile. The preset rule may also be that after receiving the operation state acquisition instruction, the target charging pile sends operation state information to the background server in a short time (for example, 3s), the background server processes the received operation state information and sends the processed operation state information to the service client, and the service client displays the operation state information of the target charging pile; the user can send the charging monitoring instruction through the service client for multiple times in the charging process.
Step S414: the background server sends running state information to the service client;
step S415: and the service client displays the running state information of the target charging pile.
Step S510: a service client acquires a user charging stop operation event;
step S511: the service client sends a charging stop instruction to the background server;
step S512: the background server sends a charging stop instruction to the target charging pile;
step S513: the target charging pile stops charging the electric automobile;
step S514: the target charging pile sends the charging electric quantity and the charging duration information to a background server;
step S515: and the background server calculates the charging cost and deducts the corresponding charging cost of the user logging in the service client.
The background server stores charging unit price and service fee unit price. Charging capacity, charging unit price and charging duration, service fee unit price and charging fee. And the background server modifies the account balance corresponding to the user identification into the current account balance-charging cost. And if the modified account balance is less than zero and greater than a preset threshold value, storing the user identification in a transaction unsettled list, and if the modified account balance is less than the preset threshold value, storing the user identification in a transaction blacklist.
Step S516: the background server sends information such as charging cost to the service client;
step S517: and the service client displays information such as charging cost and the like.
The service client displays information such as charging cost and the like, including but not limited to charging cost, charging amount, charging duration, charging unit price, service fee unit price and account balance.
While, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present invention is not limited by the illustrated ordering of acts, as some steps may occur in other orders or concurrently with other steps in accordance with the invention.
The following are embodiments of the apparatus of the present invention that may be used to perform embodiments of the method of the present invention. For details which are not disclosed in the embodiments of the apparatus of the present invention, reference is made to the embodiments of the method of the present invention.
Referring to fig. 4, a schematic diagram of an electric vehicle charging processing apparatus according to an embodiment of the present invention is shown, where the electric vehicle charging processing apparatus may be applied to a service client, and the electric vehicle charging processing apparatus may include: a first display unit 11, an event acquisition unit 12, a content reception unit 13, and a second display unit 14;
a first display unit 11, configured to display charging service content;
an event obtaining unit 12, configured to obtain an operation event completed by a user for the charging service content, and send a corresponding instruction to the background server;
a content receiving unit 13, configured to receive service information corresponding to the operation event sent by the background server;
and a second display unit 14, configured to display the service information.
The embodiment provides an electric vehicle charging processing device, which obtains an operation event completed by a user for charging service content through a service client, sends a corresponding instruction to a background server, receives service information corresponding to the corresponding instruction sent by the background server, and displays the service information. The service client is used as a starting and managing tool of the charging pile, so that a charging point card does not need to be carried about for an electric vehicle owner, multiple card swiping operations are not needed for completing charging of the electric vehicle, and the electric vehicle can be charged conveniently only through the operation of the service client; for the charging operation mechanism, fixed office places for handling charging card services can be reduced, and the cost of manpower and material resources is reduced.
Optionally, the event obtaining unit 12 specifically includes:
a first event obtaining subunit 121, configured to, when it is detected that charging request content included in the charging service content is selected, obtain a charging request operation event, and send a charging request instruction to the background server;
a second event obtaining subunit 122, configured to, when it is detected that the charging start content included in the charging service content is selected, obtain a charging start operation event, and send a charging start instruction to the background server;
a third event obtaining subunit 123, configured to, when it is detected that the charging stop content included in the charging service content is selected, obtain a charging stop operation event, and send a charging stop instruction to the background server.
Optionally, the event obtaining unit 12 further includes:
a fourth event obtaining subunit 124, configured to, when it is detected that the charging monitoring content included in the charging service content is selected, obtain a charging monitoring operation event, and send a charging monitoring instruction to the background server.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.