Detection and recovery method and device for stuck display interface of vehicle machine and storage medium

By defining the stuck detection object class of the pointer template class and the reference count base class, the stuck detection and recovery of the vehicle display interface is realized, and the problems of insufficient detection accuracy and low recovery efficiency in the existing technology are solved, and the system stability is improved Sex and user experience.

CN118916201APending Publication Date: 2024-11-08VOYAH AUTOMOBILE TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411030694.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-30
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The existing vehicle-machine display interface jam detection and recovery methods have problems such as insufficient detection accuracy and low recovery efficiency, which is difficult to effectively solve the problem of degraded user experience in real time.

Method used

By defining pointer template classes, reference count base classes and stuck detection object classes, the display module is implemented to detect stuck and callbacks in time, collect stuck information and restart the display module, and use the remote server to generate update packages for interface recovery.

Benefits of technology

It improves the stability and user experience of the system, reduces user troubles caused by interface stuck, accelerates problem diagnosis and resolution efficiency, and improves the performance and user satisfaction of the on-board display system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916201A_ABST
    Figure CN118916201A_ABST
Patent Text Reader

Abstract

The invention discloses a method and a device for detecting and recovering jamming of a display interface of an in-vehicle infotainment device and a storage medium, and relates to the technical field of automotive electronics, the method for detecting and recovering jamming of the display interface of the in-vehicle infotainment device comprises the following steps: defining a pointer template class, a reference count base class and a jamming detection object class inherited from the reference count base class; completing display module jamming detection according to the pointer template class and the jamming detection object class, and triggering timed callback; collecting jamming information in the timed callback, and restarting the display module; and updating the display module according to the jamming information to complete display interface recovery. According to the vehicle-mounted display system, the stability and reliability of the system are improved, user troubles caused by display interface jamming are reduced, the efficiency of problem diagnosis and solving is improved, and therefore the performance of the whole vehicle-mounted display system and the user satisfaction degree are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of automotive electronic technology, and in particular to a method, device and storage medium for detecting and recovering a stuck vehicle display interface. Background Art

[0002] In modern in-vehicle display systems, the stability of the display interface directly affects user experience and driving safety. However, due to complex software and hardware interactions and multi-tasking requirements, the car display interface occasionally freezes, which is manifested as unresponsive interface operations or stagnation on a certain interface for a long time, causing inconvenience and trouble to users.

[0003] Current solutions mainly rely on monitoring the running status of key modules such as the display layer synthesizer (SurfaceFlinger, SF), and try to recover the stuck interface through timed detection and resource management. For example, some technical solutions may periodically detect the response of interface elements or use the monitoring of mutually exclusive resources to determine whether the interface is stuck and take corresponding recovery strategies.

[0004] However, existing methods for detecting and recovering stuck devices often face many challenges and problems. Technically, detection methods based on parameter changes or screenshot comparisons may not be accurate enough to capture small changes in the interface, resulting in misjudgment or detection delays. In terms of recovery strategies, due to complex business logic and cross-process calls, the recovery process may lack efficiency or stability, and cannot effectively solve the problem of reduced user experience in real time. Therefore, how to detect and recover stuck vehicle display interfaces has become an urgent problem to be solved.

[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0006] The purpose of this application is to provide a method, device and storage medium for detecting and recovering a stuck vehicle display interface, aiming to solve the technical problem of how to detect and recover a stuck vehicle display interface.

[0007] To achieve the above purpose, the present application proposes a method for detecting and recovering a stuck vehicle display interface, the method comprising:

[0008] Define a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class;

[0009] Complete the display module jam detection according to the pointer template class and the jam detection object class, and trigger the timing callback;

[0010] Collecting stuck information in the timed callback and restarting the display module;

[0011] The display module is updated according to the stuck information to complete the display interface recovery.

[0012] In one embodiment, the step of completing the display module jam detection according to the pointer template class and the jam detection object class and triggering a timed callback includes:

[0013] Creating a stuck detection object at the message service processing entrance according to the stuck detection object class;

[0014] Acquire the life cycle of the stuck detection object according to the pointer template class;

[0015] When the life cycle is greater than or equal to the preset time, it is considered that the display module is stuck and a timed callback is triggered.

[0016] In one embodiment, when the life cycle is greater than or equal to a preset time, the display module is considered to be stuck, and before the step of triggering the timed callback, the step further includes:

