Vehicle software upgrading system and method

Abstract

The invention relates to the technical field of vehicle software, in particular to a vehicle software upgrading system and method.The method comprises the steps that a user terminal initiates an upgrading request to an upgrading server; after receiving the upgrading request, the upgrading server verifies the data packet; after the verification state is successful verification, the upgrade server securely encrypts and transmits the target data packet to the target vehicle; the target vehicle receives the encrypted data and the encryption key and decrypts the encrypted data and the encryption key to obtain a target data packet; and after confirming that the target data packet is completely transmitted, executing software upgrading operation at the vehicle end. According to the method, a user can finish upgrading through the terminal without going to an offline store, so that the cost of manpower, traffic and the like is reduced, and through multiple encryption, verification and communication guarantee, data tampering and attack are prevented, the upgrading progress is fed back in real time, and the personalized upgrading requirement is supported.

Description

Technical Field

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

[0002] With the advancement of the "new four modernizations" trend in the automotive industry, software has become a core element defining vehicle functions and performance. The complexity and scale of in-vehicle software continue to grow, and its update frequency has accelerated significantly for performance optimization, feature iteration, and security vulnerability patching. Against this backdrop, traditional offline upgrade models are no longer sufficient to meet the demands for efficient and convenient iteration, making over-the-air (OTA) download technology, which can be completed remotely via the network, an indispensable key technology for intelligent connected vehicles, crucial for improving user experience and ensuring vehicle safety.

[0003] In existing technologies, vehicle software upgrades primarily rely on owners driving their vehicles to offline service centers for operation using specialized diagnostic equipment. This method is cumbersome and time-consuming, resulting in low overall upgrade efficiency and incurring additional time and transportation costs for users. Furthermore, traditional upgrade methods lack effective end-to-end security encryption and verification mechanisms during software package transmission and writing, making upgrade data susceptible to interception, tampering, or malicious code injection during storage, posing significant information security vulnerabilities. Simultaneously, existing remote upgrade solutions are insufficient in terms of user interaction, intelligent judgment of upgrade conditions, and automatic recovery capabilities after upgrade failures, failing to meet users' comprehensive needs for convenience, reliability, and security. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle software upgrade system and method to solve at least one of the problems existing in the prior art.

[0005] This invention provides the following solution:

[0006] A vehicle software upgrade method, comprising:

[0007] The user terminal sends an upgrade request to the upgrade server;

[0008] After receiving the upgrade request, the upgrade server verifies the data packet;

[0009] After the verification status shows "verification successful", the upgrade server will securely encrypt and transmit the target data packet to the target vehicle.

[0010] The target vehicle receives and decrypts the encrypted data and encryption key to obtain the target data packet;

[0011] After confirming that the target data packet has been transmitted completely, perform the software upgrade operation on the vehicle side.

[0012] Furthermore, the data packet verification method includes:

[0013] The data packets are retrieved to determine the target data packet;

[0014] Perform legality verification on the target data packet;

[0015] The verification status is determined based on the result of the target data packet validity verification.

[0016] Furthermore, based on the software name and current version number in the upgrade request, the corresponding future version data packet is searched in the pre-stored data packet library and used as the target data packet.

[0017] Furthermore, the target data packet undergoes multi-dimensional legality verification, including source legality verification, suitability legality verification, and integrity verification. The source legality verification verifies the digital signature of the target data packet to confirm that it was issued by an authorized entity. The suitability legality verification compares the vehicle identification number and vehicle model in the upgrade request with the preset suitability range of the data packet to confirm that the target data packet is suitable for the vehicle that initiated the request. The integrity verification calculates the hash value of the target data packet and compares the calculation result with the baseline hash value attached to the data packet or pre-stored on the server. If they match, the integrity verification passes; otherwise, it fails.

[0018] In the validity verification process, if any verification sub-step fails, the verification status is determined to be verification failure, the process is terminated, and a prompt message containing the specific reason for failure is returned to the user terminal. If all verification sub-steps pass, the verification status is determined to be verification success, and the next step can be executed.

[0019] Furthermore, the data packet encryption transmission method includes:

[0020] The upgrade server encrypts the target data packet to obtain the encrypted data and encryption key;

[0021] Establish a secure communication channel between the upgrade server and the target vehicle;

[0022] Data transmission between the upgrade server and the target vehicle is achieved through a secure communication channel.

[0023] Furthermore, a hybrid encryption mechanism is used to process the target data packet to generate a random symmetric encryption key. The target data packet is then encrypted using the symmetric encryption key to obtain encrypted data. Finally, the symmetric encryption key is encrypted using the public key in the target vehicle's digital certificate to obtain the encryption key.

[0024] The upgrade server establishes an encrypted communication link with the target vehicle based on the transport layer security protocol to obtain a secure communication channel. The encrypted data, encryption key, and hash value of the target data packet are sent to the vehicle through the secure communication channel.

[0025] Furthermore, the encryption key is decrypted using the private key stored in the target vehicle to restore the symmetric encryption key. The restored symmetric encryption key is then used to decrypt the encrypted data to obtain the target data packet. The hash value of the decrypted target data packet is calculated and compared with the hash value of the target data packet before encryption. If the two match, the target data packet is determined to be transmitted completely; otherwise, the transmission process is determined to be risky, the current target data packet is discarded, and a retransmission is requested from the upgrade server.

[0026] Furthermore, the vehicle-side upgrade verification method includes:

[0027] The vehicle side is assessed to determine whether the upgrade conditions are met.

[0028] The upgrade operation will be performed once all upgrade conditions are met on the vehicle side.

[0029] Provide users with updates on the upgrade progress;

[0030] After the upgrade is complete, perform an integrity check on the software.

[0031] Furthermore, the vehicle's control system detects whether the current vehicle status meets preset upgrade conditions. The upgrade conditions include at least: the vehicle is in a parked state, the vehicle's power battery charge is higher than a preset threshold, and no other high-priority tasks are being executed.

[0032] The vehicle's electronic control unit initiates the upgrade program only when all upgrade conditions are met. It parses the upgrade script and files in the target data package, writes the new version software files to the target storage area according to the script instructions, overwrites the old version files, and records the upgrade progress in real time.

[0033] After the upgrade is completed, the integrity of the upgraded software is verified. If the verification is successful, the system version information is updated and the upgrade is completed. If the verification fails, a rollback operation is automatically performed to restore the software to the state before the upgrade and an upgrade failure notification is sent.

[0034] On the other hand, the present invention also provides a vehicle software upgrade system, comprising:

[0035] Upgrade the server for data packet storage and management;

[0036] The user terminal is used for vehicle binding, software version awareness and prompting, upgrade request generation and sending, and upgrade status feedback.

[0037] The vehicle communication module is used to establish a secure transmission channel with the upgrade server, receive, decrypt and verify upgrade packages, and report vehicle status back to the upgrade server.

[0038] The above solution achieves the following beneficial technical effects:

[0039] By constructing a fully automated closed-loop process from upgrade request initiation, server verification, secure transmission to vehicle-side execution and confirmation, this system comprehensively addresses many pain points in existing technologies, improving the efficiency and convenience of software upgrades. Users can complete upgrades without visiting physical stores, saving significant time and costs. In terms of security, the comprehensive application of multi-layered data verification, hybrid encryption technology, and secure communication protocols effectively ensures the integrity, confidentiality, and reliability of upgrade data at each stage of storage, transmission, and installation, significantly reducing the risk of attacks on in-vehicle networks. Meanwhile, intelligent version recommendations, status awareness, and condition judgment mechanisms optimize the user experience, while comprehensive verification and rollback strategies ensure the stability and controllability of the upgrade process and results. This provides a comprehensive and innovative technical solution for secure, efficient, and convenient remote upgrades of intelligent connected vehicle software. Attached Figure Description

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

[0041] Figure 1 This is a flowchart of the vehicle software upgrade method in this embodiment.

[0042] Figure 2 This is a flowchart of the data packet verification method in this embodiment.

[0043] Figure 3 This is a flowchart of the data packet encryption transmission method in this embodiment.

