OTA-based remote connection method and system, and vehicle-mounted connection device and electric vehicle

Abstract

The application provides an OTA-based remote connection method and system, a vehicle-mounted connection device and an electric vehicle. The OTA-based remote connection method is applied to a server end and comprises the following steps: 1) sending a communication request and a server end string to a device end; 2) receiving a device end password and a device end string fed back from the device end, and verifying the device end password; 3) generating a true or false server end password according to the verification result of the device end password, and sending the true or false server end password to the device end together with an updated server end string; 4) repeating the steps 2) to 3) for a first preset number of times, and updating the server end string and the device end string in each repetition; and 5) when the verification results of all the device end passwords are true, allowing the device end to be upgraded through OTA; otherwise, refusing to upgrade the device end through OTA. The scheme greatly improves the cracking difficulty and enhances the reliability of network communication security between the device end and the server end.

Description

Technical Field

[0001] This invention relates to the field of battery cell management applications, and in particular to an OTA-based remote connection method, system, vehicle connection device, and electric vehicle. Background Technology

[0002] Traditionally, automakers only have the opportunity to upgrade software via diagnostic tools during vehicle maintenance. This led to the development of Over-The-Air (OTA) technology. Compared to traditional automotive software system upgrades, OTA technology offers many conveniences; however, from an information security perspective, OTA has both advantages and disadvantages.

[0003] Its advantages include the ability to quickly fix system vulnerabilities, keep the system up-to-date, and ensure security throughout the system's lifecycle. This also reduces upgrade costs, aside from the development costs of the OTA system. However, vulnerabilities in a system will always be discovered through repeated verification. The reliability of a car's ECU system is crucial to driving safety, impacting the lives of drivers and passengers. Upgrades require extreme caution, ensuring both the security of the original installation program and the security of the transmission process. However, in recent years, OTA services, which control the lifeline of system updates, have been repeatedly exposed for security issues, threatening personal lives and property, and even the safety and stability of society as a whole.

[0004] Based on this, this invention is proposed. Summary of the Invention

[0005] This invention provides a safe and simple OTA-based remote connection method, system, vehicle connection device, and electric vehicle that can ensure the authenticity of the identities of the parties involved in the transmission process and has anti-hacking properties, in order to solve the technical problems mentioned above, such as the ease with which OTA upgrades can be cracked and the security risks from an information security perspective.

[0006] In a first aspect of the present invention, an OTA-based remote connection method is provided, applied to a server, comprising: 1) receiving a communication request and a server string from the server, and generating a device password based on the server string; 2) sending the device password and the device string to the server; 3) receiving the server password and the updated server string from the server, and verifying the server password; 4) generating a true or false device password based on the verification result of the server password, and repeating steps 2)-3) above a first preset number of times, wherein the server string and the device string are updated in each repetition; 5) when the verification result of all server passwords is true, OTA upgrade is allowed; otherwise, OTA upgrade is refused.

[0007] Optionally, in step 3), generating a true or false server-side password based on the verification result includes: when the verification result of the device-side password is true, matching the true server-side password corresponding to the device-side string from a preset mapping table using a lookup table method; when the device-side password is false, generating a false server-side password.

[0008] Optionally, the server-side string is randomly updated on the server side using a first true random number generator.

[0009] Optionally, generating a fake server-side password involves randomly generating a fake server-side password from a preset first database.

[0010] In a second aspect of the invention, an OTA-based remote connection method is also provided, applied to a device: 1) receiving a communication request and a server string from the server, and generating a device password based on the server string; 2) sending the device password and the device string to the server; 3) receiving the server password and the updated server string from the server, and verifying the server password; 4) generating a true or false device password based on the verification result of the server password, and repeating steps 2)-3) above a first preset number of times, wherein the server string and the device string are updated in each repetition; 5) when the verification result of all server passwords is true, OTA upgrade is allowed; otherwise, OTA upgrade is refused.

[0011] Optionally, in 4), generating a true or false device password includes: when the verification result of the server password is true, matching the true server password corresponding to the server string from a preset mapping table according to the lookup table method; when the verification result of the server password is false, generating a false device password.

[0012] Optionally, the device-side string is generated on the device side using a second true random number generator.