[0017] Obtain system load, response time, and resource utilization;

[0018] The preset duration is adjusted according to the system load, the response time and the resource utilization.

[0019] In one embodiment, the stuck information includes display module information, stack information and register information, and the step of collecting the stuck information in the timed callback and restarting the display module includes:

[0020] Collecting the display module information, the stack information and the register information in the timing callback;

[0021] The display module information, the stack information and the register information are saved through a memory core dump, and the display module is restarted.

[0022] In one embodiment, the step of saving the display module information, the stack information, and the register information through a memory core dump comprises:

[0023] Define a memory core dump object structure according to a display module information structure, a stack information structure, and a register information structure;

[0024] Creating a memory core dump object according to the memory core dump object structure;

[0025] Initialize the memory core dump object according to the current system state;

[0026] The display module information, the stack information and the register information are stored in a persistent storage medium through the memory core dump object.

[0027] In one embodiment, the step of updating the display module according to the stuck information to complete the display interface recovery includes:

[0028] Sending the display module information, the stack information and the register information to a remote server, so that the remote server pushes an update package according to the display module information, the stack information and the register information;

[0029] The display module is updated using the update package to complete the display interface recovery.

[0030] In one embodiment, the step of creating a stuck detection object at a message service processing entrance according to the stuck detection object class includes:

[0031] Locate business logic modules according to system structure;

[0032] Locate the business logic controller class according to the business logic module;

[0033] Find the message processing function in the business logic controller class;

[0034] A stuck detection object is created at the entry of the message processing function according to the stuck detection object class.

[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a device for detecting and recovering a stuck vehicle display interface, the device comprising:

[0036] A definition module, used to define a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class;

[0037] A stuck detection module, used to complete the stuck detection of the display module according to the pointer template class and the stuck detection object class, and trigger a timed callback;

[0038] A restart module, used to collect stuck information in the timed callback and restart the display module;

[0039] An updating module is used to update the display module according to the stuck information to complete the display interface recovery.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a device for detecting and recovering a vehicle display interface freeze, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the method for detecting and recovering a vehicle display interface freeze as described above.

[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the detection and recovery method for the stuck vehicle display interface as described above are implemented.

[0042] One or more technical solutions proposed in this application have at least the following technical effects:

[0043] By defining a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class; completing the display module deadlock detection according to the pointer template class and the deadlock detection object class, and triggering a timed callback; collecting deadlock information in the timed callback, and restarting the display module; updating the display module according to the deadlock information, and completing the display interface recovery. First, by defining a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class, the system can effectively manage memory and resources to ensure the life cycle of objects and the correctness of reference counting. The pointer template class can flexibly manage various types of object pointers, while the reference counting base class and its derived classes can help track the reference of objects to avoid memory leaks and dangling pointer problems. Secondly, according to the defined pointer template class and the deadlock detection object class, the system implements the deadlock detection mechanism of the display module. This includes regularly detecting the response of the display module, such as whether the interface has not responded for a long time or the operation is stuck, thereby triggering the corresponding deadlock detection operation. In the timed callback, the system collects detailed information about the display module deadlock, including the status of the current interface, possible stack information, and the status of related registers. This information is crucial for subsequent problem analysis and recovery operations, and can help accurately locate the root cause of the problem and speed up troubleshooting. Finally, based on the collected stuck information, the system sends the data to the remote server, which analyzes and generates appropriate update packages. These update packages may contain fixes or optimized instruction sets for display module problems to update the display module and restore its normal operating state, thereby effectively improving user experience and driving safety. In summary, this embodiment improves the stability and reliability of the system, reduces user distress caused by display interface stuck, and speeds up the efficiency of problem diagnosis and resolution, thereby improving the performance and user satisfaction of the overall vehicle display system. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A flowchart diagram of the first embodiment of the method for detecting and recovering a stuck vehicle display interface of the present application;

[0047] Figure 2 A flow chart of the second embodiment of the method for detecting and recovering a stuck vehicle display interface of the present application;

[0048] Figure 3 A schematic diagram of a simplified flow chart of a method for detecting and recovering a vehicle computer display interface freeze provided in the second embodiment of the present application;

[0049] Figure 4 This is a schematic diagram of the module structure of a device for detecting and recovering a stuck vehicle display interface according to an embodiment of the present application;

[0050] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the method for detecting and recovering a stuck vehicle computer display interface in an embodiment of the present application.

[0051] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0052] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0053] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0054] In modern in-vehicle display systems, the stability of the display interface is directly related to user experience and driving safety. However, due to the complex interaction between software and hardware and the need for multi-tasking, the car display interface occasionally freezes, causing unresponsive operations or long-term stagnation, which brings inconvenience to users. Current solutions mainly rely on monitoring the operating status of key modules such as the display layer compositor (SurfaceFlinger, SF), and try to restore the stuck interface through timed detection and resource management. However, existing methods face technical challenges in terms of insufficient detection accuracy and complex recovery strategies, making it difficult to improve user experience instantly and effectively.