[0044] Figure 4 This is a flowchart of the vehicle-side upgrade verification method in this embodiment.

[0045] Figure 5 This is a schematic diagram of the vehicle software upgrade system in this embodiment. Detailed Implementation

[0046] The vehicle software upgrade system and method disclosed in this invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the technical features or combinations of technical features described in the following embodiments should not be considered isolated; they can be combined with each other to achieve better technical effects. In the accompanying drawings of the following embodiments, the same reference numerals appearing in each drawing represent the same features or components, which can be applied to different embodiments. Therefore, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0047] It should be noted that the structures, proportions, sizes, etc., illustrated in the accompanying drawings are merely for illustrative purposes and to aid those skilled in the art in understanding and reading the invention. They are not intended to limit the conditions under which the invention can be implemented. Any modifications to the structure, changes in proportions, or adjustments to size, provided they do not affect the effectiveness or purpose of the invention, should fall within the scope of the technical content disclosed in the invention. The scope of the preferred embodiments of the present invention includes other implementations, wherein functions may be performed not in the order stated or discussed, including substantially simultaneously or in reverse order, depending on the functions involved. This should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0048] Techniques, methods, and apparatus known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and apparatus should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0049] In the description of the embodiments of this application, " / " means "or", and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" means: A and B exist alone, B exists alone, and A and B exist simultaneously. In the description of the embodiments of this application, "multiple" refers to two or more embodiments.

[0050] Please see Figure 1 As shown, this is the vehicle software upgrade method of this embodiment, including:

[0051] Step S1: The user terminal sends an upgrade request to the upgrade server.

[0052] Specifically, in step S1 of this embodiment, an upgrade request for the software to be upgraded for the target vehicle is sent to the upgrade server through the user terminal. The upgrade request includes at least the software name, current software version number, vehicle identification code, and vehicle model of the software to be upgraded.

[0053] In a preferred embodiment, before sending the upgrade request, the method further includes: the user terminal synchronizing data with the upgrade server to obtain a list of software versions available for the target vehicle to upgrade; selecting a target upgrade version from the list based on user operation or a preset strategy; and the user terminal generating a structured upgrade request data packet containing the above information as well as a timestamp and a unique request identifier.

[0054] Specifically, in step S1 of this embodiment, by synchronizing data between the user terminal and the upgrade server, the system can proactively and intelligently provide users with an accurate list of upgradable versions, avoiding the tediousness of manual searching and information lag. The generated standardized upgrade request data packet ensures the structured and accurate transmission of information, laying a reliable foundation for the automated processing of subsequent processes. At the same time, the design integrating timestamps and unique identifiers greatly facilitates request tracking and system auditing, effectively improving the standardization and management efficiency of the start point of the upgrade process.

[0055] Please continue reading. Figure 1 As shown, the vehicle software upgrade method further includes:

[0056] Step S2: After receiving the upgrade request, the upgrade server verifies the data packet.

[0057] Please see Figure 2 As shown, this is a data packet verification method, which includes:

[0058] Step S21: Retrieve the data packets to determine the target data packet.

[0059] Specifically, in step S21 of this embodiment, based on the software name and current version number in the upgrade request, the corresponding future version data packet is searched in a pre-stored data packet library and used as the target data packet. The data packets in the data packet library are indexed according to software name, applicable vehicle model, and version number.

[0060] Specifically, in this embodiment, the data package includes pre-stored and dynamically generated data packages. The pre-stored data package is a new version data package that the upgrade server stores in advance within the official plan. The dynamically generated data package is a customized upgrade package for user needs or vehicle-specific adaptation scenarios. After receiving a request, the server compiles and generates an adapted upgrade package in real time based on the basic version data.

[0061] Specifically, in this embodiment, when a user requests a dynamically generated data packet in an upgrade request, the upgrade server generates an adapted upgrade packet based on the base version data and calls preset compilation rules. During the compilation process, the upgrade server calculates the resource utilization and compilation time in real time to optimize the generation efficiency. The generated data packet is immediately subjected to legality verification to ensure compliance with distribution standards.

