Vehicle automatic charging method and system, device and medium

Abstract

A vehicle automatic charging method, which is applied to a cloud server, and comprises: in response to a charging request sent by a target vehicle or a mobile client, determining a target charging parking space for the target vehicle on the basis of charging related information about the target vehicle carried in the charging request, and instructing the target vehicle to drive into the target charging parking space; when it is determined that the target vehicle has driven into the target charging parking space, sending a charging instruction to a target charging pile associated with the target charging parking space, so as to instruct the target charging pile to charge the target vehicle; and upon receiving a charging completion message for the target vehicle, instructing the target vehicle to drive out of the target charging parking space. The present application further relates to a vehicle automatic charging system, an electronic device, a computer-readable storage medium and a computer program product.

Description

Methods, systems, equipment and media for automatic vehicle charging Cross-references to related applications

[0001] This application claims priority to Chinese patent application No. 202410550338.8, filed on May 6, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] One or more embodiments of this application relate to, but are not limited to, the field of electric vehicles, and in particular to a method, system, device, and medium for automatic charging of vehicles. Background Technology

[0003] With the promotion of new energy vehicles, people's demand for electric vehicles is constantly growing. Correspondingly, the demand for charging electric vehicles is also increasing. Summary of the Invention

[0004] The following is an overview of the subject matter described in detail herein. This overview is not intended to limit the scope of the claims.

[0005] This application provides a method, system, device, and medium for automatic charging of vehicles.

[0006] According to a first aspect of one or more embodiments of this application, a method for automatic vehicle charging is provided, applied to a cloud server. The method includes: responding to a charging request sent by a target vehicle or a mobile client, determining a target charging space for the target vehicle based on charging-related information of the target vehicle carried in the charging request, and instructing the target vehicle to enter the target charging space; if it is determined that the target vehicle has entered the target charging space, sending a charging instruction to a target charging pile associated with the target charging space to instruct the target charging pile to charge the target vehicle; and if a charging completion message for the target vehicle is received, instructing the target vehicle to leave the target charging space.

[0007] Optionally, the charging-related information includes information about the user who initiated the charging request command in the target vehicle or the mobile client; the method further includes: determining whether the user who initiated the charging request command has the authority to automatically charge the target vehicle based on a pre-determined binding relationship between the target vehicle and the authorized user; determining the target charging space for the target vehicle based on the charging-related information of the target vehicle carried in the charging request includes: if it is determined that the user who initiated the charging request command has the authority to automatically charge the target vehicle, determining the target charging space for the target vehicle based on the charging-related information.

[0008] Optionally, the charging-related information includes the parking lot where the target vehicle is currently located. Determining the target charging space for the target vehicle based on the charging-related information of the target vehicle carried in the charging request includes: querying the availability of charging spaces in the parking lot; if there are available charging spaces in the parking lot, identifying any available charging space as the target charging space; if there are no available charging spaces in the parking lot, issuing a waiting-for-charging instruction to the target vehicle and adding the charging request to a charging request cache queue, so as to sequentially determine the target charging space corresponding to each charging request contained in the charging request cache queue.

[0009] Optionally, the method further includes: sending a locking command to an auxiliary device associated with the target charging space to instruct the auxiliary device to lock the target charging space before the target vehicle enters the target charging space.

[0010] Optionally, the step of sequentially determining the target charging space corresponding to each charging request in the charging request cache queue includes: if the charging-related information does not include the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue, then the target charging space of the target vehicle is directly determined; if the charging-related information includes the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue but has not reached the target charging time period, then the charging request of the target vehicle is put on hold until the target charging time period is reached, and during the holding process, the target charging space corresponding to other charging requests arranged after the charging request of the target vehicle is determined first.

[0011] Optionally, the charging-related information includes the parking lot where the target vehicle is currently located, and the method further includes: acquiring a map of the parking lot and surrounding environmental data collected by the target vehicle; determining the position of the target vehicle on the map based on the surrounding environmental data; and generating the optimal path for the target vehicle to enter the target charging space based on the position of the target vehicle on the map and the position of the target charging space on the map.

[0012] Optionally, the target vehicle may be parked in any location before entering the target charging space, and / or the target vehicle may be parked in any location after leaving the target charging space.

[0013] Optionally, the method further includes: upon receiving a ground lock at the target charging parking space, sending a lock-down command to the ground lock so that the target vehicle can enter the target charging parking space after the ground lock is locked down.

[0014] Optionally, the method further includes: if it is determined that the target vehicle has entered the target charging parking space, instructing the target vehicle to open the charging port cover; or, sending an opening command to the charging gun associated with the target charging parking space to instruct the charging gun to open the charging port cover.

[0015] Optionally, the method further includes: if it is determined that the charging port cover of the target vehicle is open, instructing the robotic arm associated with the target charging parking space to perform a charging gun insertion operation.

[0016] Optionally, the method further includes: sending an end notification to the mobile client upon receiving the charging end message.

[0017] According to a second aspect of one or more embodiments of this application, a method for automatic charging of a vehicle is provided, applied to a target vehicle. The method includes: responding to a charging request instruction initiated by a user in the target vehicle or a mobile client for the target vehicle, sending a charging request to a cloud server, the charging request carrying charging-related information of the target vehicle; driving into a target charging parking space according to the instructions of the cloud server, so as to charge the target vehicle by a target charging pile associated with the target charging parking space; and driving out of the target charging parking space according to the instructions of the cloud server after charging is completed.

[0018] According to a third aspect of one or more embodiments of this application, a method for automatic vehicle charging is provided, applied to a charging pile, the method comprising: receiving a charging instruction for a target vehicle issued by a cloud server, the charging instruction including vehicle information of the target vehicle; and, in response to the charging instruction, charging the target vehicle that has entered a charging space associated with the charging pile.

[0019] Optionally, the method further includes: after completing the charging operation for the target vehicle, reporting a charging completion message for the target vehicle to the cloud server.

