In-Vehicle BEOS Architecture for Maintainable Cross-Platform Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing in-vehicle operating systems have a general and undiversified framework design, leading to poor maintainability, poor extendability, and poor portability, with the basic microcontroller programming mode increasing costs and potentially limiting future software development due to intellectual property concerns.
Innovation Solution
The implementation of a self-developed built-in Be Operating System (BEOS) with a corresponding debugging system, which includes a hardware layer, software layer, and application layer, providing better real-time performance, stability, and safety, along with a BEOS debugging method for effective development, authentication, debugging, and maintenance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a basic microcontroller programming mode is used, then costs are reduced, but code maintainability deteriorates
Solution Approach 1:
The patent uses a virtual file system that creates virtual copies of file system operations, allowing the same code to run on different hardware platforms without modification. This copying approach enables the system to maintain high code maintainability while avoiding the need for multiple platform-specific codebases, thus controlling costs.
Solution Approach 2:
The patent implements a universal virtual file system layer that can operate across different hardware architectures and operating systems. This multi-functional design allows a single codebase to serve multiple purposes and platforms, improving code maintainability without requiring expensive platform-specific development for each target system.
2Ease of manufacture
If a basic microcontroller programming mode is used, then costs are reduced, but program extendability deteriorates
Solution Approach 1:
The patent segments the file system into virtual layers that can be independently configured and extended. This segmentation allows new file system features and capabilities to be added by creating new virtual file system layers without modifying the underlying hardware or core operating system, enabling easy program extendability while maintaining cost efficiency.
Solution Approach 2:
The virtual file system is designed to be dynamically configurable at runtime, allowing the system to adapt to new requirements and extend functionality without recompilation or hardware changes. This dynamic nature enables the program to evolve and expand capabilities while avoiding the costs associated with rigid, hardware-tied architectures.
3Ease of manufacture
If a basic microcontroller programming mode is used, then costs are reduced, but project portability deteriorates
Solution Approach 1:
The patent creates a virtual copy of the file system interface that abstracts hardware-specific operations, allowing the same project to be copied and deployed to different hardware platforms without modification. This copying strategy enables excellent project portability while avoiding the expensive process of adapting code for each target platform.
4Ease of operation
If existing in-vehicle operating systems are used, then development is simplified, but real-time performance deteriorates
Solution Approach 1:
The patent introduces a virtual file system intermediary layer that sits between the application layer and the hardware layer, providing standardized file system operations while enabling precise control over timing and resource allocation. This intermediary approach maintains development simplicity through standardized interfaces while achieving superior real-time performance through optimized underlying implementations.
5Ease of operation
If existing in-vehicle operating systems are used, then development is simplified, but system stability deteriorates
Solution Approach 1:
The patent uses virtual copying to create isolated file system environments that prevent errors in one part of the system from affecting the entire system. This copying approach maintains development simplicity while improving system stability through error containment and isolation.
Data Source
AI summary
An in-vehicle operating system includes a hardware layer, a software layer, and an application layer. The hardware layer includes at least one controller, and each of the at least one controller includes a processor. The software layer includes a Be operating system (BEOS) and a BEOS driver, where the BEOS is configured to manage and control the in-vehicle operating system, and the BEOS driver is configured to transfer data between the hardware layer and the software layer. The application layer includes a plurality of applications, the applications are connected to the BEOS by an operating system interface, and each of the applications is configured to provide an in-vehicle application to the vehicle.