A private pile sharing and multi-user reservation charging method of a vehicle-mounted charging pile

Abstract

The application discloses a kind of private pile sharing and multi-user reservation charging method of vehicle-mounted charging pile, vehicle-mounted charging pile system includes: mobile phone end, including processor and the storage module electrically connected with processor, mobile phone bluetooth module;Charging pile, including MCU controller and the charging pile bluetooth module electrically connected with MCU controller, 4G module;And server-based cloud service platform;Wherein, the mobile phone end and charging pile pass through bluetooth communication, the mobile phone end, charging pile and cloud service platform pass through 4G or WIFI communication.The multi-user reservation charging method includes user information registration step, charging pile main user registration step, charging pile information sharing step and multi-user reservation charging step.Through the above-mentioned method of the application, the pile main sharing charging pile, multi-user reservation charging, multi-user data management are realized, solve multiple users share a set of charging pile equipment, provide technical means for effectively and fully utilizing charging pile equipment.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of automotive electronics, in particular to a private pile sharing and multi-user reservation charging method for a vehicle-mounted charging pile. BACKGROUND

[0002] With the rapid popularization of new energy electric vehicles, electric vehicles have become mainstream consumer goods for ordinary people, but due to insufficient planning in the early stage, the development of charging supporting facilities cannot keep up, especially in third and fourth-tier cities and rural areas, which makes it very difficult to charge electric vehicles.

[0003] Since an electric vehicle can run about 600 kilometers after being charged once, it will only be charged once a week under normal circumstances, and each charging takes about 6 hours. If each electric vehicle is equipped with a set of charging pile (for home use), it is also a waste. It can be imagined that multiple users share a set of charging pile, which effectively makes full use of the charging pile equipment.

[0004] However, when multiple users share a set of charging pile equipment, the pile owner can share his charging pile with other users in need, and each user can make an advance reservation after knowing the current state of the charging pile. However, the pile owner sharing the charging pile, multi-user reservation charging, multi-user data management, and charging energy metering and charging are the latest technical issues in the current electric vehicle charging pile industry. SUMMARY

[0005] The present application provides a private pile sharing and multi-user reservation charging method for a vehicle-mounted charging pile to solve the problems of the prior art in the background art.

[0006] The present application provides a private pile sharing and multi-user reservation charging method for a vehicle-mounted charging pile, which includes a user information registration step, a charging pile owner user registration step, a charging pile information sharing step, and a multi-user reservation charging step. After completing the user information registration step and the charging pile owner user registration step:

[0007] The pile owner and the ordinary user make a reservation for the charging pile. If the charging pile is online, it can be reserved remotely through the server for the specified charging pile. If the charging pile is not online, the user needs to be near the charging pile, and the reservation is made using Bluetooth communication under the condition of Bluetooth connection.

[0008] The pile owner and the ordinary user make a remote authorization for the charging pile. If the charging pile is online, it can be authorized remotely through the server.

[0009] Further, the charging pile information sharing step is specifically:

[0010] (c1) when the charging pile is started, first read the white list data stored locally, read the user added serial number m, and enter step (c2);

[0011] (c2) the charging pile owner inputs the mobile phone number of the user to be shared and sets the sharing time period on the charging pile sharing page of the mobile phone APP, and submits to the server for sharing application; after the server receives the sharing information of the charging pile owner, a normal user account is created in the SN number corresponding database, the server calls a random function to generate a random number, and converts it into a decimal string, and the last 6 characters of the string are reserved as an activation code, the server stores the activation code in the SN number corresponding normal user database, and at the same time, the activation code of the normal user is sent to the mobile phone APP of the charging pile owner, and enters step (c3);

[0012] (c3) the charging pile owner sends the SN number and the activation code of the normal user to the shared user through the mobile phone APP, the shared user downloads and installs the specified mobile phone APP installation software at the specified path, and registers the user information of the server, the account is uniformly the mobile phone number, the mobile phone number is registered and the password is set, and then the SN number is input to the charging pile for normal user binding, after the server receives the normal user binding request, the activation code is requested to be input; if the activation code input by the normal user is consistent with the activation code in the SN number corresponding user database, the server agrees to bind the charging pile to the corresponding APP account, and enters step (c4), otherwise, enter step (c7);

[0013] (c4) the normal user mobile phone APP requests the server to send the authorization code information, the server receives the request, reads the normal authorization code stored in the SN number corresponding database, and uses the formula: user authorization code = normal authorization code + (7*n+1)*n+A, wherein n is the serial number of the normal user, the server increases the serial number n by 1 for each normal user, the serial number n of the first user is 1, wherein n takes the value range of 【1, 10000】, and A is a calibration constant; the server uses a specified secret key and algorithm to encrypt the user authorization code and the sharing time period, and then sends the user authorization code information to the specified user mobile phone APP, and the user mobile phone APP receives the user authorization code information, and under the condition that the integrity check is passed, the ciphertext of the user authorization code is saved in the file system of the mobile phone APP, and then enters step (c5);

[0014] (c5) Ordinary users activate the charging station using the user authorization code information via a mobile APP. If the charging station is online, mobile communication can be remotely established through the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and communicate with it via Bluetooth when connected. The mobile APP sends the user authorization code information to the charging station. Upon receiving the user authorization code information and verifying its integrity, the charging station uses a specified key and algorithm to decrypt the encrypted user authorization code and the encrypted sharing time period to obtain user authorization code 1 and the sharing time period data. The charging station then substitutes the locally stored ordinary authorization code into the formula to calculate user authorization code 2: User authorization code 2 = ordinary authorization code + (7*n+1)*n + A, where n ranges from 1 to 10000 and A is a calibration constant. If any calculated user authorization code 2 from n to 10000 is equal to user authorization code 1, the user authorization code activation is successful, and the process proceeds to step (c6). If none of the two are equal, the super authorization code is invalid, and the process proceeds to step (c7).

[0015] (c6) The charging pile then copies the user authorization code 1 and the information of the sharing time period data to the user authorization code, start time and end time address corresponding to the ordinary user information array in the authorization whitelist. The array number is the user addition number m. Then add 1 to the user addition number m. If m is greater than or equal to the maximum number of ordinary users, then m is equal to 0. Then store the user addition number m locally and store the updated authorization whitelist data locally. Proceed to step (c7).

[0016] (c7) End;

[0017] The user authorization code information includes user authorization code instructions, encrypted user authorization code, encrypted sharing time period data, and frame verification data.

[0018] Furthermore, the user information registration step includes:

[0019] (a1) After the vehicle-mounted charging pile is assembled on the production line, it needs to be powered on and connected to the server. After the connection is successful, the charging pile sends a request for SN number registration information. After receiving the request for SN number registration information, the server checks whether the SN number has been registered if the integrity verification is passed. If it has been registered, the server replies with a registration failure message to the charging pile and proceeds to step (a8). If it has not been registered, the server responds to the registration, establishes the database corresponding to the SN, and replies with a registration success message to the charging pile and proceeds to step (a2).

