Firmware upgrading method of vehicle-mounted system, server and vehicle-mounted system

Abstract

The invention provides a firmware upgrading method of a vehicle-mounted system, a server and the vehicle-mounted system.The method is applied to the technical field of intelligent automobiles and comprises the steps that a first firmware upgrading instruction is received, and the first firmware upgrading instruction comprises vehicle type information and firmware information; according to the vehicle type information and the firmware information, a vehicle upgrading list and corresponding first firmware upgrading data are obtained, the first firmware upgrading data comprise a firmware upgrading list and a firmware upgrading file, and the vehicle upgrading list is used for indicating the to-be-upgraded vehicle; and based on the vehicle upgrading list, sending the first firmware upgrading data and the target firmware upgrading instruction to a corresponding vehicle-mounted system, so that the vehicle-mounted system performs firmware upgrading on each to-be-upgraded firmware in the firmware upgrading list according to the target firmware upgrading instruction and the firmware upgrading file. According to the method, the problem firmware can be repaired in time, the problem processing period is shortened, single-vehicle-level matching is achieved, redundancy is reduced, and the firmware upgrading efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of intelligent vehicle technology, and more specifically, to a firmware upgrade method, server, and vehicle system for an in-vehicle system in the field of intelligent vehicle technology. Background Technology

[0002] With the increasing popularity of automobiles, IVI (In-Vehicle Infotainment) has become a core selling point for differentiating vehicles.

[0003] However, when there are defects in the IVI firmware, the relevant technologies cannot fix them in time before the next FOTA (Firmware Over-The-Air) update, resulting in poor user experience, abnormal functions, and even safety hazards. Summary of the Invention

[0004] This application provides a firmware upgrade method for an in-vehicle system, a server, and the in-vehicle system itself. This method can promptly fix problematic firmware, thereby shortening the problem-solving cycle. Furthermore, it achieves precise matching at the vehicle level, reducing redundancy and improving the efficiency of firmware upgrades.

[0005] In a first aspect, a firmware upgrade method for an in-vehicle system is provided. This method is applied to a server and includes: receiving a first firmware upgrade instruction, wherein the first firmware upgrade instruction includes vehicle model information and firmware information; obtaining a vehicle upgrade list and corresponding first firmware upgrade data based on the vehicle model information and firmware information, wherein the first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file, wherein the vehicle upgrade list is used to indicate the vehicle to be upgraded; and sending the first firmware upgrade data and a target firmware upgrade instruction to the corresponding in-vehicle system based on the vehicle upgrade list, so that the in-vehicle system performs firmware upgrades on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

[0006] Based on the aforementioned firmware upgrade method for in-vehicle systems, the firmware upgrade cycle is shortened by instantly distributing scripts. Precise matching is achieved using vehicle model information, updating firmware only on vehicles with defects and reducing unnecessary over-flashing. This not only improves the efficiency of firmware upgrades but also reduces resource consumption and potential risks, while enhancing the reliability and security of the vehicle system, providing users with a more stable and safer driving experience.

[0007] In conjunction with the first aspect, in some possible implementations, the firmware upgrade method for the vehicle system further includes: receiving firmware upgrade result information fed back by the vehicle system, and parsing the firmware upgrade result information to obtain target vehicle information and firmware status information; if the firmware status information includes firmware upgrade failure information, determining the firmware that failed to upgrade based on the firmware upgrade failure information, and obtaining the second firmware upgrade data corresponding to the firmware that failed to upgrade; optimizing the second firmware upgrade data according to the firmware status information and a preset optimization algorithm to generate target firmware upgrade data, and sending the target firmware upgrade data and the second firmware upgrade instruction to the corresponding vehicle system according to the target vehicle information.

[0008] By receiving firmware upgrade results from the vehicle's in-vehicle system, the server can quickly diagnose failures, optimize strategies, and resend data. For example, it first parses multi-dimensional fields such as error codes, failure counts, and network quality, automatically matching optimal strategies like retries and incremental resending to generate target firmware upgrade data and issue a second firmware upgrade command, achieving secondary repair and upgrade. This improves the upgrade success rate, reduces driving safety risks caused by functional abnormalities, reduces repeated recalls and full-package flashing, lowers after-sales costs and user complaints, and ensures vehicles receive continuous and highly reliable defect fixes and version iterations throughout their entire lifecycle.

[0009] In conjunction with the first aspect, in some possible implementations, the firmware upgrade method for the vehicle system further includes: receiving a third firmware upgrade instruction sent by the vehicle system, wherein the third firmware upgrade instruction includes third vehicle information and fault firmware information; obtaining third firmware upgrade data corresponding to the fault firmware information based on the third vehicle information and the fault firmware information, and sending the third firmware upgrade data and the third firmware upgrade instruction to the corresponding vehicle system based on the third vehicle information.

[0010] By proactively triggering a third-party firmware upgrade command through the vehicle's in-vehicle system, the server can quickly respond, complete fault diagnosis, and promptly distribute a dedicated repair package. This process enables instant hot-fix of faulty firmware, shortening the cycle from fault detection to repair completion, thereby improving overall repair efficiency. This automated fault response mechanism reduces reliance on manual intervention, mitigating potential security risks and user experience degradation caused by delayed repairs. Furthermore, because the repair process targets specific faults, it avoids unnecessary updates to fault-free firmware, further optimizing resource utilization and system stability. In addition, instant repair helps reduce vehicle recalls and related costs, improves vehicle operating efficiency and reliability, and provides automakers with a more flexible and economical firmware maintenance strategy.

[0011] Secondly, another method for firmware upgrade of an in-vehicle system is provided. This method is applied to an in-vehicle system and includes: receiving first firmware upgrade data and a target firmware upgrade instruction sent by a server. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file, wherein the firmware upgrade list is used to indicate the firmware to be upgraded in the in-vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded; and performing firmware upgrade on the firmware to be upgraded according to the target firmware upgrade instruction and the firmware upgrade file.

