Abnormality repairing method and device of car machine control, electronic equipment and storage medium

Abstract

This application relates to the field of vehicle networking technology and discloses a method, device, electronic device, and storage medium for repairing anomalies in a vehicle infotainment system. The method includes: in response to the startup of the vehicle infotainment system, reading and parsing a first infotainment system configuration file; if parsing the first infotainment system configuration file fails, deleting the first infotainment system configuration file and related error logs; in response to the vehicle infotainment system calling a preset instruction to trigger an anomaly repair task, traversing all applications in the system application directory; verifying the signature information of each application to obtain the verification result; generating a second infotainment system configuration file based on all verification results, to complete the anomaly repair task of the vehicle infotainment system at least based on the second infotainment system configuration file. This application helps to improve the occasional black screen problem of existing infotainment system screens and instrument panel screens, improves the user experience, and ensures user safety when using the vehicle.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a method, device, electronic device, and storage medium for repairing anomalies in a vehicle's central control system. Background Technology

[0002] Currently, the automotive industry is developing towards connectivity, automation, sharing, and electrification, with the core of these "four new trends" all pointing towards intelligentization. Intelligentization revolutionized the mobile phone industry 15 years ago, and this revolution is now being repeated in the automotive industry, making the automotive market one of the most dynamic sectors globally. The intelligent cockpit is a crucial manifestation of automotive intelligence, significantly enhancing the intelligent driving experience and gradually becoming a key factor influencing consumers' car-buying decisions. As consumers increasingly value intelligent cockpits, their penetration rate in the automotive market is accelerating, and they are expected to become a standard feature in intelligent vehicles. Data shows that the global penetration rate of new cars equipped with intelligent cockpit technology has increased significantly; the penetration rate is even higher in the Chinese market. The continuous upgrading and iteration of intelligent cockpits will not only accelerate the process of automotive intelligence but also drive the sustained development of the in-vehicle display market.

[0003] With the accelerated development of intelligent and electric vehicles, in-vehicle display panels are trending towards higher resolution, larger size, and greater quantity, while also evolving towards diversified designs, varied technologies, and integrated functions. As a core human-machine interface device, the in-vehicle display accurately identifies the touch point, direction of movement, and speed when a user touches the screen, transmitting signals to the vehicle's infotainment system to achieve efficient interaction between the user and the system. Therefore, in-vehicle displays must possess smooth touch response and timely feedback to ensure safer operation for users while driving.

[0004] However, with the advancement of automotive intelligence and electrification, the number of screens in vehicles is increasing daily, encompassing instrument panel screens, central control screens, passenger-side screens, armrest screens, and panoramic sunroof screens. While these screens provide users with an exceptional experience, they also introduce some instability factors, with occasional screen blackouts occurring frequently—especially on the central control screen and instrument panel. This not only severely impacts user experience but also threatens driving safety. In most cases, blackout issues are intermittent malfunctions, difficult to reproduce, making it challenging to pinpoint the cause: on the one hand, effective log information is unavailable; on the other hand, existing reproduction methods are relatively limited, making it difficult to reproduce the problem in the original scenario. Summary of the Invention

[0005] The purpose of this invention is to provide a method, device, electronic device, and storage medium for repairing abnormalities in vehicle infotainment systems, so as to at least improve the occasional black screen problem of existing central control screens and instrument panel screens, thereby improving the user experience and ensuring user safety.

[0006] To address the aforementioned technical problems, in a first aspect, the present invention provides a method for repairing anomalies in a vehicle infotainment system, comprising at least:

[0007] In response to the startup of the vehicle's central control system, it reads and parses the first central control configuration file;

[0008] If the parsing of the first central control configuration file fails, delete the first central control configuration file and related error logs;

[0009] In response to the vehicle's infotainment system calling a preset command to trigger an abnormal repair task, the system traverses all applications in the system's application directory.

[0010] Verify the signature information of each application to obtain the verification result;

[0011] A second central control configuration file is generated based on all verification results, so as to complete the anomaly repair task of the vehicle central control system at least based on the second central control configuration file.

[0012] Optionally, if the parsing of the first central control configuration file fails, the first central control configuration file and related error logs are deleted, specifically including:

[0013] If an array out-of-bounds error or a format error occurs when parsing the first central control configuration file, then the parsing of the first central control configuration file is confirmed to have failed.

[0014] The first central control configuration file is deleted using a preset command, and related error logs are also deleted.

[0015] Optionally, the relevant error log includes at least one of the error information from the exception configuration file and the deletion time.

[0016] Optionally, it also includes:

[0017] If the vehicle infotainment system startup animation is black and backlighting occurs when the vehicle infotainment system startup is abnormal, then the abnormality is determined to be a software malfunction.

[0018] Secondly, the present invention also provides an abnormal repair device for a vehicle infotainment system, comprising at least:

[0019] The startup reading module is used to respond to the startup of the vehicle's central control system, read and parse the first central control configuration file;

[0020] The failure deletion module is used to delete the first central control configuration file and related error logs when the parsing of the first central control configuration file fails.

[0021] The application traversal module is used to respond to the vehicle's central control unit's call to a preset command to trigger an abnormal repair task, and to traverse all applications in the system application directory;

[0022] The signature verification module is used to verify the signature information of each application to obtain the verification result;

[0023] A restart module is configured to generate a second central control configuration file based on all verification results, so as to complete the anomaly repair task of the vehicle central control system based at least on the second central control configuration file.

[0024] Optionally, the failure deletion module is specifically used for:

[0025] If an array out-of-bounds error or a format error occurs while parsing the first central control configuration file, the parsing of the first central control configuration file is confirmed to have failed; and the first central control configuration file is deleted using a preset command, and the relevant error logs are deleted.

[0026] Optionally, the relevant error log includes at least one of the error information from the exception configuration file and the deletion time.

[0027] Optionally, it also includes:

[0028] The anomaly detection module is used to determine that the anomaly in the vehicle infotainment system is a software anomaly when the vehicle infotainment system startup animation is black and backlighting occurs.

[0029] Thirdly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps in the abnormal repair method of the vehicle central control system according to any one of the first aspects.

[0030] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in the abnormal repair method for the vehicle infotainment system described in any one of the first aspects.

[0031] The technical solution provided in this embodiment of the invention firstly reads and parses a first central control configuration file in response to the startup of the vehicle central control system; secondly, if the parsing of the first central control configuration file fails, the first central control configuration file and related error logs are deleted; thirdly, in response to the vehicle central control system calling a preset instruction to trigger an abnormal repair task, all applications in the system application directory are traversed; then, the signature information of each application is verified to obtain the verification result; finally, a second central control configuration file is generated based on all verification results, so as to complete the abnormal repair task of the vehicle central control system at least based on the second central control configuration file.

[0032] Therefore, this embodiment of the invention introduces an anomaly handling mechanism during the vehicle infotainment system startup process. This mechanism automatically analyzes the specific reasons for the failure to parse the first infotainment configuration file and automatically triggers an anomaly repair process, thereby deleting the first infotainment configuration file and related error logs to ensure subsequent fault handling. Furthermore, after the anomaly repair task is triggered, this embodiment of the invention can generate a second infotainment configuration file based on the verification results, completing the startup of the vehicle infotainment system. This effectively improves the occasional black screen problem of existing infotainment and instrument panel displays, enhancing the user experience and ensuring user safety. Attached Figure Description

[0033] Figure 1 This is a flowchart of a method for repairing anomalies in a vehicle infotainment system provided in an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram of the structure of a vehicle infotainment system malfunction repair device provided in an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention;

[0036] Figure 4 This is a power management flowchart for a vehicle infotainment system during startup, provided by an embodiment of the present invention. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0039] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0040] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0041] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0042] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0043] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

[0044] As mentioned in the background technology, blackout screens on the central control screen and instrument panel not only severely affect the user experience but also threaten driving safety. Figure 4 This is a power management flowchart for a vehicle infotainment system during startup, provided by an embodiment of the present invention. Figure 4 As shown, the startup process of the vehicle infotainment system designed by the applicant can be as follows:

[0045] First, after the vehicle is powered on, when the vehicle's infotainment system detects the IG-ON signal, it generates a power supply voltage to power the microcontroller unit (MCU). Then, when the MCU detects the IG-ON signal, it outputs an enable signal to power the system power management chip. Next, when the output enable signal turns on the power management chip, it powers components such as the system-on-chip (SoC), eMMC (e-data storage chip), and DDR (DDR memory). Finally, once the SoC is powered on normally, it loads the bootloader, initializes the memory IC, and loads the program from the eMMC onto the DDR for execution. Finally, the vehicle's infotainment system starts the hypervisor (virtual machine) and the Linux kernel, completing the system startup process.

[0046] Subsequently, the vehicle infotainment screen startup process is initiated. First, after the MCU detects the power-on signal, it outputs an enable signal to turn on the system-side power supply, providing power to the SOC. Next, after the SOC detects the power supply, it begins startup. Then, the Bootloader is loaded and run, initializing the hardware devices and establishing a memory space mapping. Loading the Bootloader mainly involves two stages:

[0047] Phase 1: Initialize the hardware code and disable all interrupts: The Bootloader execution process does not need to respond to any interrupts; providing interrupt services is usually the responsibility of the operating system driver. Set the CPU speed and clock frequency, and initialize RAM: Correctly configure the system memory controller's function registers and disable the CPU's internal instruction / data cache. After hardware initialization, reserve readable and writable RAM space for loading Phase 2 and test the read / write RAM space addresses. Set the stack pointer and modify the PC register to point to the appropriate address to achieve a jump to the Bootloader's Phase 2.

[0048] Phase 2: Detect the memory mapping within the vehicle's infotainment system, load the kernel hardware and root file system, set and invoke the kernel's boot parameters, initialize the DDR, and load the program into the DDR. After successful DDR loading, start the Hypervisor, start the Linux Kernel, and mount the system files. After successful SOC boot, start the application, read and write system logs, load the screen drivers for the central control unit and instrument cluster, light up the screen, and play the welcome animation.

[0049] However, at certain times after the vehicle's infotainment system is turned on, the screens of the central control unit and the instrument panel occasionally go black. When this happens, the screen cannot respond to the user's commands. After careful investigation, the applicant discovered that the cause of the technical problem is a system malfunction caused by software issues during the vehicle's startup process, which results in the black screen.

[0050] To address the aforementioned technical problems, the present invention proposes the following solutions:

[0051] Figure 1 This is a flowchart of a method for repairing anomalies in a vehicle infotainment system provided by an embodiment of the present invention. This embodiment is applicable to at least various scenarios involving the repair of abnormal startup of vehicle infotainment screens. This method for repairing anomalies in a vehicle infotainment system can be, but is not limited to, executed by the vehicle infotainment system anomaly repair device described in this embodiment of the present invention. This execution device can be implemented using software and / or hardware. Figure 1 As shown, the method for repairing the malfunction of the vehicle's central control system includes at least the following steps:

[0052] S1. In response to the startup of the vehicle's central control system, read and parse the first central control configuration file.

[0053] The startup of the vehicle's central control system can be initiated by the user pressing the start button. The first central control system configuration file can be a `packages.xml` file stored in the ` / data / system / ` path, which stores key information such as application permission configurations. It is understood that when the central control system is not being started for the first time, the Android system relies on reading and parsing the first configuration file to obtain the application signature. In one specific implementation, the method further includes:

[0054] (1-1) If the vehicle infotainment system startup animation is black and backlighting occurs when the vehicle infotainment system startup is abnormal, then the abnormality is determined to be a software abnormality.

[0055] Understandably, it's only necessary to check if the primary central control system configuration file failed to parse when the malfunction is attributed to a software error. If the issue is hardware-related, the corresponding hardware needs to be replaced.

[0056] S2. If the parsing of the first central control configuration file fails, delete the first central control configuration file and related error logs.