[0020] (a2) The server generates the corresponding key data based on the SN number, securely stores the key data in the database corresponding to the SN number, and sends the key configuration information; after receiving the key configuration information, the charging pile securely stores it locally if the integrity verification is passed, and replies with the key configuration success message to the server, and proceeds to step (a3).

[0021] (a3) The server generates an authorization code based on the serial number data in the SN, the server system time data, and a random number generated using a random number function; the authorization code = the serial number data in the SN + the server time data + the random number, and proceeds to step (a4);

[0022] (a4) The server generates a super authorization code based on the authorization code. The super authorization code is used by the charging pile owner. The super authorization code = authorization code & 0x3FFFFFFF, ensuring that the super authorization code cannot be greater than 0x3FFFFFFF. The server securely stores the super authorization code data in the database corresponding to the SN number and encrypts it using a specified key and algorithm. Then, it sends the super authorization code information to the charging pile corresponding to the SN number. Upon receiving the super authorization code information, the corresponding charging pile decrypts the ciphertext using the specified key and algorithm to obtain the plaintext super authorization code if the integrity verification passes. The corresponding charging pile then confirms the validity range of the super authorization code. If the super authorization code is less than or equal to 0x3FFFFFFF, it is considered valid and stored securely locally. The charging pile responds to the server that it has received the super authorization code and proceeds to step (a5). Otherwise, the charging pile responds to the server that it has received the super authorization code but it has not and proceeds to step (a8).

[0023] (a5) The server generates a regular authorization code based on the authorization code. The regular authorization code is used by the charging pile owner when sharing it with other users. The regular authorization code = ((authorization code & 0x7FFFFFFF)|0x40000000), which makes the regular authorization code greater than 0x3FFFFFFF and less than 0x80000000. The server securely stores the regular authorization code data in the database corresponding to the SN number, encrypts it using a specified key and algorithm, and then sends the regular authorization code information. The charging pile corresponding to the SN number receives the regular authorization code information. If the integrity verification passes, it decrypts the ciphertext using the specified key and algorithm to obtain the plaintext of the regular authorization code. The charging pile then confirms the validity range of the regular authorization code. If the regular authorization code is greater than 0x3FFFFFF and less than 0x80000000, it is considered valid and stored securely locally. The charging pile responds to the server that it has received the regular authorization code and proceeds to step (a6). Otherwise, the charging pile responds to the server that it has received the regular authorization code invalidally and proceeds to step (a8).

[0024] (a6) The server then calls a random function to generate a random number and calculates the A calibration constant; A calibration constant = random number & 0x7FFF, making the A calibration constant less than 0x8000. The server securely stores the A calibration constant data in the database corresponding to the SN number and then sends the A calibration constant information; the charging pile corresponding to the SN number receives the A calibration constant information. If the integrity verification passes, the charging pile then confirms the valid range of the A calibration constant. If the A calibration constant is less than 0x8000, it is considered valid and securely stored locally. The charging pile then responds to the server that the A calibration constant has been received and proceeds to step (a7); otherwise, the charging pile responds to the server that the A calibration constant has been received invalidally and proceeds to step (a8).

[0025] (a7) The server then calls a random function to generate a random number and converts it into a decimal string. The last 6 characters of the string are retained as the activation code. The server securely stores the activation code in the database corresponding to the SN number and sends the activation code to the production line computer. After receiving the activation code, the production line computer makes a card and prints the activation code, SN number and corresponding QR code on the card using a card-matching tool. A scratch-off coating is applied to the activation code. The card and the corresponding charging pile are packaged together and the process proceeds to step (a8).

[0026] (a8) End;

[0027] The SN registration information includes a registration instruction, the SN number, and frame verification data; the key configuration information includes a key configuration instruction, key data, and frame verification data.

[0028] Furthermore, the main user registration steps for the charging pile are as follows:

[0029] (b1) First, the charging station owner downloads and installs the designated mobile APP according to the instructions, and registers the user information on the server. The account is uniformly a mobile phone number. The owner registers using the mobile phone number and sets a password. Then, the owner scans the QR code of the charging station, applies to bind the charging station with the SN number corresponding to the QR code, and sends the application binding information. After the server receives the application binding information from the APP, it will request the input of an activation code. The owner scratches off the coating of the activation code on the card, enters the corresponding 6-digit string, and sends it to the server to proceed to step (b2).

[0030] (b2) After receiving the activation code, the server reads the activation code stored in the database corresponding to the SN number and compares it with the received activation code. If they are the same, the server agrees to bind the charging pile to the account corresponding to the APP and creates a super user account in the database corresponding to the SN number, and proceeds to step (b3); if they are different, the binding of the charging pile fails and proceeds to step (b6).

[0031] (b3) The charging pile main mobile APP requests the server to send the super authorization code information. After receiving the request, the server reads the super authorization code stored in the super user database corresponding to the SN number, encrypts it using the specified key and algorithm, and then sends the super authorization code information to the mobile APP. After receiving the super authorization code information, the mobile APP saves the encrypted super authorization code in the mobile APP file system if the integrity verification is passed, and proceeds to step (b4).

[0032] (b4) The charging pile owner's mobile APP uses the super authorization code to activate the charging pile as a super user. If the charging pile is online, it can remotely communicate with the server. If the charging pile is offline, the charging pile owner needs to go to the vicinity of the charging pile and communicate with the charging pile via Bluetooth when connected via Bluetooth. The mobile APP sends the encrypted super authorization code and the verification value to the charging pile. After receiving the super activation information, the charging pile first checks the integrity of the frame information, calculates the verification value and compares it with the received verification value. If they are equal, it proceeds to step (b5); if they are not equal, it replies with the message that the activation verification failed and proceeds to step (b6).

[0033] (b5) The charging pile decrypts the ciphertext to obtain the super authorization code, and compares it with the super authorization code stored locally. If they are equal, the super authorization code is replied to be successfully activated. The plaintext of the super authorization code is then copied to the address corresponding to the super authorization code in the authorization whitelist, and the whitelist data is stored locally securely. If they are not equal, the super authorization code is replied to be invalid, and the process proceeds to step (b6).

[0034] (b6) End.

[0035] Furthermore, the charging station owner and ordinary users can reserve charging stations. If the charging station is online, they can remotely reserve a specific charging station through the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and make a reservation via Bluetooth communication when connected. Specifically:

[0036] (d1) First, check the status of the charging station on the mobile APP. The charging station status is mainly divided into charging status, reservation status, fault status and idle status. If the charging station status is idle, you can make a reservation and proceed to step (d2); if the charging station status is not idle, you cannot make a reservation and proceed to step (d5).

[0037] (d2) Click the "Request Reservation" button on the mobile app. The mobile app sends reservation information (including reservation instructions, encrypted authorization code, and frame verification data; if it is the charging station owner, it is the encrypted super authorization code; otherwise, it is the encrypted user authorization code). After receiving the reservation information, the charging station, if the integrity verification passes, decrypts the received encrypted authorization code to obtain the plaintext authorization code, and then compares it. If the received authorization code is a super authorization code in the whitelist, the reservation authorization code is the super authorization code, and a reservation success message is sent back to the mobile app. If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, the reservation authorization code is the corresponding user authorization code, and a reservation success message is sent back to the mobile app. Proceed to step (d3). Otherwise, a reservation failure message is sent back to the mobile app. Proceed to step (d5).