[0012] According to the aforementioned firmware upgrade method for in-vehicle systems, after receiving the first firmware upgrade data and the target firmware upgrade instruction sent by the server, the in-vehicle system verifies and parses this information, identifies the firmware components that need to be updated, and performs the corresponding upgrades. This improves the automation level of firmware upgrades, enhances the accuracy and efficiency of updates, and enables the in-vehicle system to promptly fix defects, improve performance, and introduce new functions, thereby enhancing vehicle reliability and user experience.

[0013] In conjunction with the second aspect, in some possible implementations, after upgrading the firmware to be upgraded according to the target firmware upgrade instruction and firmware upgrade file, the firmware upgrade method of the vehicle system further includes: generating corresponding firmware upgrade result information and feeding the firmware upgrade result information back to the server; determining whether the firmware upgrade has failed based on the firmware upgrade result information, and if it has failed, performing an upgrade rollback on the failed firmware.

[0014] By employing a rollback mechanism, in the event of an upgrade failure, the vehicle system can quickly restore to the original firmware state, ensuring firmware functionality is reset and reducing the likelihood of vehicle function interruptions or security degradation due to patch anomalies. This shortens the duration of faults, reduces user perception and after-sales costs, while meeting the design requirements of automotive electronics for safety, reliability, and rapid recovery.

[0015] In conjunction with the second aspect, in some possible implementations, the firmware upgrade method for the vehicle system further includes: receiving target firmware upgrade data and a second firmware upgrade instruction sent by the server, and performing firmware upgrade on the firmware that failed to be upgraded according to the second firmware upgrade instruction and the target firmware upgrade data.

[0016] By receiving a second firmware upgrade command from the server and optimized target firmware upgrade data, the vehicle system can complete the retry repair and upgrade of failed firmware. This mechanism improves the success rate of firmware upgrades, shortens the defect recovery cycle, and ensures continuous, highly reliable, and low-cost firmware self-healing capabilities throughout the vehicle's entire lifecycle.

[0017] In conjunction with the second aspect, in some possible implementations, the firmware upgrade method for the vehicle system further includes: when a firmware fault is detected in the vehicle system, generating a corresponding third firmware upgrade instruction, wherein the third firmware upgrade instruction includes third vehicle information and faulty firmware information; and sending the third firmware upgrade instruction to the server.

[0018] The in-vehicle system proactively diagnoses the firmware. If an anomaly is detected, a third firmware upgrade command is triggered and uploaded to the cloud server, shortening the cycle from fault detection to repair. Furthermore, the server reduces the redundancy risk associated with batch firmware upgrades for reported vehicles, lowering after-sales recall costs and reducing user complaint rates.

[0019] In combination with the second aspect and the above implementation methods, in some possible implementation methods, the firmware upgrade method of the vehicle system further includes: receiving third firmware upgrade data and third firmware upgrade instructions sent by the server, and upgrading the faulty firmware according to the third firmware upgrade instructions and third firmware upgrade data.

[0020] Firmware upgrades are performed on faulty firmware based on third-party firmware upgrade instructions and data. Differentiated scripts are issued for faulty firmware, reducing redundancy and lowering transmission and storage costs. Simultaneously, this mechanism enables vehicles to perform firmware fault self-diagnosis and self-healing, reducing after-sales recall rates and improving user experience.

[0021] Thirdly, a server is provided, comprising: a receiving module for receiving a first firmware upgrade instruction, wherein the first firmware upgrade instruction includes vehicle model information and firmware information; an obtaining module for obtaining a vehicle upgrade list and corresponding first firmware upgrade data based on the vehicle model information and firmware information, wherein the first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file, wherein the vehicle upgrade list is used to indicate vehicles to be upgraded; and a sending module for sending the first firmware upgrade data and a target firmware upgrade instruction to a corresponding vehicle system based on the vehicle upgrade list, so that the vehicle system performs firmware upgrades on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

[0022] According to the server described in this application, the receiving module receives upgrade instructions containing vehicle model and firmware information, the obtaining module extracts the vehicle upgrade list and upgrade data based on this information, and the sending module sends this data and instructions to the corresponding vehicle system, which then performs the firmware upgrade. This automates the firmware upgrade process, improves efficiency and accuracy, reduces data transmission and storage requirements, reduces operational errors, accelerates the upgrade cycle, and enhances user experience and vehicle manufacturer management efficiency.

[0023] Fourthly, an in-vehicle system is provided, comprising: a communication module for receiving first firmware upgrade data and a target firmware upgrade instruction sent by a server, wherein the first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file, wherein the firmware upgrade list is used to indicate the firmware to be upgraded in the in-vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded; and an upgrade module for performing firmware upgrade on the firmware to be upgraded according to the target firmware upgrade instruction and the firmware upgrade file.

[0024] According to the vehicle-mounted system of this application, a communication module is responsible for receiving first firmware upgrade data and target firmware upgrade instructions sent by a server. The firmware upgrade list clearly indicates the vehicle-mounted firmware that needs to be upgraded, while the firmware upgrade file contains the operations and data required to perform the upgrade. The upgrade module then upgrades the specified firmware according to these instructions and data, realizing automated and intelligent upgrades of the vehicle-mounted system. This not only improves the efficiency and accuracy of firmware upgrades and reduces manual intervention but also ensures the rational use of resources, thereby enhancing the performance and reliability of the vehicle-mounted system and providing users with a better driving experience. Attached Figure Description

[0025] Figure 1 This is an environmental architecture diagram of a firmware upgrade method for an in-vehicle system according to some embodiments of this application; Figure 2 This is a flowchart illustrating a firmware upgrade method for an in-vehicle system according to some embodiments of this application; Figure 3 This is a flowchart illustrating a firmware upgrade method for an in-vehicle system according to other embodiments of this application; Figure 4 An interactive diagram illustrating a firmware upgrade method for an in-vehicle system according to a specific embodiment of this application; Figure 5 An interactive diagram illustrating a firmware upgrade method for an in-vehicle system according to another specific embodiment of this application; Figure 6 A block diagram of a server according to some embodiments of this application; Figure 7 This is a block diagram of an in-vehicle system according to some embodiments of this application. Detailed Implementation

