A charging billing method and system for a vehicle

Abstract

The application provides a charging billing method of a vehicle, which is applied to a charging billing system comprising a vehicle machine charging end, a billing end and a charging background end which are connected in communication with each other, and comprises the following steps: the vehicle machine charging end sends a charging billing request to the billing end bound thereto, wherein the charging billing request is generated by encrypting user's household number information and a vehicle identifier according to a preset public key; the billing end decrypts and processes the charging billing request through a private key to obtain the vehicle identifier and the household number information; the billing end judges whether the vehicle identifier obtained by decryption is consistent with the vehicle identifier of the vehicle machine charging end bound to the billing end; if yes, the charging background end is reminded to perform charging billing according to the household number information; if not, the charging background end is reminded to perform charging billing in a public way. Through the charging billing method and system of the vehicle, the vehicle charging cost of a community owner can be reduced.

Description

Technical Field

[0001] This invention relates to the field of vehicle charging billing technology, and in particular to a vehicle charging billing method and system. Background Technology

[0002] With the increasing popularity of new energy vehicles, the charging demand in residential communities has increased significantly. The existing charging station system only allows vehicle owners to charge using the public power supply system. However, the electricity cost of the public power supply system is relatively high for residents, increasing their charging costs and discouraging them from using electric vehicles, thus negatively impacting their living experience. Therefore, improvements are needed. Summary of the Invention

[0003] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a charging billing method and system for vehicles, which improves the problem of high vehicle charging costs for residents in residential communities.

[0004] To solve the above-mentioned technical problems, the present invention is achieved through the following technical solution:

[0005] This invention provides a charging billing method for vehicles, applied to a charging billing system comprising a vehicle-mounted charging terminal, a billing terminal, and a charging backend terminal that are communicatively connected to each other. The charging billing method includes:

[0006] The vehicle charging terminal sends a charging billing request to the billing terminal bound to it, wherein the charging billing request is generated by encrypting the user's account number information and vehicle identifier according to a preset public key;

[0007] The billing terminal receives the charging billing request and decrypts the charging billing request using a private key to obtain the vehicle identifier and account number information.

[0008] The billing terminal determines whether the vehicle identifier obtained through decryption matches the vehicle identifier bound to the vehicle charging terminal:

[0009] If the vehicle identifier obtained through decryption matches the vehicle identifier of the vehicle charging terminal bound to the billing terminal, then the charging backend terminal is reminded to perform charging billing according to the account number information.

[0010] If the vehicle identifier obtained through decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend terminal is reminded to perform charging billing in accordance with the public method.

[0011] In one embodiment of the present invention, before the step of the vehicle-mounted charging terminal sending a charging billing request to the billing terminal bound to it, the method further includes:

[0012] The vehicle-mounted charging terminal sends a charging request to the charging backend terminal, wherein the charging request is generated based on the user's account number information;

[0013] The charging backend receives the charging request and determines whether the account number information in the charging request is in a preset account number information database:

[0014] If so, the charging backend terminal will charge the user number according to the user number information;

[0015] If not, the charging backend terminal will charge the charging in a public manner.

[0016] In one embodiment of the present invention, before the step of the vehicle-mounted charging terminal sending a charging billing request to the billing terminal bound to it, the method further includes:

[0017] The vehicle-mounted charging terminal sends a charging request to the charging backend terminal, wherein the charging request is generated based on the user's account number information;

[0018] The charging backend receives the charging request and determines whether the account number information in the charging request is in a preset account number information database:

[0019] If present, the vehicle charging terminal is reminded to send the charging billing request to the billing terminal bound to it.

[0020] If not, the charging backend terminal will charge the charging in a public manner.

[0021] In one embodiment of the present invention, the vehicle charging terminal and the billing terminal are bound together according to the following steps:

[0022] The billing terminal obtains a key generation request, generates a public key and a corresponding private key based on the key generation request, and sends the public key to the vehicle charging terminal.

[0023] The vehicle charging terminal receives the public key and sends a vehicle binding request to the billing terminal, wherein the vehicle binding request includes the user's account number information and vehicle identifier;

[0024] The billing terminal receives the vehicle-to-machine binding request and binds the vehicle-to-machine charging terminal to the billing terminal according to the vehicle identifier in the vehicle-to-machine binding request.

[0025] In one embodiment of the present invention, the step of generating the charging billing request by encrypting the user's account number information and vehicle identifier according to a preset public key includes:

[0026] The vehicle charging terminal encrypts the user's account number information, vehicle identifier, and preset public key according to a preset encryption algorithm to generate a charging billing request; wherein, the encryption algorithm includes RSA encryption algorithm or ECC encryption algorithm.

[0027] In one embodiment of the present invention, the preset public key is randomly generated by the billing terminal according to the key generation request.