[0038] (d3) Once the charging pile is successfully reserved, the charging pile status is set to reserved status, and the status information is reported to the server; the timeout reservation timer is set to 0, and the process proceeds to step (d4).

[0039] (d4) When the charging pile is in the reservation state, the timeout reservation timer is incremented by 1 in the periodic task. It is determined whether the timeout reservation timer is greater than the reservation timeout threshold. If the timeout is met, the reservation is canceled directly, the charging pile status is set to idle status, and the status information is reported to the server; proceed to step (d5).

[0040] (d5) End.

[0041] Furthermore, charging station owners and ordinary users can remotely authorize charging at the charging stations. If the charging station is found to be online, authorization can be remotely granted through the server. Specifically:

[0042] (e1) Click the "Request Remote Authorization Charging" button on the mobile APP. The mobile APP sends remote authorization information (including remote authorization instructions, encrypted authorization code, and frame verification data; if it is the charging station owner, it is encrypted super authorization code; otherwise, it is encrypted user authorization code). After receiving the remote authorization information, the charging station decrypts the received encrypted authorization code to obtain the plaintext authorization code if the integrity verification passes. If the charging station is in an idle state, proceed to step (e2). If the charging station is in a reserved state, proceed to step (e3). If the charging station is in a fault state or charging state, directly reject the request and proceed to step (e5).

[0043] (e2) The charging station compares the received authorization code. If the received authorization code is a super authorization code in the whitelist, it directly authorizes the charging request and replies with an authorization success message to the mobile APP. If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, it directly authorizes the charging request, the current charging authorization code is the received authorization code, and replies with an authorization success message to the mobile APP; proceed to step (e4); otherwise, it replies with an authorization failure message to the mobile APP; proceed to step (e5).

[0044] (e3) The charging station compares the received authorization code. If the received authorization code is a reservation authorization code, it directly authorizes the charging request, and the current charging authorization code is the received authorization code. It then replies with authorization success information to the mobile APP and proceeds to step (e4). Otherwise, it replies with authorization failure information to the mobile APP and proceeds to step (e5).

[0045] (e4) The charging station checks whether the charging gun is plugged in. If it is plugged in, charging is started. If it is not plugged in, a timer is started. If the charging gun is not plugged in within 5 minutes, the authorization request is canceled, the charging station is set to idle state, and a timeout authorization cancellation message is sent to the corresponding mobile APP. Proceed to step (e5).

[0046] (e5) End.

[0047] Furthermore, 7. Charging station owners and users can cancel authorized charging at charging stations. If the charging station is online, the cancellation can be done remotely via the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and, with a Bluetooth connection, use Bluetooth communication to cancel the authorized charging. Specifically:

[0048] (g1) The user can click the button on the mobile app to request Bluetooth or remotely cancel authorized charging. The mobile app sends a cancellation information message. If the user is the charging station owner, the message is a super authorization code in encrypted form; otherwise, it is a user authorization code in encrypted form. After receiving the cancellation information, the charging station decrypts the encrypted authorization code to obtain the plaintext authorization code, provided the integrity verification passes. The charging station compares the received authorization code. If the received authorization code is a super authorization code, charging is canceled directly, and the reason for cancellation is set to "super user cancellation". If the received authorization code is the current charging authorization code, charging is canceled directly, and the reason for cancellation is set to "regular user cancellation". Proceed to step (g2).

[0049] (g2) End.

[0050] 11. Further, the ordinary authorization code information includes ordinary authorization code instructions, ordinary authorization code ciphertext, and frame verification data; the super authorization code information includes super authorization code instructions, super authorization code ciphertext, and frame verification data.

[0051] Furthermore, the A calibration constant is a constant in the ordinary user authorization code calculation formula, including calibration constant instructions, A calibration constant data, and frame check data.

[0052] A vehicle-mounted charging pile system employing the aforementioned private charging pile sharing and multi-user scheduled charging methods includes:

[0053] The mobile device includes a processor and a storage module electrically connected to the processor, as well as a mobile Bluetooth module;

[0054] The charging pile includes an MCU controller and a charging pile Bluetooth module and a 4G module electrically connected to the MCU controller.

[0055] Server-based cloud service platform;

[0056] The mobile phone and the charging pile communicate via Bluetooth, and the mobile phone, the charging pile and the cloud service platform communicate via 4G or WIFI.

[0057] The above-described at least one technical solution adopted in the embodiments of the present invention can achieve the following beneficial effects:

[0058] The above-described method of the present invention enables charging pile owners to share charging piles, multiple users to schedule charging, and multiple users to manage data, thus solving the problem of multiple users sharing a set of charging pile equipment and providing a technical means for effectively and fully utilizing charging pile equipment. Attached Figure Description

[0059] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:

[0060] Figure 1 This is a schematic diagram of the vehicle-mounted charging pile system according to an embodiment of the present invention. Detailed Implementation

[0061] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0062] The technical solutions provided by the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0063] To address the issue of multiple users sharing a single charging station, this invention proposes a method for private charging station sharing and multi-user scheduled charging. For example... Figure 1 As shown, the on-board charging pile system includes a main controller MCU, a Bluetooth module, and a 4G module. The main controller MCU communicates with the Bluetooth module via serial port 1 and with the 4G module via serial port 2. The mobile device needs to have a designated user app installed, allowing users to communicate directly with the charging pile via Bluetooth and also with the cloud server via mobile signal. The system also includes a mobile terminal, comprising a processor, a storage module electrically connected to the processor, a Bluetooth module, and a server-based cloud service platform. The mobile terminal and the charging pile communicate via Bluetooth, while the mobile terminal, the charging pile, and the cloud service platform communicate via 4G or Wi-Fi.

[0064] The specific steps of the method of the present invention are as follows:

[0065] (1) After the vehicle-mounted charging pile is produced and assembled on the production line, user information registration is required, which mainly includes the following steps:

[0066] (a1) After the vehicle-mounted charging pile is assembled on the production line, it needs to be powered on and connect to the server. After successful connection, the charging pile sends a request for SN registration information (including registration command, SN number, and frame verification data). After receiving the request for SN registration information, the server checks whether the SN number has already been registered if the integrity verification passes. If it has been registered, the server replies with a registration failure message to the charging pile and proceeds to step (a8). If it has not been registered, the server responds to the registration request, establishes the database corresponding to the SN, and replies with a registration success message to the charging pile. Proceed to step (a2).

[0067] (a2) The server generates corresponding key data based on the SN number, securely stores the key data in the database corresponding to the SN number, and sends key configuration information (including key configuration instructions, key data, and frame verification data). After receiving the key configuration information, the charging pile securely stores it locally if the integrity verification passes, and replies with a key configuration success message to the server. Proceed to step (a3);

[0068] (a3) The server generates an authorization code based on the serial number data in the SN (generally used for production line generation numbering), the server system time data, and a random number generated using a random number function. Authorization code = Serial number data in SN + Server time data + Random number. Proceed to step (a4);

