Charging method, electronic equipment and computer readable storage medium

Abstract

The invention provides a charging method, electronic equipment and a computer readable storage medium, and relates to the technical field of charging. Based on the connection between the charging end and the to-be-authenticated end, judging whether the charging end supports plug-and-play charging or not; if the charging end supports plug-and-play charging, the authentication end detects the code scanning charging behavior of the user; if the authentication end detects the code scanning charging behavior of the user, the charging end charges the to-be-authenticated end; if the authentication end does not detect the code scanning charging behavior of the user, the charging end uploads an authentication code to the authentication end for authentication; and under the condition that the authentication of the authentication code is passed, the charging end charges the to-be-authenticated end. And if the authentication code is uploaded to the authentication end and the authentication code does not pass, the code scanning charging behavior of the user is still detected, and authentication is tried again. According to the invention, an authentication mechanism is optimized, the conflict between code scanning and a VIN authentication time sequence is solved under the condition of conforming to related standards (such as national standards), the dependence on a touch screen is reduced, and low-cost and safe charging starting is realized.

Description

Technical Field

[0001] The present application provides a charging method, an electronic device, and a computer-readable storage medium, which relate to the field of charging technology, and in particular to the field of charging technology for new energy vehicles. Background Art

[0002] With the popularity of electric vehicles, the plug-and-play charging method of non-on-board chargers has become a key technology to improve user experience. In this way, users only need to insert the charging gun into the car charging port to start the charging process, without the need for additional code scanning or card swiping operations. However, the current mainstream technology requires users to manually select the scan code or VIN code to start the charging method through the touch screen equipped with the charging pile after plugging the gun, which increases the hardware cost and fails to achieve a true plug-and-play experience. At the same time, for vehicles that have not activated the VIN plug-and-play function, once the platform receives the VIN authentication instruction, it usually directly refuses authentication, resulting in charging startup failure, thereby increasing the startup failure rate of the operating station.

[0003] The existing technical solutions require that the vehicle-pile communication support a private protocol in the control logic of attempting to be compatible with scanning code charging and VIN-started charging. This is not common in new energy vehicles on the market, limiting its application in different brands of vehicles and chargers. More importantly, this logic of plugging in the gun to identify the VIN code poses a compatibility risk for BMS communication across brands of vehicles. Therefore, the charging control or charging authentication methods in the prior art have the problems of low compatibility and low authentication / charging start efficiency. Summary of the invention

[0004] In view of this, the purpose of the embodiments of the present application is to provide a charging method to improve the problems of high cost, timing conflict between code scanning and VIN authentication, and reduce touch screen dependence in the prior art, so as to achieve low-cost, high-compatibility, and safe charging startup. In view of the shortcomings of the prior art, the charging method provided by the present application optimizes the authentication mechanism, solves the problem of timing conflict between code scanning and VIN authentication, provides users with a smoother and more reliable charging experience, and significantly improves the startup success rate of the charging system.

[0005] Specifically, an embodiment of the present application provides a charging method, which is applied to a charging system including a charging end, an authentication end and an end to be authenticated; the method includes: based on the connection between the charging end and the end to be authenticated, judging whether the charging end supports plug-and-charge; if the charging end supports plug-and-charge, the authentication end detects the user's charging behavior of scanning a code; if the authentication end detects the user's charging behavior of scanning a code, the charging end charges the end to be authenticated; if the authentication end does not detect the user's charging behavior of scanning a code, the charging end uploads an authentication code to the authentication end for authentication; and if the authentication code authentication passes, the charging end charges the end to be authenticated.

[0006] In the above implementation process, the charging end is connected to the end to be authenticated, and after determining that the charging end supports plug-and-charge, it waits for charging to start. The user scanning the code indicates that the user has a charging demand. After the authentication end detects the user's scanning charging behavior, it starts charging; if the charging end supports plug-and-charge, but does not detect the user's scanning behavior, the charging end uploads the authentication code to the authentication end; the authentication end receives the authentication code and compares it with the valid authentication code in the database. If the authentication code is verified, the authentication end sends a charging start instruction to the charging end, and the charging end starts charging after receiving the charging start instruction. Charging can be started smoothly through both plug-and-charge and scanning charging, reducing charging failures caused by improper operation or device incompatibility. At the same time, by distinguishing the timing of plug-and-charge and scanning charging, conflicts between the two are avoided.

[0007] Optionally, the charging of the terminal to be authenticated by the charging terminal includes: the authentication terminal sends a charging start instruction to the charging terminal; and the authentication terminal generates a charging order based on the charging start instruction sent to the charging terminal; wherein the charging order includes a corresponding charging order number; after the charging terminal receives the charging start instruction sent by the authentication terminal, within a first time period, the charging terminal sends a response message to the authentication terminal; wherein the response message includes a charging start result; if the authentication terminal does not receive the charging start result, the authentication terminal will send the charging start instruction to the charging terminal again and suspend the charging order; wherein the two charging order numbers sent by the authentication terminal are consistent.

[0008] In the above implementation process, after confirming that the user authentication is successful, the authentication end sends a start charging instruction to the charging end. The authentication end generates a charging order based on the issued start charging instruction, and the order contains a unique charging order number. At the same time, after receiving the start charging instruction, the charging end starts to perform the charging operation. In the first period, the charging end needs to report the start charging result to the authentication end and send a response message to the authentication end. If the authentication end does not receive the start charging result of the charging end within the specified time, the authentication end will send the start charging instruction to the charging end again and keep the charging order suspended. Even if the authentication end needs to resend the start charging instruction, the charging order number remains unchanged, making the order continuous and traceable. Through timely response messages, it can indicate to the user that the charging request has been received and processed, and make the waiting time visible. The system design takes into account the possibility of communication failure, and takes corresponding measures to ensure the smooth progress of the charging process. Through the retransmission mechanism, the success rate of charging startup is improved.

[0009] Optionally, the response message includes an information field; the information field may be filled with a code indicating a first type of charging order or a code indicating a second type of charging order.

[0010] In the above implementation process, the response message contains one or more information fields for transmitting additional order information. The information field may contain a code indicating a first-class charging order or a code indicating a second-class charging order. The charging end fills the corresponding code in the information field in the response message according to the actual type of charging service provided, which is convenient for related configuration and statistical management of subsequent operations.

[0011] Optionally, the method further includes: if the authentication code authentication fails, the authentication end does not send the start charging instruction to the charging end; if the charging end does not receive the start charging instruction from the authentication end, reporting a timeout event and performing a reconnection operation.