[0028] In one embodiment of the present invention, the steps of receiving the charging billing request and decrypting the charging billing request using a private key to obtain the vehicle identifier and account number information include:

[0029] The billing terminal receives the charging billing request;

[0030] The billing terminal decrypts the charging billing request according to a preset decryption algorithm and private key to obtain the vehicle identifier and account number information; wherein, the decryption algorithm corresponds to the encryption algorithm and includes: RSA decryption algorithm or ECC decryption algorithm.

[0031] In one embodiment of the present invention, the charging billing request further includes charging power information; the step of reminding the charging backend to perform charging billing according to the public method if the vehicle identifier obtained by decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal includes:

[0032] If the vehicle identifier obtained by the billing terminal through decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to it, the decrypted charging power information will be sent to the charging backend terminal.

[0033] The charging backend receives the charging power information and generates a charging payment request for the user to pay.

[0034] The charging backend monitors the charging payment status and starts charging after the charging payment request is completed.

[0035] In one embodiment of the present invention, the communication method between the vehicle charging terminal, the billing terminal and the charging back-end terminal is at least one of power line communication, WIFI communication, cellular network communication and Bluetooth communication.

[0036] The present invention also provides a vehicle charging billing system, the charging billing system comprising a vehicle-mounted charging terminal, a charging back-end terminal, and a billing terminal that are communicatively connected to each other;

[0037] The vehicle-mounted charging terminal includes a charging billing request module, and the billing terminal includes a decryption processing module, a judgment module, and a reminder module.

[0038] The charging billing request module is used to send a charging billing request to the billing terminal bound to it. The charging billing request is generated by encrypting the user's account number information and vehicle identifier according to a preset public key.

[0039] The decryption processing module is used to receive the charging billing request and decrypt the charging billing request using a private key to obtain the vehicle identifier and account number information.

[0040] The judgment module is used to determine whether the vehicle identifier obtained by decryption is consistent with the vehicle identifier bound to the vehicle charging terminal.

[0041] The reminder module is used to remind the charging backend to perform charging billing according to the account number information when the vehicle identifier obtained by decryption is consistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal.

[0042] The reminder module is also used to remind the charging backend to charge according to the public method when the vehicle identifier obtained by decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal.

[0043] As described above, this invention provides a charging billing method and system for vehicles. The system sends a charging billing request, generated by encrypting the user's account number and vehicle identifier using a preset public key, to a billing terminal bound to it. The billing terminal decrypts the charging billing request using a private key to obtain the vehicle identifier and account number information. It then determines whether the decrypted vehicle identifier matches the vehicle identifier of the vehicle-to-charger bound to it, enabling data authentication of the vehicle-to-charger and thus improving charging billing security. Furthermore, only when the decrypted vehicle identifier matches the vehicle identifier of the vehicle-to-charger bound to the billing terminal can the charging backend perform charging billing according to the account number information. This allows for differentiation between vehicle-to-charger users and residents, reducing vehicle charging costs for residents while ensuring charging billing security, and making vehicle charging management and maintenance more convenient for residents. Attached Figure Description

[0044] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a schematic flowchart of an embodiment of a vehicle charging billing method according to the present invention;

[0046] Figure 2 This is a schematic flowchart illustrating another embodiment of a vehicle charging billing method according to the present invention;

[0047] Figure 3 This is a flowchart illustrating a third embodiment of a vehicle charging billing method according to the present invention;

[0048] Figure 4 This is a schematic diagram of a vehicle charging billing system according to the present invention. Detailed Implementation

[0049] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0050] Please see Figures 1 to 4 This invention provides a charging billing method for vehicles, which can be used to charge new energy vehicles in a residential community. When the user of the new energy vehicle to be charged is a community resident, the charging billing can be carried out according to the household registration information, thereby reducing the vehicle charging cost for community residents and making it more convenient for community residents to manage and maintain vehicle charging.

[0051] Please see Figure 1 The present invention provides a flowchart of a vehicle charging billing method. In one embodiment of the present invention, the vehicle charging billing method may include steps S10 to S32, which are described in detail below.

[0052] Step S10: The vehicle charging terminal sends a charging billing request to the billing terminal bound to it. The charging billing request is generated by encrypting the user's account number information and vehicle identifier based on a preset public key.

[0053] Step S20: The billing terminal receives the charging billing request and decrypts the charging billing request using the private key to obtain the vehicle identifier and account number information.

[0054] Step S30: The billing terminal determines whether the vehicle identifier obtained through decryption is consistent with the vehicle identifier of its own bound vehicle charging terminal.

[0055] If the vehicle identifier obtained through decryption matches the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend will be notified to perform charging billing according to the account number information.

[0056] If the vehicle identifier obtained through decryption does not match the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend will be reminded to charge according to the public method.