[0013] A third aspect of the present invention also provides an OTA-based remote connection method, comprising: 1) a server sending a communication request and a server string to a device; 2) the device receiving the communication request and the server string from the server and generating a device password mapped to the server string; 3) the device sending the device password and the device string to the server; 4) the server receiving the device password and the device string from the device and verifying the device password; 5) the server generating a true or false server password based on the verification result of the device password and sending it, along with the updated device string, to the device; 6) the device receiving the server password and the updated device string from the server and verifying the server password; 7) the device generating a true or false device password based on the verification result of the server password; 8) repeating steps 3)-7) above a first preset number of times, wherein the server string and the device string are updated in each repetition; 9) when the verification result of all device passwords is true, the server performing an OTA upgrade on the device; otherwise, the server not performing an OTA upgrade on the device.

[0014] In a fourth aspect, the present invention also provides an OTA-based remote connection system, comprising a server side including a first main control unit, the server side being configured with a first true random number generator and a second mapping table; and a device side including a second main control unit, the device side being configured with a second true random number generator and a first mapping table; wherein the first main control unit is configured to execute the remote connection method described above, and the second main control unit is configured to execute the remote connection method described above.

[0015] Additionally, an in-vehicle connectivity device is provided, comprising: a first true random number generator for generating server-side strings; and a first main control unit configured to execute the remote connection method applied to the device as described above.

[0016] An electric vehicle is also provided, including the vehicle connectivity device described above.

[0017] This invention provides an OTA-based remote connection method that uses cyclic verification between the device and server to grant communication permission based on the number of verifications. This enables communication handshake verification before the device is upgraded via OTA. Furthermore, both the device and server use true random number generators to generate true random numbers. Combined with a preset first mapping table and a second mapping table, this greatly increases the difficulty of cracking the method and enhances the reliability of network communication security between the device and server.

[0018] Other features and advantages of the embodiments of the present invention will be described in the following detailed description section. Attached Figure Description

[0019] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of the modules of the OTA-based remote connection system provided in an embodiment of the present invention;

[0021] Figure 2 A flowchart illustrating the OTA-based remote connection method provided in Embodiment 2 of the present invention is shown.

[0022] Figure 3 The flowchart of step S103 in the OTA-based remote connection method provided in Embodiment 2 of the present invention is shown; and

[0023] Figure 4 A flowchart of the OTA-based remote connection method provided in Embodiment 3 of the present invention is shown.

[0024] The components represented by each number in the above attached diagram are listed below:

[0025] 100. Remote connection system;

[0026] 10. Server-side; 20. Device-side;

[0027] 101. First main control unit; 202. Second main control unit;

[0028] 10a, First True Random Number Generator; 20a, Second True Random Number Generator;

[0029] 10b, First mapping table; 20b, Second mapping table. Detailed Implementation

[0030] To make the above and other features and advantages of the present invention clearer, the invention will be further described below with reference to the accompanying drawings. It should be understood that the specific embodiments given herein are for the purpose of explanation to those skilled in the art and are exemplary only, not restrictive.

[0031] Techniques, methods, and systems known to a person skilled in the art may not be discussed in detail, but where appropriate, they should be considered part of the license specification.

[0032] In existing technologies, automotive OTA services only perform simple encryption during transmission to ensure the confidentiality of transmitted information, but the information security during the initial handshake is not perfect. The solution of this invention aims to solve this problem.

[0033] Example 1

[0034] like Figure 1 As shown, Figure 1 This is a schematic diagram of a module of an OTA-based remote connection system 100 provided in an embodiment of the present invention. The system 100 includes:

[0035] The server 10 includes a first main control unit 101, which is configured with a first true random number generator 10a and a first mapping table 10b.

[0036] The device 20 includes a second main control unit 202, which is equipped with a second true random number generator 20a and a second mapping table 20b.

[0037] The server 10 can be a cloud server, and the device 20 can be an in-vehicle unit (such as a Tbox) with a communication module in an electric or fuel-powered vehicle. The server 10 and the device 20 establish a remote communication connection through a base station.

[0038] The first true random number generator 10a and the second true random number generator 20a automatically generate random strings (such as random numbers between 0 and 4294967295, or add character elements such as symbols, which are also called true random numbers, and can be configured according to the system requirements, i.e., the string can be letters, numbers, or symbols, or any combination thereof) by customizing the quantity, minimum value, maximum value, character format, etc. The first mapping table 10b and the second mapping table 20b both have preset mapping relationships between strings and passwords, such as string 1 corresponding to password 1, string 2 corresponding to password 2, string 3 corresponding to password 3, and so on.

