Operation management method and device for intelligent cabin system, storage medium, vehicle controller and vehicle

Abstract

The invention provides an operation management method and device for an intelligent cabin system, a storage medium, a vehicle controller and a vehicle. According to the operation management method for the intelligent cabin system, the target controller of the intelligent cabin system built based on a QNX operation system can be connected with the storage medium; running a target plug-in for managing the running condition of the intelligent cabin system, and calling a target application programming interface provided by a QNX operating system by using the target plug-in to obtain at least one of computing resource use condition information and process running condition information at the intelligent cabin system, according to a preset system management strategy, on the basis of at least one of the computing resource use condition information and the process operation condition information, the operation condition of the intelligent cabin system can be managed efficiently and accurately in real time, and stable operation of the intelligent cabin system can be guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of smart cockpits, and in particular to an operation management method, device, storage medium, vehicle controller and vehicle for a smart cockpit system. Background Art

[0002] With the development of automobile intelligence and integration, intelligent cockpit systems that integrate a variety of Internet technologies and artificial intelligence technologies have also emerged. Intelligent cockpit systems built on the QNX operating system usually have the characteristics of high real-time performance, flexibility and reliability. Therefore, vehicles are gradually equipped with intelligent cockpit systems built on the QNX operating system to provide drivers with a better intelligent experience and promote driving safety. When there are abnormal conditions in important resources or processes in the intelligent cockpit system, it may affect the normal operation of the intelligent cockpit system. However, the QNX operating system does not provide a complete functional module to realize the monitoring and management of important resources or processes of the intelligent cockpit system. Therefore, there is an urgent need for a solution to manage the operation of the intelligent cockpit system in a timely and effective manner. Summary of the invention

[0003] Based on this, the present invention provides an operation management method, device, storage medium, vehicle controller and vehicle for a smart cockpit system. By adopting the operation management method for a smart cockpit system, the operation status of the smart cockpit system can be managed in real time, efficiently and accurately to ensure the stable operation of the smart cockpit system.

[0004] In one aspect, the present invention provides an operation management method for an intelligent cockpit system, the method comprising:

[0005] At a target controller of an intelligent cockpit system built on the basis of the QNX operating system, a target plug-in for managing the operation status of the intelligent cockpit system is run;

[0006] Using the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system;

[0007] According to a preset system management strategy, the operation of the smart cockpit system is managed based on at least one of the computing resource usage information and the process operation information.

[0008] Further, in some implementations, the target plug-in includes: a first plug-in for managing central processing unit resources of the smart cockpit system;

[0009] The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes:

[0010] Using the first plug-in to call a first application programming interface provided by the QNX operating system, so as to obtain first central processing unit occupancy time information corresponding to a first moment and second central processing unit occupancy time information corresponding to a second moment from a proc file in the QNX operating system;

[0011] The CPU usage rate of the smart cockpit system is calculated based on the first CPU occupation time information and the second CPU occupation time information.

[0012] Furthermore, in some implementations, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes:

[0013] According to a preset CPU resource management strategy, determining whether the CPU usage rate reaches a first threshold value, and obtaining a first determination result;

[0014] If the first judgment result indicates that the CPU usage rate reaches a first threshold, a first instruction for instructing to shut down or restart a first process at the smart cockpit system is generated; or,

[0015] If the first judgment result indicates that the CPU usage rate reaches a first threshold, first management information for managing the CPU resources is sent to a second process at the smart cockpit system; the second process is used to release at least part of the occupied CPU resources according to the first management information.

[0016] Further, in some implementations, the target plug-in includes: a second plug-in for managing memory resources of the smart cockpit system;

[0017] The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes:

[0018] After receiving the preset event trigger information, the second plug-in is used to call a second application programming interface provided by the QNX operating system to obtain the amount of memory resources occupied by the third process at the smart cockpit system;

[0019] Among them, the preset event trigger information is information generated by a preset event set by triggering the second plug-in to pre-call the third application programming interface provided by the QNX operating system when the remaining amount of memory resources at the smart cockpit system is less than a second threshold.

[0020] Furthermore, in some implementations, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes:

[0021] According to the preset memory resource management strategy, determining whether the amount of memory resources occupied by the third process reaches a third threshold, and obtaining a second determination result;

[0022] If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, then generating a second instruction for instructing to close or restart the third process; or,

[0023] If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, second management information for managing the memory resources is sent to the third process; the third process is used to release at least part of the occupied memory resources according to the second management information.

[0024] Furthermore, in some embodiments, the above method further comprises:

[0025] determining whether the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, and obtaining a third determination result;

[0026] If the third judgment result indicates that the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, then the relevant configuration parameter data of the third process is stored.

[0027] Further, in some implementations, the target plug-in includes: a third plug-in for managing non-volatile storage resources of the smart cockpit system;

[0028] The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes:

[0029] Using the third plug-in to call a fourth application programming interface provided by the QNX operating system to obtain resource occupancy of at least part of the non-volatile storage resource partition at the smart cockpit system;

[0030] The managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes:

[0031] For any of the non-volatile storage resource partitions, judging whether the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold according to a preset non-volatile storage resource management strategy, and obtaining a fourth judgment result;

[0032] If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches the fifth threshold, a third instruction for instructing to delete at least part of the data in the non-volatile storage resource partition is generated; or,

[0033] If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold, third management information for managing the data stored in the non-volatile storage resource partition is sent to a fourth process at the smart cockpit system;

[0034] If information indicating permission to delete the target data of the fourth process stored in the non-volatile storage resource partition is obtained from any of the fourth processes, at least part of the target data of the fourth process stored in the non-volatile storage resource partition is deleted.

[0035] Further, in some implementations, the target plug-in includes: a fourth plug-in for managing a process at the smart cockpit system;

[0036] The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes:

[0037] The fourth plug-in is used to call a fifth application programming interface provided by the QNX operating system to obtain the running status information of the fifth process at the smart cockpit system.

[0038] The managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes:

[0039] For any of the fifth processes, if the running status information of the fifth process reflects that the fifth process is in an abnormal state, then according to the preset process management strategy, based on the relevant startup information of the fifth process obtained in advance, a first child process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