[0057] Please see Figure 1 In one embodiment of the present invention, when performing step S10, it should first be noted that the vehicle charging terminal and the billing terminal are bound according to the following steps, which are described in detail below.

[0058] Step S11: The billing terminal obtains the key generation request, generates a public key and a corresponding private key according to the key generation request, and sends the public key to the vehicle charging terminal.

[0059] Step S12: The vehicle charging terminal receives the public key and sends a vehicle binding request to the billing terminal. The vehicle binding request includes the user's account number information and vehicle identifier.

[0060] Step S13: The billing terminal receives the vehicle-to-vehicle (V2V) binding request and binds the V2V charging terminal to the billing terminal according to the vehicle identifier in the V2V binding request.

[0061] Please see Figure 1 In one embodiment of the present invention, when step S11 is executed, the billing terminal can specifically be a billing chip. The billing chip is the part of the charging device responsible for metering electrical energy and processing payment information. It is mainly responsible for accurately measuring the amount of electricity transmitted to the electric vehicle through the charging backend, processing charging data including charging time, rate calculation, etc., and interacting with the user's payment system to ensure the accuracy and security of payment information.

[0062] The power measurement chip within the billing chip can be Analog Devices' ADE7753 or ADE7858A to provide high-precision power measurement. For communication and data processing, the billing chip can use microcontrollers from STMicroelectronics or NXP.

[0063] Furthermore, a key generation request can be obtained by pressing the reset button on the billing terminal, or it can be obtained through wireless communication between the vehicle charging terminal and the billing terminal. For example, the vehicle charging terminal and the billing terminal can achieve wireless communication through at least one of Bluetooth, Wi-Fi, Near Field Communication (NFC), and cellular networks.

[0064] The billing terminal can randomly generate a public key and a corresponding private key based on a key generation request. The public key is a publicly distributed key used in encrypted communication to encrypt data, converting plaintext into ciphertext. Because the public key is public, anyone can use it to encrypt information and send it to the holder of the private key to ensure the security of data transmission. The private key is confidential and can only be accessed by the holder of the public key; it can be used to decrypt data encrypted with the public key.

[0065] For example, in one embodiment of the present invention, after the billing terminal randomly generates a public key and a corresponding private key according to the key generation request, it can send the public key to the vehicle charging terminal and store the private key so as to facilitate the decryption of data encrypted by the public key in the future.

[0066] Please see Figure 1 In one embodiment of the present invention, when steps S12 to S13 are executed, specifically, the vehicle-mounted charging terminal can be a vehicle-mounted system including a chip, mainly responsible for managing the current and voltage from the charging backend to ensure compatibility with the vehicle's charging system. The vehicle-mounted charging terminal is also used to communicate with the charging backend to synchronize the charging status and control the charging process.

[0067] Furthermore, the vehicle charging terminal and the billing terminal can communicate via at least one of Powerline Communication (PLC), Wi-Fi, cellular network communication, and Bluetooth. For example, the billing terminal can send its public key to the vehicle charging terminal via PLC.

[0068] The vehicle-to-charger sending a vehicle-to-charger binding request to the billing terminal means that the vehicle-to-charger sends the user's household registration number and vehicle identifier to the billing terminal via PLC communication. The household registration number can consist of the user's specific building, unit number, floor, and apartment number. For example, if a user lives in the third apartment on the 20th floor of building 12, unit 1, their household registration number could be 12012003. However, this is not limited to this; the household registration number can also be composed of other information, meaning the specific format of the household registration number is not restricted. The vehicle identifier (ID) is the corresponding identifier for each vehicle-to-charger; each vehicle-to-charger has a unique vehicle identifier.

[0069] Furthermore, the vehicle-to-everything (V2X) binding request can be a binding request instruction that includes a hash value. This hash value is generated by processing the user's account number and vehicle identifier using a hash function, thus achieving initial encryption of the V2X binding request and enhancing the data interaction security between the vehicle-to-everything charging terminal and the billing terminal. However, it is not limited to this; the V2X binding request can also be a binding request instruction that includes an encrypted value generated by other data encryption functions.

[0070] A hash function is a function that processes an input of arbitrary length using a mathematical algorithm and transforms it into a fixed-length output. When the vehicle's charging terminal receives user information and vehicle identifier, and uses a hash function to generate a hash value, because the hash value is an irreversible data representation, even if the hash value is leaked, the original data content cannot be directly known, thus protecting the sensitive information of the user and the vehicle. Common hash functions include, but are not limited to, SHA-256 and MD5.