[0012] In the above implementation process, if the authentication code authentication fails, the authentication end will not send a start charging instruction to the charging end, but wait for other actions to occur. While the charging end is waiting for the start charging instruction, if the preset time limit is exceeded, a timeout event will be detected. The charging end reports the timeout event to the authentication end for problem diagnosis and processing. After detecting the timeout, the charging end will automatically try to reconnect to the end to be authenticated to maintain communication between the end to be authenticated and the charging end. These measures help ensure that only verified users can use the charging service, and when the start charging instruction is not received (it may be due to unstable network connection or problems with the authentication end), the system can automatically detect and try to maintain communication with the end to be authenticated through timeout reporting and reconnection operations, thereby reducing charging interruptions caused by hardware communication or network communication problems.

[0013] Optionally, the reporting of the timeout event and the reconnection operation include: when the charging end has not received the start charging instruction from the authentication end after a second time period, the charging end reports the timeout event to the authentication end, and continues to send a not ready instruction to the end to be authenticated, waiting for the end to be authenticated to send a timeout message; the charging end receives the timeout message sent by the end to be authenticated, and sends an identification message to perform the reconnection operation, and detects whether the authentication end has sent the start charging instruction.

[0014] In the above implementation process, if the charging end still does not receive the charging start instruction from the authentication end after the second time period, a timeout event will be detected. The charging end reports the timeout event to the authentication end, indicating that the current charging end has failed to receive the required charging start instruction. At the same time, it continues to send not ready instructions to the end to be authenticated, indicating that the charging end is not ready for charging operations. After receiving the timeout message sent by the end to be authenticated, the charging end sends an identification message to the end to be authenticated for reconnection. After this reconnection operation, the charging end continues to detect whether the authentication end has issued a charging start instruction. Even when the network connection is unstable or there is a problem with the authentication end, the charging end can try to resume normal charging operations by automatically reconnecting. At the same time, it also helps to maintain the security of the system and user satisfaction.

[0015] Optionally, the reconnection operation includes: when the charging end performs the reconnection operation, if the charging end receives the charging start instruction sent by the authentication end, it indicates that the reconnection operation is successful, and the charging end charges the end to be authenticated, and the charging end sends a response message to the authentication end; if the charging end still does not receive the charging start instruction sent by the authentication end, the reconnection operation is repeated; if the charging end performs the multiple reconnection operations but does not receive the charging start instruction, the charging process is terminated and the connection between the charging end and the end to be authenticated is released; at the same time, the charging order fails to start and no charging order number is generated.

[0016] In the above implementation process, when the charging end is performing a reconnection operation, if the charging end successfully receives the start charging instruction issued by the authentication end, it means that the reconnection operation is successful, the charging end starts to charge the end to be authenticated, and the charging end reports the startup result to the authentication end. At the same time, the charging end sends a response message to the authentication end to confirm that the start charging instruction has been received and charging has started. If the charging end still does not receive the start charging instruction issued by the authentication end after the reconnection operation, the reconnection operation is repeated. If the charging end performs multiple reconnection operations but does not receive the start charging instruction, the charging process is terminated and the connection between the charging end and the end to be authenticated is released. In this case, the charging order fails to start and the charging order number is not generated. By limiting the number of reconnections and setting a reasonable timeout time, system resources are prevented from being occupied for a long time, which causes other users to be unable to use the charging service, thereby improving resource utilization efficiency. At the same time, the startup failure rate of the operating station is avoided to be too high.

[0017] Optionally, if the authentication end detects that the user has unlocked the charging end, the connection between the end to be authenticated and the charging end is released.

[0018] In the above implementation process, the unlocking operation usually means that the user's demand is to end charging or move the charging gun. After the authentication end detects the unlocking behavior, the end to be authenticated releases the connection with the charging end, so that the end to be authenticated can be safely disconnected when the user unlocks the charging end, avoiding damage to the user or the device. In the prior art, once the charging process starts, the user is usually not allowed to disconnect the charging connection midway. If the user needs to move the vehicle urgently or interrupt charging for other reasons at this time, they may have to wait for the charging to end, or take measures to forcibly disconnect the connection. Forcibly disconnecting the charging connection may cause damage to the charging equipment or electric vehicles, increase maintenance costs, and there are safety hazards between people, vehicles and piles; if the user needs to interrupt charging, it may waste time because the system does not allow interruption. The solution proposed in this application enables the user to interrupt the charging process at any time by unlocking the charging gun, which improves the flexibility of the charging system. The charging end can safely disconnect from the end to be authenticated, avoiding damage to the device; the user does not need to wait for the charging process to end to interrupt charging, saving time.

[0019] The embodiment of the present application also provides a charging method, which is applied to a charging terminal, and includes: based on the connection between the charging terminal and the terminal to be authenticated, after the charging terminal receives the charging start instruction sent by the authentication terminal, the charging terminal reports the charging start result within a first time period, the charging terminal charges the terminal to be authenticated, and the charging terminal sends a response message to the authentication terminal; if the charging terminal still does not receive the charging start instruction from the authentication terminal after a second time period, the charging terminal reports a timeout event to the authentication terminal, continuously sends a not ready instruction to the terminal to be authenticated, and waits for the terminal to be authenticated to send a timeout message; After receiving the timeout message sent by the end to be authenticated, the charging end sends an identification message to perform a reconnection operation, and detects the start charging instruction sent by the authentication end; when the charging end performs the reconnection operation and receives the start charging instruction sent by the authentication end, it is determined that the reconnection operation is successful, and the charging end charges the end to be authenticated, and the charging end sends a response message to the authentication end; when the charging end performs the reconnection operations for multiple times but does not receive the start charging instruction, the charging end terminates the charging process and releases the connection with the end to be authenticated.

[0020] In the above implementation process, after receiving the start charging instruction sent by the authentication end, the charging end will complete the start charging within the first time period and report the result, and the charging end will send a response message to the authentication end. If the start charging instruction is still not received at the end of the second time period, the charging end will report a timeout event and continue to send a not ready instruction, waiting for the timeout message from the end to be authenticated. Once the timeout message is received, the charging end sends an identification message to try to reconnect, and detects whether the authentication end has issued a start charging instruction. If the reconnection is successful and the start charging instruction is received, it means that the reconnection operation is successful, and the end to be authenticated continues to charge, and a response message is sent to the authentication end. If the charging end still does not receive the start charging instruction after multiple reconnection attempts, the charging process will be terminated and the connection with the end to be authenticated will be released. The entire process design is designed to improve the reliability and safety of the charging operation, and respond to the user's operation instructions in a timely manner to optimize the user experience.

