OTA upgrading process self-defining method and system capable of adapting to multiple vehicle types

Abstract

The invention discloses an OTA upgrade process customizing method and system adaptable to multiple vehicle types, and relates to the technical field of OTA upgrade.The OTA upgrade process customizing system comprises an OTA upgrade process customizing layer, is compatible with an existing OTA network architecture, and mainly relates to upgrade strategy management, dependency management, task scheduling and exception handling technologies; a user can customize upgrading paths of different vehicle types through the upgrading strategy management module; dynamically distributing upgrading tasks through an upgrading task scheduling module; analyzing the dependency relationship of the software component through a dependency relationship management module; the user-defined upgrading process is executed through an OTA upgrading execution module; and a log recording and exception handling mechanism is provided through the exception handling and log management module. Therefore, by the adoption of the OTA upgrading process self-defining method and system capable of adapting to the multiple vehicle types, OTA upgrading optimization of the different vehicle types can be achieved, the success rate is increased, and the maintenance cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of OTA upgrade technology, and in particular to a method and system for customizing an OTA upgrade process that can be adapted to multiple vehicle models. Background Art

[0002] OTA (Over-the-Air) upgrade technology is widely used in smart cars, smart homes, mobile devices and other fields. Its main purpose is to remotely update the software or firmware of the device through wireless networks to fix vulnerabilities, optimize performance or add new functions. In the field of smart cars, OTA upgrades involve multiple modules such as ECU (electronic control unit), T-BOX (vehicle terminal), IVI (in-vehicle infotainment system), etc., to ensure that the software versions of different control units are in the latest state to meet the needs of safety, regulatory compliance and user experience.

[0003] However, with the rapid development of the automotive industry, there are significant differences in hardware architecture, software platform, network environment and user needs between different models, making it difficult for a unified OTA upgrade process to meet the needs of all models. For example, hardware and software differences between different models: different models may be equipped with different versions of ECU, or there may be differences in suppliers, resulting in firmware compatibility issues; differences in upgrade order: some models may need to upgrade the T-BOX first, then upgrade the ECU, while other models may not have this restriction; complexity of dependencies: some software upgrades need to rely on the prior upgrade of other components. If the dependencies are not handled correctly, it may cause upgrade failure or vehicle malfunction; different network environments and OTA strategies: some models may support incremental upgrades, while some models only support full package upgrades, and the flexibility of the upgrade strategy is required to be high.

[0004] In the above context, most existing OTA upgrade solutions adopt a fixed upgrade process, resulting in the following problems: they cannot flexibly adapt to different models, and additional development and adaptation are required for each model, increasing development and maintenance costs; the upgrade failure rate is high. Due to the different hardware and software dependencies of different models, a unified process may not be applicable, resulting in upgrade failures and even affecting the normal operation of the vehicle; the scalability is poor. When new models are added or upgrade requirements change, the code needs to be modified or the fixed process needs to be adjusted, which increases the complexity and maintenance cost of the system.

[0005] In order to solve these problems, the present invention proposes an OTA upgrade process customization method and system, which supports users to define the upgrade process through configuration, adapts to the needs of different models, and improves the flexibility and success rate of OTA upgrades. Summary of the invention

[0006] The purpose of the present invention is to provide a method and system for customizing the OTA upgrade process that can adapt to multiple vehicle models, which is suitable for OTA upgrade optimization of different vehicle models, improves the success rate, and reduces maintenance costs.

[0007] To achieve the above objectives, the present invention provides an OTA upgrade process customization system that can adapt to multiple vehicle models, including: The car company's cloud OTA platform is responsible for storing and issuing upgrade packages, and provides upgrade strategy management and task scheduling capabilities; The OTA upgrade process customization layer is deployed on the cloud OTA platform and interacts with the vehicle terminal. It is responsible for parsing the upgrade process configured by the user and generating personalized upgrade strategies. During the upgrade process, it monitors and adjusts the upgrade sequence, dependencies, and exception handling processes. The vehicle terminal receives OTA tasks and executes them according to the customized upgrade process; The electronic control unit upgrade module performs upgrades on specific electronic control units and synchronizes the status with the cloud server through the vehicle terminal.

