Vehicle charging method, device, equipment and storage medium

Abstract

The application relates to a vehicle charging method and device, equipment and a storage medium, and relates to the technical field of automobiles. The method comprises the following steps: in the case that a charging gun of a charging pile is connected with a target vehicle, receiving an operator identification message sent by the charging pile, wherein the operator identification message comprises an operator identifier corresponding to the charging pile; based on the operator identifier corresponding to the charging pile, obtaining charging parameter information, and sending the charging parameter information to the charging pile, wherein the charging parameter information comprises at least one of the following: a vehicle owner identifier, a target vehicle identifier, a key, a key identifier, a random parameter and a timestamp; in the case that the charging pile determines that the target vehicle charging authentication is passed based on the charging parameter information, the target vehicle starts charging. Therefore, in the case that the target vehicle charging authentication is passed, the target vehicle can be directly charged by the charging pile, and the technical problem that there is a security loophole in the verification of the VIN of the vehicle before charging and the safety of the charging of the vehicle when the vehicle is directly connected to the charging pile cannot be guaranteed is solved.

Description

Technical Field

[0001] This invention relates to the field of automotive technology, and more specifically to a vehicle charging method, device, equipment, and storage medium. Background Technology

[0002] Electric vehicles, as an environmentally friendly and energy-saving mode of transportation, have received increasing attention and promotion in recent years. Charging is an essential part of the electric vehicle usage process. Currently, the charging process for electric vehicles generally consists of three stages: connecting the charger, identity verification, and starting charging. Identity verification can be done by scanning a QR code with a mobile phone or swiping a card; however, this method offers a poor charging experience, is not simple or efficient enough, and does not achieve the "plug-and-charge" effect. Currently, when verifying vehicle identity, the charging station's charging gun reads the vehicle's Vehicle Identification Number (VIN) and uploads the VIN and charging station information to the charging station cloud platform. The charging station cloud platform verifies the VIN, and upon successful verification, sends a charging command to the charging station to begin charging, achieving "plug-and-charge" functionality.

[0003] However, in the above method, when the vehicle's VIN is verified through the charging pile cloud platform to achieve plug-and-charge, the VIN read by the charging gun is in plaintext. This allows for theft of the vehicle's VIN through technical means, creating a security vulnerability and failing to guarantee the safety of plug-and-charge charging. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle charging method, apparatus, device, and storage medium to solve the technical problem that the VIN verification of the vehicle through the charging pile cloud platform before charging has security vulnerabilities, failing to guarantee the safety of charging when the vehicle is plugged in and charged. The technical solution of this application is as follows:

[0005] According to a first aspect of this application, a vehicle charging method is provided, applied to a target vehicle. The method includes: when the charging gun of a charging pile is connected to the target vehicle, receiving an operator identification message sent by the charging pile, the operator identification message including an operator identifier corresponding to the charging pile; obtaining charging parameter information based on the operator identifier corresponding to the charging pile, and sending the charging parameter information to the charging pile, the charging parameter information including at least one of the following: vehicle owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp; and when the charging pile determines that the target vehicle has passed charging authentication based on the charging parameter information, the target vehicle begins charging.

[0006] Based on the aforementioned technical means, this application can obtain charging parameter information based on the operator identification message sent by the charging pile, and send the charging parameter information to the charging pile. Charging can begin when the charging pile determines that the target vehicle has passed the charging authentication based on the charging parameter information. In other words, the vehicle can be plugged and charged instantly through the operator identification message sent by the charging pile. At the same time, the vehicle is authenticated for charging based on the charging parameter information, which solves the technical problem of security vulnerabilities in verifying the vehicle's VIN before charging. This improves the efficiency of vehicle charging and ensures the safety of vehicle charging during plug-and-charge.

[0007] In one possible implementation, charging parameter information is obtained based on the operator identifier corresponding to the charging pile, and the charging parameter information is sent to the charging pile. This includes: obtaining a key, vehicle owner identifier, target vehicle identifier, random parameters, timestamp, and key identifier based on the operator identifier corresponding to the charging pile, wherein the random parameters and timestamp are information generated in real time for the target vehicle; encrypting the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp using the key to obtain target ciphertext, and sending the target ciphertext and key identifier to the charging pile, wherein the target ciphertext and key identifier are used by the charging pile operator's cloud platform to perform charging authentication for the target vehicle.

[0008] Based on the aforementioned technical means, this application can encrypt the vehicle owner's identifier, the target vehicle identifier, random parameters, and timestamp to obtain the target ciphertext, and then send the target ciphertext to the charging pile, thereby ensuring the security of information transmission and preventing information theft during transmission.

[0009] In one possible implementation, the method further includes: obtaining user charging information from the vehicle operator cloud platform corresponding to the target vehicle. The user charging information includes at least one of the following: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The user charging information is generated when the user registers on the charging pile operator cloud platform. The user charging information is used to obtain charging parameter information when the target vehicle is charging.

[0010] Based on the aforementioned technical means, this application can obtain user charging information from the vehicle operator's cloud platform corresponding to the target vehicle, for use in subsequently obtaining charging parameter information.

[0011] According to the second aspect of this application, a vehicle charging method is provided, applied to a charging pile. The method includes: when the charging gun of the charging pile is connected to a target vehicle, sending an operator identification message to the target vehicle, the operator identification message including an operator identifier corresponding to the charging pile, the operator identifier corresponding to the charging pile being used by the target vehicle to obtain charging parameter information, the charging parameter information including at least one of the following: owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp; receiving target ciphertext and key identifier sent by the target vehicle, the target ciphertext being obtained by the target vehicle encrypting the owner identifier, target vehicle identifier, random parameters, and timestamp using the key, the random parameters and timestamp being information generated by the target vehicle in real time; sending the target ciphertext and key identifier to the charging pile operator cloud platform, the target ciphertext and key identifier being used by the charging pile operator cloud platform to perform charging authentication for the target vehicle; receiving a charging authentication pass message returned by the charging pile operator cloud platform, and starting charging for the target vehicle.

[0012] Based on the aforementioned technical means, this application can achieve plug-and-charge for vehicles by sending operator identification messages from the charging pile to the target vehicle, and perform charging authentication on the vehicle based on the target encrypted text and key identifier, so as to charge the target vehicle when the charging authentication is successful. This solves the technical problem of security vulnerabilities in verifying the vehicle's VIN during plug-and-charge, thereby improving the efficiency of vehicle charging and ensuring the safety of vehicle charging during plug-and-charge.

