Processing method and device for abnormal display of in-vehicle infotainment system, computer equipment and medium

Abstract

The invention relates to the technical field of vehicle-mounted infotainment, and discloses a processing method and device for abnormal display of a vehicle-mounted infotainment system, computer equipment and a medium, the method comprises the following steps: detecting an interactive interface component of the vehicle-mounted infotainment system running on a stack top, the interactive interface component comprising a plurality of view elements; determining whether the interactive interface component is in an abnormal display state or not according to the view element; if the interactive interface component is in the display abnormal state, controlling the interactive interface component to execute a restart operation, and obtaining a first continuous restart frequency of the interactive interface component; and when the first continuous restart frequency reaches a first preset frequency, executing a corresponding control operation on the interactive interface component based on an application repair mechanism. According to the invention, the problems that the vehicle black screen processing is complex to realize by adopting a dual-system architecture technology and the main system needs to be restarted by a minimum system are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle computers, and in particular to a method, device, computer equipment and medium for processing abnormal display of a vehicle computer system. Background Art

[0002] With the development of smart cockpit and vehicle computer technology, vehicle computer systems are increasingly used in vehicles. The stability of vehicle computer systems is crucial to driving experience and safety. However, in actual use, vehicle computer systems are prone to problems such as black screens, which can have serious impacts on car owners who are driving, such as interfering with normal driving operations and affecting the acquisition of vehicle information.

[0003] The existing black screen processing method of the car system adopts a dual system architecture to handle the black screen problem of the car and instrument system. Although this method can monitor the occurrence of black screen in the car in real time, identify the black screen scene, and intervene and automatically recover in time when the black screen scene is perceptible to the user. However, the dual system architecture has many disadvantages: on the one hand, it increases the difficulty of technical implementation, requires an additional minimum system to restart the main system, increases development costs, system complexity and bloat; on the other hand, it will generate more failure points, reduce system stability and reliability, and bring more inconvenience to users, especially car owners. Summary of the invention

[0004] In view of this, the embodiments of the present invention provide a method, device, computer equipment and medium for processing abnormal display of a vehicle computer system to solve the problem that the vehicle computer black screen processing using dual system architecture technology is complex and requires a minimum system to restart the main system.

[0005] In a first aspect, an embodiment of the present invention provides a method for processing abnormal display of a vehicle system, the method comprising:

[0006] Detecting an interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes a plurality of view elements;

[0007] Determining whether the interactive interface component is in an abnormal display state according to the view element;

[0008] If the display is in an abnormal state, controlling the interactive interface component to perform a restart operation, and obtaining a first continuous restart count of the interactive interface component;

[0009] When the first continuous restart number reaches a first preset number, a corresponding control operation is performed on the interactive interface component based on an application repair mechanism.

[0010] Further, determining whether the interactive interface component is in an abnormal display state according to the view element includes:

[0011] Performing image conversion on the view element to obtain a view image;

[0012] Identify black pixels in the view image and obtain the number of black pixels;

[0013] Obtaining the total number of pixels in the interactive interface component, and calculating the ratio of the number of black pixels to the total number of pixels;

[0014] Based on the ratio, it is determined whether the interactive interface component is in a display abnormal state.

[0015] Further, determining whether the interactive interface component is in an abnormal display state based on the ratio includes:

[0016] comparing the ratio with a preset ratio;

[0017] If the ratio is greater than the preset ratio, starting a timer and obtaining the duration of the timer;

[0018] It is determined whether the duration reaches a preset time, and when the ratio is greater than the preset ratio and the duration reaches the preset time, it is determined that the interactive interface component is in an abnormal display state.

[0019] Furthermore, the method further comprises:

[0020] If the ratio is less than the preset ratio, or the duration does not reach the preset time, it is determined that the interactive interface component is not in a display abnormal state;

[0021] Detecting pixel fluctuations of a view image in the interactive interface component;

[0022] Extracting attribute features of the pixel fluctuation, and determining whether the pixel fluctuation is an abnormal fluctuation according to the attribute features;

[0023] If the pixel fluctuation is an abnormal fluctuation, obtaining a concentration area of ​​the black pixel fluctuation;

[0024] When the gathering area is a key area, the view elements corresponding to the key area in the interactive interface component are reloaded.

