Security domain fault information processing method, electronic device, and smart cockpit

Abstract

Disclosed in the present invention are a security domain fault information processing method, an electronic device, and a smart cockpit. The method comprises the steps of: a system control service creating a communication channel for performing communication interaction with a system kernel, and searching a system information dynamic library for information of all processes that are currently running in a system; promptly detecting whether a security domain process among the current system processes has crashed, and if yes, reading a process number of the security domain process by means of the communication channel; and acquiring process information of the security domain process and current system information, and sending the process information and the current system information to a cloud. In the present invention, a system kernel is used as an information acquisition way. Compared with conventional application instrumentation solutions, the present invention can still accurately acquire key information when an application crashes.

Description

A method for processing fault information in the security domain, electronic devices, and intelligent cockpits. Technical Field

[0001] This invention relates to a fault information processing method, electronic device, and smart cockpit, and more particularly to a fault information processing method, electronic device, and smart cockpit in the security domain. Background Technology

[0002] The system safety domain refers to the critical, error-prone parts of a car's intelligent cockpit, such as instrument cluster applications, head-up displays, and vehicle speed algorithms. These applications are crucial to safe vehicle operation. Applications within the safety domain require rapid response and zero errors. However, problems and malfunctions can still occur within the safety domain, potentially leading to traffic accidents in severe cases. Summary of the Invention

[0003] The purpose of this invention is to provide a method for processing fault information in a security domain, an electronic device, and a smart cockpit. The primary technical problem to be solved is that when a fault occurs, the system can report it to the server immediately. The secondary technical problem is establishing a communication channel with the system kernel. When a process crashes, the system kernel broadcasts the crash information to all services that have established channels and subscribed to relevant events, highlighting the shortcomings of existing technologies.

[0004] This invention provides the following solution:

[0005] A method for processing security domain fault information based on kernel communication, applied to a vehicle security domain fault information processing system, includes:

[0006] The system control service creates communication channels for communicating and interacting with the system kernel, and queries the system information dynamic library for information on currently running processes.

[0007] The system can detect in real time whether the security domain process in the current system process has crashed. If the security domain process in the current system process is detected to have crashed, the process ID of the security domain process is read through the communication channel.

[0008] Obtain process information and current system information of the security domain process, and send the process information and current system information to the cloud.

[0009] Furthermore, the step of querying the currently running process information from the system information dynamic library specifically involves storing the process information in a corresponding data structure.

[0010] Furthermore, the real-time detection of whether the security domain process in the current system processes has crashed, and if a crash is detected, reading the process ID of the security domain process through the communication channel, further includes:

[0011] The system can detect whether a system process has crashed in real time. If a system process crash is detected, the system kernel broadcasts a pulse signal to the communication channel.

[0012] The system control service receives the pulse signal and checks whether there is a process ID in the pulse signal that has crashed.

[0013] The system control service acquires the pulse signal and reads the process ID carried in the pulse signal, which includes information about process crash.

[0014] The system retrieves the process information of the current running status from the system information dynamic library, compares it with the process ID, and detects whether the crashed process is a security domain process.

[0015] Furthermore, if the detection results confirm that the process causing the crash is a security domain process, then the information of this process, along with the current system information, will be sent to the cloud.

[0016] Furthermore, the step of obtaining the process information and current system information of the security domain process, and sending the process information and current system information to the cloud, further includes:

[0017] A communication middleware called sharedinfoAPI based on both QNX and Android systems was established to provide communication interfaces for each system and enable data exchange of process information and current system information through shared memory.

[0018] A security domain fault information processing system based on kernel communication includes:

[0019] The communication channel establishment module and the system control service create communication channels for communication and interaction with the system kernel, and query the currently running process information from the system information dynamic library.

[0020] The security domain process crash detection module detects in real time whether the security domain process in the current system process has crashed. If the crash of the security domain process in the current system process is detected, the process ID of the security domain process is read through the communication channel.

[0021] The process information / system information sending module obtains the process information and current system information of the security domain process and sends the process information and current system information to the cloud.

[0022] A smart cockpit, the smart cockpit including the aforementioned kernel communication-based security domain fault information processing system, for implementing the aforementioned kernel communication-based security domain fault information processing method.

[0023] A vehicle having the aforementioned intelligent cockpit.

[0024] An electronic device includes: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method.

[0025] A computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the method.

[0026] Compared with the prior art, the present invention has the following advantages:

[0027] Existing event tracking solutions lack a mechanism for collecting and reporting information on emergency events such as process crashes and system downtime. This results in the inability to continue uploading relevant information when the application itself encounters problems. This invention fills this gap by employing the system kernel as the information acquisition method. Compared to traditional application-specific event tracking solutions, this invention can still accurately obtain critical information even when the application crashes.