[0057] The parsing failure can occur when the packages.xml file has an abnormal format (such as missing closing symbols for permission configuration tags, incorrect attribute value formats, etc.). During the loading of the first central control configuration file and application signature verification process, the Android system's PackageManagerService (the parsing function used to parse packages.xml) may encounter an array out-of-bounds error due to its inability to handle the format abnormality, leading to application signature reading failure. This error will cause the Android system server to crash and repeatedly restart, preventing the vehicle's infotainment system from properly booting into the Android system. Specifically, this manifests as a black screen (but with backlight) after the central control screen plays the boot animation, no touch button sounds, and inability to wake up via voice commands, severely impacting the user experience and functionality. In one specific implementation, optionally, the relevant error log includes at least one of the error information from the abnormal configuration file and the deletion time. In another specific implementation, optionally, step S2 specifically includes:

[0058] (2-1) If there is an array out of bounds or a format error when parsing the first central control configuration file, then the parsing of the first central control configuration file is confirmed to have failed.

[0059] Array out-of-bounds errors or format errors can be identified by adding a try-catch exception handling block to the parsing function of the PackageManagerService in the Android system that loads the packages.xml file. When the parsing function detects array out-of-bounds errors (such as the index exceeding the file content length when reading application permission attributes) or XML format errors (such as unclosed tags or missing quotation marks in attribute values), it confirms that the parsing of the first central control configuration file has failed and immediately triggers the exception handling logic.

[0060] (2-2) Delete the first central control configuration file and related error logs by using preset instructions.

[0061] Step (2-2) can be implemented using a shell script (the script is stored in the / system / bin directory and has executable permissions). This script performs the following operations:

[0062] 1. Delete the abnormal packages.xml file using the command "rm / data / system / packages.xml (i.e., the default command)";

[0063] 2. Record deletion operation logs to / system / log / android_system_error.log. The log content includes the deletion time and error information of the abnormal file (such as the index value of the array out of bounds, the line number of the XML format error), which will facilitate subsequent troubleshooting.

[0064] S3. Responding to the vehicle's central control system's abnormal repair task triggered by the vehicle's system calling preset instructions, iterates through all applications in the system's application directory.

[0065] Specifically, the anomaly repair task triggered by the vehicle's infotainment system in response to a preset command can be achieved by the system calling the "am restart" command (the preset command) to restart the core services of the Android system (i.e., the anomaly repair task). Understandably, during the infotainment system restart process, the Android system will detect the absence of ` / data / system / packages.xml` (the primary configuration file) and will recreate it. The system application directories can be ` / system / app` and ` / data / app`.

[0066] S4. Verify the signature information of each application to obtain the verification results.

[0067] The signature information of each application can be verified using Android's native signature verification algorithm, such as RSA encryption verification. The Android system includes a host (core processor, memory, storage unit), a central control screen, touch sensing unit, voice wake-up unit, and AVM (Aspect Rim Visual) control unit. The storage unit is divided into a / data / system partition for storing packages.xml files; the core processor runs the Android system's system server process and PackageManagerService service; the AVM control unit is independent of the Android system's core services, and can still display AVM images even if the Android system crashes.

[0068] S5. Generate a second central control configuration file based on all verification results, and complete the abnormal repair task of the vehicle central control system based at least on the second central control configuration file.

[0069] The second central control configuration file can be a new packages.xml file, containing application permission configurations (such as correctly formatted permission tags). It's understandable that creating the packages.xml file requires re-obtaining the signatures of all applications, which will take approximately 30 seconds longer than normal startup (reading an existing packages.xml file). To avoid users misinterpreting this as a system malfunction, a message stating "The system is optimizing application configuration; expected to recover in 30 seconds" can be displayed on the central control screen when executing the method provided in this embodiment, improving user experience. Furthermore, the method provided in this embodiment can be integrated into the PackageManagerService parsing function and into the Android system's OTA upgrade package. This allows the upgrade package to be pushed to vehicles already in use through the automaker's OTA service platform. After the user confirms the upgrade, the system automatically completes the software update, enabling the exception handling mechanism of this embodiment without requiring a visit to a dealership.

[0070] The technical solution provided in this embodiment firstly reads and parses the first central control configuration file in response to the startup of the vehicle central control system; secondly, if the parsing of the first central control configuration file fails, the first central control configuration file and related error logs are deleted; thirdly, in response to the vehicle central control system calling a preset instruction to trigger the abnormal repair task of the vehicle central control system, all applications in the system application directory are traversed; then, the signature information of each application is verified to obtain the verification result; finally, a second central control configuration file is generated based on all verification results to complete the abnormal repair task of the vehicle central control system based on the second central control configuration file.

