Methods for upgrading in-vehicle systems, electrical equipment, and computer-readable storage media

Abstract

This application discloses a method for upgrading an in-vehicle system. The method, used on a server, includes: when an upgrade is needed for the in-vehicle system, obtaining first vehicle status information of the target vehicle; determining whether the first vehicle status information meets the upgrade conditions based on the first vehicle status information; and if the first vehicle status information meets the upgrade conditions, creating an in-vehicle system upgrade task and sending it to the target vehicle, wherein the target vehicle downloads the in-vehicle system upgrade software package according to the upgrade task. Thus, by pre-detecting and screening the vehicle status before the upgrade, upgrade tasks are only sent to vehicles that meet the conditions, achieving precise screening of vehicle status before the upgrade. This effectively avoids upgrade failures due to unqualified vehicle status, thereby reducing the waste of network traffic and server processing resources to a certain extent, improving the upgrade success rate and stability, and optimizing the user experience during the in-vehicle system upgrade process.

Description

Technical Field

[0001] This application relates to the fields of automotive electronics and intelligent connected vehicle technology, and in particular to a method for upgrading an in-vehicle system, electrical equipment, and a computer-readable storage medium. Background Technology

[0002] In related technologies, the process of upgrading in-vehicle system software is easily affected by vehicle status and environment, leading to upgrade failure, waste of resources, and poor user experience. Summary of the Invention

[0003] This application provides a method for upgrading an in-vehicle system, an electrical device, and a computer-readable storage medium.

[0004] This application provides a method for upgrading an in-vehicle system, the method being used on a server, the method comprising: When there is an upgrade requirement for the in-vehicle system, obtain the first vehicle status information of the target vehicle; Based on the first vehicle status information, determine whether the first vehicle status information meets the upgrade conditions, wherein the first vehicle status information includes first battery information, first location information, first fault status information and / or first vehicle system software version information; If the first vehicle status information meets the upgrade conditions, an in-vehicle system upgrade task is created and sent to the target vehicle, wherein the target vehicle downloads the in-vehicle system upgrade software package according to the in-vehicle system upgrade task.

[0005] In this way, by pre-detecting and screening the vehicle status before the upgrade, the upgrade task is only sent to vehicles that meet the conditions. This achieves accurate screening of the vehicle status before the upgrade, effectively avoiding upgrade failures caused by substandard vehicle status. This reduces the waste of network traffic and server processing resources to a certain extent, improves the success rate and stability of the upgrade, and optimizes the user experience during the vehicle system upgrade process.

[0006] In some implementations, the first vehicle status information includes first battery level information, first location information, first fault status information, and first vehicle system software version information. The step of determining whether the first vehicle status information meets the upgrade conditions based on the first vehicle status information includes: If the first power information is greater than or equal to a preset power threshold, the first location information is at a preset location, the first fault state is a normal operating state, and the first vehicle system software version information matches the vehicle system upgrade package, then the first vehicle status information is determined to meet the upgrade conditions.

[0007] In this way, by clarifying the specific composition of the first vehicle status information and the judgment criteria for upgrade conditions, a comprehensive and strict verification of vehicle upgrade eligibility is achieved. This effectively avoids misjudgment problems caused by missing status information or ambiguous judgment criteria, ensuring that only vehicles that truly meet the upgrade conditions will enter the subsequent upgrade process. This, to a certain extent, improves the success rate and stability of vehicle system upgrades, reduces invalid upgrade operations caused by misjudgment, and reduces the waste of network traffic and server resources. At the same time, the alarm notification mechanism ensures the traceability and adjustability of the upgrade process.

[0008] In some embodiments, the method further includes: Upon receiving feedback that the vehicle system upgrade package has been successfully downloaded and upon reaching the preset upgrade time, a software upgrade instruction is generated and sent to the target vehicle. The target vehicle then performs a vehicle system upgrade based on the software upgrade instruction and the successfully downloaded vehicle system upgrade package.

[0009] In this way, by setting the trigger conditions for the generation and issuance of software upgrade instructions, the orderly management of vehicle system upgrades is achieved. To a certain extent, this avoids the interference to users caused by vehicles starting upgrades at inappropriate times, effectively ensuring that the vehicle system can start upgrades at the preset optimal time, guaranteeing the continuity and stability of vehicle system upgrades, and improving the success rate of vehicle system upgrades.

[0010] In some embodiments, the method further includes: If the first vehicle status information does not meet the upgrade conditions or if feedback information indicating that the vehicle system upgrade package download failed is received, a download failure prompt message is sent. After a preset detection interval, it is determined again whether the first vehicle status information meets the upgrade conditions.

[0011] In this way, by setting up a notification mechanism and a timed re-inspection mechanism for upgrade anomalies, effective control over abnormal situations in the upgrade process is achieved. This effectively avoids the direct termination of the upgrade process due to temporary vehicle status non-compliance or network fluctuations. The server can dynamically track changes in vehicle status and provide subsequent upgrade opportunities for vehicles that do not meet the conditions temporarily. This improves the coverage and flexibility of vehicle system upgrades to a certain extent, reduces the waste of upgrade resources caused by abnormal situations, and facilitates timely awareness and handling of upgrade obstacles by relevant parties, thereby improving the manageability of the upgrade process and user experience.

[0012] This application provides a method for upgrading an in-vehicle system, the method being used in a vehicle, the method comprising: Based on the received vehicle system upgrade task, the server downloads the vehicle system upgrade software package. When there is an upgrade requirement for the vehicle system, the server obtains the first vehicle status information of the vehicle, determines whether the first vehicle status information meets the upgrade conditions, and if the first vehicle status information meets the upgrade conditions, the server creates the vehicle system upgrade task and sends it to the vehicle.

[0013] In this way, by pre-detecting and screening the vehicle status before the upgrade, the orderly control of the vehicle system upgrade process is achieved, effectively avoiding upgrade failure caused by blindly starting the download operation when the vehicle does not meet the upgrade conditions. This reduces the probability of download failure to a certain extent, reduces the waste of network traffic and vehicle resources, and ensures the standardization and reliability of the upgrade process.

[0014] In some embodiments, the method further includes: After the preset time for executing the vehicle system upgrade task, check whether the vehicle system upgrade package has been successfully downloaded; If the vehicle system upgrade package is successfully downloaded, a feedback message indicating that the vehicle system upgrade package has been successfully downloaded is sent to the server. If the vehicle system upgrade package fails to download, the vehicle system upgrade package will be downloaded again after a preset waiting time. If the preset execution end time is reached, the download of the vehicle system upgrade package is terminated and a feedback message indicating that the download of the vehicle system upgrade package failed is sent to the server.