[0028] This invention collects and uploads information during emergencies such as process crashes and system downtime. It achieves data acquisition by establishing a system channel and acquiring system pulses, and uses this data as crucial evidence for analysis and processing. This invention fills the gap in current data tracking solutions regarding the lack of effective methods for collecting and reporting information during emergencies such as process crashes and system downtime. By introducing a data acquisition method based on the system kernel and using the establishment of a system channel and acquisition of system pulses as its implementation principle, it provides a reliable, efficient, and comprehensive means to cover data collection needs under various abnormal conditions. Attached Figure Description

[0029] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0030] Figure 1 is a flowchart of a security domain fault information processing method based on kernel communication.

[0031] Figure 2 is an architecture diagram of a security domain fault information processing system based on kernel communication.

[0032] Figure 3 is a flowchart of a specific implementation of the present invention in a specific application scenario.

[0033] Figure 4 is a timing diagram of a specific embodiment of the present invention in a specific application scenario.

[0034] Figure 5 is a schematic diagram of the electronic device. Detailed Implementation

[0035] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0036] Figure 1 shows the flowchart of the security domain fault information processing method based on kernel communication, which is applied to a vehicle security domain fault information processing system, including:

[0037] Step S1: The system control service creates a communication channel for communicating and interacting with the system kernel, and queries the system information dynamic library for information on all currently running processes.

[0038] Step S2: Real-time detection of whether the security domain process in the current system process has crashed. If the security domain process in the current system process is detected to have crashed, the process ID of the security domain process is read through the communication channel.

[0039] Step S3: Obtain the process information of the security domain process and the current system information, and send the process information and the current system information to the cloud.

[0040] The technical solutions provided in steps S1 to S3 describe the workflow of a system control service:

[0041] In step S1, the system control service creates a communication channel and queries information about all currently running processes in the system. First, the system control service creates a communication channel for interacting with the system kernel. Through this channel, it sends requests to the kernel and retrieves corresponding data. Simultaneously, it queries the system information dynamic library for information about all currently running processes.

[0042] In step S2, the system detects whether a security domain process has crashed in real time and reads its process ID. If a security domain process is found to have crashed, the system reads the process ID corresponding to that security domain process through the previously created communication channel.

[0043] In some embodiments disclosed in step S3, the relevant information of the security domain process (including its user, permissions, etc.) and the current operating environment (i.e. which programs are currently running) are sent to the cloud server for analysis and processing.

[0044] In this embodiment, a security domain refers to a region in the QNX system used to meet high real-time requirements. A security domain is a mechanism established to ensure that the vehicle system can acquire and process important data in a timely and accurate manner. For example, many important tasks in a car need to be executed in real time, such as braking control and acceleration control. If these tasks cannot be responded to in a timely manner or errors occur, it may lead to traffic accidents. The technical problem to be solved in this embodiment is to send information related to the security domain to a cloud server for analysis and processing when the security domain process crashes, in order to identify the source of the problem and track anomalies. By collecting relevant information when the security domain crashes and sending it to a cloud server for analysis and processing, this embodiment can improve the real-time performance of the vehicle system and enhance its ability to monitor anomalies.

[0045] Preferably, the step of querying all currently running process information from the system information dynamic library specifically involves storing the process information in a corresponding data structure.

[0046] In this embodiment, process information is managed by a dedicated dynamic library. The vehicle system's applications and system kernel can query process information by calling functions in this library and use the dynamic library to manage process information, and obtain the corresponding information by calling functions in the dynamic library.

[0047] Preferably, the real-time detection of whether the security domain process in the current system processes has crashed, and if a crash of the security domain process in the current system processes is detected, then reading the process ID of the security domain process through the communication channel, further includes:

[0048] The system can detect whether a system process has crashed in real time. If a system process crash is detected, the system kernel broadcasts a pulse signal to the communication channel.

[0049] The system control service receives the pulse signal and checks whether there is a process ID in the pulse signal that has crashed.

[0050] The system control service acquires the pulse signal and reads the process ID carried in the pulse signal, which includes information about process crash.

[0051] The system retrieves the process information of the current running status from the system information dynamic library, compares it with the process ID, and detects whether the crashed process is a security domain process.

[0052] For example, if the detection results confirm that the process that crashed is a security domain process, then the information of this process and the current system information are sent to the cloud.

[0053] This embodiment describes a method for real-time detection of whether a security domain process in a system has crashed. A security domain process refers to a specific process in an in-vehicle system responsible for processing real-time data and protecting system security.