[0013] In one possible implementation, the method further includes: starting a timer while sending the target ciphertext and key identifier to the charging pile operator's cloud platform; and determining that the target vehicle has failed charging authentication if no charging authentication pass message is received from the charging pile operator's cloud platform after the timer has reached a first preset time.

[0014] Based on the above technical means, this application can determine that the target vehicle has failed the charging certification if no charging certification success message is received after the first preset time period has elapsed, thus avoiding the problem of poor user experience caused by not receiving the charging certification success message for a long time.

[0015] According to the third aspect of this application, a vehicle charging method is provided, applied to a charging pile operator cloud platform. The method includes: receiving target ciphertext and key identifier sent by the charging pile, wherein the target ciphertext is obtained by encrypting the owner identifier, target vehicle identifier, random parameters, and timestamp of the target vehicle using the key, and the random parameters and timestamp are information generated by the target vehicle in real time; determining a key based on the key identifier, and decrypting the target ciphertext using the key to obtain the owner identifier, target vehicle identifier, random parameters, and timestamp; performing charging authentication on the target vehicle based on the owner identifier, target vehicle identifier, random parameters, and timestamp, and returning a charging authentication success message to the charging pile if the charging authentication is successful, so that the charging pile can charge the target vehicle.

[0016] Based on the aforementioned technical means, this application can decrypt the target ciphertext to obtain the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp, and perform charging authentication on the target vehicle based on the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp, thus solving the problem of security vulnerabilities in security verification through the vehicle's VIN.

[0017] In one possible implementation, charging authentication of the target vehicle is performed based on the vehicle owner identifier, the target vehicle identifier, random parameters, and a timestamp. This includes: determining whether the timestamp is valid based on the current time and a second preset duration; if the timestamp is valid, determining whether the vehicle owner identifier, the target vehicle identifier, random parameters, and the timestamp already exist in the local cache; if the vehicle owner identifier, the target vehicle identifier, random parameters, and the timestamp do not exist in the local cache, determining whether the vehicle owner identifier and the target vehicle identifier match; if the vehicle owner identifier and the target vehicle identifier match, determining that the charging authentication of the target vehicle is successful, and caching the vehicle owner identifier, the target vehicle identifier, random parameters, and the timestamp locally for the second preset duration.

[0018] Based on the aforementioned technical means, this application can determine the validity of the timestamp based on the current time and a second preset duration, avoiding the problem of the timestamp becoming invalid due to excessive generation time; it can determine that the owner identifier, target vehicle identifier, random parameters, and timestamp do not exist in the local cache, avoiding the problem of replay attacks caused by this request being a duplicate request; it can determine that the owner identifier and target vehicle identifier match, preventing the charging pile from transmitting other users' owner identifiers through encrypted transmission of legitimate keys, thereby ensuring the security of vehicle charging.

[0019] According to the fourth aspect provided in this application, a vehicle charging device is provided, applied to a target vehicle. The vehicle charging device includes a transmission module and a processing module. The transmission module is used to receive an operator identification message sent by the charging pile when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The transmission module is also used to obtain charging parameter information based on the operator identifier corresponding to the charging pile and send the charging parameter information to the charging pile. The charging parameter information includes at least one of the following: vehicle owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp. The processing module is used to start charging the target vehicle when the charging pile determines that the target vehicle has passed the charging authentication based on the charging parameter information.

[0020] In one possible implementation, the transmission module is further configured to obtain a key, a vehicle owner identifier, a target vehicle identifier, random parameters, a timestamp, and a key identifier based on the operator identifier corresponding to the charging pile, wherein the random parameters and timestamp are information generated in real time for the target vehicle; the processing module is further configured to encrypt the vehicle owner identifier, the target vehicle identifier, the random parameters, and the timestamp using the key to obtain target ciphertext; the transmission module is further configured to send the target ciphertext and the key identifier to the charging pile, wherein the target ciphertext and the key identifier are used by the charging pile operator's cloud platform to perform charging authentication for the target vehicle.

[0021] In one possible implementation, the transmission module is further configured to obtain user charging information from the vehicle operator cloud platform corresponding to the target vehicle. The user charging information includes at least one of the following: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The user charging information is generated when the user registers on the charging pile operator cloud platform. The user charging information is used to obtain charging parameter information when the target vehicle is charging.

[0022] According to the fifth aspect provided in this application, a vehicle charging device is provided, applied to a charging pile. The vehicle charging device includes a transmission module and a processing module. The transmission module is used to send an operator identification message to the target vehicle when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The operator identifier corresponding to the charging pile is used by the target vehicle to obtain charging parameter information. The charging parameter information includes at least one of the following: owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp. The transmission module is also used to receive target ciphertext and key identifier sent by the target vehicle. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, target vehicle identifier, random parameters, and timestamp using the key. The random parameters and timestamp are information generated by the target vehicle in real time. The transmission module is also used to send the target ciphertext and key identifier to the charging pile operator cloud platform. The target ciphertext and key identifier are used by the charging pile operator cloud platform to perform charging authentication on the target vehicle. The transmission module is also used to receive a charging authentication pass message returned by the charging pile operator cloud platform. The processing module is used to start charging the target vehicle.

[0023] In one possible implementation, the vehicle charging device further includes a determination module; a processing module, which is further configured to start timing while sending the target ciphertext and key identifier to the charging pile operator's cloud platform; and a determination module, which is configured to determine that the target vehicle has failed charging authentication if the timing duration reaches a first preset duration and no charging authentication pass message is received from the charging pile operator's cloud platform.

[0024] According to the sixth aspect of this application, a vehicle charging device is provided, applied to a charging pile operator cloud platform. The vehicle charging device includes a transmission module, a determination module, and a processing module. The transmission module is used to receive target ciphertext and a key identifier sent by the charging pile. The target ciphertext is obtained by encrypting the owner identifier, target vehicle identifier, random parameters, and a timestamp using a key. The random parameters and timestamp are information generated by the target vehicle in real time. The determination module is used to determine a key based on the key identifier. The processing module is used to decrypt the target ciphertext using the key to obtain the owner identifier, target vehicle identifier, random parameters, and timestamp. The processing module is also used to perform charging authentication on the target vehicle based on the owner identifier, target vehicle identifier, random parameters, and timestamp. The transmission module is also used to return a charging authentication success message to the charging pile if the charging authentication is successful, so that the charging pile can charge the target vehicle.