[0020] According to a fourth aspect of one or more embodiments of this application, a system for automatic vehicle charging is provided, comprising a cloud server and a charging pile communicatively connected to the cloud server, wherein the cloud server is configured to, in response to a charging request sent by a target vehicle or a mobile client, determine a target charging space for the target vehicle based on charging-related information of the target vehicle carried in the charging request, and instruct the target vehicle to enter the target charging space; if it is determined that the target vehicle has entered the target charging space, send a charging instruction to the charging pile to instruct the charging pile to charge the target vehicle, wherein the charging pile is associated with the target charging space; and, upon receiving a charging completion message for the target vehicle, instruct the target vehicle to leave the target charging space; the charging pile is configured to charge the target vehicle in response to the charging instruction.

[0021] According to a fifth aspect of one or more embodiments of this application, an electronic device is provided, comprising: a processor; a memory configured to store processor-executable instructions; wherein the processor executes the executable instructions to implement the method as described in any of the embodiments of the first, second, or third aspects described above.

[0022] According to a sixth aspect of one or more embodiments of this application, a computer-readable storage medium is provided having computer instructions stored thereon that, when executed by a processor, implement the method described in any of the embodiments of the first, second, or third aspects described above.

[0023] According to a seventh aspect of one or more embodiments of this application, a computer program product is provided, including a computer program and / or instructions that, when executed by a processor, implement the method described in any of the embodiments of the first, second, or third aspects described above.

[0024] In one or more embodiments of this application, communication connections are established between the cloud server, the vehicle, and the charging pile. When a vehicle has a charging need, the cloud server determines the target charging space for the vehicle based on the received charging request and issues an instruction to the vehicle to enter the target charging space. After confirming that the vehicle has entered the target charging space, the cloud server issues a charging instruction to the target charging pile associated with the target charging space, causing the target charging pile to respond to the charging instruction and charge the vehicle parked in the target charging space. Finally, after receiving a message that the vehicle has finished charging, the cloud server instructs the vehicle to leave the target charging space to make it available for other vehicles that need charging. It is evident that in the above charging process, the user only needs to initiate a charging request instruction on the vehicle or mobile client at the beginning, without needing to perform any other operations. The entire charging process achieves automatic charging of the vehicle through communication and interaction between the cloud server, the vehicle, and the charging pile. Furthermore, the user can initiate a charging request instruction remotely through a mobile client or on the vehicle; regardless of the method, the user does not need to remain in the vehicle after initiating the charging request instruction. In other words, users no longer need to wait for an available charging station while in their vehicle, greatly reducing their waiting time and enabling charging of vehicles in autonomous driving mode, effectively improving the convenience of vehicle charging and user experience.

[0025] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit this application. Other aspects will become clear after reading and understanding the accompanying drawings and detailed description. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the principles of this application, but do not constitute a limitation on the technical solutions of this application.

[0027] Figure 1 is a schematic diagram of an automatic vehicle charging scenario provided by an exemplary embodiment of this application.

[0028] Figure 2 is a schematic flowchart of an exemplary embodiment of this application of a method for automatic charging of a vehicle.

[0029] Figure 3 is a flowchart illustrating a method for automatic vehicle charging provided in another exemplary embodiment of this application.

[0030] Figure 4 is a flowchart illustrating a method for automatic vehicle charging provided in another exemplary embodiment of this application.

[0031] Figure 5 is a schematic diagram of the interactive process of automatic vehicle charging provided by an exemplary embodiment of this application.

[0032] Figure 6 is a schematic diagram of a system architecture for automatic vehicle charging provided in an exemplary embodiment of this application.

[0033] Figure 7 is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application.

[0034] Figure 8 is a block diagram of an automatic vehicle charging device provided in an exemplary embodiment of this application.

[0035] Figure 9 is a block diagram of an automatic vehicle charging device provided in another exemplary embodiment of this application.

[0036] Figure 10 is a block diagram of an automatic vehicle charging device provided in another exemplary embodiment of this application. Detailed Implementation

[0037] Currently, most charging stations require users to manually plug in the charging gun, start charging, and stop charging, which means waiting for an available charging station and wasting time. Furthermore, this charging method cannot charge the now-common self-driving vehicles.

[0038] In view of this, this application provides a method, system, device and medium for automatic charging of vehicles.

[0039] The following describes one or more embodiments of this application in detail.

[0040] Figure 1 is a schematic diagram of an automatic vehicle charging scenario provided by an exemplary embodiment. As shown in Figure 1, the cloud server 12 establishes communication connections with the target vehicle 11, charging devices 13, 14, and 15, respectively. The target vehicle 11 is the charging object and can be any vehicle with charging needs, including manned or unmanned vehicles. The cloud server 12 can provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. Each of the charging devices 13, 14, and 15 includes a charging pile and a robotic arm, which can provide power to the target vehicle 11. Each charging device can be set up in a charging parking space, thereby establishing an association between the charging device and the charging parking space. For example, in Figure 1, charging device 13 is associated with charging parking space a, charging device 14 is associated with charging parking space b, and charging device 15 is associated with charging parking space c. In addition, the relationship between charging equipment and charging parking spaces can be set manually, so that the relationship is not limited by the physical spatial relationship between the charging equipment and the charging parking space.

[0041] Figure 2 is a flowchart of an exemplary method for automatic vehicle charging, which can be applied to the cloud server 12 shown in Figure 1. As shown in Figure 2, the method may include the following steps S201 to S203.

[0042] In S201, in response to a charging request sent by the target vehicle or mobile client, the target charging parking space of the target vehicle is determined based on the charging-related information of the target vehicle carried in the charging request, and the target vehicle is instructed to drive into the target charging parking space.

[0043] The target vehicle can be any vehicle with a charging need. The mobile client can be understood as an electronic device with communication capabilities, such as a personal computer (PC), tablet, laptop, PDA, mobile phone, wearable device (such as smart glasses, smartwatch, etc.). In this embodiment, the user's account logged in on the mobile client is bound to the target vehicle. When the target vehicle's battery is low and needs charging, the user can initiate a charging request command on the target vehicle, such as through the target vehicle's Human Machine Interface (HMI). The user needs to have usage rights to the target vehicle; for example, the user can be the vehicle owner or a family member of the owner. Furthermore, the user can also initiate a charging request command for the target vehicle on the mobile client. For example, the user can install a vehicle charging-related app on the mobile client to initiate a charging request command through the app. This embodiment is applicable to various charging scenarios. For example, after entering a parking lot, the user can initiate a charging request command on the target vehicle before getting out, and then leave without waiting for the vehicle to charge. In addition, users can initiate charging request commands from home or office via mobile clients (such as mobile phones) to remotely instruct target vehicles in parking lots to automatically charge.