[0055] The main solution of the embodiment of the present application is: by defining the pointer template class, the reference counting base class and the derived class of the stuck detection object class, the memory and resources are effectively managed to ensure the correctness of the object life cycle and the reference count. The pointer template class flexibly manages various types of object pointers, and the reference counting base class and its derived classes track the object references to avoid memory leaks and dangling pointers. The system implements the stuck detection mechanism of the display module based on the defined class, regularly detects the response of the display module and triggers the corresponding detection operation. In the timed callback, the system collects detailed stuck information of the display module, including the interface status, possible stack information and related register status, which is helpful for problem analysis and recovery operations, and improves troubleshooting efficiency. Finally, the system sends the collected stuck information to the remote server, and the server analyzes and generates an update package, which may contain a display module problem repair program or an optimized instruction set to update the display module and restore normal operation, thereby improving user experience and driving safety.

[0056] It should be noted that the execution subject of the embodiment of the present application may be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a vehicle system, a display system, etc. that can realize the above functions. The following takes the vehicle system as an example to illustrate this embodiment and the following embodiments.

[0057] Based on this, the embodiment of the present application provides a method for detecting and recovering a stuck vehicle display interface. Figure 1 , Figure 1 This is a flow chart of the first embodiment of the method for detecting and recovering a stuck vehicle display interface of the present application.

[0058] In this embodiment, the method for detecting and recovering from a stuck vehicle display interface includes steps S10 to S40:

[0059] Step S10, defining a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class;

[0060] It should be noted that the pointer template class refers to a smart pointer template class, such as the sp class, which is used to manage dynamically allocated objects and implement a reference counting mechanism to ensure that memory is automatically released when no longer needed. In this solution, sp refers to a smart pointer template class used to manage a stuck detection object.

[0061] Smart pointer template class sp

[0062]

[0063]

[0064] A reference counting base class refers to a base class, such as the RefBase class, which contains methods to increase and decrease the reference count of an object, used to track the number of times the object has been referenced. In this solution, RefBase refers to the base class used to implement the object reference counting mechanism.

[0065]

[0066]

[0067] The stuck detection object class refers to a specific class inherited from the reference counting base class, such as the MyTestRef class, which implements the specific business logic of stuck detection. In this solution, MyTestRef refers to the object class used to monitor and handle stuck interfaces.

[0068]

[0069]

[0070]

[0071] It can be understood that in this embodiment, firstly, a pointer template class sp is defined, which is a smart pointer template used to manage dynamically allocated objects and implement a reference counting mechanism. Secondly, a reference counting base class RefBase is introduced, which includes methods for increasing and decreasing object reference counts to ensure the validity of tracking object references. Finally, a deadlock detection object class MyTestRef inherited from RefBase is defined, which undertakes the specific deadlock detection task, initializes the deadlock detection and handles the management of the object life cycle by implementing the onFirstRef() and onLastStrongRef() methods to ensure system stability and reliability.

[0072] Step S20, completing the display module stuck detection according to the pointer template class and the stuck detection object class, and triggering a timed callback;

[0073] It should be noted that the "display module" refers to the core module responsible for display processing in the vehicle display system, such as SurfaceFlinger in the Android system, which is responsible for managing and rendering all graphics on the screen. The timed callback refers to the timer callback function set in the stuck detection object class MyTestRef, which is used to perform a specific operation after a predetermined time interval. Specifically, in this embodiment, the timed callback function is used to monitor the operating status of the display module. When the display module is detected to be stuck, the timed callback function will be triggered to collect information and execute related recovery strategies, such as restarting the display module or the system to restore the normal operating state.