[0071] Therefore, this embodiment introduces an exception handling mechanism during the vehicle infotainment system startup process. This mechanism automatically analyzes the specific reasons for the failure to parse the first infotainment configuration file and automatically triggers an exception repair process, thereby deleting the first infotainment configuration file and related error logs to ensure subsequent fault handling. Furthermore, after the exception repair task is triggered, this embodiment can generate a second infotainment configuration file based on the verification results, completing the startup of the vehicle infotainment system. This effectively improves the occasional black screen issue of existing infotainment and instrument panel displays, enhancing the user experience and ensuring vehicle safety.

[0072] Figure 2 This is a schematic diagram of a vehicle infotainment system malfunction repair device provided in an embodiment of the present invention. This embodiment is applicable to at least various vehicle infotainment system screen startup malfunction repair scenarios. This vehicle infotainment system malfunction repair device can be implemented using software and / or hardware methods. Figure 2 As shown, the fault repair device for the vehicle's central control system includes at least the following:

[0073] The startup reading module 110 is used to respond to the startup of the vehicle central control unit, read and parse the first central control configuration file.

[0074] The failure deletion module 120 is used to delete the first central control configuration file and related error logs when the parsing of the first central control configuration file fails.

[0075] The application traversal module 130 is used to respond to the vehicle's central control system's abnormal repair task triggered by the vehicle's system calling preset instructions, and traverse all applications in the system's application directory.

[0076] The signature verification module 140 is used to verify the signature information of each application to obtain the verification result.

[0077] Configure the restart module 150 to generate a second central control configuration file based on all verification results, so as to complete the abnormal repair task of the vehicle central control system based at least on the second central control configuration file.

[0078] Optionally, the failure deletion module 120 is specifically used for:

[0079] When parsing the first central control configuration file, if there is an array out-of-bounds error or a format error, confirm that the parsing of the first central control configuration file has failed; and delete the first central control configuration file and related error logs through preset commands.

[0080] Optionally, the relevant error log should include at least one of the following: error information from the exception configuration file and the deletion time.

[0081] Optionally, it also includes:

[0082] The anomaly detection module 160 is used to determine that the anomaly in the vehicle infotainment system is a software anomaly when the vehicle infotainment system startup is abnormal and the startup animation is black with backlighting.

[0083] The technical solution provided in this embodiment firstly, in response to the startup of the vehicle central control unit, reads and parses the first central control configuration file through the startup reading module. Further, if the parsing of the first central control configuration file fails, the first central control configuration file and related error logs are deleted through the failure deletion module. Further, in response to the vehicle central control unit calling a preset command to trigger an anomaly repair task, all applications in the system application directory are traversed through the application traversal module. Further, the signature verification module verifies the signature information of each application to obtain the verification result. Finally, the configuration restart module generates a second central control configuration file based on all verification results, and completes the anomaly repair task of the vehicle central control unit based on the second central control configuration file.

[0084] Therefore, this embodiment introduces an exception handling mechanism during the vehicle infotainment system startup process. This mechanism automatically analyzes the specific reasons for the failure to parse the first infotainment configuration file and automatically triggers an exception repair process, thereby deleting the first infotainment configuration file and related error logs to ensure subsequent fault handling. Furthermore, after the exception repair task is triggered, this embodiment can generate a second infotainment configuration file based on the verification results, completing the startup of the vehicle infotainment system. This effectively improves the occasional black screen issue of existing infotainment and instrument panel displays, enhancing the user experience and ensuring vehicle safety.

[0085] This embodiment provides an electronic device. Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. See also: Figure 3 The electronic device 1000 includes a processor 1001 and a memory 1002. The memory 1002 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 1001, the steps in any of the above-mentioned vehicle central control system abnormality repair methods are performed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanism (not shown). The memory 1002 stores a computer program that can be executed by the processor. When the electronic device 1000 is running, the processor 1001 executes the computer program to perform the vehicle central control system abnormal repair method in any optional implementation of the above embodiments, so as to achieve at least the following functions: in response to the startup of the vehicle central control system, read and parse the first central control configuration file; if the parsing of the first central control configuration file fails, delete the first central control configuration file and related error logs; in response to the vehicle central control system calling a preset instruction to trigger the abnormal repair task of the vehicle central control system, traverse all applications in the system application directory; verify the signature information of each application to obtain the verification result; generate a second central control configuration file based on all verification results, so as to complete the abnormal repair task of the vehicle central control system at least based on the second central control configuration file.