[0044] When a target vehicle or mobile client receives a charging request instruction for that vehicle, it can generate a matching charging request containing charging-related information about the target vehicle. This charging-related information refers to information associated with each charging session and may include the vehicle's license plate number, vehicle model, charging duration, and urgency level. The target vehicle or mobile client then sends the generated charging request to a cloud server. The cloud server parses the received charging request to obtain the charging-related information. Based on this information, the cloud server determines the target charging space for the vehicle within the parking lot's charging station and issues an instruction to the vehicle to enter that space. For example, the cloud server can send this instruction to the vehicle's cockpit domain controller. The cockpit domain controller then sends a corresponding driving instruction to the autonomous driving domain controller, allowing the vehicle to enter the target charging space under the control of the autonomous driving domain controller.

[0045] In one embodiment, the charging-related information carried in the charging request may include information about the user who initiated the charging request command in the target vehicle or mobile client. After receiving the charging request command from the user (hereinafter referred to as the "initiator"), the target vehicle or mobile client can collect the initiator's identity information and generate a charging request based on that identity information. For example, the target vehicle or mobile client can collect the initiator's facial information through a device such as a camera and use the collected facial information as the initiator's identity information. After receiving the charging request, the cloud server parses the charging request to obtain the initiator's information. The cloud server pre-stores the binding relationship between the target vehicle and authorized users. The authorized user refers to a user with the authority to automatically charge the target vehicle. The cloud server can determine whether the initiator is an authorized user of the target vehicle, i.e., whether the initiator has the authority to automatically charge the target vehicle, based on the binding relationship between the target vehicle and authorized users. If it is determined that the initiator has the authority to automatically charge the target vehicle, the cloud server can determine the target charging location for the target vehicle. If it is determined that the initiator does not have the authority to automatically charge the target vehicle, the cloud server can return a message that automatic charging is not possible to the sender of the charging request (i.e., the target vehicle or mobile client), so that the sender of the charging request returns the corresponding "cannot automatically charge" prompt message to the initiator.

[0046] In this embodiment, by verifying the user who initiates the charging request command, it is determined whether the target vehicle needs to be automatically charged based on the verification result. This helps to avoid accidents caused by unauthorized users performing automatic charging operations on the target vehicle, thereby improving vehicle safety.

[0047] In one embodiment, the charging-related information carried in the charging request may include the parking lot where the target vehicle is currently located. The cloud server parses the received charging request to determine the parking lot where the target vehicle is currently located (hereinafter referred to as the "current parking lot"), and then queries for charging spaces within that parking lot. Of course, not all parking lots have charging stations (including charging spaces and charging piles). Therefore, if the cloud server detects that the current parking lot does not have a charging station, it can return a prompt message to the sender of the charging request (i.e., the target vehicle or mobile client) indicating that the current parking lot does not have charging functionality, thereby instructing the user to charge at another parking lot with a charging station.

[0048] If the current parking lot has charging stations, the cloud server can query the availability of charging spaces within the parking lot. The cloud server can send status query commands to all charging piles in the parking lot, instructing each charging pile to report the status of its associated charging spaces. The status of a charging space can include occupied, available, or abnormal status.

[0049] If the cloud server finds any available charging spaces in the current parking lot, it can designate any of these spaces as the target charging space for the target vehicle. If the cloud server finds no available charging spaces (i.e., all charging spaces in the current parking lot are occupied), it can issue a waiting charging instruction to the target vehicle, for example, instructing the vehicle to drive into a temporary parking space (i.e., a non-charging parking space used only for parking) to wait. Simultaneously, the cloud server can add the target vehicle's charging request to a charging request cache queue and sequentially determine the target charging space for each charging request in the queue. The order of the charging requests in the cache queue can be determined based on a combination of factors, such as the time the request was initiated, the urgency of the target vehicle's charging, and the target vehicle's charging level. This charging level is a user level generated by the system based on the user's historical charging behavior, used to evaluate vehicle charging priority. Users can improve the target vehicle's charging level through civilized charging behavior at charging stations. The urgency of charging reflects the urgent need for charging a target vehicle and can be determined based on various factors, such as the vehicle's current remaining battery power and the user's next scheduled usage time. Those skilled in the art can set the factors related to charging urgency themselves, and this application does not impose any restrictions on this. Determining the order of charging requests by comprehensively considering various information helps to rationally arrange these requests, thereby optimizing the allocation of target charging spaces for each request and improving the user's charging experience.

[0050] In this embodiment, if there are no available charging spaces in the current parking lot, the cloud server instructs the target vehicle to queue and wait in line. When its turn comes, the target vehicle is instructed to drive into the target charging space. This method eliminates the need for the user to wait for charging with the vehicle, significantly reducing the user's waiting time.

[0051] In one embodiment, during the process of sequentially determining the target charging space corresponding to each charging request in the charging request cache queue, if the charging-related information carried in the charging request does not include a target charging time period, then if the charging request is at the head of the charging request cache queue, it can be directly identified as the target charging space corresponding to the charging request at the head of the queue when an available charging space becomes available in the parking lot. If the charging-related information carried in the charging request includes a target charging time period, then when the charging request is at the head of the charging request cache queue but the target charging time period has not yet arrived, the charging request at the head of the queue needs to be put aside first, and other charging requests arranged after the charging request should be processed first. When the target charging time period arrives, the previously put aside charging requests should be processed first.