[0025] Furthermore, extracting the attribute features of the pixel fluctuation and determining whether the pixel fluctuation is an abnormal fluctuation according to the attribute features includes:

[0026] Extracting fluctuation trend characteristics and periodic characteristics of the pixel fluctuation;

[0027] Calculating a first similarity between the fluctuation trend feature and a preset trend pattern, and a second similarity between the periodic feature and a preset periodic pattern;

[0028] Whether the pixel fluctuation is an abnormal fluctuation is determined according to the first similarity and the second similarity.

[0029] Furthermore, the performing corresponding control operations on the interactive interface component based on the application repair mechanism includes:

[0030] Querying whether there is an installation file associated with the interactive interface component in the preset storage space;

[0031] If there is an associated installation file, performing a replacement operation of the interactive interface component based on the installation file;

[0032] Or, if there is no associated installation file, the startup operation of the interactive interface component is prohibited, and a corresponding reminder operation is performed.

[0033] Furthermore, the method further comprises:

[0034] Obtaining the service status of each system service in the vehicle system;

[0035] Determine whether the system service is in an abnormal situation according to the service status;

[0036] If there is an abnormal situation, a restart operation of the vehicle system is executed, and a second continuous restart number of the vehicle system is obtained;

[0037] When the second continuous restart number reaches a second preset number, a corresponding service request is generated based on the abnormal situation, and the service request is sent to the server.

[0038] In a second aspect, an embodiment of the present invention provides a device for processing abnormal display of a vehicle system, the device comprising:

[0039] A detection module, used to detect the interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes multiple view elements;

[0040] A determination module, used to determine whether the interactive interface component is in an abnormal display state according to the view element;

[0041] A control module, configured to control the interactive interface component to execute a restart operation if the display is in an abnormal state, and obtain a first continuous restart count of the interactive interface component;

[0042] An execution module is used to execute a corresponding control operation on the interactive interface component based on an application repair mechanism when the first continuous restart number reaches a first preset number.

[0043] In a third aspect, an embodiment of the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0044] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method of the first aspect or any corresponding embodiment thereof.

[0045] In the fifth aspect, an embodiment of the present invention provides a vehicle, comprising: a display exception handling system and a controller; wherein the controller stores instructions for controlling the operation of the display exception handling system, and the display exception handling system is used to execute the method of the above-mentioned first aspect or any corresponding embodiment thereof according to the instructions of the controller.

[0046] The method provided in the embodiment of the present application has the following beneficial effects:

[0047] The method provided in the embodiment of the present application can accurately locate the user interaction part by paying attention to the interactive interface component at the top of the stack, promptly discover the black screen problem, provide a target for processing, and avoid resource waste and inefficiency. Judging the abnormal display state of the view element can accurately identify the problem and improve the accuracy and pertinence of the processing. Restarting the interactive interface component with a black screen can restore normal use and reduce the impact. Obtaining the number of restarts can determine the severity of the problem and avoid repeated restarts. When multiple restarts are ineffective, an application repair mechanism is adopted to avoid continuous impact on user use, inform users of problems, and improve experience and stability.

[0048] The method provided in the embodiment of the present application converts view elements into images for easy processing and analysis, and quantifies the degree of black screen by identifying the number of black pixels and calculating its ratio to the total number of pixels, making the judgment more accurate and objective and avoiding misjudgment. The preset ratio provides a judgment threshold, and combined with the timer to monitor the duration of the black screen, it can more accurately distinguish between true and false black screen problems and reduce unnecessary restarts. Accurately exclude non-black screen situations and save resources. Detecting pixel fluctuations can detect potential display anomalies, and analyzing its attribute characteristics can more accurately identify problems. Determining the area where black pixel fluctuations are concentrated can help locate problems, and reloading key areas can improve repair efficiency. By obtaining fluctuation trends and periodic characteristics, combined with similarity calculations with preset patterns, abnormal fluctuations are comprehensively judged to ensure display quality.

[0049] The method provided in the embodiment of the present application provides a way to repair faulty applications by querying installation files. When there are installation files, the application components are replaced to restore the function. When there are no installation files, the startup is prohibited and the user is reminded, which can avoid waste of resources and reduced user experience. In addition, obtaining the system service status can timely discover the root cause of the problem. After accurately judging the abnormality, the system is restarted when the system service is abnormal. The severity of the problem is evaluated by obtaining the number of consecutive restarts. If multiple restarts are invalid, a request is made to the server to ensure the long-term stable operation of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 is a flow chart of a method for processing abnormal display of a vehicle system according to an embodiment of the present invention;