[0086] This embodiment provides a computer-readable storage medium storing a computer program. When executed by a processor, the program implements the vehicle infotainment system (VMS) anomaly repair method as provided in all embodiments of this application: in response to the startup of the VMS, a first VMS configuration file is read and parsed; if the parsing of the first VMS configuration file fails, the first VMS configuration file and related error logs are deleted; in response to the VMS calling a preset instruction to trigger the VMS anomaly repair task, all applications in the system application directory are traversed; the signature information of each application is verified to obtain the verification result; a second VMS configuration file is generated based on all verification results to complete the VMS anomaly repair task based on the second VMS configuration file.

[0087] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0088] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0089] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0090] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

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

Claims

1. A method for repairing anomalies in a vehicle infotainment system, characterized in that, At least including: In response to the startup of the vehicle's central control system, it reads and parses the first central control configuration file; If the parsing of the first central control configuration file fails, delete the first central control configuration file and related error logs; In response to the vehicle's infotainment system calling a preset command to trigger an abnormal repair task, the system traverses all applications in the system's application directory. Verify the signature information of each application to obtain the verification result; A second central control configuration file is generated based on all verification results, so as to complete the anomaly repair task of the vehicle central control system at least based on the second central control configuration file.

2. The method for repairing anomalies in a vehicle infotainment system according to claim 1, characterized in that, If the parsing of the first central control configuration file fails, the first central control configuration file and related error logs will be deleted, specifically including: If an array out-of-bounds error or a format error occurs when parsing the first central control configuration file, then the parsing of the first central control configuration file is confirmed to have failed. The first central control configuration file is deleted using a preset command, and related error logs are also deleted.

3. The method for repairing anomalies in a vehicle infotainment system according to claim 2, characterized in that, The relevant error logs include at least one of the following: error information from the abnormal configuration file and the deletion time.

4. The method for repairing anomalies in a vehicle infotainment system according to claim 2, characterized in that, Also includes: If the vehicle infotainment system startup animation is black and backlighting occurs when the vehicle infotainment system startup is abnormal, then the abnormality is determined to be a software malfunction.

5. A device for repairing malfunctions in a vehicle infotainment system, characterized in that, At least including: The startup reading module is used to respond to the startup of the vehicle's central control system, read and parse the first central control configuration file; The failure deletion module is used to delete the first central control configuration file and related error logs when the parsing of the first central control configuration file fails. The application traversal module is used to respond to the vehicle's central control unit's call to a preset command to trigger an abnormal repair task, and to traverse all applications in the system application directory; The signature verification module is used to verify the signature information of each application to obtain the verification result; A restart module is configured to generate a second central control configuration file based on all verification results, so as to complete the anomaly repair task of the vehicle central control system based at least on the second central control configuration file.

6. The vehicle infotainment system malfunction repair device according to claim 5, characterized in that, The failure deletion module is specifically used for: If an array out-of-bounds error or a format error occurs while parsing the first central control configuration file, the parsing of the first central control configuration file is confirmed to have failed; and the first central control configuration file is deleted using a preset command, and the relevant error logs are deleted.

7. The vehicle infotainment system malfunction repair device according to claim 6, characterized in that, The relevant error logs include at least one of the following: error information from the abnormal configuration file and the deletion time.

8. The vehicle infotainment system malfunction repair device according to claim 6, characterized in that, Also includes: The anomaly detection module is used to determine that the anomaly in the vehicle infotainment system is a software anomaly when the vehicle infotainment system startup animation is black and backlighting occurs.

9. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the abnormal repair method of the vehicle central control system according to any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps in the abnormal repair method of the vehicle central control system according to any one of claims 1 to 4.

Images