[0071] It is worth further explaining that when the billing terminal receives a vehicle-to-vehicle (V2V) binding request, it can bind the V2V charging terminal to the billing terminal based on the vehicle identifier in the hash value of the V2V binding request. This enables the binding authentication of the V2V charging terminal and the billing terminal, thereby achieving initial screening of the V2V charging terminal. It also facilitates subsequent data interaction between the successfully bound V2V charging terminal and the billing terminal, improving the security and convenience of data interaction.

[0072] The billing terminal can bind the vehicle-to-vehicle charging terminal to the vehicle identifier based on the hash value to verify the legitimacy of the charging terminal. By binding the billing terminal to the charging terminal using the hash value, the billing terminal can confirm the identity of the charging terminal and ensure that it is an authorized device.

[0073] When the billing terminal fails to bind with the vehicle charging terminal, that is, when the vehicle identifier in the hash value of the billing terminal and the vehicle charging terminal does not match, the vehicle charging terminal needs to regenerate the vehicle binding request, and the billing terminal needs to rebind the vehicle charging terminal according to the vehicle identifier in the hash value of the regenerated vehicle binding request, until the billing terminal and the vehicle charging terminal are successfully bound.

[0074] Please see Figure 1 In one embodiment of the present invention, when step S10 is executed, specifically, the step of generating the charging billing request by encrypting the user's account number information and vehicle identifier according to the preset public key includes step S14, which is described in detail below.

[0075] Step S14: The vehicle charging terminal encrypts the user's account number information, vehicle identifier and preset public key according to the preset encryption algorithm to generate a charging billing request. The encryption algorithm includes RSA encryption algorithm or ECC encryption algorithm.

[0076] Please see Figure 1In one embodiment of the present invention, when executing step S14, specifically, provided that the vehicle charging terminal and the billing terminal are successfully bound, the vehicle charging terminal can encrypt the user number information and vehicle identifier according to a preset encryption algorithm based on the public key, and generate a charging billing request. The encryption algorithm may include, but is not limited to, RSA encryption algorithm or ECC encryption algorithm. RSA encryption algorithm is an asymmetric encryption algorithm widely used for secure data transmission and digital signatures. ECC encryption algorithm is an asymmetric encryption algorithm based on elliptic curve mathematics; compared to RSA, it provides the same level of security with a smaller key length, and is therefore more efficient.

[0077] Please see Figure 1 In one embodiment of the present invention, when step S20 is performed, step S20 may specifically include steps S21 to S22, as detailed below.

[0078] Step S21: The billing terminal receives the charging billing request.

[0079] Step S22: The billing terminal decrypts the charging billing request according to a preset decryption algorithm and private key to obtain the vehicle identifier and account number information. The decryption algorithm corresponds to the encryption algorithm and includes either RSA or ECC decryption algorithms.

[0080] Please see Figure 1 and Figure 4 In one embodiment of the present invention, when executing steps S21 and S22, specifically, the billing terminal can decrypt the charging billing request according to a preset decryption algorithm and private key to obtain the decrypted vehicle identifier and account number information, ensuring that the charging billing request transmitted in an insecure network cannot be read by unauthorized third parties. Decryption is a crucial step in encrypted communication, involving the conversion of the encrypted hash value back to its original form. Decryption ensures that only individuals holding the correct key can view the original data content. The decryption algorithm needs to correspond to the encryption algorithm, and when the encryption algorithm is RSA or ECC, the decryption algorithm can also be RSA or ECC.

[0081] It should be noted that when the account number and vehicle identifier in the charging billing request are represented as hash values, the vehicle identifier and account number obtained after decryption will also appear as hash values. However, this is not the only possibility; the account number and vehicle identifier in the charging billing request can also be directly encrypted using the public key, and the corresponding vehicle identifier and account number obtained after decryption using the private key will then be obtained.

[0082] Please see Figure 1In one embodiment of the present invention, when step S30 is executed, specifically, after the billing terminal decrypts the charging billing request using its private key and obtains the vehicle identifier and account number information, it can determine whether the vehicle identifier obtained through decryption is consistent with the vehicle identifier of its own bound vehicle charging terminal: if the vehicle identifier obtained through decryption is consistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend is reminded to perform charging billing according to the account number information. If the vehicle identifier obtained through decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend is reminded to perform charging billing according to the public method.

[0083] It's worth noting that if the vehicle identifier obtained through decryption matches the vehicle identifier of the charging terminal bound to the billing terminal, it indicates that the charging billing request has not been tampered with during transmission. This result can be fed back to the charging backend. When the charging backend receives this feedback, it can perform charging billing according to the household number information. Specifically, the charging backend can perform charging billing according to the household number information by connecting the charging backend to the electricity meter corresponding to the household number information. This allows the electricity meter with the household number information to perform charging billing for the charging terminal, thereby reducing charging billing costs and providing convenient vehicle charging for residents.