[0052] For example, if a user wants to charge during off-peak hours when charging costs are low (i.e., the target charging time period), the charging request generated by the target vehicle or mobile client can include the off-peak time period. If this charging request is at the head of the charging request cache queue but the off-peak time period has not yet arrived, the charging request can be put on hold, and other charging requests following it can be processed first. When the off-peak time period arrives, the previously put-off charging requests will be processed first. Specifically, when the off-peak time period arrives, if an available charging space exists, that available charging space will be designated as the target charging space for the previously put-off charging request. Furthermore, to avoid situations where the target vehicle has to wait continuously due to the lack of available charging spaces when the off-peak time period arrives, some measures can be taken to ensure that vehicles that have reserved off-peak time periods in advance can be automatically charged during the off-peak time period. For example, if user A has pre-booked a time slot for charging their vehicle during off-peak hours, and another user wants to charge their vehicle before that time slot, the system can send a friendly reminder such as "The off-peak time slot is already occupied; your vehicle may not be able to fully charge. Do you confirm charging?" when that user initiates their charging request. If the other user confirms, their vehicle can automatically move out of the charging spot when the off-peak time slot arrives, making room for user A's vehicle. Alternatively, when the off-peak time slot arrives, the cloud server can send a command to the other user's vehicle to move out of the charging spot, while simultaneously instructing user A's vehicle to move into the charging spot. This method allows users to pre-book charging time slots and ensures that there are available charging spots for their reserved vehicles during those slots, preventing inconvenience.

[0053] In one embodiment, after determining the target charging space for a target vehicle, the cloud server can send a command to the target vehicle to enter the target charging space, and simultaneously send a locking command to the auxiliary device associated with the target charging space, instructing the auxiliary device to lock the target charging space before the target vehicle enters. The auxiliary device associated with the target charging space may include, but is not limited to, ground locks, parking barriers, and charging piles at the target charging space. The locking command carries vehicle information of the target vehicle, such as license plate number, Vehicle Identification Number (VIN), vehicle model, and vehicle color. Upon receiving the locking command, the ground lock or parking barrier locks the target charging space by raising / lowering the barrier, and then, through user accounts operating the corresponding auxiliary devices, ensures that the target charging space is only open to the target vehicle, preventing other vehicles from entering. The charging pile, upon receiving the locking command, only provides charging functionality to the target vehicle and not to other vehicles, thus effectively locking the target charging space. The above method of locking the target charging space can reserve the target charging space for the target vehicle before the target vehicle drives into the target charging space, thus preventing other vehicles (such as vehicles in manual driving mode) from cutting in line to charge.

[0054] In one embodiment, the charging-related information carried in the charging request may include the parking lot where the target vehicle is currently located. After determining the target charging space, the cloud server can obtain a map of the parking lot and simultaneously instruct the target vehicle to collect its surrounding environmental data.

[0055] The target vehicle can collect data about its surrounding environment using various onboard sensors and upload the data to a cloud server. The cloud server then determines the target vehicle's current location on a map based on this data, and, based on this location and the location of the target charging space on the map, determines the optimal route for the vehicle to enter the target charging space from its current parking position. This optimal route information can be added to the command sent by the cloud server to the target vehicle to enter the target charging space, allowing the target vehicle to parse the command and obtain the optimal route to the target charging space.

[0056] Alternatively, the target vehicle can use its onboard computing platform to determine the optimal route to the target charging space. The target vehicle can obtain the location information of the target charging space from a cloud server, determine its own location using collected surrounding environmental data, and then use the parking lot map, the target charging space's location information, and its own location information to determine the optimal route. The parking lot map can be temporarily obtained from the cloud by the target vehicle or pre-stored on the vehicle.

[0057] In the above method, using a parking lot map to generate the optimal route for the target vehicle to enter the target charging space helps to speed up the process, thereby improving the charging efficiency of the target vehicle. Furthermore, this method can determine the optimal route regardless of where the target vehicle is parked in the parking lot.

[0058] In one embodiment, the target vehicle can be parked anywhere before entering the target charging space. In other words, the user can get out of the car anywhere in the parking lot and then instruct the vehicle to start automatic charging. Of course, after the target vehicle has finished automatic charging and left the target charging space, it can also park anywhere and send the parking location information to the user so that the user can find the target vehicle based on the location information the next time they need to use the car.

[0059] In one embodiment, if a parking lock is present in the charging space, a communication connection can be established between the parking lock's controller and a cloud server. If a target vehicle detects the presence of a parking lock when approaching the target charging space, it can send this information to the cloud server. The cloud server then sends a locking command to the parking lock's controller, which in turn locks the parking lock. After detecting that the parking lock has been lowered, the target vehicle can enter the target charging space. This method, through interaction between the parking lock and the cloud server, enables the automatic locking and lowering of the parking lock during the vehicle's automatic charging process.

[0060] In S202, if it is determined that the target vehicle has entered the target charging parking space, a charging command is sent to the target charging pile associated with the target charging parking space to instruct the target charging pile to charge the target vehicle.

[0061] Typically, a charging parking space is associated with a charging station, which is usually equipped with a robotic arm and a charging gun. Therefore, the robotic arm can be considered as being associated with the charging parking space, and the charging gun can be considered as being associated with the charging parking space.

[0062] In one embodiment, after the target vehicle has entered the target charging space, it needs to open the charging port cover before charging. In this embodiment, the charging port cover has at least three opening logics. First, after entering the target charging space, the target vehicle can send parking completion information to the cloud server. Upon receiving the parking completion information, the cloud server issues an opening command to the target vehicle, instructing it to open the charging port cover. For example, the target vehicle can send an opening command to the controller of the charging port cover, causing the controller to open the charging port cover. Second, upon receiving the parking completion information, the cloud server sends an opening notification to a mobile client. The user can remotely instruct the target vehicle to open the charging port cover via the mobile client based on the opening notification. For example, the user can send an opening message to the target vehicle via a vehicle control APP installed on the mobile client, instructing the target vehicle to open the charging port cover. Third, upon receiving the parking completion information, the cloud server sends an opening command to the charging gun associated with the target charging space. The charging gun responds to the opening command by sending an radio frequency signal or a Bluetooth signal to the controller of the charging port cover. The controller of the charging port cover opens the cover based on the received radio frequency (RF) or Bluetooth signal. Those skilled in the art can configure appropriate opening logic according to the control principles of the hardware system on the target vehicle; this application does not impose any limitations on this. For example, in another embodiment, the cloud server receives a parking completion message from the target vehicle and sends an opening command to the robotic arm associated with the target charging space. In response to the opening command, the robotic arm presses a button on the charging gun. After the button is pressed, the robotic arm sends an RF or Bluetooth signal to the controller of the charging port cover. The controller of the charging port cover opens the cover based on the received RF or Bluetooth signal.