[0062] In a preferred embodiment, the user terminal intelligently recommends upgrade versions based on the user's historical upgrade records and preferences, and calculates the matching degree between the user and each version of the data package. The matching degree is expressed as: matching degree = α × function preference weight + β × usage frequency weight + γ × user rating weight, where α, β, and γ represent adjustable matching parameters, which belong to [0,1]. The function preference weight, usage frequency weight, and user rating weight are weight values ​​based on the analysis of the user's upgrade records and preferences, which indicate which aspect of the content the user prefers.

[0063] Please continue reading. Figure 2 As shown, the data packet verification method further includes:

[0064] Step S22: Verify the legitimacy of the target data packet.

[0065] Specifically, in step S22 of this embodiment, the target data packet undergoes multi-dimensional legality verification, including source legality verification, suitability legality verification, and integrity verification. Source legality verification verifies the digital signature of the target data packet to confirm that it was issued by an authorized entity. Suitability legality verification compares the vehicle identification number and vehicle model in the upgrade request with the preset suitability range of the data packet to confirm that the target data packet is suitable for the vehicle initiating the request. Integrity verification calculates the hash value of the target data packet and compares the calculation result with a baseline hash value attached to the data packet or pre-stored on the server. If they match, the integrity verification passes; otherwise, it fails. Source legality verification can be accomplished by verifying the trustworthiness of the certificate chain corresponding to the digital signature.

[0066] Please continue reading. Figure 2 As shown, the data packet verification method further includes:

[0067] Step S23: Determine the verification status based on the result of the target data packet validity verification.

[0068] Specifically, in step S23 of this embodiment, if any verification sub-step fails during the legality verification, the verification status is determined to be verification failure, the process is terminated, and a prompt message containing the specific reason for failure is returned to the user terminal. If all verification sub-steps pass, the verification status is determined to be verification success, and the next step is allowed to be executed.

[0069] Specifically, in step S2 of this embodiment, by constructing a multi-layered, comprehensive verification system that includes source, compatibility, and integrity, illegal, incompatible, or corrupted data packets can be prevented from entering the upgrade process at the source. This rigorous pre-screening mechanism significantly reduces the risk of vehicle upgrade failure or even system malfunction due to data packet issues. It not only ensures the legality and security of the upgrade content but also ensures a high degree of compatibility between the upgrade package and the vehicle hardware through precise compatibility assessment, thus providing a solid and reliable security barrier for the smooth execution of subsequent upgrade operations.

[0070] Please continue reading. Figure 1 As shown, the vehicle software upgrade method further includes:

[0071] Step S3: After the verification status is successful, the upgrade server securely encrypts and transmits the target data packet to the target vehicle.

[0072] Please see Figure 3 As shown, it is a data packet encryption transmission method, including:

[0073] Step S31: The upgrade server encrypts the target data packet to obtain encrypted data and encryption key.

[0074] Specifically, in step S31 of this embodiment, a hybrid encryption mechanism is used to process the target data packet to generate a random symmetric encryption key. The target data packet is then encrypted using the symmetric encryption key to obtain encrypted data. Finally, the symmetric encryption key is encrypted using the public key in the target vehicle's digital certificate to obtain an encryption key.

[0075] Please continue reading. Figure 3 As shown, the data packet encryption transmission method further includes:

[0076] Step S32: Establish a secure communication channel between the upgrade server and the target vehicle.

[0077] Specifically, in step S32 of this embodiment, an encrypted communication link is established between the upgrade server and the target vehicle based on the transport layer security protocol to obtain a secure communication channel.

[0078] Please continue reading. Figure 3 As shown, the data packet encryption transmission method further includes:

[0079] Step S33: Based on the secure communication channel, data transmission between the upgrade server and the target vehicle is realized.

[0080] Specifically, in step S33 of this embodiment, the encrypted data, the encryption key, and the hash value of the target data packet are sent to the vehicle through a secure communication channel, and the log information of this transmission is recorded.