[0026] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0027] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0028] Traditional IVI firmware upgrade methods often use FOTA (Firmware Over-The-Air). FOTA is a technology that allows for remote upgrades of vehicle firmware without a physical connection. It pushes new firmware packages directly to the vehicle terminal via a wireless network, enabling rapid iteration and bug fixing of IVI core modules.

[0029] However, when defects are found in the IVI firmware, relying on FOTA to upgrade the firmware has the following problems: 1. From problem discovery, code fixing, and full package integration to multiple rounds of bench / road verification, and then to production scheduling and push, the entire chain has a long cycle and a long defect window period.

[0030] 2. A complete firmware package must be produced and verified. Any changes to the driver, kernel, or application versions must be retested, which is a complex, time-consuming, and resource-intensive process.

[0031] 3. The vehicles are widely distributed, and the hardware configurations and software versions of different types vary greatly. A unified FOTA package can only be applied in a "one-size-fits-all" manner, making it difficult to provide dedicated repairs and upgrades for specific batches or individual vehicle issues.

[0032] 4. Framework layer (system framework layer) problems and interface logic errors that occur during the operation of the vehicle system are located in the core of the system and are difficult to fix and upgrade through application layer patches.

[0033] 5. Vehicle systems have extremely high requirements for stability and security, and cannot be frequently flashed with full packages for firmware upgrades like ordinary mobile devices.

[0034] Before explaining the firmware upgrade method for the vehicle system provided in the embodiments of this application, the environmental architecture involved in the embodiments of this application will be described first. See Figure 1 .

[0035] The environmental architecture involved in this application embodiment includes a server 110 and multiple vehicle systems (such as vehicle system 121, vehicle system 122, vehicle system 123, etc.). Figure 1 Taking three in-vehicle systems as an example, the specific number of in-vehicle systems depends on the actual situation and is not limited here.

[0036] Server 110 is responsible for storing and managing various data required for firmware upgrades, including firmware information (such as firmware identifier and firmware version), upgrade scripts, and vehicle information, such as vehicle type and VIN (Vehicle Identification Number). Server 110 not only generates firmware upgrade instructions but also sends these instructions, along with relevant files and data required for the firmware upgrade, to the corresponding in-vehicle system, guiding it to complete the firmware repair and upgrade. Furthermore, Server 110 establishes a cloud-based script distribution mechanism, using a cloud-based script management platform to distribute scripts differently based on the vehicle's VIN code. Server 110 stores repair scripts for different VINs or vehicle models, supporting script version management, canary releases, and rollback mechanisms to ensure the flexibility and security of firmware upgrades.

[0037] Server 110 also manages secure and reliable communication with the vehicle system, ensuring accurate data transmission. After firmware upgrades are completed, server 110 collects and analyzes upgrade result information from the vehicle system, evaluates the upgrade effect, and performs necessary optimizations accordingly. In the event of upgrade failure, server 110 can intelligently generate remedial instructions and data to guide the vehicle system in fault recovery.

[0038] The in-vehicle system refers to the collective term for all electronic control and information interaction systems integrated within a vehicle, used for real-time control, status monitoring, fault diagnosis, and remote upgrades of various functional domains of the vehicle. Taking in-vehicle system 121 as an example, the in-vehicle system may include a remote service module, a Frida (Frida Dynamic Instrumentation Toolkit) engine, and a system framework layer.

[0039] The remote service module acts as a bridge between the in-vehicle system and the outside world, responsible for exchanging data with the cloud server. It possesses robust network communication capabilities, enabling it to receive scripts and instructions from the cloud and execute them locally. Typically running in the background, the remote service module ensures a stable and secure data transmission channel between the vehicle and the automaker's cloud server, enabling secure data encryption and decryption.

[0040] The Frida engine can dynamically modify the system framework layer code of an in-vehicle system without restarting the system. Utilizing code injection and function hooking techniques, the Frida engine can instantly intercept and adjust application operations, enabling efficient dynamic changes to both Java-written and native code components, providing strong support for the flexibility and scalability of in-vehicle systems.

[0041] The system framework layer is the core of the in-vehicle system, providing a foundational platform upon which various applications and services can run. The system framework layer manages the various resources of the in-vehicle system, including hardware interfaces, system services, and application programming interfaces, ensuring that they can work together efficiently and securely.

[0042] Figure 2 This is a flowchart illustrating a firmware upgrade method for an in-vehicle system according to some embodiments of this application. The firmware upgrade method for the in-vehicle system is applied to a server.

[0043] Reference Figure 2 The method may include: S210 receives a first firmware upgrade command, which includes vehicle model information and firmware information.

[0044] For example, after confirming a common defect in the firmware of a certain model batch through multiple channels such as market research, after-sales work orders, vehicle connectivity logs, or recall warnings, the company initiates a unified repair and upgrade of the firmware defect for that model.

[0045] The first firmware upgrade instruction is a firmware upgrade task instruction issued by an engineer, which instructs the cloud server to send relevant firmware upgrade instructions and data to vehicles within the upgrade scope. Vehicle model information is a set of vehicle attributes used to determine the upgrade scope, such as vehicle model number and VIN. Firmware information is a set of data describing the firmware to be upgraded, which may include firmware identification code and version information.

[0046] Specifically, when market research, after-sales feedback, or vehicle logs confirm that a certain firmware of a certain model or batch of vehicles has a common defect, the company's R&D engineers will create and issue the first firmware upgrade command. This command is received and parsed by the server, and its content includes model information used to lock the upgrade scope, as well as firmware information used to describe the firmware to be upgraded.

[0047] S220 obtains the vehicle upgrade list and the corresponding first firmware upgrade data based on the vehicle model information and firmware information. The first firmware upgrade data includes the firmware upgrade list and the firmware upgrade file. The vehicle upgrade list is used to indicate the vehicles to be upgraded.

