Charging method and apparatus based on vehicle-side rapid authentication, device, and storage medium

Abstract

A charging method and apparatus based on vehicle-side rapid authentication, a device, and a storage medium. The method comprises: acquiring a charging request of a vehicle to be charged, and reading vehicle state information of the vehicle (S1); on the basis of the vehicle state information and pile-side state information of a charging pile, sending the charging request to a cloud server, so that the cloud server determines a charging condition and transaction information on the basis of the uploaded charging request (S2); receiving charging request feedback issued by the cloud server, determining a charging authorization of the vehicle to be charged, and charging the vehicle when the charging authorization is obtained (S3); and, upon detecting that the vehicle to be charged satisfies a charging termination request, stopping charging of the vehicle, and sending a generated charging timestamp to the cloud server, so that the cloud server generates transaction information of the vehicle (S4).

Description

Vehicle-based fast authentication charging method, device, equipment, and storage medium

[0001] This application claims priority to Chinese Patent Application No. 202411580108.2, filed with the Chinese Patent Office on November 7, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of robotics, for example to a vehicle-mounted fast authentication and charging method, apparatus, device, and storage medium. Background Technology

[0003] Currently, with the rapid development of electric vehicles, commercial charging stations need to be able to charge vehicles to a sufficient amount of power in a shorter time. Therefore, the Open Charging Protocol (OCPP) needs to be able to authenticate charging customers as quickly as possible to facilitate fast charging for users.

[0004] Currently in OCPP, most home charging stations (home charging stations) use the default plug-and-charge mode, which eliminates the need for complicated authentication procedures, making it convenient and fast.

[0005] Commercial charging stations require essential customer authentication, primarily through three methods: 1) authenticating via a user swiping a contactless chip card (including various RFID cards and bank cards); 2) remote charging via a mobile app, requiring client-side authentication; and 3) charging via a plug-and-charge system set up in the app. However, each of these authentication methods has some drawbacks. First, the authentication process is relatively cumbersome, and in special circumstances (such as poor mobile signal or remote start failure), unnecessary time is required. Second, customers may lose their cards or phones, making charging impossible. Third, some car owners may be unfamiliar with the operation or find the process too complicated, making it difficult to correctly set up plug-and-charge on their mobile devices.

[0006] Therefore, in summary, OCPP requires a rapid authentication method to address the aforementioned issues regarding commercial charging stations. To resolve the three problems mentioned above: First, in special circumstances such as poor mobile signal, demagnetized M1 cards or bank cards, customers cannot quickly initiate charging via card swiping or mobile app. Second, customers may accidentally lose their cards or phones, preventing them from charging their electric vehicles. Third, elderly users or other vehicle owners may not know how to operate plug-and-charge functions, or rental owners may lack the necessary permissions to configure related functions. In these cases, traditional methods such as card swiping or QR code scanning are still required for vehicle charging services. Summary of the Invention

[0007] This application provides a vehicle-side fast authentication charging method, apparatus, device, and storage medium to solve the problem of charging authentication waiting in related technologies.

[0008] On one hand, this application provides a vehicle-side fast authentication charging method, the method being used in a charging pile, the method comprising:

[0009] In response to a charging request from a vehicle to be charged, the vehicle status information of the vehicle to be charged is read; the vehicle status information is used to determine the charging status of the vehicle.

[0010] Based on the vehicle status information and the charging pile terminal status information, a charging request is sent to the cloud server so that the cloud server can determine the charging conditions and transaction information based on the uploaded charging request.

[0011] In response to receiving a charging request from the cloud server, the charging permission of the vehicle to be charged is determined, and the vehicle to be charged is charged if the charging authorization is obtained;

[0012] In response to the detection that the vehicle to be charged meets the charging termination request, charging of the vehicle to be charged is stopped, and the generated charging timestamp is sent to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

[0013] Specifically, the charging pile obtains vehicle status information based on the plug-in status of the vehicle to be charged;

[0014] The vehicle status information includes remaining battery power, charging power, unique vehicle identifier, and request timestamp; the unique vehicle identifier is used to bind the charging account and transaction settlement.