[0081] Specifically, in step S3 of this embodiment, a high-strength end-to-end secure transmission channel is constructed by combining a hybrid encryption mechanism with a transport layer security protocol. Symmetric encryption ensures the efficiency of large data packet encryption, while asymmetric encryption ensures the security of key distribution. This dual protection ensures that even if data is intercepted during transmission, it cannot be cracked or tampered with. This design greatly enhances the confidentiality and integrity of upgrade data during transmission over public networks, effectively resisting network threats such as man-in-the-middle attacks and data theft, and providing core security guarantees for the remote wireless transmission of critical software data.

[0082] Please continue reading. Figure 1 As shown, the vehicle software upgrade method further includes:

[0083] In step S4, the target vehicle receives the encrypted data and encryption key and decrypts them to obtain the target data packet.

[0084] Specifically, in step S4 of this embodiment, the encryption key is decrypted using the private key stored in the target vehicle to restore the symmetric encryption key. The restored symmetric encryption key is then used to decrypt the encrypted data to obtain the target data packet. The hash value of the decrypted target data packet is calculated and compared with the hash value of the target data packet before encryption. If the two match, it is determined that the target data packet has been transmitted completely; otherwise, it is determined that there is a risk in the transmission process, the current target data packet is discarded, and a retransmission is requested from the upgrade server.

[0085] Specifically, in step S4 of this embodiment, the vehicle dynamically adjusts the upgrade conditions according to the real-time environment and system status. If a weak network signal is detected, the upgrade is delayed; if the battery level is at a critical value, the user is prompted to connect the charger; if an abnormality occurs during the upgrade process, the upgrade is paused and the abnormal event is recorded.

[0086] Specifically, in step S4 of this embodiment, a rigorous decryption and integrity re-verification process is performed on the vehicle side, constituting an effective verification and supplement to the secure transmission on the server side. By comparing the data digest values ​​before and after decryption, any abnormal changes in data at the transmission end can be accurately identified. Its intelligent strategy of dynamically adjusting upgrade conditions avoids the risks that may be caused by forcibly upgrading when the network is unstable or the vehicle is in poor condition, ensuring that the upgrade task is only started in a safe and suitable environment, thereby improving the success rate of a single upgrade and the reliability of system behavior.

[0087] Please continue reading. Figure 1As shown, the vehicle software upgrade method further includes:

[0088] Step S5: After confirming that the target data packet has been transmitted completely, perform a software upgrade operation on the vehicle side.

[0089] Please see Figure 4 As shown, this is the vehicle-side upgrade verification method, which includes:

[0090] Step S51: Perform an upgrade condition check on the vehicle to determine whether the upgrade conditions are met.

[0091] Specifically, in step S51 of this embodiment, the vehicle control system detects whether the current vehicle status meets the preset upgrade conditions. The upgrade conditions include at least: the vehicle is in a parked state, the vehicle's power battery charge is higher than a preset threshold, and no other high-priority tasks are being executed.

[0092] Please continue reading. Figure 4 As shown, the vehicle-side upgrade verification method further includes:

[0093] Step S52: When all upgrade conditions are met on the vehicle side, perform the upgrade operation.

[0094] Specifically, in step S52 of this embodiment, the vehicle's electronic control unit starts the upgrade program when all upgrade conditions are met, parses the upgrade script and file in the target data packet, writes the new version software file to the target storage area according to the script instructions, overwrites the old version file, and records the upgrade progress in real time.

[0095] Please continue reading. Figure 4 As shown, the vehicle-side upgrade verification method further includes:

[0096] Step S53: Provide feedback to the user on the upgrade progress.

[0097] Specifically, in step S53 of this embodiment, during the upgrade process, the vehicle communication module feeds back the upgrade progress information to the upgrade server and user terminal in real time.

[0098] Please continue reading. Figure 4 As shown, the vehicle-side upgrade verification method further includes:

[0099] Step S54: After the upgrade is completed, perform an integrity check on the software.

[0100] Specifically, in step S54 of this embodiment, after the upgrade is completed, the integrity of the upgraded software is verified. If the verification is successful, the system version information is updated and the upgrade is completed. If the verification fails, a rollback operation is automatically performed to restore the software to the state before the upgrade and an upgrade failure notification is sent.