[0021] An embodiment of the present application further provides an electronic device, which includes a memory and a processor, wherein the memory stores program instructions, and when the processor reads and runs the program instructions, the steps in any of the above implementation methods are executed.

[0022] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the steps in any of the above implementation methods are executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 A flow chart of a charging method provided in an embodiment of the present application;

[0025] Figure 2 Flowchart A of the charging end charging the authentication end provided in the embodiment of the present application;

[0026] Figure 3 Flowchart B of the charging end charging the authentication end provided in the embodiment of the present application;

[0027] Figure 4 An overall flow chart of the charging method provided in the embodiment of the present application when the authentication code fails;

[0028] Figure 5 Flowchart A of the charging method provided in the embodiment of the present application when the authentication code fails;

[0029] Figure 6 Flowchart B of the charging method provided in the embodiment of the present application when the authentication code fails;

[0030] Figure 7 Flowchart C of the charging method provided in the embodiment of the present application when the authentication code fails;

[0031] Figure 8 Flowchart D of the charging method provided in the embodiment of the present application when the authentication code fails;

[0032] Fig. 9 A flow chart of a charging method applied to a charging terminal provided in an embodiment of the present application;

[0033] Fig.10 The embodiment of the present application provides a multi-terminal interaction diagram A that supports plug-and-play charging and user code scanning;

[0034] Fig.11 The embodiment of the present application provides a multi-terminal interaction diagram B that supports plug-and-play charging and user code scanning;

[0035] Fig.12 The multi-terminal interaction diagram provided by the embodiment of the present application where the user has not scanned the code and the authentication has been passed;

[0036] Fig.13 The multi-terminal interaction diagram provided in the embodiment of the present application where the user fails to scan the code and the authentication fails;

[0037] Fig.14 An electronic device provided in an embodiment of the present application;

[0038] Fig.15 An embodiment of the present application provides a computer-readable storage medium.

[0039] Icon: 000 - user terminal; 100 - electronic device; 111 - memory; 112 - storage controller; 113 - processor; 114 - peripheral interface; 115 - input and output unit; 116 - display unit. DETAILED DESCRIPTION

[0040] The technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments of the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the embodiments of the present application.

[0041] The embodiment of the present application provides a charging method, which is applied to a charging system including a charging end, an authentication end and an end to be authenticated; the method includes: based on the connection between the charging end and the end to be authenticated, the authentication end detects the user's charging behavior of scanning a code; if the authentication end detects the user's charging behavior of scanning a code, it determines whether the charging end supports plug-and-charge; if it is determined that the charging end supports plug-and-charge, the charging end charges the end to be authenticated; if the authentication end does not detect the user's charging behavior of scanning a code, the authentication code is uploaded to the authentication end through the charging end for authentication; and when the authentication code authentication passes, the charging end charges the authentication end.

[0042] See also Figure 1 , Figure 1 A flow chart of the charging method provided in an embodiment of the present application.

[0043] When the charging terminal is connected to the terminal to be authenticated, it is determined whether the charging terminal supports plug-and-play charging. If the charging terminal has enabled plug-and-play charging, the authentication terminal detects the user's charging behavior by scanning the code. Next, it is determined whether the authentication terminal has detected the user's charging behavior by scanning the code. If it is determined to be yes, that is, the authentication terminal has detected the user's charging behavior by scanning the code, the charging terminal will charge the terminal to be authenticated; if it is determined to be no, that is, the authentication terminal has not detected the user's charging behavior by scanning the code, the charging terminal will upload the authentication code to the authentication terminal. If it is determined that the authentication code is authenticated, the charging terminal will charge the terminal to be authenticated.

[0044] In the above implementation process, the charging end is connected to the end to be authenticated, and this connection can be a physical connection or a wireless connection. Based on this connection, the entire system (charging end, end to be authenticated and authentication end) starts the charging process; when the charging end is successfully connected to the end to be authenticated and the charging end supports plug-and-play charging, the authentication end detects the user's charging behavior of scanning the code. It can be understood that the user's scanning the code indicates that the user has a charging demand; after the authentication end detects the user's charging behavior of scanning the code, the charging end charges the end to be authenticated; if the authentication end does not detect the user's charging behavior of scanning the code, the charging end uploads the authentication code to the authentication end, the authentication end receives the authentication code, and compares it with the valid authentication code in the database. If the authentication code verification is passed, charging starts.

[0045] Optionally, if the charging end does not support plug-and-charge or the plug-and-charge function is not turned on, it is necessary to wait for other methods to start, such as starting charging after the user scans the code for interaction, charging with a card, or charging with authentication.

[0046] Exemplarily, the charging end can be a charging pile, charging station, charging socket or any device that can provide electricity, or it can be a control software or server embedded in the charging device, which is responsible for managing the charging process; the end to be authenticated usually refers to the device that needs to be charged, which can be an electric car, electric bicycle, mobile phone, laptop, etc., or it can be the charging interface of these devices or the built-in charging management software; the authentication end can be a central server, cloud service or any device responsible for processing authentication requests, or it can be a software system running the authentication program, which is responsible for verifying the user's identity and authorizing charging; the authentication code is used to verify the identity of both parties in communication. Only authorized devices or users can access specific resource services. It can be a string of numbers or characters, SMS verification code, dynamic code generated by the application, or a specific identifier in the user account. The application scenario can be charging electric vehicles for private piles at home, public parking lots, enterprise parks, wireless charging, commercial or logistics vehicles.

[0047] In one embodiment of the present application, the charging end may be an off-board charger, the end to be authenticated may be an electric vehicle that needs to be charged, and the authentication end may be a central server or cloud platform, which is responsible for processing authentication and billing. The authentication code may come from the vehicle VIN, unique code, key, and other data that can prove the identity of the end to be authenticated. Insert the charging gun into the charging port of the vehicle, and the charging pile and the electric vehicle establish a secure communication connection through the built-in communication protocol. The electric vehicle sends its identity information to the charging pile, and the charging pile verifies the accuracy of this information by uploading its identity information to the platform. After the platform confirms the identity and charging authority of the electric vehicle user, the charging pile starts charging the electric vehicle. After charging is completed, the platform can automatically perform billing and settlement based on the charging amount and rate.

