Vehicle Software Execution Through Logic–Interaction Script Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing vehicle software development methods, relying on hard coding and Over the Air (OTA) technology, face challenges in meeting rapid user requirement changes, with long development cycles and poor adaptability to updates and iterations.
Innovation Solution
A vehicle software execution method that splits script files into logic and interaction script files, executed by separate logic and interaction engines, allowing collaborative execution and enabling flexible, efficient development and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hard coding is used to implement vehicle software development, then the software can be executed on specific vehicle-mounted systems, but the development cycle becomes long and adaptability to updates and iterations is poor
Solution Approach 1:
The patent segments vehicle software into multiple independent script files (e.g., control scripts, interaction scripts, configuration scripts) that can be developed, updated, and executed independently. This segmentation allows specific software modules to be updated without requiring complete re-encoding and repackaging, thereby shortening the development cycle while maintaining execution reliability through the structured script file system with defined parsing and execution mechanisms.
2Stability of the object's composition
If traditional hardware update methods are used, then the system structure remains stable, but the update and iteration speed cannot meet rapidly changing user requirements
Solution Approach 1:
The patent implements a dynamic software architecture where script files can be updated independently without changing the underlying system structure. The engine parses and executes script files dynamically, allowing software functionality to adapt rapidly to user requirements while the stable engine core maintains system structure integrity. This enables frequent software iterations through simple script file updates rather than complex hardware or system reconfiguration.
3Device complexity
If a single engine is used to execute all script files, then the system structure is simple, but system operation efficiency and robustness are poor
Solution Approach 1:
The patent divides the execution engine into multiple specialized engines (e.g., control engine, interaction engine, configuration engine), where each engine is responsible for executing specific types of script files. This segmentation improves system operation robustness by isolating execution contexts and reducing interdependencies, while maintaining manageable complexity through clear engine specialization and standardized script file interfaces.
4Ease of manufacture
If all script file execution logic is handled by one engine, then the implementation is straightforward, but interaction conflicts may occur and collaboration between different script files is difficult
Solution Approach 1:
The patent introduces a script file management system that acts as an intermediary between multiple engines and script files. This management system handles script file parsing, validation, and coordination, enabling seamless collaboration between different engines executing different script files. The standardized management layer simplifies implementation while improving operational efficiency by providing centralized control and conflict resolution mechanisms.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A vehicle software execution method and device, a vehicle, and a storage medium are provided. The vehicle software execution method includes obtaining a script file corresponding to vehicle software, the script file includes a number of nodes of different types; splitting the script file into a logic script file and an interaction script file according to a node type of each node in the script file; and transmitting the logic script file to a logic engine and transmitting the interaction script file to an interaction engine respectively, enabling the logic engine to execute the logic script file, and enabling the interaction engine to executes the interaction script file, during a script file execution process, the interaction engine and the logic engine call each other according to content of the script file, which can improve the system operation efficiency, system robustness, and business coverage of the script file, support a large number of complex software businesses, avoid the problem of interactive conflicts that are easy to occur when the interaction script files of different vehicle software are executed, and have good flexibility and adaptability for vehicle software development and change iteration.