[0052] Figure 2 is a schematic diagram of the process of starting an Android system according to an embodiment of the present invention;

[0053] Figure 3 is a schematic diagram of an interface showing an abnormal state of a vehicle system according to an embodiment of the present invention;

[0054] Figure 4 is a structural block diagram of a device for processing abnormal display of a vehicle system according to an embodiment of the present invention;

[0055] Figure 5 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are 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 those skilled in the art without creative work are within the scope of protection of the present invention.

[0057] According to an embodiment of the present invention, a method, apparatus, computer device and medium for processing abnormal display of a vehicle system are provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0058] In this embodiment, a method for processing abnormal display of a vehicle system is provided. Figure 1 is a flow chart of a method for processing abnormal display of a vehicle system according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0059] Step S11, detecting the interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes a plurality of view elements.

[0060] In the embodiment of the present application, the detection of the interactive interface component (Activity) running at the top of the stack of the vehicle system is performed after the system service is started, such as Figure 2 As shown in the figure, the Android system startup process is as follows: First, the device's built-in read-only memory (Boot ROM) is started. The Boot ROM contains the initial instructions for the device to start, and at the same time loads the small program (Boot Loader) responsible for initializing the hardware and loading the kernel. Next, the kernel (Kernel) is loaded through the Boot Loader. The Kernel is the core of the operating system and is used to manage system resources such as the CPU, memory, and device drivers. After the Kernel is started, the main process (init process) with a process ID of 1 is run. The init process is the parent process of other processes in the system and is responsible for starting and managing other processes. Then, the key component (Zygote AndroidRuntime) responsible for creating application processes and running continuously when the system starts is started. The key component starts the system service (System Server) responsible for starting and managing various services (such as window management, power management, notification management, etc.). Finally, based on the startup of the system service, various applications (APPs) run by users on the device, such as social media applications, games, and tool software, are started. In addition, the C++ native framework (C++Framework Native) plays a supporting role between the key components and the system services, and the JAVA framework (Java Framework) plays a supporting role between the system services and the applications.

[0061] Step S12: determining whether the interactive interface component is in an abnormal display state according to the view element.

[0062] It should be noted that if Figure 3As shown, the abnormal display state refers to the state of a black desktop screen caused by a problem with the application loading. Most of the screen area is black, and only a small number of interface elements (such as some icons at the bottom and the prompt information in the upper left corner) are visible. This situation indicates that there may be a failure in some links during the system startup application, resulting in the desktop interface that should be displayed normally not being fully presented, but being covered by a large area of ​​black. This may be caused by system resource allocation problems, software conflicts, or errors in the application itself. Through a series of judgment operations, this abnormal display state can be accurately detected and identified, and then subsequent repair measures can be taken to solve the problem.

[0063] In the embodiment of the present application, step S12 includes the following steps A1-A4:

[0064] Step A1, performing image conversion on the view element to obtain a view image.

[0065] Specifically, after obtaining the view elements (View) in the interactive interface component, these view elements need to be converted into pictures, that is, to obtain view images. For example, view elements can include various types of UI components (such as buttons, text boxes, etc.), which can be uniformly analyzed at the pixel level after being converted into images, just like projecting objects of different materials in reality onto a two-dimensional plane to observe and analyze features in a unified form.

[0066] Step A2: identifying black pixels in the view image and obtaining the number of black pixels.

[0067] Specifically, after obtaining the view image, the black pixels in the image need to be identified. This can be achieved through image recognition algorithms or related image processing libraries. The identification process includes: traversing each pixel in the image to determine whether its color value meets the definition of black (different color models have different judgment criteria, such as in the RGB model, values ​​close to (0,0,0) can be considered black). Through this traversal and identification method, the number of all black pixels is counted. This number will be used for subsequent comparison with the total number of pixels to determine the proportion of black pixels in the entire image.

[0068] Step A3, obtaining the total number of pixels in the interactive interface component, and calculating the ratio of the number of black pixels to the total number of pixels.