[0063] The above method, through interaction with the cloud server, enables the charging port cover to open automatically during the vehicle's automatic charging process, reducing the need for users to manually open the cover.

[0064] In one embodiment, the target vehicle can send a message to the cloud server indicating that the opening is complete after opening the charging port cover. Then, the cloud server sends a charging gun insertion command to the robotic arm associated with the target charging space, instructing the robotic arm to perform the insertion operation. The robotic arm may be equipped with a small camera. During the insertion process, the robotic arm can determine the specific location of the charging port on the target vehicle based on data collected in real time by the small camera, then insert the charging gun at the determined location, and after completion, send a message to the cloud server indicating that the insertion is complete. Upon receiving the message, the cloud server sends a charging command to the target charging station. This method enables the cloud server to control the robotic arm's insertion, eliminating the need for manual insertion by the user and greatly improving the convenience of vehicle charging.

[0065] In S203, upon receiving a charging completion message for the target vehicle, the target vehicle is instructed to leave the target charging parking space.

[0066] After the target vehicle finishes charging, either the vehicle or the charging station can send a charging completion message to the cloud server. Upon receiving this message, the cloud server sends a disconnect command to the robotic arm, instructing it to disconnect the charging port. Within a preset time after the robotic arm completes the disconnection, the charging port cover on the target vehicle will automatically close. After returning to the charging station, the robotic arm can send a return message to the cloud server. Then, based on this return message, the cloud server sends a parking instruction to the target vehicle to leave the designated charging space, making that space available for other waiting vehicles. After leaving the designated charging space, the target vehicle can park anywhere.

[0067] In one embodiment, after the target vehicle has finished charging, the cloud server can send a completion notification to the mobile client bound to the target vehicle, thereby informing the user that charging has ended through the mobile client. The completion notification may include, but is not limited to: a message indicating that charging has ended, the final parking location information of the target vehicle, and the settlement bill for this charging session.

[0068] In the charging process described in the above embodiments, the user only needs to initiate a charging request command from the vehicle or mobile client at the beginning, without performing any other operations. The entire charging process achieves automatic charging of the vehicle through communication and interaction between the cloud server, the vehicle, and the charging station. Furthermore, the user can initiate a charging request command remotely through the mobile client or from the vehicle; regardless of the method, the user does not need to remain in the vehicle after initiating the charging request command. In other words, the user does not need to wait for an available charging station in the vehicle, greatly reducing the user's waiting time, thereby enabling charging of vehicles in an autonomous driving state and effectively improving the convenience of vehicle charging and the user experience.

[0069] Figure 3 is a flowchart of an exemplary embodiment of a method for automatic charging of a vehicle, which can be applied to the target vehicle 11 shown in Figure 1. As shown in Figure 3, the method may include the following steps S301 to S303.

[0070] In S301, in response to a charging request instruction initiated by a user for the target vehicle or mobile client, a charging request is sent to the cloud server, the charging request carrying charging-related information of the target vehicle.

[0071] In one embodiment, after receiving a charging request instruction from a user, the target vehicle or mobile client can determine whether the user initiating the charging request instruction is an authorized user of the target vehicle based on the binding relationship between the target vehicle and the authorized user. If the user initiating the charging request instruction is determined to be an authorized user, the target vehicle or mobile client can generate a charging request and send it to the cloud server. If the user initiating the charging request instruction is not an authorized user, the target vehicle or mobile client needs to return a "cannot automatically charge" prompt message to the user initiating the charging request instruction, and / or display the relevant agreement for automatic charging to the user. The target vehicle or mobile client can generate a charging request and send it to the cloud server after the user initiating the charging request instruction agrees to the agreement.

[0072] In S302, the vehicle drives into the target charging space according to the instructions of the cloud server, so that the target vehicle can be charged by the target charging pile associated with the target charging space.

[0073] The specific details of this step can be found in the embodiment shown in Figure 2, and will not be repeated here.

[0074] In S303, after charging is completed, the vehicle drives out of the target charging space according to the instructions of the cloud server.

[0075] In one embodiment, after charging is completed, the target vehicle can return a charging completion message to the cloud server to inform the cloud server that the charging has ended, thereby enabling the cloud server to settle the charging fee for this charging.

[0076] Figure 3 illustrates the specific implementation process of this application from the perspective of the vehicle, corresponding to the embodiment described in Figure 2 from the perspective of the cloud server. This embodiment of the application utilizes a vehicle in conjunction with a cloud server to achieve a complete automatic charging process. All descriptions related to the cloud server during the generation and management of various requests, information, and data in the embodiment shown in Figure 2 are also applicable to the embodiment shown in Figure 3, and will not be repeated here.

[0077] Figure 4 is a flowchart of an exemplary method for automatic vehicle charging, which can be applied to the charging stations of charging devices 13 to 15 shown in Figure 1. As shown in Figure 4, the method may include the following steps S401 and S402.

[0078] In step S401, a charging instruction for the target vehicle is received from the cloud server, the charging instruction containing vehicle information of the target vehicle.

[0079] In one embodiment, the vehicle information may include license plate number, vehicle identification number (VIN), vehicle model, vehicle color, etc. After the target vehicle has entered the charging space associated with the charging pile (hereinafter referred to as the "target charging space"), the charging pile can identify whether the vehicle information of the target vehicle currently entering the target charging space matches the vehicle information included in the charging instruction. If the identification result is a mismatch, the charging pile can return a message indicating a vehicle error to the cloud server and wait for the next instruction from the cloud server. If the identification result is a match, it can simply wait for the next instruction from the cloud server.

[0080] In S402, in response to the charging command, the target vehicle that has entered the charging space associated with the charging pile is charged.

[0081] Once the cloud server determines that the target vehicle has entered the target charging space and the charging port cover on the vehicle is open, it sends a charging arm on the charging station a charging gun insertion command, instructing the arm to insert the charging gun into the vehicle's charging port. After completing the insertion, the robotic arm sends a message back to the cloud server confirming completion. Upon receiving this message, the cloud server sends a charging command to the charging station. The charging station then responds to the received command and begins charging the target vehicle.