[0069] (a4) The server generates a super authorization code based on the authorization code. The super authorization code is used by the charging pile owner. The super authorization code = authorization code & 0x3FFFFFFF, ensuring that the super authorization code cannot be greater than 0x3FFFFFFF. The server securely stores the super authorization code data in the database corresponding to the SN number and encrypts it using a specified key and algorithm. Then, it sends the super authorization code information to the charging pile corresponding to the SN number. Upon receiving the super authorization code information, the corresponding charging pile decrypts the ciphertext using the specified key and algorithm to obtain the plaintext super authorization code if the integrity verification passes. The corresponding charging pile then confirms the validity range of the super authorization code. If the super authorization code is less than or equal to 0x3FFFFFFF, it is considered valid and stored securely locally. The charging pile responds to the server that it has received the super authorization code and proceeds to step (a5). Otherwise, the charging pile responds to the server that it has received the super authorization code but it has not and proceeds to step (a8).

[0070] (a5) The server generates a regular authorization code based on the authorization code. The regular authorization code is used by the charging pile owner when sharing it with other users. The regular authorization code = ((authorization code & 0x7FFFFFFF)|0x40000000), which makes the regular authorization code greater than 0x3FFFFFFF and less than 0x80000000. The server securely stores the regular authorization code data in the database corresponding to the SN number, encrypts it using a specified key and algorithm, and then sends the regular authorization code information. The charging pile corresponding to the SN number receives the regular authorization code information. If the integrity verification passes, it decrypts the ciphertext using the specified key and algorithm to obtain the plaintext of the regular authorization code. The charging pile then confirms the validity range of the regular authorization code. If the regular authorization code is greater than 0x3FFFFFF and less than 0x80000000, it is considered valid and stored securely locally. The charging pile responds to the server that it has received the regular authorization code and proceeds to step (a6). Otherwise, the charging pile responds to the server that it has received the regular authorization code invalidally and proceeds to step (a8).

[0071] (a6) The server then calls a random function to generate a random number and calculates the A calibration constant; A calibration constant = random number & 0x7FFF, making the A calibration constant less than 0x8000. The server securely stores the A calibration constant data in the database corresponding to the SN number and then sends the A calibration constant information; the charging pile corresponding to the SN number receives the A calibration constant information. If the integrity verification passes, the charging pile then confirms the valid range of the A calibration constant. If the A calibration constant is less than 0x8000, it is considered valid and securely stored locally. The charging pile then responds to the server that the A calibration constant has been received and proceeds to step (a7); otherwise, the charging pile responds to the server that the A calibration constant has been received invalidally and proceeds to step (a8).

[0072] (a7) The server then calls a random function to generate a random number, converts it into a decimal string, and retains the last 6 characters as the activation code. The server securely stores the activation code in the database corresponding to the SN number and sends the activation code to the production line computer. After receiving the activation code, the production line computer makes a card and prints the activation code, SN number, and corresponding QR code on the card using a card-matching tool. A scratch-off coating is applied to the activation code. The card and the corresponding charging station are packaged together, and the process proceeds to step (a8).

[0073] (a8) End.

[0074] (2) After installing the charging pile, the charging pile owner needs to register as a user. The specific process is as follows:

[0075] (b1) First, the charging station owner downloads and installs the designated mobile app according to the instructions. They then register their user information on the server, using their mobile phone number as the account and setting a password. Next, they scan the charging station's QR code to apply for binding to the charging station with the corresponding SN number, sending the binding application information. After receiving the charging station binding application information from the app, the server will request an activation code. The charging station owner scratches off the activation code coating on the card, enters the corresponding 6-digit string, and sends it to the server. Proceed to step (b2).

[0076] (b2) After receiving the activation code, the server reads the activation code stored in the database corresponding to the SN number and compares it with the received activation code. If they are the same, the server agrees to bind the charging pile to the account corresponding to the APP and creates a super user account in the database corresponding to the SN number, and proceeds to step (b3); if they are different, the binding of the charging pile fails and proceeds to step (b6).

[0077] (b3) The charging pile main mobile APP requests the server to send the super authorization code information. After receiving the request, the server reads the super authorization code stored in the super user database corresponding to the SN number, encrypts it using the specified key and algorithm, and then sends the super authorization code information to the mobile APP. After receiving the super authorization code information, the mobile APP saves the encrypted super authorization code in the mobile APP file system if the integrity verification is passed, and proceeds to step (b4).

[0078] (b4) The charging pile owner's mobile APP uses the super authorization code to activate the charging pile as a super user. If the charging pile is online, it can remotely communicate with the server. If the charging pile is offline, the charging pile owner needs to go to the vicinity of the charging pile and communicate with the charging pile via Bluetooth when connected via Bluetooth. The mobile APP sends the encrypted super authorization code and the verification value to the charging pile. After receiving the super activation information, the charging pile first checks the integrity of the frame information, calculates the verification value and compares it with the received verification value. If they are equal, it proceeds to step (b5); if they are not equal, it replies with the message that the activation verification failed and proceeds to step (b6).

[0079] (b5) The charging pile decrypts the ciphertext to obtain the super authorization code, and compares it with the super authorization code stored locally. If they are equal, the super authorization code is replied to be successfully activated. The plaintext of the super authorization code is then copied to the address corresponding to the super authorization code in the authorization whitelist, and the whitelist data is stored locally securely. If they are not equal, the super authorization code is replied to be invalid, and the process proceeds to step (b6).

[0080] (b6) End.

[0081] (3) When using a charging station, the owner can share the charging station with other users who need it. The specific process is as follows:

[0082] (c1) When the charging pile starts up, it first reads the whitelist data stored locally, reads the user addition serial number m, and proceeds to step (c2);

[0083] (c2) The charging station owner enters the mobile phone number of the user to be shared on the charging station sharing page of the mobile APP, sets the sharing time period, and submits the sharing application to the server. After receiving the sharing information from the charging station owner, the server creates a regular user account in the database corresponding to the SN number. The server then calls a random function to generate a random number and converts it into a decimal string. The last 6 characters of the string are retained as the activation code. The server securely stores the activation code in the database corresponding to the regular user of the SN number. At the same time, the server sends the activation code of the regular user to the charging station owner's mobile APP and proceeds to step (c3).

[0084] (c3) The charging station owner sends the SN number and the activation code of the ordinary user to the sharing user through the mobile APP. The sharing user downloads and installs the specified mobile APP software at the specified path, and registers the user information on the server. The account is uniformly a mobile phone number. The user registers and sets a password using the mobile phone number, and then enters the SN number to bind the charging station as an ordinary user. After receiving the binding request from the ordinary user, the server requests the input of the activation code. If the activation code entered by the ordinary user is consistent with the activation code in the database corresponding to the SN number, the server agrees to bind the corresponding APP account to the charging station and proceeds to step (c4); otherwise, proceeds to step (c7).