[0015] In this way, by performing download result detection, failure retry, and timeout termination operations, dynamic control of the vehicle-side download process is achieved, effectively improving the download success rate of the vehicle system upgrade software package and avoiding download failures caused by temporary issues such as single network fluctuations. This, to a certain extent, ensures the smooth progress of subsequent upgrade processes. At the same time, clear timeout termination rules prevent download tasks from occupying vehicle resources indefinitely, improving the utilization efficiency of vehicle system resources to a certain extent. Furthermore, timely result feedback ensures information synchronization between the server and the vehicle, enhancing the synergy of the entire upgrade process and optimizing the user experience.

[0016] In some embodiments, the method further includes: According to the software upgrade instruction and the successfully downloaded vehicle system upgrade package, the vehicle system is upgraded. When the server receives feedback that the vehicle system upgrade package has been successfully downloaded and the preset upgrade time has been reached, it generates a software upgrade instruction and sends it to the vehicle.

[0017] In this way, by setting the trigger conditions for the generation and issuance of software upgrade instructions, the orderly management of vehicle system upgrades is achieved. To a certain extent, this avoids the interference to users caused by vehicles starting upgrades at inappropriate times, effectively ensuring that the vehicle system can start upgrades at the preset optimal time, guaranteeing the continuity and stability of vehicle system upgrades, and improving the success rate of vehicle system upgrades.

[0018] In some implementations, upgrading the vehicle system according to the software upgrade instruction and the successfully downloaded vehicle system upgrade package includes: According to the software upgrade instruction, the second vehicle status information of the vehicle is obtained, wherein the second vehicle status information includes vehicle speed information, gear information, second battery level information, second location information, and second fault status information. If the second vehicle status information meets the burning conditions, the vehicle system is upgraded according to the vehicle system upgrade software package.

[0019] In this way, by obtaining the second vehicle status information and verifying the burning conditions before the upgrade is executed, a second precise control over the timing of vehicle upgrades is achieved. This effectively avoids safety risks and upgrade failures caused by performing upgrades when the vehicle is in an unsuitable state such as driving or malfunctioning. As a result, the safety and reliability of vehicle system upgrades are improved to a certain extent, ensuring vehicle driving safety and user property safety, reducing resource waste caused by upgrade failures, and optimizing user experience.

[0020] This application also provides an electrical device, including: a processor and a memory for storing processor-executable instructions, wherein the processor is configured to execute the instructions to implement the above-described method.

[0021] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0022] The electrical equipment and computer-readable storage medium provided in this application, when implementing the above method, firstly, when there is an upgrade requirement for the in-vehicle system, acquire the first vehicle status information of the target vehicle. Then, based on the first vehicle status information, determine whether the first vehicle status information meets the upgrade conditions. The first vehicle status information includes first battery level information, first location information, first fault status information, and / or first in-vehicle system software version information. Finally, if the first vehicle status information meets the upgrade conditions, create an in-vehicle system upgrade task and send it to the target vehicle. The target vehicle downloads the in-vehicle system upgrade software package according to the upgrade task. In this way, by pre-detecting and screening the vehicle status before the upgrade, upgrade tasks are only sent to vehicles that meet the conditions, achieving accurate screening of the vehicle status before the upgrade. This effectively avoids upgrade failures due to unqualified vehicle status, thereby reducing the waste of network traffic and server processing resources to a certain extent, improving the upgrade success rate and stability, and optimizing the user experience during the in-vehicle system upgrade process.

[0023] Additional aspects and advantages of embodiments of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of embodiments of this application. Attached Figure Description

[0024] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein: Figure 1 This is one of the flowcharts illustrating a vehicle system upgrade method according to certain embodiments of this application; Figure 2 This is a second schematic flowchart of a vehicle system upgrade method according to certain embodiments of this application; Figure 3 This is a schematic diagram of the vehicle status inspection implementation process in some embodiments of this application; Figure 4 This is a schematic diagram of the vehicle detection system structure according to some embodiments of this application; Figure 5 This is a third schematic flowchart of a vehicle system upgrade method according to certain embodiments of this application; Figure 6 This is a schematic diagram of the vehicle system upgrade implementation process for certain embodiments of this application; Figure 7 This is the fourth flowchart illustrating a method for upgrading an in-vehicle system according to certain embodiments of this application; Figure 8 This is the fifth flowchart illustrating a method for upgrading an in-vehicle system according to certain embodiments of this application; Figure 9This is a flowchart of a vehicle system upgrade method according to certain embodiments of this application, number six. Figure 10 This is a schematic diagram illustrating the download of an in-vehicle system upgrade software package according to certain embodiments of this application; Figure 11 This is a schematic diagram of the vehicle system structure according to certain embodiments of this application; Figure 12 This is the seventh flowchart illustrating a method for upgrading an in-vehicle system according to certain embodiments of this application; Figure 13 This is the eighth flowchart of a vehicle system upgrade method according to certain embodiments of this application. Detailed Implementation

[0025] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of this application, and should not be construed as limiting the embodiments of this application.

[0026] With the rapid development of automotive electronics technology, the functions of in-vehicle systems are becoming increasingly sophisticated, making software updates a crucial element in ensuring vehicle performance optimization, functional expansion, and vulnerability patching. To meet the demands for remote and efficient upgrades, over-the-air (OTA) technology is increasingly being adopted to enable remote upgrades of in-vehicle system software. This technology supports remote program version detection, remote diagnostics, remote program upgrades, and other related remote services, greatly facilitating vehicle after-sales maintenance and functional upgrades. The core principle of OTA technology is to establish a connection with the vehicle through the air interface of mobile communication, enabling the transmission and installation of upgrade programs, and it has become the mainstream technology choice for current vehicle software upgrades.

[0027] The current OTA (Over-The-Air) upgrade process typically involves the user initiating an upgrade command via a vehicle-mounted tablet or other terminal. Upon receiving the command, the system initiates the upgrade process, directly downloading and installing the software. Some optimized OTA solutions employ methods such as software package downloading, package combination, and resume download to mitigate the impact of network fluctuations on the upgrade process. These solutions break the complete upgrade package into multiple packages, download them sequentially, and then combine them. Simultaneously, a resume download module records the download progress, allowing the download to resume from the point of interruption when the network connection is restored, eliminating the need to re-download the complete package.