[0025] In one possible implementation, the determining module is further configured to determine whether the timestamp is valid based on the current time and a second preset duration, and if the timestamp is valid, determine whether the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp already exist in the local cache; the determining module is further configured to determine whether the vehicle owner identifier and target vehicle identifier match if the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp do not exist in the local cache; the determining module is further configured to determine that the target vehicle charging authentication is successful if the vehicle owner identifier and target vehicle identifier match; the processing module is further configured to cache the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp locally, and the caching duration of the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp is the second preset duration.

[0026] According to a seventh aspect provided in this application, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement the method of the first aspect described above and any possible implementation thereof.

[0027] According to the eighth aspect provided in this application, a computer-readable storage medium is provided that, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the methods described in the first aspect and any possible implementation thereof.

[0028] According to the ninth aspect provided in this application, a computer program product is provided, the computer program product including computer instructions, which, when executed on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0029] Therefore, the above-mentioned technical features of this application have the following beneficial effects:

[0030] (1) The charging parameter information can be obtained based on the operator identification message sent by the charging pile and sent to the charging pile. The charging can start charging when the charging pile determines that the target vehicle has passed the charging authentication based on the charging parameter information. That is, the vehicle can be plugged and charged through the operator identification message sent by the charging pile. At the same time, the vehicle is authenticated for charging based on the charging parameter information. This solves the technical problem of security vulnerabilities in verifying the vehicle's VIN before charging, thereby improving the efficiency of charging the vehicle and ensuring the safety of vehicle charging when plugged and charged.

[0031] (2) The vehicle owner identifier, target vehicle identifier, random parameters and timestamp can be encrypted to obtain the target ciphertext, and then the target ciphertext can be sent to the charging pile to ensure the security of information transmission and prevent information from being stolen during transmission.

[0032] (3) User charging information can be obtained from the cloud platform of the vehicle operator corresponding to the target vehicle, which can be used to obtain charging parameter information later.

[0033] (4) The vehicle can be plugged and charged by sending the operator identification message to the target vehicle through the charging pile, and the vehicle can be charged based on the target ciphertext and key identifier. The vehicle can be charged if the charging authentication is successful. This solves the technical problem of security vulnerability in verifying the vehicle's VIN during plug-and-charge, thereby improving the efficiency of charging the vehicle and ensuring the safety of vehicle charging during plug-and-charge.

[0034] (5) If the charging authentication pass message is not received after the first preset time period is reached, it can be determined that the target vehicle has failed the charging authentication, thus avoiding the problem of poor user experience caused by not receiving the charging authentication pass message for a long time.

[0035] (6) The target ciphertext can be decrypted to obtain the owner identifier, target vehicle identifier, random parameters and timestamp, and the target vehicle can be charged based on the owner identifier, target vehicle identifier, random parameters and timestamp, which solves the problem of security vulnerabilities in security verification through the vehicle's VIN.

[0036] (7) The validity of the timestamp can be determined based on the current time and the second preset duration, avoiding the problem of the timestamp becoming invalid due to excessive generation time; it can be determined that there is no vehicle owner identifier, target vehicle identifier, random parameters and timestamp in the local cache, avoiding the problem of replay attack caused by the current request being a duplicate request; it can be determined that the vehicle owner identifier and the target vehicle identifier match, preventing the charging pile from transmitting other users' vehicle owner identifiers through the encryption of a valid key, thereby ensuring the security of vehicle charging.

[0037] It should be noted that the technical effects of any of the implementation methods in aspects two through nine can be found in the technical effects of the corresponding implementation methods in aspect one, and will not be repeated here.

[0038] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application, and do not constitute an undue limitation of this application.

[0040] Figure 1 This is a schematic diagram of the structure of a vehicle charging system according to an exemplary embodiment;

[0041] Figure 2This is a flowchart illustrating a vehicle charging method according to an exemplary embodiment;

[0042] Figure 3 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0043] Figure 4 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0044] Figure 5 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0045] Figure 6 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0046] Figure 7 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0047] Figure 8 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment;

[0048] Figure 9 This is a flowchart illustrating a vehicle charging authentication method according to an exemplary embodiment;

[0049] Figure 10 This is a block diagram illustrating a vehicle charging device according to an exemplary embodiment;

[0050] Figure 11 This is a block diagram illustrating yet another vehicle charging device according to an exemplary embodiment;

[0051] Figure 12 This is a block diagram illustrating yet another vehicle charging device according to an exemplary embodiment;

[0052] Figure 13 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0053] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0054] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0055] Currently, manufacturers and research institutions can certify electric vehicles to achieve plug-and-charge functionality through the following methods: First, the charging gun at the charging station reads the vehicle's VIN and uploads the VIN and charging station information to the charging station cloud platform. The cloud platform then verifies the VIN, and upon successful verification, sends a charging command to the charging station to initiate charging, thus achieving plug-and-charge functionality. Second, the vehicle is certified by connecting a mobile phone to the charging station via Bluetooth for communication, also achieving plug-and-charge functionality. Third, plug-and-charge functionality can be achieved by optimizing existing charging protocols and adding safety authentication mechanisms. Specifically, this can be done by adding plug-and-charge request messages (BCC) from the vehicle's battery management system (BMS) and plug-and-charge request messages (CCC) from the charging equipment for safety authentication.

[0056] However, in the methods described above, when the vehicle's VIN is verified through the charging pile cloud platform to achieve plug-and-charge, the VIN read by the charging gun is in plaintext. This allows for the forgery of the vehicle's VIN to commit fraud, creating a security vulnerability and failing to guarantee the safety of vehicle charging during plug-and-charge. Bluetooth authentication requires the user to carry a mobile phone and necessitates the installation of a Bluetooth module on the charging pile, increasing costs. Furthermore, Bluetooth connections may fail due to interference from other signals. While optimizing the existing charging protocol and adding a security authentication mechanism, multiple communications between the terminal device and the cloud platform are required each time charging authentication is performed. Network instability reduces the success rate of the plug-and-charge function, and multiple network communications increase user waiting time, resulting in a poor user experience. Additionally, plug-and-charge functionality cannot be implemented in areas without network access (such as underground parking garages).

[0057] For ease of understanding, the vehicle charging method provided in this application will be described in detail below with reference to the accompanying drawings.

[0058] The vehicle charging method provided in this application embodiment can be applied to vehicle charging systems. Figure 1 This is a schematic diagram illustrating the structure of a vehicle charging system according to an exemplary embodiment. Figure 1 As shown, the vehicle charging system 10 includes: a charging pile 11, a target vehicle 12, a charging pile operator cloud platform 13, and a vehicle operator cloud platform 14.