[0074] It is understandable that first, an instance of MyTestRef is created through the sp smart pointer management, which ensures that memory resources are automatically released when no longer needed. Secondly, the logic of the deadlock detection is implemented in the MyTestRef class, including the operation of initializing the deadlock detection and the setting of the timer callback function. The timer callback function is used to regularly detect the response status of the display module. When the display module is detected to be dead, the timer callback function will be triggered and the predefined recovery strategy will be executed, such as collecting key information, restarting the display module or the system, to ensure user experience and system stability.

[0075] Step S30, collecting stuck information in the timed callback and restarting the display module;

[0076] It should be noted that the stuck information refers to the key information collected in the timing callback function, which usually includes the stack information of the display module (such as SurfaceFlinger), current status information, possible error logs, etc. This information helps to analyze why the display module is stuck.

[0077] It is understandable that, first of all, the timer callback function is set to monitor the operating status of the display module (such as SurfaceFlinger) in the vehicle display system. When the display module is detected to be stuck, the timer callback function will be triggered, and key stuck information will be collected at this time, such as the stack trace, current status and possible error log of the display module. Then, based on the collected information, the system will execute a recovery strategy, which may include restarting the display module or the entire system to ensure that the display interface resumes normal operation and improves the user experience and system stability.

[0078] As an example, the freeze information includes display module information, stack information and register information. The steps of collecting the freeze information in the timed callback and restarting the display module include: collecting the display module information, the stack information and the register information in the timed callback; saving the display module information, the stack information and the register information through a memory core dump, and restarting the display module.

[0079] Display module information refers to the current running status, configuration information and other key parameters of the display module (such as SurfaceFlinger). Stack information refers to the function call stack information of the display module when it is stuck, including which functions are being executed and the call relationship. Register information refers to the register status of the display module when it is running, including the value and status of each register. Memory core dump refers to saving the memory status, stack information and register information of the current display module as a file or data stream for subsequent offline analysis and diagnosis. First, in the timed callback function, the current display module information is collected in detail: including the running status and configuration parameters of the display module, the function call chain in the stack information, and the current status of each register. The collection of this information is achieved through the pre-defined methods and data structures in the internal monitoring object class to ensure the accuracy and integrity of the data. Then, the collected information is stored in the memory core dump for subsequent offline analysis and fault diagnosis. Finally, based on the analysis results and the collected data, the display module is restarted. This step aims to effectively restore the normal operation of the display module, thereby solving the stuck problem and improving the user experience and stability of the vehicle system.

[0080] As an example, the steps of saving the display module information, the stack information and the register information through a memory core dump include: defining a memory core dump object structure according to the display module information structure, the stack information structure and the register information structure; creating a memory core dump object according to the memory core dump object structure; initializing the memory core dump object according to the current system state; and storing the display module information, the stack information and the register information in a persistent storage medium through the memory core dump object.

[0081] The display module information structure refers to a data structure that defines and describes the current status, configuration, and other related information of the display module, usually including the running status, parameter settings, and connection status of the display module. The stack information structure refers to a data structure that describes the function call chain during program execution, which is used to record the currently executed code path and function call sequence. The register information structure refers to a data structure that describes the current status of registers in the CPU or other processors, including register values, flags, status, and other information. The memory core dump object structure refers to a data structure used to store the above three types of information (display module information, stack information, and register information). It may include various fields and methods for operating and managing the storage and access of this information. The memory core dump object refers to the actual object instance created based on the memory core dump object structure, which is used to store key information in a persistent storage medium when an exception occurs in the system or the state needs to be saved. The current system state refers to the overall running state of the system when the memory core dump operation is performed, including running processes, resource usage, etc. Persistent storage media refers to media that can store data for a long time, such as hard disks, flash memory, etc., which are used to store information in memory core dump objects for subsequent offline analysis and fault diagnosis. In the process of saving display module information, stack information, and register information, the detailed layout and fields of each information structure need to be defined first to ensure that the memory core dump object can accurately carry this data. Then, based on these definitions, a memory core dump object is created, which is designed to hold all the necessary information and ensure the consistency and validity of the structure. Next, the memory core dump object is initialized according to the current system state, including ensuring that the data fields in the object are ready to receive the latest information. Finally, using the initialized memory core dump object, the display module information, stack information, and register information are stored in a persistent storage medium, such as a hard disk or flash memory, to ensure that important debugging and analysis data can be retained and retrieved even if the system is restarted or powered off.

[0082] Step S40, updating the display module according to the stuck information to complete the display interface recovery.