[0015] When the vehicle status information does not match the charging pile terminal, the connection with the vehicle to be charged is disconnected, and a charging prompt is issued.

[0016] Specifically, sending a charging request to the cloud server based on the vehicle status information and the charging pile's terminal status information includes:

[0017] The vehicle status information is matched with the charging pile terminal to obtain the charging pile terminal status information;

[0018] When the charging pile information indicates that it is in an idle state, a charging request is sent to the cloud server based on the charging pile information and the vehicle's unique identifier.

[0019] Specifically, the cloud server performs charging condition judgment and transaction information judgment based on the uploaded charging request, including:

[0020] When it is determined that the current pile end is in an idle state, the historical order transaction timestamp is obtained based on the vehicle's unique identifier and the request timestamp to determine the historical order settlement information;

[0021] When the historical order settlement information indicates that resource settlement has been completed, it is determined that the current vehicle to be charged meets the charging conditions; when the historical order settlement information indicates that resource settlement has not been completed, it is determined that the current vehicle to be charged does not meet the charging conditions.

[0022] Based on the charging authorization status of the vehicle to be charged, a charging request feedback is sent to the charging station.

[0023] Specifically, the method further includes:

[0024] Obtain the battery capacity of the vehicle to be charged and the remaining power in the current charging cycle;

[0025] When the remaining charge during a charging cycle reaches the battery capacity threshold, charging of the vehicle to be charged is stopped.

[0026] Specifically, after stopping charging the vehicle to be charged, the method further includes:

[0027] The cloud server determines the charging duration and generates transaction information based on the request timestamp and charging timestamp of the vehicle to be charged.

[0028] The transaction information is sent to the corresponding bound account platform and charging pile, and the transaction is settled when the paid resources are received.

[0029] Specifically, after the charging pile disconnects from the vehicle to be charged, the method further includes:

[0030] Detect the plugging / unplugging status of all charging guns, and update the charging status of the charging station when a charging gun is detected to be unplugged.

[0031] On the other hand, this application provides a vehicle-side fast authentication charging device, the device being used in a charging pile, comprising:

[0032] The receiving module is configured to read the vehicle status information of the vehicle to be charged in response to receiving a charging request from the vehicle to be charged; the vehicle status information is used to determine the charging status of the vehicle.

[0033] The first sending module is configured to send a charging request to the cloud server based on the vehicle status information and the charging pile terminal status information, so that the cloud server can determine the charging conditions and transaction information based on the uploaded charging request.

[0034] The control module is configured to respond to a charging request feedback received from the cloud server, determine the charging permission of the vehicle to be charged, and charge the vehicle to be charged if charging authorization is obtained.

[0035] The second sending module is configured to stop charging the vehicle in response to detecting that the vehicle to be charged meets the charging termination request, and send the generated charging timestamp to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

[0036] In another aspect, this application provides an electronic device, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set, or instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the vehicle-side fast authentication and charging method described above.

[0037] In another aspect, this application provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the vehicle-side fast authentication and charging method described above.

[0038] The beneficial effects of the technical solution provided in this application include at least the following: This application changes the previous method of scanning a code before charging, replacing it with a method that uses a charging gun to detect and generate a charging request. This allows the charging pile to first obtain the vehicle status information of the vehicle to be charged, making a preliminary judgment on whether the vehicle meets the charging conditions. After confirmation, the vehicle status information and the current charging pile status information are sent to the cloud server as cloud-based judgment criteria. The cloud then judges the charging conditions and transaction information based on the charging request sent by the charging pile, and sends a charging request feedback to the charging pile, which then initiates the charging process based on authorization. After charging is completed, the cloud server is notified to generate transaction information, realizing a charging logic of charging first and settling later, achieving the goal of rapid authentication charging. Attached Figure Description

[0039] Figure 1 is a flowchart of the vehicle-side fast authentication and charging method provided in an embodiment of this application;

[0040] Figure 2 is a schematic diagram of OCPP fast authentication;

[0041] Figure 3 shows a structural block diagram of the vehicle-side fast authentication and charging device;

[0042] Figure 4 shows a structural block diagram of an electronic device provided in an exemplary embodiment of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0044] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0045] Figure 1 is a flowchart of the vehicle-side fast authentication and charging method provided in an embodiment of this application, including the following steps:

[0046] S1. In response to the charging request of the vehicle to be charged, read the vehicle status information of the vehicle to be charged; the vehicle status information is used to determine the charging status of the vehicle.

[0047] The vehicle to be charged is the vehicle that the owner needs to charge before driving to the charging station. Traditional charging requires the user to scan a code and connect to the internet before charging can begin, which is cumbersome and leaves the user helpless without a SIM card or mobile phone. Therefore, this application proposes a pre-charging model, where the charging request is sent directly through the charging station when the owner plugs in the vehicle. Once the charging station receives the request, it first reads the vehicle's status information to determine whether charging is possible.

[0048] S2. Based on the vehicle status information and the charging pile terminal status information, send a charging request to the cloud server so that the cloud server can judge the charging conditions and transaction information based on the uploaded charging request.

[0049] As a semi-autonomous control unit, the charging pile needs to interact with a cloud server to synchronize data for commercial charging piles. The charging pile typically uses low-computing-power devices. After collecting vehicle status information, it combines this information with its own pile information to send a charging request to the cloud server. This charging request from the charging pile differs from that from the vehicle's request. The purpose of the charging pile's request is to request permissions from the cloud server, i.e., vehicle authentication, to determine whether the vehicle currently awaiting charging has the necessary permissions.

[0050] For cloud servers, they connect to a massive number of commercial charging stations, each potentially containing numerous charging nozzles, and each station has a limited rated charging power. When there are too many charging devices or when all devices are fully charged, the actual charging power for each vehicle is affected. Furthermore, charging stations themselves may cease operation due to maintenance, malfunctions, or upgrades, which is not immediately apparent to users. All this information needs to be sent to the cloud server for decision-making and assessment. In particular, financial transactions for commercial charging stations must be settled through the cloud.

[0051] S3. Upon receiving a charging request from the cloud server, determine the charging permission of the vehicle to be charged, and charge the vehicle if the charging authorization is obtained.

[0052] The purpose of the charging request feedback sent by the cloud server is to inform the charging pile of the actual charging authority of the vehicle to be charged. Charging will only be carried out on the vehicle if charging authorization is obtained; otherwise, charging will be refused.

[0053] S4. In response to detecting that the vehicle to be charged meets the charging termination request, stop charging the vehicle to be charged and send the generated charging timestamp to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

[0054] Charging termination requests can take various forms, such as the charging gun being unplugged, charging completion, abnormal power outage, or the charging time reaching the specified limit. For cases where charging is stopped, a charging bill can be generated for settlement. The settlement process requires recording the timestamp of charging interruption, determining the valid charging time based on the interval between two timestamps, and then processing the payment accordingly. The settlement task is also executed by the cloud server, which receives the charging timestamps sent by the charging station to generate transaction information.

[0055] Furthermore, for prepaid users with sufficient account balance, charges can be deducted directly based on transaction information, and settlement information and deduction records can be sent to the user. For scenarios and users where balance deductions are not executed, the transaction information and bill can be sent to the linked user terminal. Even if the user does not have their phone with them while charging, they can complete charging first and then manually settle the bill by connecting and disconnecting the client.

[0056] In step S2, the process of judging transaction information by the cloud server is essentially a judgment of bill settlement, that is, whether the bill in the historical record has been settled. Authorization for charging will only be issued if settlement is confirmed; otherwise, the charging request for the vehicle to be charged will be rejected.

[0057] In summary, this application changes the previous model of scanning a code before charging, replacing it with a model where the charging gun detects and generates a charging request. This allows the charging pile to first obtain the vehicle's status information to initially determine if the vehicle is ready for charging. Once confirmed, the charging pile sends the vehicle status information and the current status of the charging station to the cloud server, which serves as the cloud's judgment criteria. The cloud then judges the charging conditions and transaction information based on the charging request sent by the charging station and sends a charging request feedback to the charging station, which then initiates the charging process based on authorization. After charging is completed, the cloud server is notified to generate transaction information, achieving a "charge first, settle later" charging logic and enabling rapid authentication for charging.