[0059] The charging pile 11 is used to send an operator identification message to the target vehicle 12, receive charging parameter information sent by the target vehicle 12, determine whether the target vehicle's charging authentication is successful based on the charging parameter information, and charge the target vehicle when the charging gun of the charging pile 11 is connected to the target vehicle 12. The target vehicle 12 is used to obtain charging parameter information based on the user's charging information according to the operator identification message sent by the charging pile 11 and send the charging parameter information to the charging pile 11. The charging pile operator cloud platform 13 is used to perform charging authentication on the target vehicle 12 and return a charging authentication success message to the charging pile 11. The vehicle operator cloud platform 14 is used to send user charging information to the target vehicle 12 so that the vehicle can be charged based on the charging pile 11, the target vehicle 12, the charging pile operator cloud platform 13, and the vehicle operator cloud platform 14.

[0060] Figure 2 This is a flowchart illustrating a vehicle charging method according to an exemplary embodiment, applied to a target vehicle, such as... Figure 2 As shown, the vehicle charging method includes the following steps:

[0061] S201. When the charging gun of the charging pile is connected to the target vehicle, receive the operator identification message sent by the charging pile.

[0062] The operator identification message includes the operator's identifier corresponding to the charging pile.

[0063] Optionally, when charging the target vehicle is required, the owner can connect the charging gun of the charging station to the target vehicle. Once the charging gun is successfully connected, the charging station sends a carrier identification message (CPM message) to the battery management system (BMS) of the connected target vehicle, and the BMS of the target vehicle receives the carrier identification message sent by the charging station. Timing can begin simultaneously with sending the carrier identification message to the BMS of the connected target vehicle via the charging station.

[0064] S202. Based on the operator's identifier corresponding to the charging pile, obtain the charging parameter information and send the charging parameter information to the charging pile.

[0065] The charging parameter information includes at least one of the following: owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp.

[0066] Optionally, based on the operator identifier (CPCODE) corresponding to the charging pile included in the operator identification message, the BMS of the target vehicle can obtain charging parameter information including the owner identifier (CUID), target vehicle identifier (VIN), key (KEY), key identifier (KEYID), random parameters (NONCE), and timestamp (TIMESTAMP), and send the charging parameter information to the charging pile through the BMS of the target vehicle based on the vehicle and user identification message (UVM message).

[0067] If the target vehicle's BMS fails to obtain charging parameter information and the charging pile does not receive charging parameter information when the timing duration exceeds the preset timing duration (i.e., ΔT1), it indicates that the vehicle has not implemented the plug-and-charge protocol, and the charging pile enters the non-plug-and-charge charging process.

[0068] For example, the operator identifier corresponding to the charging pile can be 8 bytes, the random parameter can be a 4-byte random number, the timestamp can be 4 bytes, the vehicle owner identifier can be a 4-byte unsigned integer, the key can be 16 bytes, the key identifier can be a 4-byte unsigned integer, and the preset timing duration can be set to 1-3 seconds.

[0069] It should be noted that CPM and UVM messages are new messages added based on the "Communication Protocol between Off-board Conductive Chargers and Battery Management Systems for Electric Vehicles" (GB / T 27930-2015). The current GB / T 27930-2015 does not include secure design for vehicle and user identification, nor does it reserve sufficient extended fields in the handshake message.

[0070] For example, as shown in Table 1, the details of CPM and UVM messages are shown, including the message description, parameter group number (PGN), priority, data length, message period, source address, and destination address.

[0071] Table 1 As shown in Table 2, the format of a CPM message is illustrated, which includes the start byte or bit, length, SPN, SPN definition, and sending options.

[0072] Table 2

[0073] start byte or bit length SPN SPN Definition Send options 1 8 4001 Charging operator code must

[0074] As shown in Table 3, the format of a UVM message is illustrated, which includes the start byte or bits, length, SPN, SPN definition, and sending options.

[0075] Table 3

[0076]

[0077] It should be noted that the charging operator codes in Table 1 are the operator identifiers corresponding to the charging piles.

[0078] S203. If the charging station determines that the target vehicle has passed the charging certification based on the charging parameter information, the target vehicle will begin charging.

[0079] Figure 3 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment, such as... Figure 3 As shown, the method in step S202 above specifically includes the following steps:

[0080] S301. Based on the operator identifier corresponding to the charging pile, obtain the key, vehicle owner identifier, target vehicle identifier, random parameters, timestamp, and key identifier.

[0081] The random parameters and timestamps are information generated in real time for the target vehicle.

[0082] Optionally, based on the operator's identifier corresponding to the charging pile, the corresponding key, owner identifier, and target vehicle identifier can be obtained by querying the BMS of the target vehicle. When the corresponding key, owner identifier, and target vehicle identifier are found in the BMS of the target vehicle, random parameters can be generated and the current timestamp can be obtained.

[0083] S302. The target ciphertext is obtained by encrypting the vehicle owner identifier, target vehicle identifier, random parameters and timestamp using a key, and then the target ciphertext and key identifier are sent to the charging pile.

[0084] Among them, the target ciphertext and key identifier are used by the charging pile operator's cloud platform to authenticate the target vehicle for charging.

[0085] Optionally, the owner identifier, target vehicle identifier, random parameters, and timestamp can be assembled in plaintext using the target vehicle's BMS in the manner of VIN+CUID+NONCE+TIMESTAMP. Furthermore, the assembled owner identifier, target vehicle identifier, random parameters, and timestamp can be encrypted using AES using a key to obtain the target ciphertext (i.e., ENCRYPT_DATA), and the target ciphertext and key identifier can be sent to the charging pile through the target vehicle's BMS.

[0086] For example, the specific encryption mode for AES encryption can be: AES / ECB / PKCS7Padding.

[0087] Figure 4 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment, such as... Figure 4As shown, the method also includes the following steps:

[0088] S401. Obtain user charging information from the cloud platform of the vehicle operator corresponding to the target vehicle.

[0089] It is understandable that user charging information can be obtained from the cloud platform of the vehicle operator corresponding to the target vehicle through the charging pile.

[0090] The user charging information includes at least one of the following: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The user charging information is generated when the user registers on the charging pile operator's cloud platform. The user charging information is used to obtain charging parameter information when the target vehicle is charging.

[0091] Optionally, users can register an account on the charging pile cloud platform and fill in the VIN of the target vehicle to bind the target vehicle. After the account is registered, the charging pile cloud platform generates a corresponding vehicle owner identifier for the user and performs a unique verification of the VIN of the target vehicle. After the target vehicle is successfully bound, the charging pile cloud platform generates a set of key identifiers and keys for the target vehicle and enables the plug-and-charge function for the target vehicle.