[0054] In this embodiment, a monitoring program or other means are used to detect in real time whether the security domain process in the current system process has crashed.

[0055] If a security domain process crash is detected, the process ID of that security domain process will be read through a communication channel. This communication channel can be an interface provided by the operating system or other reliable communication methods; in this embodiment, it is the communication channel. If a security domain process crash is detected, the operating system kernel will broadcast a pulse signal to the communication channel.

[0056] After receiving the pulse signal, the system control service will parse the information carried in it and obtain the corresponding security domain process number.

[0057] Preferably, the step of obtaining the process information of the security domain process and the current system information, and sending the process information and the current system information to the cloud, further includes:

[0058] A communication middleware called sharedinfoAPI based on both QNX and Android systems was established to provide communication interfaces for each system and enable data exchange of process information and current system information through shared memory.

[0059] This embodiment describes how to exchange process information and system information in a QNX and Android dual-system environment through a shared memory mechanism, including the following steps:

[0060] Define a shared memory region: Based on the operating system's memory management API, define a shared memory region in QNX and Android systems.

[0061] Create a communication middleware: Develop a middleware called sharedinfoAPI to provide a communication interface between the QNX and Android systems. sharedinfoAPI can access shared memory regions and provide read and write operations.

[0062] Implement process information acquisition: Implement the function of obtaining the current system status in both systems, such as system load, network status, hardware information, etc.

[0063] Data interaction: The process and system information obtained is written to the shared memory area through the sharedinfo API, and the consistency of the data is ensured based on the synchronization mechanism.

[0064] Data reading and sending: Based on network programming and data encryption technology, data is written to shared memory, enabling another system to read the information through the sharedinfo API and send it to the cloud.

[0065] For the purpose of simplicity, the method steps disclosed in the above embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0066] Any flowchart or other description of a process or method can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of preferred embodiments of the invention includes additional implementations in which functions may be performed and implemented not in the order shown or discussed, including substantially simultaneously or in reverse order according to the functions involved, or by executing computer instructions and implementing corresponding functions according to program structures such as loops, branches, etc., as will naturally be understood by those skilled in the art when practicing embodiments of the invention.

[0067] The security domain fault information processing system based on kernel communication, as shown in Figure 2, includes:

[0068] The communication channel establishment module, the system control service creates a communication channel for communication and interaction with the system kernel, and queries the system information dynamic library for information on all currently running processes in the system.

[0069] The security domain process crash detection module detects in real time whether the security domain process in the current system process has crashed. If the crash of the security domain process in the current system process is detected, the process ID of the security domain process is read through the communication channel.

[0070] The process information / system information sending module obtains the process information and current system information of the security domain process and sends the process information and current system information to the cloud.

[0071] The implementation methods of the system described above are merely illustrative. For example, the various functional modules, units, or subsystems within the system may or may not be physically separate, or they may or may not be physical units; that is, they may be located in the same place or distributed across multiple different systems and their subsystems or modules. Those skilled in the art can select some or all of the functional modules, units, or subsystems to achieve the objectives of the embodiments of the present invention according to actual needs. Those skilled in the art can understand and implement the above-described situations without any creative effort.

[0072] Figure 3 shows a flowchart of a specific implementation of the present invention in a particular application scenario. The flowchart illustrates the overall data flow of the embodiment of the present invention, and is used to implement the general process of the system control service scheme:

[0073] The QNX and Android dual-system is currently the most widely used cockpit implementation solution for automotive smart cockpits, and this invention is designed based on this.

[0074] The system security domain applications all run on the QNX system, while the communication services with the cloud run on Android.

[0075] The system control service first queries the system information dynamic library for information on all currently running processes and stores it in the corresponding data structure.

[0076] The system control service creates a communication channel to establish a connection with the kernel. This communication channel is mainly used to receive pulse signals from the system kernel.

[0077] When a system process crashes, the kernel broadcasts a pulse signal to all processes that have established channels with it.

[0078] After receiving the pulse signal, the system control service reads the pulse information, which carries the process ID of the process that crashed.

[0079] After obtaining the process ID of the crashed process, retrieve all currently running process information from the system information dynamic library and compare it with the process information obtained initially.

[0080] The system compares and filters to determine whether the process that crashed is a security domain process. If it is, it reports the detailed information of the process and the current system information to the cloud; otherwise, it does nothing.

[0081] The sharedinfoAPI is a communication middleware between two operating systems, providing a communication interface for both parties. It uses shared memory and can complete initialization during system startup, resulting in higher efficiency. Process crashes occurring during system startup can also be successfully uploaded to the cloud.