[0082] In one embodiment, after completing the charging operation for the target vehicle, the charging station can report a charging completion message to the cloud server. Specifically, the charging station can report the charging completion message to the cloud server after the robotic arm returns to its original position, thus notifying the cloud server that the charging is complete. This method can prevent situations where the target vehicle attempts to leave the target charging space before the robotic arm has returned to its original position, thereby avoiding accidents such as electrical leakage and improving the safety of automatic vehicle charging.

[0083] Figure 4 illustrates the specific implementation process of this application from the perspective of a charging pile, corresponding to the embodiment described in Figure 2 from the perspective of a cloud server. This application's embodiment utilizes a charging pile in conjunction with a cloud server to achieve a complete automatic charging process. All descriptions related to the cloud server during the generation and management of various requests, information, and data in the embodiment shown in Figure 2 are also applicable to the embodiment shown in Figure 4, and will not be repeated here.

[0084] Figure 5 is an interactive flowchart of an automatic vehicle charging process provided in an exemplary embodiment. As shown in Figure 5, the interactive process involves a cloud server, a target vehicle, a charging pile, and a mobile client. When the charging parking space is equipped with a parking lock, the interactive process also involves a parking lock controller. The automatic charging process for the target vehicle includes the following steps S501 to S519.

[0085] In S501, the mobile client responds to the user's charging request instruction, generates a corresponding charging request, and sends the charging request to the cloud server. The charging request carries charging-related information of the target vehicle.

[0086] It should be noted that users can also initiate a charging request command on the target vehicle, so that the target vehicle can generate a corresponding charging request and send the charging request to the cloud server.

[0087] In S502, the cloud server determines whether the user who initiated the charging request command has the authority to automatically charge the target vehicle based on the pre-determined binding relationship between the target vehicle and the authorized user.

[0088] If it is determined that the user initiating the charging request does not have the permission to automatically charge the target vehicle, a message indicating that automatic charging is not possible is returned to the sender of the charging request (i.e., the mobile client or the target vehicle). If it is determined that the user initiating the charging request has the permission to automatically charge the target vehicle, then S503 is executed.

[0089] In the S503, the cloud server sends status query commands to each charging pile in the parking lot where the target vehicle is currently located, based on the received charging request, in order to check the availability of charging spaces in the parking lot.

[0090] The cloud server can send status query commands to all charging stations in the parking lot, instructing each charging station to report the status of its associated charging space. The status of the charging space can include occupied, vacant, or abnormal status.

[0091] In S504, each charging pile reports the status of its associated charging space to the cloud server.

[0092] Based on the reported results from the charging piles, the cloud server in the S505 determines the target charging location for the target vehicle.

[0093] If the reported result indicates that an available charging space exists, the cloud server can designate any available charging space as the target charging space for the target vehicle. If the reported result indicates that no available charging space exists, the cloud server issues a waiting instruction to the target vehicle, adds the target vehicle's charging request to the charging request cache queue, and sequentially determines the target charging space corresponding to each charging request contained in the charging request cache queue.

[0094] In S506, the cloud server issues a parking instruction to the target vehicle to drive into the target charging space.

[0095] In S507, if the target vehicle detects a ground lock in the target charging space when it approaches the target charging space, the target vehicle sends a request to the cloud server to unlock the lock.

[0096] In response to the target vehicle's lock-down request, the S508 cloud server sends a lock-down command to the controller of the parking lock located in the target charging parking space, instructing the parking lock controller to perform the lock-down operation.

[0097] In the S509, the ground lock controller sends the result of the lock being lowered to the cloud server.

[0098] After receiving the result that the parking lock has been lowered, the S510 cloud server issues a parking instruction to the target vehicle to instruct the target vehicle to continue driving into the target charging parking space.

[0099] It should be noted that if the target vehicle has the function of recognizing the status of the parking lock (locked up / locked down), then after the parking lock is lowered, the target vehicle can automatically recognize that the parking lock has been lowered, and thus continue to drive into the target charging parking space. In this case, after executing S509, S510 can be skipped and S511 can be executed directly.

[0100] In S511, after the target vehicle has entered the target charging space, it sends a parking end command to the cloud server.

[0101] After receiving the parking end command, the S512 cloud server sends an open cover command to the target vehicle to instruct the target vehicle to open the charging port cover.

[0102] In S513, the target vehicle returns a message to the cloud server indicating that the hood opening is complete.

[0103] In the S514 cloud server, a charging gun insertion command is sent to the robotic arm on the charging pile associated with the target charging space to instruct the robotic arm to insert the charging gun into the target vehicle.

[0104] In S515, the charging pile sends a message to the cloud server that the robotic arm has completed inserting the charging gun.

[0105] In the S516, the cloud server sends charging instructions to the charging station to instruct the charging station to charge the target vehicle.

[0106] In S517, the charging station sends a message to the cloud server indicating that charging has ended.

[0107] In the S518, the cloud server sends a parking instruction to the target vehicle to leave the target charging space.

[0108] Once the S519 cloud server determines that the target vehicle has left the target charging parking space, it sends an end notification to the mobile client.

[0109] The notification to end charging may include, but is not limited to: a message that charging has ended, the final parking location information of the target vehicle, and the settlement bill for this charging session.

[0110] Figure 6 is a schematic diagram of the architecture of an automatic vehicle charging system 600 provided in an exemplary embodiment. As shown in Figure 6, the automatic charging system includes a cloud server 601 and a charging pile 602, which are connected by a communication link. The cloud server 601 is used to respond to a charging request sent by a target vehicle or a mobile client, determine the target charging space for the target vehicle based on the charging-related information of the target vehicle carried in the charging request, and instruct the target vehicle to drive into the target charging space; if it is determined that the target vehicle has entered the target charging space, it sends a charging command to the charging pile to instruct the charging pile to charge the target vehicle, the charging pile being associated with the target charging space; and if it receives a charging completion message for the target vehicle, it instructs the target vehicle to leave the target charging space.

[0111] The charging pile 602 is used to charge the target vehicle in response to the charging command sent by the cloud server.

[0112] Figure 7 is a schematic diagram of the structure of an electronic device 700 according to an exemplary embodiment of this application. Referring to Figure 7, at the hardware level, the electronic device 700 includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a non-volatile memory 710, and may also include other hardware required for services. The processor 702 reads the corresponding computer program from the non-volatile memory 710 into the memory 708 and then runs it. Of course, in addition to the software implementation, this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0113] Corresponding to the above method embodiments, this application also provides embodiments of an automatic vehicle charging device.