[0039] Furthermore, the first main control unit 101 and the second main control unit 202 can be independently controlled on the server side 10 and the device side 20, respectively. That is, the server side 10 and the device side 20 each have their own main control unit, which can increase the difficulty of cracking compared to the single-end operation method.

[0040] It is understandable that, in practice, the OTA service platform, i.e., server 10, performs remote upgrades to the vehicle's onboard unit via OTA. Before sending the OTA upgrade package to device 20, it needs to authenticate the device (similarly, device 20 also needs to authenticate itself). Only after both devices have verified each other's identity—commonly referred to as a handshake before communication—and confirming the device's eligibility to upload OTA data, can the next step of communication interaction, such as uploading the OTA package, proceed. Therefore, this invention aims to provide a remote connection system that ensures a secure handshake before communication interaction, thereby reducing the risk of OTA handshake information being compromised.

[0041] To more clearly illustrate this scheme, the random number generated by the first true random number generator 10a on the server side 10 is defined as the "server-side string", the random number generated by the second true random number generator 20a on the device side 20 is defined as the "device-side string", the password mapped by the first mapping table 10b on the server side 10 is defined as the "server-side password", and the password mapped by the second mapping table 20b is defined as the "device-side password". That is, the first mapping table 10b on the server side 10 is a mapping table of device-side string and server-side password, and the second mapping table 20b on the device side 20 is a mapping table of server-side string and device-side password.

[0042] The first true random number generator 10a and the second true random number generator 20a may be the same or different. The first mapping table 10b and the second mapping table 20b may be the same or different, but the server 10 and the device 20 should know each other's mapping table data in order to determine whether the received password is correct.

[0043] It should be noted that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features.

[0044] Based on the above definition, in a general inventive concept, the OTA-based remote connection system includes the following control logic:

[0045] Step 1 (Initiating Handshake Request Phase): Server 10 sends a communication request and generates a server string, and sends the communication request and the server string to server 10 simultaneously or in task order;

[0046] In this embodiment of the invention, the party that initiates the communication request first is not limited. In some embodiments, the device 20 may initiate the communication request for the update first, generate a device string, and send the device string and the communication request to the server 10.

[0047] Step 2 (Handshake Verification Phase): After receiving the server-side string and communication request, device 20 matches the corresponding device-side password in the second mapping table 20b according to the server-side string, and generates a device-side string. It then sends the device-side password and device-side string to server 10. If the device-side password verification is successful, server 10 looks up the server-side password in the table based on the device-side string. If the device-side password verification fails, server 10 randomly generates a fake server-side password and a server-side string, and sends the server-side password and server-side string to device 20 again. Server 10 and device 20 continue to execute the same response, that is, server 10 and device 20 repeatedly send messages to each other for verification. The string is updated in each repetition, thus performing a cyclical verification between server 10 and device 20.

[0048] Step 2 can be understood as follows: Server 10 generates a server-side string and a true or false server-side password, while device 20 generates a device-side string and a true or false device-side password. The true server-side password or device-side password is obtained by looking up the first mapping table 10b and the second mapping table 20b, while the false device-side password and server-side password are randomly generated on their respective ends.

[0049] It is understandable that both the server-side 10 and the device-side 20 use true random number generators instead of software pseudo-random number generation programs, making it difficult for attackers to crack the true random numbers with software, thus increasing the system's security.

[0050] Step 3: When the server 10 (or device 20) receives a genuine device password (or server password) a first preset number of times, the handshake is successful, allowing communication between the server 10 and device 20. Conversely, when the server 10 (or device 20) receives a fake device password (or server password) a second preset number of times, the OTA function is locked, and the server 10 cannot perform OTA upgrades on the device 20.

[0051] It should be noted that step 3 is set to receive genuine device or server passwords consecutively for a preset number of times to prevent cracking through repeated attempts. The first and second preset number of attempts can be customized. The second preset number of attempts can be designed to be higher than the first preset number of attempts, such as 3 times for the first preset number and 10 times for the second preset number of attempts, to increase the difficulty of cracking.