[0101] Specifically, this embodiment does not specify the method for performing integrity verification on the upgraded software, such as comparing the hash value after the upgrade with the expected value to achieve integrity verification.

[0102] Specifically, in step S5 of this embodiment, by setting strict upgrade prerequisites and introducing an automatic verification and rollback mechanism after the upgrade, the upgrade operation itself is ensured to have zero interference with vehicle operation safety. The real-time progress feedback makes the upgrade process transparent and knowable to users and servers, enhancing user experience and system controllability. The complete verification-execution-confirmation closed-loop design can capture and repair possible software write errors in the final stage, ensuring that the vehicle is immediately in a fully functional, stable and usable software state after the upgrade, greatly improving the final success rate and system robustness of the entire upgrade process.

[0103] Please see Figure 5 As shown, this is the vehicle software upgrade system of this embodiment, including:

[0104] Upgrade the server for data packet storage and management.

[0105] The upgrade server is a high-performance server equipped with a large-capacity storage device, supports parallel processing of multiple vehicle upgrade requests, and deploys Linux-based upgrade management software with data packet management, request processing, security verification, and communication scheduling functions.

[0106] The upgrade server establishes an index database for data packets by software name, vehicle model, and version number, supporting fast retrieval. It periodically scans the official version repository, automatically downloads and verifies new version data packets. All data packets must undergo digital signature verification, vulnerability scanning, and compatibility testing before being uploaded, and only data packets marked as "distributable" can be stored.

[0107] The upgrade server verifies the legitimacy of data packets by verifying the identity of the data packet publisher through a digital certificate chain, comparing the vehicle identification code and vehicle model with the data packet adaptation table, calculating the hash value of the data packet using the SM3 hash algorithm, and comparing it with a preset value. If the verification fails, the data packet is automatically isolated and an alarm is pushed to the system administrator.

[0108] The user terminal is used for vehicle binding, software version awareness and prompts, upgrade request generation and sending, and upgrade status feedback.

[0109] The user terminal requires users to enter a VIN code upon first use, which is then linked to the account. The list of upgradable versions is periodically synchronized with the server. User preferences include, but are not limited to, feature type and release time, which are used to filter versions. Available upgrades are indicated via pop-ups or notifications. The upgrade request includes the software name, current version, VIN, and upgrade type. The user terminal displays the download progress and upgrade progress in real time, and supports upgrade success / failure notifications and rollback prompts.

[0110] The vehicle communication module is used to establish a secure transmission channel with the upgrade server, receive, decrypt and verify upgrade packages, and report vehicle status back to the upgrade server.

[0111] The vehicle communication module is an embedded module that supports 4G / 5G communication. It integrates a security chip to store digital certificates, and the private key and certificate are stored in the hardware security module to prevent unauthorized access.

[0112] In the above description, the disclosure of this invention is not intended to limit itself to these aspects. Rather, within the scope of the objectives of this disclosure, components can be selectively and operationally combined in any number. Furthermore, terms such as “comprising,” “encompassing,” and “having” should be interpreted by default as inclusive or open-ended, rather than exclusive or closed, unless explicitly defined as such. All technical, scientific, or other terms are to be understood by those skilled in the art, unless defined as such. Public terms found in dictionaries should not be interpreted in the context of the relevant technical documents in an overly idealistic or impractical manner, unless explicitly defined as such in this disclosure. Any modifications or alterations made by those skilled in the art based on the foregoing disclosure are within the scope of the claims.

Claims

1. A vehicle software upgrade method, characterized in that, include: The user terminal sends an upgrade request to the upgrade server; After receiving the upgrade request, the upgrade server verifies the data packet; After the verification status shows "verification successful", the upgrade server will securely encrypt and transmit the target data packet to the target vehicle. The target vehicle receives and decrypts the encrypted data and encryption key to obtain the target data packet; After confirming that the target data packet has been transmitted completely, perform the software upgrade operation on the vehicle side.

2. The vehicle software upgrade method according to claim 1, characterized in that, Data packet verification methods include: The data packets are retrieved to determine the target data packet; Perform legality verification on the target data packet; The verification status is determined based on the result of the target data packet validity verification.