[0048] For details on the steps for the charging end to support plug-and-play charging and for the charging end to charge the authentication end, please refer to Figure 2 , Figure 2 Flowchart A of the charging end charging the authentication end provided in the embodiment of the present application.

[0049] Based on the connection between the charging end and the end to be authenticated, the charging end determines whether it has enabled plug-and-charge. If the charging end enables plug-and-charge, and meets the condition that the user scans the code or the authentication code is passed, the charging end will charge the end to be authenticated. At this time, the authentication end sends a start charging instruction to the charging end. The charging end determines whether the start charging instruction has been received. If so, it is determined to be yes and the next step is performed. The authentication end generates a charging order containing a unique order number. After receiving the instruction, the charging end sends a response message to the authentication end within the first time period, and the charging end starts to charge the end to be authenticated. If it is determined that the authentication end has not received the response message from the charging end, it will send a start charging instruction to the charging end again. While the instruction is resent, the charging order will be suspended, which means that the order will be temporarily shelved and await further instructions.

[0050] In the above implementation process, the charging end is connected to the end to be authenticated. Based on this connection, the entire system (charging end, end to be authenticated and authentication end) starts the charging process; and when the charging end determines that it supports plug-and-play charging and satisfies the detection of the user scanning code or authentication code, the charging end charges the end to be authenticated, and the authentication end will issue a start charging instruction to the charging end at this time; the authentication end generates a charging order based on the start charging instruction issued to the charging end; then, the charging end determines whether the start charging instruction issued by the authentication end is received; if the charging end receives the start charging instruction issued by the authentication end, then within the first time period, the charging end sends a response message to the authentication end, and after the charging end sends a ready message to the end to be authenticated, the charging end charges the end to be authenticated; the authentication end determines whether the response message from the charging end is received. If the authentication end does not receive the response message from the charging end, the authentication end will issue a start charging instruction to the charging end again and suspend the charging order. Once the charging end is reconnected and confirms that the start charging instruction has been received, the charging order can be restored from the suspended state and the charging process can continue. The entire charging process is automated, reducing manual intervention and improving efficiency. Users can track the charging status through the charging order number, increasing the transparency of the service.

[0051] Optionally, possible operations for a suspended order include: the status of the charging order will be updated to "suspended" to indicate that the current order has not been completed, the billing associated with the charging order may be suspended until the charging process can continue, the system may record an event log indicating the reason and time the order was suspended, the system may attempt to reestablish a connection with the charging terminal in order to resend charging instructions, and if applicable, the system may notify the user that the charging order is suspended and provide further instructions.

[0052] Specifically, see Figure 3 , Figure 3 Flowchart B of the charging end charging the authentication end provided in the embodiment of the present application.

[0053] Step S210: the authentication end sends a charging start instruction to the charging end; the authentication end generates a charging order based on the charging start instruction sent to the charging end.

[0054] In the above step S210, after confirming that the user authentication is successful, the authentication end sends a charging start instruction to the charging end, and the authentication end generates a charging order based on the issued charging start instruction. The charging order contains necessary information, such as user information, charging amount, cost, charging time, etc. At the same time, each charging order will be assigned a unique charging order number, which is used for subsequent order tracking, billing and user query.

[0055] Step S220: After the charging terminal receives the charging start instruction sent by the authentication terminal, the charging terminal sends a response message to the authentication terminal within the first time period.

[0056] In the above step S220, after the charging terminal receives the charging start instruction, it starts to execute the charging operation. During the first period, the charging terminal needs to report the charging start result to the authentication terminal and send a response message to the authentication terminal. The response message usually contains charging status information, such as charging has started, charging pile number, charging time, etc. It is possible that when charging fails to start successfully, the charging terminal needs to explain the reason in the response message and take corresponding error handling measures. During the charging process, the charging terminal continuously monitors the charging status and pays attention to charging safety and efficiency.

[0057] In one embodiment of the present application, the response message includes the result of starting charging, clearly indicating whether charging has been successfully started, and serves as an identification indicator for subsequent processes. The response message also includes an information field; the information field can be filled with a code indicating a first type of charging order or a code indicating a second type of charging order. Optionally, the code in the information field is used to distinguish different types of charging orders, so that the authentication end can execute different subsequent processes or count different types of opening states according to the order type; different levels of service can be provided according to the type of charging order, such as priority charging, preferential charging rates, etc.; or different types of charging orders may have different billing strategies, and the information field helps the authentication end determine the applicable billing rules; the charging station can optimize resource allocation according to the order type, such as reserving high-power charging piles for fast charging orders.

[0058] Optionally, the response message may have a header and fields, wherein the header may include the message type, the total byte length of the message and a serial number that uniquely identifies this communication; the fields may contain information such as charging results, charging order number, information field, charging timestamp, charging power, charging power, user identification, etc., wherein the charging order number is unique, and the information field 01 represents the first type of charging order, 02 represents the second type of charging order, and so on.

[0059] In one embodiment of the present application, the first type of charging order may be a charging order that is initiated by scanning a code when plug-and-charge is not enabled, and the second type of order may be a charging order that is initiated by the plug-and-charge function.

[0060] Step S230: If the authentication end does not receive the charging start result, the authentication end will send a charging start instruction to the charging end again and suspend the charging order;

[0061] In the above step S230, if the authentication end does not receive the charging start result from the charging end within the specified time, the authentication end will reissue the charging start instruction to the charging end and keep the charging order suspended. Even if the authentication end needs to reissue the charging start instruction, the charging order number remains unchanged, so that the order has continuity and traceability. Optionally, the authentication end records the operation of each re-issuance of the instruction, including the time, reason and result; if no response is received after multiple re-sending of the instruction, the authentication end will start the error handling procedure; the authentication end may need to notify the user of the current charging status and any delays; if there are continuous failures, the authentication end may trigger a system alarm to remind the management staff to check.

[0062] See also Figure 4 , Figure 4 This is an overall flow chart of the charging method provided in an embodiment of the present application when the authentication code fails.