[0052] It is understandable that by taking steps 2-3 above, the security of OTA downloads can be improved. Whether the verification on the server side 10 or the device side 20 is correct or incorrect, no error will be prompted or the handshake process will be terminated immediately. Instead, it will continue until the entire handshake process is completed. Since the handshake process between the server side 10 and the device side 20 is not terminated after the verification fails, the attacker cannot know which link the password has a problem, nor can they know at which step the real password appears. This greatly increases the difficulty of cracking and thus increases the connection security of OTA.

[0053] Based on the above overall inventive concept, the following is a specific system control strategy:

[0054] When the remote server 10 upgrades the system software of the device 20 via OTA, the system 100 performs the following steps:

[0055] S1. The server 10 first sends a communication request, and at the same time generates a server string a through the first true random number generator 10a located on the server 10, and sends the communication request and the device string a to the device 20.

[0056] S2. After receiving the communication request and the server string a, the device 20 uses the second mapping table 20b to look up the table using the preset mapping relationship to obtain the device password A corresponding to the server string a. At this time, the second true random number generator 20a of the device 20 generates the device string b and returns the device password A and the device string b together to the device 20.

[0057] S3. Server 10 receives device password A and device string b, and verifies the correctness of device password A, that is, checks whether it is the device password A corresponding to server string a. If the verification result is correct, the server 10 looks up the first mapping table 10b to obtain the real server password B corresponding to device string b. If the verification result is incorrect, a fake server password B' is randomly generated, and then the server string c is generated by the first true random number generator 10a. B or B', together with the server string c, is sent to device 20.

[0058] S4. Device 20 receives the server password B or B', along with the server string c, and verifies the correctness of password B or B' again. If the verification result is correct, it looks up the table to obtain the real device password C corresponding to the server string c; if the verification result is incorrect, it randomly generates a fake device password C', and then generates the device string d through the second true random number generator 20a. It then sends C or C', along with d, to the server 10.

[0059] S5. Server 10 verifies the correctness of password C or C'. If the verification result is correct, it looks up the table to get the real server password D corresponding to the device string d. If the verification result is incorrect, it randomly generates a fake server password D', then generates a server string e, and sends D or D' together with e to server 10.

[0060] S6. Device 20 verifies the correctness of password D or D'. If the verification result is correct, it looks up the table to get the real device password E corresponding to the server string e. If the verification result is incorrect, it randomly generates a fake device password E', and then generates a device string f. It sends E or E' together with f to server 10.

[0061] S7. Server 10 verifies the correctness of password E or E'. If the verification result is correct, it looks up the table to get the password F corresponding to the true random number f from device 20. If the verification result is incorrect, it randomly generates a fake server password F', then generates a server true random number g, and sends F or F' together with g to device 20.

[0062] S8. Device 20 re-verifies the correctness of password F or F'; if all the above rounds of verification are correct, the next operation is allowed; otherwise, a verification failure signal is sent and the handshake communication ends.

[0063] S9. If the handshake process fails to complete the verification, n attempts (n is a custom setting, greater than 2) are allowed. If all attempts fail, OTA updates and upgrades are prohibited. Professional personnel need to go to the device to unlock it on-site before the OTA function can be restored.

[0064] It should be noted that the number of rounds can be increased or decreased in S2 to S7. Decreasing the number of rounds can increase the response speed of the handshake between the server 10 and the device 20, while increasing the number of rounds can increase the difficulty of cracking. Any changes made to the number of rounds are within the scope of protection covered by the embodiments of this invention.

[0065] At the same time, the system limits the number of times the handshake verification fails, preventing attackers from repeatedly verifying and achieving brute-force attacks.

[0066] On the other hand, the server 10 and device 20 are controlled independently in this system, which increases security.

[0067] In summary, Embodiment 1 of the present invention provides an OTA-based remote connection system. Through cyclic verification between the server 10 and the device 20, communication interaction is permitted based on the number of verifications. This enables communication handshake verification before the device is upgraded via OTA. Furthermore, both the server 10 and the device 20 use true random number generators to generate true random numbers. Combined with the preset first and second mapping tables, this greatly increases the difficulty of cracking and enhances the reliability of network communication security between the device 20 and the server 10.

[0068]

Example 2

[0069] Embodiment 2 of the present invention also provides a remote connection method based on OTA, that is, a method for remote handshake between the server and the device. Similarly, the device can be the vehicle controller of an electric or fuel vehicle, and the server can be a cloud server, aiming to solve the technical problems such as the ease of cracking existing OAT technology.