[0028] However, current OTA technology solutions impose strict requirements on the real-time status of the vehicle during upgrades. Multiple conditions, such as the vehicle's braking status, gear position, power mode, remaining battery power, and driving speed, must meet preset standards. Otherwise, the upgrade is likely to fail. However, the OTA technology does not actively and comprehensively assess the vehicle's status during the upgrade process. Instead, it directly executes the upgrade operation, causing the vehicle to initiate the upgrade even when the upgrade conditions are not met. This not only leads to upgrade failure but also wastes network traffic, server resources, and vehicle power.

[0029] Furthermore, the success rate of OTA upgrades is easily affected by the network environment. Even with optimization solutions such as packet downloading and breakpoint resume, it is difficult to completely avoid interference from network factors. Once a network anomaly occurs, the upgrade may still fail, requiring repeated upgrade requests. This not only prolongs the upgrade cycle but also increases traffic consumption costs. Especially for export vehicles, cross-border traffic costs are high, and repeated upgrades will increase usage costs.

[0030] In addition, some optimization solutions require additional configuration of breakpoint resume modules, which have specific requirements for hardware and software equipment, increasing the complexity and cost of technical implementation. However, their core technical logic still cannot fundamentally solve the upgrade problems caused by vehicle status adaptability and network stability.

[0031] Based on the above issues, please refer to Figure 1 This application provides a method for upgrading an in-vehicle system, the method being used on a server, the method comprising: 01: When there is an upgrade requirement for the in-vehicle system, obtain the first vehicle status information of the target vehicle; 02: Based on the first vehicle status information, determine whether the first vehicle status information meets the upgrade conditions, wherein the first vehicle status information includes first battery level information, first location information, first fault status information and / or first vehicle system software version information; 03: If the vehicle status information meets the upgrade conditions, create an in-vehicle system upgrade task and send it to the target vehicle. The target vehicle downloads the in-vehicle system upgrade package according to the in-vehicle system upgrade task.

[0032] This application provides a first device for upgrading an in-vehicle system. The in-vehicle system upgrade method of this application can be implemented by the first device for upgrading an in-vehicle system. Specifically, the first device for upgrading an in-vehicle system includes an acquisition module, a determination module, and a sending module. The acquisition module is used to acquire first vehicle status information of the target vehicle when there is an upgrade requirement for the in-vehicle system. The determination module is used to determine whether the first vehicle status information meets the upgrade conditions based on the first vehicle status information, wherein the first vehicle status information includes first battery level information, first location information, first fault status information, and / or first in-vehicle system software version information. The sending module is used to create an in-vehicle system upgrade task and send it to the target vehicle when the first vehicle status information meets the upgrade conditions, wherein the target vehicle downloads the in-vehicle system upgrade software package according to the in-vehicle system upgrade task.

[0033] This application also provides a server, which includes a memory and a processor. The vehicle system upgrade method of this application can be implemented by the server of this application. Specifically, the memory stores a computer program, and the processor is used to obtain first vehicle status information of the target vehicle when there is an upgrade requirement for the vehicle system. The processor is also used to determine whether the first vehicle status information meets the upgrade conditions based on the first vehicle status information, wherein the first vehicle status information includes first battery level information, first location information, first fault status information, and / or first vehicle system software version information. The processor is also used to create a vehicle system upgrade task and send it to the target vehicle when the first vehicle status information meets the upgrade conditions, wherein the target vehicle downloads the vehicle system upgrade software package according to the vehicle system upgrade task.

[0034] Specifically, upgrade requirements refer to situations where the in-vehicle system needs to be upgraded due to software version updates, function optimizations, or vulnerability fixes.

[0035] The target vehicle is a specific vehicle that requires an upgrade to its onboard system.

[0036] The first vehicle status information is the target vehicle's current status data obtained by the server when determining whether an upgrade can be initiated.

[0037] The first battery information is the remaining percentage of the target vehicle's power battery, used to determine whether the target vehicle has enough power to support subsequent download and upgrade operations.

[0038] The first location information is the current geographical location data of the target vehicle, used to confirm whether the vehicle is in a suitable upgrade area with stable network and safe environment.

[0039] The first fault status information is whether the target vehicle currently has a fault and the fault-related status data, which is used to check whether there are any fault issues that may affect the upgrade.

[0040] The first vehicle system software version information is the version number of the software currently installed on the target vehicle's vehicle system, used to determine whether it is compatible with the software package to be upgraded.

[0041] The upgrade conditions are based on the stability and security requirements of the in-vehicle system upgrade, which are preset by the server to determine whether the target vehicle is eligible for the upgrade. These standards include sufficient power, suitable location, no faults that would affect the upgrade, and software version compatibility.

[0042] The vehicle system upgrade task is a task file created by the server that includes upgrade-related instructions and parameters.

[0043] The vehicle system upgrade package is a file package that includes the software programs, data, and other contents required for the vehicle system upgrade.

[0044] When there is an upgrade requirement for the vehicle system, the server will actively obtain the first vehicle status information of the target vehicle. This information includes one or more of the following: first battery level information, first location information, first fault status information, and first vehicle system software version information. This information can reflect whether the target vehicle currently has the basic conditions for upgrade.

[0045] Subsequently, the server analyzes and judges the first vehicle status information obtained, and checks whether it meets the preset upgrade conditions to ensure that the upgrade process will not be interrupted or fail due to the vehicle's own status problems.

[0046] If the status information of the first vehicle meets the upgrade conditions, it indicates that the target vehicle currently has the ability to upgrade the software. The server creates a corresponding vehicle system upgrade task and sends the upgrade task to the target vehicle. After receiving the upgrade task, the target vehicle can download the vehicle system upgrade package according to the task requirements, thus preparing for the subsequent actual upgrade operation.

[0047] In this way, by pre-detecting and screening the vehicle status before the upgrade, the upgrade task is only sent to vehicles that meet the conditions. This achieves accurate screening of the vehicle status before the upgrade, effectively avoiding upgrade failures caused by substandard vehicle status. This reduces the waste of network traffic and server processing resources to a certain extent, improves the success rate and stability of the upgrade, and optimizes the user experience during the vehicle system upgrade process.

