Automobile embedded platform software deployment method, equipment, medium and product
By analyzing functional safety requirements and module division of automotive embedded platforms, combined with virtualization and physical isolation technologies, priority scheduling and redundant mechanisms solve the problem of neglecting functional security in traditional methods, significantly improved the embedded platform software Safety and reliability deployment.
Patent Information
- Application Number
- CN202411517798.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-01-24
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The traditional automotive embedded software deployment method lacks systematic considerations for functional safety, resulting in the failure to fully identify and manage potential security risks during the software deployment process, and ignores the differentiated needs of software components under different security levels.
By analyzing functional security requirements for the overall architecture of the car embedded platform, determine the security level of each functional module, and use a computer to deploy multiple functional modules to the operating system task. The partition technology of virtualization technology and memory management units is used for logical and physical isolation. Based on real -time operating systems, priority scheduling, deploying safety monitoring modules and redundant mechanisms, and functional security verification and regression testing.
Significantly improves the security, real-time, flexibility and fault tolerance of embedded platform software deployment, optimizes system resource utilization efficiency, reduces security risks during system operation and update, and ensures that the system meets the requirements of functional safety standards such as ISO26262 .
Smart Images
Figure CN119356693A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of automobile technology, and in particular to a method, device, medium and product for deploying software on an automobile embedded platform. Background Art
[0002] With the rapid development of the automotive industry, the degree of vehicle electrification and intelligence continues to increase. Embedded platform software plays a vital role in automotive systems, especially in the fields of autonomous driving and advanced driver assistance systems (ADAS), where the complexity and functionality of software are increasing. However, with the expansion of software functions, the functional safety of vehicles is also facing greater challenges. Traditional automotive embedded software deployment methods often focus on function implementation and performance optimization, lacking systematic consideration of functional safety. This may lead to failure to fully identify and manage potential safety risks during software deployment. At the same time, most traditional methods ignore the differentiated requirements of software components at different safety levels and lack special treatment for key safety functions. In addition, during software updates and maintenance, there is a lack of an assessment mechanism for the impact of functional safety, which may introduce new safety hazards. With the increasing complexity and connectivity of vehicle electronic systems, these problems may lead to serious consequences. Therefore, the proposal of an automotive embedded platform software deployment method that considers functional safety can fully consider functional safety requirements throughout the entire life cycle of software deployment, thereby further improving the overall safety and reliability of vehicles operating in complex environments. Summary of the invention
[0003] The purpose of this application is to provide a method, device, medium and product for deploying software on an automotive embedded platform, which can improve the overall safety and reliability of the vehicle operating in a complex environment.
[0004] To achieve the above objectives, this application provides the following solutions:
[0005] In a first aspect, the present application provides a method for deploying software on an automotive embedded platform, comprising:
[0006] Conduct functional safety requirements analysis on the overall architecture of the automotive embedded platform and determine the safety level of each functional module;
[0007] Deploy multiple functional modules to the operating system task using a computer according to the security level of each functional module;
[0008] According to the functional safety requirements, the real-time operating system based on the embedded platform schedules each task with priority;
[0009] Deploy and execute security monitoring modules using computers, and deploy redundancy mechanisms for security-critical modules;
[0010] Functional safety verification and regression testing are performed on the automotive embedded platform after the software is deployed. The regression test results are used to describe whether the automotive embedded platform after the software is deployed meets the functional safety requirements and does not have system failures caused by improper deployment or functional interaction problems.
[0011] Optionally, the safety level is an ASIL level.
[0012] Optionally, according to the security level of each functional module, multiple functional modules are deployed to the operating system task using a computer, including:
[0013] Determine that the functional module whose security level reaches the preset level is a security-critical module;
[0014] Use virtualization technology to logically isolate all safety-critical modules so that each safety-critical module can run independently in different virtual environments;
[0015] All functional modules are physically isolated using the partitioning technology of the computer memory management unit. After physical isolation, multiple functional modules with the same security level are deployed in the same physical area of the memory management unit, and functional modules with different security levels are deployed in different physical areas of the memory management unit.
[0016] Optionally, a computer is used to deploy and execute a security monitoring module, and a redundancy mechanism is deployed for the security-critical module, including:
[0017] Deploy security monitoring modules using computers;
[0018] The security monitoring module monitors the system's operating status in real time and records abnormal situation logs when the operating status triggers the alarm mechanism;
[0019] Deploy a redundancy mechanism in the security monitoring module, adopt a multi-copy redundancy strategy to run the same functional module in multiple independent environments at the same time, and switch to another normally running copy when the functional module triggers an alarm mechanism;
[0020] The time redundancy technology is used to run the same key task multiple times, and the key task running results are obtained by comparing the multiple running results; the key task is a task that requires real-time performance.
[0021] Optionally, after functional safety verification and regression testing of the automotive embedded platform after software deployment, it also includes:
[0022] Use incremental technology to update functional modules of automotive embedded platforms.
[0023] Optionally, after functional safety verification and regression testing of the automotive embedded platform after software deployment, it also includes:
[0024] When a function module is updated abnormally, the version rollback mechanism is used to roll back the abnormally updated function module to the previous safe version.
[0025] Optionally, the automotive embedded platform software deployment method further includes:
[0026] After the functional modules are updated, regression testing is performed on the updated automotive embedded platform.
[0027] In a second aspect, the present application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-mentioned automotive embedded platform software deployment method.
[0028] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-mentioned automotive embedded platform software deployment method.
[0029] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the above-mentioned automotive embedded platform software deployment method when executed by a processor.
[0030] According to the specific embodiments provided in this application, this application discloses the following technical effects:
[0031] This application provides a method, device, medium and product for deploying software on an automotive embedded platform. Through innovative technologies such as functional safety requirements analysis and module division, safety isolation and scheduling, safety monitoring and redundancy, functional verification and regression testing, as well as incremental updates and version rollback mechanisms, the security, real-time performance, flexibility and fault tolerance of embedded platform software deployment are significantly improved. Compared with the prior art, this application improves the overall functional safety of the system while optimizing the efficiency of system resource utilization and reducing potential safety hazards during system operation and updates.
[0032] This application adopts a combination of logical isolation (virtualization technology) and physical isolation (memory management unit MMU) in the isolation and scheduling strategy of security-critical modules, effectively reducing the mutual interference between high-security level modules and low-security level modules. This isolation technology greatly reduces the probability of security vulnerabilities and failures in the system due to interaction or shared resources between modules, and enhances the overall security of the system. In addition, by monitoring the system operation status in real time in the security monitoring module, abnormal situations can be discovered in a timely manner. Combined with the deployment of redundant mechanisms (such as multi-copy redundancy and time redundancy), the system can quickly switch to a backup module when a key module fails, thereby improving the system's fault tolerance and operational reliability. These technical measures jointly ensure that the system can continue to operate stably when some modules fail or are abnormal, reducing the risk of system downtime or major functional failures.
[0033] This application uses the real-time operating system (RTOS) in the embedded platform to schedule tasks with priority, ensuring that tasks with high safety levels (such as ASIL D modules) are executed first. This scheduling strategy prevents high-priority tasks from being slowed down by low-priority tasks when the system load is high, thereby greatly improving the response speed of key system tasks. At the same time, the time slicing mechanism introduced in the RTOS allows tasks to be executed within a specified time window, ensuring the real-time performance of the system, and preventing low-priority tasks from consuming too many system resources, thereby optimizing the scheduling efficiency of the entire embedded system. Through this priority scheduling and time window mechanism, this application can effectively reduce task delays and resource contention problems when facing complex multi-tasking scenarios, ensuring the real-time performance of the system under high load conditions.
[0034] Compared with traditional large-scale software updates, this application uses incremental update technology, that is, only updating the part of the code or module that needs to be changed, which significantly reduces the impact of the update process on system stability. Through this update method, functional upgrades and security patches can be quickly implemented without affecting the overall performance of the system, improving the efficiency of the update. In addition, this application introduces a version rollback mechanism. When there is a problem with the update, the system can immediately restore to the last safe version to ensure that the system will not be in an unstable state for a long time due to update failure. These technical measures make the system more flexible and secure when updating software, avoiding uncertainties and potential security risks during the update process.
[0035] The functional safety verification and regression testing in this application not only performs functional testing on the newly deployed software modules, but also conducts a comprehensive inspection of potential security issues, interface interaction errors, etc. in the software code through static code analysis and dynamic testing tools. This method greatly improves the coverage and accuracy of the test, ensuring that the deployed software fully complies with the requirements of functional safety standards such as ISO26262. Through regression testing, the system can verify the interface compatibility between different modules, prevent new software from causing functional conflicts, and improve the overall security of the system and the reliability of operation. This comprehensive verification process enables the system to quickly discover and fix potential problems during deployment and operation, reducing safety risks caused by software deployment or updates.
[0036] The redundancy mechanism provides backup for key modules through multiple copies of redundancy or time redundancy. Once a key functional module fails, the system can automatically switch to the redundant module to ensure that the system function is not interrupted. At the same time, the system detects abnormal conditions through the safety monitoring module during operation and triggers the emergency response mechanism for functional safety events. Once a potential security threat or failure is found, the system will enter a safe state or take emergency measures in time to ensure the safety of the system and the vehicle. These mechanisms together enhance the system's fault response capabilities, making the system more robust and fault-tolerant under complex or extreme operating conditions. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0038] Figure 1 This is a flow chart of a method for deploying software on an automotive embedded platform in one embodiment of the present application;
[0039] Figure 2 This is a schematic diagram of a method for deploying software on an automotive embedded platform in an embodiment of the present application;
[0040] Figure 3 A schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0042] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.
[0043] In an exemplary embodiment, Figure 1 As shown, a method for deploying software on an automotive embedded platform is provided, comprising:
[0044] Step 101: Perform functional safety requirements analysis on the overall architecture of the automotive embedded platform and determine the safety level of each functional module. The safety level is the ASIL level.
[0045] The computer device performs functional safety requirements analysis through a special software tool and divides the modules according to the analysis results. First, the computer device extracts the functional safety requirements from the overall architecture design of the system, divides the safety level of each functional module with reference to the functional safety standard ISO 26262, and defines the ASIL level (Automotive Safety Integrity Level) of each module. According to different ASIL levels, the computer device automatically divides the functional modules of the embedded platform to ensure that modules with high safety levels are clearly separated from modules with low safety levels. During the division process, the dependencies and data interaction paths between modules are clarified to avoid potential safety risks caused by functional interactions. For key modules, especially core modules involving vehicle control, a higher safety level, such as ASIL D, is assigned, and the real-time and reliability requirements of these modules are marked. Through the analysis of functional safety requirements and reasonable software module division, it is ensured that software modules with different safety levels can be effectively isolated in subsequent steps, thereby avoiding threats to the safety of the overall system caused by high-risk modules.
[0046] Step 102: Deploy multiple functional modules to an operating system task using a computer according to the security level of each functional module.
[0047] Step 102 includes:
[0048] Step 102 - 1 : Determine that a functional module whose security level reaches a preset level is a security-critical module.
[0049] Step 102 - 2 : Use virtualization technology to logically isolate all safety-critical modules so that each safety-critical module can run independently in different virtual environments.
[0050] Step 102-3: Use the partitioning technology of the computer memory management unit to physically isolate all functional modules. After physical isolation, multiple functional modules with the same security level are deployed in the same physical area of the memory management unit, and functional modules with different security levels are deployed in different physical areas of the memory management unit.
[0051] Step 103: According to functional safety requirements, the real-time operating system based on the embedded platform performs priority scheduling on each task.
[0052] The isolation and scheduling strategies of safety-critical modules are operated by the embedded system deployment software and real-time operating system (RTOS) in the computer device. The computer device first determines the isolation strategy of the safety-critical modules based on the results of the safety requirements analysis. For modules with high ASIL levels, virtualization technology is used for logical isolation to ensure that these modules run independently in different virtual environments to avoid mutual influence. On the basis of logical isolation, the computer device further uses the memory management unit (MMU) for physical isolation, and deploys software of different safety levels in independent physical areas through partitioning technology to prevent memory overflow or accidental memory access from affecting system security. The real-time operating system (RTOS) of the embedded platform schedules each task according to the functional safety requirements. The safety-critical module is deployed to the highest priority task to ensure that it can still obtain computing resources first when the system load is high. In addition, the RTOS also introduces time slicing technology to divide task execution into predetermined time windows to prevent low-priority tasks from taking up too much execution time. Through logical and physical isolation means and priority scheduling strategies, the independence and real-time performance of safety-critical modules are ensured, and mutual interference between high-risk modules is avoided, thereby improving the functional safety of the entire embedded system.
[0053] Step 104: Deploy and execute the security monitoring module using a computer, and deploy a redundancy mechanism for the security-critical module.
[0054] Security monitoring and redundancy mechanism deployment are performed by the security monitoring module in the computer equipment and the redundancy mechanism deployment tool in the embedded platform. The computer equipment first deploys the security monitoring module to monitor the operating status of the system in real time. The monitoring content includes system resource usage, task execution, abnormal behavior detection, etc. Once an abnormal situation is detected, such as task timeout, memory overflow, etc., the security monitoring module will trigger the alarm mechanism and record relevant log information for subsequent troubleshooting. The computer equipment further deploys a redundancy mechanism for safety-critical modules. For important control modules, a multi-copy redundancy strategy is adopted, that is, the same software module is run simultaneously in multiple independent environments. Once a copy fails, the system will quickly switch to another normally running copy to ensure the continuous operation of the system. For tasks with high real-time requirements, time redundancy technology is used. That is, during the execution of the same task, the system will run the same task multiple times and compare the execution results to ensure the correctness and safety of the final result. The combination of the security monitoring module and the redundancy mechanism can effectively improve the system's fault detection and fault tolerance capabilities, ensuring that the system can respond in time and maintain functional safety when a fault occurs.
[0055] Step 104 includes:
[0056] Step 104-1: Deploy a security monitoring module using a computer.
[0057] Step 104-2: Execute the security monitoring module to monitor the operating status of the system in real time, and record abnormal situation logs when the operating status triggers an alarm mechanism.
[0058] Step 104-3: Deploy a redundancy mechanism in the safety-critical module, adopt a multi-copy redundancy strategy to run the same functional module in multiple independent environments simultaneously, and switch to another normally running copy when the functional module triggers the alarm mechanism.
[0059] Step 104-4: Use time redundancy technology to run the same key task multiple times, and compare the multiple running results to obtain the key task running result. The key task is a task that requires real-time performance.
[0060] Step 105: Perform functional safety verification and regression testing on the automotive embedded platform after the software is deployed. The functional safety verification results and regression test results are used to describe whether the automotive embedded platform after the software is deployed meets the functional safety requirements and does not have system failures caused by improper deployment or functional interaction problems.
[0061] Functional safety verification and regression testing are performed by computer equipment through an automated testing platform. After the software is deployed, the computer equipment will start the functional safety verification program and perform static code analysis and dynamic testing on each module in accordance with the requirements of ISO 26262. Static analysis is used to check the logic defects, potential security vulnerabilities and memory usage of the code; dynamic testing tests the performance of the module under various extreme conditions by simulating the actual operating environment. After the functional safety verification is completed, the computer equipment will continue to perform regression testing to ensure that the interfaces and interactions between different modules can operate correctly and that the newly deployed software will not cause functional anomalies in other modules. The system's fault tolerance mechanism will also be simulated and tested during the regression test, such as artificially creating hardware failures or software errors to observe the system's emergency response capabilities under the synergy of the redundant mechanism and the monitoring module. Functional safety verification and regression testing ensure that the deployed software meets the established functional safety requirements and avoids system failures caused by improper deployment or functional interaction problems.
[0062] Step 106: Use incremental technology to update the functional modules of the automotive embedded platform.
[0063] Step 107: When the function module is updated abnormally, the function module with the abnormal update is rolled back to the last safe version using the version rollback mechanism.
[0064] Step 108: After the functional modules are updated, regression testing is performed on the automotive embedded platform after the functional modules are updated.
[0065] Security updates and version management are performed by the software update management system in the computer equipment. In the process of software updates, the computer equipment adopts incremental update technology, that is, only the changed modules or code parts are updated to reduce the impact on the overall operation of the system. After the incremental update, the system automatically verifies the version to ensure that the updated software meets the security requirements. To ensure the security of the update process, the computer equipment also deploys a version rollback mechanism. When the software update fails or causes a system abnormality, the system can quickly roll back to the previous safe version and restore the normal operation of the system. After each software update, the system automatically performs necessary regression tests to verify the compatibility between different modules after the update to ensure that there will be no functional safety issues caused by the new version. Through the security update strategy and version management mechanism, the stability and security of the system during the software update process are ensured, and the impact of failures during the update process on the functional safety of the system is reduced.
[0066] like Figure 2, this application first analyzes the functional safety requirements of the automotive embedded platform, determines the safety level of each functional module (such as ASIL level), and divides the software into multiple functional modules according to the requirements, and clarifies the dependencies and data interactions between modules. Secondly, for key modules with high safety levels, a strategy combining logical isolation (such as virtualization, memory management) and physical isolation (partition design) is adopted. Use a priority scheduling algorithm to ensure that high-security modules are executed first at critical moments to avoid interference from low-priority tasks. After that, deploy a security monitoring module to detect system anomalies and fault warnings in real time. Use a redundant mechanism (such as multi-copy redundancy or time redundancy) for key modules to improve the system's fault tolerance and security. Finally, after the software is deployed, functional safety verification and regression testing are performed to ensure that the system meets safety requirements. At the same time, during the software update process, an incremental update and version rollback mechanism are used to ensure security and stability during the update process. This application proposes a method for deploying software for an automotive embedded platform, which comprehensively improves the security and reliability of embedded platform software deployment through steps such as functional safety requirements analysis and module division, isolation and scheduling of safety-critical modules, deployment of security monitoring and redundant mechanisms, functional safety verification and regression testing, software updates and version management. Through this method, it can be ensured that software modules with different safety levels do not interfere with each other during deployment and operation, have strong fault tolerance and fault emergency handling capabilities, and meet the requirements of functional safety standards such as ISO26262.
[0067] In an exemplary embodiment, a computer device is provided. The computer device may be a server or a terminal. The internal structure diagram thereof may be as follows: Figure 3 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for deploying automotive embedded platform software is implemented.
[0068] Those skilled in the art will understand that Figure 3The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components. In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.
[0069] In an exemplary embodiment, a computer-readable storage medium is provided, storing a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.
[0070] In an exemplary embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.
[0071] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0072] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
[0073] The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. The non-relational database may include a distributed database based on blockchain, etc., but is not limited thereto. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but is not limited thereto.
[0074] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0075] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, according to the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.
Claims
1. A method for deploying software on an automotive embedded platform, characterized in that: include: Conduct functional safety requirements analysis on the overall architecture of the automotive embedded platform and determine the safety level of each functional module; Deploy multiple functional modules to the operating system task using a computer according to the security level of each functional module; According to the functional safety requirements, the real-time operating system based on the embedded platform schedules each task with priority; Deploy and execute security monitoring modules using computers, and deploy redundancy mechanisms for security-critical modules; Functional safety verification and regression testing are performed on the automotive embedded platform after the software is deployed. The functional safety verification results and regression test results are used to describe whether the automotive embedded platform after the software is deployed meets the functional safety requirements and does not have system failures caused by improper deployment or functional interaction problems.
2. The automotive embedded platform software deployment method according to claim 1, characterized in that: The safety level is the ASIL level.
3. The automotive embedded platform software deployment method according to claim 1, characterized in that: According to the security level of each functional module, multiple functional modules are deployed to the operating system tasks using computers, including: Determine that the functional module whose security level reaches the preset level is a security-critical module; Use virtualization technology to logically isolate all safety-critical modules so that each safety-critical module can run independently in different virtual environments; All functional modules are physically isolated using the partitioning technology of the computer memory management unit. After physical isolation, multiple functional modules with the same security level are deployed in the same physical area of the memory management unit, and functional modules with different security levels are deployed in different physical areas of the memory management unit.
4. The automotive embedded platform software deployment method according to claim 3, characterized in that: Deploy and execute security monitoring modules using computers, and deploy redundancy mechanisms for security-critical modules, including: Deploy security monitoring modules using computers; The security monitoring module monitors the system's operating status in real time and records abnormal situation logs when the operating status triggers the alarm mechanism; Deploy a redundancy mechanism in the safety-critical module, adopt a multi-copy redundancy strategy to run the same functional module in multiple independent environments at the same time, and switch to another normally running copy when the functional module triggers an alarm mechanism; The time redundancy technology is used to run the same key task multiple times, and the key task running results are obtained by comparing the multiple running results; the key task is a task that requires real-time performance.
5. The automotive embedded platform software deployment method according to claim 1, characterized in that: After functional safety verification and regression testing of the automotive embedded platform after software deployment, it also includes: Use incremental technology to update functional modules of automotive embedded platforms.
6. The automotive embedded platform software deployment method according to claim 1, characterized in that: After functional safety verification and regression testing of the automotive embedded platform after software deployment, it also includes: When a function module is updated abnormally, the version rollback mechanism is used to roll back the abnormally updated function module to the previous safe version.
7. The automotive embedded platform software deployment method according to claim 1, characterized in that: The automotive embedded platform software deployment method further includes: After the functional modules are updated, regression testing is performed on the updated automotive embedded platform.
8. A computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the automotive embedded platform software deployment method according to any one of claims 1 to 7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the automotive embedded platform software deployment method described in any one of claims 1 to 7 is implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the automotive embedded platform software deployment method described in any one of claims 1 to 7 is implemented.