[0070] Please refer to Figure 2 , Figure 2 The flowchart illustrates the OTA-based remote connection method provided in Embodiment 2 of the present invention. This method is applied to the server side and includes the following steps:

[0071] Step S101: Send a communication request and server-side string to the device.

[0072] Step S102: Receive the device password and device string fed back from the device, and verify the device password;

[0073] Step S103: Generate a true or false server-side password based on the verification result of the device-side password, and send it to the device along with the updated server-side string;

[0074] Step S104: Repeat steps S102 to S103 up to the first preset number of times, updating both the server-side string and the device-side string in each repetition;

[0075] Step S105: If the verification results of all device passwords are true, allow OTA upgrade of the device; otherwise, refuse OTA upgrade of the device.

[0076] It is understood that the device 20 will execute the instructions of steps S101 to S105 above through an independent second main control unit, wherein the number of cycles in step S104 can be customized.

[0077] The first and second preset number of attempts can be customized. The second preset number of attempts can be designed to be higher than the first preset number of attempts, such as the first preset number of attempts being 3 times and the second preset number of attempts being 10 times, to increase the difficulty of cracking the code.

[0078] Furthermore, in steps S103 and S104, when the device and the server verify each other's passwords, they can use a verification string.

[0079] Please refer to Figure 3 , Figure 3 The flowchart illustrates step S103 of the OTA-based remote connection method provided in Embodiment 2 of the present invention; further, in a preferred embodiment of the present invention, step S103, which generates a true or false server-side password based on the verification result, includes:

[0080] Step S1031: If the password on the device side is true, match the true server-side password corresponding to the server-side string from the preset mapping table using the lookup table method.

[0081] Step S1032: If the password on the device side is false, randomly generate a false password on the server side.

[0082] The server-side string is generated on the device side using a server-side string generator.

[0083]

Example 3

[0084] Please refer to Figure 4 , Figure 4 The flowchart illustrates the OTA-based remote connection method provided in Embodiment 3 of the present invention; an OTA-based remote connection method, applied to a device, includes:

[0085] Step S201: Receive the communication request and server string from the server, and generate the device password based on the server string;

[0086] Step S202: Send the device password and device string to the server.

[0087] Step S203: Receive the server password and the updated server string from the server, and verify the server password;

[0088] Step S204: Based on the verification result of the server-side password, generate a true or false device-side password, and repeat steps S202 to S203 up to the first preset number of times. In each repetition, both the server-side string and the device-side string are updated.

[0089] Step S205: If all server-side password verification results are true, OTA upgrade is allowed; otherwise, OTA upgrade is refused.

[0090] It is understood that the device 20 will execute the instructions of steps S201 to S205 above through an independent first main control unit, wherein the number of cycles in step S203 can be customized.

[0091] The first and second preset number of attempts can be customized. The second preset number of attempts can be designed to be higher than the first preset number of attempts, such as the first preset number of attempts being 3 times and the second preset number of attempts being 10 times, to increase the difficulty of cracking the code.

[0092] Furthermore, in steps S202 and S203, when the device and the server verify each other's passwords, they can use a verification string.

[0093] Furthermore, the generation of the device-side password in step S201 includes:

[0094] Receive device-side strings sent from the server;

[0095] The server-side password corresponding to the server-side string is matched from the preset mapping table using a lookup table method.

[0096] The server-side string is generated on the device side using a server-side string generator.

[0097] In step S204, generating a true or false device-side password includes:

[0098] Step S2041: When the verification result of the server-side password is true, match the server-side password that corresponds to the server-side string from the preset mapping table according to the lookup table method;

[0099] Step S2042: When the server-side password verification result is false, generate a false device-side password.

[0100]

Example 4

[0101] Embodiment 4 of the present invention also provides a vehicle-mounted connectivity device, comprising:

[0102] The first true random number generator is used to generate server-side strings;

[0103] The first main control unit is configured to execute the remote connection method applied to the device side according to the above embodiment three.

[0104] Example 5

[0105] Embodiment 5 of the present invention also provides an electric vehicle, including the vehicle-mounted connection device as described in Embodiment 4.

[0106] Furthermore, those skilled in the art should understand that if the battery module provided in the embodiments of the present invention is combined or replaced by means of fusion, simple changes, or mutual transformation, such as moving the positions of each component; or the product formed by them is set up as a whole; or it is designed to be detachable; and the combined components can form a device / apparatus / system with a specific function, then using such a device / apparatus / system to replace the corresponding components of the present invention also falls within the protection scope of the present invention.