[0114] Figure 8 is a block diagram of an automatic vehicle charging device 800 according to an exemplary embodiment of this application. The device 800 can be applied to a cloud server. Referring to Figure 8, the device 800 includes a charging parking space determination unit 801, a charging instruction sending unit 802, and an exit instruction unit 803, wherein: the charging parking space determination unit 801 is configured to, in response to a charging request sent by a target vehicle or a mobile client, determine a target charging parking space for the target vehicle based on charging-related information of the target vehicle carried in the charging request, and instruct the target vehicle to enter the target charging parking space; the charging instruction sending unit 802 is configured to, upon determining that the target vehicle has entered the target charging parking space, send a charging instruction to a target charging pile associated with the target charging parking space to instruct the target charging pile to charge the target vehicle; and the exit instruction unit 803 is configured to, upon receiving a charging completion message for the target vehicle, instruct the target vehicle to exit the target charging parking space.

[0115] Optionally, the charging-related information includes information about the user who initiated the charging request command in the target vehicle or the mobile client; the device 800 further includes: an authorization determination unit 804, configured to determine whether the user who initiated the charging request command has the authorization to automatically charge the target vehicle based on a pre-determined binding relationship between the target vehicle and the authorized user; the charging parking space determination unit 801 is further configured to: determine the target charging parking space for the target vehicle based on the charging-related information when it is determined that the user who initiated the charging request command has the authorization to automatically charge the target vehicle.

[0116] Optionally, the charging-related information includes the parking lot where the target vehicle is currently located, and the charging space determination unit 801 is further configured to: query the availability of charging spaces in the parking lot; if there are available charging spaces in the parking lot, determine any available charging space as the target charging space; if there are no available charging spaces in the parking lot, issue a waiting charging instruction to the target vehicle and add the charging request to the charging request cache queue, so as to sequentially determine the target charging space corresponding to each charging request contained in the charging request cache queue.

[0117] Optionally, the device 800 further includes: a locking unit 805 configured to send a locking command to an auxiliary device associated with the target charging space, instructing the auxiliary device to lock the target charging space before the target vehicle enters the target charging space.

[0118] Optionally, the step of sequentially determining the target charging space corresponding to each charging request in the charging request cache queue includes: if the charging-related information does not include the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue, then the target charging space of the target vehicle is directly determined; if the charging-related information includes the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue but has not reached the target charging time period, then the charging request of the target vehicle is put on hold until the target charging time period is reached, and during the holding process, the target charging space corresponding to other charging requests arranged after the charging request of the target vehicle is determined first.

[0119] Optionally, the charging-related information includes the parking lot where the target vehicle is currently located. The device 800 further includes: a path generation unit 806, configured to acquire a map of the parking lot and surrounding environmental data collected by the target vehicle; determine the position of the target vehicle on the map based on the surrounding environmental data; and generate the optimal path for the target vehicle to enter the target charging space based on the position of the target vehicle on the map and the position of the target charging space on the map.

[0120] Optionally, the target vehicle may be parked in any location before entering the target charging space, and / or the target vehicle may be parked in any location after leaving the target charging space.

[0121] Optionally, the device 800 further includes: a ground lock lowering unit 807, configured to send a ground lock lowering command to the ground lock when it is received that the target charging parking space is locked, so that the target vehicle can drive into the target charging parking space after the ground lock is lowered.

[0122] Optionally, the device 800 further includes: a cover opening unit 808, configured to: instruct the target vehicle to open the charging port cover when it is determined that the target vehicle has entered the target charging parking space; or, send a cover opening command to the charging gun associated with the target charging parking space to instruct the charging gun to open the charging port cover.

[0123] Optionally, the device 800 further includes: a gun insertion unit 809, configured to: instruct a robotic arm associated with the target charging space to perform a gun insertion operation when it is determined that the charging port cover of the target vehicle is open.

[0124] Optionally, the device 800 further includes a notification sending unit 810, configured to send an end notification to the mobile client upon receiving the charging end message.

[0125] Figure 9 is a block diagram of an automatic vehicle charging device 900 according to an exemplary embodiment of this application. The device 900 can be applied to a target vehicle. Referring to Figure 9, the device 900 includes a charging request sending unit 901, an entry unit 902, and an exit unit 903, wherein: the charging request sending unit 901 is configured to send a charging request to a cloud server in response to a charging request instruction initiated by a user on the target vehicle or a mobile client, the charging request carrying charging-related information of the target vehicle; the entry unit 902 is configured to enter a target charging parking space according to the instructions of the cloud server, so that the target vehicle can be charged by a target charging pile associated with the target charging parking space; and the exit unit 903 is configured to exit the target charging parking space according to the instructions of the cloud server after charging is completed.

[0126] Figure 10 is a block diagram illustrating an automatic vehicle charging device 1000 according to an exemplary embodiment of this application. The device 1000 can be applied to charging piles. Referring to Figure 10, the device 1000 includes a charging instruction receiving unit 1001 and a charging unit 1002, wherein: the charging instruction receiving unit 1001 is configured to receive a charging instruction for a target vehicle issued by a cloud server, the charging instruction containing vehicle information of the target vehicle; the charging unit 1002 is configured to, in response to the charging instruction, charge the target vehicle that has entered the charging space associated with the charging pile.

[0127] Optionally, the device 1000 further includes a charging completion message reporting unit 1003, configured to report a charging completion message for the target vehicle to the cloud server after completing the charging operation for the target vehicle.

[0128] The specific implementation process of the functions and roles of each module / unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0129] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware (e.g., a processor), and the program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Accordingly, each module / unit in the above embodiments can be implemented in hardware, such as by using an integrated circuit to implement its corresponding function, or it can be implemented in the form of a software functional module, such as by a processor executing a program / instruction stored in memory to implement its corresponding function. This application is not limited to any particular combination of hardware and software.

[0130] The apparatus, module, or unit described in the above embodiments can be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer, which can be a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0131] In a typical configuration, a computer includes one or more processors, including a central processing unit (CPU) and a graphics processing unit (GPU), input / output interfaces, a network interface, and memory. The CPU is used for computational simulation, while the GPU is used to output high-quality 3D images.