[0063] If the authentication code authentication fails, the authentication end does not send the charging start instruction to the charging end, and determines whether the charging end has received the charging start instruction after the second period. If the charging end receives the charging start instruction, it means that the reconnection is successful, the charging end charges the end to be authenticated, and the charging end sends a response message to the authentication end; if the charging end does not receive the charging start instruction, the charging end reports the timeout event to the authentication end, and the charging end continues to send the not ready instruction to the end to be authenticated, waiting for the end to be authenticated to send a timeout message; after the charging end receives the timeout message sent by the end to be authenticated, it sends an identification message to the end to be authenticated; during this process, the charging end continues to detect the user's unlocking behavior. If the charging end detects the user's unlocking behavior, the charging end will release the connection with the end to be authenticated; if the charging end does not detect the user's unlocking behavior during this process, the charging end sends an identification message for reconnection. Even in the case of unstable network or other communication problems, the system can still try to maintain operation, which enhances the system's fault tolerance. For users, if authentication fails, the charging terminal will not wait in vain, but will report the timeout event in time, avoiding long waiting times for users; even if the authentication code fails, the reconnection mechanism provides users with the possibility to continue charging attempts instead of directly terminating the service. At the same time, for operators, by implementing the reconnection operation, the system can automatically try to re-establish the communication connection, reducing charging failures caused by temporary communication failures. The automated reconnection mechanism also reduces the number of times operators need to intervene to deal with communication problems, reducing labor costs.

[0064] Specifically, see Figure 5 , Figure 5 Flowchart A of the charging method provided in the embodiment of the present application when the authentication code fails.

[0065] Step S410: If the authentication code fails to be authenticated, the authentication end does not send a charging start instruction to the charging end.

[0066] In the above step S410, if the authentication code authentication fails, the authentication end will not send a charging start instruction to the charging end, but wait for other actions to occur without understanding the user's startup intention, allowing the system to re-evaluate resource allocation after authentication failure and give priority to verified user requests. While preventing unauthorized users from starting charging and protecting charging facilities from illegal access, the charging process can only start after the user correctly expresses the charging intention and passes the verification, avoiding unnecessary charging caused by misoperation or incorrect input of the authentication code, and saving resources.

[0067] Alternatively, the situation where the user's start intention is not understood may be that the user is standing in front of the charging pile, and may be considering whether to use the plug-and-charge service or scan the code to charge. At this time, the user does not immediately take action and the intention is unclear; the user receives an emergency call or is distracted by other things after plugging the gun, causing them to not immediately take the next step, such as scanning the code, entering the authentication code, or directly communicating with the authenticated end to obtain the authentication code; users who use the charging pile for the first time may not be familiar with the charging process, and they may need time to read the sign or find the charging start option after plugging the gun; the user may be comparing the costs of different charging options, or waiting for coupons and discounts, so they do not start charging immediately after plugging the gun. In these cases, the charging system re-evaluates resource allocation and user intention by waiting for further user behavior, such as scanning the code, entering the authentication code, or unlocking the charging gun. This design can prevent unauthorized charging startup, while allowing the system to flexibly adjust according to user behavior and system status after authentication fails, and resources are preferentially allocated to verified user requests.

[0068] Step S420: When the charging end does not receive the charging start instruction from the authentication end, the charging end reports a timeout event and performs a reconnection operation.

[0069] In the above step S420, when the charging terminal is waiting for the charging start instruction, if the preset time limit is exceeded, a timeout event will be detected. The charging terminal reports the timeout event to the authentication terminal for problem diagnosis and processing. After detecting the timeout, the charging terminal will automatically try to reconnect to the authentication terminal to restore communication. An automatic recovery mechanism is provided when communication fails to reduce system downtime. At the same time, charging will not be started when the user's intention cannot be verified to prevent unauthorized charging.

[0070] Optionally, the charging end attempts to reestablish a connection with the authentication end, which may include resending a network request, reestablishing a communication session, etc.; the charging end may notify the user of the current status, including timeouts and reconnection attempts, through a display screen or other means.

[0071] For details about reconnection operations, see Figure 6 , Figure 6 Flowchart B of the charging method provided in the embodiment of the present application when the authentication code fails.

[0072] Step S510: When the charging end has not received the charging start instruction from the authentication end after the second period, the charging end reports a timeout event to the authentication end, and continues to send a not ready instruction to the end to be authenticated, waiting for the end to be authenticated to send a timeout message.

[0073] In the above step S510, the system will start a timer and enter the waiting stage of the second period. This stage is the extra time left by the charging end for the authentication end to respond. If the charging end still does not receive the start charging instruction from the authentication end at the end of the second period, the charging end will detect a timeout. The charging end will report the timeout event to the authentication end, informing the authentication end that it has not received the start charging instruction within the expected time. The charging end will continue to send a not ready instruction to the end to be authenticated, indicating that the charging end is not ready for charging at present. At the same time, it will wait for the timeout message from the end to be authenticated. By continuously reporting the not ready status after the timeout, the authentication end will understand the current charging status and will not mistakenly believe that charging has started due to the lack of updated real-time status.

[0074] As an example, the length of the second period can be determined as follows: the initial setting can be based on industry standards or experience data from similar systems to set an initial value; testing and adjustment are performed through actual operation tests and adjustments are made based on system performance and user feedback; or the system can dynamically adjust the timeout based on real-time network conditions and historical data. For example, if a charging station finds in actual operation that the authentication process usually takes 5-10 seconds, but occasionally takes 20 seconds due to network fluctuations, then the timeout for the second period can be set to 30 seconds, so that there is enough time to handle most situations, while also taking into account abnormal situations. The preferred time length may be in the following range: a shorter time, such as 15-30 seconds, is suitable for environments with fast system response speed and good network conditions. A medium time, such as 1-2 minutes, is suitable for situations where communication with a remote server is required or the system has low processing power. A longer time, such as 5 minutes or more, is suitable for situations where the network condition is unstable or complex authentication is required. The final determined time length should be able to improve the stability and security of the system while ensuring user experience. By setting the timeout period appropriately, charging stations can effectively manage charging resources, reduce unnecessary waiting time, and allow only verified users to initiate the charging process.

[0075] Step S520: the charging end receives the timeout message sent by the end to be authenticated, and sends an identification message to reconnect, and detects whether the authentication end sends a charging start instruction.

[0076] In the above step S520, after receiving the timeout message, the charging end sends an identification message to the end to be authenticated, requesting to re-establish the connection or confirm the status of the end to be authenticated. The charging end attempts to re-establish a stable communication connection with the end to be authenticated. During the reconnection process, the charging end continuously detects whether the authentication end has issued a command to start charging. By continuously sending the not ready command, the charging end keeps the communication channel with the end to be authenticated active, which helps to discover and solve problems in a timely manner. By sending an identification message, the charging end actively tries to restore the connection with the end to be authenticated, demonstrating the system's initiative and its ability to maintain stable operation and self-recovery in the face of abnormal situations.