[0058] In some embodiments, the transaction information settlement scheme can obtain information from the vehicle status information. In the open OCPP protocol, vehicle status information can be obtained through the user's charging station connection status, specifically including remaining battery power, charging power, vehicle unique identifier, request timestamp, etc. The vehicle unique identifier can be used to bind the charging account and for transaction settlement; this information can be bound to the account during the first charging session. In cases of incompatibility between the charging station and the vehicle due to specific vehicle models, charging power, poor contact, or malfunctions, the charging station will actively disconnect from the vehicle and provide a charging prompt.

[0059] Figure 2 illustrates the OCPP rapid authentication process. During the charging station insertion, the charging pile collects authentication information, sends the required data segments to the platform, and sends a charging request to the cloud server. The charging pile then matches the vehicle's status information with its own status information, which may include the following:

[0060] 1. Power Grid: If there is a problem with the power grid, such as a power outage or unstable voltage, the charging station cannot operate normally, resulting in the vehicle being unable to charge. At this time, the charging station is in an unavailable state.

[0061] 2. System update or maintenance: When the charging station is undergoing system update or maintenance, the charging pile will be shut down and will be in an unavailable state.

[0062] 3. Charging Pile Fault Information: If any fault or abnormality occurs at the charging pile, the fault information needs to be reported in some embodiments so that the platform can diagnose and handle it. At this time, the pile status is unavailable.

[0063] When the charging pile information indicates that it is in an idle state, a charging request can be sent to the cloud server based on the charging pile information and the vehicle's unique identifier.

[0064] For the cloud server, upon receiving a charging request from the charging station, the following judgment is made:

[0065] A. When it is determined that the current pile end is in an idle state, obtain the historical order transaction timestamp based on the vehicle's unique identifier and request timestamp to determine the historical order settlement information;

[0066] The main purpose of this stage is to query the transaction time of the most recent charging order from the cloud database and to check whether the settlement task for the last charging has been completed.

[0067] B. When the historical order settlement information indicates that resource settlement has been completed, determine that the current vehicle to be charged meets the charging conditions; when the historical order settlement information indicates that resource settlement has not been completed, determine that the current vehicle to be charged does not meet the charging conditions.

[0068] C. Send a charging request feedback to the charging station based on the charging authorization status of the vehicle to be charged.

[0069] Regardless of whether the settlement is completed or not, the cloud server will send a charging request feedback to the charging station. This means the charging station will send a packaged set of required data segments, including charging authorization information. For completed settlements, an authorization command will be sent; otherwise, the vehicle will not be charged.

[0070] Once authorized, the vehicle will be charged normally. During the charging process, the charging station will obtain the battery capacity of the vehicle to be charged and the remaining power of the current charging cycle in real time. When the remaining power of the vehicle to be charged reaches the battery capacity threshold within the charging cycle, the charging of the vehicle to be charged will be stopped.

[0071] Upon receiving a charging termination request, the charging station sends a charging timestamp to the cloud server. The cloud server then determines the charging duration and generates transaction information based on the vehicle's request timestamp and the charging timestamp. This transaction information is then sent to the corresponding linked account platform and charging station. Users then have several options: if they have a bank card or relevant prepaid card, they can swipe it at the charging station to complete the payment; if they have their mobile phone, they can complete the payment. Alternatively, if they don't have their mobile phone with them, they can pay via their account at other times. The cloud server processes the transaction upon receiving payment resources so that it can issue authorized charging instructions during the subsequent charging authentication phase.

[0072] In some embodiments, after the charging station disconnects from the vehicle's charging process, the charging status of the charging station is further updated. This depends primarily on the number of charging guns on the charging station. For example, if all charging guns are operating, or if the number of charging states reaches the total power load, the charging station is in an unavailable state, meaning it is not responding to other charging requests. When a charging process is disconnected and a charging gun is released, the charging station releases certain resources, allowing the charging status to be updated upon detecting the removal of a charging gun, thus facilitating subsequent responses.

[0073] Figure 3 shows a structural block diagram of the vehicle-side fast authentication and charging device provided in an embodiment of this application. The device includes:

[0074] The receiving module 310 is configured to read the vehicle status information of the vehicle to be charged in response to receiving a charging request from the vehicle to be charged; the vehicle status information is used to determine the charging status of the vehicle.

[0075] The first sending module 320 is configured to send a charging request to the cloud server based on the vehicle status information and the charging pile terminal status information, so that the cloud server can determine the charging conditions and transaction information based on the uploaded charging request.

[0076] The control module 330 is configured to respond to a charging request feedback received from the cloud server, determine the charging permission of the vehicle to be charged, and charge the vehicle to be charged if the charging authorization is obtained.

[0077] The second sending module 340 is configured to stop charging the vehicle in response to detecting that the vehicle to be charged meets the charging termination request, and send the generated charging timestamp to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

[0078] The vehicle-side fast authentication and charging device provided in this application embodiment can be applied to the vehicle-side fast authentication and charging method provided in the above embodiments. For relevant details, please refer to the above method embodiments. The implementation principle and technical effect are similar, and will not be repeated here.

[0079] It should be noted that the vehicle-side fast authentication and charging device provided in this embodiment is only an example of the above-described division of functional modules / units. In practical applications, the above functions can be assigned to different functional modules / units as needed, that is, the internal structure of the vehicle-side fast authentication and charging device can be divided into different functional modules / units to complete all or part of the functions described above. Furthermore, the implementation method of the vehicle-side fast authentication and charging method provided in the above method embodiments and the implementation method of the vehicle-side fast authentication and charging device provided in this embodiment belong to the same concept. For details of the specific implementation process of the vehicle-side fast authentication and charging device provided in this embodiment, please refer to the above method embodiments, which will not be repeated here.

[0080] Figure 4 shows a structural block diagram of an electronic device provided in an exemplary embodiment of this application. This includes desktop computers, laptops, handheld computers, and cloud servers. The electronic device may include, but is not limited to, a processor and memory. The processor and memory can be connected via a bus or other means. The processor can be a Central Processing Unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, graphics processing units (GPUs), embedded neural network processing units (NPUs) or other dedicated deep learning coprocessors, discrete gate or transistor logic devices, discrete hardware components, or combinations of the above types of chips.

[0081] The processor may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor may be implemented using at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor may also include a main processor and coprocessors. The main processor, also known as the CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, the processor may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0082] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the above embodiments of this application. The processor executes various functional applications and data processing by running the non-transitory software programs, instructions, and modules stored in the memory, thereby implementing the methods in the above embodiments. The memory may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created by the processor, etc. Furthermore, the memory may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0083] In some embodiments, the electronic device may also optionally include: a peripheral device interface and at least one peripheral device. The processor, memory, and peripheral device interface can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of: radio frequency circuitry, a display screen, and a keyboard.

[0084] Peripheral device interfaces can be used to connect at least one I / O (Input / Output) related peripheral device to the processor and memory. In some embodiments, the processor, memory, and peripheral device interface are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor, memory, and peripheral device interface can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0085] The display screen is used to display the UI (User Interface). This UI can include graphics, text, icons, videos, and any combination thereof. When the display screen is a touch screen, it also has the ability to collect touch signals on or above the surface of the display. These touch signals can be input as control signals to a processor for processing. In this case, the display screen can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there can be one display screen, located on the front panel of the electronic device; in other embodiments, there can be at least two display screens, respectively located on different surfaces of the electronic device or in a folded design; in still other embodiments, the display screen can be a flexible display screen, located on a curved or folded surface of the electronic device. Furthermore, the display screen can be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0086] A power source is used to supply power to various components in an electronic device. The power source can be alternating current (AC), direct current (DC), a disposable battery, or a rechargeable battery. When the power source includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is charged via a wired connection, while a wireless rechargeable battery is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0087] Those skilled in the art will understand that the structure shown in this embodiment does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0088] This application also discloses a computer-readable storage medium. Specifically, the computer-readable storage medium is used to store a computer program, which, when executed by a processor, implements the methods described in the above-described method embodiments. Those skilled in the art will understand that implementing all or part of the processes in the methods described in the above-described embodiments of this application can be accomplished by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0089] This specific embodiment is merely an explanation of this application and is not intended to limit it. After reading this specification, those skilled in the art can make modifications to this embodiment without contributing any inventive step, but such modifications are protected by patent law as long as they fall within the scope of the claims of this application.