[0083] It should be noted that display interface recovery refers to restarting or updating the display module by utilizing the collected stuck information to restore its normal operating state so that the user can continue to use the interface and functions of the vehicle display system normally.

[0084] It can be understood that the status of the display module and the possible causes of the freeze are analyzed based on the collected freeze information; an appropriate recovery strategy is selected based on the analysis results, which may involve restarting the display module, releasing or reallocating resources; the selected strategy is implemented to update or restart the display module to ensure that it is restored to normal operating status, and the recovery process is monitored to ensure the effectiveness and stability of the recovery.

[0085] As an example, the display module is updated according to the stuck information, and the step of completing the display interface recovery includes: sending the display module information, the stack information and the register information to a remote server, so that the remote server pushes an update package according to the display module information, the stack information and the register information; using the update package to update the display module to complete the display interface recovery.

[0086] A remote server refers to a remote computer or server located in a network, which is used to receive and process display module information, stack information and register information from the vehicle system, and generate an update package based on this information. An update package refers to a software update file generated by a remote server, which contains program code or configuration files customized according to the received display module information, stack information and register information, and is used to repair or update problems or stuck phenomena in the vehicle display system to restore the normal function of the display interface. In the process of completing the display interface recovery, first, the vehicle display system will collect detailed information about the current display module, including the interface status, stack information that may cause stuck, and the status of related registers. This information will then be transmitted to a remote server, which analyzes the current display module problem based on the received data and generates a specific update package. This update package is designed to solve the stuck problem, which may include a fix or optimized instruction set to ensure that the display interface can operate normally after the system is updated. After the update is completed, the vehicle display system will restart the display module to apply the update and restore the user's normal operating experience.

[0087] This embodiment provides a method for detecting and recovering a stuck display interface of a vehicle computer, by defining a pointer template class, a reference counting base class, and a stuck detection object class inherited from the reference counting base class; completing the stuck detection of the display module according to the pointer template class and the stuck detection object class, and triggering a timed callback; collecting stuck information in the timed callback, and restarting the display module; updating the display module according to the stuck information, and completing the display interface recovery. First, by defining a pointer template class, a reference counting base class, and a stuck detection object class inherited from the reference counting base class, the system can effectively manage memory and resources, and ensure the correctness of the object life cycle and reference count. The pointer template class can flexibly manage various types of object pointers, while the reference counting base class and its derived classes can help track the reference of the object, avoiding memory leaks and dangling pointer problems. Secondly, according to the defined pointer template class and the stuck detection object class, the system implements the stuck detection mechanism of the display module. This includes regularly detecting the response of the display module, such as whether the interface has not responded for a long time or the operation is stuck, thereby triggering the corresponding stuck detection operation. In the timed callback, the system collects detailed information about the display module being stuck, including the status of the current interface, possible stack information, and the status of related registers. This information is crucial for subsequent problem analysis and recovery operations, and can help accurately locate the root cause of the problem and speed up troubleshooting. Finally, based on the collected stuck information, the system sends the data to the remote server, which analyzes and generates appropriate update packages. These update packages may contain fixes or optimized instruction sets for display module problems to update the display module and restore its normal operating state, thereby effectively improving user experience and driving safety. In summary, this embodiment improves the stability and reliability of the system, reduces user distress caused by the stuck display interface, and accelerates the efficiency of problem diagnosis and resolution, thereby improving the performance and user satisfaction of the overall vehicle display system.

[0088] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , Figure 2 This is a flow chart of a second embodiment of the method for detecting and recovering a vehicle display interface stuck in the present application. Step S20 of the method for detecting and recovering a vehicle display interface stuck includes steps S21 to S23:

[0089] Step S21, creating a stuck detection object at the message service processing entrance according to the stuck detection object class;

[0090] It should be noted that the message service processing entry refers to the starting position of the main function or module that processes messages or events in the system, which is responsible for receiving and processing messages from the outside or inside. The stuck detection object refers to a specific instance created based on the stuck detection object class, which is used to monitor the system operation status and perform stuck detection related operations.

[0091] It is understandable that at the core entry of system message or event processing, a stuck detection object is created by instantiating a stuck detection object class. This step ensures that the system can immediately start the stuck detection mechanism when a message arrives, monitor and record the system operation status, so that when an abnormal situation (such as interface stuck) is detected, it can respond in time and take corresponding fault handling measures, thereby ensuring system stability and user experience.