[0048] Please refer to the following: Figure 2 , Figure 3 and Figure 4In some implementations, the first vehicle status information includes first battery level information, first location information, first fault status information, and first vehicle system software version information. Step 02 includes: 021: If the first power information is greater than or equal to the preset power threshold, the first location information is at the preset location, the first fault state is the normal operating state, and the first vehicle system software version information matches the vehicle system upgrade package, then the first vehicle status information is determined to meet the upgrade conditions.

[0049] In some implementations, the determining module is further configured to determine that the first vehicle status information meets the upgrade conditions when the first power information is greater than or equal to a preset power threshold, the first location information is at a preset location, the first fault state is a normal operating state, and the first vehicle system software version information matches the vehicle system upgrade package.

[0050] In some implementations, the processor is further configured to determine that the first vehicle status information meets the upgrade conditions when the first power information is greater than or equal to a preset power threshold, the first location information is at a preset location, the first fault state is a normal operating state, and the first vehicle system software version information matches the vehicle system upgrade package.

[0051] Specifically, the preset power threshold is a minimum power standard pre-set by the server to determine whether the vehicle's power is sufficient to support the vehicle system upgrade. The preset power threshold can be determined comprehensively based on the size of the vehicle system upgrade package, the download time, and the power consumption during the upgrade process. It is usually set to 30% or higher to ensure that the vehicle has enough power to complete the package download and subsequent upgrade operations, and to avoid upgrade interruption due to insufficient power.

[0052] The preset location is a specific geographical area pre-defined by the server, suitable for upgrading the vehicle's in-vehicle system. This area is typically characterized by stable network signal, no extreme weather, or a safe and controllable surrounding environment. This ensures a stable network connection during the download process, preventing download failures or corruption due to signal fluctuations. Furthermore, in the event of an upgrade failure, it allows staff to quickly locate the vehicle, promptly conduct repairs and troubleshooting, reduce repair and time costs, and ensure the continuity of the upgrade process and the efficiency of subsequent maintenance. Examples include private garages and licensed parking lots.

[0053] Normal operating condition is when all vehicle components and systems are fault-free and function normally, ensuring that all vehicle components and systems can work together normally during the upgrade process.

[0054] The vehicle system upgrade package matching ensures that the current vehicle system software version and the package to be upgraded meet the upgrade requirements in terms of compatibility and adaptability, meaning that the package to be upgraded is suitable for this version of the vehicle system.

[0055] The following is a detailed workflow explanation of the implementation method of this application, which takes the OTA system as the core, relies on the vehicle detection system to complete the collection and verification of vehicle status information, and then promotes the creation of subsequent tasks through the OTA upgrade implementation process, forming a closed-loop management: When there is an upgrade requirement for the in-vehicle system, the OTA system will first detect the vehicle status, and this detection process is specifically executed by the vehicle detection system.

[0056] The vehicle detection system's instruction execution module, relying on its two main functions of vehicle status inspection and vehicle status query, collaborates with various related systems on the service platform to collect primary vehicle status information. Specifically, primary battery level information is obtained from the cloud service platform and transmitted to the vehicle battery management module for synchronous verification. Primary location information is also collected by the cloud service platform and then verified for validity by the vehicle configuration information management module to ensure the accuracy and usability of the location data. Primary fault status information is professionally detected by the fault detection system and transmitted to the vehicle fault management module for organization and classification, clarifying the relevant fault details. Primary onboard system software version information is collected and summarized by the vehicle version management module with the collaborative cooperation of other systems.

[0057] After all status information has been collected and processed, the vehicle detection system integrates and archives all the first vehicle status information through the information aggregation function and feeds it back to the OTA system, laying a solid data foundation for subsequent upgrade condition verification work.

[0058] After obtaining the integrated first vehicle status information, the OTA system verifies the first battery information, first location information, first fault status information, and first vehicle system software version information according to preset judgment criteria. This verification process is implemented by the vehicle detection system's inspection item execution function.

[0059] The OTA system checks whether the first battery information is greater than or equal to the preset battery threshold to ensure that the vehicle has sufficient battery power to support the upgrade process and avoid upgrade interruption due to insufficient battery. It also checks whether the first location information is in the preset location to ensure that the vehicle is in a stable network and safe environment for the upgrade. The system confirms whether the first fault state is a normal operating state to eliminate upgrade anomalies that may be caused by vehicle malfunctions. Finally, it verifies whether the first vehicle system software version information matches the vehicle system upgrade package to ensure that the upgrade package can be installed and run normally on the target vehicle.

[0060] If any verification fails, the OTA system will send a non-compliance alarm notification to the vehicle detection system. Subsequently, the notification delivery module of the vehicle detection system will trigger the corresponding alarm notification. If the battery level is insufficient, a low battery alarm notification will be sent; if there is a fault, a fault alarm notification will be sent; if the location or version is incompatible, a non-compliance alarm notification will be sent. These notifications can be synchronized to relevant personnel through robot notifications, etc., to remind them to adjust the vehicle status.

[0061] If all four checks pass, meaning the first vehicle status information meets the upgrade conditions, the OTA system will automatically generate an in-vehicle system upgrade task, including instructions for downloading the upgrade package, and send it to the target vehicle.

[0062] After receiving the vehicle system upgrade task, the target vehicle will start the software pre-download according to the procedure, and the vehicle detection system will continuously monitor the vehicle status through various functional modules to ensure the vehicle status remains stable during the download process.

[0063] In this way, by clarifying the specific composition of the first vehicle status information and the judgment criteria for upgrade conditions, a comprehensive and strict verification of vehicle upgrade eligibility is achieved. This effectively avoids misjudgment problems caused by missing status information or ambiguous judgment criteria, ensuring that only vehicles that truly meet the upgrade conditions will enter the subsequent upgrade process. This, to a certain extent, improves the success rate and stability of vehicle system upgrades, reduces invalid upgrade operations caused by misjudgment, and reduces the waste of network traffic and server resources. At the same time, the alarm notification mechanism ensures the traceability and adjustability of the upgrade process.

[0064] Please refer to the following: Figure 5 and Figure 6 Methods for upgrading in-vehicle systems include: 04: Upon receiving feedback that the vehicle system upgrade package has been successfully downloaded and the preset upgrade time has arrived, a software upgrade instruction is generated and sent to the target vehicle. The target vehicle then performs the vehicle system upgrade according to the software upgrade instruction and the successfully downloaded vehicle system upgrade package.