[0069] Specifically, in order to determine the proportion of black pixels in the view image, it is necessary to obtain the total number of pixels of the entire interactive interface component. This total number of pixels can be calculated based on the resolution or size information of the image (for example, for an image with a width of w pixels and a height of h pixels, the total number of pixels is w*h). Then divide the number of black pixels by the total number of pixels to obtain the ratio of the two. This ratio can intuitively reflect the relative number of black pixels in the entire image, and is one of the important bases for determining whether the screen is black.

[0070] Step A4: determining whether the interactive interface component is in an abnormal display state based on the ratio.

[0071] Specifically, the judgment process can be based on a pre-set judgment standard, which can be a fixed ratio threshold, and a threshold that can be dynamically changed according to different application scenarios and device types. In addition, the judgment standard also needs to be combined with other conditions, such as the duration of the state with a high proportion of black pixels, etc., to determine whether the interactive interface component is in an abnormal display state after comprehensive consideration.

[0072] In an embodiment of the present application, step A4 includes: comparing the ratio with a preset ratio; if the ratio is greater than the preset ratio, starting a timer and obtaining the duration of the timer; determining whether the duration reaches the preset time, and when the ratio is greater than the preset ratio and the duration reaches the preset time, determining that the interactive interface component is in an abnormal display state.

[0073] Specifically, first compare the calculated ratio of black pixels to the total number of pixels with the preset ratio. If the ratio is greater than the preset ratio, it means that the proportion of black pixels has exceeded the normal range, and you need to start a timer to record the duration of this high proportion state. Next, the duration recorded by the timer is judged. Only when this duration reaches the preset time and the ratio is always greater than the preset ratio, can it be determined that the interactive interface component is in an abnormal display state. This process comprehensively considers the two key factors of black pixel proportion and duration, avoids misjudgment due to momentary pixel fluctuations or accidental circumstances, and thus more accurately judges whether the interactive interface component is actually in an abnormal state such as a black screen.

[0074] In the embodiment of the present application, the method further includes the following steps C1-C5:

[0075] Step C1: if the ratio is less than a preset ratio, or the duration does not reach a preset time, it is determined that the interactive interface component is not in an abnormal display state.

[0076] Specifically, if the ratio of black pixels to the total number of pixels is less than the preset ratio, it indicates that the proportion is normal, and it can be determined that the interactive interface component is not black; if the ratio is greater than the preset ratio, but the high proportion lasts for less than the preset time, it is regarded as a short-term pixel change, and it is also determined that the screen is not black. This judgment can avoid misjudgment caused by normal visual changes or momentary interference.

[0077] Step C2, detecting pixel fluctuations of the view image in the interactive interface component.

[0078] Specifically, after determining that the interactive interface component is not black, the pixel fluctuation of its view image should be detected to find potential problems or anomalies. Analyzing the changes in pixel values ​​over a certain period of time can obtain dynamic information, such as the frequency and amplitude of pixel changes in certain areas, which helps to find minor anomalies that affect user experience or indicate system failures in advance. Methods for detecting pixel fluctuations include but are not limited to:

[0079] Method 1: Time series analysis: First, collect the image sequence of the interactive interface components at fixed time intervals. For each pixel point in each image, establish a sequence of its pixel value changing over time. By calculating the statistical characteristics of these time series, such as standard deviation, coefficient of variation, etc., the degree of fluctuation of the pixel value is measured. For example, if the standard deviation of the pixel value time series of a certain pixel point is large, it indicates that the pixel has obvious fluctuations.

[0080] Method 2: Space-frequency domain analysis: Perform a two-dimensional discrete Fourier transform on the acquired view image to convert the image from the space domain to the frequency domain. In the frequency domain, different frequency components represent changes of different scales in the image. Analyze the energy distribution of each frequency component in the frequency domain. If the energy of some high-frequency components suddenly increases, it means that there are pixel fluctuations in the image, especially local three-dimensional rapid changes. The fluctuation characteristics of pixels in the joint dimension of space and frequency can be detected.

[0081] Method 3, based on regional comparison: Divide the interactive interface component image into multiple regular small areas. At each time point, calculate the mean, variance and other statistics of the pixel values ​​in each small area. Then, compare the statistical changes of the same small area at adjacent time points. If the mean change of a certain area exceeds the set value or the variance changes significantly, it is considered that the pixels in the area fluctuate.