[0008] Preferably, the OTA upgrade process customization layer includes: User management module, which provides permission management and allows administrators or technicians to configure the OTA upgrade process for different models; The upgrade strategy management module provides graphical or scripted definition of the upgrade process and supports upgrade path configuration for different vehicle models; Dependency management module, which supports dependency analysis between components to ensure the correct OTA upgrade sequence and avoid upgrade failures; The upgrade task scheduling module dynamically allocates upgrade tasks to target vehicles according to the customized upgrade process and executes the upgrade process; OTA upgrade execution module, which performs OTA upgrade operations, including downloading, verification, installation, and rollback; The exception handling and log management module monitors the upgrade progress in real time and provides log records and exception recovery mechanisms.

[0009] Preferably, the upgrade strategy management module adopts a visual process editor, supports users to configure the upgrade process sequence by dragging and dropping, and supports automatic adjustment based on a rule engine.

[0010] Preferably, the upgrade strategy management module uses front-end Vue.js to build a visual interface, and the back-end uses SpringBoot to store upgrade strategy data.

[0011] Preferably, the dependency management module analyzes dependencies between components through a directed acyclic graph to ensure that the upgrade sequence is correct.

[0012] Preferably, the dependency management module uses a Neo4j graph database to store dependencies and uses a Graph algorithm to calculate the execution order.

[0013] Preferably, the exception handling and log management module is used to monitor the upgrade progress and record detailed logs of each OTA task, support remote debugging and problem analysis, and support automatic rollback and retry mechanisms.

[0014] Preferably, the exception handling and log management module uses ELK to implement log management and analysis.

[0015] The present invention also provides a method for customizing an OTA upgrade process that can be adapted to multiple vehicle models, using the above-mentioned system for customizing an OTA upgrade process that can be adapted to multiple vehicle models, comprising the following steps: S1. Users can customize the upgrade paths of different models through the upgrade strategy management module, and allow graphical configuration or dynamic adjustment of the process based on the rule engine; S2. Dynamically allocate upgrade tasks through the upgrade task scheduling module according to vehicle information; S3. Analyze the dependencies of software components through the dependency management module. When a circular dependency is detected, the task execution is rejected and an error prompt is given to avoid upgrade failure due to sequence errors. S4. Perform the upgrade operation through the OTA upgrade execution module according to the custom process to ensure the correct upgrade sequence; S5. Log records are provided through the exception handling and log management modules, and a rollback or retry mechanism is provided when an error occurs.

[0016] Therefore, the present invention adopts the above-mentioned OTA upgrade process customization method and system that can adapt to multiple models, which has the following technical effects: (1) The present invention can configure different upgrade logics for different vehicle models or software versions by customizing the OTA upgrade process, and flexibly adapt to different vehicle models and different versions without the need to develop additional adaptation code, thereby reducing development costs.

[0017] (2) The present invention allows the upgrade steps to be set according to the characteristics of different vehicle models, thereby improving the success rate of OTA upgrades, avoiding upgrade failures due to incompatibility, and improving the stability and reliability of upgrades.

[0018] (3) The present invention defines the upgrade process in a visual or regularized manner, which can quickly modify and adjust the process. At the same time, it provides more intuitive log and diagnostic capabilities, reduces the time for manual intervention, reduces maintenance costs, and improves troubleshooting efficiency.

[0019] (4) When new car models or software versions are added in the future, only the configuration needs to be adjusted to adapt, without the need for redevelopment, which improves the scalability and reusability of the OTA system and enhances the scalability and reusability of the system.

[0020] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a flow chart of a customized method for OTA upgrade process that can be adapted to multiple vehicle models. DETAILED DESCRIPTION

[0022] The present invention can be explained in more detail by the following examples. The purpose of disclosing the present invention is to protect all changes and improvements within the scope of the present invention. The present invention is not limited to the following examples.

[0023] At present, there are some OTA upgrade management solutions on the market, but most of them still have problems of rigid process and insufficient flexibility. For example, an OTA system based on a fixed upgrade strategy is a typical OTA upgrade solution, which is implemented as follows: (1) The vehicle manufacturer or OTA service provider predefines the upgrade process, such as following a fixed "download->verify->upgrade->restart" mode.

[0024] (2) Different upgrade packages are used to adapt to different car models, but the core upgrade process remains unchanged.

[0025] (3) The central server issues the upgrade strategy, and all vehicles execute it according to the same logic.

[0026] Based on the above solutions, it can be seen that the existing OTA upgrade solution has the following shortcomings: (1) The upgrade process is difficult to adjust: If the upgrade steps for a certain vehicle model need to be changed, for example, some models require additional verification, the system logic needs to be modified again, increasing development costs.

[0027] (2) Adapting to new car models is complex: When new car models or new modules are added, it may be necessary to redevelop specific adaptation codes, which has poor scalability.