[0084] If the vehicle identifier obtained through decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal, it indicates that the data in the charging billing request may have been tampered with during the process from the vehicle charging terminal to the billing terminal, or that the charging user is not a resident of the community. This judgment result can be fed back to the charging backend. After receiving the feedback result, the charging backend can perform charging billing in a public manner to distinguish whether the charging user is a resident of the community, while providing certain charging convenience for non-residents.

[0085] In one embodiment of the present invention, since the user number information and vehicle identifier are unique, the hash value generated based on the user number information and vehicle identifier is also unique. When the user number information and vehicle identifier are encrypted in the form of a hash value to generate a charging billing request, the billing terminal decrypts the charging billing request and generates the corresponding hash value. Therefore, the billing terminal can determine whether the vehicle identifier obtained after decryption is consistent with the vehicle identifier of its own bound vehicle charging terminal by checking whether the hash value obtained after decryption is consistent with the hash value of its own bound vehicle charging terminal, so as to verify whether the hash value has been tampered with during transmission.

[0086] Furthermore, the fact that the vehicle identifier obtained through decryption is consistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal can mean that the hash value obtained through decryption is consistent with the hash value of the vehicle charging terminal bound to it. When the hash value obtained through decryption is consistent with the hash value of the vehicle charging terminal bound to it, the billing terminal can remind the charging backend to perform charging billing according to the user number information.

[0087] Similarly, the discrepancy between the vehicle identifier obtained through decryption and the vehicle identifier of the vehicle charging terminal bound to the billing terminal can mean that the hash value obtained through decryption is inconsistent with the hash value of the vehicle charging terminal it is bound to. When the hash value obtained through decryption is inconsistent with the hash value of the vehicle charging terminal it is bound to, the billing terminal can remind the charging backend to perform charging billing in a public manner.

[0088] The charging backend system can bill charging in a public manner, using generated QR code information or other wireless payment methods. Specifically, when the charging backend generates a QR code, users can scan it to pay for charging.

[0089] It should be noted that in the above-mentioned communication between the vehicle charging terminal, billing terminal and charging back-end terminal, the communication method between the vehicle charging terminal, billing terminal and charging back-end terminal can be at least one of power line communication, WIFI communication, cellular network communication and Bluetooth communication.

[0090] Please see Figure 1 In one embodiment of the present invention, when the vehicle identifier obtained by decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend is reminded to perform the charging billing step in a common manner. Specifically, this step may include steps S31 to S33, which are described in detail below.

[0091] Step S31: If the vehicle identifier obtained by the billing terminal through decryption is inconsistent with the vehicle identifier of the vehicle charging terminal bound to it, the decrypted charging power information is sent to the charging backend terminal.

[0092] Step S32: The charging backend receives the charging power information and generates a charging payment request for the user to pay.

[0093] Step S33: The charging backend monitors the charging payment status and starts charging after the charging payment request is completed.

[0094] Please see Figure 1In one embodiment of the present invention, when executing steps S31 to S33, it should first be noted that the charging billing request also includes charging power information. Therefore, when the vehicle identifier obtained by the billing terminal through decryption is inconsistent with the vehicle identifier of its bound vehicle charging terminal, the billing terminal needs to send the decrypted charging power information to the charging backend. When the charging backend receives the charging power information, it can generate a charging payment request based on the charging power information for the user to pay. This charging payment request can be a QR code payment request or other wireless payment requests. Furthermore, to ensure real-time charging, the charging backend also needs to monitor the charging payment status in real time and charge the vehicle after the charging payment request is completed.

[0095] Please see Figure 1 and Figure 2 In another embodiment of the present invention, before the step of the vehicle charging terminal sending a charging billing request to the billing terminal bound to it, the following steps are included, which are described in detail below.

[0096] Step S110: The vehicle charging terminal sends a charging request to the charging backend terminal, wherein the charging request is generated based on the user's account number information.

[0097] Step S120: The charging backend receives the charging request and determines whether the user number information in the charging request is in the preset user number information database.

[0098] If so, the charging backend will calculate the charging fee based on the account number information.

[0099] If not, the charging backend will charge the device using the public charging method.

[0100] Please see Figure 1 and Figure 2 In another embodiment of the present invention, when performing step S110, specifically, assuming the vehicle charging terminal and the billing terminal have been successfully bound, the socket of the vehicle charging terminal can be directly inserted into the charging backend terminal to send a charging request to the charging backend terminal. The charging request is generated based on the user's account number information. Unlike the aforementioned charging terminal sending a charging billing request to the billing terminal, this charging request can be directly generated based on the user's account number information.

[0101] Please see Figure 1 and Figure 2 In another embodiment of the present invention, when step S120 is executed, specifically, when the charging backend determines that it has received a charging request, it can determine whether the user number information in the charging request is in a preset user number information database. If it is, the charging backend performs charging billing according to the user number information. If it is not, the charging backend performs charging billing according to the public method.