[0082] Step C3, extracting the attribute features of the pixel fluctuation, and determining whether the pixel fluctuation is an abnormal fluctuation according to the attribute features.

[0083] Specifically, after detecting pixel fluctuations, it is necessary to extract attribute features of the pixel fluctuations, where the attribute features may include fluctuation trend features and periodic features, which describe the changing patterns of pixels from multiple dimensions. This is the key basis for determining whether the fluctuations are abnormal.

[0084] In the embodiment of the present application, step C3 includes the following steps C31-C33:

[0085] Step C31, extracting the fluctuation trend characteristics and periodic characteristics of pixel fluctuations.

[0086] Specifically, the fluctuation trend features and periodic features are extracted from the pixel fluctuations. The fluctuation trend features can describe whether the pixel value rises, falls, or has other complex change trends over time, such as gradually getting brighter or darker. The periodic features are used to determine whether the pixel changes show a certain periodic pattern, for example, the flashing of some dynamic elements may have a fixed period. These features can determine the pattern of pixel fluctuations.

[0087] Step C32, calculating a first similarity between the fluctuation trend feature and the preset trend pattern, and a second similarity between the periodic feature and the preset periodic pattern.

[0088] Specifically, the first similarity between the fluctuation trend feature and the preset trend mode, and the second similarity between the periodic feature and the preset period mode are calculated. The preset trend mode and the preset period mode here are based on normal application interface behavior or standard modes set by system expectations. By calculating the similarity, the degree of difference between the current pixel fluctuation and the normal mode can be quantified, thereby providing a specific numerical basis for judging whether it is abnormal or not. The calculation method includes:

[0089] For the first similarity calculation: Assume that the fluctuation trend feature is represented by vector V t =(v t1 ,v t1 ,…,v tn ), the preset trend mode is represented by vector P t =(p t1 ,p t1 ,…,p tn ), where n is the feature dimension (e.g., the number of trend values ​​at different time points). Then the first similarity (here the reciprocal of the distance is used to represent the similarity, the smaller the distance, the higher the similarity) can be calculated by the following formula:

[0090]

[0091] Among them, S1 is the first similarity, v ti is the fluctuation trend characteristic, p ti The preset trend mode.

[0092] For the second similarity calculation, similar to the first similarity, assume that the periodic feature vector is V p =(v p1 ,v p1 ,…,v pm), the preset periodic pattern vector is P p =(p p1 ,p p1 ,…,p pm ), where m is the periodic feature dimension (such as the value of different periodic points). The calculation formula for the second similarity is:

[0093]

[0094] Among them, S2 is the first similarity, v pi is the fluctuation trend characteristic, p pi The preset trend mode.

[0095] Step C33, determining whether the pixel fluctuation is an abnormal fluctuation according to the first similarity and the second similarity.

[0096] Specifically, whether the pixel fluctuation is an abnormal fluctuation is determined based on the first similarity S1 and the second similarity S2. If the similarity is low, it means that the current pixel fluctuation is greatly different from the normal pattern and is likely to be an abnormal fluctuation, indicating that there is a problem with the system or a failure in the application. For example, if the first similarity is lower than a certain threshold and the second similarity is also lower than the corresponding threshold, the pixel fluctuation can be determined to be an abnormal fluctuation.

[0097] Step C4: if the pixel fluctuation is abnormal, obtain the concentrated area of ​​the black pixel fluctuation.

[0098] Specifically, after determining that the pixel fluctuation is an abnormal fluctuation, it is necessary to further obtain the clustering area of ​​the black pixel fluctuation. This clustering area is the key to the problem. It represents the place where the abnormal pixel changes are concentrated. It may be that there is a problem with a specific UI element. Locating it will help with subsequent targeted processing. The method of obtaining the black pixel fluctuation clustering area may include: treating each black pixel as a data point, and its coordinates in the image are the eigenvalues ​​of the data point. Using a density-based spatial clustering algorithm (Density-Based Spatial Clustering of Applications with Noise, DBSCAN), based on the density of data points, if the density of data points in an area exceeds a certain threshold, these points are divided into a cluster. For black pixels, this method can be used to find clustering areas with higher density, which are the clustering areas of black pixel fluctuations. In the case of abnormal pixel fluctuations, the changes in black pixels in these clustering areas can be further analyzed.