[0077] Optionally, if the initial communication channel fails, the charging end can try to establish a connection with the authentication end through a different communication channel (such as switching network frequency, using a backup network, etc.); if the authentication end continues to fail to respond, the charging end can automatically switch to a backup authentication server or use a preset fault switching strategy; provide detailed status information on the user interface of the charging end, such as "waiting for start instructions", "communication timeout", etc., so that the user can understand the current status; dynamically adjust the timeout time according to network conditions and historical data to adapt to different network environments and usage scenarios.

[0078] For the follow-up of the reconnection operation, see Figure 7 , Figure 7 Flowchart C of the charging method provided in the embodiment of the present application when the authentication code fails.

[0079] Step S610: When the charging terminal performs a reconnection operation, if the charging terminal receives the charging start instruction sent by the authentication terminal, it means that the reconnection is successful. At this time, the charging terminal charges the authentication terminal and sends a response message to the authentication terminal.

[0080] In the above step S610, when the charging end is performing the reconnection operation, if the charging end successfully receives the charging start instruction sent by the authentication end, it means that the reconnection operation is successful. At this time, the charging end continues to communicate with the end to be authenticated until entering the charging stage, until the charging end starts to charge the end to be authenticated. The charging end reports the startup result to the authentication end, and at the same time, sends a response message to confirm that the charging start instruction has been received and charging has started.

[0081] Optionally, the charging end continuously monitors the charging process and sends charging status updates to the authentication end when necessary; the charging end may notify the user that charging has started by other means.

[0082] In one embodiment of the present application, the charging terminal does not need to have a touch screen but is replaced by an APP. The other methods mentioned here may be sending push notifications through a dedicated charging service application on the user's mobile phone, or sending text messages containing the charging status to the user's registered mobile phone number; or more concisely using an indicator light or a small display screen on the charging terminal to display the charging status. The charging terminal can issue a sound prompt, such as a beep or voice prompt, to notify nearby users.

[0083] Step S620: When the charging end performs the multiple reconnections but fails to receive the charging start instruction, the charging process is terminated and the connection between the charging end and the end to be authenticated is released; at the same time, the charging order fails to be started and the charging order number is not generated;

[0084] In the above step S620, if the charging terminal still does not receive the charging start instruction issued by the authentication terminal after the reconnection operation, the reconnection operation will be repeated. If the charging terminal performs multiple reconnection operations but does not receive the charging start instruction, the charging process is terminated and the connection between the charging terminal and the terminal to be authenticated is released. In this case, the charging order fails to start and the charging order number is not generated. By limiting the number of reconnections and setting a reasonable timeout time, the system can avoid unnecessary resource consumption and improve resource utilization efficiency. At the same time, it avoids excessive startup failure rate of operating stations.

[0085] Optionally, after multiple reconnection failures, the charging terminal can automatically perform fault diagnosis and generate a diagnostic report, providing detailed fault codes and solutions to help users and maintenance personnel quickly locate the problem; dynamically adjust the time interval between reconnection attempts based on historical data and current network conditions, use predictive analysis tools to predict the possibility of successful reconnection, and adjust the reconnection strategy accordingly; when the authentication terminal is unavailable, automatically switch to the backup authentication service, optimize the communication protocol, reduce unnecessary data transmission, and improve reconnection efficiency.

[0086] If you want to interrupt the reconnection operation and exit the charging process, please refer to Figure 8 , Figure 8 Flowchart D of the charging method provided in the embodiment of the present application when the authentication code fails.

[0087] Step S710: When the charging terminal is reconnecting, if the authentication terminal detects that the user has unlocked the terminal to be authenticated and the charging terminal, the connection between the terminal to be authenticated and the charging terminal is released.

[0088] In the above step S710, the user sends an unlocking request by operating the physical unlocking mechanism on the charging end or through the user interface of the charging end. After the authentication end confirms the user's unlocking intention (i.e., releases the connection between the end to be authenticated and the charging end), the charging end performs the unlocking operation, stops the charging process, and disconnects the electrical connection with the end to be authenticated.

[0089] In one embodiment of the present application, the charging terminal performs an unlocking operation, releases the connection between the end to be authenticated and the charging gun in the charging terminal, and allows the user to unplug the charging gun. At the same time, the charging terminal may notify the user that the unlocking operation is completed through a mobile application or other means. During the unlocking process, the charging terminal performs necessary safety checks so that the unlocking operation does not cause harm to the user or the device. The system can respond to the user's needs in a timely manner, that is, the request to interrupt charging and unlock the charging gun.

[0090] Even when the network connection is unstable or there is a problem with the authentication end, the charging end can automatically reconnect and try to restore normal charging operations. In other words, the reconnection operation and the mechanism of continuous detection of authentication end instructions help the system remain stable in the face of network fluctuations. At the same time, when faced with communication problems, the system can automatically try to recover, reducing the need for user intervention and improving user satisfaction; the charging end will only start charging when the authentication end explicitly issues a charge start instruction, ensuring the safety of the charging process.

[0091] The embodiment of the present application also provides a charging method, which is applied to a charging terminal, and the method includes: based on the connection between the charging terminal and the terminal to be authenticated, determining whether the charging terminal supports plug-and-charge; after the charging terminal receives the charging start instruction sent by the authentication terminal, reporting the charging start result within a first time period, the charging terminal charges the terminal to be authenticated, and the charging terminal sends a response message to the authentication terminal; if the charging terminal still does not receive the charging start instruction from the authentication terminal after a second time period, the charging terminal reports a timeout event to the authentication terminal, continues to send a not ready instruction to the terminal to be authenticated, and waits for the terminal to be authenticated to send a timeout message; after receiving the timeout message sent by the terminal to be authenticated, the charging terminal sends an identification message to perform a reconnection operation, and detects the issuance of the charging start instruction by the authentication terminal; when the charging terminal performs a reconnection operation, if the charging terminal receives the charging start instruction sent by the authentication terminal, it means that the reconnection operation is successful, the charging terminal charges the terminal to be authenticated, and the charging terminal sends a response message to the authentication terminal; if the charging terminal performs multiple reconnection operations but does not receive the charging start instruction, the charging process is terminated, and the charging terminal releases the connection with the terminal to be authenticated.