[0065] In some implementations, the sending module is further configured to generate a software upgrade instruction and send it to the target vehicle upon receiving feedback that the vehicle system upgrade package has been successfully downloaded and upon reaching a preset upgrade time. The target vehicle then performs a vehicle system upgrade based on the software upgrade instruction and the successfully downloaded vehicle system upgrade package.

[0066] In some implementations, the processor is further configured to generate a software upgrade instruction and send it to the target vehicle upon receiving feedback that the vehicle system upgrade package has been successfully downloaded and upon reaching a preset upgrade time. The target vehicle then performs a vehicle system upgrade based on the software upgrade instruction and the successfully downloaded vehicle system upgrade package.

[0067] Specifically, the feedback information is the signal or data sent by the target vehicle to the server after completing the download of the onboard system upgrade software package, informing the server of the download result.

[0068] The preset upgrade time is a specific time point pre-set by the server based on factors such as user driving habits and network load, suitable for carrying out the actual upgrade operation of the vehicle system software. The preset upgrade time is usually selected during the early morning hours or other times when users use their vehicles less frequently. Users can also customize the preset upgrade time through the vehicle terminal or mobile APP to ensure that the upgrade operation will not affect the user's normal vehicle use.

[0069] The software upgrade command is a command signal generated by the server to instruct the target vehicle to start the on-board system upgrade operation. It usually includes the upgrade start time, upgrade steps, verification rules, and exception handling plan to ensure that the target vehicle can perform the upgrade operation in accordance with the standard procedure.

[0070] Once the target vehicle meets the upgrade requirements and receives the upgrade task from the server, it downloads the corresponding in-vehicle system upgrade package. The pre-download process can be completed during the vehicle's idle time without affecting normal vehicle use, effectively reducing the impact of network fluctuations on the download.

[0071] After the vehicle system upgrade package is downloaded, the target vehicle sends a successful download notification to the server. Upon receiving this notification, the server monitors in real time whether the preset upgrade time has elapsed.

[0072] Upon receiving a successful download notification and reaching the preset upgrade time, the server generates a software upgrade command and sends it to the target vehicle via a secure communication channel. Upon receiving the command, the target vehicle invokes the successfully downloaded vehicle system upgrade package and executes the software upgrade operation according to the steps outlined in the software upgrade command.

[0073] After the upgrade is completed, the target vehicle will send information such as upgrade success, upgrade failure and the reason for failure to the server. After receiving the feedback, the server will complete the closed-loop management of the entire upgrade process.

[0074] In this way, by setting the trigger conditions for the generation and issuance of software upgrade instructions, the orderly management of vehicle system upgrades is achieved. To a certain extent, this avoids the interference to users caused by vehicles starting upgrades at inappropriate times, effectively ensuring that the vehicle system can start upgrades at the preset optimal time, guaranteeing the continuity and stability of vehicle system upgrades, and improving the success rate of vehicle system upgrades.

[0075] Please refer to the following: Figure 6 and Figure 7 In some implementations, the vehicle system upgrade method includes: 05: If the first vehicle status information does not meet the upgrade conditions or if feedback information is received that the vehicle system upgrade package download failed, send a download failure prompt message; 06: After a preset detection interval, re-determine whether the status information of the first vehicle meets the upgrade conditions.

[0076] In some implementations, the sending module is further configured to send a download failure message if the first vehicle status information does not meet the upgrade conditions or if feedback information indicating a failure to download the vehicle system upgrade package is received. The sending module is also configured to re-determine whether the first vehicle status information meets the upgrade conditions at preset detection intervals.

[0077] In some implementations, the processor is further configured to send a download failure message if the first vehicle status information does not meet the upgrade conditions or if feedback information indicating a failure to download the vehicle system upgrade package is received. The processor is also configured to re-determine whether the first vehicle status information meets the upgrade conditions at preset detection intervals.

[0078] Specifically, the download failure message is a signal or data sent by the server to the relevant parties when it detects that the upgrade conditions do not meet the preset upgrade standards or the software package download has failed, informing the relevant parties that the upgrade process is blocked.

[0079] The preset detection duration is the time interval between two verification and upgrade conditions pre-set by the server. It can be flexibly adjusted according to the reason for failure. For example, if the failure is due to insufficient power, the detection duration can be set to 1 hour. If the failure is due to network abnormality, the detection duration can be set to 30 minutes to ensure that relevant personnel have enough time to deal with the problem or wait for the status to improve.

[0080] When there is an upgrade requirement for the in-vehicle system, the server will rely on the vehicle detection system to collect vehicle status information.

[0081] The instruction execution module of the vehicle detection system, through vehicle status check and vehicle status query functions, collaborates with the fault detection system, cloud service platform and other systems of the service platform to obtain the first fault status information, first location information, first battery information and first vehicle system software version information of the target vehicle, respectively. After the information is summarized, it is fed back to the OTA system, which determines whether the first vehicle status information meets the upgrade conditions.

[0082] Subsequently, if the server determines that the first vehicle's status information does not meet the upgrade requirements, or if it receives feedback from the target vehicle indicating that the in-vehicle system upgrade package download failed, the server will send download failure notifications to relevant personnel via vehicle central control screen display, mobile app push notifications, and SMS notifications. For example, if the failure is due to insufficient battery power, a low battery alarm notification will be sent; if it is due to vehicle malfunction, a malfunction alarm notification will be sent; if it is due to location mismatch or version incompatibility, a non-compliance alarm notification will be sent. Some notifications can also be synchronized via chatbot notifications, allowing relevant personnel to promptly understand the cause of the failure and take corresponding vehicle status adjustment measures.

[0083] At the same time, the server will also start a timed detection mechanism. After a preset detection interval, it will obtain the first vehicle status information of the target vehicle through the various functional modules of the vehicle detection system and re-determine whether the upgrade conditions are met.

[0084] For example, the vehicle fault management, vehicle power management, vehicle version management, and vehicle configuration information management modules of the vehicle inspection system continuously track changes in vehicle status, while the inspection item execution function repeatedly implements various verification processes to ensure the accuracy of the re-inspection results.

[0085] If the status information of the first vehicle meets the upgrade conditions, the server will create an in-vehicle system upgrade task and send it to the target vehicle. If the upgrade conditions are still not met, the server will send a prompt message again through the notification delivery module and repeat the above-mentioned timed detection process until the vehicle status meets the upgrade conditions or the preset maximum number of detections is reached.