[0099] Step C5: when the clustered area is a key area, reload the view elements corresponding to the key area in the interactive interface component.

[0100] Specifically, if the clustered area of ​​black pixel fluctuations is found to be a critical area, the view elements corresponding to the critical area in the interactive interface component need to be reloaded. The critical area can be a part that has an important impact on user interaction or application functions, such as navigation bars, operation buttons, text display boxes, and other key areas of interaction or information display. Reloading the view elements in these areas can try to fix the display problems that occur and restore the normal user experience, while avoiding unnecessary restarts of the entire application or other more complex operations.

[0101] Step S13: If the display is abnormal, the interactive interface component is controlled to execute a restart operation, and a first continuous restart count of the interactive interface component is obtained.

[0102] In an embodiment of the present application, when it is determined that the interactive interface component is in an abnormal display state, corresponding measures must be taken. At this time, the system will control the interactive interface component to perform a restart operation. This is because the abnormal display state indicates that there is a problem with the application during the current operation, which may be a temporary failure, and restarting can try to restore normal operation. After each restart operation, the system will record the restart to obtain the first consecutive restart number of the interactive interface component. This number of consecutive restarts is an important basis for subsequent judgments on the severity of application problems. If the number of restarts is too many, it means that restarting alone may not be able to completely solve the problem, and further repair measures are required. For example, if the interactive interface of a navigation application is black, the system will restart the application and start counting the number of restarts to monitor the persistence of the problem.

[0103] Step S14, when the first continuous restart number reaches a first preset number, performing a corresponding control operation on the interactive interface component based on the application repair mechanism.

[0104] In the embodiment of the present application, the corresponding control operation is performed on the interactive interface component based on the application repair mechanism, including the following steps D1-D3:

[0105] Step D1, querying whether there is an installation file associated with the interactive interface component in the preset storage space.

[0106] Specifically, when the first consecutive restart times of the interactive interface component reaches the first preset times, the system will start to query in the preset storage space. The preset storage space is a specific area in the system dedicated to storing application-related files. The purpose of the query is to determine whether there is an installation file associated with the current interactive interface component. This association is determined based on the identification information of the application, such as the package name of the application. By searching for the installation file, a basis can be provided for subsequent repair operations to determine whether there are local resources that can be used for replacement or repair.

[0107] Step D2: If there is an associated installation file, a replacement operation of the interactive interface component is performed based on the installation file.

[0108] Specifically, if an installation file associated with an interactive interface component is found in the query, the system will perform a replacement operation on the interactive interface component based on this installation file. This means that the system will use the new installation file to redeploy the interactive interface component, overwriting the original component that may have problems. The replacement process includes a series of operations such as file decompression, configuration file update, and resource reloading to ensure that the new interactive interface component can run normally, thereby solving the frequent black screen problem caused by the failure of the original component.

[0109] Step D3, or, if the associated installation file does not exist, the startup operation of the interactive interface component is prohibited, and a corresponding reminder operation is performed.

[0110] Specifically, if the installation file associated with the interactive interface component is not found in the preset storage space, it means that there are no local resources available for repair. At this time, the system will prohibit the startup operation of the interactive interface component to prevent it from continuing to fail and affect the user experience. At the same time, the system will also perform corresponding reminder operations and send notifications to users to inform them that the application has a problem and cannot be started, as well as related advice information, such as checking the network connection to try to obtain the installation file from the network for repair.

[0111] In the embodiment of the present application, the method further includes the following steps E1-E4:

[0112] Step E1, obtaining the service status of each system service in the vehicle system.

[0113] Specifically, system services include but are not limited to services responsible for various functions such as network connection, sensor data processing, and background process management. The acquisition method can be through the system's internal monitoring mechanism or a specific query interface to collect various information such as the operating parameters, response time, and resource usage of each service.

[0114] Step E2, determining whether there is any abnormality in the system service according to the service status.

[0115] Specifically, the system service status is analyzed and judged. By comparing the service status with the standard parameters or expected behavior patterns under normal operating conditions, it is determined whether the system service has abnormal conditions. For example, if the response time of a service is far beyond the normal range, frequent error prompts appear, or the resource usage is too high and continues to be abnormal, it indicates that there is a problem with the system service.