[0107] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0108] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0109] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0110] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0111] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

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

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

[0114] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0115] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. An OTA-based remote connection method applied to a server end, characterized in that, The method comprises the following steps: 1) sending a communication request and a server-side string to a device side; 2) receiving a device-side password and a device-side string fed back from the device side, and verifying the device-side password; 3) generating a true or false server-side password according to the verification result of the device-side password, and sending the true or false server-side password to the device side together with an updated server-side string; wherein generating the true or false server-side password according to the verification result of the device-side password comprises: when the verification result of the device-side password is true, matching a true server-side password corresponding to the device-side string from a preset mapping table according to a lookup table method; and when the device-side password is false, generating a false server-side password; 4) repeating the steps 2) to 3) for a first preset number of times, and updating the server-side string and the device-side string in each repetition; 5) when the verification result of all device-side passwords is true, allowing the device side to be upgraded by OTA; otherwise, refusing to upgrade the device side by OTA.

2. The remote connection method according to claim 1, wherein The server-side string is randomly updated by a first true random number generator at the server side.

3. The remote connection method according to claim 1, wherein The false server-side password is randomly generated from a preset first database. 4.A method for remote connection based on OTA, applied to a device side, and characterized in that, The method comprises the following steps: 1) receiving a communication request and a server-side string from a server side, and generating a device-side password according to the server-side string; 2) sending the device-side password and a device-side string to the server side; 3) receiving a server-side password and an updated server-side string from the server side, and verifying the server-side password; 4) generating a true or false device-side password according to the verification result of the server-side password, and repeating the steps 2) to 3) for a first preset number of times, and updating the server-side string and the device-side string in each repetition; wherein generating the true or false device-side password comprises: when the verification result of the server-side password is true, matching a true server-side password corresponding to the server-side string from a preset mapping table according to a lookup table method; and when the verification result of the server-side password is false, generating a false device-side password; 5) when the verification result of all server-side passwords is true, allowing the device side to be upgraded by OTA; otherwise, refusing to upgrade the device side by OTA.

5. The remote connection method according to claim 4, wherein The device-side string is generated by a second true random number generator at the device side.

6. An OTA-based remote connection method, characterized by, The method comprises the following steps: 1) a server side sends a communication request and a server-side string to a device side; 2) the device side receives the communication request and the server-side string from the server side, and generates a device-side password mapped with the server-side string; 3) the device side sends the device-side password and the device-side string to the server side; 4) the server side receives the device-side password and the device-side string fed back from the device side, and verifies the device-side password; 5) the server side generates a true or false server-side password according to the verification result of the device-side password, and sends the true or false server-side password to the device side together with an updated device-side string; The server-side password true or false generated according to the verification result of the device-side password includes: when the verification result of the device-side password is true, matching the server-side password true corresponding to the device-side string from a preset mapping table according to a lookup table method; and when the device-side password is false, generating a false server-side password. 6) The device end receives the server-side password and the updated device-side string from the server end, and verifies the server-side password; 7) The device end generates a device-side password true or false according to the verification result of the server-side password; The generation of the device-side password true or false includes: when the verification result of the server-side password is true, matching the server-side password true corresponding to the server-side string from a preset mapping table according to a lookup table method; and when the verification result of the server-side password is false, generating a false device-side password; 8) Repeating 3) to 7) above to a first preset number of times, and updating the server-side string and the device-side string in each repetition; 9) When the verification result of all device-side passwords is true, the server end performs OTA upgrade on the device end; Otherwise, the server end does not perform OTA upgrade on the device end.

7. An OTA-based remote connection system, characterized by, It includes: The server end includes a first master control unit, and is configured with a first true random number generator and a second mapping table; The device end includes a second master control unit, and is configured with a second true random number generator and a first mapping table; The first master control unit is configured to perform the remote connection method according to any one of claims 1 to 3, and the second master control unit is configured to perform the remote connection method according to any one of claims 4 to 5.

8. An in-vehicle connection device characterized by comprising: It includes: The first true random number generator is used to generate a server string; The first master control unit is configured to perform the remote connection method according to any one of claims 4 to 5.

9. An electric vehicle, characterized by The vehicle-mounted connection device according to claim 8 is included.

Images