[0048] Specifically, the automaker's database stores a mapping table between vehicle model information and VINs, used to store vehicle model information and all corresponding VINs, supporting the rapid retrieval of all vehicles to be upgraded by model for upgrade tasks. In addition, the database also stores all firmware information, such as firmware identification numbers, firmware version numbers, and checksums, providing a basis for version comparison and file integrity verification. Furthermore, a firmware repair and upgrade script library written by R&D engineers stores scripts (such as Python scripts) for known defects, which the server can directly call when generating upgrade tasks, enabling rapid defect repair and upgrades and traceable version management.

[0049] The vehicle upgrade list refers to the set of VINs for vehicles that meet the vehicle model information. The first firmware upgrade data refers to the complete data packet prepared by the server to complete this upgrade, consisting of two parts: the firmware upgrade list and the firmware upgrade file. The firmware upgrade list is a list containing the identifiers of all firmware to be upgraded, the current firmware version number, and the target version number, with each item corresponding to the others. The firmware upgrade file is a hotfix script file (e.g., a Python script) used to fix the firmware defects.

[0050] Specifically, after receiving the first firmware upgrade instruction, the server retrieves the vehicle model information and firmware information to be repaired and upgraded. It then immediately searches the vehicle manufacturer's database, first extracting all VINs matching the vehicle model information from the vehicle model information and VIN mapping table to form a vehicle upgrade list; subsequently, based on the firmware information, it reads the corresponding current firmware version, target version, and checksum from the firmware data to assemble the firmware upgrade list. Finally, it retrieves pre-written firmware upgrade files (e.g., Python scripts) from the script library and combines them to form the first firmware upgrade data.

[0051] S230: Based on the vehicle upgrade list, the first firmware upgrade data and the target firmware upgrade instruction are sent to the corresponding vehicle system, so that the vehicle system can perform firmware upgrades on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

[0052] Among them, the target firmware upgrade instruction is an operation command encapsulated by the server based on the first firmware upgrade data, which is used to inform the vehicle system to complete the upgrade task for the listed firmware at a specified time and according to a predetermined strategy.

[0053] Specifically, the server retrieves the VINs of all vehicles with firmware upgrades from the vehicle upgrade list. Then, based on the VIN, the server pushes the packaged first firmware upgrade data and the target firmware upgrade command to the target vehicle. Upon receiving this data, the target vehicle's onboard system sequentially calls the firmware upgrade files (scripts) according to the target firmware upgrade command, performing bug fixes and version updates for each firmware item listed in the firmware upgrade list.

[0054] First, the server receives the initial firmware upgrade command issued by the company's engineers after identifying common defects through market research or after-sales data. This command contains vehicle model information (e.g., vehicle code, VIN range) and firmware information (e.g., firmware identifier, current and target versions). Then, the server retrieves all vehicles to be upgraded from the vehicle manufacturer's database's vehicle model information and VIN mapping table to form a vehicle upgrade list. Simultaneously, it reads the firmware upgrade list based on the firmware information to obtain the identifier, version number, and checksum of all firmware to be upgraded and repaired. The corresponding firmware upgrade file (i.e., a script file, such as a Python script) is extracted from the script library, and the firmware upgrade list and firmware upgrade file are merged to form the first firmware upgrade data. Finally, the server issues the first firmware upgrade data and the target firmware upgrade command to each vehicle according to the vehicle upgrade list. After verifying the command within the scheduled time window, the vehicle system calls the firmware upgrade file to dynamically patch each firmware item in the firmware upgrade list, completing zero-reboot defect repair and version update.

[0055] R&D engineers submit scripts, which are then immediately distributed to the server, eliminating the need for full package compilation, bench testing, and road verification, thus shortening the upgrade cycle. By mapping vehicle information to VINs, it ensures that packages are only applied to defective vehicles, achieving precise matching at the vehicle level, avoiding over-flashing, and improving the efficiency of firmware repair and upgrades.

[0056] In some embodiments of this application, the firmware upgrade method for an in-vehicle system further includes: receiving firmware upgrade result information fed back by the in-vehicle system, and parsing the firmware upgrade result information to obtain target vehicle information and firmware status information; if the firmware status information includes firmware upgrade failure information, determining the firmware that failed to upgrade based on the firmware upgrade failure information, and obtaining the second firmware upgrade data corresponding to the firmware that failed to upgrade; optimizing the second firmware upgrade data according to the firmware status information and a preset optimization algorithm to generate target firmware upgrade data, and sending the target firmware upgrade data and the second firmware upgrade instruction to the corresponding in-vehicle system according to the target vehicle information.

[0057] The firmware upgrade result information refers to the message sent back by the vehicle system after completing the upgrade operation, containing target vehicle information and firmware status information. Target vehicle information refers to the identification of the vehicle corresponding to this upgrade, such as the VIN of the vehicle sending the firmware upgrade result information. This information is used by the server to identify the vehicle sending the update, ensuring a one-to-one correspondence between upgrade records and vehicles and preventing information misalignment. Firmware status information includes a description of the upgrade operation result and can be used to indicate whether each firmware upgrade was successful or failed.

[0058] The second firmware upgrade data refers to the firmware upgrade list and firmware upgrade file extracted again, corresponding to the firmware that failed to upgrade, which is used for secondary distribution to retry repair and upgrade.

[0059] The preset optimization algorithm refers to the set of failure attribution strategies built into the server. It automatically selects retry and other optimization methods based on fields such as error codes, number of failures, and network quality in the firmware status information, and generates corresponding upgrade parameters. The preset optimization algorithm can be set by relevant personnel according to actual needs; no specific restrictions are imposed here. The target firmware upgrade data refers to the firmware upgrade list and firmware upgrade files obtained after processing the second firmware upgrade data using the preset optimization algorithm, with adjusted upgrade strategies and / or upgrade file content. It is used to replace the second firmware upgrade data.

[0060] The second firmware upgrade command refers to the control command regenerated by the server for retrying the upgrade, which is used to inform the vehicle system to perform a second firmware repair and upgrade.