[0092] As an example, the steps of creating a stuck detection object at the message service processing entrance according to the stuck detection object class include: locating the business logic module according to the system structure; locating the business logic controller class according to the business logic module; searching for the message processing function in the business logic controller class; and creating a stuck detection object at the entrance of the message processing function according to the stuck detection object class.

[0093] System structure refers to the organization and architecture of the entire software system, including the relationship and interaction between each module. Business logic module The module in the system that handles specific business logic is responsible for executing the core functions of the system. The business logic controller class is part of the business logic module and is usually the class responsible for coordinating and controlling the business logic process. Message processing function The function or method defined in the business logic controller class is used to process the messages or events received by the system. The system will first analyze in detail according to its overall structure to determine the location and function of each module involved in the specific business logic. Subsequently, the system will further refine the located business logic module to find and confirm the appropriate business logic controller class. In these controller classes, the system will carefully search to find the function or method that is responsible for processing the message. Finally, according to the definition of the stuck detection object class, the system will accurately implement the creation and initialization of the stuck detection object at the entrance of the found message processing function. The detailed decomposition of this process ensures that the system can accurately and timely start the stuck detection function to monitor and respond to the changes in the running status of the display module, thereby maintaining the reliability of the system and user experience.

[0094] Step S22, obtaining the life cycle of the stuck detection object according to the pointer template class;

[0095] It should be noted that the life cycle refers to the entire usage time of the deadlock detection object from its creation to its destruction.

[0096] It can be understood that the pointer to the stuck detection object is defined and managed through the pointer template class to ensure the correctness of the reference count and the management of the object life cycle during the use of the object; when the object is created, the pointer template class is used to allocate memory and initialize the object, and the current timestamp is recorded; when the object is referenced or used, the reference count of the object is updated; when the object is no longer needed, the memory of the object is released through the pointer template class, the reference count is reduced, and the current timestamp is obtained again; finally, when the reference count returns to zero, the object is destroyed and the related resources are released to ensure the effective management and safe release of memory and resources. The time difference between the two timestamps is the life cycle.

[0097] Step S23, when the life cycle is greater than or equal to the preset time length, it is regarded as the display module being stuck, and a timed callback is triggered.

[0098] It should be noted that the preset duration refers to a set threshold or time interval. When the life cycle of the stuck detection object reaches or exceeds the preset duration, the system will use the time length as a basis for judging whether the display module is stuck, thereby triggering a timed callback operation. The preset duration can be set according to the needs and performance characteristics of the system, and is usually determined according to the actual scenario and performance test results. In this embodiment, it is 10 seconds.

[0099] It is understandable that the system will check whether the running time of the stuck detection object exceeds the preset threshold. If it exceeds, it will be determined that there is a problem with the display module, and a timed callback will be triggered to collect detailed stuck information, including the current interface status, stack information and register status, for subsequent analysis and recovery operations.

[0100] As an example, when the life cycle is greater than or equal to the preset duration, the display module is considered to be stuck. Before triggering the timed callback step, it also includes: obtaining system load, response time and resource utilization; adjusting the preset duration according to the system load, the response time and the resource utilization.

[0101] System load refers to the amount of tasks and load currently processed by the system, which can be measured by monitoring indicators such as CPU usage and memory usage. Response time refers to the time interval from the system receiving a request to completing the response, which is used to evaluate the system's ability to respond quickly to external requests. Resource utilization refers to the utilization of various resources in the system (such as CPU, memory, and network bandwidth), which is used to evaluate the system's resource consumption and performance bottlenecks. Before performing display module jam detection, the system will obtain the current system load, that is, the workload and number of tasks being processed by the system; response time, that is, the system's reaction speed to input or request; and resource utilization, including the use of resources such as CPU, memory, and network. These indicators provide important information about the overall operating status and performance of the system. Based on this data, the system will dynamically adjust the preset jam detection duration to ensure that the duration is set reasonably and that possible jams can be detected in a timely manner, thereby effectively ensuring the stability and responsiveness of the display module.