[0116] Step E3: If there is an abnormal situation, a restart operation of the vehicle system is executed, and a second continuous restart number of the vehicle system is obtained.

[0117] Specifically, when it is determined that there is an abnormality in the system service, in order to try to restore the normal operation of the system, the vehicle system will be restarted. The restart operation can clear some temporary fault states and reinitialize the system service. After each restart operation, the system will record the restart to obtain the second consecutive restart number of the vehicle system, which is used for subsequent evaluation of the severity of the problem.

[0118] Step E4: when the second consecutive restart times reaches a second preset times, a corresponding service request is generated based on the abnormal situation, and the service request is sent to the server.

[0119] Specifically, when the second consecutive restart times of the vehicle system reaches the second preset times, it means that the abnormal problem of the system service cannot be solved by restarting alone. At this time, the system will generate a detailed service request based on the current abnormal situation. This request includes the type of abnormality, the system service information where the abnormality occurred, and related error logs. The service request is then sent to the server, which can send the new installation file to the vehicle system based on the received information, so that the vehicle system can download and install the system service according to the newly sent installation file, such as pushing update patches or adjusting the server configuration.

[0120] In this embodiment, a processing device for abnormal display of a vehicle system is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0121] This embodiment provides a processing device for abnormal display of a vehicle system, such as Figure 4 As shown, including:

[0122] A detection module 41 is used to detect the interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes multiple view elements;

[0123] A determination module 42, used to determine whether the interactive interface component is in an abnormal display state according to the view element;

[0124] The control module 43 is used to control the interactive interface component to perform a restart operation if the display is in an abnormal state, and obtain a first continuous restart count of the interactive interface component;

[0125] The execution module 44 is used to execute a corresponding control operation on the interactive interface component based on the application repair mechanism when the first continuous restart number reaches a first preset number.

[0126] In an optional embodiment of the present application, a determination module 42 is used to perform image conversion on view elements to obtain a view image; identify black pixels in the view image to obtain the number of black pixels; obtain the total number of pixels in the interactive interface component, and calculate the ratio of the number of black pixels to the total number of pixels; and determine whether the interactive interface component is in an abnormal display state based on the ratio.

[0127] In an optional embodiment of the present application, a determination module 42 is used to compare the ratio with a preset ratio; if the ratio is greater than the preset ratio, a timer is started and the duration of the timer is obtained; it is determined whether the duration reaches the preset time, and when the ratio is greater than the preset ratio and the duration reaches the preset time, it is determined that the interactive interface component is in an abnormal display state.

[0128] In an optional embodiment of the present application, a determination module 42 is used to determine that the interactive interface component is not in an abnormal display state if the ratio is less than a preset ratio, or the duration does not reach a preset time; detect pixel fluctuations in the view image in the interactive interface component; extract attribute features of the pixel fluctuations, and determine whether the pixel fluctuations are abnormal fluctuations based on the attribute features; if the pixel fluctuations are abnormal fluctuations, obtain a clustering area of ​​black pixel fluctuations; when the clustering area is a key area, reload the view elements corresponding to the key area in the interactive interface component.

[0129] In an optional embodiment of the present application, a determination module 42 is used to extract the fluctuation trend characteristics and periodic characteristics of pixel fluctuations; calculate a first similarity between the fluctuation trend characteristics and a preset trend pattern, and a second similarity between the periodic characteristics and a preset periodic pattern; and determine whether the pixel fluctuation is an abnormal fluctuation based on the first similarity and the second similarity.

[0130] In an optional embodiment of the present application, the execution module 44 is used to query whether there is an installation file associated with the interactive interface component in the preset storage space; if there is an associated installation file, the replacement operation of the interactive interface component is performed based on the installation file; or, if there is no associated installation file, the startup operation of the interactive interface component is prohibited, and a corresponding reminder operation is performed.

[0131] In an optional embodiment of the present application, the device also includes: an acquisition module for acquiring the service status of each system service in the vehicle system; determining whether there is an abnormal situation in the system service based on the service status; if there is an abnormal situation, executing a restart operation of the vehicle system and obtaining a second consecutive restart number of the vehicle system; when the second consecutive restart number reaches a second preset number, generating a corresponding service request based on the abnormal situation, and sending the service request to the server.