[0061] Specifically, the server receives the firmware upgrade result information returned by the vehicle system, parses it to obtain the target vehicle information (such as VIN) and firmware status information; if the firmware status information contains a firmware upgrade failure information identifier, the failed firmware is locked, and the corresponding second firmware upgrade data is retrieved from the database. Subsequently, the built-in preset optimization algorithm automatically selects strategies such as retry, incremental retransmission, full replacement, segmented download, or extended charging window based on fields such as error code, number of failures, and network quality to optimize the second firmware upgrade data and generate the adjusted target firmware upgrade data; at the same time, a second firmware upgrade command is issued to notify the vehicle system that this is a secondary repair and upgrade task.

[0062] By receiving firmware upgrade results from the vehicle's onboard system, the server can quickly diagnose failures, optimize strategies, and resend data. It first parses multi-dimensional fields such as error codes, failure counts, and network quality, then automatically matches optimal strategies like retrying, incremental resending, full replacement, or extending the charging window. This generates target firmware upgrade data and issues a second firmware upgrade command, achieving precise secondary repair. This improves upgrade success rates, reduces driving safety risks caused by functional abnormalities, and minimizes repeated recalls and full-package flashing, lowering after-sales costs and user complaints. It ensures vehicles receive continuous and highly reliable defect fixes and version iterations throughout their entire lifecycle.

[0063] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: receiving a third firmware upgrade instruction sent by the vehicle system, wherein the third firmware upgrade instruction includes third vehicle information and fault firmware information; obtaining third firmware upgrade data corresponding to the fault firmware information based on the third vehicle information and the fault firmware information, and sending the third firmware upgrade data and the third firmware upgrade instruction to the corresponding vehicle system based on the third vehicle information.

[0064] The third firmware upgrade command refers to the upgrade request for defective firmware actively reported by the vehicle system, used to notify the server to immediately obtain and issue the corresponding repair data. The third vehicle information refers to the identification of the reported vehicle, such as the VIN, used by the server to locate the target vehicle. The faulty firmware information refers to the abnormal firmware identifier detected by the vehicle system's self-detection, including the firmware identifier number, current version, and fault code, used by the server to match the corresponding third firmware upgrade data. The third firmware upgrade data refers to the firmware repair data package obtained by the server based on the faulty firmware information, containing a firmware upgrade list and firmware upgrade files, used for immediate patching or version replacement of the abnormal firmware.

[0065] Specifically, during operation, the vehicle-mounted system detects a functional anomaly through real-time self-checks or periodic diagnostics. Upon this detection, it immediately generates a third-party firmware upgrade command locally and sends it to the server. The server receives the command, parses it to obtain third-party vehicle information (such as the VIN) and faulty firmware information (such as the faulty firmware identifier, current version, and fault code). Then, the server searches its database based on the vehicle and firmware information to extract the corresponding third-party firmware upgrade data, including a firmware upgrade list (such as firmware identifier, target version number, and identifier) ​​and a firmware upgrade file (such as a Python script). The cloud server then encrypts the third-party firmware upgrade data along with a new third-party firmware upgrade command (including task sequence number, immediate execution flag, script download token, and retry policy) and sends it back to the faulty vehicle. Finally, the vehicle's onboard system dynamically repairs the faulty firmware.

[0066] By proactively triggering a third-party firmware upgrade command through the vehicle's in-vehicle system, the server can quickly respond, complete fault diagnosis, and promptly distribute a dedicated repair package. This process enables instant hot-fix of faulty firmware, shortening the cycle from fault detection to repair completion, thereby improving overall repair efficiency. This automated fault response mechanism reduces reliance on manual intervention, mitigating potential security risks and user experience degradation caused by delayed repairs. Furthermore, because the repair process targets specific faults, it avoids unnecessary updates to fault-free firmware, further optimizing resource utilization and system stability. In addition, instant repair helps reduce vehicle recalls and related costs, improves vehicle operating efficiency and reliability, and provides automakers with a more flexible and economical firmware maintenance strategy.

[0067] Figure 3 This is a flowchart of a firmware upgrade method for an in-vehicle system according to other embodiments of this application.

[0068] The firmware upgrade method for vehicle systems is applied to vehicle terminals, refer to Figure 3 The firmware upgrade method for this vehicle system may include: S310 receives first firmware upgrade data and target firmware upgrade instruction sent by the server. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The firmware upgrade list is used to indicate the firmware to be upgraded in the vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded.

[0069] Specifically, the vehicle system receives first firmware upgrade data and target firmware upgrade instructions from the server. The first firmware upgrade data consists of two parts: one part is a firmware upgrade list, indicating the various firmware components in the vehicle system that need to be updated and their related information (such as firmware identifier code, target identifier code, and checksum); the other part is a firmware upgrade file, i.e., a script (such as a Python script), used to perform upgrade operations on the listed firmware components.

[0070] S320 performs firmware upgrades on the firmware to be upgraded according to the target firmware upgrade instructions and firmware upgrade files.

[0071] Specifically, the vehicle system first verifies the received firmware upgrade file to confirm its completeness and correctness. Then, based on the information in the firmware upgrade list, it identifies the firmware components that need upgrading. The vehicle system then repairs and upgrades these firmware components according to the instructions in the firmware upgrade file.

[0072] The vehicle system first receives initial firmware upgrade data and target firmware upgrade instructions from the server. This initial firmware upgrade data consists of two parts: a firmware upgrade list, which clearly identifies the firmware components in the vehicle system that need to be updated and their related information; and a firmware upgrade file, typically a script, such as a Python script, which contains the specific operations required to perform the upgrade. The vehicle system then verifies the completeness and correctness of the firmware upgrade file, identifies the firmware components to be upgraded based on the firmware upgrade list, and performs the upgrade operations on these components according to the instructions in the firmware upgrade file, thus completing the entire firmware upgrade process.

[0073] This improves the automation level of firmware repair and upgrades, enhances the accuracy and efficiency of updates, and enables the vehicle system to promptly fix defects, improve performance, and introduce new features, thereby enhancing vehicle reliability and user experience.

[0074] In some embodiments of this application, after the firmware to be upgraded is upgraded according to the target firmware upgrade instruction and firmware upgrade file, the firmware upgrade method of the vehicle system further includes: generating corresponding firmware upgrade result information and feeding back the firmware upgrade result information to the server; determining whether the firmware upgrade has failed based on the firmware upgrade result information, and if it has failed, performing an upgrade rollback on the failed firmware.