[0092] It's important to note that registering an account and binding a vehicle on the charging pile cloud platform only needs to be done once. Subsequent binding is unnecessary if the bound vehicles remain the same. One account can be bound to multiple vehicles simultaneously, facilitating unified payment for charging across multiple vehicles. Plug-and-charge functionality can be enabled for individual vehicles or all vehicles under any account. Before enabling plug-and-charge, pre-payment or binding a third-party payment platform's pay-later feature is required for the current account. The key identifier is unique within the charging pile cloud platform and is used for subsequent AES encryption and decryption.

[0093] When automakers need to enable plug-and-charge functionality for a particular operator's charging stations, they need to integrate the operator's charging stations with the charging station operator's cloud platform. Specifically, this can be achieved by authorizing any user's charging information from the charging station operator's cloud platform to the vehicle operator's cloud platform. The vehicle operator's cloud platform can then associate the received user charging information with the target vehicle and store it persistently.

[0094] After the vehicle operator's cloud platform successfully receives the user charging information synchronized from the charging pile operator's platform, if the target vehicle is online, the user charging information can be sent to the target vehicle through the established communication channel. Correspondingly, when the target vehicle is powered on and started, the above user charging information can be actively obtained through the application programming interface (API) interface on the target vehicle. If the current user has enabled the plug-and-charge function on multiple charging pile operator cloud platforms simultaneously, multiple records (i.e., user charging information from multiple charging pile operator cloud platforms) can be obtained simultaneously through the API on the target vehicle, and the target vehicle can persistently store the obtained user charging information.

[0095] It should be noted that authorization can be achieved through the industry-standard OAuth 2.0 protocol. After authorization, the user can access specific interfaces on the charging station operator's cloud platform using the authorization credentials to obtain the user's charging information on the platform. The operator identifiers for different operators must be unique.

[0096] One possible implementation is to persistently store the acquired user charging information through the target vehicle so that it can be used directly during subsequent charging processes without having to retrieve it from the cloud again.

[0097] Figure 5 This is a flowchart illustrating another vehicle charging method according to an exemplary embodiment, applied to charging piles, such as... Figure 5 As shown, the method includes the following steps:

[0098] S501. When the charging gun of the charging pile is connected to the target vehicle, send an operator identification message to the target vehicle.

[0099] The operator identification message includes the operator identifier corresponding to the charging pile. The operator identifier corresponding to the charging pile is used by the target vehicle to obtain charging parameter information. The charging parameter information includes at least one of the following: vehicle owner identifier, target vehicle identifier, key, key identifier, random parameters, and timestamp.

[0100] It is understandable that when the charging gun of the charging station is connected to the target vehicle, the operator identification message is sent to the target vehicle through the charging station.

[0101] S502, Receive the target ciphertext and key identifier sent by the target vehicle.

[0102] The target ciphertext is obtained by encrypting the owner's identifier, the target vehicle identifier, random parameters, and timestamp using a key. The random parameters and timestamp are information generated by the target vehicle in real time.

[0103] It is understandable that the target encrypted text and key identifier sent by the target vehicle can be received through the charging pile.

[0104] S503. Send the target ciphertext and key identifier to the charging pile operator's cloud platform.

[0105] Among them, the target ciphertext and key identifier are used by the charging pile operator's cloud platform to authenticate the target vehicle for charging.

[0106] It is understandable that the target ciphertext and key identifier can be sent to the charging station operator's cloud platform through the charging station.

[0107] S504: Receive the charging authentication pass message returned by the charging pile operator's cloud platform and start charging the target vehicle.

[0108] It is understandable that the charging station can receive a charging authentication message from the charging station operator's cloud platform and begin charging the target vehicle.

[0109] Optionally, after charging the target vehicle via a charging station is completed, an order can be automatically generated and payment deducted based on the currently identified charging station operator's cloud platform, following the process of scanning a code or swiping a card for charging.

[0110] Figure 6 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment, such as... Figure 6 As shown, the method also includes the following steps:

[0111] S601. Start timing while sending the target ciphertext and key identifier to the charging pile operator's cloud platform.

[0112] It is understandable that timing can begin simultaneously with sending the target ciphertext and key identifier to the charging station operator's cloud platform via the charging station.

[0113] S602. If the charging authentication is not approved after the first preset time has elapsed, it is determined that the target vehicle has failed the charging authentication.

[0114] Optionally, if the charging pile does not receive a charging authentication pass message from the charging pile operator's cloud platform after the timing duration reaches the first preset duration (i.e., ΔT2), it is determined that the target vehicle has failed the charging authentication and enters the non-plug-and-charge charging process.

[0115] For example, the first preset duration can be set to 1-3 seconds.

[0116] Figure 7 This is a flowchart illustrating another vehicle charging method according to an exemplary embodiment, applied to a charging pile operator's cloud platform, such as... Figure 7As shown, the method includes the following steps:

[0117] S701, Receive the target ciphertext and key identifier sent by the charging pile.

[0118] The target ciphertext is obtained by encrypting the owner's identifier, the target vehicle identifier, random parameters, and timestamp using a key. The random parameters and timestamp are information generated by the target vehicle in real time.

[0119] It is understandable that the target ciphertext and key identifier sent by the charging pile can be received through the charging pile operator's cloud platform.

[0120] S702. Determine the key based on the key identifier, and decrypt the target ciphertext using the key to obtain the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp.

[0121] Optionally, based on the key identifier, the corresponding key can be queried from the database through the charging pile operator's cloud platform. If the corresponding key is not found in the database, a charging authentication failure message is directly returned to the charging pile. If the corresponding key is found in the database, the target ciphertext is further decrypted using the key. If the decryption of the target ciphertext using the key is successful, the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp are obtained. If the decryption of the target ciphertext using the key fails, a charging authentication failure message is returned.

[0122] S703 performs charging authentication for the target vehicle based on the owner's identifier, the target vehicle identifier, random parameters, and timestamp.

[0123] It is understandable that charging authentication of target vehicles can be performed through the charging pile operator's cloud platform based on the vehicle owner's identifier, the target vehicle's identifier, random parameters, and timestamps.

[0124] S704. If the charging authentication is successful, return a charging authentication success message to the charging station so that the charging station can charge the target vehicle.

[0125] Optionally, if the charging certification is successful, the charging pile operator's cloud platform can return a charging certification success message to the charging pile, so that the charging pile can conduct subsequent communication in accordance with the GB / T 27930-2015 protocol and start charging the target vehicle.