[0040] Furthermore, in some implementations, after creating a first child process for the plug-in process corresponding to the fourth plug-in to restart the fifth process, the method further includes:

[0041] Using the plug-in process corresponding to the fourth plug-in to obtain the process identifier of the first sub-process;

[0042] When it is identified based on the process identifier that the first sub-process is in an abnormal state, restarting the first sub-process to restart the fifth process; or,

[0043] When it is identified based on the process identifier that the first sub-process is in an abnormal state, a second sub-process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

[0044] Furthermore, in some implementations, after running a target plug-in for managing the operation status of the smart cockpit system at the target controller of the smart cockpit system built based on the QNX operating system, the method further includes:

[0045] Determine whether a preset closing condition for the target plug-in is met, and obtain a fifth determination result;

[0046] If the fifth judgment result indicates that the preset closing condition for the target plug-in is met, a fourth instruction for instructing to close the target plug-in is generated.

[0047] On the other hand, the present invention also provides an operation management device for an intelligent cockpit system, comprising:

[0048] A plug-in running module, used to run a target plug-in for managing the operation status of the smart cockpit system at a target controller of the smart cockpit system built based on the QNX operating system;

[0049] An information acquisition module, configured to use the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process operation information at the smart cockpit system;

[0050] A management module is used to manage the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information.

[0051] On the other hand, the present invention further provides a storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0052] On the other hand, the present invention further provides a vehicle controller, comprising: a processor and a memory; wherein the memory stores computer-readable instructions, and the computer-readable instructions are suitable for being loaded by the processor and executing the steps of the above method.

[0053] On the other hand, the present invention further provides a vehicle, comprising the operation management device for the smart cockpit system as described above or the vehicle controller as described above.

[0054] According to the operation management method for the smart cockpit system provided by the present invention, a target plug-in for managing the operation status of the smart cockpit system is run at the target controller of the smart cockpit system built on the QNX operating system, so that the target plug-in can be used to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and the process operation status information at the smart cockpit system. Then, according to the preset system management strategy, based on at least one of the computing resource usage information and the process operation status information, the operation status of the smart cockpit system can be managed in real time, efficiently and accurately, which is conducive to ensuring the stable operation of the smart cockpit system and improving the user experience.

[0055] It should be understood that the contents described in the summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 A schematic diagram of a flow chart of an operation management method for an intelligent cockpit system provided by an embodiment of the present invention;

[0057] Figure 2 A schematic diagram of an operation management module for an intelligent cockpit system provided by an embodiment of the present invention;

[0058] Figure 3 A schematic diagram of the structure of an operation management device for an intelligent cockpit system provided by an embodiment of the present invention;

[0059] Figure 4 A schematic structural diagram of a vehicle controller provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the specific embodiments of the present invention and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0061] In the description of one or more embodiments of the present invention, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0062] With the rise of intelligent cockpit technology, automakers have gradually begun to deploy intelligent cockpit systems based on the QNX operating system in vehicles to improve the experience of drivers and passengers. However, the QNX operating system does not provide a complete functional module to monitor and manage important resources or processes of the intelligent cockpit system, which makes it easy for the intelligent cockpit system to have abnormal operation problems during operation due to factors such as excessive resource utilization and process jamming. Therefore, there is a need to monitor and manage the operation of important resources and processes in the intelligent cockpit system.

[0063] At present, due to the differences in the smart cockpit systems used by various automobile manufacturers, and the types of system resources and processes that need to be monitored and managed specified by different automobile manufacturers are also different, there is no general solution that can comprehensively manage the operation of various smart cockpit systems. Although some automobile manufacturers have begun to try to add monitoring functions for some resources in the smart cockpit system, the implementation of these monitoring functions usually requires frequent calls to the TOP command of the QNX operating system, which not only requires a large amount of computing resources, but also affects the timeliness of monitoring the operation of the smart cockpit system due to the limitation of the command execution cycle. In addition, since the monitoring modules for different types of system resources often lack unified planning when designing, it is easy to cause redundancy of the same program code, and even cause interference between each other, thereby affecting the accuracy and effectiveness of the monitoring and management results of the operation of the smart cockpit system.

[0064] Based on this, how to provide a versatile solution for real-time, efficient and accurate management of the operation of the smart cockpit system built on the QNX operating system has become a technical problem that needs to be solved urgently.

[0065] The present invention proposes an operation management method for a smart cockpit system. The method can run a target plug-in for managing the operation of the smart cockpit system at a target controller of the smart cockpit system built on the basis of the QNX operating system, so as to use the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process operation information at the smart cockpit system. Then, according to a preset system management strategy, based on at least one of the computing resource usage information and the process operation information, the operation of the smart cockpit system can be managed in real time, efficiently and accurately.

[0066] In addition, compared with relying on calling the TOP command of the QNX operating system to obtain system operation information, this method obtains system operation information by calling the target application programming interface provided by the QNX operating system. It can not only improve the real-time performance of the obtained system operation information, thereby improving the accuracy and effectiveness of the management of the operation of the smart cockpit system, but also reduce the consumption of central processing unit resources, and has good practicality.

[0067] In addition, by pre-developing various target plug-ins to monitor and manage various computing resources and processes in the smart cockpit system, it is plug-and-play, with good scalability and comprehensiveness. In addition, it allows convenient configuration of preset system management strategies according to actual monitoring and management needs, thereby meeting the personalized management needs of various resources and programs of various automobile manufacturers, with good flexibility and strong versatility.

[0068] See also Figure 1 , which is a flow chart of a method for managing the operation of a smart cockpit system provided by an embodiment of the present invention. From a program perspective, the execution subject of the process may be an application program for managing the operation of the smart cockpit system. Alternatively, the execution subject of the process may also be a target controller equipped with the above application program at the smart cockpit system, which is not specifically limited.

[0069] The following is for Figure 1 The process shown in the figure is described in detail, and the operation management method for the intelligent cockpit system may specifically include the following steps:

[0070] Step S102: running a target plug-in for managing the operation status of the smart cockpit system at a target controller of the smart cockpit system built based on the QNX operating system.