3. The vehicle software upgrade method according to claim 2, characterized in that, Based on the software name and current version number in the upgrade request, the corresponding future version data packet is searched in the pre-stored data packet library and used as the target data packet.

4. The vehicle software upgrade method according to claim 3, characterized in that, The target data packet undergoes multi-dimensional legality verification, including source legality verification, suitability legality verification, and integrity verification. Source legality verification verifies the digital signature of the target data packet to confirm that it was issued by an authorized entity. Suitability legality verification compares the vehicle identification number and vehicle model in the upgrade request with the preset suitability range of the data packet to confirm that the target data packet is suitable for the vehicle that initiated the request. Integrity verification calculates the hash value of the target data packet and compares the calculation result with the baseline hash value attached to the data packet or pre-stored on the server. If they match, the integrity verification passes; otherwise, it fails. In the validity verification process, if any verification sub-step fails, the verification status is determined to be verification failure, the process is terminated, and a prompt message containing the specific reason for failure is returned to the user terminal. If all verification sub-steps pass, the verification status is determined to be verification success, and the next step can be executed.

5. The vehicle software upgrade method according to claim 1, characterized in that, Data packet encryption transmission methods include: The upgrade server encrypts the target data packet to obtain the encrypted data and encryption key; Establish a secure communication channel between the upgrade server and the target vehicle; Data transmission between the upgrade server and the target vehicle is achieved through a secure communication channel.

6. The vehicle software upgrade method according to claim 5, characterized in that, A hybrid encryption mechanism is used to process the target data packet, generate a random symmetric encryption key, and use the symmetric encryption key to encrypt the target data packet to obtain encrypted data. The public key in the target vehicle's digital certificate is used to encrypt the symmetric encryption key to obtain the encryption key. The upgrade server establishes an encrypted communication link with the target vehicle based on the transport layer security protocol to obtain a secure communication channel. The encrypted data, encryption key, and hash value of the target data packet are sent to the vehicle through the secure communication channel.

7. The vehicle software upgrade method according to claim 1, characterized in that, The encryption key is decrypted using the private key stored in the target vehicle to restore the symmetric encryption key. The restored symmetric encryption key is then used to decrypt the encrypted data to obtain the target data packet. The hash value of the decrypted target data packet is calculated and compared with the hash value of the target data packet before encryption. If they match, the target data packet is determined to be transmitted completely; otherwise, the transmission process is deemed to be at risk, the current target data packet is discarded, and a retransmission is requested from the upgrade server.

8. The vehicle software upgrade method according to claim 1, characterized in that, Vehicle-side upgrade verification methods include: The vehicle side is assessed to determine whether the upgrade conditions are met. The upgrade operation will be performed once all upgrade conditions are met on the vehicle side. Provide users with updates on the upgrade progress; After the upgrade is complete, perform an integrity check on the software.

9. The vehicle software upgrade method according to claim 8, characterized in that, The vehicle's control system detects whether the current vehicle status meets preset upgrade conditions. The upgrade conditions include at least: the vehicle is in a parked state, the vehicle's power battery charge is higher than a preset threshold, and no other high-priority tasks are being executed. The vehicle's electronic control unit initiates the upgrade program only when all upgrade conditions are met. It parses the upgrade script and files in the target data package, writes the new version software files to the target storage area according to the script instructions, overwrites the old version files, and records the upgrade progress in real time. After the upgrade is completed, the integrity of the upgraded software is verified. If the verification is successful, the system version information is updated and the upgrade is completed. If the verification fails, a rollback operation is automatically performed to restore the software to the state before the upgrade and an upgrade failure notification is sent.

10. A vehicle software upgrade system, applied to the vehicle software upgrade method as described in any one of claims 1-9, characterized in that, include: Upgrade the server for data packet storage and management; The user terminal is used for vehicle binding, software version awareness and prompting, upgrade request generation and sending, and upgrade status feedback. The vehicle communication module is used to establish a secure transmission channel with the upgrade server, receive, decrypt and verify upgrade packages, and report vehicle status back to the upgrade server.

Images