[0132] See also Figure 5 , Figure 5 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 5 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system).

[0133] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0134] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0135] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of a computer device based on the presentation of a small program landing page, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0136] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0137] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0138] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0139] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for processing abnormal display of a vehicle computer system, characterized in that: The method comprises: Detecting an interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes a plurality of view elements; Determining whether the interactive interface component is in an abnormal display state according to the view element; If the display is in an abnormal state, controlling the interactive interface component to perform a restart operation, and obtaining a first continuous restart count of the interactive interface component; When the first continuous restart number reaches a first preset number, a corresponding control operation is performed on the interactive interface component based on an application repair mechanism.

2. The method according to claim 1, characterized in that The determining, according to the view element, whether the interactive interface component is in an abnormal display state comprises: Performing image conversion on the view element to obtain a view image; Identify black pixels in the view image and obtain the number of black pixels; Obtaining the total number of pixels in the interactive interface component, and calculating the ratio of the number of black pixels to the total number of pixels; Based on the ratio, it is determined whether the interactive interface component is in a display abnormal state.

3. The method according to claim 2, characterized in that The determining whether the interactive interface component is in an abnormal display state based on the ratio includes: comparing the ratio with a preset ratio; If the ratio is greater than the preset ratio, starting a timer and obtaining the duration of the timer; It is determined whether the duration reaches a preset time, and when the ratio is greater than the preset ratio and the duration reaches the preset time, it is determined that the interactive interface component is in an abnormal display state.

4. The method according to claim 3, characterized in that The method further comprises: If the ratio is less than the preset ratio, or the duration does not reach the preset time, it is determined that the interactive interface component is not in a display abnormal state; Detecting pixel fluctuations of a view image in the interactive interface component; Extracting attribute features of the pixel fluctuation, and determining whether the pixel fluctuation is an abnormal fluctuation according to the attribute features; If the pixel fluctuation is an abnormal fluctuation, obtaining a concentration area of ​​the black pixel fluctuation; When the gathering area is a key area, the view elements corresponding to the key area in the interactive interface component are reloaded.

5. The method according to claim 4, characterized in that The extracting the attribute feature of the pixel fluctuation and determining whether the pixel fluctuation is an abnormal fluctuation according to the attribute feature includes: Extracting fluctuation trend characteristics and periodic characteristics of the pixel fluctuation; Calculating a first similarity between the fluctuation trend feature and a preset trend pattern, and a second similarity between the periodic feature and a preset periodic pattern; Whether the pixel fluctuation is an abnormal fluctuation is determined according to the first similarity and the second similarity.

6. The method according to claim 1, characterized in that The performing corresponding control operations on the interactive interface component based on the application repair mechanism includes: Querying whether there is an installation file associated with the interactive interface component in the preset storage space; If there is an associated installation file, performing a replacement operation of the interactive interface component based on the installation file; Or, if there is no associated installation file, the startup operation of the interactive interface component is prohibited, and a corresponding reminder operation is performed.

7. The method according to claim 1, characterized in that The method further comprises: Obtaining the service status of each system service in the vehicle system; Determine whether the system service is in an abnormal situation according to the service status; If there is an abnormal situation, a restart operation of the vehicle system is executed, and a second continuous restart number of the vehicle system is obtained; When the second continuous restart number reaches a second preset number, a corresponding service request is generated based on the abnormal situation, and the service request is sent to the server.

8. A device for processing abnormal display of a vehicle system, characterized in that: The device comprises: A detection module, used to detect the interactive interface component running on the top of the stack of the vehicle system, wherein the interactive interface component includes multiple view elements; A determination module, used to determine whether the interactive interface component is in an abnormal display state according to the view element; A control module, configured to control the interactive interface component to execute a restart operation if the display is in an abnormal state, and obtain a first continuous restart count of the interactive interface component; An execution module is used to execute a corresponding control operation on the interactive interface component based on an application repair mechanism when the first continuous restart number reaches a first preset number.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 7.

11. A vehicle, characterized in that: The vehicle comprises: a display exception processing system and a controller; wherein the controller stores instructions for controlling the operation of the display exception processing system, and the display exception processing system is used to execute the vehicle system display exception processing method described in any one of claims 1 to 7 according to the instructions of the controller.

Images