[0028] (3) Dependence on server-side policy issuance: The upgrade strategy is generally controlled by the cloud and cannot be configured independently by the front end, resulting in insufficient flexibility in adjusting the process.

[0029] Based on this, the present invention provides an OTA upgrade process customization system that can adapt to multiple vehicle models, including: The cloud-based OTA platform is responsible for storing and issuing upgrade packages, and provides upgrade strategy management and task scheduling capabilities.

[0030] The OTA upgrade process customization layer is deployed in the cloud OTA platform and needs to interact with the vehicle terminal to perform customized OTA upgrade tasks. It is responsible for parsing the upgrade process configured by the user, generating personalized upgrade strategies, and monitoring and adjusting the upgrade sequence, dependencies, and exception handling processes during the upgrade process to ensure the correct upgrade sequence and improve the upgrade success rate.

[0031] The vehicle-mounted terminal (T-BOX) is used to receive OTA tasks and execute tasks according to the customized upgrade process.

[0032] The ECU upgrade module performs upgrade tasks for specific ECUs and synchronizes the status with the cloud server through T-BOX.

[0033] In another embodiment, the OTA upgrade process custom layer is compatible with the existing OTA network architecture, including: The user management module provides permission management, allowing administrators or technicians to configure the OTA upgrade process for different models.

[0034] The upgrade strategy management module uses Vue.js on the front end to build a visual interface, and Spring Boot on the back end to store upgrade strategy data. It can provide graphical or scripted definitions of the upgrade process, support upgrade path configuration for different models, and have multi-model compatibility. This upgrade strategy is not a fixed upgrade process. Non-developers can adjust the OTA upgrade process and implement a custom upgrade process to adapt to different models through visualization or low-code configuration, saving development costs and making it more flexible and widely applicable.

[0035] In one embodiment, the upgrade paths for different vehicle models are customized as follows: for vehicle model X, the upgrade process is set to "upgrade ECU A first, then upgrade ECU B"; for vehicle model Y, the upgrade process is set to "upgrade ECU B first, then upgrade ECU A". In actual operation, the user can use a visual process editor to configure the upgrade steps by dragging and dropping; at the same time, the user can also automatically adjust based on the rule engine, such as "if vehicle model = X, then upgrade ECU A -> ECU B; if vehicle model = Y, then upgrade ECU B -> ECU A".

[0036] The dependency management module uses the Neo4j graph database to store dependencies and uses the Graph algorithm to calculate the execution order. It analyzes the dependencies between components through a directed acyclic graph (DAG) and automatically identifies the dependencies between software modules. In addition, it can intelligently manage the dependencies between modules to ensure the correct OTA upgrade sequence and avoid upgrade failures; for example, when a circular dependency is detected, the task execution is rejected and an error prompt is given.

[0037] The upgrade task scheduling module dynamically allocates upgrade tasks to target vehicles according to the defined upgrade process and executes the upgrade process.

[0038] The OTA upgrade execution module specifically performs OTA upgrade operations, including downloading, verification, installation, rollback and other steps.

[0039] The exception handling and log management module uses ELK (Elasticsearch + Logstash + Kibana) to implement log management and analysis, and supports remote debugging and problem analysis. In actual applications, this module monitors the upgrade progress in real time, records detailed logs for each OTA task, and quickly locates problems when upgrade exceptions occur through log tracking and automatic analysis, and provides a flexible exception handling mechanism. If an error occurs, rollback, retry, skip and other mechanisms are provided according to user needs.

[0040] like Figure 1 As shown, based on a system for customizing an OTA upgrade process that can adapt to multiple vehicle models, the present invention also provides a method for customizing an OTA upgrade process that can adapt to multiple vehicle models, which has the advantages of optimizing the data processing process, especially the customization capability of the upgrade process, and is suitable for the OTA upgrade requirements in the field of smart cars, and includes the following steps: S1. Users can customize the upgrade paths of different models through the upgrade strategy management module, and allow graphical configuration or dynamic adjustment of the process based on the rule engine; S2. Dynamically allocate upgrade tasks through the upgrade task scheduling module according to vehicle information; S3. Analyze the dependencies of software components through the dependency management module. When a circular dependency is detected, the task execution is rejected and an error prompt is given to avoid upgrade failure due to sequence errors. S4. Perform the upgrade operation through the OTA upgrade execution module according to the custom process to ensure the correct upgrade sequence; S5. Log records are provided through the exception handling and log management modules, and a rollback or retry mechanism is provided when an error occurs.