[0126] Figure 8 This is a flowchart illustrating yet another vehicle charging method according to an exemplary embodiment, such as... Figure 8 As shown, the method in step S703 above specifically includes the following steps:

[0127] S801. Determine whether the timestamp is valid based on the current time and the second preset duration, and if the timestamp is valid, determine whether the vehicle owner identifier, target vehicle identifier, random parameters and timestamp already exist in the local cache.

[0128] Optionally, if the difference between the current time and the time corresponding to the timestamp is less than the second preset duration (i.e., ΔT3), the timestamp is determined to be valid through the charging pile operator's cloud platform. If the timestamp is valid, the charging pile operator's cloud platform determines whether the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp already exist in the local cache. If the difference between the current time and the time corresponding to the timestamp is greater than or equal to the second preset duration, the timestamp is determined to be invalid through the charging pile operator's cloud platform, and a charging authentication failure message is returned to the charging pile.

[0129] If the charging station operator's cloud platform determines that the vehicle owner's identifier, target vehicle identifier, random parameters, and timestamp already exist in the local cache, it indicates that this charging authentication request is a duplicate request, which may be a replay attack. In this case, a charging authentication failure message is returned to the charging station. If the charging station operator's cloud platform determines that the vehicle owner's identifier, target vehicle identifier, random parameters, and timestamp do not exist in the local cache, then it is necessary to further determine whether the vehicle owner's identifier and the target vehicle identifier match.

[0130] It should be noted that the second preset duration can be set according to the local cache capacity; that is, the larger the local cache capacity, the longer the second preset duration can be.

[0131] S802. If it is determined that the owner identifier, target vehicle identifier, random parameters and timestamp do not exist in the local cache, determine whether the owner identifier and target vehicle identifier match.

[0132] Optionally, if the charging pile operator's cloud platform determines that the vehicle owner's identifier and the target vehicle's identifier match, the vehicle owner's identifier, the target vehicle's identifier, random parameters, and timestamp in this charging authentication request are cached locally, and the cache duration (i.e., the cache validity period) is set to the second preset duration; if the charging pile operator's cloud platform determines that the vehicle owner's identifier and the target vehicle's identifier do not match, a charging authentication failure message is returned to the charging pile.

[0133] It should be noted that setting the cache duration to the second preset duration is to prevent replay attacks. Ensuring the vehicle owner's identifier matches the target vehicle's identifier prevents the charging station from transmitting other users' vehicle owner's identifiers using a legitimate key for encryption.

[0134] S803: If the owner's identifier and the target vehicle's identifier match, the charging authentication of the target vehicle is confirmed to be successful, and the owner's identifier, the target vehicle's identifier, random parameters and timestamp are cached locally.

[0135] The caching duration for the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp is the second preset duration.

[0136] Optionally, if the vehicle owner's identifier and the target vehicle's identifier match, the system further determines, based on the target vehicle's identifier, whether the target vehicle has enabled the plug-and-charge function through the charging pile operator's cloud platform. If the charging pile operator's cloud platform determines that the target vehicle has enabled the plug-and-charge function, the charging authentication for the target vehicle is deemed successful, and a successful charging authentication message is returned to the charging pile; if the charging pile operator's cloud platform determines that the target vehicle has not enabled the plug-and-charge function, a failed charging authentication message is returned to the charging pile.

[0137] Figure 9 This is a flowchart illustrating a vehicle charging authentication method according to an exemplary embodiment, such as... Figure 9 As shown, after the charging pile operator's cloud platform receives the authentication request, it checks whether the KEYID exists. If the KEYID does not exist, authentication fails. If the KEYID exists, it further checks whether the ENCRYPT_DATA was successfully decrypted. If the ENCRYPT_DATA decryption fails, authentication fails again. If the ENCRYPT_DATA decryption succeeds, it further checks whether the authentication request is a duplicate request. If the authentication request is a duplicate request, authentication fails again. If the authentication request is not a duplicate request, it further checks whether the KEYID and CUID match. If the KEYID and CUID do not match, authentication fails again. If the KEYID and CUID match, it further checks whether the CUID and VIN match. If the CUID and VIN do not match, authentication fails again. If the CUID and VIN match, the request record is cached, and it is checked whether the VIN has the plug-and-charge function enabled. If the VIN does not have the plug-and-charge function enabled, authentication fails again. If the VIN has the plug-and-charge function enabled, authentication succeeds.

[0138] This application provides a vehicle charging method. Without increasing hardware costs, this method optimizes existing charging protocols, addresses current security vulnerabilities in plug-and-charge systems, reduces the number of authentication steps and time required, and improves charging authentication efficiency. It enables plug-and-charge vehicles even in locations without network access (where the charging station and vehicle are connected via a network cable).

[0139] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the vehicle charging device or electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0140] This application embodiment can, according to the above method, exemplarily divide a vehicle charging device or electronic device into functional modules. For example, the vehicle charging device or electronic device may include functional modules corresponding to each functional division, or two or more functions may be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0141] Figure 10 This is a block diagram illustrating a vehicle charging device according to an exemplary embodiment. (Refer to...) Figure 10 The vehicle charging device 70 includes: a transmission module 701 and a processing module 702;

[0142] The transmission module 701 is used to receive the operator identification message sent by the charging pile when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile.

[0143] The transmission module 701 is also used to obtain charging parameter information based on the operator identifier corresponding to the charging pile, and send the charging parameter information to the charging pile. The charging parameter information includes at least one of the following: vehicle owner identifier, target vehicle identifier, key, key identifier, random parameter and timestamp;

[0144] The processing module 702 is used to start charging the target vehicle when the charging pile determines that the target vehicle has passed the charging certification based on the charging parameter information.

[0145] In one possible implementation, the transmission module 701 is further configured to obtain a key, a vehicle owner identifier, a target vehicle identifier, random parameters, a timestamp, and a key identifier based on the operator identifier corresponding to the charging pile, wherein the random parameters and timestamp are information generated in real time for the target vehicle; the processing module 702 is further configured to encrypt the vehicle owner identifier, the target vehicle identifier, the random parameters, and the timestamp using the key to obtain target ciphertext; the transmission module 701 is further configured to send the target ciphertext and the key identifier to the charging pile, wherein the target ciphertext and the key identifier are used by the charging pile operator's cloud platform to perform charging authentication for the target vehicle.