[0082] Public_SDK is a service for communicating with the cloud, mainly used to receive and send data to the cloud.

[0083] Figure 4 shows a timing diagram of a specific implementation of the present invention in a specific application scenario:

[0084] The system control service establishes a communication channel with the system kernel.

[0085] The system control service obtains process information from the system information dynamic library.

[0086] For example, the process information stored in the system information dynamic library includes, but is not limited to, process identifier, startup time, memory usage, CPU usage, and security level.

[0087] When a process crash occurs in the system, the system kernel sends a pulse to the system control service.

[0088] The system control service requests the system information dynamic library again to obtain the current process running information.

[0089] The system control service compares the process execution information from the two instances and uses the process ID interpreted from the pulse signal to determine whether the process crashed within the security domain.

[0090] If the security domain process crashes, data is sent to the publicSDK to report to the cloud.

[0091] When a system crash occurs, the system kernel sends a pulse to the system control service.

[0092] The system control service does not filter system downtime behavior and reports it directly to the cloud server.

[0093] For example, record detailed information and context of the crash process, analyze the cause of the crash, and report the analysis results to the cloud server.

[0094] The technical solution of this embodiment can be further improved:

[0095] This embodiment is a system control service method for monitoring and responding to process crashes and system downtime in an operating system, including the following steps:

[0096] Establish a communication channel with the system kernel to receive pulse signals indicating changes in system state;

[0097] Process information is periodically retrieved from and stored in the system information dynamic library;

[0098] When a process crash pulse signal is received from the system kernel, the system requests the system information dynamic library again to obtain the current process status information.

[0099] By comparing process information before and after the crash, crash events of security domain processes can be identified and filtered out.

[0100] The filtered crash information is sent to the cloud server for recording and analysis via the publicSDK module.

[0101] This invention improves system stability and security: by monitoring the process status in the operating system in real time, this invention can promptly detect and respond to process crashes and system downtime events. Especially for processes within a security domain, this solution ensures rapid identification and action upon the occurrence of a crash, thereby reducing potential security risks.

[0102] This invention optimizes the fault diagnosis and recovery process: by comparing information before and after a process crash, the system control service can provide detailed crash context, which helps to quickly locate the cause of the problem and accelerate the fault diagnosis process. Simultaneously, reporting crash information to the cloud server allows for further analysis of crash patterns using big data analytics, providing data support for system optimization and fault prevention.

[0103] The embodiments of the present invention enhance data security: before reporting crash information to the cloud server, the system control service encrypts the data to ensure data security during transmission and prevent the leakage of sensitive information.

[0104] This invention improves user experience: by rapidly responding to system crashes and process failures, this technical solution reduces the impact of system malfunctions on user operations, thus enhancing the user experience. Especially in multi-user environments, it ensures system continuity and reliability.

[0105] The embodiments of the present invention improve the performance of system maintenance and upgrades: the process information and crash data collected by the system control service can provide valuable information resources for system maintenance personnel, helping them to better understand the system's operating status and potential problems, thereby guiding system maintenance and upgrade work and improving the long-term stability and performance of the system.

[0106] The embodiments of the present invention realize automated monitoring and management: by monitoring and managing the status of the operating system in an automated manner, the need for manual intervention is reduced, the operation and maintenance costs are lowered, and the accuracy and response speed of monitoring are improved.

[0107] In summary, the embodiments of the present invention, through their advanced monitoring, identification, response, and reporting mechanisms, not only improve the stability and security of the system, but also enhance user experience and data protection through data analysis and encryption technologies, providing strong support for the long-term healthy operation of the system.

[0108] As shown in Figure 5, in addition to disclosing a method and system for processing security domain fault information based on kernel communication, this invention also discloses a corresponding intelligent cockpit, vehicle, electronic device, and storage medium:

[0109] A smart cockpit, the smart cockpit including the aforementioned kernel communication-based security domain fault information processing system, for implementing the aforementioned kernel communication-based security domain fault information processing method.

[0110] A vehicle having the aforementioned intelligent cockpit.

[0111] An electronic device is characterized in that it comprises: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method.

[0112] A computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the method.

[0113] Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. As shown in Figure 5, the electronic device provided in this embodiment of the present invention includes: one or more processors 710 and a storage device 720; the processors 710 in the electronic device may be one or more, and one processor 710 is used as an example in Figure 5; the storage device 720 is used to store one or more programs; the one or more programs are executed by the one or more processors 710, so that the one or more processors 710 implement the security domain fault information processing method based on kernel communication as described in any one embodiment of the present invention.