[0041] In summary, compared with the prior art, the method and system of this embodiment have outstanding advantages, as shown in Table 1 for details.

[0042] Table 1 Differences between the prior art and the present invention ;

[0043] Therefore, the present invention adopts the above-mentioned OTA upgrade process customization method and system that can adapt to multiple vehicle models, and optimizes OTA upgrades for different vehicle models through key technologies such as upgrade strategy management, dependency management, task scheduling, and exception handling, thereby improving the success rate and reducing maintenance costs.

[0044] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that they can still modify or replace the technical solution of the present invention with equivalents, and these modifications or equivalent replacements cannot cause the modified technical solution to deviate from the spirit and scope of the technical solution of the present invention.

Claims

1. A customized OTA upgrade process system that can adapt to multiple vehicle models, characterized in that: include: The car company's cloud OTA platform is responsible for storing and issuing upgrade packages, and provides upgrade strategy management and task scheduling capabilities; The OTA upgrade process customization layer is deployed on the cloud OTA platform and interacts with the vehicle terminal. It is responsible for parsing the upgrade process configured by the user and generating personalized upgrade strategies. During the upgrade process, it monitors and adjusts the upgrade sequence, dependencies, and exception handling processes. The vehicle terminal receives OTA tasks and executes them according to the customized upgrade process; The electronic control unit upgrade module performs upgrades on specific electronic control units and synchronizes the status with the cloud server through the vehicle terminal.

2. According to claim 1, a customized OTA upgrade process system that can adapt to multiple vehicle models is characterized in that: OTA upgrade process customization layer, including: User management module, which provides permission management and allows administrators or technicians to configure the OTA upgrade process for different models; The upgrade strategy management module provides graphical or scripted definition of the upgrade process and supports upgrade path configuration for different vehicle models; Dependency management module, which supports dependency analysis between components to ensure the correct OTA upgrade sequence and avoid upgrade failures; The upgrade task scheduling module dynamically allocates upgrade tasks to target vehicles according to the customized upgrade process and executes the upgrade process; OTA upgrade execution module, which performs OTA upgrade operations, including downloading, verification, installation, and rollback; The exception handling and log management module monitors the upgrade progress in real time and provides log records and exception recovery mechanisms.

3. The OTA upgrade process customization system adaptable to multiple vehicle models according to claim 2 is characterized in that: The upgrade strategy management module uses a visual process editor that supports users to configure the upgrade process sequence by dragging and dropping, and also supports automatic adjustment based on the rule engine.

4. According to claim 3, a customized OTA upgrade process system that can adapt to multiple vehicle models is characterized in that: The upgrade strategy management module uses Vue.js on the front end to build a visual interface, and Spring Boot on the back end to store upgrade strategy data.

5. The OTA upgrade process customization system adaptable to multiple vehicle models according to claim 2 is characterized in that: The dependency management module analyzes the dependencies between components through a directed acyclic graph to ensure the correct upgrade order.

6. The OTA upgrade process customization system adaptable to multiple vehicle models according to claim 5 is characterized in that: The dependency management module uses the Neo4j graph database to store dependencies and uses the Graph algorithm to calculate the execution order.

7. The OTA upgrade process customization system adaptable to multiple vehicle models according to claim 2 is characterized in that: The exception handling and log management module is used to monitor the upgrade progress and record detailed logs of each OTA task. It supports remote debugging and problem analysis, and also supports automatic rollback and retry mechanisms.

8. The OTA upgrade process customization system adaptable to multiple vehicle models according to claim 7 is characterized in that: The exception handling and log management module uses ELK to implement log management and analysis.

9. A method for customizing an OTA upgrade process that can adapt to multiple vehicle models, using a system for customizing an OTA upgrade process that can adapt to multiple vehicle models as claimed in any one of claims 1 to 8, characterized in that: The following steps are involved: S1. Users can customize the upgrade paths of different models through the upgrade strategy management module, and allow graphical configuration or dynamic adjustment of the process based on the rule engine; S2. Dynamically allocate upgrade tasks through the upgrade task scheduling module according to vehicle information; S3. Analyze the dependencies of software components through the dependency management module. When a circular dependency is detected, the task execution is rejected and an error prompt is given to avoid upgrade failure due to sequence errors. S4. Perform the upgrade operation through the OTA upgrade execution module according to the custom process to ensure the correct upgrade sequence; S5. Log records are provided through the exception handling and log management modules, and a rollback or retry mechanism is provided when an error occurs.

Images