[0086] If the maximum number of tests is reached and the conditions are still not met, the server will terminate the testing process and send a final prompt message. At this time, the OTA system will remove the upgrade task for that vehicle to avoid unnecessary resource consumption.

[0087] In this way, by setting up a notification mechanism and a timed re-inspection mechanism for upgrade anomalies, effective control over abnormal situations in the upgrade process is achieved. This effectively avoids the direct termination of the upgrade process due to temporary vehicle status non-compliance or network fluctuations. The server can dynamically track changes in vehicle status and provide subsequent upgrade opportunities for vehicles that do not meet the conditions temporarily. This improves the coverage and flexibility of vehicle system upgrades to a certain extent, reduces the waste of upgrade resources caused by abnormal situations, and facilitates timely awareness and handling of upgrade obstacles by relevant parties, thereby improving the manageability of the upgrade process and user experience.

[0088] Please see Figure 8 This application also provides a method for upgrading an in-vehicle system, the method being used in a vehicle, the method comprising: 07: Based on the received vehicle system upgrade task, download the vehicle system upgrade package. When there is an upgrade requirement for the vehicle system, the server obtains the first vehicle status information, determines whether the first vehicle status information meets the upgrade conditions, and creates a vehicle system upgrade task and sends it to the vehicle if the first vehicle status information meets the upgrade conditions.

[0089] This application provides a second device for upgrading an in-vehicle system. The in-vehicle system upgrade method of this application can be implemented by the second device. Specifically, the second device includes a download module. The download module is used to download an in-vehicle system upgrade package according to a received in-vehicle system upgrade task. When there is an upgrade requirement for the in-vehicle system, the server obtains first vehicle status information, determines whether the first vehicle status information meets the upgrade conditions, and if the first vehicle status information meets the upgrade conditions, creates an in-vehicle system upgrade task and sends it to the vehicle.

[0090] This application also provides a server, which includes a memory and a processor. The vehicle system upgrade method of this application can be implemented by the server of this application. Specifically, the memory stores a computer program, and the processor is used to download a vehicle system upgrade software package according to a received vehicle system upgrade task. When there is an upgrade requirement for the vehicle system, the server obtains first vehicle status information, determines whether the first vehicle status information meets the upgrade conditions, and if the first vehicle status information meets the upgrade conditions, creates a vehicle system upgrade task and sends it to the vehicle.

[0091] Specifically, when there is an upgrade requirement for the vehicle system, the server will actively obtain the first vehicle status information of the target vehicle. This information includes one or more of the following: first battery level information, first location information, first fault status information, and first vehicle system software version information. This information can reflect whether the target vehicle currently has the basic conditions for upgrade.

[0092] Subsequently, the server analyzes and judges the first vehicle status information obtained, and checks whether it meets the preset upgrade conditions to ensure that the upgrade process will not be interrupted or fail due to the vehicle's own status problems.

[0093] If the status information of the first vehicle meets the upgrade conditions, it indicates that the target vehicle currently has the ability to upgrade the software. The server creates a corresponding vehicle system upgrade task and sends the upgrade task to the target vehicle. After receiving the upgrade task, the target vehicle can download the vehicle system upgrade package according to the task requirements, thus preparing for the subsequent actual upgrade operation.

[0094] In this way, by pre-detecting and screening the vehicle status before the upgrade, the orderly control of the vehicle system upgrade process is achieved, effectively avoiding upgrade failure caused by blindly starting the download operation when the vehicle does not meet the upgrade conditions. This reduces the probability of download failure to a certain extent, reduces the waste of network traffic and vehicle resources, and ensures the standardization and reliability of the upgrade process.

[0095] Please refer to the following: Figure 9 , Figure 10 and Figure 11 In some implementations, the vehicle system upgrade method includes: 08: After the preset time for executing the vehicle system upgrade task, check whether the vehicle system upgrade package has been downloaded successfully; 09: If the vehicle system upgrade package is successfully downloaded, send a feedback message to the server indicating that the vehicle system upgrade package has been successfully downloaded; 010: If the vehicle system upgrade package fails to download, wait for the preset time interval and then download the vehicle system upgrade package again; 011: If the preset execution end time is reached, terminate the download of the vehicle system upgrade package and send a feedback message to the server indicating that the vehicle system upgrade package download failed.

[0096] In some implementations, the download module is further configured to detect whether the vehicle system upgrade package has been successfully downloaded after a preset time period for executing the vehicle system upgrade task. The download module is also configured to send a feedback message indicating successful download of the vehicle system upgrade package to the server if the download is successful. If the download fails, the download module is also configured to retry downloading the vehicle system upgrade package after a preset waiting time. Finally, the download module is also configured to terminate the download of the vehicle system upgrade package and send a feedback message indicating download failure to the server when a preset execution end time is reached.

[0097] In some implementations, the processor is further configured to detect whether the vehicle system upgrade package has been successfully downloaded after a preset time period for executing the vehicle system upgrade task. The processor is further configured to send feedback information indicating successful download of the vehicle system upgrade package to the server if the download is successful. The processor is further configured to attempt to download the vehicle system upgrade package again after a preset waiting time period if the download fails. The processor is further configured to terminate the download of the vehicle system upgrade package and send feedback information indicating download failure to the server when a preset execution end time is reached.

[0098] Specifically, the preset duration is the time set by the vehicle beforehand for waiting for the download results after the vehicle system upgrade task is executed. It can usually be set according to factors such as the size of the software package and the network transmission rate to ensure that there is enough time to complete the phased download and status detection, for example, 10 minutes or 30 minutes.

[0099] The preset waiting time is the interval between download failures and subsequent attempts to re-initiate the download. This timeframe can usually be set based on the cause of the failure. For example, a shorter waiting time, such as 5 minutes, can be set for failures caused by network interruptions, while a longer waiting time, such as 15 minutes, can be set for failures caused by server timeouts.

[0100] The preset execution end time is the longest valid time for the vehicle system upgrade package download task, which is usually 24 hours.

[0101] After receiving the vehicle system upgrade task from the server, the software pre-download system responds immediately and automatically creates a software package pre-download task. Meanwhile, the vehicle detection system monitors the vehicle's current status in real time to ensure sufficient vehicle resources and stable operation during the download process, providing a fundamental guarantee for the download operation.

[0102] After the vehicle receives the vehicle system upgrade task from the server and begins downloading the software package, in order to ensure timely knowledge of the download progress and results, the system will automatically check the download status of the vehicle system upgrade software package after a preset time period for executing the upgrade task.