[0146] In one possible implementation, the transmission module 701 is further configured to obtain user charging information from the vehicle operator cloud platform corresponding to the target vehicle. The user charging information includes at least one of the following: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The user charging information is generated when the user registers on the charging pile operator cloud platform. The user charging information is used to obtain charging parameter information when the target vehicle is charging.

[0147] Figure 11 This is a block diagram illustrating yet another vehicle charging device according to an exemplary embodiment. (Refer to...) Figure 11 The vehicle charging device 80 includes: a transmission module 801 and a processing module 802;

[0148] The transmission module 801 is used to send an operator identification message to the target vehicle when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The operator identifier corresponding to the charging pile is used by the target vehicle to obtain charging parameter information. The charging parameter information includes at least one of the following: vehicle owner identifier, target vehicle identifier, key, key identifier, random parameter and timestamp.

[0149] The transmission module 801 is also used to receive the target ciphertext and key identifier sent by the target vehicle. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, the target vehicle identifier, random parameters and timestamp using the key. The random parameters and timestamp are information generated by the target vehicle in real time.

[0150] The transmission module 801 is also used to send the target ciphertext and key identifier to the charging pile operator cloud platform. The target ciphertext and key identifier are used by the charging pile operator cloud platform to perform charging authentication on the target vehicle.

[0151] The transmission module 801 is also used to receive a charging authentication pass message returned by the charging pile operator's cloud platform;

[0152] Processing module 802 is used to start charging the target vehicle.

[0153] In one possible implementation, the vehicle charging device 80 further includes a determination module 803; a processing module 802, which is also used to start timing while sending the target ciphertext and key identifier to the charging pile operator cloud platform; and a determination module 803, which is used to determine that the target vehicle has failed charging authentication if the timing duration reaches a first preset duration and no charging authentication pass message is received from the charging pile operator cloud platform.

[0154] Figure 12 This is a block diagram illustrating yet another vehicle charging device according to an exemplary embodiment. (Refer to...) Figure 12 The vehicle charging device 90 includes: a transmission module 901, a determination module 902, and a processing module 903;

[0155] Transmission module 901 is used to receive target ciphertext and key identifier sent by charging pile. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, target vehicle identifier, random parameters and timestamp through the key. The random parameters and timestamp are information generated by the target vehicle in real time.

[0156] Determining module 902 is used to determine the key based on the key identifier;

[0157] The processing module 903 is used to decrypt the target ciphertext using a key to obtain the vehicle owner identifier, the target vehicle identifier, random parameters, and a timestamp.

[0158] The processing module 903 is also used to perform charging authentication on the target vehicle based on the vehicle owner identifier, the target vehicle identifier, random parameters and timestamp;

[0159] The transmission module 901 is also used to return a charging authentication success message to the charging pile when the charging authentication is successful, so that the charging pile can charge the target vehicle.

[0160] In one possible implementation, the determining module 902 is further configured to determine whether the timestamp is valid based on the current time and a second preset duration, and if the timestamp is valid, determine whether the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp already exist in the local cache; the determining module 902 is further configured to determine whether the vehicle owner identifier and target vehicle identifier match if the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp do not exist in the local cache; the determining module 902 is further configured to determine that the target vehicle charging authentication is successful if the vehicle owner identifier and target vehicle identifier match; the processing module 903 is further configured to cache the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp locally, and the caching duration of the vehicle owner identifier, target vehicle identifier, random parameters, and timestamp is the second preset duration.

[0161] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0162] Figure 13 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Figure 13 As shown, the electronic device 100 includes, but is not limited to, a processor 1001 and a memory 1002.

[0163] The memory 1002 described above is used to store executable instructions of the processor 1001. It is understood that the processor 1001 is configured to execute instructions to implement the vehicle charging method in the above embodiments.

[0164] It should be noted that those skilled in the art will understand that Figure 13 The electronic device structure shown does not constitute a limitation on the electronic device; the electronic device may include, but is not limited to, other electronic devices. Figure 13 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0165] The processor 1001 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 1002, and by calling data stored in the memory 1002, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. The processor 1001 may include one or more processing modules. Optionally, the processor 1001 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1001.

[0166] The memory 1002 can be used to store software programs and various data. The memory 1002 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and application programs required by at least one functional module (such as an acquisition unit, a determination unit, a processing unit, etc.). Furthermore, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0167] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 1002 including instructions, which can be executed by a processor 1001 of an electronic device 1000 to implement the vehicle charging method in the above embodiments.

[0168] In actual implementation, Figure 10 The transmission module 701 and processing module 702 in the middle Figure 11 The transmission module 801, processing module 802, and determination module 803 are included. Figure 12 The functions of the transmission module 901, the determination module 902, and the processing module 903 can all be provided by... Figure 13 The processor 1001 calls the computer program stored in the memory 1002 to implement the process. The specific execution process can be found in the description of the vehicle charging method section of the previous embodiment, and will not be repeated here.

[0169] Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.

[0170] In an exemplary embodiment, this application also provides a computer program product including one or more instructions, which can be executed by the processor 1001 of an electronic device to complete the vehicle charging method in the above embodiments.

[0171] It should be noted that when one or more instructions in the computer-readable storage medium or computer program product are executed by the processor of the electronic device, they implement the various processes of the above-described vehicle charging method embodiments and achieve the same technical effects as the above-described vehicle charging method. To avoid repetition, they will not be described again here.

[0172] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0174] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the classified units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0175] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0176] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, essentially, or the part that contributes to the prior art, or a complete or partial classification of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0177] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A vehicle charging method, characterized in that, Applied to a target vehicle, the method includes: When the charging gun of the charging pile is connected to the target vehicle, the operator identification message sent by the charging pile is received, and the operator identification message includes the operator identifier corresponding to the charging pile. Based on the operator identifier corresponding to the charging pile and the locally stored user charging information, a key, vehicle owner identifier, target vehicle identifier, random parameters, timestamp, and key identifier are obtained. The random parameters and timestamp are information generated in real time for the target vehicle. The user charging information includes: the vehicle owner identifier, the key, the key identifier, and the operator identifier corresponding to the charging pile. The target ciphertext is obtained by encrypting the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp using the key. The target ciphertext and the key identifier are then sent to the charging pile. The target ciphertext and the key identifier are used by the charging pile operator's cloud platform to authenticate the target vehicle for charging. Once the charging station determines that the target vehicle has passed the charging authentication based on the target ciphertext and the key identifier, the target vehicle begins charging.