[0102] In this embodiment, a stuck detection object is created at the entrance of the message service processing according to the stuck detection object class; the life cycle of the stuck detection object is obtained according to the pointer template class; when the life cycle is greater than or equal to the preset duration, it is regarded as the display module stuck, and the timing callback is triggered. In this embodiment, by first creating a stuck detection object at the entrance of the message service processing, the system can monitor and capture the stuck situation that may occur in the display module during the message processing process in real time, ensuring that the problem is discovered in time. Secondly, the life cycle of the stuck detection object is obtained using the pointer template class, and the system can accurately calculate and manage the entire usage time of the object from creation to destruction, which is crucial for the accuracy and effectiveness of the stuck detection. Finally, when it is detected that the life cycle of the stuck object exceeds or reaches the preset duration, the system regards it as the display module may be stuck, and triggers the timing callback operation. This mechanism can help the system take timely measures after the stuck occurs, such as collecting relevant information or starting the recovery process, thereby improving the stability and reliability of the system and avoiding affecting the normal user experience.

[0103] For example, in order to help understand the implementation process of the vehicle display interface stuck detection and recovery method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 3 , Figure 3 A brief flow chart of a method for detecting and recovering a stuck vehicle display interface is provided, specifically:

[0104] In the car display system, the main thread is responsible for continuously taking out and executing messages from the message queue. At the starting point of message processing, the system creates a stuck detection object named MyTestRef, which is managed by the smart pointer sp for life cycle management to ensure the correct release of memory and resources. The system monitors the life cycle of the MyTestRef object. If the cycle exceeds the preset time threshold, it is considered that the display module may be stuck. At this time, the system will trigger a callback function named timerCallback, which is responsible for collecting the stuck information of the display module, including but not limited to key data such as stack information and register status, and try to restart the display module to temporarily restore the display function. The collected stuck information is then sent to the remote server. After receiving this information, the server will analyze the cause and develop a corresponding update package. This update package is designed to solve the specific problem that causes the stuck, which may be achieved by fixing program errors or optimizing system performance. Once the update package is developed and sent back to the car system, the system will use this update package to update the display module and complete the complete recovery of the display interface. This process not only improves the stability and reliability of the system, but also reduces the troubles users suffer from display interface freezes. It also speeds up the efficiency of problem diagnosis and resolution, and improves the overall vehicle display system performance and user satisfaction.

[0105] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the detection and recovery method of the vehicle display interface freeze of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0106] This application also provides a detection and recovery device for a vehicle display interface stuck, please refer to Figure 4 The vehicle computer display interface stuck detection and recovery device comprises:

[0107] A definition module 10 is used to define a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class;

[0108] A stuck detection module 20, used to complete the stuck detection of the display module according to the pointer template class and the stuck detection object class, and trigger a timed callback;

[0109] A restart module 30, used to collect stuck information in the timed callback and restart the display module;

[0110] The updating module 40 is used to update the display module according to the stuck information to complete the display interface recovery.

[0111] The device for detecting and recovering a stuck vehicle display interface provided by the present application adopts the method for detecting and recovering a stuck vehicle display interface in the above-mentioned embodiment, and can solve the technical problem of how to detect and recover a stuck vehicle display interface. Compared with the prior art, the beneficial effects of the device for detecting and recovering a stuck vehicle display interface provided by the present application are the same as the beneficial effects of the method for detecting and recovering a stuck vehicle display interface provided by the above-mentioned embodiment, and the other technical features of the device for detecting and recovering a stuck vehicle display interface are the same as the features disclosed in the above-mentioned embodiment method, and are not described in detail here.

[0112] The present application provides a device for detecting and recovering a vehicle display interface freeze. The device for detecting and recovering a vehicle display interface freeze includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method for detecting and recovering a vehicle display interface freeze in the above-mentioned embodiment one.

[0113] Reference below Figure 5 , which shows a schematic diagram of the structure of a vehicle display interface stuck detection and recovery device suitable for implementing the embodiment of the present application. The vehicle display interface stuck detection and recovery device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The vehicle display interface stuck detection and recovery device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0114] like Figure 5As shown, the vehicle display interface stuck detection and recovery device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle display interface stuck detection and recovery device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. The input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the vehicle display interface stuck detection and recovery device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a vehicle display interface stuck detection and recovery device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have alternatively.

[0115] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0116] The vehicle display interface stuck detection and recovery device provided by the present application adopts the vehicle display interface stuck detection and recovery method in the above embodiment, which can solve the technical problem of how to detect and recover the vehicle display interface stuck. Compared with the prior art, the beneficial effects of the vehicle display interface stuck detection and recovery device provided by the present application are the same as the beneficial effects of the vehicle display interface stuck detection and recovery method provided by the above embodiment, and other technical features in the vehicle display interface stuck detection and recovery device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0117] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0118] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0119] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the method for detecting and recovering a vehicle display interface freeze in the above-mentioned embodiment.