[0102] Furthermore, determining whether the household number information in the charging request is in the preset household number information database means that the charging backend polls the charging request sent by the vehicle-mounted charging terminal based on the household number information. If the household number information exists in the preset household number information database, it means that the user of the vehicle-mounted charging terminal corresponding to the household number information is a resident of the community. In this case, the charging backend can directly charge the vehicle according to the household number information, which can achieve both fast charging and distinguish whether the vehicle-mounted charging terminal is a resident of the community. If the household number information does not exist in the preset household number information database, it means that the user of the vehicle-mounted charging terminal corresponding to the household number information is not a resident of the community. Although charging services need to be provided to this user, charging can only be charged according to the public charging method. The specific form of charging backend charging according to household number information or public charging method can be referred to in step S30 above, so it will not be repeated here.

[0103] Please see Figure 1 and Figure 3 In the third embodiment of the present invention, before the step of the vehicle charging terminal sending a charging billing request to the billing terminal bound to it, the following steps are also included, which are described in detail below.

[0104] Step S210: The vehicle charging terminal sends a charging request to the charging backend terminal, wherein the charging request is generated based on the user's account number information.

[0105] Step S220: The charging backend receives the charging request and determines whether the user number information in the charging request is in the preset user number information database.

[0106] If not, the charging backend will charge the device using the public charging method.

[0107] If present, the vehicle's charging terminal will be prompted to send a charging billing request to the billing terminal it is bound to.

[0108] Step S230: The billing terminal receives the charging billing request and decrypts the charging billing request using the private key to obtain the vehicle identifier and account number information.

[0109] Step S240: The billing terminal determines whether the vehicle identifier obtained through decryption is consistent with the vehicle identifier of its own bound vehicle charging terminal.

[0110] If the vehicle identifier obtained through decryption matches the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend will be notified to perform charging billing according to the account number information.

[0111] If the vehicle identifier obtained through decryption does not match the vehicle identifier of the vehicle charging terminal bound to the billing terminal, the charging backend will be reminded to charge according to the public method.

[0112] Please see Figure 1 and Figure 3 In the third embodiment of the present invention, when steps S210 to S220 are executed, specifically, the vehicle-mounted charging terminal sends a charging request to the charging backend, which will not be repeated here. It is worth noting that when the charging backend determines that it has received a charging request, it can determine whether the household number information in the charging request is in a preset household number information database. If the preset household number information exists in the preset household number information database, it means that the user of the vehicle-mounted charging terminal corresponding to the household number information belongs to a resident of the community, and the charging backend needs to remind the vehicle-mounted charging terminal to send a charging billing request to the billing terminal bound to it.

[0113] Furthermore, the billing terminal can receive charging billing requests and decrypt them using a private key to obtain the vehicle identifier and account number information. The billing terminal also needs to determine if the decrypted vehicle identifier matches the vehicle identifier of its bound vehicle-mounted charging terminal. If the decrypted vehicle identifier matches, the billing backend is notified to bill charging according to the account number information. If the decrypted vehicle identifier does not match, the billing backend is notified to bill charging according to the public charging method.

[0114] It is worth noting that in step S220, when the preset household number information exists in the database, the charging backend needs to remind the vehicle-mounted charging terminal to send a charging billing request to the billing terminal bound to it. The difference from step S120 is that it needs to further send the charging billing request to the billing terminal, decrypt the request, and determine whether the vehicle identifier obtained after decryption matches the vehicle identifier of the vehicle-mounted charging terminal bound to it. Only when the vehicle identifier obtained after decryption matches the vehicle identifier of the vehicle-mounted charging terminal bound to the billing terminal is the charging backend reminded to perform charging billing according to the household number information. Thus, step S220 improves the security of data interaction between the vehicle-mounted charging terminal and the billing terminal, thereby improving the data security of residents during charging, enhancing their user experience, and increasing charging satisfaction. The specific form of charging billing by the charging backend according to household number information or public charging methods can be referred to in step S30 above, and will not be repeated here.