[0085] (c4) A regular user's mobile app requests the server to send an authorization code. After receiving the request, the server reads the regular authorization code stored in the database corresponding to the SN number and uses the formula: User authorization code = Regular authorization code + (7*n+1)*n+A, where n is the serial number of the regular user. For each new regular user added by the server, the serial number n is incremented by 1. The serial number n of the first user is 1. The value of n is in the range of [1, 10000], and A is a calibration constant. The server then uses a specified key and algorithm to encrypt the user authorization code and the sharing time period, and then sends the user authorization code information to the specified user's mobile app. After receiving the user authorization code information, if the integrity verification passes, the user's mobile app saves the encrypted user authorization code in the mobile app's file system, and then proceeds to step (c5).

[0086] (c5) Ordinary users activate the charging station using the user authorization code information via a mobile APP. If the charging station is online, mobile communication can be remotely established through the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and communicate with it via Bluetooth when connected. The mobile APP sends the user authorization code information to the charging station. Upon receiving the user authorization code information and verifying its integrity, the charging station uses a specified key and algorithm to decrypt the encrypted user authorization code and the encrypted sharing time period to obtain user authorization code 1 and the sharing time period data. The charging station then substitutes the locally stored ordinary authorization code into the formula to calculate user authorization code 2: User authorization code 2 = ordinary authorization code + (7*n+1)*n + A, where n ranges from 1 to 10000 and A is a calibration constant. If any calculated user authorization code 2 from n to 10000 is equal to user authorization code 1, the user authorization code activation is successful, and the process proceeds to step (c6). If none of the two are equal, the super authorization code is invalid, and the process proceeds to step (c7).

[0087] (c6) The charging pile then copies the user authorization code 1 and the information of the sharing time period data to the user authorization code, start time and end time address corresponding to the ordinary user information array in the authorization whitelist. The array number is the user addition number m. Then add 1 to the user addition number m. If m is greater than or equal to the maximum number of ordinary users, then m is equal to 0. Then store the user addition number m locally and store the updated authorization whitelist data locally. Proceed to step (c7).

[0088] (c7) End.

[0089] (4) Simultaneously, the charging station owner and ordinary users can reserve charging stations. If the charging station is online, a reservation can be made remotely via the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and make a reservation via Bluetooth communication with a Bluetooth connection. The specific process is as follows:

[0090] (d1) First, check the status of the charging station on the mobile app. The charging station status is mainly divided into charging status, reservation status, fault status, and idle status. If the charging station is in an idle status, you can request a reservation and proceed to step (d2). If the charging station is not in an idle status, you cannot make a reservation and proceed to step (d5).

