Wireless debugging method and system for charging pile
The wireless charging station debugging method and system address inefficiencies and security issues by using a wireless connection and secure authentication to facilitate rapid, secure, and efficient debugging across multiple stations.
Patent Information
- Application Number
- CN202510340488.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-21
- Publication Date
- 2025-07-15
AI Technical Summary
The traditional wired debugging of charging piles poses safety risks, is inefficient, and data transmission is unsafe, making it difficult to meet the rapid deployment and operation and maintenance needs of large-scale charging pile groups.
Wireless debugging method is adopted to establish a connection with the charging pile through a wireless serial port adapter, and after two-way authentication, a LAN is formed, debugging instructions are broadcasted, and the debugging logs are stored in multiple layers. Combined with multiple wireless communication modules and multiple security mechanisms, batch debugging and automated management are realized.
It improves the efficiency and safety of charging pile debugging, reduces the need for manual intervention, is suitable for rapid deployment and operation and maintenance in complex environments, reduces labor and travel costs, and improves the security of data transmission and storage.
Smart Images

Figure CN120307942A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of charging pile debugging, and in particular to a charging pile wireless debugging method and system. Background Art
[0002] A charging pile is a device that provides electric energy to electric vehicles, enabling them to store enough electricity to support their operation. With the rapid development of electric vehicles, the demand for charging piles is also increasing day by day. Charging piles can be divided into AC charging piles (slow charging) and DC charging piles (fast charging) according to the charging method. AC charging piles directly transmit AC power from the power grid to the on-board charger of the electric vehicle, which converts AC power into DC power and charges it into the battery; DC charging piles directly transmit DC power to the battery of the electric vehicle, charging faster. AC charging piles are generally used for individual users in the community, and DC charging piles are generally used in charging stations.
[0003] After the installation is completed, the charging pile needs to be debugged before it can be put into operation. For the debugging of the charging pile, it is traditionally necessary to connect the charging pile to the debug interface for debugging. Due to the complexity of the deployment scenarios of charging piles (such as three-dimensional charging areas in underground parking lots and distributed service stations on highways), debuggers often need to perform interface plugging and unplugging operations in narrow spaces or high-altitude working environments, which poses a safety hazard and prolongs the operation time. Actual measured data shows that in dense charging station scenarios, the wired debugging of a single pile takes an average of 25-40 minutes, of which 15% of the time is lost due to repeated operations caused by unstable physical connections; in addition, the log files generated by wired debugging are stored in various debugging terminals in a scattered manner, lacking a unified encryption transmission mechanism. A security audit report pointed out that 23% of charging pile security incidents were caused by the interception of unencrypted data during the debugging phase, resulting in the leakage of the charging billing system key.
[0004] Therefore, how to provide a charging pile wireless debugging method and system to improve the charging pile debugging efficiency and safety has become a technical problem that needs to be solved urgently. Summary of the invention
[0005] The technical problem to be solved by the present invention is to provide a charging pile wireless debugging method and system to improve the debugging efficiency and safety of the charging pile.
[0006] In a first aspect, the present invention provides a charging pile wireless debugging method, comprising the following steps:
[0007] Step S10: The debugging terminal establishes a wireless connection with one of the charging piles through the wireless serial port adapter of the charging pile, and performs two-way authentication with the charging pile;
[0008] Step S20: The debugging terminal sends a networking instruction to the connected charging piles to form a local area network with all charging piles within the coverage range of the wireless signal;
[0009] Step S30: The debugging terminal sends a debugging instruction to the charging pile. After verifying the received debugging instruction, the charging pile broadcasts the debugging instruction within the local area network.
[0010] Step S40: Each charging pile that receives the debugging instruction performs a firmware version verification.
[0011] Step S50: Each charging pile synchronously executes a debugging operation based on the debugging task carried in the debugging instruction. During the debugging process, the debugging progress is announced through a speaker, and after the debugging is completed, the debugging result is fed back to the debugging terminal.
[0012] Step S60: The debugging terminal records a debugging log that at least includes the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log into an encrypted log, and backs up the encrypted log to the server.
[0013] Further, step S10 specifically includes:
[0014] Step S11: The debugging terminal connects to the wireless serial port adapter of one of the charging piles through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a WIFI communication module, a Bluetooth communication module, or a ZigBee communication module, and then establishes a wireless connection with the charging pile.
[0015] Step S12: The debugging terminal presets a root certificate, a terminal working certificate, and a first terminal private key, and the charging pile presets a root certificate, a charging pile working certificate, and a charging pile private key; the root certificate carries a root public key; the terminal working certificate is obtained by signing the first terminal public key with the root private key; the charging pile working certificate is obtained by signing the charging pile public key with the root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm.
[0016] Step S13: The debugging terminal and the charging pile perform two-way authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate, and the charging pile private key.
[0017] Further, step S20 is specifically:
[0018] The debugging terminal sends a networking instruction that at least carries a network frequency band, a first sending time, and a first hash value to the connected charging pile, and the first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time.
[0019] The charging pile parses the received networking instruction to obtain a network frequency band, a first transmission time, and a first hash value. After performing integrity verification on the network frequency band and the first transmission time through the first hash value, it performs timeliness verification through the first transmission time, and then forms a local area network with all charging piles within the wireless signal coverage based on the network frequency band.
[0020] Further, the specific step S30 is as follows:
[0021] The debugging terminal sends a debugging instruction to the charging pile, which at least carries ciphertext data, a second transmission time, and a second hash value. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second transmission time. The ciphertext data is encrypted through the RC6 algorithm and the 3DES algorithm for the debugging task, the latest firmware version number, and the firmware download URL.
[0022] The charging pile parses the received debugging instruction to obtain the ciphertext data, the second transmission time, and the second hash value. After performing integrity verification on the ciphertext data and the second transmission time through the second hash value, it performs timeliness verification through the second transmission time, and then broadcasts the debugging instruction within the local area network.
[0023] The specific step S40 is as follows:
[0024] Each charging pile that receives the debugging instruction parses the debugging instruction to obtain the ciphertext data, decrypts the ciphertext data through the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number, and the firmware download URL, verifies the local firmware version through the latest firmware version number, and if an upgrade is required, downloads the latest firmware through the firmware download URL to perform the upgrade operation.
[0025] Further, the specific step S60 is as follows:
[0026] The debugging terminal records a debugging log that at least includes the debugging time, the debugging terminal number, the charging pile number, and the debugging result. Encrypts the debugging log through the SM4 algorithm to obtain a first-layer encrypted text, generates a 16-bit random string, inserts the random string at the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text, encrypts the second-layer encrypted text through the IDEA algorithm to obtain a third-layer encrypted text, swaps the numbers 0 and the letter O, the numbers 1 and the letter L, and the numbers 5 and the letter S in the third-layer encrypted text to obtain a fourth-layer encrypted text, encrypts the fourth-layer encrypted text through the ECDSA algorithm to obtain an encrypted log, and backs up the encrypted log to the server.
[0027] In a second aspect, the present invention provides a wireless debugging system for a charging pile, including the following modules:
[0028] A wireless connection module, which is used for a debugging terminal to establish a wireless connection with one of the charging piles through a wireless serial port adapter of the charging pile and perform two-way authentication with the charging pile;
[0029] A local area network formation module, which is used for the debugging terminal to send a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage range;
[0030] A debugging instruction broadcasting module, which is used for the debugging terminal to send a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, it broadcasts the debugging instruction within the local area network;
[0031] A firmware version verification module, which is used for each charging pile receiving the debugging instruction to perform firmware version verification;
[0032] A batch debugging module, which is used for each charging pile to synchronously execute debugging operations based on the debugging tasks carried in the debugging instruction, broadcast the debugging progress through a speaker during the debugging process, and feedback the debugging result to the debugging terminal after the debugging ends;
[0033] A debugging log management module, which is used for the debugging terminal to record debugging logs including at least debugging time, debugging terminal number, charging pile number, and debugging result, encrypt the debugging logs into encrypted logs, and back up the encrypted logs to the server.
[0034] Further, the wireless connection module specifically includes:
[0035] A charging pile connection unit, which is used for the debugging terminal to connect to a wireless serial port adapter of one of the charging piles through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a Wi-Fi communication module, a Bluetooth communication module, or a ZigBee communication module, and then establish a wireless connection with the charging pile;
[0036] A key preset unit, which is used for the debugging terminal to preset a root certificate, a terminal working certificate, and a first terminal private key, and the charging pile to preset a root certificate, a charging pile working certificate, and a charging pile private key; the root certificate carries a root public key; the terminal working certificate is obtained by signing a first terminal public key with a root private key; the charging pile working certificate is obtained by signing a charging pile public key with a root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm;
[0037] A two-way authentication unit, which is used for the debugging terminal and the charging pile to perform two-way authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate, and the charging pile private key.
[0038] Further, the local area network establishment module is specifically configured to:
[0039] The debugging terminal sends a networking instruction carrying at least a network frequency band, a first sending time, and a first hash value to the connected charging pile. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time.
[0040] The charging pile analyzes the received networking instruction to obtain the network frequency band, the first sending time, and the first hash value. After performing an integrity check on the network frequency band and the first sending time through the first hash value, a timeliness check is performed through the first sending time, and then a local area network is established with all the charging piles within the wireless signal coverage range based on the network frequency band.
[0041] Further, the debugging instruction broadcasting module is specifically configured to:
[0042] The debugging terminal sends a debugging instruction carrying at least ciphertext data, a second sending time, and a second hash value to the charging pile. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is obtained by encrypting the debugging task, the latest firmware version number, and the firmware download URL through the RC6 algorithm and the 3DES algorithm.
[0043] The charging pile analyzes the received debugging instruction to obtain the ciphertext data, the second sending time, and the second hash value. After performing an integrity check on the ciphertext data and the second sending time through the second hash value, a timeliness check is performed through the second sending time, and then the debugging instruction is broadcast within the local area network.
[0044] The firmware version verification module is specifically configured to:
[0045] Each charging pile that receives the debugging instruction analyzes the debugging instruction to obtain the ciphertext data, decrypts the ciphertext data through the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number, and the firmware download URL, verifies the local firmware version through the latest firmware version number, and if an upgrade is required, downloads the latest firmware through the firmware download URL to perform the upgrade operation.
[0046] Further, the debugging log management module is specifically configured to:
[0047] The debugging terminal record includes at least the debugging time, the debugging terminal number, the charging pile number, and the debugging log of the debugging result. The debugging log is encrypted by the SM4 algorithm to obtain a first-layer encrypted text. A 16-bit random string is generated and inserted into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. The second-layer encrypted text is encrypted into a third-layer encrypted text by the IDEA algorithm. The numbers 0 and the letter O, the numbers 1 and the letter L, and the numbers 5 and the letter S in the third-layer encrypted text are swapped to obtain a fourth-layer encrypted text. The fourth-layer encrypted text is encrypted by the ECDSA algorithm to obtain an encrypted log, and the encrypted log is backed up to the server.
[0048] The advantages of the present invention are as follows:
[0049] 1. The debugging terminal uses a wireless serial adapter to establish a wireless connection with the charging pile and conducts two-way authentication with the charging pile. The debugging terminal sends a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage range. Then the debugging terminal sends a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, it broadcasts the debugging instruction within the local area network. Each charging pile that receives the debugging instruction performs a firmware version verification and synchronously executes the debugging operation based on the debugging task carried in the debugging instruction. During the debugging process, the debugging progress is broadcast through a speaker, and after the debugging is completed, the debugging result is fed back to the debugging terminal. The debugging terminal records the debugging log that includes at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log into an encrypted log, and backs it up to the server. That is, the debugging terminal connects to the serial port of the charging pile through a wireless serial adapter for debugging, without the need for the traditional plug-and-unplug operation of the interface. Each charging pile forms a local area network, and the debugging instruction is broadcast within the local area network to perform a batch debugging operation on each charging pile. Moreover, security measures are taken for the networking instruction, the debugging instruction, and the debugging log to prevent data from being tampered with or stolen in plain text, thus greatly improving the debugging efficiency and security of the charging pile.
[0050] 2. When the charging pile receives the debugging instruction, it first performs a firmware version verification. If there is an updated firmware, it first executes the upgrade operation. The discovered BUGs can be repaired through firmware upgrade, reducing the debugging threshold and further improving the debugging efficiency of the charging pile.
[0051] 3. By recording the debugging log that includes at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result and backing it up to the server, it is convenient for later traceability and subsequent problem analysis and responsibility definition.
[0052] 4. Connect to the wireless serial adapter of the charging pile through a 4G communication module, 5G communication module, NB-IOT communication module, LORA communication module, WIFI communication module, Bluetooth communication module or ZigBee communication module, and then establish a wireless connection with the charging pile. That is, establish a connection with the charging pile through multi-mode communication, and the communication module with the best signal strength can be selected as needed, thus greatly improving the stability of the wireless connection and further greatly improving the stability of the charging pile debugging.
[0053] 5. Preset the root certificate, terminal working certificate and the first terminal private key in the debugging terminal, and preset the root certificate, charging pile working certificate and charging pile private key in the charging pile; the debugging terminal and the charging pile perform two-way authentication through the root certificate, terminal working certificate, the first terminal private key, charging pile working certificate and charging pile private key. The authentication process adopts at least 6 security measures (terminal working certificate verification, charging pile working certificate verification, first signature data verification, second signature data verification, first verification value verification, timestamp timeliness verification), and the first signature data verification, second signature data verification and first verification value verification are all generated based on multiple keys, increasing the difficulty of cracking and preventing illegal terminals from controlling the charging pile, thus greatly improving the security of the charging pile debugging.
[0054] 6. Send a networking instruction carrying at least the network frequency band, the first sending time and the first hash value to the connected charging pile through the debugging terminal. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time; subsequent integrity verification can be performed through the first hash value, and timeliness verification can be performed through the first sending time to avoid executing illegal networking instructions, thus greatly improving the security of the charging pile networking.
[0055] 7. Send a debugging instruction carrying at least ciphertext data, the second sending time and the second hash value to the charging pile through the debugging terminal. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is encrypted through the RC6 algorithm and the 3DES algorithm for the debugging task, the latest firmware version number and the firmware download URL; subsequent integrity verification can be performed through the second hash value, timeliness verification can be performed through the second sending time, and the debugging task, the latest firmware version number and the firmware download URL are double-encrypted through the RC6 algorithm and the 3DES algorithm to avoid the plaintext theft of data, thus greatly improving the security of the debugging instruction transmission.
[0056] 8. Encrypt the debugging log through the SM4 algorithm to obtain a first-layer encrypted text. Generate a 16-bit random string, and insert the random string into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. Encrypt the second-layer encrypted text into a third-layer encrypted text through the IDEA algorithm. Swap the number 0 and the letter O, the number 1 and the letter L, and the number 5 and the letter S in the third-layer encrypted text to obtain a fourth-layer encrypted text. Encrypt the fourth-layer encrypted text through the ECDSA algorithm to obtain an encrypted log, and back up the encrypted log to the server. That is, the encryption process of the debugging log combines triple encryption (symmetric encryption of the SM4 algorithm, symmetric encryption of the IDEA algorithm, and asymmetric encryption of the ECDSA algorithm) and second-order data transformation (insertion of random strings, character replacement). Inserting random strings can improve the ability to resist replay attacks. Combining national cryptographic algorithms with international standard algorithms forms a hybrid encryption system. The final encrypted log requires both the encryption algorithm and the data transformation rules to be decrypted, thus greatly improving the security of the debugging log storage.
[0057] 9. By supporting multiple wireless modules such as 4G / 5G / NB-IoT / LoRa / WiFi / Bluetooth / ZigBee, it adapts to the network coverage requirements of different scenarios, gets rid of the dependence on physical interfaces and cables in traditional wired debugging, and improves the deployment efficiency. Establish an initial connection through a wireless serial adapter, reduce the rigid requirements for the physical location of the charging pile, and facilitate debugging in remote or complex environments.
[0058] 10. After the debugging terminal is connected to a single charging pile, quickly form a local area network, and all charging piles within the coverage area automatically connect to the network, realizing unified debugging management of the charging piles and significantly improving the multi-node debugging efficiency.
[0059] 11. Broadcast the debugging progress through a speaker, and feedback the operation status in real time, which is convenient for on-site personnel to monitor and improves the visualization and user experience of the debugging process.
[0060] 12. From wireless connection, security authentication, dynamic networking, command broadcasting to log management, each link is closely connected to form a complete wireless debugging closed loop, systematically improving the efficiency and security of charging pile operation and maintenance.
[0061] 13. Through wireless networking, multiple security mechanisms, batch synchronization operations, and automated maintenance, it solves the problems of traditional charging pile debugging such as dependence on wired connections, low efficiency, and insufficient security, and is especially suitable for the rapid deployment and operation and maintenance of large-scale charging pile groups.
[0062] 14. The networking instruction only needs to carry the network frequency band, the first sending time, and the first hash value, without complex configuration parameters, reducing the networking protocol overhead, adapting to charging piles with limited resources, and effectively improving the networking efficiency.
[0063] 15. Wireless debugging reduces the need for on-site manual intervention (such as eliminating the need for individual wiring), and is especially suitable for widely distributed charging pile groups, significantly saving manpower, time, and travel costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0064] The present invention will be further described below with reference to the accompanying drawings in conjunction with embodiments.
[0065] Figure 1 It is a flowchart of a method for wireless debugging of a charging pile according to the present invention.
[0066] Figure 2 It is a schematic structural diagram of a wireless debugging system for a charging pile according to the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0067] The overall idea of the technical solution in the embodiments of the present application is as follows: The debugging terminal connects to the serial port of the charging pile through a wireless serial port adapter for debugging, eliminating the need for traditional interface plugging and unplugging operations. Each charging pile forms a local area network, and the debugging instructions are broadcast within the local area network to perform batch debugging operations on each charging pile. Moreover, security measures are taken for the networking instructions, debugging instructions, and debugging logs to prevent data from being tampered with or stolen in plaintext, thereby improving the debugging efficiency and security of the charging pile.
[0068] Please refer to Figures 1 to 2 As shown, a preferred embodiment of a method for wireless debugging of a charging pile according to the present invention includes the following steps:
[0069] Step S10: The debugging terminal establishes a wireless connection with one of the charging piles through the wireless serial port adapter of the charging pile and performs two-way authentication with the charging pile;
[0070] By supporting various wireless modules such as 4G / 5G / NB-IoT / LoRa / WiFi / Bluetooth / ZigBee, it adapts to the network coverage requirements of different scenarios, gets rid of the dependence on physical interfaces and cables in traditional wired debugging, and improves the deployment efficiency; establishing an initial connection through the wireless serial port adapter reduces the rigid requirements for the physical location of the charging pile, facilitating debugging in remote or complex environments.
[0071] Step S20: The debugging terminal sends a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage range;
[0072] After the debugging terminal is connected to a single charging pile, it quickly forms a local area network, and all the charging piles within the coverage range automatically join the network, realizing unified debugging management of the charging piles and significantly improving the multi-node debugging efficiency.
[0073] Step S30: The debugging terminal sends a debugging instruction to the charging pile. After verifying the received debugging instruction, the charging pile broadcasts the debugging instruction within the local area network;
[0074] Step S40: Each charging pile that receives the debugging instruction performs a firmware version verification;
[0075] When a charging pile receives a debugging instruction, it first performs a firmware version verification. If there is an updated firmware, it first executes the upgrade operation. The discovered BUGs can be repaired through firmware upgrade, reducing the debugging threshold and further improving the debugging efficiency of the charging pile.
[0076] Step S50: Each charging pile synchronously executes a debugging operation based on the debugging task carried in the debugging instruction. During the debugging process, the debugging progress is broadcast through a speaker, and after the debugging is completed, the debugging result is fed back to the debugging terminal;
[0077] By broadcasting the debugging progress through a speaker and providing real-time feedback on the operation status, it is convenient for on-site personnel to monitor and improves the visualization and user experience of the debugging process.
[0078] Step S60: The debugging terminal records a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log into an encrypted log, and backs up the encrypted log to the server.
[0079] By recording a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result and backing it up to the server, it is convenient for later traceability and subsequent problem analysis and responsibility definition.
[0080] From wireless connection, security authentication, dynamic networking, instruction broadcasting to log management, each link is closely connected to form a complete wireless debugging closed loop, systematically improving the efficiency and security of charging pile operation and maintenance.
[0081] Through wireless networking, multiple security mechanisms, batch synchronous operations, and automated maintenance, it solves the problems of traditional charging pile debugging relying on wired connections, low efficiency, and insufficient security, and is especially suitable for the rapid deployment and operation and maintenance of large-scale charging pile groups.
[0082] Wireless debugging reduces the need for on-site manual intervention (such as no need to connect wires one by one), is especially suitable for widely distributed charging pile groups, and significantly saves labor, time, and travel costs.
[0083] Furthermore, the specific steps of Step S10 include:
[0084] Step S11: The debugging terminal connects to the wireless serial port adapter of one of the charging piles through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a Wi-Fi communication module, a Bluetooth communication module, or a ZigBee communication module, and then establishes a wireless connection with the charging pile;
[0085] By connecting to the wireless serial port adapter of the charging pile through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a Wi-Fi communication module, a Bluetooth communication module, or a ZigBee communication module, and then establishing a wireless connection with the charging pile, that is, establishing a connection with the charging pile through multi-mode communication, the communication module with the best signal strength can be selected as needed, thus greatly improving the stability of the wireless connection, and further greatly improving the stability of the charging pile debugging.
[0086] Step S12: The debugging terminal presets a root certificate, a terminal working certificate, and a first terminal private key, and the charging pile presets a root certificate, a charging pile working certificate, and a charging pile private key; the root certificate carries a root public key; the terminal working certificate is obtained by signing the first terminal public key with the root private key; the charging pile working certificate is obtained by signing the charging pile public key with the root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm; the charging pile private key and the charging pile public key are a pair of keys generated by the RSA algorithm;
[0087] Step S13: The debugging terminal and the charging pile perform mutual authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate, and the charging pile private key.
[0088] By presetting a root certificate, a terminal working certificate, and a first terminal private key in the debugging terminal, and presetting a root certificate, a charging pile working certificate, and a charging pile private key in the charging pile; the debugging terminal and the charging pile perform mutual authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate, and the charging pile private key. The authentication process adopts at least six security measures (terminal working certificate verification, charging pile working certificate verification, first signature data verification, second signature data verification, first verification value verification, time stamp timeliness verification), and the first signature data verification, the second signature data verification, and the first verification value verification are all generated based on multiple keys, increasing the cracking difficulty and preventing illegal terminals from controlling the charging pile, thus greatly improving the security of the charging pile debugging.
[0089] The specific steps of step S13 include:
[0090] Step S131: The debugging terminal generates a first random number through a random number generator, obtains the current first timestamp, generates a first instruction based on the first random number, the terminal working certificate, and the first timestamp, and sends the first instruction to the charging pile.
[0091] Step S132: After verifying the first instruction, the charging pile extracts the first terminal public key from the terminal working certificate carried in the first instruction, generates a second random number through a random number generator, signs the first random number with the charging pile private key to obtain the first signature data, obtains the current second timestamp, generates a second instruction based on the first signature data, the charging pile working certificate, the second random number, and the second timestamp, and sends the second instruction to the debugging terminal.
[0092] Step S133: After verifying the second instruction, the debugging terminal extracts the charging pile public key from the charging pile working certificate carried in the second instruction, verifies the first signature data with the charging pile public key, creates a second terminal private key and a second terminal public key based on the RSA algorithm, signs the second terminal public key and the second random number with the first terminal private key to obtain the second signature data, obtains the current third timestamp, generates a third instruction based on the second signature data, the second terminal public key, and the third timestamp, and sends the third instruction to the charging pile.
[0093] Step S134: After verifying the third instruction, the charging pile generates a session key, encrypts the session key with the second terminal public key to obtain ciphertext data, and calculates the first verification value of the session key.
[0094] Step S135: The charging pile signs the ciphertext data and the first verification value with the charging pile private key to obtain the third signature data, obtains the current fourth timestamp, generates a fourth instruction based on the ciphertext data, the first verification value, the third signature data, and the fourth timestamp, and sends the fourth instruction to the debugging terminal.
[0095] Step S136: After verifying the fourth instruction, the debugging terminal decrypts the ciphertext data carried in the fourth instruction to obtain the session key, and calculates the second verification value of the session key.
[0096] Step S137: After verifying the first verification value with the second verification value, the debugging terminal completes the mutual authentication between the debugging terminal and the charging pile.
[0097] The specific steps of S132 are as follows: The charging pile receives the first instruction in real time, parses the first instruction to obtain a first random number, a terminal working certificate, and a first timestamp. After performing a timeliness check through the first timestamp, it extracts the root public key from the root certificate, verifies the signature of the terminal working certificate through the root public key, extracts the first terminal public key from the public key modulus field in the terminal working certificate, generates a second random number through a random number generator, signs the first random number with the private key of the charging pile to obtain first signature data, obtains the current second timestamp, generates a second instruction based on the first signature data, the charging pile working certificate, the second random number, and the second timestamp, and sends the second instruction to the debugging terminal in real time.
[0098] Further, the specific steps of S20 are as follows:
[0099] The debugging terminal sends a networking instruction to the connected charging pile, which at least carries a network frequency band, a first sending time, and a first hash value. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time;
[0100] By sending a networking instruction to the connected charging pile through the debugging terminal, which at least carries a network frequency band, a first sending time, and a first hash value. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time; Subsequently, integrity verification can be performed through the first hash value, and timeliness verification can be performed through the first sending time to avoid executing illegal networking instructions, thereby greatly improving the security of charging pile networking.
[0101] The networking instruction only needs to carry a network frequency band, a first sending time, and a first hash value, without complex configuration parameters, reducing the networking protocol overhead, adapting to charging piles with limited resources, and effectively improving the networking efficiency.
[0102] The charging pile parses the received networking instruction to obtain a network frequency band, a first sending time, and a first hash value. After performing integrity verification on the network frequency band and the first sending time through the first hash value, it performs timeliness verification through the first sending time, and then forms a local area network with all charging piles within the wireless signal coverage range based on the network frequency band.
[0103] Further, the specific steps of S30 are as follows:
[0104] The debugging terminal sends a debugging instruction to the charging pile, which at least carries ciphertext data, a second sending time, and a second hash value. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is obtained by encrypting the debugging task, the latest firmware version number, and the firmware download URL through the RC6 algorithm and the 3DES algorithm;
[0105] Send a debugging instruction to the charging pile through the debugging terminal, which at least carries ciphertext data, the second sending time, and the second hash value. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is encrypted by using the RC6 algorithm and the 3DES algorithm on the debugging task, the latest firmware version number, and the firmware download URL. Subsequently, integrity verification can be performed through the second hash value, timeliness verification can be performed through the second sending time, and the debugging task, the latest firmware version number, and the firmware download URL are double-encrypted by using the RC6 algorithm and the 3DES algorithm to prevent the data from being stolen in plaintext, thereby greatly improving the security of the transmission of the debugging instruction.
[0106] The charging pile parses the received debugging instruction to obtain the ciphertext data, the second sending time, and the second hash value. After performing integrity verification on the ciphertext data and the second sending time through the second hash value, timeliness verification is performed through the second sending time, and then the debugging instruction is broadcast within the local area network.
[0107] The specific step S40 is as follows:
[0108] Each charging pile that receives the debugging instruction parses the debugging instruction to obtain the ciphertext data, decrypts the ciphertext data by using the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number, and the firmware download URL, verifies the local firmware version through the latest firmware version number, and if an upgrade is required, downloads the latest firmware through the firmware download URL to perform the upgrade operation.
[0109] Further, the specific step S60 is as follows:
[0110] The debugging terminal records the debugging log that at least includes the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log by using the SM4 algorithm to obtain a first-layer encrypted text, generates a 16-bit random string, inserts the random string into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text, encrypts the second-layer encrypted text into a third-layer encrypted text by using the IDEA algorithm, swaps the number 0 and the letter O, the number 1 and the letter L, and the number 5 and the letter S in the third-layer encrypted text to obtain a fourth-layer encrypted text, encrypts the fourth-layer encrypted text by using the ECDSA algorithm to obtain the encrypted log, and backs up the encrypted log to the server.
[0111] The debug log is encrypted by the SM4 algorithm to obtain a first-layer encrypted text. A 16-bit random string is generated and inserted into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. The second-layer encrypted text is encrypted into a third-layer encrypted text by the IDEA algorithm. The numbers 0 and the letter O, the numbers 1 and the letter L, and the numbers 5 and the letter S in the third-layer encrypted text are swapped to obtain a fourth-layer encrypted text. The fourth-layer encrypted text is encrypted by the ECDSA algorithm to obtain an encrypted log, and the encrypted log is backed up to the server. That is, the encryption process of the debug log combines triple encryption (symmetric encryption of the SM4 algorithm, symmetric encryption of the IDEA algorithm, and asymmetric encryption of the ECDSA algorithm) and second-order data transformation (random string insertion, character replacement). Inserting a random string can improve the ability to resist replay attacks. Combining the national cryptography algorithm and the international standard algorithm forms a hybrid encryption system. The final encrypted log requires knowledge of both the encryption algorithm and the data transformation rules to decrypt, thus greatly improving the security of the debug log storage.
[0112] A preferred embodiment of a wireless debugging system for a charging pile according to the present invention includes the following modules:
[0113] A wireless connection module for a debugging terminal to establish a wireless connection with one of the charging piles through a wireless serial port adapter of the charging pile and perform two-way authentication with the charging pile;
[0114] By supporting multiple wireless modules such as 4G / 5G / NB-IoT / LoRa / WiFi / Bluetooth / ZigBee, it can adapt to the network coverage requirements of different scenarios, get rid of the dependence on physical interfaces and cables for traditional wired debugging, and improve the deployment efficiency. An initial connection is established through a wireless serial port adapter, reducing the strict requirements for the physical location of the charging pile and facilitating debugging in remote or complex environments.
[0115] A local area network formation module for the debugging terminal to send a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage range;
[0116] After the debugging terminal is connected to a single charging pile, a local area network is quickly formed, and all the charging piles within the coverage range automatically join the network, realizing unified debugging management of the charging piles and significantly improving the multi-node debugging efficiency.
[0117] A debugging instruction broadcasting module for the debugging terminal to send a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, it broadcasts the debugging instruction within the local area network;
[0118] A firmware version verification module for each charging pile receiving the debugging instruction to perform firmware version verification;
[0119] When a debugging instruction is received through the charging pile, first perform a firmware version check. If there is an updated firmware, first execute the upgrade operation. BUGs found can be repaired through firmware upgrade, reducing the debugging threshold and further improving the debugging efficiency of the charging pile.
[0120] A batch debugging module is used for each charging pile to synchronously execute debugging operations based on the debugging tasks carried in the debugging instruction. During the debugging process, the debugging progress is broadcast through a speaker, and the debugging result is fed back to the debugging terminal after the debugging is completed.
[0121] The debugging progress is broadcast through a speaker, and the operation status is fed back in real time, facilitating on-site personnel to monitor and improving the visualization and user experience of the debugging process.
[0122] A debugging log management module is used for the debugging terminal to record debugging logs including at least debugging time, debugging terminal number, charging pile number, and debugging result, encrypt the debugging logs into encrypted logs, and back up the encrypted logs to the server.
[0123] By recording debugging logs including at least debugging time, debugging terminal number, charging pile number, and debugging result and backing them up to the server, it is convenient for later traceability, subsequent problem analysis, and responsibility definition.
[0124] From wireless connection, security authentication, dynamic networking, instruction broadcasting to log management, each link is closely connected to form a complete wireless debugging closed loop, systematically improving the efficiency and security of charging pile operation and maintenance.
[0125] Through wireless networking, multiple security mechanisms, batch synchronization operations, and automated maintenance, problems such as the dependence on wired connections, low efficiency, and insufficient security in traditional charging pile debugging are solved, especially suitable for the rapid deployment and operation and maintenance of large-scale charging pile groups.
[0126] Wireless debugging reduces the need for manual on-site intervention (such as no need to connect wires one by one), especially suitable for widely distributed charging pile groups, significantly saving manpower, time, and travel costs.
[0127] Furthermore, the wireless connection module specifically includes:
[0128] A charging pile connection unit is used for the debugging terminal to connect to the wireless serial port adapter of one of the charging piles through a 4G communication module, 5G communication module, NB-IOT communication module, LORA communication module, WIFI communication module, Bluetooth communication module, or ZigBee communication module, and then establish a wireless connection with the charging pile.
[0129] Connect to the wireless serial adapter of the charging pile through a 4G communication module, 5G communication module, NB-IOT communication module, LORA communication module, WIFI communication module, Bluetooth communication module or ZigBee communication module, and then establish a wireless connection with the charging pile. That is, establish a connection with the charging pile through multi-mode communication. The communication module with the best signal strength can be selected as needed, which greatly improves the stability of the wireless connection and thus greatly improves the stability of the charging pile debugging.
[0130] The key preset unit is used to preset the root certificate, terminal working certificate and first terminal private key for the debugging terminal, and the root certificate, charging pile working certificate and charging pile private key for the charging pile; the root certificate carries the root public key; the terminal working certificate is obtained by signing the first terminal public key with the root private key; the charging pile working certificate is obtained by signing the charging pile public key with the root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm; the charging pile private key and the charging pile public key are a pair of keys generated by the RSA algorithm;
[0131] The two-way authentication unit is used for the debugging terminal and the charging pile to perform two-way authentication through the root certificate, terminal working certificate, first terminal private key, charging pile working certificate and charging pile private key.
[0132] By presetting the root certificate, terminal working certificate and first terminal private key in the debugging terminal, and presetting the root certificate, charging pile working certificate and charging pile private key in the charging pile; the debugging terminal and the charging pile perform two-way authentication through the root certificate, terminal working certificate, first terminal private key, charging pile working certificate and charging pile private key. The authentication process adopts at least 6 security measures (terminal working certificate verification, charging pile working certificate verification, first signature data verification, second signature data verification, first verification value verification, time stamp timeliness verification), and the first signature data verification, second signature data verification and first verification value verification are all generated based on multiple keys, increasing the cracking difficulty and preventing illegal terminals from controlling the charging pile, thus greatly improving the security of the charging pile debugging.
[0133] The two-way authentication unit specifically includes:
[0134] The first instruction sending sub-unit is used for the debugging terminal to generate a first random number through a random number generator, obtain the current first time stamp, generate a first instruction based on the first random number, terminal working certificate and first time stamp, and send the first instruction to the charging pile;
[0135] The second instruction sending subunit is configured to, after the charging pile verifies the first instruction, extract the first terminal public key from the terminal working certificate carried in the first instruction, generate a second random number through a random number generator, sign the first random number with the private key of the charging pile to obtain first signature data, acquire the current second timestamp, generate a second instruction based on the first signature data, the charging pile working certificate, the second random number, and the second timestamp, and send the second instruction to the debugging terminal;
[0136] The third instruction sending subunit is configured to, after the debugging terminal verifies the second instruction, extract the public key of the charging pile from the charging pile working certificate carried in the second instruction, verify the first signature data with the public key of the charging pile, create a second terminal private key and a second terminal public key based on the RSA algorithm, sign the second terminal public key and the second random number with the first terminal private key to obtain second signature data, acquire the current third timestamp, generate a third instruction based on the second signature data, the second terminal public key, and the third timestamp, and send the third instruction to the charging pile;
[0137] The first check value generating subunit is configured to, after the charging pile verifies the third instruction, generate a session key, encrypt the session key with the second terminal public key to obtain ciphertext data, and calculate the first check value of the session key;
[0138] The fourth instruction sending subunit is configured to, sign the ciphertext data and the first check value with the private key of the charging pile to obtain third signature data, acquire the current fourth timestamp, generate a fourth instruction based on the ciphertext data, the first check value, the third signature data, and the fourth timestamp, and send the fourth instruction to the debugging terminal;
[0139] The second check value generating subunit is configured to, after the debugging terminal verifies the fourth instruction, decrypt the ciphertext data carried in the fourth instruction to obtain the session key, and calculate the second check value of the session key;
[0140] The check value comparison subunit is configured to, after the debugging terminal verifies the first check value with the second check value, complete the mutual authentication between the debugging terminal and the charging pile.
[0141] The second instruction sending subunit is specifically configured to: The charging pile receives the first instruction in real time, parses the first instruction to obtain a first random number, a terminal working certificate, and a first timestamp. After performing a timeliness check through the first timestamp, it extracts the root public key from the root certificate, verifies the signature of the terminal working certificate through the root public key, extracts the first terminal public key from the public key modulus field in the terminal working certificate, generates a second random number through a random number generator, signs the first random number with the private key of the charging pile to obtain first signature data, obtains the current second timestamp, generates a second instruction based on the first signature data, the charging pile working certificate, the second random number, and the second timestamp, and sends the second instruction to the debugging terminal in real time.
[0142] Further, the local area network building module is specifically configured to:
[0143] The debugging terminal sends a networking instruction to the connected charging pile, which at least carries a network frequency band, a first sending time, and a first hash value. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time;
[0144] By the debugging terminal sending a networking instruction to the connected charging pile, which at least carries a network frequency band, a first sending time, and a first hash value. The first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time; Subsequently, integrity verification can be performed through the first hash value, and timeliness verification can be performed through the first sending time to avoid executing illegal networking instructions, thereby greatly improving the security of the charging pile networking.
[0145] The networking instruction only needs to carry a network frequency band, a first sending time, and a first hash value, without complex configuration parameters, reducing the networking protocol overhead, adapting to charging piles with limited resources, and effectively improving the networking efficiency.
[0146] The charging pile parses the received networking instruction to obtain a network frequency band, a first sending time, and a first hash value. After performing integrity verification on the network frequency band and the first sending time through the first hash value, it performs timeliness verification through the first sending time, and then builds a local area network based on the network frequency band and all charging piles within the wireless signal coverage range.
[0147] Further, the debugging instruction broadcasting module is specifically configured to:
[0148] The debugging terminal sends a debugging instruction to the charging pile, which at least carries ciphertext data, a second sending time, and a second hash value. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is obtained by encrypting the debugging task, the latest firmware version number, and the firmware download URL through the RC6 algorithm and the 3DES algorithm;
[0149] Send a debugging instruction carrying at least ciphertext data, a second sending time, and a second hash value to the charging pile through a debugging terminal. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is obtained by encrypting the debugging task, the latest firmware version number, and the firmware download URL through the RC6 algorithm and the 3DES algorithm. Subsequently, integrity verification can be performed through the second hash value, aging verification can be performed through the second sending time, and the debugging task, the latest firmware version number, and the firmware download URL are double-encrypted through the RC6 algorithm and the 3DES algorithm to prevent the data from being stolen in plaintext, thereby greatly improving the security of the transmission of the debugging instruction.
[0150] The charging pile analyzes the received debugging instruction to obtain ciphertext data, a second sending time, and a second hash value. After performing integrity verification on the ciphertext data and the second sending time through the second hash value, aging verification is performed through the second sending time, and then the debugging instruction is broadcast within the local area network.
[0151] The firmware version verification module is specifically used for:
[0152] Each charging pile that receives the debugging instruction analyzes the debugging instruction to obtain ciphertext data, decrypts the ciphertext data through the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number, and the firmware download URL, verifies the local firmware version through the latest firmware version number, and if an upgrade is required, downloads the latest firmware through the firmware download URL to perform the upgrade operation.
[0153] Furthermore, the debugging log management module is specifically used for:
[0154] The debugging terminal records a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result. Encrypt the debugging log through the SM4 algorithm to obtain a first-layer encrypted text, generate a 16-bit random string, insert the random string into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text, encrypt the second-layer encrypted text into a third-layer encrypted text through the IDEA algorithm, swap the number 0 and the letter O, the number 1 and the letter L, and the number 5 and the letter S in the third-layer encrypted text to obtain a fourth-layer encrypted text, encrypt the fourth-layer encrypted text through the ECDSA algorithm to obtain an encrypted log, and back up the encrypted log to the server.
[0155] The debugging log is encrypted by the SM4 algorithm to obtain a first-layer encrypted text. A 16-bit random string is generated and inserted into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. The second-layer encrypted text is encrypted into a third-layer encrypted text by the IDEA algorithm. The numbers 0 and the letter O, the numbers 1 and the letter L, and the numbers 5 and the letter S in the third-layer encrypted text are swapped to obtain a fourth-layer encrypted text. The fourth-layer encrypted text is encrypted by the ECDSA algorithm to obtain an encrypted log, and the encrypted log is backed up to the server. That is, the encryption process of the debugging log combines triple encryption (symmetric encryption of the SM4 algorithm, symmetric encryption of the IDEA algorithm, and asymmetric encryption of the ECDSA algorithm) and second-order data transformation (random string insertion, character replacement). The ability to resist replay attacks can be improved by inserting a random string. A hybrid encryption system is formed by combining national cryptographic algorithms and international standard algorithms. The final encrypted log requires knowledge of both the encryption algorithm and the data transformation rules to decrypt, thereby greatly enhancing the security of the debugging log storage.
[0156] In summary, the advantages of the present invention are as follows:
[0157] 1. The debugging terminal uses a wireless serial adapter to establish a wireless connection with the charging pile and performs two-way authentication with the charging pile. The debugging terminal sends a networking instruction to the connected charging pile to form a local area network with all charging piles within the wireless signal coverage. Then, the debugging terminal sends a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, it broadcasts the debugging instruction within the local area network. Each charging pile that receives the debugging instruction performs a firmware version verification and synchronously executes a debugging operation based on the debugging task carried in the debugging instruction. During the debugging process, the debugging progress is announced through a speaker, and the debugging result is fed back to the debugging terminal after the debugging is completed. The debugging terminal records the debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log into an encrypted log, and backs it up to the server. That is, the debugging terminal connects to the serial port of the charging pile through a wireless serial adapter for debugging, eliminating the need for the traditional plugging and unplugging operation of the interface. Each charging pile forms a local area network, and the debugging instruction is broadcast within the local area network to perform a batch debugging operation on each charging pile. Moreover, security measures are taken for the networking instruction, the debugging instruction, and the debugging log to prevent data from being tampered with or stolen in plaintext, thereby greatly improving the charging pile debugging efficiency and security.
[0158] 2. When the charging pile receives the debugging instruction, it first performs a firmware version verification. If there is an updated firmware, it first executes the upgrade operation. The discovered BUGs can be repaired through firmware upgrade, reducing the debugging threshold and further improving the charging pile debugging efficiency.
[0159] 3. By recording the debugging log that includes at least the debugging time, debugging terminal number, charging pile number, and debugging result and backing it up to the server, it is convenient for later traceability, subsequent problem analysis, and responsibility definition.
[0160] 4. Through a 4G communication module, 5G communication module, NB-IOT communication module, LORA communication module, WIFI communication module, Bluetooth communication module, or ZigBee communication module, connect to the wireless serial port adapter of the charging pile, and then establish a wireless connection with the charging pile, that is, establish a connection with the charging pile through multi-mode communication. The communication module with the best signal strength can be selected as needed, which greatly improves the stability of the wireless connection, and further greatly improves the stability of the charging pile debugging.
[0161] 5. By presetting the root certificate, terminal working certificate, and the first terminal private key on the debugging terminal, and presetting the root certificate, charging pile working certificate, and charging pile private key on the charging pile; the debugging terminal and the charging pile perform two-way authentication through the root certificate, terminal working certificate, the first terminal private key, charging pile working certificate, and charging pile private key. The authentication process takes at least 6 security measures (terminal working certificate verification, charging pile working certificate verification, first signature data verification, second signature data verification, first check value verification, timestamp timeliness verification), and the first signature data verification, second signature data verification, and first check value verification are all generated based on multiple keys, increasing the difficulty of cracking and preventing illegal terminals from controlling the charging pile, thereby greatly improving the security of the charging pile debugging.
[0162] 6. By sending a networking instruction carrying at least the network band, the first sending time, and the first hash value to the connected charging pile by the debugging terminal. The first hash value is obtained by performing a hash calculation on the network band and the first sending time; subsequent integrity verification can be performed through the first hash value, and timeliness verification can be performed through the first sending time to avoid executing illegal networking instructions, thereby greatly improving the security of the charging pile networking.
[0163] 7. By sending a debugging instruction carrying at least ciphertext data, the second sending time, and the second hash value to the charging pile by the debugging terminal. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is encrypted by the RC6 algorithm and 3DES algorithm for the debugging task, the latest firmware version number, and the firmware download URL; subsequent integrity verification can be performed through the second hash value, timeliness verification can be performed through the second sending time, and the debugging task, the latest firmware version number, and the firmware download URL are double-encrypted by the RC6 algorithm and 3DES algorithm to avoid the plaintext theft of data, thereby greatly improving the security of the debugging instruction transmission.
[0164] 8. Encrypt the debug log through the SM4 algorithm to obtain a first-layer encrypted text. Generate a 16-bit random string, and insert the random string into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. Encrypt the second-layer encrypted text into a third-layer encrypted text through the IDEA algorithm. Swap the digit 0 and the letter O, the digit 1 and the letter L, and the digit 5 and the letter S in the third-layer encrypted text to obtain a fourth-layer encrypted text. Encrypt the fourth-layer encrypted text through the ECDSA algorithm to obtain an encrypted log, and back up the encrypted log to the server. That is, the encryption process of the debug log combines triple encryption (symmetric encryption of the SM4 algorithm, symmetric encryption of the IDEA algorithm, and asymmetric encryption of the ECDSA algorithm) and second-order data transformation (random string insertion, character replacement). Inserting a random string can enhance the ability to resist replay attacks. Combining national cryptographic algorithms with international standard algorithms forms a hybrid encryption system. The final encrypted log requires knowledge of both the encryption algorithm and the data transformation rules to decrypt, thereby greatly enhancing the security of debug log storage.
[0165] 9. Support multiple wireless modules such as 4G / 5G / NB-IoT / LoRa / WiFi / Bluetooth / ZigBee, adapt to the network coverage requirements of different scenarios, get rid of the dependence on physical interfaces and cables for traditional wired debugging, and improve the deployment efficiency. Establish an initial connection through a wireless serial adapter, reduce the rigid requirements for the physical location of the charging pile, and facilitate debugging in remote or complex environments.
[0166] 10. After the debugging terminal is connected to a single charging pile, quickly form a local area network, and all charging piles within the coverage area automatically connect to the network to achieve unified debugging management of the charging piles, significantly improving the multi-node debugging efficiency.
[0167] 11. Broadcast the debugging progress through a speaker, and provide real-time feedback on the operation status, which is convenient for on-site personnel to monitor and improves the visualization and user experience of the debugging process.
[0168] 12. From wireless connection, security authentication, dynamic networking, instruction broadcasting to log management, all links are closely connected to form a complete wireless debugging closed loop, systematically improving the efficiency and security of charging pile operation and maintenance.
[0169] 13. Through wireless networking, multiple security mechanisms, batch synchronization operations, and automated maintenance, it solves the problems of traditional charging pile debugging, such as dependence on wired connections, low efficiency, and insufficient security. It is especially suitable for the rapid deployment and operation and maintenance of large-scale charging pile groups.
[0170] 14. The networking instruction only needs to carry the network frequency band, the first sending time, and the first hash value, without complex configuration parameters, reducing the networking protocol overhead, adapting to charging piles with limited resources, and effectively improving the networking efficiency.
[0171] 15. Wireless debugging reduces the need for manual on-site intervention (such as eliminating the need for individual wiring), and is particularly suitable for widely distributed charging pile groups, significantly saving manpower, time and travel costs.
[0172] Although the specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments we described are illustrative rather than used to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered by the scope of protection of the claims of the present invention.
Claims
1. A wireless debugging method for a charging pile, characterized in that: It includes the following steps: Step S10: The debugging terminal establishes a wireless connection with one of the charging piles through the wireless serial port adapter of the charging pile and conducts two-way authentication with the charging pile; Step S20: The debugging terminal sends a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage; Step S30: The debugging terminal sends a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, it broadcasts the debugging instruction within the local area network; Step S40: Each charging pile that receives the debugging instruction conducts a firmware version verification; Step S50: Each charging pile synchronously executes a debugging operation based on the debugging task carried by the debugging instruction. During the debugging process, the debugging progress is announced through a speaker, and after the debugging is completed, the debugging result is fed back to the debugging terminal; Step S60: The debugging terminal records a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypts the debugging log into an encrypted log, and backs up the encrypted log to the server.
2. The wireless debugging method of a charging pile according to claim 1, characterized in that: The specific content of step S10 includes: Step S11: The debugging terminal connects to the wireless serial port adapter of one of the charging piles through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a Wi-Fi communication module, a Bluetooth communication module, or a ZigBee communication module, and then establishes a wireless connection with the charging pile; Step S12: The debugging terminal presets a root certificate, a terminal working certificate, and a first terminal private key, and the charging pile presets a root certificate, a charging pile working certificate, and a charging pile private key; the root certificate carries a root public key; the terminal working certificate is obtained by signing the first terminal public key with the root private key; the charging pile working certificate is obtained by signing the charging pile public key with the root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm; Step S13: The debugging terminal and the charging pile conduct two-way authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate, and the charging pile private key.
3. A wireless debugging method for a charging pile according to claim 1, characterized in that: The specific content of step S20 is: The debugging terminal sends a networking instruction carrying at least a network frequency band, a first sending time, and a first hash value to the connected charging pile, and the first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time; The charging pile analyzes the received networking instruction to obtain the network frequency band, the first sending time, and the first hash value. After performing an integrity verification on the network frequency band and the first sending time through the first hash value, it conducts a timeliness verification through the first sending time, and then forms a local area network with all the charging piles within the wireless signal coverage based on the network frequency band.
4. The wireless debugging method of a charging pile according to claim 1, wherein: The specific content of step S30 is: The debugging terminal sends a debugging instruction carrying at least ciphertext data, a second sending time, and a second hash value to the charging pile. The second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time. The ciphertext data is obtained by encrypting the debugging task, the latest firmware version number, and the firmware download URL through the RC6 algorithm and the 3DES algorithm; The charging pile parses the received debugging instruction to obtain the ciphertext data, the second sending time, and the second hash value. After performing an integrity check on the ciphertext data and the second sending time through the second hash value, a timeliness check is performed through the second sending time, and then the debugging instruction is broadcast within the local area network; The specific step S40 is as follows: Each charging pile that receives the debugging instruction parses the debugging instruction to obtain the ciphertext data, decrypts the ciphertext data through the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number, and the firmware download URL, and checks the local firmware version through the latest firmware version number. If an upgrade is required, the latest firmware is downloaded through the firmware download URL to perform the upgrade operation.
5. A wireless debugging method for a charging pile according to claim 1, characterized in that: The specific step S60 is as follows: The debugging terminal records a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result. The debugging log is encrypted through the SM4 algorithm to obtain a first-layer encrypted text. A 16-bit random string is generated, and the random string is inserted into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. The second-layer encrypted text is encrypted into a third-layer encrypted text through the IDEA algorithm. The numbers 0 and the letter O in the third-layer encrypted text are swapped, the numbers 1 and the letter L are swapped, and the numbers 5 and the letter S are swapped to obtain a fourth-layer encrypted text. The fourth-layer encrypted text is encrypted through the ECDSA algorithm to obtain an encrypted log, and the encrypted log is backed up to the server.
6. A wireless debugging system for a charging pile, characterized in that: It includes the following modules: A wireless connection module, which is used for the debugging terminal to establish a wireless connection with one of the charging piles through the wireless serial port adapter of the charging pile and perform two-way authentication with the charging pile; A local area network formation module, which is used for the debugging terminal to send a networking instruction to the connected charging pile to form a local area network with all the charging piles within the wireless signal coverage range; A debugging instruction broadcast module, which is used for the debugging terminal to send a debugging instruction to the charging pile. After the charging pile verifies the received debugging instruction, the debugging instruction is broadcast within the local area network; A firmware version verification module, which is used for each charging pile that receives the debugging instruction to perform a firmware version verification; A batch debugging module, which is used for each charging pile to synchronously execute debugging operations based on the debugging task carried in the debugging instruction. During the debugging process, the debugging progress is broadcast through a speaker, and the debugging result is fed back to the debugging terminal after the debugging is completed; A debugging log management module, which is used for the debugging terminal to record a debugging log including at least the debugging time, the debugging terminal number, the charging pile number, and the debugging result, encrypt the debugging log into an encrypted log, and back up the encrypted log to the server.
7. The wireless debugging system for a charging pile according to claim 6, wherein: The wireless connection module specifically includes: The charging pile connection unit is used for the debugging terminal to connect to the wireless serial port adapter of one of the charging piles through a 4G communication module, a 5G communication module, an NB-IoT communication module, a LoRa communication module, a WIFI communication module, a Bluetooth communication module or a ZigBee communication module, and then establish a wireless connection with the charging pile; The key preset unit is used for the debugging terminal to preset a root certificate, a terminal working certificate and a first terminal private key, and the charging pile to preset a root certificate, a charging pile working certificate and a charging pile private key; the root certificate carries a root public key; the terminal working certificate is obtained by signing the first terminal public key with the root private key; the charging pile working certificate is obtained by signing the charging pile public key with the root private key; the first terminal private key and the first terminal public key are a pair of keys generated by the RSA algorithm; the root private key and the root public key are a pair of keys generated by the RSA algorithm; The two-way authentication unit is used for the debugging terminal and the charging pile to perform two-way authentication through the root certificate, the terminal working certificate, the first terminal private key, the charging pile working certificate and the charging pile private key.
8. The wireless debugging system of a charging pile according to claim 6, characterized in that: The local area network building module is specifically used for: The debugging terminal sends a networking instruction to the connected charging pile, which at least carries a network frequency band, a first sending time and a first hash value, and the first hash value is obtained by performing a hash calculation on the network frequency band and the first sending time; The charging pile analyzes the received networking instruction to obtain the network frequency band, the first sending time and the first hash value. After performing an integrity check on the network frequency band and the first sending time through the first hash value, performs a timeliness check through the first sending time, and then forms a local area network with all the charging piles within the wireless signal coverage range based on the network frequency band.
9. The wireless debugging system for a charging pile according to claim 6, wherein: The debugging instruction broadcasting module is specifically used for: The debugging terminal sends a debugging instruction to the charging pile, which at least carries ciphertext data, a second sending time and a second hash value, and the second hash value is obtained by performing a hash calculation on the ciphertext data and the second sending time, and the ciphertext data is obtained by encrypting the debugging task, the latest firmware version number and the firmware download URL through the RC6 algorithm and the 3DES algorithm; The charging pile analyzes the received debugging instruction to obtain the ciphertext data, the second sending time and the second hash value. After performing an integrity check on the ciphertext data and the second sending time through the second hash value, performs a timeliness check through the second sending time, and then broadcasts the debugging instruction within the local area network; The firmware version verification module is specifically used for: Each charging pile that receives the debugging instruction analyzes the debugging instruction to obtain the ciphertext data, decrypts the ciphertext data through the RC6 algorithm and the 3DES algorithm to obtain the debugging task, the latest firmware version number and the firmware download URL, verifies the local firmware version through the latest firmware version number, and if an upgrade is required, downloads the latest firmware through the firmware download URL and executes the upgrade operation.
10. A wireless debugging system for a charging pile according to claim 6, characterized in that: The debugging log management module is specifically used for: The debugging terminal record includes at least the debugging time, the debugging terminal number, the charging pile number, and the debugging log of the debugging result. The debugging log is encrypted by the SM4 algorithm to obtain a first-layer encrypted text. A 16-bit random string is generated, and the random string is inserted into the head, middle, and tail of the first-layer encrypted text to obtain a second-layer encrypted text. The second-layer encrypted text is encrypted into a third-layer encrypted text by the IDEA algorithm. In the third-layer encrypted text, the number 0 and the letter O are swapped, the number 1 and the letter L are swapped, and the number 5 and the letter S are swapped to obtain a fourth-layer encrypted text. The fourth-layer encrypted text is encrypted by the ECDSA algorithm to obtain an encrypted log, and the encrypted log is backed up to the server.