[0103] The software pre-download system performs integrity checks and version matching checks on downloaded software packages to confirm whether they are the target versions, thus avoiding subsequent upgrade anomalies caused by damaged software packages or version incompatibility.

[0104] Upon detecting that the vehicle system upgrade package has been successfully downloaded, the vehicle immediately sends a success message to the OTA system, enabling the OTA system to promptly grasp the download completion status and prepare for the issuance of subsequent upgrade commands.

[0105] If a download failure is detected, the software pre-download system will re-initiate the download request after a preset waiting period. This preset waiting period can be reasonably set based on network recovery patterns and vehicle usage scenarios, allowing time for the network or download link to recover, effectively reducing the impact of network fluctuations on downloads and improving download success rates.

[0106] If the preset execution end time is reached during multiple retry downloads, it indicates that the download task has exceeded the reasonable execution cycle. Continuing to retry may be meaningless and will consume vehicle resources. At this time, the software pre-download system will automatically terminate the download operation of the vehicle system upgrade package and send a download failure feedback message to the OTA system.

[0107] After receiving the data, the OTA system can initiate manual intervention or follow-up processing as needed, while recording the cause of failure and synchronizing it to the vehicle detection system to provide data support for subsequent optimization and upgrade processes.

[0108] In this way, by performing download result detection, failure retry, and timeout termination operations, dynamic control of the vehicle-side download process is achieved, effectively improving the download success rate of the vehicle system upgrade software package and avoiding download failures caused by temporary issues such as single network fluctuations. This, to a certain extent, ensures the smooth progress of subsequent upgrade processes. At the same time, clear timeout termination rules prevent download tasks from occupying vehicle resources indefinitely, improving the utilization efficiency of vehicle system resources to a certain extent. Furthermore, timely result feedback ensures information synchronization between the server and the vehicle, enhancing the synergy of the entire upgrade process and optimizing the user experience.

[0109] Please see Figure 12 In some implementations, the vehicle system upgrade method further includes: 012: Based on the software upgrade instruction and the successfully downloaded vehicle system upgrade package, perform the vehicle system upgrade. Specifically, when the server receives feedback that the vehicle system upgrade package has been successfully downloaded and the preset upgrade time has arrived, it generates a software upgrade instruction and sends it to the vehicle.

[0110] In some implementations, the download module is also used to upgrade the vehicle system according to the software upgrade instruction and the successfully downloaded vehicle system upgrade package. In this case, the server generates a software upgrade instruction and sends it to the vehicle when it receives feedback that the vehicle system upgrade package has been successfully downloaded and the preset upgrade time has been reached.

[0111] In some implementations, the processor is also used to perform an on-board system upgrade based on the software upgrade instruction and the successfully downloaded on-board system upgrade package. In this case, the server generates a software upgrade instruction and sends it to the vehicle when it receives feedback that the on-board system upgrade package has been successfully downloaded and a preset upgrade time has been reached.

[0112] Specifically, after the target vehicle meets the upgrade conditions and receives the upgrade task from the server, it downloads the corresponding vehicle system upgrade software package. The pre-download process can be completed during the vehicle's idle time without affecting normal vehicle use, effectively reducing the impact of network fluctuations on the download.

[0113] After the vehicle system upgrade package is downloaded, the target vehicle sends a successful download notification to the server. Upon receiving this notification, the server monitors in real time whether the preset upgrade time has elapsed.

[0114] Upon receiving a successful download notification and reaching the preset upgrade time, the server generates a software upgrade command and sends it to the target vehicle via a secure communication channel. Upon receiving the command, the target vehicle invokes the successfully downloaded vehicle system upgrade package and executes the software upgrade operation according to the steps outlined in the software upgrade command.

[0115] After the upgrade is completed, the target vehicle will send information such as upgrade success, upgrade failure and the reason for failure to the server. After receiving the feedback, the server will complete the closed-loop management of the entire upgrade process.

[0116] In this way, by setting the trigger conditions for the generation and issuance of software upgrade instructions, the orderly management of vehicle system upgrades is achieved. To a certain extent, this avoids the interference to users caused by vehicles starting upgrades at inappropriate times, effectively ensuring that the vehicle system can start upgrades at the preset optimal time, guaranteeing the continuity and stability of vehicle system upgrades, and improving the success rate of vehicle system upgrades.

[0117] Please see Figure 13In some implementations, step 012 includes: 0121: According to the software upgrade instruction, obtain the vehicle's second vehicle status information, which includes vehicle speed information, gear information, second battery level information, second location information, and second fault status information. 0122: If the second vehicle status information meets the burning conditions, perform an onboard system upgrade according to the onboard system upgrade package.

[0118] In some implementations, the download module is further configured to acquire second vehicle status information according to software upgrade instructions, wherein the second vehicle status information includes vehicle speed information, gear information, second battery level information, second location information, and second fault status information. The download module is also configured to perform an on-board system upgrade according to the on-board system upgrade software package if the second vehicle status information meets the burning conditions. In some implementations, the processor is further configured to acquire second vehicle status information according to software upgrade instructions, wherein the second vehicle status information includes vehicle speed information, gear information, second battery level information, second location information, and second fault status information. The processor is also configured to perform an on-board system upgrade according to an on-board system upgrade software package if the second vehicle status information meets the burning conditions.

[0119] Specifically, the second vehicle status information is the current vehicle status data obtained by the vehicle after receiving the software upgrade instruction in order to determine whether it is suitable to immediately perform the upgrade operation. It usually includes vehicle speed information, gear information, second battery information, second location information, and second fault status information. This information can comprehensively reflect the current real-time status of the vehicle to ensure that the vehicle is in a safe and stable state during the upgrade.

[0120] Vehicle speed information is the vehicle's current speed data, used to determine whether the vehicle is parked.

[0121] The gear information is the current gear position of the vehicle's transmission, used to confirm whether the vehicle is in the parking gear.

[0122] The second battery information is the percentage of remaining battery power when the vehicle receives the software upgrade command, used to determine whether there is enough power to complete the upgrade.

[0123] The second location information is the geographical location data of the vehicle when it receives the software upgrade instruction, used to confirm whether the vehicle is still in a safe and suitable upgrade area.

[0124] The second fault status information is the real-time operating status of each system component when the vehicle receives the software upgrade command, which is used to check whether any new faults have occurred before the upgrade.