2. The method according to claim 1, characterized in that, The method further includes: User charging information is obtained from the vehicle operator cloud platform corresponding to the target vehicle. The user charging information is generated when the user registers on the charging pile operator cloud platform. The user charging information is used to obtain the target ciphertext and the key identifier when the target vehicle is charging.

3. A vehicle charging method, characterized in that, Applied to charging piles, the method includes: When the charging gun of the charging pile is connected to the target vehicle, an operator identification message is sent to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The operator identifier corresponding to the charging pile is used by the target vehicle to obtain target encrypted text and key identifier based on the target vehicle identifier, random parameters, timestamp, and user charging information stored locally by the target vehicle. The user charging information includes: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The random parameters and timestamp are information generated by the target vehicle in real time. The system receives the target ciphertext and the key identifier sent by the target vehicle. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, the target vehicle identifier, the random parameter, and the timestamp using the key. The target ciphertext and the key identifier are sent to the charging pile operator's cloud platform, and the target ciphertext and the key identifier are used by the charging pile operator's cloud platform to perform charging authentication for the target vehicle; Upon receiving the charging authentication pass message returned by the charging pile operator's cloud platform, charging of the target vehicle begins.

4. The method according to claim 3, characterized in that, The method further includes: The timing begins simultaneously with sending the target ciphertext and the key identifier to the charging pile operator's cloud platform; If the charging authentication is not approved by the charging pile operator's cloud platform after the first preset time period has elapsed, it is determined that the target vehicle has failed the charging authentication.

5. A vehicle charging method, characterized in that, The method, applied to a charging pile operator's cloud platform, includes: The system receives target ciphertext and key identifier sent by the charging pile. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, target vehicle identifier, random parameters, and timestamp using a key. The random parameters and timestamp are information generated by the target vehicle in real time. The key, owner identifier, and key identifier are obtained by the target vehicle based on the operator identifier corresponding to the charging pile and the user charging information stored locally by the target vehicle. The user charging information includes: the owner identifier, the key, key identifier, and the operator identifier corresponding to the charging pile. The key is determined based on the key identifier, and the target ciphertext is decrypted using the key to obtain the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp; The target vehicle is authenticated for charging based on the owner's identifier, the target vehicle identifier, the random parameters, and the timestamp. If the charging authentication is successful, a charging authentication success message is returned to the charging pile so that the charging pile can charge the target vehicle.

6. The method according to claim 5, characterized in that, The charging authentication of the target vehicle based on the vehicle owner identifier, the target vehicle identifier, the random parameters, and the timestamp includes: Based on the current time and a second preset duration, determine whether the timestamp is valid, and if the timestamp is valid, determine whether the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp already exist in the local cache; If it is determined that the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp do not exist in the local cache, determine whether the vehicle owner identifier and the target vehicle identifier match; If the owner identifier and the target vehicle identifier are found to match, the charging authentication of the target vehicle is determined to be successful, and the owner identifier, the target vehicle identifier, the random parameter and the timestamp are cached locally. The caching duration of the owner identifier, the target vehicle identifier, the random parameter and the timestamp is the second preset duration.

7. A vehicle charging device, applied to a target vehicle, characterized in that, The vehicle charging device includes a transmission module and a processing module; The transmission module is used to receive an operator identification message sent by the charging pile when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The transmission module is further configured to obtain a key, a vehicle owner identifier, a target vehicle identifier, random parameters, a timestamp, and a key identifier based on the operator identifier corresponding to the charging pile and the user charging information stored locally. The random parameters and the timestamp are information generated in real time for the target vehicle. The user charging information includes: the vehicle owner identifier, the key, the key identifier, and the operator identifier corresponding to the charging pile. The processing module is used to encrypt the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp using the key to obtain the target ciphertext. The transmission module is further configured to send the target ciphertext and the key identifier to the charging pile, wherein the target ciphertext and the key identifier are used by the charging pile operator cloud platform to perform charging authentication on the target vehicle; The processing module is further configured to allow the target vehicle to begin charging when the charging pile determines that the target vehicle has passed the charging authentication based on the target ciphertext and the key identifier.

8. A vehicle charging device, applied to a charging pile, characterized in that, The vehicle charging device includes a transmission module and a processing module; The transmission module is used to send an operator identification message to the target vehicle when the charging gun of the charging pile is connected to the target vehicle. The operator identification message includes the operator identifier corresponding to the charging pile. The operator identifier corresponding to the charging pile is used by the target vehicle to obtain target encrypted text and key identifier based on the target vehicle identifier, random parameters, timestamp, and user charging information stored locally by the target vehicle. The user charging information includes: vehicle owner identifier, key, key identifier, and operator identifier corresponding to the charging pile. The random parameters and timestamp are information generated by the target vehicle in real time. The transmission module is further configured to receive the target ciphertext and the key identifier sent by the target vehicle, wherein the target ciphertext is obtained by the target vehicle encrypting the owner identifier, the target vehicle identifier, the random parameter and the timestamp using the key; The transmission module is further configured to send the target ciphertext and the key identifier to the charging pile operator cloud platform, wherein the target ciphertext and the key identifier are used by the charging pile operator cloud platform to perform charging authentication on the target vehicle; The transmission module is also used to receive a charging authentication pass message returned by the charging pile operator's cloud platform; The processing module is used to start charging the target vehicle.

9. A vehicle charging device, applied to a charging pile operator's cloud platform, characterized in that, The vehicle charging device includes a transmission module, a determination module, and a processing module; The transmission module is used to receive target ciphertext and key identifier sent by the charging pile. The target ciphertext is obtained by the target vehicle encrypting the owner identifier, target vehicle identifier, random parameters, and timestamp using a key. The random parameters and timestamp are information generated by the target vehicle in real time. The key, the owner identifier, and the key identifier are obtained by the target vehicle based on the operator identifier corresponding to the charging pile and the user charging information stored locally by the target vehicle. The user charging information includes: the owner identifier, the key, the key identifier, and the operator identifier corresponding to the charging pile. The determining module is used to determine the key based on the key identifier; The processing module is used to decrypt the target ciphertext using the key to obtain the vehicle owner identifier, the target vehicle identifier, the random parameter, and the timestamp; The processing module is also used to perform charging authentication on the target vehicle based on the vehicle owner identifier, the target vehicle identifier, the random parameters, and the timestamp; The transmission module is also used to return a charging authentication success message to the charging pile when the charging authentication is successful, so that the charging pile can charge the target vehicle.

10. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 1 to 6.

11. A computer-readable storage medium, characterized in that, When the computer-executable instructions stored in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is capable of performing the method as described in any one of claims 1 to 6.

Images