[0092] See also Fig. 9 , Fig. 9 A flow chart of a charging method applied to a charging terminal provided in an embodiment of the present application.

[0093] Step S810: After receiving the charging start instruction sent by the authentication end, the charging end reports the charging start result within the first time period, and the charging end charges the authentication end, and the charging end sends a response message to the authentication end;

[0094] In the above step S810, after receiving the charging start instruction sent by the authentication end, the charging end will complete the charging start within the first time period and report the result, and send a response message to the authentication end.

[0095] Optionally, the response message may include: the charging terminal performs a battery status check and a charging device self-check before starting charging; and records a detailed log of the start of charging, including time, charging parameters, etc.

[0096] Step S820: after the second period of time has passed and the charging end still has not received the charging start instruction from the authentication end, the charging end reports a timeout event to the authentication end, continues to send a not ready instruction, and waits for the authentication end to send a timeout message;

[0097] In the above step S820, if the start charging instruction is still not received at the end of the second period, the charging end will report a timeout event, and continue to send a not ready instruction to the end to be authenticated, waiting for a timeout message from the end to be authenticated.

[0098] Optionally, a timeout notification is sent to the user via an APP or SMS, prompting the user to check the charging device; in some cases, the charging terminal can automatically extend the waiting time.

[0099] Step S830: After receiving the timeout message sent by the end to be authenticated, the charging end sends an identification message to reconnect, and detects the start charging instruction sent by the authentication end.

[0100] In the above step S830, once a timeout message is received, the charging end sends an identification message to try to reconnect, and detects whether the authentication end sends a charging start instruction.

[0101] Optionally, the charger can try multiple network protocols or communication channels to reconnect; provide options for users to manually trigger reconnection through the mobile application; perform network connection quality detection and adjust the reconnection strategy based on the results.

[0102] Step S840: When the charging end performs the reconnection operation and receives a charging start instruction from the authentication end, the reconnection is determined to be successful, the charging end charges the authentication end, and the charging end sends a response message to the authentication end.

[0103] In the above step S840, if the reconnection is successful and the charging start instruction is received, it means that the reconnection operation is successful, the charging end continues to communicate with the end to be authenticated, performs the charging process, and sends a response message to the authentication end.

[0104] Optionally, the response message may also include: charging results, charging order number, information field, charging timestamp, charging power, charging power, user identification and other information.

[0105] Step S850: When the charging terminal has been reconnected multiple times but has not received the instruction to start charging, the charging process is terminated and the connection between the charging terminal and the terminal to be authenticated is released;

[0106] In the above step S850, if the charging end still does not receive the charging start instruction after multiple reconnection attempts, the charging process will be terminated and the connection between the charging end and the end to be authenticated will be released.

[0107] Optionally, set a maximum number of reconnection attempts to prevent infinite attempts; provide troubleshooting guidance or suggest that the user contact customer service; automatically switch to an alternative charging service or authentication server.

[0108] Overall, see Fig.10 , Fig.10 A multi-terminal interaction diagram that supports plug-and-charge and user code scanning is provided in an embodiment of the present application.

[0109] Based on the connection between the end to be authenticated and the charging end, if the charging end supports the plug-and-charge function and the authentication end detects the user scanning the code, the authentication end sends a start-charging instruction to the charging end and generates a charging order at the same time. The charging end charges the end to be authenticated and sends a response message to the authentication end, which contains the result of starting charging.

[0110] If the charging end does not report the charging start result, the authentication end order will be suspended and wait for the charging end to report the charging start result. For details, please refer to Fig.11 , Fig.11 Figure B is a multi-terminal interaction diagram that supports plug-and-play charging and user code scanning provided in the embodiment of the present application. After the user scans the code, the system can respond immediately and start the charging process, which improves the convenience of charging; the user does not need to perform complex operations, just scan the code to start charging, which simplifies the user's operation process; by starting charging immediately, the charging pile can be used more effectively and idle time can be reduced; the charging start result contained in the response message can be used for data tracking and analysis to help optimize the operation of the charging station; through code scanning authentication, only authorized users can start charging, which enhances the safety of the charging process.

[0111] Fig.12The multi-terminal interaction diagram provided in the embodiment of the present application in which the user has not scanned the code and the authentication has passed. When the user scanning the code is not detected, the charging end will upload the authentication code to the authentication end for authentication. When the authentication end passes the authentication, the authentication end sends a start charging instruction to the charging end and generates a charging order at the same time. The charging end charges the authentication end and sends a response message to the authentication end. The response message contains the result of starting charging. Even if the user does not scan the code, the system can start charging through other authentication methods (such as VIN code), providing a variety of charging start options; once the authentication is passed, the system automatically starts the charging process, reducing manual intervention and improving efficiency; through automated authentication and charging instruction issuance, the charging success rate is improved.

[0112] Fig.13 The multi-terminal interaction diagram provided in the embodiment of the present application in which the user has not scanned the code and the authentication has not passed, when the user scanning the code is not detected, the charging end will upload the authentication code to the authentication end for authentication, and when the authentication end fails to pass the authentication, the charging end does not receive the start charging instruction, and reports the timeout time and continues to send the not ready instruction. The charging end sends an identification message to the end to be authenticated based on the timeout message sent by the end to be authenticated to perform a reconnection operation, and detects the authentication end to send the start charging instruction. If the start charging instruction is not detected, continue the operation according to the above process; if the start charging instruction is detected, charge according to the process. If the authentication fails, the system will not start charging, preventing unauthorized access and potential abuse; even if the authentication fails, the system can try to recover through the reconnection operation, which enhances the stability of the system; by reporting the timeout and sending the identification message, the system provides a feedback mechanism to help diagnose problems; by continuously sending the not ready instruction, the communication channel with the end to be authenticated is kept active, which helps to find and solve problems in a timely manner.

[0113] See also Fig.14 , Fig.14 A block diagram of an electronic device provided in an embodiment of the present application. Fig.14 The structure shown is for illustration only. The electronic device 100 may also include Fig.14 More or fewer components as shown, or with Fig.14 The electronic device 100 may include a memory 111, a storage controller 112, a processor 113, a peripheral interface 114, an input / output unit 115, and a display unit 116. Each component is directly or indirectly electrically connected to each other to achieve data transmission or interaction. The processor 113 is used to execute the executable module stored in the memory.

[0114] Among them, the memory 111 is used to store programs, and the processor 113 executes the program after receiving the execution instruction. The method executed by the electronic device 100 defined by the process disclosed in any embodiment of the present application can be applied to the processor 113 or implemented by the processor 113.