[0125] The flashing conditions are based on preset safety and stability criteria for flashing the vehicle system software, used to determine whether it is suitable to perform the vehicle system software installation and writing operation. For example, the vehicle speed is 0 km / h, the gear is in park, the second battery level is greater than or equal to 20%, the second location information is within a preset safe zone, and the second fault status information is a fault that does not affect the upgrade.

[0126] After receiving the software upgrade instruction from the server, the vehicle will first perform a secondary verification of the vehicle status. The vehicle will actively obtain its own second vehicle status information and compare the obtained second vehicle status information with the preset burning conditions.

[0127] Once all indicators of the second vehicle status information meet the burning conditions, confirming that the vehicle is currently in a safe and stable state and will not cause safety risks or upgrade anomalies due to the upgrade operation, the vehicle calls the successfully downloaded vehicle system upgrade package and performs the vehicle system upgrade operation according to the established procedure.

[0128] In addition, after the vehicle system upgrade is completed, the vehicle detection system will check the vehicle status information again to determine the upgrade result and send the detection results, including whether the upgrade was successful, failed, and the reason for the failure, to the server.

[0129] If the second vehicle status information does not meet the burning conditions, the vehicle upgrade operation will be paused, and a feedback message indicating that the status is not met will be sent to the server. After receiving the feedback, the server may adjust the upgrade time or send a prompt message to inform the user. The upgrade operation will be re-executed once the vehicle status meets the burning conditions.

[0130] In this way, by obtaining the second vehicle status information and verifying the burning conditions before the upgrade is executed, a second precise control over the timing of vehicle upgrades is achieved. This effectively avoids safety risks and upgrade failures caused by performing upgrades when the vehicle is in an unsuitable state such as driving or malfunctioning. As a result, the safety and reliability of vehicle system upgrades are improved to a certain extent, ensuring vehicle driving safety and user property safety, reducing resource waste caused by upgrade failures, and optimizing user experience.

[0131] This application also provides an electrical device, including: a processor and a memory for storing processor-executable instructions, wherein the processor is configured to execute instructions to implement the methods of some of the above embodiments.

[0132] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the methods described in some of the above embodiments.

[0133] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the methods described in some of the above embodiments.

[0134] It is understood that a computer program includes computer program code. Computer program code can be in the form of source code, object code, executable files, or some intermediate form. Computer-readable storage media can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), and software distribution media, etc.

[0135] In this specification, the terms "specifically," "furthermore," "particularly," "understandably," etc., refer to specific features, structures, materials, or characteristics described in connection with embodiments or examples that are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0136] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of executable request code comprising one or more steps for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order according to the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

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

Claims

1. A method for upgrading an in-vehicle system, characterized in that, The method is used on a server, and the method includes: When there is an upgrade requirement for the in-vehicle system, obtain the first vehicle status information of the target vehicle; Based on the first vehicle status information, determine whether the first vehicle status information meets the upgrade conditions, wherein the first vehicle status information includes first battery information, first location information, first fault status information and / or first vehicle system software version information; If the first vehicle status information meets the upgrade conditions, an in-vehicle system upgrade task is created and sent to the target vehicle, wherein the target vehicle downloads the in-vehicle system upgrade software package according to the in-vehicle system upgrade task.

2. The method according to claim 1, characterized in that, The first vehicle status information includes first battery level information, first location information, first fault status information, and first vehicle system software version information. The step of determining whether the first vehicle status information meets the upgrade conditions based on the first vehicle status information includes: If the first power information is greater than or equal to a preset power threshold, the first location information is at a preset location, the first fault state is a normal operating state, and the first vehicle system software version information matches the vehicle system upgrade package, then the first vehicle status information is determined to meet the upgrade conditions.

3. The method according to claim 2, characterized in that, The method further includes: Upon receiving feedback that the vehicle system upgrade package has been successfully downloaded and upon reaching the preset upgrade time, a software upgrade instruction is generated and sent to the target vehicle. The target vehicle then performs a vehicle system upgrade based on the software upgrade instruction and the successfully downloaded vehicle system upgrade package.

4. The method according to claim 1, characterized in that, The method further includes: If the first vehicle status information does not meet the upgrade conditions or if feedback information indicating that the vehicle system upgrade package download failed is received, a download failure prompt message is sent. After a preset detection interval, it is determined again whether the first vehicle status information meets the upgrade conditions.

5. A method for upgrading an in-vehicle system, characterized in that, The method is used for vehicles, and the method includes: Based on the received vehicle system upgrade task, the server downloads the vehicle system upgrade software package. When there is an upgrade requirement for the vehicle system, the server obtains the first vehicle status information of the vehicle, determines whether the first vehicle status information meets the upgrade conditions, and if the first vehicle status information meets the upgrade conditions, the server creates the vehicle system upgrade task and sends it to the vehicle.

6. The method according to claim 5, characterized in that, The method further includes: After the preset time for executing the vehicle system upgrade task, check whether the vehicle system upgrade package has been successfully downloaded; If the vehicle system upgrade package is successfully downloaded, a feedback message indicating that the vehicle system upgrade package has been successfully downloaded is sent to the server. If the vehicle system upgrade package fails to download, the vehicle system upgrade package will be downloaded again after a preset waiting time. If the preset execution end time is reached, the download of the vehicle system upgrade package is terminated and a feedback message indicating that the download of the vehicle system upgrade package failed is sent to the server.

7. The method according to claim 6, characterized in that, The method further includes: According to the software upgrade instruction and the successfully downloaded vehicle system upgrade package, the vehicle system is upgraded. When the server receives feedback that the vehicle system upgrade package has been successfully downloaded and the preset upgrade time has been reached, it generates a software upgrade instruction and sends it to the vehicle.

8. The method according to claim 7, characterized in that, The process of upgrading the vehicle system according to the software upgrade instructions and the successfully downloaded vehicle system upgrade package includes: According to the software upgrade instruction, the second vehicle status information of the vehicle is obtained, wherein the second vehicle status information includes vehicle speed information, gear information, second battery level information, second location information, and second fault status information. If the second vehicle status information meets the burning conditions, the vehicle system is upgraded according to the vehicle system upgrade software package.

9. An electrical appliance, characterized in that, The method includes a memory and a processor, wherein the memory stores a computer program, which, when executed by the processor, implements the method according to any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by one or more processors, implements the method of any one of claims 1-8.

Images