[0115] In the first embodiment of the present invention, the billing terminal can first be reset by performing a key generation request to generate the corresponding public and private keys. After generating the public key, the billing terminal can send it to the vehicle charging terminal via power line communication (PLC). The vehicle charging terminal receives the public key and sends a vehicle binding request to the billing terminal. The vehicle binding request includes a hash value generated by hashing the user's account number information and vehicle identifier using a hash function. The billing terminal receives the vehicle binding request and binds the vehicle charging terminal to the billing terminal based on the vehicle identifier in the request. If the binding between the billing terminal and the vehicle charging terminal fails, the vehicle charging terminal needs to regenerate the vehicle binding request according to the above steps, and the billing terminal re-binds the vehicle charging terminal based on the binding request until the binding is successful. If the binding between the billing terminal and the vehicle charging terminal is successful, the vehicle charging terminal sends a charging billing request to the bound billing terminal. The charging billing request is generated by encrypting the hash value using a preset public key. After receiving a charging billing request, the billing terminal can decrypt the request using its private key to obtain a hash value containing the vehicle identifier and household number information. The billing terminal also needs to determine if the hash value containing the vehicle identifier matches the hash value containing the vehicle identifier of its own bound vehicle-mounted charging terminal. If the hash value matches, the billing backend is notified to bill the charging according to the household number information. If the hash value does not match, the billing backend is notified to bill the charging according to the public method. This is to authenticate whether the charging user is a resident of the community, thereby differentiating the charging user group, reducing the charging cost for community residents, and improving data security for community residents charging.

[0116] As can be seen, in the above solution, the charging terminal sends a charging request generated based on the user's household number information to the charging backend. The charging backend determines the specific charging billing method by judging whether the household number information in the charging request is in the preset household number information database. This can not only achieve fast charging, but also distinguish whether the charging user is a resident of the community, thereby reducing the vehicle charging cost for community residents and improving their living experience.

[0117] Furthermore, the charging terminal sends a charging billing request to the billing terminal bound to it, which is generated by encrypting the user's account number information and vehicle identifier using a preset public key. The billing terminal decrypts the charging billing request using a private key to obtain the vehicle identifier and account number information, and determines whether the decrypted vehicle identifier is consistent with the vehicle identifier of its own bound charging terminal. This can improve the data interaction security between the charging terminal and the billing terminal, thereby improving the charging billing security for community residents. By determining the specific charging billing method on the charging backend based on the judgment result, the charging cost for community residents can be reduced, the charging convenience for community residents can be improved, and the living experience of community residents can be enhanced.

[0118] Please see Figure 4 , Figure 4 This is a schematic diagram of a vehicle charging billing system provided by the present invention. This charging billing system can be applied to vehicle charging billing methods to differentiate charging vehicles and reduce vehicle charging costs for residents while ensuring data security. The processing flow of this charging billing system corresponds to that of the charging billing system described above. The charging billing system may include a vehicle-mounted charging terminal 10, a billing terminal 20, and a charging backend terminal 30, all of which are communicatively connected. The billing terminal 20 and the charging backend terminal 30 can be located within a single charging pile. The vehicle-mounted charging terminal 10 may include a billing request module 110. The billing terminal 20 may include a decryption processing module 210, a judgment module 220, and a reminder module 230. Detailed descriptions of each functional module are as follows.

[0119] In one embodiment of the present invention, the charging billing request module 110 can be used to send a charging billing request to the billing terminal 20 bound to it, wherein the charging billing request is generated by encrypting the user's account number information and vehicle identifier according to a preset public key.

[0120] In one embodiment of the present invention, the decryption processing module 210 can be used to receive a charging billing request and decrypt the charging billing request using a private key to obtain the vehicle identifier and account number information.

[0121] In one embodiment of the present invention, the judgment module 220 can be used to determine whether the vehicle identifier obtained by decryption is consistent with the vehicle identifier of its own bound vehicle charging terminal 10.

[0122] In one embodiment of the present invention, the reminder module 230 can be used to remind the charging backend 30 to perform charging billing according to the user number information when the vehicle identifier obtained after decryption matches the vehicle identifier of the vehicle charging terminal 10 bound to the billing terminal 20. The reminder module 230 is also used to remind the charging backend 30 to perform charging billing according to the common method when the vehicle identifier obtained after decryption does not match the vehicle identifier of the vehicle charging terminal 10 bound to the billing terminal 20.

[0123] In the description of this specification, the references to terms such as "this embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0124] The embodiments of the present invention disclosed above are merely illustrative of the invention. The embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A charging billing method of a vehicle, characterized by, The application relates to a charging and charging method applied to a charging and charging system comprising a vehicle machine charging terminal, a charging terminal and a charging background terminal which are connected in communication with each other. The vehicle machine charging terminal sends a charging request to the charging background terminal, wherein the charging request is generated according to user's household number information; The charging background terminal receives the charging request and judges whether the household number information in the charging request is in a preset household number information library: if yes, the charging background terminal prompts the vehicle machine charging terminal to send the charging and charging request to the charging terminal bound therewith; if not, the charging background terminal carries out charging and charging in a public mode; The vehicle machine charging terminal sends a charging and charging request to the charging terminal bound therewith, wherein the charging and charging request is generated by encrypting user's household number information and vehicle identifier according to a preset public key; The charging terminal receives the charging and charging request and carries out decryption processing on the charging and charging request through a private key to obtain vehicle identifier and household number information; The charging terminal judges whether the vehicle identifier obtained by decryption and the vehicle identifier of the vehicle machine charging terminal bound with the charging terminal are consistent: If the vehicle identifier obtained by decryption and the vehicle identifier of the vehicle machine charging terminal bound with the charging terminal are consistent, the charging background terminal is prompted to carry out charging and charging according to the household number information; If the vehicle identifier obtained by decryption and the vehicle identifier of the vehicle machine charging terminal bound with the charging terminal are inconsistent, the charging background terminal is prompted to carry out charging and charging in a public mode.