[0071] In an embodiment of the present invention, the QNX operating system can be a distributed, embedded, scalable real-time operating system (RTOS) with the characteristics of high performance, high reliability, scalability and portability. It can quickly process large amounts of data with extremely low latency in a complex hardware environment. It has been widely used in many fields such as automobiles, medical care, and industrial automation.

[0072] The smart cockpit system built on the QNX operating system can usually effectively control and enhance the connection and communication between the in-vehicle infotainment system, instrument panel system, Internet of Vehicles system and driver assistance system, thereby enabling efficient human-computer interaction, improving the user's driving experience, and enhancing the safety and stability of the vehicle's driving process.

[0073] In an embodiment of the present invention, the smart cockpit system may generally include one or more target controllers, so as to use the target controller to calculate and process the data obtained or generated during the operation of the smart cockpit system, so as to realize at least some of the functions supported by the smart cockpit system. Based on this, a target plug-in that supports the management of the operation of the smart cockpit system can be started and run at the target controller. Among them, the target plug-in can be a program written in accordance with a certain specification of the application program interface, and when the target plug-in is running, it can realize the function of monitoring and managing the operation of the computing resources, processes, etc. of the smart cockpit system. Since the working principle of the target plug-in will be explained in subsequent embodiments, it will not be repeated here. Among them, the target controller can be a system-on-chip (System on Chip, SOC), a domain controller, etc. at the smart cockpit system, or it can also be other types of controllers or chips, which are not specifically limited.

[0074] Step S104: Using the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system.

[0075] In an embodiment of the present invention, the role of the Application Programming Interface (API) can mainly be to serve as a communication bridge between different software components, providing the ability to access specific functions without having to access the source code or understand the details of the internal working mechanism, so that different software components can be easily integrated and used based on the Application Programming Interface to achieve functional expansion and integration.

[0076] Since the QNX operating system provides a wealth of application programming interfaces (APIs) and functions for developers to use, developers can use these APIs and functions to develop and customize software modules for implementing specified functions according to actual needs. Based on this, you can pre-use the functions provided by the QNX operating system to develop the target application programming interface, or pre-select the target application programming interface provided by the QNX operating system to combine the target application programming interface to write and customize the target plug-in that can manage the operation of the smart cockpit system. Therefore, during the operation of the target plug-in, you can call the target application programming interface to obtain computing resource usage information and process operation information at the smart cockpit system, which is convenient and quick.

[0077] Among them, the computing resource usage information can reflect the usage of resources such as central processing unit (CPU), memory resources, non-volatile storage resources, etc. in the smart cockpit system. Of course, it can also include but not be limited to the usage of network resources, graphics processor resources, etc.; the process operation status information can reflect the operation status of related processes created to implement various functions of the smart cockpit system; there is no specific limitation on this.

[0078] Step S106: manage the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information.

[0079] In the embodiment of the present invention, the preset system management strategy can be used to reflect the processing schemes to be executed for computing resources or processes in various operating conditions; for example, when the operating condition of a computing resource or process is good, it can continue to be monitored and managed according to the preset system management strategy; when the operating condition of a computing resource or process is abnormal or risky, it can continue to be processed according to the preset system management strategy to reduce or even eliminate the abnormality or risk. Of course, it can also issue an early warning for the abnormality or risk. The preset system management strategy can be set according to actual needs, and there is no specific limitation on this.

[0080] Figure 1 The method in the embodiment of the present invention uses a target plug-in to call a target application programming interface provided by the QNX operating system to obtain computing resource usage information and / or process operation information of the smart cockpit system, so as to manage the operation of the smart cockpit system in real time, efficiently and accurately based on the computing resource usage information and / or the process operation information according to a preset system management strategy. And, Figure 1The solution based on target plug-in implementation has good scalability and is suitable for comprehensive management of various system resources and processes. It can also conveniently configure the preset system management strategy based on actual system management needs, thereby meeting the personalized management needs of various automobile manufacturers for various system resources and processes. It has good flexibility and strong versatility.

[0081] In a feasible implementation manner, the target plug-in may include: a first plug-in for managing central processing unit resources of the smart cockpit system.

[0082] Correspondingly, the using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and the process running information at the smart cockpit system may include:

[0083] The first plug-in is used to call a first application programming interface provided by the QNX operating system to obtain first central processing unit occupancy time information corresponding to a first moment and second central processing unit occupancy time information corresponding to a second moment from a proc file at the QNX operating system.

[0084] The CPU usage rate of the smart cockpit system is calculated based on the first CPU occupation time information and the second CPU occupation time information.

[0085] In an embodiment of the present invention, the proc file at the QNX operating system may generally contain relevant system operation information of the intelligent cockpit system, such as CPU resource usage, system hardware configuration information, etc. Based on this, the proc file at the QNX operating system may be read by calling the first application programming interface to obtain the first central processing unit occupation time information corresponding to the first moment and the second central processing unit occupation time information corresponding to the second moment. Among them, the first / second central processing unit occupation time information may reflect the cumulative length of time that the central processing unit is occupied by each process from the moment when the central processing unit was last started to the first / second moment.