[0075] Upgrade rollback refers to the process where, in the event of an upgrade failure or verification anomaly, the vehicle system immediately uninstalls the firmware upgrade file (such as a Python script) that was written in the current upgrade, restores the relevant parameters of the firmware (such as firmware functions, version number, and checksum) to the state before the upgrade, and restores the abnormal firmware to the stable version before the failure.

[0076] Specifically, after the vehicle system upgrades the firmware to be upgraded according to the target firmware upgrade instruction and firmware upgrade file (such as a Python script), it immediately compares the firmware-related parameters, such as firmware checksums. If the values ​​do not match the target values ​​or an upgrade failure signal is received, a rollback is immediately triggered. The system further stops the execution of the firmware upgrade file (such as the Python script), unloads the loaded firmware upgrade file (such as the Python script), ensures the firmware is restored to its stable state before the upgrade, and reports the rollback completion result to the server.

[0077] By employing a rollback mechanism, in the event of an upgrade failure, the vehicle system can quickly restore to the original firmware state, ensuring firmware functionality is reset and reducing the likelihood of vehicle function interruptions or security degradation due to patch anomalies. This shortens the duration of faults, reduces user perception and after-sales costs, while meeting the design requirements of automotive electronics for safety, reliability, and rapid recovery.

[0078] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: receiving target firmware upgrade data and a second firmware upgrade instruction sent by a server, and performing firmware upgrade on the firmware that failed to be upgraded according to the second firmware upgrade instruction and the target firmware upgrade data.

[0079] Specifically, after detecting an upgrade failure, the server adjusts the second firmware upgrade data using a preset optimization algorithm, generates target firmware upgrade data, and encapsulates it into a second firmware upgrade command, which is then sent to the vehicle system. Upon receiving the command, the vehicle system begins firmware repair and upgrade work under idle conditions with sufficient power and a stable network. It first verifies the target firmware upgrade data; if it is correct, it stops running the current failed firmware and repairs and upgrades the failed firmware based on the optimized target firmware upgrade data.

[0080] By receiving a second firmware upgrade command from the server and optimized target firmware upgrade data, the vehicle system can complete the retry repair upgrade of failed firmware. This mechanism improves the success rate of firmware upgrades, shortens the defect recovery cycle, and ensures that the vehicle can continuously, reliably, and cost-effectively obtain firmware self-healing capabilities throughout its entire lifecycle.

[0081] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: when a firmware fault is detected in the vehicle system, generating a corresponding third firmware upgrade instruction, wherein the third firmware upgrade instruction includes third vehicle information and faulty firmware information; and sending the third firmware upgrade instruction to a server.

[0082] Specifically, when the vehicle system detects a firmware fault through periodic self-diagnosis or abnormal interruption during operation, it immediately generates a third firmware upgrade command locally. This third firmware upgrade command contains third vehicle information (such as VIN) and faulty firmware information (such as faulty firmware identifier, current version number, fault code, etc.). Furthermore, the vehicle system uploads this third firmware upgrade command to the server.

[0083] The in-vehicle system proactively diagnoses the firmware. If an anomaly is detected, a third firmware upgrade command is triggered and uploaded to the cloud server, shortening the cycle from fault detection to repair. Furthermore, the server reduces the redundancy risk associated with batch firmware upgrades for reported vehicles, lowering after-sales recall costs and reducing user complaint rates.

[0084] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: receiving third firmware upgrade data and third firmware upgrade instructions sent by a server, and upgrading the faulty firmware according to the third firmware upgrade instructions and third firmware upgrade data.

[0085] Specifically, after the vehicle system actively reports a fault, it immediately receives the third firmware upgrade command and corresponding third firmware upgrade data from the server. Under idle conditions with sufficient power and a stable network, the firmware repair and upgrade process begins. First, the third firmware upgrade command is verified; once confirmed to be correct, the current failed firmware is stopped, and the failed firmware is repaired and upgraded based on the optimized third firmware upgrade data.

[0086] Firmware upgrades are performed on faulty firmware based on third-party firmware upgrade instructions and data. Differentiated scripts are issued for faulty firmware, reducing redundancy and lowering transmission and storage costs. Simultaneously, this mechanism enables vehicles to perform firmware fault self-diagnosis and self-healing, reducing after-sales recall rates and improving user experience.

[0087] Figure 4 This is an interactive diagram illustrating a firmware upgrade method for an in-vehicle system according to a specific embodiment of this application. (Refer to...) Figure 4 The firmware upgrade method for the vehicle system in this application may include: S401 sends the first firmware upgrade command.

[0088] For example, after confirming a common defect in a batch of firmware for a specific vehicle model through multiple channels such as market research, after-sales work orders, vehicle connectivity logs, or recall warnings, the R&D engineer selects the vehicle model and firmware version to be upgraded and issues a first firmware upgrade command. This first firmware upgrade command includes vehicle model information and firmware information. Vehicle model information includes vehicle type, VIN, etc., and firmware information includes firmware identification number, current version number, target version number, etc. The first firmware upgrade command is received by the server.

[0089] S402, retrieve the vehicle upgrade list and the corresponding first firmware upgrade data.

[0090] Specifically, after receiving the first firmware upgrade instruction, the server queries the database to obtain a list of vehicles that meet the criteria for upgrade. This vehicle upgrade list contains all vehicle VINs that need to be upgraded. Simultaneously, the server extracts firmware upgrade data matching the firmware information from the firmware library, including a firmware upgrade list and firmware upgrade files. The firmware upgrade list details key information such as the identifier code, current version number, and target version number of all firmware to be upgraded. The firmware upgrade files contain the actual upgrade scripts or files.

[0091] S403 sends the first firmware upgrade data and the target firmware upgrade command according to the vehicle upgrade list.

[0092] Specifically, the server packages the first firmware upgrade data and the target firmware upgrade instruction according to the vehicle upgrade list and sends them to the vehicle system. The target firmware upgrade instruction may include information such as task sequence number, execution time, and upgrade strategy. After receiving the first firmware upgrade data, the vehicle system performs digital signature verification to ensure the integrity and security of the data.