[0132] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0133] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0134] Corresponding to the embodiments of the aforementioned automatic vehicle charging method, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the automatic vehicle charging method as described in any of the foregoing embodiments.

[0135] Corresponding to the aforementioned embodiments of the automatic vehicle charging method, this application also provides a computer program product, including a computer program and / or instructions, which, when executed by a processor, implement the automatic vehicle charging method as described in any of the foregoing embodiments.

[0136] The above descriptions are merely some embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for automatic charging of a vehicle, applied to a cloud server, the method comprising: In response to a charging request sent by the target vehicle or mobile client, the target charging space of the target vehicle is determined based on the charging-related information of the target vehicle carried in the charging request, and the target vehicle is instructed to drive into the target charging space (S201). If it is determined that the target vehicle has entered the target charging parking space, a charging command is sent to the target charging pile associated with the target charging parking space to instruct the target charging pile to charge the target vehicle (S202). as well as Upon receiving a charging completion message for the target vehicle, the system instructs the target vehicle to leave the target charging parking space (S203).

2. The method according to claim 1, wherein, The charging-related information includes information about the user who initiated the charging request command in the target vehicle or the mobile client. The method further includes: determining whether the user who initiated the charging request command has the authority to automatically charge the target vehicle based on the predetermined binding relationship between the target vehicle and the authorized user; Determining the target charging location for the target vehicle based on the charging-related information of the target vehicle carried in the charging request includes: determining the target charging location for the target vehicle based on the charging-related information when it is determined that the user who initiated the charging request command has the authority to automatically charge the target vehicle.

3. The method according to claim 1 or 2, wherein, The charging-related information includes the parking lot where the target vehicle is currently located. Determining the target charging space for the target vehicle based on the charging-related information carried in the charging request includes: Check the availability of charging spaces in the parking lot; If there are available charging spaces in the parking lot, any one of the available charging spaces will be designated as the target charging space. If there are no available charging spaces in the parking lot, a waiting charging instruction is issued to the target vehicle, and the charging request is added to the charging request cache queue, so as to sequentially determine the target charging space corresponding to each charging request contained in the charging request cache queue.

4. The method according to claim 3, further comprising: A locking command is sent to the auxiliary equipment associated with the target charging space to instruct the auxiliary equipment to lock the target charging space before the target vehicle enters the target charging space.

5. The method according to claim 3 or 4, wherein, The step of sequentially determining the target charging space corresponding to each charging request contained in the charging request cache queue includes: If the charging-related information does not include the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue, then the target charging parking space of the target vehicle is directly determined. If the charging-related information includes the target charging time period of the target vehicle, and the charging request of the target vehicle is at the head of the charging request cache queue and has not reached the target charging time period, then the charging request of the target vehicle is put on hold until the target charging time period is reached. During the holding process, the target charging parking space corresponding to other charging requests that are arranged after the charging request of the target vehicle is determined first.

6. The method according to any one of claims 1 to 5, wherein, The charging-related information includes the parking lot where the target vehicle is currently located, and the method further includes: Obtain a map of the parking lot and surrounding environmental data collected from the target vehicle; The location of the target vehicle on the map is determined based on the surrounding environmental data; and The optimal route for the target vehicle to enter the target charging space is generated based on the location of the target vehicle on the map and the location of the target charging space on the map.

7. The method according to any one of claims 1 to 6, wherein, The target vehicle is parked in any location before entering the target charging space, and / or The target vehicle can be parked anywhere after leaving the target charging parking space.

8. The method according to any one of claims 1 to 7, further comprising: If a ground lock is detected at the target charging parking space, a ground lock release command is sent to the ground lock so that the target vehicle can enter the target charging parking space after the ground lock is released.

9. The method according to any one of claims 1 to 8, further comprising: If it is determined that the target vehicle has entered the target charging parking space, instruct the target vehicle to open the charging port cover; or Send an open cover command to the charging gun associated with the target charging space to instruct the charging gun to open the charging port cover. and / or The method further includes: If it is determined that the charging port cover of the target vehicle is open, instruct the robotic arm associated with the target charging bay to perform the charging gun insertion operation; and / or The method further includes: Upon receiving the charging completion message, a completion notification is sent to the mobile client.

10. A method for automatically charging a vehicle, applied to a target vehicle, the method comprising: In response to a charging request instruction initiated by a user for the target vehicle or a mobile client, a charging request is sent to a cloud server, the charging request carrying charging-related information of the target vehicle (S301). The vehicle drives into the target charging space according to the instructions of the cloud server, so that the target vehicle can be charged by the target charging pile associated with the target charging space (S302). as well as After charging is completed, the vehicle will drive out of the target charging space according to the instructions of the cloud server (S303).

11. A method for automatic charging of a vehicle, applied to a charging pile, the method comprising: Receive a charging instruction for the target vehicle sent by the cloud server, the charging instruction containing vehicle information of the target vehicle (S401); as well as In response to the charging command, the target vehicle that has entered the charging space associated with the charging pile is charged (S402).

12. A vehicle automatic charging system (600) includes a cloud server (601) and a charging pile (602) communicatively connected to the cloud server (601), wherein, The cloud server (601) is configured to respond to a charging request sent by a target vehicle or mobile client, determine the target charging space for the target vehicle based on the charging-related information of the target vehicle carried in the charging request, and instruct the target vehicle to drive into the target charging space; if it is determined that the target vehicle has driven into the target charging space, a charging instruction is sent to the charging pile to instruct the charging pile to charge the target vehicle, and the charging pile is associated with the target charging space; And upon receiving a charging completion message for the target vehicle, instruct the target vehicle to leave the target charging parking space; The charging station (602) is configured to charge the target vehicle in response to the charging command.

13. An electronic device (700), comprising: Processor (702); Memory (710) configured to store processor-executable instructions; The processor (702) implements the method as described in any one of claims 1 to 11 by running the executable instructions.

14. A computer-readable storage medium having stored thereon computer instructions, wherein, When executed by a processor, the computer instructions implement the method as described in any one of claims 1 to 11.

15. A computer program product comprising a computer program and / or instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 11.

Images