[0115] The processor 113 may be an integrated circuit chip with signal processing capability. It can implement or execute the methods, steps and logic diagrams disclosed in the embodiments of the present application. The general processor may be a microprocessor or any conventional processor.

[0116] The peripheral interface 114 couples various input / output devices to the processor 113 and the memory 111. In some embodiments, the peripheral interface 114, the processor 113 and the memory controller 112 can be implemented in a single chip. In other embodiments, they can be implemented by separate chips.

[0117] The input and output unit 115 is used to provide input data to the user. The input and output unit 115 can be, but is not limited to, a mouse and a keyboard.

[0118] The display unit 116 provides an interactive interface (e.g., a user operation interface) between the electronic device 100 and the user terminal 000 or is used to display image data for reference by the user terminal 000. In this embodiment, the display unit may be a liquid crystal display or a touch display. If it is a touch display, it may be a capacitive touch screen or a resistive touch screen that supports single-point and multi-point touch operations. Supporting single-point and multi-point touch operations means that the touch display can sense touch operations generated simultaneously from one or more positions on the touch display, and the sensed touch operations are handed over to the processor for calculation and processing.

[0119] The electronic device in this embodiment can be used to perform each step in the charging method provided in the embodiment of the present application. The principle of solving the problem by the electronic device in the embodiment of the present application is similar to that in the embodiment of the charging method described above, so the implementation of the electronic device in this embodiment can refer to the description in the embodiment of the above method, and the repeated parts will not be repeated.

[0120] Fig.15 A computer-readable storage medium is provided in an embodiment of the present application, and a computer program instruction is stored in the computer-readable storage medium. When the computer program instruction is executed by a processor, it can be used to execute the various steps in the charging method provided in the embodiment of the present application. The principle of solving the problem by the computer-readable storage medium in the embodiment of the present application is similar to that in the embodiment of the aforementioned charging method, so the implementation of the computer-readable storage medium in this embodiment can refer to the description in the embodiment of the aforementioned method, and the repeated parts will not be repeated.

[0121] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

Claims

1. A charging method, characterized in that: The method is applied to a charging system including a charging terminal, an authentication terminal and a terminal to be authenticated; the method includes: Based on the connection between the charging terminal and the terminal to be authenticated, determine whether the charging terminal supports plug-and-charge; if the charging terminal supports plug-and-charge, the authentication terminal detects the user's charging behavior by scanning the code; if the authentication terminal detects the user's charging behavior by scanning the code, the charging terminal charges the terminal to be authenticated; if the authentication terminal does not detect the user's charging behavior by scanning the code, the charging terminal uploads the authentication code to the authentication terminal for authentication; and if the authentication code is authenticated, the charging terminal charges the terminal to be authenticated.

2. The method according to claim 1, characterized in that The step of charging the terminal to be authenticated by the charging terminal includes: The authentication terminal issues a charging start instruction to the charging terminal; and the authentication terminal generates a charging order based on the charging start instruction issued to the charging terminal; wherein the charging order includes a corresponding charging order number; After the charging terminal receives the charging start instruction sent by the authentication terminal, the charging terminal sends a response message to the authentication terminal within a first time period; wherein the response message includes a charging start result; If the authentication end does not receive the charging start result, the authentication end will send the charging start instruction to the charging end again and suspend the charging order; wherein, the two charging order numbers sent by the authentication end are consistent.

3. The method according to claim 2, characterized in that in, The response message also includes an information field; the information field may be filled with a code indicating a first type of charging order or a code indicating a second type of charging order.

4. The method according to claim 2, characterized in that: The method further includes: if the authentication code authentication fails, the authentication end does not send the charging start instruction to the charging end; if the charging end does not receive the charging start instruction from the authentication end, the charging end reports a timeout event and performs a reconnection operation.

5. The method according to claim 4, characterized in that The reporting of the timeout event and the reconnection operation include: when the charging end still does not receive the charging start instruction from the authentication end after a second period of time, the charging end reports the timeout event to the authentication end, and continuously sends a not ready instruction to the end to be authenticated, waiting for the end to be authenticated to send a timeout message; the charging end receives the timeout message sent by the end to be authenticated, and the charging end sends an identification message to perform the reconnection operation, and detects whether the authentication end sends the charging start instruction.

6. The method according to claim 4, characterized in that The reconnection operation includes: when the charging terminal performs the reconnection operation, if the charging terminal receives the charging start instruction sent by the authentication terminal, it indicates that the reconnection operation is successful, the charging terminal charges the terminal to be authenticated, and the charging terminal sends a response message to the authentication terminal; If the charging end still has not received the charging start instruction sent by the authentication end, the reconnection operation will continue to be repeated; if the charging end performs the reconnection operation multiple times but does not receive the charging start instruction, the charging process will be terminated and the connection between the charging end and the end to be authenticated will be released; at the same time, the charging order fails to start and no charging order number is generated.

7. The method according to claim 1, characterized in that If the authentication end detects that the user has unlocked the charging end, the connection between the end to be authenticated and the charging end is released.

8. A charging method, characterized in that: The method is applied to a charging terminal, and the method includes: judging whether the charging terminal supports plug-and-charge based on the connection between the charging terminal and the terminal to be authenticated; after the charging terminal receives the charging start instruction sent by the authentication terminal, reporting the charging start result within a first time period, the charging terminal charges the terminal to be authenticated, and the charging terminal sends a response message to the authentication terminal; if the charging terminal still does not receive the charging start instruction from the authentication terminal after a second time period, reporting a timeout event to the authentication terminal, continuously sending a not ready instruction to the terminal to be authenticated, and waiting for the terminal to be authenticated to send a timeout message After receiving the timeout message sent by the end to be authenticated, the charging end sends an identification message to perform a reconnection operation, and detects the start charging instruction sent by the authentication end; when the charging end performs the reconnection operation, if the start charging instruction is received from the authentication end, it means that the reconnection operation is successful, and the charging end charges the end to be authenticated, and the charging end sends a response message to the authentication end; when the charging end performs the reconnection operation multiple times but does not receive the start charging instruction, the charging process is terminated and the connection between the charging end and the end to be authenticated is released.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory stores program instructions, and when the processor runs the program instructions, the steps in the method according to any one of claims 1 to 7 are executed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the steps in the method according to any one of claims 1 to 7 are executed.

Images