[0093] S404 performs a firmware upgrade based on the target firmware upgrade instruction and firmware upgrade file.

[0094] Specifically, the vehicle system determines the firmware components that need to be upgraded based on the information in the target firmware upgrade instruction. The vehicle system downloads the firmware upgrade file and executes the upgrade operation through the Frida engine within the scheduled upgrade time. After the upgrade is complete, the system performs a version verification to ensure that the firmware has been updated correctly.

[0095] S405, feedback on upgrade results.

[0096] Specifically, the onboard system sends the upgrade result information back to the server. This upgrade result information may include the vehicle VIN, firmware version number, and upgrade status (e.g., success or failure). After receiving the feedback information, the server parses and records it in the database for subsequent analysis and optimization.

[0097] Through the above implementation methods, the firmware upgrade process of the vehicle system is automated and intelligent, which improves the efficiency and accuracy of the upgrade, reduces manual intervention, reduces the risk of operational errors, and upgrades specific firmware, thereby reducing redundancy and saving resources.

[0098] Figure 5 This is an interactive diagram illustrating a firmware upgrade method for an in-vehicle system according to another specific embodiment of this application. (Refer to...) Figure 5 The firmware upgrade method for the vehicle system in this application may further include: S501, a firmware malfunction was detected in the vehicle system.

[0099] Specifically, during operation, the vehicle system detects firmware faults through self-tests or abnormal interruptions. The vehicle system records fault information, including firmware identifier number, current version, and fault code.

[0100] S502 generates the third firmware upgrade command.

[0101] Specifically, the onboard system generates a third firmware upgrade command based on the detected fault information. This third firmware upgrade command contains third vehicle information (such as the VIN code of the faulty vehicle) and faulty firmware information. After being digitally signed, the third firmware upgrade command is reported to the server through the onboard system's remote communication module.

[0102] S503 obtains the third firmware upgrade data corresponding to the fault firmware information based on the third vehicle information and the fault firmware information.

[0103] Specifically, after receiving the third firmware upgrade command, the server retrieves the corresponding third firmware upgrade data from the database based on the third vehicle information and the faulty firmware information. The third firmware upgrade data includes the repair script, target version number, and checksum.

[0104] S504 sends third firmware upgrade data and third firmware upgrade instructions based on third vehicle information.

[0105] Specifically, the server packages the third firmware upgrade data and the third firmware upgrade command, and sends them to the vehicle system. After receiving the data packet, the vehicle system can perform digital signature verification to ensure the integrity and security of the data.

[0106] S505 performs firmware upgrades on faulty firmware based on third firmware upgrade instructions and third firmware upgrade data.

[0107] Specifically, the vehicle system determines the firmware components that need to be upgraded based on the information in the third firmware upgrade instruction. The vehicle system downloads the third firmware upgrade data and performs the upgrade operation through the Frida engine within the scheduled upgrade time. After the upgrade is completed, the system performs a version verification to ensure that the firmware has been updated correctly.

[0108] Through the above implementation methods, the vehicle-mounted system can quickly respond to and repair firmware faults, improving system reliability and stability. The server receives fault information from the vehicle-mounted system and provides targeted upgrade data for targeted repair. Upon receiving the upgrade data, the vehicle-mounted system can automatically execute the upgrade operation without manual intervention, improving upgrade efficiency and user experience.

[0109] Figure 6 This is a block diagram of a server provided in an embodiment of this application. (Refer to...) Figure 6 The server may include a receiving module 610, an acquisition module 620, and a sending module 630.

[0110] The receiving module 610 is used to receive a first firmware upgrade instruction, which includes vehicle model information and firmware information; the obtaining module 620 is used to obtain a vehicle upgrade list and corresponding first firmware upgrade data based on the vehicle model information and firmware information, the first firmware upgrade data including a firmware upgrade list and a firmware upgrade file, wherein the vehicle upgrade list is used to indicate the vehicle to be upgraded; the sending module 630 is used to send the first firmware upgrade data and the target firmware upgrade instruction to the corresponding vehicle system according to the vehicle upgrade list, so that the vehicle system can perform firmware upgrades on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

[0111] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: a receiving module 610 receiving firmware upgrade result information fed back by the vehicle system, and parsing the firmware upgrade result information to obtain target vehicle information and firmware status information; if the firmware status information includes firmware upgrade failure information, the receiving module 610 determines the firmware that failed to upgrade based on the firmware upgrade failure information, and the acquisition module acquires the second firmware upgrade data corresponding to the firmware that failed to upgrade; the acquisition module 620 optimizes the second firmware upgrade data according to the firmware status information and a preset optimization algorithm to generate target firmware upgrade data, and the sending module 630 sends the target firmware upgrade data and the second firmware upgrade instruction to the corresponding vehicle system according to the target vehicle information.

[0112] In some embodiments of this application, the firmware upgrade method for the vehicle system further includes: a receiving module 610 receiving a third firmware upgrade instruction sent by the vehicle system, wherein the third firmware upgrade instruction includes third vehicle information and fault firmware information; an obtaining module 620 obtaining third firmware upgrade data corresponding to the fault firmware information based on the third vehicle information and the fault firmware information; and a sending module 630 sending the third firmware upgrade data and the third firmware upgrade instruction to the corresponding vehicle system based on the third vehicle information.

[0113] Figure 7 This is a block diagram of an in-vehicle system according to some embodiments of this application. (Refer to...) Figure 7 The vehicle-mounted system may include a communication module 710 and an upgrade module 720.

[0114] The communication module 710 is used to receive first firmware upgrade data and target firmware upgrade instructions sent by the server. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The firmware upgrade list is used to indicate the firmware to be upgraded in the vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded. The upgrade module 720 is used to upgrade the firmware to be upgraded according to the target firmware upgrade instructions and the firmware upgrade file.