2. The charging billing method for a vehicle according to claim 1, characterized by, Before the step of sending the charging and charging request to the charging terminal bound therewith by the vehicle machine charging terminal, the application further comprises: The vehicle machine charging terminal sends a charging request to the charging background terminal, wherein the charging request is generated according to user's household number information; The charging background terminal receives the charging request and judges whether the household number information in the charging request is in a preset household number information library: If yes, the charging background terminal carries out charging and charging according to the household number information; If not, the charging background terminal carries out charging and charging in a public mode.

3. The charging billing method for a vehicle according to claim 1, characterized by, The vehicle machine charging terminal and the charging terminal are bound according to the following steps: The charging terminal obtains a key generation request and generates a public key and a corresponding private key according to the key generation request, and sends the public key to the vehicle machine charging terminal; The vehicle machine charging terminal receives the public key and sends a vehicle machine binding request to the charging terminal, wherein the vehicle machine binding request comprises user's household number information and vehicle identifier; The charging terminal receives the vehicle machine binding request and binds the vehicle machine charging terminal and the charging terminal according to the vehicle identifier in the vehicle machine binding request.

4. The charging billing method for a vehicle according to claim 1, characterized by, The step of generating the charging and charging request by encrypting user's household number information and vehicle identifier according to a preset public key comprises: The vehicle machine charging terminal carries out encryption processing on user's household number information, vehicle identifier and a preset public key according to a preset encryption algorithm to generate a charging and charging request, wherein the encryption algorithm comprises an RSA encryption algorithm or an ECC encryption algorithm.

5. The charging billing method for a vehicle according to claim 4, wherein The preset public key is randomly generated by the charging terminal according to a key generation request.

6. The charging billing method for a vehicle according to claim 4, wherein The charging end receives the charging billing request, and the step of obtaining the vehicle identifier and the account information by decrypting the charging billing request through a private key comprises: The charging end receives the charging billing request; The charging end decrypts the charging billing request through a preset decryption algorithm and a private key to obtain the vehicle identifier and the account information; the decryption algorithm corresponds to the encryption algorithm, and comprises an RSA decryption algorithm or an ECC decryption algorithm.

7. The charging billing method for a vehicle according to claim 1, wherein The charging billing request further comprises charging power information; if the vehicle identifier obtained by decryption is inconsistent with the vehicle identifier of the car machine charging end bound by the charging end, the step of prompting the charging background end to perform charging billing in a public manner comprises: If the vehicle identifier obtained by decryption of the charging end is inconsistent with the vehicle identifier of the car machine charging end bound by the charging end, the charging power information obtained by decryption is sent to the charging background end; The charging background end receives the charging power information and generates a charging payment request for user payment; The charging background end monitors the charging payment situation and performs charging after the charging payment request is paid.

8. The charging billing method of a vehicle according to claim 1, characterized by, The communication mode between the car machine charging end, the charging end and the charging background end is at least one of power line communication, WIFI communication, cellular network communication and Bluetooth communication.

9. A charging billing system of a vehicle characterized by, The charging billing method of the vehicle according to any one of claims 1 to 8 is applied to the charging billing system comprising a car machine charging end, a charging background end and a charging end in communication connection with each other; The car machine charging end comprises a charging billing request module, and the charging end comprises a decryption processing module, a judgment module and a prompting module; The charging billing request module is used to send a charging billing request to the charging end bound thereto, wherein the charging billing request is generated by encrypting the account information and the vehicle identifier of the user according to a preset public key; The decryption processing module is used to receive the charging billing request and decrypt the charging billing request through a private key to obtain the vehicle identifier and the account information; The judgment module is used to judge whether the vehicle identifier obtained by decryption is consistent with the vehicle identifier of the car machine charging end bound by the charging end; The prompting module is used to prompt the charging background end to perform charging billing according to the account information when the vehicle identifier obtained by decryption is consistent with the vehicle identifier of the car machine charging end bound by the charging end; The prompting module is also used to prompt the charging background end to perform charging billing in a public manner when the vehicle identifier obtained by decryption is inconsistent with the vehicle identifier of the car machine charging end bound by the charging end.

Images