[0086] Specifically, the CPU usage rate at the smart cockpit system can be calculated in the following manner, that is, CPU usage rate = 100-(((second CPU occupancy time information-first CPU occupancy time information)*100) / time difference between the second moment and the first moment, which is convenient and quick. Of course, the CPU usage rate at the smart cockpit system can also be calculated in other ways, which are not specifically limited.

[0087] In actual applications, the first application programming interface can specifically read the / proc / {cpuid} / as file and use the devctl function to obtain the occupancy time information of the central processing unit CPU to which each cpuid belongs. Of course, other functions can also be used to obtain the occupancy time information of the central processing unit CPU, and there is no specific limitation on this. It is understandable that it is also possible to obtain the central processing unit occupancy time information of each process in the smart cockpit system based on a similar principle, and then calculate the central processing unit utilization rate of each process to analyze the operation status of each process, which will not be elaborated.

[0088] In practical applications, the preset CPU resource management policy may indicate a preset collection period for the CPU occupancy time information, for example, 500ms, 1s, 2s, etc., without specific limitation. The first moment and the second moment may be moments for collecting the CPU occupancy time information within two or more adjacent collection periods, so that the operation status of the CPU resources can be monitored and managed according to actual needs.

[0089] Also, since a large amount of CPU resources in the smart cockpit system will be used to start various processes after the smart cockpit system is started, it is easy for the CPU to run at full capacity, which is a normal phenomenon. Therefore, the preset CPU resource management strategy can also be pre-configured to indicate that within a specified time after the smart cockpit system is started, there is no need to call the first application programming interface to obtain the CPU occupancy time information, which is flexible.

[0090] In this embodiment, the solution of using the first application programming interface to obtain the CPU usage rate of the smart cockpit system is more efficient than the solution of using the TOP command of the QNX operating system to obtain the CPU usage rate of the smart cockpit system, which is beneficial to ensuring the real-time and accuracy of the obtained CPU usage rate.

[0091] In a feasible implementation manner, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information may include:

[0092] According to a preset CPU resource management strategy, it is determined whether the CPU usage rate reaches a first threshold value to obtain a first determination result.

[0093] If the first judgment result indicates that the CPU usage rate reaches a first threshold, a first instruction for instructing to shut down or restart a first process at the smart cockpit system is generated; or,

[0094] If the first judgment result indicates that the CPU usage rate reaches a first threshold, first management information for managing the CPU resources is sent to a second process at the smart cockpit system; the second process is used to release at least part of the occupied CPU resources according to the first management information.

[0095] In the embodiments of this specification, in order to ensure the stable operation of the smart cockpit system, it is usually necessary to avoid the central processor of the smart cockpit system being in a full load or overload state. Therefore, when the CPU usage rate reaches a first threshold, the preset CPU resource management strategy can be used to control the release of at least part of the occupied CPU resources of the smart cockpit system.

[0096] Specifically, according to actual needs, the first process and / or the second process that can cooperate to release the occupied CPU resources can be pre-screened from the processes running in the smart cockpit system. Generally, the behavior of the first process and / or the second process releasing the occupied CPU resources will not affect the normal operation of the smart cockpit system; and the first process and the second process can be the same process or different processes; the specific types of the first process and / or the second process are not limited here.

[0097] In actual applications, the smart cockpit system or the first plug-in can close or restart the first process at the smart cockpit system by responding to the first instruction generated by the first plug-in, thereby releasing the CPU resources once occupied by the first process, which is convenient and quick. Alternatively, the first plug-in can also generate and send first management information to the second process; the second process can know that the current CPU usage rate is high based on the first management information, and it can decide whether to release at least part of the CPU resources it has occupied based on its actual operating conditions, which is not only flexible, but also conducive to ensuring the normal and stable operation of the smart cockpit system.

[0098] In a feasible implementation manner, the target plug-in may include: a second plug-in for managing memory resources of the smart cockpit system.

[0099] Correspondingly, the using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and the process running information at the smart cockpit system may include:

[0100] After receiving the preset event trigger information, the second plug-in is used to call the second application programming interface provided by the QNX operating system to obtain the amount of memory resources occupied by the third process at the smart cockpit system.

[0101] Among them, the preset event trigger information is information generated by a preset event set by triggering the second plug-in to pre-call the third application programming interface provided by the QNX operating system when the remaining amount of memory resources at the smart cockpit system is less than a second threshold.

[0102] In the embodiment of this specification, in order to reduce the resources consumed by frequently calling the API interface to check the memory resource usage of the smart cockpit system, the third application programming interface provided by the QNX operating system can be called in advance by the second plug-in to register a preset event that can be triggered when it is identified that the remaining amount of memory resources at the smart cockpit system is less than the second threshold. And, after receiving the preset event trigger information generated after the preset event is triggered, the second plug-in can call the second application programming interface provided by the QNX operating system to obtain the amount of memory resources occupied by the third process at the smart cockpit system, which can not only ensure that a more comprehensive and specific memory resource usage is obtained in time when an abnormality or risk occurs in the memory resource, but also reduce the frequency of obtaining a more comprehensive and specific memory resource usage, and has good flexibility.

[0103] In practical applications, the third application programming interface may include but is not limited to the procmgr_value_notify_add interface, and the second application programming interface may include but is not limited to the procmgr_value_current interface. The second threshold may be set according to actual needs, for example, may be tens to hundreds of megabytes, etc., and is not specifically limited thereto.

[0104] In a feasible implementation manner, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information may include:

[0105] According to the preset memory resource management strategy, it is determined whether the amount of memory resources occupied by the third process reaches a third threshold, and a second determination result is obtained.

[0106] If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, a second instruction for instructing to close or restart the third process is generated.

[0107] If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, second management information for managing the memory resources is sent to the third process; the third process is used to release at least part of the occupied memory resources according to the second management information.

[0108] In the embodiments of this specification, a relatively reasonable preset maximum amount of memory resources that can be used by the third process at the smart cockpit system can be pre-determined as the third threshold corresponding to the third process. When the remaining amount of memory resources at the smart cockpit system is less than the second threshold, after obtaining the amount of memory resources occupied by the third process, if it is determined that the amount of memory resources occupied by the third process reaches the corresponding third threshold, it can be indicated that the actual amount of memory resources occupied by the third process is too much, so that the second plug-in can generate a second instruction according to the preset memory resource management strategy; so that the smart cockpit system or the second plug-in can respond to the second instruction, and the third process whose current amount of memory resources has reached the corresponding third threshold can be closed or restarted to release the memory resources once occupied by the third process, which is convenient and quick.

[0109] Alternatively, the second plug-in can also generate and send second management information to the third process. The third process can know from the second management information that it currently occupies too much memory resources, so that it can decide whether to release at least part of the memory resources it has occupied based on its actual operating conditions. This not only has good flexibility, but also helps to ensure the normal and smooth operation of the smart cockpit system.

[0110] In actual applications, under normal circumstances, releasing the memory resources occupied by the third process will not affect the normal operation of the smart cockpit system; and the third process can be the same process as the aforementioned first process, second process, etc., or a different process; the specific type of the third process is not limited here.

[0111] In a feasible implementation, Figure 1 The method may also include:

[0112] It is determined whether the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, and a third determination result is obtained.

[0113] If the third judgment result indicates that the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, then the relevant configuration parameter data of the third process is stored.

[0114] In the embodiments of this specification, during the operation of the smart cockpit system, if the remaining amount of memory resources at the smart cockpit system is less than the second threshold at different times, the preset event will usually be triggered multiple times. If the amount of memory resources occupied by a third process reaches the corresponding third threshold when it is triggered multiple times at the preset time, the second plug-in may generate a second instruction or second management information for the same third process multiple times at different times, so that the third process may perform multiple shutdown or restart operations in response to each of the second instructions or the second management information. Since such third processes have multiple cases where the actual amount of memory resources occupied exceeds the ideal amount of memory resources (i.e., the third threshold), there may usually be anomalies or risks. Therefore, the relevant configuration parameter data of the third process whose shutdown times or restart times in response to the second instruction / second management information reach the fourth threshold can be stored, so as to optimize it by analyzing the relevant configuration parameter data of the third process in the future, which is conducive to ensuring the normal and stable operation of the smart cockpit system.

[0115] In practical applications, the size of the fourth threshold can be set according to actual needs, for example, 3 times, 5 times, etc., and there is no specific limitation on this. The type of the configuration parameter data related to the third process to be stored can also be set according to actual needs, for example, the environment variables of the third process, the third threshold corresponding to the amount of memory resources allowed to be occupied by the third process, etc., and there is no specific limitation on this.

[0116] In a feasible implementation manner, the target plug-in may include: a third plug-in for managing non-volatile storage resources of the smart cockpit system.

[0117] Correspondingly, the using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and the process running information at the smart cockpit system may include:

[0118] The fourth application programming interface provided by the QNX operating system is called by using the third plug-in to obtain the resource occupancy rate of at least part of the non-volatile storage resource partition at the smart cockpit system.

[0119] Correspondingly, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information may include:

[0120] For any of the non-volatile storage resource partitions, according to a preset non-volatile storage resource management strategy, it is determined whether the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold, and a fourth determination result is obtained.

[0121] If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches the fifth threshold, a third instruction is generated to instruct to delete at least part of the data in the non-volatile storage resource partition.

[0122] If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches the fifth threshold, third management information for managing the data stored in the non-volatile storage resource partition is sent to the fourth process at the smart cockpit system.

[0123] If information indicating permission to delete the target data of the fourth process stored in the non-volatile storage resource partition is obtained from any of the fourth processes, at least part of the target data of the fourth process stored in the non-volatile storage resource partition is deleted.

[0124] In the embodiments of this specification, the smart cockpit system usually has non-volatile storage resources, for example, it may include but not be limited to: Universal Flash Storage (UFS), hard disk, magnetic disk, etc. In practical applications, in order to make full use of the non-volatile storage resources of the smart cockpit system, the non-volatile memory may be divided into multiple non-volatile storage resource partitions in advance by logical division. In addition, the fifth threshold corresponding to the resource occupancy rate of each non-volatile storage resource partition may be pre-set according to actual needs. Subsequently, if the resource occupancy rate of a non-volatile storage resource partition obtained by the third plug-in calling the fourth application programming interface provided by the QNX operating system reaches the corresponding fifth threshold, it may indicate that the amount of data stored in the non-volatile storage resource partition is too much, which may easily cause anomalies or risks.

[0125] Based on this, the third plug-in can generate a third instruction according to the preset non-volatile storage resource management strategy, so that the smart cockpit system or the third plug-in can directly delete at least part of the data in the non-volatile storage resource partition (for example, data of a preset specified type or specified process) in response to the third instruction to release the storage resources of the non-volatile storage resource partition, which is convenient and fast. Alternatively, the third plug-in can also generate and send the third management information to the fourth process. The fourth process can know that the remaining storage resources of the non-volatile storage resource partition storing its relevant data are insufficient according to the third management information, so that it can decide whether to release at least part of the non-volatile storage resource of the non-volatile storage resource partition it has occupied according to its actual operation. If so, the information indicating that the target data of the fourth process stored in the non-volatile storage resource partition is allowed to be deleted can be fed back to the third plug-in; if not, the fourth process does not need to feed back information to the third plug-in. Not only is the flexibility good, but it is also conducive to ensuring the normal and stable operation of the smart cockpit system.

[0126] In practical applications, usually, the behavior of releasing the non-volatile storage resources occupied by the fourth process will not affect the normal operation of the smart cockpit system; and the fourth process and the aforementioned first process to third process, etc. can be the same process or different processes; the specific type of the fourth process is not limited here. In addition, the fifth threshold can be set according to actual needs, for example, it can be 70%, 80%, etc., and there is no specific limitation on this.

[0127] In a feasible implementation manner, the target plug-in may include: a fourth plug-in for managing a process at the smart cockpit system.

[0128] Correspondingly, the using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and the process running information at the smart cockpit system may include:

[0129] The fourth plug-in is used to call a fifth application programming interface provided by the QNX operating system to obtain the running status information of the fifth process at the smart cockpit system.

[0130] Correspondingly, managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information may include:

[0131] For any of the fifth processes, if the running status information of the fifth process reflects that the fifth process is in an abnormal state, then according to the preset process management strategy, based on the relevant startup information of the fifth process obtained in advance, a first child process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

[0132] In the embodiments of this specification, during the operation of the smart cockpit system, there may be abnormal process operation problems. At this time, it is usually necessary to quickly restart and restore the process to ensure the normal operation of the smart cockpit system. Based on this, after the fifth process in the smart cockpit system starts to run, the fourth plug-in can be used to obtain the relevant startup information of the fifth process, so that when the fourth plug-in calls the fifth application programming interface provided by the QNX operating system and identifies that the fifth process is in an abnormal state, the fifth process can be restarted using the relevant startup information of the fifth process, which is conducive to ensuring the normal and stable operation of the smart cockpit system.

[0133] In actual applications, a child process may refer to a process created by another process (correspondingly referred to as a parent process). Since the child process and the parent process can communicate and collaborate through some system calls, the parent process can monitor and manage the child process after creating it. Therefore, in order to facilitate the fourth plug-in to continuously monitor and manage the running status of the fifth process, the plug-in process corresponding to the fourth plug-in can be made to create a first child process based on the application corresponding to the fifth process according to the preset process management strategy. At this time, the first child process in the running state is equivalent to the fifth process after restart, which is convenient and fast. Among them, the fifth process and the aforementioned first process to fourth process, etc. can be the same process or different processes; the specific type of the fifth process is not limited here.

[0134] In a feasible implementation manner, after creating a first child process for the plug-in process corresponding to the fourth plug-in to restart the fifth process, the method may further include:

[0135] The process identifier of the first sub-process is obtained by using the plug-in process corresponding to the fourth plug-in.

[0136] When the first sub-process is identified as being in an abnormal state based on the process identifier, the first sub-process is restarted to restart the fifth process. Or,

[0137] When it is identified based on the process identifier that the first sub-process is in an abnormal state, a second sub-process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

[0138] In the embodiments of this specification, the process identifier (PID) of the first child process may refer to the unique process identification information assigned to the first child process by the system. Since the parent process can use the process identifier of the child process to perceive and manage the running process of the child process, the plug-in process corresponding to the fourth plug-in can obtain the process identifier of the first child process (i.e., the fifth process after restart), so as to restart the first child process after identifying that the first child process is in an abnormal state based on the process identifier of the first child process, or to create a second child process based on the application corresponding to the fifth process to restart the fifth process again; it is efficient and fast, which is conducive to ensuring the normal and stable operation of the smart cockpit system.

[0139] In a feasible implementation manner, after running a target plug-in for managing the operation status of the smart cockpit system at the target controller of the smart cockpit system built based on the QNX operating system, the process further includes:

[0140] It is determined whether a preset closing condition for the target plug-in is met to obtain a fifth determination result.

[0141] If the fifth judgment result indicates that the preset closing condition for the target plug-in is met, a fourth instruction for instructing to close the target plug-in is generated.

[0142] In the embodiment of this specification, since there may be a situation where the use Figure 1 Based on the need to manage the operation of the smart cockpit system according to the method in the embodiment, a preset shutdown condition for the target plug-in can be set in advance according to actual needs, so that after the preset shutdown condition is met, the target plug-in is controlled to stop running by generating and responding to the fifth instruction, and then no longer in accordance with the Figure 1 The method in the embodiment manages the operation of the smart cockpit system, which has good flexibility. The preset shutdown condition may include but is not limited to: obtaining a shutdown instruction for the smart cockpit system, or obtaining a user's operation management module (i.e., Figure 1 The closing instruction of the execution subject of the solution in the above method may of course also include other conditions, which are not specifically limited.

[0143] In the embodiments of this specification, in order to facilitate understanding of the operation management module (i.e. Figure 1 The working principle and characteristics of the executive body of the scheme are combined here. Figure 2 The schematic diagram of an operation management module of an intelligent cockpit system provided by an embodiment of the present invention is illustrated for explanation. Figure 2As shown, the operation management module for the smart cockpit system may include: a core control module 21, a plug-in module 22, a policy configuration module 23, a communication module 24 and a general component module 25.

[0144] Among them, the core control module 21 can be responsible for controlling the start or stop operation of the first plug-in 201, the second plug-in 202, the third plug-in 203 and the fourth plug-in 204 included in the plug-in module 22, as well as the operating status of the control strategy configuration module 23, the communication module 24 and the general component module 25, so as to manage or terminate the operation of the intelligent cockpit system.

[0145] The plug-in module 22 may include various plug-ins for managing the operating status of the CPU resources, memory resources, non-volatile storage resources, and processes of the smart cockpit system. Of course, it may also include plug-ins for managing other resources of the smart cockpit system, and there is no specific limitation on this.

[0146] The policy configuration module 23 can be used for users to configure and store corresponding preset system management policies, for example, the frequency of monitoring the operation of the above-mentioned CPU resources, memory resources, non-volatile storage resources and processes, the first threshold to the fifth threshold mentioned in the above-mentioned embodiment, etc., which are not specifically limited.

[0147] The communication module 24 can integrate the platform's communication design and other communication frameworks to facilitate the transmission of relevant instructions (for example, the first instruction to the fourth instruction) or relevant management information (for example, the first management information to the third management information) required to be generated during the operation of each plug-in in the plug-in module 22.

[0148] The general component module 25 may include general components required for the operation of the above modules, such as timers, counters, etc., which are not specifically limited. This is helpful to avoid each module containing a large number of repeated applications, thereby improving the simplicity and practicality of the operation management module for the smart cockpit system and reducing its development cost.

[0149] The operation management module for the smart cockpit system provided in the embodiments of this specification pre-develops plug-in modules, general component modules, communication modules and policy configuration modules including various target plug-ins to monitor and manage various computing resources and processes in the smart cockpit system. It is efficient, convenient, plug-and-play and has good scalability. It can not only improve the accuracy and effectiveness of the management of the operation of the smart cockpit system and reduce the consumption of central processing unit resources, but also meet the personalized management needs of various automobile manufacturers for various resources and programs by configuring preset system management strategies. It has good flexibility and strong versatility.

[0150] See also Figure 3 , is a schematic diagram of the structure of an operation management device for an intelligent cockpit system provided by an embodiment of the present invention. Figure 3 As shown, the operation management device 03 for the smart cockpit system can be implemented as all or part of the vehicle controller (for example, the target controller of the smart cockpit system) through software, hardware or a combination of both. According to some embodiments, the operation management device 03 for the smart cockpit system may include a plug-in operation module 31, an information acquisition module 32, and a management module 33, which may specifically include:

[0151] The plug-in running module 31 is used to run a target plug-in for managing the operation status of the smart cockpit system at a target controller of the smart cockpit system built based on the QNX operating system.

[0152] The information acquisition module 32 is used to use the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of the computing resource usage information and process operation information of the smart cockpit system.

[0153] The management module 33 is used to manage the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information.

[0154] Optionally, the target plug-in may include: a first plug-in for managing central processing unit resources of the smart cockpit system.

[0155] The information acquisition module may include:

[0156] The first acquisition unit is used to use the first plug-in to call a first application programming interface provided by the QNX operating system to obtain first central processing unit occupancy time information corresponding to a first moment and second central processing unit occupancy time information corresponding to a second moment from a proc file at the QNX operating system.

[0157] The calculation unit is used to calculate the usage rate of the central processing unit at the smart cockpit system according to the occupation time information of the first central processing unit and the occupation time information of the second central processing unit.

[0158] Optionally, the management module may include:

[0159] The first judgment unit is used to judge whether the CPU usage rate reaches a first threshold according to a preset CPU resource management strategy to obtain a first judgment result.

[0160] A first generating unit is configured to generate a first instruction for instructing to shut down or restart a first process in the smart cockpit system if the first judgment result indicates that the CPU usage rate reaches a first threshold.

[0161] A first sending unit is used to send first management information for managing the central processing unit resources to a second process at the smart cockpit system if the first judgment result indicates that the central processing unit usage rate reaches a first threshold; the second process is used to release at least part of the occupied central processing unit resources according to the first management information.

[0162] Optionally, the target plug-in may include: a second plug-in for managing memory resources of the smart cockpit system.

[0163] The information acquisition module may include:

[0164] The second acquisition unit is used to use the second plug-in to call the second application programming interface provided by the QNX operating system after receiving the preset event trigger information, so as to obtain the amount of memory resources occupied by the third process at the smart cockpit system.

[0165] Among them, the preset event trigger information is information generated by a preset event set by triggering the second plug-in to pre-call the third application programming interface provided by the QNX operating system when the remaining amount of memory resources at the smart cockpit system is less than a second threshold.

[0166] Optionally, the management module may include:

[0167] The second judgment unit is used to judge whether the amount of memory resources occupied by the third process reaches a third threshold according to a preset memory resource management strategy, and obtain a second judgment result.

[0168] The second generating unit is configured to generate a second instruction for instructing to close or restart the third process if the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold.

[0169] A second sending unit is used to send second management information for managing the memory resources to the third process if the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold; the third process is used to release at least part of the occupied memory resources according to the second management information.

[0170] Optionally, the management module may include:

[0171] The third judgment unit is used for the judgment module, and is used to judge whether the number of times the third process is closed or restarted in response to each of the second instructions or the second management information reaches a fourth threshold, and obtain a third judgment result.

[0172] A storage unit is used to store relevant configuration parameter data of the third process if the third judgment result indicates that the number of shutdown times or restart times of the third process in response to each of the second instructions or the second management information reaches a fourth threshold.

[0173] Optionally, the target plug-in may include: a third plug-in for managing non-volatile storage resources of the smart cockpit system.

[0174] The information acquisition module may include:

[0175] The third acquisition unit is used to use the third plug-in to call a fourth application programming interface provided by the QNX operating system to obtain the resource occupancy rate of at least part of the non-volatile storage resource partition at the smart cockpit system.

[0176] Optionally, the management module may include:

[0177] The fourth judgment unit is used to judge whether the resource occupancy rate of any of the non-volatile storage resource partitions reaches a fifth threshold according to a preset non-volatile storage resource management strategy, and obtain a fourth judgment result.

[0178] The third generating unit is configured to generate a third instruction for instructing to delete at least part of the data in the non-volatile storage resource partition if the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold.

[0179] The third sending unit is used to send third management information for managing the data stored in the non-volatile storage resource partition to the fourth process of the smart cockpit system if the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold.

[0180] A deleting unit is used to delete at least part of the target data of the fourth process stored in the non-volatile storage resource partition if information fed back by any of the fourth processes is obtained to indicate that deletion of the target data of the fourth process stored in the non-volatile storage resource partition is allowed.

[0181] Optionally, the target plug-in may include: a fourth plug-in for managing the process at the smart cockpit system.

[0182] The information acquisition module may include:

[0183] The fourth acquisition unit is used to use the fourth plug-in to call the fifth application programming interface provided by the QNX operating system to obtain the running status information of the fifth process at the smart cockpit system.

[0184] Optionally, the management module may include:

[0185] The first creation unit is used to create a first sub-process for the plug-in process corresponding to the fourth plug-in according to a preset process management strategy and based on the relevant startup information of the fifth process obtained in advance, for any of the fifth processes, if the running status information of the fifth process reflects that the fifth process is in an abnormal state, so as to restart the fifth process.

[0186] The fifth acquiring unit is configured to acquire the process identifier of the first sub-process by using the plug-in process corresponding to the fourth plug-in.

[0187] a restart unit, configured to restart the first sub-process to restart the fifth process when the first sub-process is identified to be in an abnormal state based on the process identifier; or

[0188] The second creating unit is configured to create a second sub-process for the plug-in process corresponding to the fourth plug-in to restart the fifth process when it is identified that the first sub-process is in an abnormal state based on the process identifier.

[0189] Optional, Figure 3 The device may also include:

[0190] The judgment module is used to judge whether a preset closing condition for the target plug-in is met to obtain a fifth judgment result.

[0191] The closing module is configured to generate a fourth instruction for instructing to close the target plug-in if the fifth judgment result indicates that the preset closing condition for the target plug-in is met.

[0192] The above device embodiments correspond to the method embodiments. For specific descriptions, please refer to the description of the method embodiments, which will not be repeated here. The device embodiments are obtained based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments. For specific descriptions, please refer to the corresponding method embodiments.

[0193] The present invention also provides a storage medium, which can store a computer program. When the computer program is executed by a processor, it can implement the operation management method for the intelligent cockpit system as in the above-mentioned embodiments. The specific execution process can be found in the specific descriptions in the above-mentioned embodiments, which will not be repeated here.

[0194] In one embodiment, the present invention also provides Figure 4 The structural diagram of the vehicle controller is shown in FIG. Figure 4 At the hardware level, the vehicle controller may include a processor 41 and a memory 45, and may also include an internal bus 42, a network interface 43, a memory 44, and other hardware required for other services. The vehicle controller may be arranged in a vehicle, wherein the processor 41 may read the corresponding computer-readable instructions from the memory 45 into the memory and then run them to implement the above-mentioned operation management method for the smart cockpit system. The specific execution process may refer to the specific descriptions in the above-mentioned embodiments, which will not be described in detail here. In practical applications, the vehicle controller may be a target controller at the smart cockpit system.

[0195] In one embodiment, the present invention also provides a vehicle, which may include an operation management device or a vehicle controller for a smart cockpit system as described above, so as to execute the steps of an operation management method for the smart cockpit system through the operation management device or the vehicle controller for the smart cockpit system. The specific execution process can be found in the specific descriptions in the above embodiments and will not be repeated here.

[0196] Finally, the various embodiments of the present invention are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the storage medium, vehicle controller, and vehicle embodiments, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0197] The above description is only an embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. An operation management method for an intelligent cockpit system, comprising: At a target controller of an intelligent cockpit system built on the basis of the QNX operating system, a target plug-in for managing the operation status of the intelligent cockpit system is run; Using the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system; According to a preset system management strategy, the operation of the smart cockpit system is managed based on at least one of the computing resource usage information and the process operation information.

2. The method according to claim 1, wherein the target plug-in comprises: A first plug-in for managing central processing unit resources of the smart cockpit system; The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes: Using the first plug-in to call a first application programming interface provided by the QNX operating system, so as to obtain first central processing unit occupancy time information corresponding to a first moment and second central processing unit occupancy time information corresponding to a second moment from a proc file in the QNX operating system; The CPU usage rate of the smart cockpit system is calculated based on the first CPU occupation time information and the second CPU occupation time information.

3. The method according to claim 2, wherein the operation of the smart cockpit system is managed according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information, comprising: According to a preset CPU resource management strategy, determining whether the CPU usage rate reaches a first threshold value, and obtaining a first determination result; If the first judgment result indicates that the CPU usage rate reaches a first threshold, generating a first instruction for instructing to shut down or restart a first process at the smart cockpit system; or, If the first judgment result indicates that the CPU usage rate reaches a first threshold, sending first management information for managing the CPU resources to a second process at the smart cockpit system; The second process is used to release at least a portion of the occupied central processing unit resources according to the first management information.

4. The method according to claim 1, wherein the target plug-in comprises: A second plug-in for managing memory resources of the smart cockpit system; The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes: After receiving the preset event trigger information, the second plug-in is used to call a second application programming interface provided by the QNX operating system to obtain the amount of memory resources occupied by the third process at the smart cockpit system; Among them, the preset event trigger information is information generated by a preset event set by triggering the second plug-in to pre-call the third application programming interface provided by the QNX operating system when the remaining amount of memory resources at the smart cockpit system is less than a second threshold.

5. The method according to claim 4, wherein the managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information comprises: According to the preset memory resource management strategy, determining whether the amount of memory resources occupied by the third process reaches a third threshold, and obtaining a second determination result; If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, a second instruction for instructing to close or restart the third process is generated; or, If the second judgment result indicates that the amount of memory resources occupied by the third process reaches a third threshold, sending second management information for managing the memory resources to the third process; The third process is used to release at least part of the occupied memory resources according to the second management information.

6. The method according to claim 5, further comprising: Determine whether the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, and obtain a third determination result; If the third judgment result indicates that the number of shutdowns or restarts of the third process in response to each of the second instructions or the second management information reaches a fourth threshold, then the relevant configuration parameter data of the third process is stored.

7. The method according to claim 1, wherein the target plug-in comprises: A third plug-in for managing non-volatile storage resources of the smart cockpit system; The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes: Using the third plug-in to call a fourth application programming interface provided by the QNX operating system to obtain resource occupancy of at least part of the non-volatile storage resource partition at the smart cockpit system; The managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes: For any of the non-volatile storage resource partitions, judging whether the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold according to a preset non-volatile storage resource management strategy, and obtaining a fourth judgment result; If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches the fifth threshold, a third instruction for instructing to delete at least part of the data in the non-volatile storage resource partition is generated; or, If the fourth judgment result indicates that the resource occupancy rate of the non-volatile storage resource partition reaches a fifth threshold, third management information for managing the data stored in the non-volatile storage resource partition is sent to a fourth process at the smart cockpit system; If information indicating permission to delete the target data of the fourth process stored in the non-volatile storage resource partition is obtained from any of the fourth processes, at least part of the target data of the fourth process stored in the non-volatile storage resource partition is deleted.

8. The method according to claim 1, wherein the target plug-in comprises: a fourth plug-in for managing processes at the smart cockpit system; The using the target plug-in to call the target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process running information at the smart cockpit system includes: Using the fourth plug-in to call a fifth application programming interface provided by the QNX operating system to obtain running status information of a fifth process at the smart cockpit system; The managing the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information includes: For any of the fifth processes, if the running status information of the fifth process reflects that the fifth process is in an abnormal state, then according to the preset process management strategy, based on the relevant startup information of the fifth process obtained in advance, a first child process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

9. The method according to claim 8, after creating a first child process for the plug-in process corresponding to the fourth plug-in to restart the fifth process, further comprises: Using the plug-in process corresponding to the fourth plug-in to obtain the process identifier of the first sub-process; When it is identified based on the process identifier that the first sub-process is in an abnormal state, restarting the first sub-process to restart the fifth process; or, When it is identified based on the process identifier that the first sub-process is in an abnormal state, a second sub-process is created for the plug-in process corresponding to the fourth plug-in to restart the fifth process.

10. The method according to claim 1, after running a target plug-in for managing the operation status of the smart cockpit system at a target controller of the smart cockpit system built on the QNX operating system, further comprises: Determine whether a preset closing condition for the target plug-in is met, and obtain a fifth determination result; If the fifth judgment result indicates that the preset closing condition for the target plug-in is met, a fourth instruction for instructing to close the target plug-in is generated.

11. An operation management device for an intelligent cockpit system, comprising: A plug-in running module, used to run a target plug-in for managing the operation status of the smart cockpit system at a target controller of the smart cockpit system built based on the QNX operating system; An information acquisition module, configured to use the target plug-in to call a target application programming interface provided by the QNX operating system to obtain at least one of computing resource usage information and process operation information at the smart cockpit system; A management module is used to manage the operation of the smart cockpit system according to a preset system management strategy based on at least one of the computing resource usage information and the process operation information.

12. A storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.

13. A vehicle controller, comprising: A processor and a memory; wherein the memory stores computer-readable instructions, and the computer-readable instructions are suitable for being loaded by the processor and executing the steps of the method as claimed in any one of claims 1 to 10.

14. A vehicle, comprising the operation management device for the smart cockpit system according to claim 11 or the vehicle controller according to claim 13.

Images