Claims

1. A vehicle-side fast authentication charging method, the method being used in a charging pile, the method comprising: In response to a charging request from a vehicle to be charged, the vehicle status information of the vehicle to be charged is read. The vehicle status information is used to determine the vehicle's rechargeability. Based on the vehicle status information and the charging pile terminal status information, a charging request is sent to the cloud server so that the cloud server can determine the charging conditions and transaction information based on the uploaded charging request. In response to receiving a charging request from the cloud server, the charging permission of the vehicle to be charged is determined, and the vehicle to be charged is charged if the charging authorization is obtained; In response to the detection that the vehicle to be charged meets the charging termination request, charging of the vehicle to be charged is stopped, and the generated charging timestamp is sent to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

2. The method according to claim 1, wherein, The charging pile obtains vehicle status information based on the plug-in status of the vehicle to be charged; The vehicle status information includes remaining battery power, charging power, unique vehicle identifier, and request timestamp; the unique vehicle identifier is used to bind the charging account and transaction settlement. When the vehicle status information does not match the charging pile terminal, the connection with the vehicle to be charged is disconnected, and a charging prompt is issued.

3. The method according to claim 2, wherein, The step of sending a charging request to the cloud server based on the vehicle status information and the charging pile's terminal status information includes: The vehicle status information is matched with the charging pile terminal to obtain the charging pile terminal status information; When the charging pile information indicates that it is in an idle state, a charging request is sent to the cloud server based on the charging pile information and the vehicle's unique identifier.

4. The method according to claim 3, wherein, The cloud server performs charging condition and transaction information checks based on the uploaded charging request, including: When it is determined that the current pile end is in an idle state, the historical order transaction timestamp is obtained based on the vehicle's unique identifier and the request timestamp to determine the historical order settlement information; When the historical order settlement information indicates that resource settlement has been completed, it is determined that the current vehicle to be charged meets the charging conditions; when the historical order settlement information indicates that resource settlement has not been completed, it is determined that the current vehicle to be charged does not meet the charging conditions. Based on the charging authorization status of the vehicle to be charged, a charging request feedback is sent to the charging station.

5. The method according to claim 1, further comprising: Obtain the battery capacity of the vehicle to be charged and the remaining power in the current charging cycle; When the remaining charge during a charging cycle reaches the battery capacity threshold, charging of the vehicle to be charged is stopped.

6. The method according to claim 2, wherein after stopping charging the vehicle to be charged, the method further comprises: The cloud server determines the charging duration and generates transaction information based on the request timestamp and charging timestamp of the vehicle to be charged. The transaction information is sent to the corresponding bound account platform and charging pile, and the transaction is settled when the paid resources are received.

7. The method according to claim 2, wherein after the charging pile disconnects from the vehicle to be charged, the method further comprises: Detect the plugging / unplugging status of all charging guns, and update the charging status of the charging station when a charging gun is detected to be unplugged.

8. A vehicle-mounted fast authentication charging device, the device being used in a charging pile, comprising: The receiving module is configured to read the vehicle status information of the vehicle to be charged in response to receiving a charging request from the vehicle to be charged. The vehicle status information is used to determine the vehicle's rechargeability. The first sending module is configured to send a charging request to the cloud server based on the vehicle status information and the charging pile terminal status information, so that the cloud server can determine the charging conditions and transaction information based on the uploaded charging request. The control module is configured to respond to a charging request feedback received from the cloud server, determine the charging permission of the vehicle to be charged, and charge the vehicle to be charged if charging authorization is obtained. The second sending module is configured to stop charging the vehicle in response to detecting that the vehicle to be charged meets the charging termination request, and send the generated charging timestamp to the cloud server so that the cloud server can generate transaction information for the vehicle to be charged.

9. An electronic device comprising a processor and a memory, the memory storing at least one instruction, at least one program, a code set, or an instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the vehicle-side fast authentication and charging method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing at least one instruction, at least one program, a code set, or an instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the vehicle-side fast authentication and charging method as described in any one of claims 1 to 7.

Images