[0114] The electronic device may also include an input device 730 and an output device 740.

[0115] The processor 710, storage device 720, input device 730 and output device 740 in this electronic device can be connected by a bus or other means. Figure 5 shows an example of connection via a bus.

[0116] The storage device 720 in this electronic device serves as a computer-readable storage medium, capable of storing one or more programs. These programs can be software programs, computer-executable programs, or modules, such as the program instructions / modules corresponding to the kernel-communication-based security domain fault information processing method provided in this embodiment of the invention. The processor 710 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the storage device 720, thereby implementing the kernel-communication-based security domain fault information processing method described in the above embodiment.

[0117] Storage device 720 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device. Furthermore, storage device 720 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, storage device 720 may further include memory remotely located relative to processor 710, which can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0118] Input device 730 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the electronic device. Output device 740 may include display devices such as a display screen.

[0119] Furthermore, when one or more programs included in the aforementioned electronic device are executed by one or more processors 710, the programs perform the operations of steps S1 to S3.

[0120] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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.

[0121] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features but not others included in other embodiments, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, any of the embodiments claimed in the claims can be used in any combination of embodiments of the invention.

[0122] In the description of this specification, references to terms such as "an embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0123] Furthermore, the technical solutions of the various embodiments of the present invention can be combined with each other, but only if they are feasible for those skilled in the art. If the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the present invention.

[0124] All features disclosed in this specification, or steps in all disclosed methods or processes, may be combined in any way, except for mutually exclusive features and / or steps. Any feature disclosed in this specification, unless specifically stated otherwise, may be replaced by other equivalent or similar features. That is, unless specifically stated otherwise, each feature is merely one example of a series of equivalent or similar features. Throughout this specification, the same reference numerals indicate the same elements.

[0125] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the corresponding claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the corresponding claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing security domain fault information based on kernel communication, applied to a vehicle security domain fault information processing system, characterized in that, include: The system control service creates communication channels for communicating and interacting with the system kernel, and queries the system information dynamic library for information on currently running processes. The system can detect in real time whether the security domain process in the current system process has crashed. If the security domain process in the current system process is detected to have crashed, the process ID of the security domain process is read through the communication channel. Obtain process information and current system information of the security domain process, and send the process information and current system information to the cloud.

2. The method for processing security domain fault information based on kernel communication according to claim 1, characterized in that, The step of querying the currently running process information from the system information dynamic library specifically involves storing the process information in a corresponding data structure.

3. The method for processing security domain fault information based on kernel communication according to claim 1, characterized in that, The real-time detection of whether the security domain process in the current system processes has crashed, and if a crash is detected, reading the process ID of the security domain process through the communication channel, further includes: The system can detect whether a system process has crashed in real time. If a system process crash is detected, the system kernel broadcasts a pulse signal to the communication channel. The system control service receives the pulse signal and checks whether there is a process ID in the pulse signal that has crashed. The system control service acquires the pulse signal and reads the process ID carried in the pulse signal, which includes information about process crash. The system retrieves the process information of the current running status from the system information dynamic library, compares it with the process ID, and detects whether the crashed process is a security domain process.

4. The security domain fault information processing method based on kernel communication according to claim 3, characterized in that, If the detection results confirm that the process that crashed is a security domain process, then the information of this process and the current system information will be sent to the cloud.

5. The method for processing security domain fault information based on kernel communication according to claim 1, characterized in that, The step of obtaining process information and current system information of the security domain process, and sending the process information and current system information to the cloud, further includes: A communication middleware called sharedinfoAPI based on both QNX and Android systems was established to provide communication interfaces for each system and enable data exchange of process information and current system information through shared memory.

6. A security domain fault information processing system based on kernel communication, characterized in that, include: The communication channel establishment module and the system control service create communication channels for communication and interaction with the system kernel, and query the currently running process information from the system information dynamic library. The security domain process crash detection module detects in real time whether the security domain process in the current system process has crashed. If the crash of the security domain process in the current system process is detected, the process ID of the security domain process is read through the communication channel. The process information / system information sending module obtains the process information and current system information of the security domain process and sends the process information and current system information to the cloud.

7. An intelligent cockpit, characterized in that, The intelligent cockpit includes the security domain fault information processing system based on kernel communication as described in claim 6, used to implement the security domain fault information processing method based on kernel communication as described in any one of claims 1 to 5.

8. A vehicle, characterized in that, The vehicle is equipped with the intelligent cockpit as described in claim 1.

9. An electronic device, characterized in that, include: The system includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that, It stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the method according to any one of claims 1 to 5.

Images