[0120] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0121] The computer-readable storage medium may be included in the vehicle display interface stuck detection and recovery device; or may exist independently without being assembled into the vehicle display interface stuck detection and recovery device.

[0122] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the detection and recovery device for the vehicle display interface being stuck, the detection and recovery device for the vehicle display interface being stuck: defines a pointer template class, a reference count base class and a stuck detection object class inherited from the reference count base class; completes display module stuck detection according to the pointer template class and the stuck detection object class, and triggers a timed callback; collects stuck information in the timed callback, and restarts the display module; updates the display module according to the stuck information to complete display interface recovery.

[0123] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0124] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0125] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0126] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle display interface stuck detection and recovery method, and can solve the technical problem of how to detect and recover the vehicle display interface stuck. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle display interface stuck detection and recovery method provided by the above-mentioned embodiment, and will not be repeated here.

[0127] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the above-mentioned method for detecting and recovering a stuck vehicle display interface.

[0128] The computer program product provided by the present application can solve the technical problem of how to detect and recover the stuck display interface of the vehicle computer. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the detection and recovery method of the stuck display interface of the vehicle computer provided by the above embodiment, which will not be repeated here.

[0129] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A method for detecting and recovering a stuck vehicle display interface, characterized in that: The method comprises: Define a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class; Complete the display module jam detection according to the pointer template class and the jam detection object class, and trigger the timing callback; Collecting stuck information in the timed callback and restarting the display module; The display module is updated according to the stuck information to complete the display interface recovery.

2. The method according to claim 1, characterized in that The step of completing the display module stuck detection according to the pointer template class and the stuck detection object class and triggering the timing callback comprises: Creating a stuck detection object at the message service processing entrance according to the stuck detection object class; Acquire the life cycle of the stuck detection object according to the pointer template class; When the life cycle is greater than or equal to the preset time, it is considered that the display module is stuck and a timed callback is triggered.

3. The method according to claim 2, characterized in that When the life cycle is greater than or equal to the preset time, the display module is regarded as being stuck, and before the step of triggering the timing callback, the method further includes: Obtain system load, response time, and resource utilization; The preset duration is adjusted according to the system load, the response time and the resource utilization.

4. The method according to claim 1, characterized in that The stuck information includes display module information, stack information and register information. The step of collecting the stuck information in the timed callback and restarting the display module includes: Collecting the display module information, the stack information and the register information in the timing callback; The display module information, the stack information and the register information are saved through a memory core dump, and the display module is restarted.

5. The method according to claim 4, characterized in that The step of saving the display module information, the stack information and the register information by memory core dump comprises: Define a memory core dump object structure according to a display module information structure, a stack information structure, and a register information structure; Creating a memory core dump object according to the memory core dump object structure; Initialize the memory core dump object according to the current system state; The display module information, the stack information and the register information are stored in a persistent storage medium through the memory core dump object.

6. The method according to claim 4, characterized in that The step of updating the display module according to the stuck information to complete the display interface recovery includes: Sending the display module information, the stack information and the register information to a remote server, so that the remote server pushes an update package according to the display module information, the stack information and the register information; The display module is updated using the update package to complete the display interface recovery.

7. The method according to claim 2, characterized in that The step of creating a stuck detection object at the message service processing entrance according to the stuck detection object class comprises: Locate business logic modules according to system structure; Locate the business logic controller class according to the business logic module; Find the message processing function in the business logic controller class; A stuck detection object is created at the entry of the message processing function according to the stuck detection object class.

8. A device for detecting and recovering a stuck vehicle display interface, characterized in that: The device comprises: A definition module, used to define a pointer template class, a reference counting base class, and a deadlock detection object class inherited from the reference counting base class; A stuck detection module, used to complete the stuck detection of the display module according to the pointer template class and the stuck detection object class, and trigger a timed callback; A restart module, used to collect stuck information in the timed callback and restart the display module; An updating module is used to update the display module according to the stuck information to complete the display interface recovery.

9. A device for detecting and recovering a stuck vehicle display interface, characterized in that: The device comprises: a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the method for detecting and recovering a stuck vehicle display interface as described in any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the method for detecting and recovering a stuck vehicle display interface as described in any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Interface management method and device, new energy automobile and storage medium

    CN120653352A