[0115] In some embodiments of this application, after the upgrade module 720 performs a firmware upgrade on the firmware to be upgraded according to the target firmware upgrade instruction and firmware upgrade file, it is further configured to: generate corresponding firmware upgrade result information and feed the firmware upgrade result information back to the server; the upgrade module 720 determines whether the firmware upgrade has failed based on the firmware upgrade result information, and if it fails, it performs an upgrade rollback on the failed firmware.

[0116] In some embodiments of this application, the communication module 710 receives target firmware upgrade data and a second firmware upgrade instruction sent by the server, and the upgrade module 720 performs firmware upgrade on the firmware that failed to be upgraded according to the second firmware upgrade instruction and the target firmware upgrade data.

[0117] In some embodiments of this application, when a firmware failure is detected in the vehicle system, the upgrade module 720 generates a corresponding third firmware upgrade instruction, wherein the third firmware upgrade instruction includes third vehicle information and faulty firmware information; the communication module 710 sends the third firmware upgrade instruction to the server.

[0118] In some embodiments of this application, the communication module 710 receives third firmware upgrade data and third firmware upgrade instructions sent by the server, and the upgrade module 720 performs firmware upgrade on the faulty firmware according to the third firmware upgrade instructions and third firmware upgrade data.

[0119] It should be noted that for details not disclosed in this application regarding the server and vehicle system, please refer to the details disclosed in the firmware upgrade method of the vehicle system in this application, which will not be elaborated here.

[0120] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. 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.

[0121] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0122] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

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

[0124] Any process or method described in the flowchart or otherwise herein is to be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, 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 depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0125] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0126] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0127] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0128] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0129] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. 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.

[0130] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this application can be achieved, and this is not limited herein.

[0131] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A firmware upgrade method for an in-vehicle system, characterized in that, Applied to a server, the method includes: Receive a first firmware upgrade instruction, wherein the first firmware upgrade instruction includes vehicle model information and firmware information; Based on the vehicle model information and the firmware information, a vehicle upgrade list and corresponding first firmware upgrade data are obtained. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The vehicle upgrade list is used to indicate the vehicle to be upgraded. Based on the vehicle upgrade list, the first firmware upgrade data and the target firmware upgrade instruction are sent to the corresponding vehicle system, so that the vehicle system can perform firmware upgrades on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

2. The firmware upgrade method for an in-vehicle system according to claim 1, characterized in that, Also includes: Receive firmware upgrade result information fed back by the vehicle system, and parse the firmware upgrade result information to obtain target vehicle information and firmware status information; If the firmware status information includes firmware upgrade failure information, then the firmware that failed to upgrade is determined based on the firmware upgrade failure information, and the second firmware upgrade data corresponding to the firmware that failed to upgrade is obtained. Based on the firmware status information and the preset optimization algorithm, the second firmware upgrade data is optimized to generate target firmware upgrade data, and the target firmware upgrade data and the second firmware upgrade command are sent to the corresponding vehicle system according to the target vehicle information.

3. The firmware upgrade method for an in-vehicle system according to claim 1, characterized in that, Also includes: Receive a third firmware upgrade command sent by the vehicle system, wherein the third firmware upgrade command includes third vehicle information and fault firmware information; Based on the third vehicle information and the fault firmware information, obtain the third firmware upgrade data corresponding to the fault firmware information, and send the third firmware upgrade data and the third firmware upgrade command to the corresponding vehicle system based on the third vehicle information.

4. A firmware upgrade method for an in-vehicle system, characterized in that, Applied to in-vehicle systems, the method includes: The system receives first firmware upgrade data and a target firmware upgrade instruction sent by the server. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The firmware upgrade list is used to indicate the firmware to be upgraded in the vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded. The firmware to be upgraded is performed according to the target firmware upgrade instruction and the firmware upgrade file.

5. The firmware upgrade method for an in-vehicle system according to claim 4, characterized in that, After upgrading the firmware to be upgraded according to the target firmware upgrade instruction and the firmware upgrade file, the process further includes: Generate corresponding firmware upgrade result information and send the firmware upgrade result information back to the server; Based on the firmware upgrade result information, determine whether the firmware upgrade has failed. If it has failed, roll back the failed firmware upgrade.

6. The firmware upgrade method for an in-vehicle system according to claim 5, characterized in that, Also includes: The system receives target firmware upgrade data and a second firmware upgrade instruction sent by the server, and performs a firmware upgrade on the failed firmware according to the second firmware upgrade instruction and the target firmware upgrade data.

7. The firmware upgrade method for an in-vehicle system according to claim 5, characterized in that, Also includes: When a firmware failure is detected in the vehicle system, a corresponding third firmware upgrade instruction is generated, wherein the third firmware upgrade instruction includes third vehicle information and faulty firmware information. The third firmware upgrade command is sent to the server.

8. The firmware upgrade method for a vehicle system according to claim 7, characterized in that, Also includes: The system receives third firmware upgrade data and third firmware upgrade instructions sent by the server, and upgrades the faulty firmware according to the third firmware upgrade instructions and the third firmware upgrade data.

9. A server, characterized in that, include: A receiving module is configured to receive a first firmware upgrade instruction, wherein the first firmware upgrade instruction includes vehicle model information and firmware information; The acquisition module is used to acquire a vehicle upgrade list and corresponding first firmware upgrade data based on the vehicle model information and the firmware information. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The vehicle upgrade list is used to indicate the vehicle to be upgraded. The sending module is used to send the first firmware upgrade data and the target firmware upgrade instruction to the corresponding vehicle system based on the vehicle upgrade list, so that the vehicle system can perform firmware upgrade on each firmware to be upgraded in the firmware upgrade list according to the target firmware upgrade instruction and the firmware upgrade file.

10. A vehicle-mounted system, characterized in that, include: The communication module is used to receive first firmware upgrade data and target firmware upgrade instructions sent by the server. The first firmware upgrade data includes a firmware upgrade list and a firmware upgrade file. The firmware upgrade list is used to indicate the firmware to be upgraded in the vehicle system, and the firmware upgrade file is used to upgrade the firmware to be upgraded. The upgrade module is used to upgrade the firmware to be upgraded according to the target firmware upgrade instruction and the firmware upgrade file.

Images