[0091] (d2) Click the "Request Reservation" button on the mobile app. The mobile app sends reservation information (including reservation instructions, encrypted authorization code, and frame verification data; if it's the charging station owner, it's the encrypted super authorization code; otherwise, it's the encrypted user authorization code). After receiving the reservation information, the charging station, if the integrity verification passes, decrypts the received encrypted authorization code to obtain the plaintext authorization code, then compares it. If the received authorization code is a super authorization code in the whitelist, the reservation authorization code is the super authorization code, and a reservation success message is sent back to the mobile app. If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, the reservation authorization code is the corresponding user authorization code, and a reservation success message is sent back to the mobile app. Proceed to step (d3); otherwise, a reservation failure message is sent back to the mobile app. Proceed to step (d5).

[0092] (d3) Once a charging station reservation is successful, set the charging station status to reserved and report the status information to the server. Set the timeout reservation timer to 0 and proceed to step (d4);

[0093] (d4) When the charging pile is in the reservation state, the timeout reservation timer is incremented by 1 in the periodic task. It is then determined whether the timeout reservation timer is greater than the reservation timeout threshold (default is 60 minutes). If the timeout is met, the reservation is canceled directly, and the charging pile is set to end (d5).

[0094] (5) Charging station owners and ordinary users can remotely authorize charging at the charging station. If the charging station is found to be online, authorization can be remotely processed through the server. The specific process is as follows:

[0095] (e1) Click the "Request Remote Authorization Charging" button on the mobile app. The mobile app sends remote authorization information (including remote authorization instructions, encrypted authorization code, and frame verification data; if it is the charging station owner, it is encrypted super authorization code; otherwise, it is encrypted user authorization code). After receiving the remote authorization information, the charging station decrypts the received encrypted authorization code to obtain the plaintext authorization code, provided the integrity verification passes. If the charging station is idle, proceed to step (e2). If the charging station is in a reserved state, proceed to step (e3). If the charging station is in a fault state or charging state, directly reject the request and proceed to step (e5).

[0096] (e2) The charging station compares the received authorization code. If the received authorization code is a super authorization code in the whitelist, it directly authorizes the charging request and replies with an authorization success message to the mobile APP. If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, it directly authorizes the charging request, the current charging authorization code is the received authorization code, and replies with an authorization success message to the mobile APP. Proceed to step (e4); otherwise, it replies with an authorization failure message to the mobile APP. Proceed to step (e5);

[0097] (e3) The charging station compares the received authorization code. If the received authorization code is a reservation authorization code, it directly authorizes the charging request, uses the received authorization code as the current charging authorization code, and replies with an authorization success message to the mobile app. Proceed to step (e4); otherwise, it replies with an authorization failure message to the mobile app; proceed to step (e5).

[0098] (e4) The charging station checks whether the charging gun is properly plugged in. If it is, charging is started. If it is not properly plugged in, a timer is started. If the charging gun is not properly plugged in within 5 minutes, the authorization request is canceled, the charging station is set to idle state, and a timeout authorization cancellation message is sent to the corresponding mobile APP.

[0099] Proceed to step (e5);

[0100] (e5) End.

[0101] (6) The charging station owner and the user authorize charging via Bluetooth communication. If the charging station is offline, the user needs to go to the vicinity of the charging station and authorize via Bluetooth communication when connected. The specific process is as follows:

[0102] (f1) When the charging station owner or user approaches the charging station, Bluetooth will actively establish a connection. The first connection requires entering the correct passkey. After the mobile app detects that the phone's Bluetooth and the charging station's Bluetooth have established a connection, it will actively send authentication information (including authentication instructions, encrypted authorization code, and frame verification data; if it is the charging station owner, it is the encrypted super authorization code; otherwise, it is the encrypted user authorization code). Proceed to step (f2);

[0103] (f2) After receiving the information, the charging pile decrypts the received authorization code ciphertext to obtain the plaintext authorization code, provided the integrity verification passes. The authorization codes are then compared. If the received authorization code is a super authorization code from the whitelist, super user authentication is set to successful, the corresponding authorization code is recorded, and an authentication success message is sent to the mobile app. If the received authentication code is any user authorization code from the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, then the corresponding ordinary user authentication is set to successful, the corresponding authorization code is recorded, and an authentication success message is sent to the mobile app. Next, it is determined whether the charging pile is in a reservation state. If it is in a reservation state, proceed to step (f3). If it is not in a reservation state, proceed to step (f6).

[0104] (f3) If the plug-and-charge function is enabled on the charging station, proceed to step (f4). If the plug-and-charge function is disabled on the charging station, proceed to step (f5).

[0105] (f4) Check if the authorization code corresponding to all Bluetooth authentication successful states is equal to the reservation authorization code. If there is an authorization code corresponding to a Bluetooth authentication successful state that is equal to the reservation authorization code, then directly authorize the charging request, set the current charging authorization code to be equal to the reservation authorization code, and proceed to step (f9). If there is no authorization code corresponding to a Bluetooth authentication successful state that is equal to the reservation authorization code, then proceed to step (f10).

[0106] (f5) The user can click the "Request Bluetooth Authorization for Charging" button on the mobile app. The mobile app sends Bluetooth authorization information (including Bluetooth authorization instructions, encrypted authorization code, and frame verification data; if the user is the charging station owner, it is encrypted super authorization code; otherwise, it is encrypted user authorization code). After receiving the authorization information, the charging station decrypts the encrypted authorization code to obtain the plaintext authorization code, provided the integrity verification passes. The charging station then compares the received authorization code. If the received authorization code equals the reservation authorization code, it directly authorizes the charging request, sets the current charging authorization code as the reservation authorization code, and replies with authorization success information to the mobile app. Proceed to step (f9); otherwise, it replies with authorization failure information to the mobile app. Proceed to step (f10).

[0107] (f6) If the charging station is configured to enable plug-and-charge, proceed to step (f7). If the charging station is configured to disable plug-and-charge, proceed to step (f8).

[0108] (f7) Check if there is a Bluetooth authentication pass status. If it is, directly authorize the charging request, set the current charging authorization code to the authorization code corresponding to the Bluetooth authentication pass status, and proceed to step (f9); otherwise, proceed to step (f8).

[0109] (f8) The user can click the "Request Bluetooth Authorization for Charging" button on the mobile app. The mobile app sends Bluetooth authorization information (including Bluetooth authorization instructions, encrypted authorization code, and frame verification data; if it is the charging station owner, it is the encrypted super authorization code; otherwise, it is the encrypted user authorization code). After receiving the authorization information, the charging station decrypts the encrypted authorization code to obtain the plaintext authorization code, provided the integrity verification passes. The charging station then compares the received authorization code. If the received authorization code is a super authorization code in the whitelist, it directly authorizes the charging request, sets the current charging authorization code to the received authorization code, and replies with an authorization success message to the mobile app. If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, it directly authorizes the charging request, sets the current charging authorization code to the received authorization code, and replies with an authorization success message to the mobile app. Proceed to step (f9). Otherwise, it replies with an authorization failure message to the mobile app. Proceed to step (f10).

[0110] (f9) The charging station checks if the charging gun is properly plugged in. If it is, charging begins. If it is not properly plugged in, a timer starts. If the charging gun is not properly plugged in within 5 minutes, the authorization request is canceled, the charging station is set to idle status, and a timeout authorization cancellation message is sent to the corresponding mobile app.

[0111] Proceed to step (f10);

[0112] (f10) End.

[0113] (7) Charging station owners and users can cancel the charging authorization for the charging station. If the charging station is online, the authorization can be canceled remotely through the server. If the charging station is offline, the user needs to go to the vicinity of the charging station and cancel the charging authorization via Bluetooth communication when connected via Bluetooth. The specific process is as follows:

[0114] (g1) The user can click the button on the mobile app to request Bluetooth or remote cancellation of charging authorization. The mobile app sends cancellation information (including Bluetooth or remote cancellation command, encrypted authorization code, and frame verification data; if it is the charging station owner, it is the encrypted super authorization code; otherwise, it is the encrypted user authorization code). After receiving the cancellation information, the charging station decrypts the encrypted authorization code to obtain the plaintext authorization code, provided the integrity verification passes. The charging station compares the received authorization code. If the received authorization code is a super authorization code, charging is canceled directly, and the reason for cancellation is set as "super user cancellation". If the received authorization code is the current charging authorization code (the authorization code corresponding to the authorization at the time of authorization), charging is canceled directly, and the reason for cancellation is set as "ordinary user cancellation". Proceed to step (g2).

[0115] (g2) End.

[0116] (8) Configuring the charging station: Only the charging station owner has the authority to configure the charging station. If the charging station is online, it can be configured remotely through the server. If the charging station is offline, you need to go to the vicinity of the charging station and configure it via Bluetooth communication with a Bluetooth connection. The specific process is as follows:

[0117] (h1) The charging station owner clicks on the mobile app to enter the configuration interface, which includes options to enable or disable the plug-and-charge function. If enabled, the configuration status is "enabled"; if disabled, the configuration status is "disabled". The mobile app sends the plug-and-charge function configuration information (including the plug-and-charge function configuration command, configuration status, encrypted super authorization code, and frame verification data). Proceed to step (h2);

[0118] (h2) After receiving the plug-and-charge function configuration information, the charging pile decrypts the received authorization code ciphertext to obtain the authorization code plaintext if the integrity verification passes. If the received authorization code is a super authorization code, the plug-and-charge function configuration status is set to the received configuration status, and the configuration status is saved to EEPROM; proceed to step (h3).

[0119] (h3) End.

[0120] The above-described method of the present invention enables charging pile owners to share charging piles, multiple users to schedule charging, and multiple users to manage data, thus solving the problem of multiple users sharing a set of charging pile equipment and providing a technical means for effectively and fully utilizing charging pile equipment.

[0121] The above description is merely an embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of the claims of the present invention.

Claims

1. A method for private pile sharing and multi-user reservation charging of a vehicle-mounted charging pile, characterized in that, The method comprises user information registration, charging pile main user registration, charging pile information sharing and multi-user reservation charging, wherein after the user information registration and the charging pile main user registration are completed: The pile main and the ordinary user make reservation charging for the charging pile. If the charging pile is online, the specified charging pile can be reserved remotely through the server. If the charging pile is not online, the user needs to be near the charging pile, and the reservation is made through Bluetooth communication under the condition of Bluetooth connection; The pile main and the ordinary user make remote authorization charging for the charging pile. If the charging pile is online, the authorization can be made remotely through the server. The charging pile information sharing step specifically comprises: (c1) When the charging pile is started, the white list data stored locally is read first, the user addition serial number m is read, and step (c2) is entered; (c2) The charging pile main inputs the mobile phone number of the user to be shared on the charging pile sharing page of the mobile phone APP, sets the sharing time period, and submits the sharing application to the server; After the server receives the sharing information of the charging pile main, an ordinary user account is created in the database corresponding to the SN number, a random number is generated by calling a random function, and the random number is converted into a decimal string. The last 6 characters of the string are reserved as the activation code. The server stores the activation code in the database of the ordinary user corresponding to the SN number, and sends the activation code of the ordinary user to the mobile phone APP of the charging pile main, and step (c3) is entered; (c3) The charging pile main sends the SN number and the activation code of the ordinary user to the shared user through the mobile phone APP. The shared user downloads and installs the specified mobile phone APP installation software at the specified path, registers the user information of the server, the account is unified as the mobile phone number, registers and sets the password using the mobile phone number, and binds the charging pile as an ordinary user by inputting the SN number. After the server receives the ordinary user binding request, the activation code is requested to be input. If the activation code input by the ordinary user is consistent with the activation code in the database corresponding to the SN number, the server agrees to bind the charging pile to the corresponding APP account, and step (c4) is entered. Otherwise, step (c7) is entered; (c4) The common user mobile phone APP requests the server to send the authorization code information. After receiving the request, the server reads the common authorization code stored in the database corresponding to the SN number, and calculates the user authorization code through the formula: user authorization code = common authorization code + (7 n+1) n + A, where n is the serial number of the common user, the serial number n is increased by 1 for each additional common user, the serial number n of the first user is 1, where n takes the value range 【1, 10000】, and A is a calibration constant. (c5) The common user mobile phone APP sends the user authorization code to the server, and the server verifies the user authorization code. If the user authorization code is correct, the server sends the user a welcome message and a common user account password to the mobile phone APP of the user. The server further encrypts the user authorization code and the sharing time period using a specified secret key and algorithm, and sends the user authorization code information to the specified user mobile phone APP. After the user mobile phone APP receives the user authorization code information, the user authorization code ciphertext is saved in the file system of the mobile phone APP under the condition that the integrity verification is passed, and step (c5) is entered; (c5) The ordinary user activates the charging pile through the mobile phone APP using the user authorization code information. If the charging pile is online, it can be remotely communicated through the server; if the charging pile is not online, the user needs to be near the charging pile, and communicate with the charging pile under the condition of Bluetooth connection; the mobile phone APP sends the user authorization code information to the charging pile, and the charging pile receives the user authorization code information. If the integrity check is passed, the user authorization code 1 and the shared time period data are obtained by using the specified secret key and algorithm to decrypt the user authorization code ciphertext and the shared time period ciphertext; the charging pile substitutes the locally stored ordinary authorization code into the formula to calculate the user authorization code 2, user authorization code 2 = ordinary authorization code + (7 n+1) n +A, where n is in the range of 1-10000, and A is a calibration constant; if n is from 1 to 10000, any calculated user authorization code 2 is equal to the user authorization code 1, then reply that the user authorization code activation is successful, and enter step (c6); if none of them are equal, reply that the super authorization code is invalid, and enter step (c7); (c6) The charging pile copies the user authorization code 1 and the sharing time period data information to the user authorization code, the start time and the end time addresses of the ordinary user information array corresponding to the authorization white list, and the array serial number is the user addition serial number m. Then, the user addition serial number m is increased by 1. If m is greater than or equal to the maximum number of ordinary users, m is equal to 0. Then, the user addition serial number m is stored locally, the updated authorization white list data is stored locally, and step (c7) is entered; (c7) End; The user authorization code information comprises a user authorization code instruction, a user authorization code ciphertext, a sharing time period data ciphertext and frame check data. 2.The method of claim 1, wherein, The user information registration step includes: (a1) after the vehicle-mounted charging pile is assembled on the production line, power supply is needed to start and establish a connection with the server, after the connection is successful, the charging pile sends a request SN number registration information; after the server receives the request SN number registration information, under the condition that the integrity check is passed, it further checks whether the SN number has been registered, if it has been registered, it returns a registration failure information to the charging pile, and enters step (a8); if it has not been registered, it responds to the registration, establishes a database corresponding to the SN, and returns a registration success information to the charging pile, and enters step (a2); (a2) the server generates corresponding secret key data according to the SN number, securely stores the secret key data in the database corresponding to the SN number, and sends secret key configuration information; after the charging pile receives the secret key configuration information, under the condition that the integrity check is passed, it performs local secure storage, and returns secret key configuration success information to the server, and enters step (a3); (a3) the server generates an authorization code according to the serial number data in the SN number, the server system time data and the random number generated by the random number function; the authorization code = the serial number data in the SN number + the server time data + the random number, and enters step (a4); (a4) the server generates a super authorization code according to the authorization code, which is used for the main use of the charging pile; the super authorization code = the authorization code & 0x3FFFFFFF, so that the super authorization code cannot be greater than 0x3FFFFFFF; the server securely stores the super authorization code data in the database corresponding to the SN number, and encrypts it using the specified secret key and algorithm, and then sends the super authorization code information to the charging pile corresponding to the SN number; the corresponding charging pile receives the super authorization code information, and under the condition that the integrity check is passed, it decrypts the ciphertext using the specified secret key and algorithm to obtain the super authorization code plaintext; the corresponding charging pile further confirms the effective range of the super authorization code, if the super authorization code is less than or equal to 0x3FFFFFFF, it is considered valid, and is stored locally securely, and responds to the server to effectively receive the super authorization code, and enters step (a5), otherwise, it responds to the server to invalidly receive the super authorization code, and enters step (a8); (a5) The server generates a normal authorization code according to the authorization code, and the normal authorization code is used when the charging pile host shares it with other users; the normal authorization code = ((authorization code & 0x7FFFFFFF) | 0x40000000), so that the normal authorization code is greater than 0x3FFFFFFF and less than 0x80000000; the server stores the normal authorization code data in the database corresponding to the SN number, and encrypts it using the specified key and algorithm, and then sends the normal authorization code information; the charging pile corresponding to the SN number receives the normal authorization code information, and under the condition that the integrity check is passed, the ciphertext is decrypted using the specified key and algorithm to obtain the normal authorization code plaintext; the charging pile further confirms the effective range of the normal authorization code, if the normal authorization code is greater than 0x3FFFFFFF and less than 0x80000000, it is considered valid, and is stored locally, and the server effectively receives the normal authorization code, and enters step (a6); otherwise, the server invalidly receives the normal authorization code, and enters step (a8); (a6) The server further calls a random function to generate a random number, and calculates an A constant; the A constant = random number & 0x7FFF, so that the A constant is less than 0x8000, the server stores the A constant data in the database corresponding to the SN number, and then sends the A constant information; the charging pile corresponding to the SN number receives the A constant information, and under the condition that the integrity check is passed, the charging pile further confirms the effective range of the A constant, if the A constant is less than 0x8000, it is considered valid, and is stored locally, and the server effectively receives the A constant, and enters step (a7); otherwise, the server invalidly receives the A constant, and enters step (a8); (a7) The server further calls a random function to generate a random number, and converts it into a decimal string, and the last 6 characters of the string are taken as the activation code, the server stores the activation code in the database corresponding to the SN number, and sends the activation code to the production line computer; the production line computer receives the activation code and makes a card, prints the activation code, SN number and corresponding two-dimensional code on the card through the card distribution tool, and coats a layer of scratchable coating on the activation code; the card and the corresponding charging pile are packaged together, and enter step (a8); (a8) End. The SN number registration information includes a registration instruction, an SN number and frame check data; the key configuration information includes a key configuration instruction, key data and frame check data. 3.The method of claim 1, wherein, The charging pile host user registration step is specifically: (b1) First, the charging pile master downloads the designated mobile phone APP installation software according to the instructions and installs it, and registers the user information of the server, the account is unified as a mobile phone number, and the mobile phone number is registered, and a password is set; then scan the two-dimensional code of the charging pile, apply to bind the charging pile of the SN number corresponding to the two-dimensional code, and send the application binding information; after the server receives the APP application binding charging pile information, it will request to input the activation code, the pile master scratches the activation code coating of the card, inputs the corresponding 6-bit string, and sends it to the server, and enters step (b2); (b2) After the server receives the activation code, the SN number corresponding to the database is read and compared with the received activation code, if they are the same, the APP corresponding account is bound to the charging pile, and a super user account is created in the SN number corresponding database, and enters step (b3); if they are not the same, the binding of the charging pile fails, and enters step (b6); (b3) The charging pile master mobile phone APP requests the server to send super authorization code information, the server receives the request, reads the super user stored super authorization code in the SN number corresponding database, and uses the specified secret key and algorithm to encrypt, and then sends the super authorization code information to the mobile phone APP. The mobile phone APP receives the super authorization code information, saves the super authorization code ciphertext in the mobile phone APP file system under the condition that the integrity check is passed, and enters step (b4); (b4) The charging pile master mobile phone APP uses the super authorization code to activate the charging pile, which can remotely communicate through the server if the charging pile is online; if the charging pile is not online, the charging pile master needs to be near the charging pile, and communicate with the charging pile through Bluetooth under the condition of Bluetooth connection; the mobile phone APP sends the super authorization code ciphertext and the check value to the charging pile, and the charging pile receives the super activation information, first checks the integrity of the frame information, calculates the check value and the received check value, and compares them, if they are equal, enter step (b5); if they are not equal, reply information activation check fails, and enter step (b6); (b5) The charging pile decrypts the ciphertext to obtain the super authorization code, and compares it with the locally stored super authorization code, if they are equal, reply super authorization code activation success, copy the super authorization code plaintext to the super authorization code corresponding address of the authorization white list, and store the white list data locally; If they are not equal, reply information super authorization code invalid, enter step (b6); (b6) End.

4. The method of claim 1, wherein, The pile master and the ordinary user make a reservation for the charging pile, and if the charging pile is online, the designated charging pile can be remotely reserved through the server; if the charging pile is not online, the user needs to be near the charging pile, and communicates through Bluetooth under the condition of Bluetooth connection, which is specifically as follows: (d1) First, check the status of the charging pile on the mobile phone APP, the charging pile status is mainly divided into charging state, reservation state, fault state and idle state, if the charging pile state is idle, it can be reserved, step (d2); If the charging pile state is not idle, it cannot be reserved, step (d5); (d2) Click the mobile phone APP request reservation button, the mobile phone APP sends the reservation information (including reservation instruction, authorization code ciphertext and frame check data, if it is a pile master, it is a super authorization code ciphertext, otherwise it is a user authorization code ciphertext); After receiving the reservation information, the charging pile passes the integrity check, decrypts the received authorization code ciphertext to get the authorization code plaintext, and then compares it. If the received authorization code is a super authorization code in the white list, the reservation authorization code is a super authorization code, and the mobile phone APP is replied with a reservation success information; If the received authorization code is any user authorization code in the white list, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the white list, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the white list, the reservation authorization code is the corresponding user authorization code, and the mobile phone APP is replied with a reservation success information; Step (d3); Otherwise, reply the mobile phone APP with a reservation failure information; Step (d5); (d3) Once the charging pile is successfully reserved, set the charging pile state to reservation state, and report the state information to the server; Set the timeout reservation timer to 0, step (d4); (d4) In the periodic task, the charging pile is in the reservation state, and the timeout reservation timer is added by 1. If the timeout reservation timer is greater than the reservation timeout threshold, the reservation is directly canceled, the charging pile state is set to idle, and the state information is reported to the server; Step (d5); (d5) End.

5. The method of claim 1, wherein, The pile master and the ordinary user remotely authorize the charging pile to charge, if the charging pile is online, it can be remotely authorized through the server, which is specifically: (e1) Click the mobile phone APP request remote authorization charging button, the mobile phone APP sends the remote authorization information; After receiving the remote authorization information, the charging pile passes the integrity check, and decrypts the received authorization code ciphertext to get the authorization code plaintext; If the charging pile is in idle state, step (e2); If the charging pile is in reservation state, step (e3); If the charging pile is in fault state or in charging state, directly refuse the request, step (e5); (e2) The charging pile compares the received authorization code. If the received authorization code is a super authorization code in the white list, it directly authorizes the request to charge, and replies the mobile phone APP with an authorization success information; If the received authorization code is any user authorization code in the whitelist, and the current system time is greater than or equal to the valid start time of the corresponding user authorization code in the whitelist, and the current system time is less than or equal to the valid end time of the corresponding user authorization code in the whitelist, the request for charging is directly authorized, the current charging authorization code is the received authorization code, and the authorization success information is returned to the mobile phone APP; Step (e4) is entered; otherwise, the authorization failure information is returned to the mobile phone APP; step (e5) is entered; (e3) The charging pile compares the received authorization code. If the received authorization code is a reservation authorization code, the request for charging is directly authorized, the current charging authorization code is the received authorization code, and the authorization success information is returned to the mobile phone APP; Step (e4) is entered; otherwise, the authorization failure information is returned to the mobile phone APP; Step (e5) is entered. (e4) The charging pile checks whether the charging gun is inserted. If it is inserted, the charging is started. If it is not inserted, the periodic timing is started. If the charging gun is not inserted within 5 minutes, the authorization request is directly canceled, the charging pile is set to an idle state, and the uninserted gun timeout cancellation authorization information is sent to the corresponding mobile phone APP; step (e5) is entered. (e5) is ended.

6. The method of claim 5, wherein the method further comprises: The pile master and the user cancel the authorized charging of the charging pile. If the charging pile is online, the remote cancellation of the authorized charging can be performed through the server. If the charging pile is not online, the user needs to be near the charging pile. Under the condition of Bluetooth connection, the cancellation of the authorized charging is performed through Bluetooth communication. Specifically, (g1) The user can click the mobile phone APP to request the Bluetooth or remote cancellation of the authorized charging button. The mobile phone APP sends the cancellation authorization information. After the charging pile receives the cancellation authorization information, the authorization code ciphertext is decrypted to obtain the authorization code plaintext under the condition that the integrity check is passed. The charging pile compares the received authorization code. If the received authorization code is a super authorization code, the charging is directly canceled, and the cancellation reason of the charging is set to the super user cancellation of the charging. If the received authorization code is the current charging authorization code, the charging is directly canceled, and the cancellation reason of the charging is set to the ordinary user cancellation of the charging. Step (g2) is entered. (g2) is ended. 7.The method of claim 2, wherein, The ordinary authorization code information includes an ordinary authorization code instruction, an ordinary authorization code ciphertext, and frame check data. The super authorization code information includes a super authorization code instruction, a super authorization code ciphertext, and frame check data. 8.The method of claim 2, wherein, The A calibration constant is a constant in the ordinary user authorization code calculation formula, including a calibration constant instruction, A calibration constant data, and frame check data.

9. A vehicle-mounted charging pile system using the private pile sharing and multi-user reservation charging method according to any one of claims 1-8, characterized in that, It includes: A mobile phone terminal including a processor and a storage module and a mobile phone Bluetooth module electrically connected to the processor; A charging pile including an MCU controller and a charging pile Bluetooth module and a 4G module electrically connected to the MCU controller; A cloud service platform based on a server; The mobile phone terminal and the charging pile communicate through Bluetooth, and the mobile phone terminal, the charging pile, and the cloud service platform communicate through 4G or WIFI.

Images