CN112181746A - Fault repairing method, device and equipment for vehicle-mounted operating system - Google Patents

Fault repairing method, device and equipment for vehicle-mounted operating system Download PDF

Info

Publication number
CN112181746A
CN112181746A CN202011048157.3A CN202011048157A CN112181746A CN 112181746 A CN112181746 A CN 112181746A CN 202011048157 A CN202011048157 A CN 202011048157A CN 112181746 A CN112181746 A CN 112181746A
Authority
CN
China
Prior art keywords
fault
target
vehicle
operating system
function module
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011048157.3A
Other languages
Chinese (zh)
Inventor
丘英方
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Liuhuan Information Technology Co ltd
Original Assignee
Guangzhou Liuhuan Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Liuhuan Information Technology Co ltd filed Critical Guangzhou Liuhuan Information Technology Co ltd
Priority to CN202011048157.3A priority Critical patent/CN112181746A/en
Publication of CN112181746A publication Critical patent/CN112181746A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/22Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2205Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/22Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2273Test methods

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to a fault repairing method, a device and equipment of a vehicle-mounted operating system, wherein the fault repairing method of the vehicle-mounted operating system comprises the following steps: when a certain preset fault occurs in a target function module, acquiring a target fault code corresponding to the preset fault; determining a fault type corresponding to the target fault code, and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces; and controlling the target function module to call the target interface and executing the target fault repairing program. Compared with the prior art, the method and the device can quickly repair the faults in the functional module, ensure the normal operation of the vehicle-mounted operating system and further improve the driving safety of the automobile.

Description

Fault repairing method, device and equipment for vehicle-mounted operating system
Technical Field
The embodiment of the application relates to the technical field of electronics, in particular to a method, a device and equipment for repairing a fault of a vehicle-mounted operating system.
Background
The vehicle-mounted operating system has a plurality of functional modules, and in the working process of the vehicle-mounted operating system, the functional modules often have faults, such as process breakdown, process deadlock, hang-up and the like.
At present, fault repair of a vehicle-mounted operating system can only be performed after a product flows into the market and goes back to a fault, and at this time, a fault system cannot be started or the fault problem disappears, so that the time for solving the problem is missed, and the fault repair efficiency is low.
Disclosure of Invention
The embodiment of the application provides a method, a device and equipment for repairing faults of a vehicle-mounted operating system, wherein the technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a method for repairing a fault of a vehicle-mounted operating system, where the vehicle-mounted operating system includes a plurality of functional modules for processing system data, and the method includes:
when a certain preset fault occurs in a target function module, acquiring a target fault code corresponding to the preset fault;
determining a fault type corresponding to the target fault code, and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces;
and controlling the target function module to call the target interface and executing the target fault repairing program.
Optionally, the method further comprises the steps of:
and broadcasting the target fault code in the vehicle-mounted operating system through the target function module, enabling other function modules except the target function module in the vehicle-mounted operating system to receive the target fault code, and controlling the other function modules in binding relationship with the target function module to execute the target fault repairing program together.
Optionally, before the target fault code is broadcast in the vehicle-mounted operating system by the target function module, the method includes:
acquiring a data calling relation among the functional modules;
and binding the function module of the calling data with the function module of the called data according to the data calling relation.
Optionally, the controlling and the other functional modules having the binding relationship with the target functional module execute the target fault repairing program together, including the steps of:
and controlling the other functional modules to judge whether the fault corresponding to the target fault code is a public fault, and if so, controlling the other functional modules to execute the target fault repairing program together.
Optionally, the controlling and the other functional modules having the binding relationship with the target functional module execute the target fault repairing program together, further including the steps of:
and controlling the other function modules to judge whether the fault corresponding to the target fault code is a non-public fault, if so, controlling the non-public fault associated function module to search a target interface corresponding to the target fault repairing program from a program interface of the vehicle-mounted operating system, and calling back the target interface to execute the target fault repairing program.
Optionally, when a preset fault occurs in the target function module, the method further includes the steps of:
capturing running environment information of a current vehicle-mounted operating system;
and storing the target fault and the current operating environment information according to a preset local path.
Optionally, when a preset fault occurs in the target function module, the method further includes the steps of:
if the vehicle-mounted operating system is in a development mode, capturing running environment information of the current vehicle-mounted operating system and a log document of the target function module;
storing the target fault, the current operating environment information and the log document of the target function module according to a preset local path;
and/or the presence of a gas in the gas,
and outputting the target fault, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system.
In a second aspect, an embodiment of the present application provides a fault repairing apparatus for an onboard operating system, including:
a first obtaining module 61, configured to obtain, when a certain preset fault occurs in a target function module, a target fault code corresponding to the preset fault;
a second obtaining module 62, configured to determine a fault type corresponding to the target fault code, and search, according to a correspondence between the fault type and a preset fault repairing program, a target interface corresponding to the target fault repairing program from a fault repairing program interface library; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces;
and the execution control module 63 is configured to control the target function module to call the target interface, and execute the target fault repairing program.
In a third aspect, an embodiment of the present application provides an apparatus, including: a processor, a memory and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method for fault recovery of an in-vehicle operating system according to the first aspect when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, where a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method for repairing a fault of an in-vehicle operating system according to the first aspect.
In the embodiment of the application, different faults are preset in the vehicle-mounted operating system, the faults are classified according to fault codes corresponding to the faults, a fault repairing program interface library is preloaded in each functional module, and a plurality of calling interfaces of preset fault repairing programs are provided, so that when a certain preset fault occurs in a target functional module, a target fault code corresponding to the preset fault can be timely acquired, and the fault type corresponding to the target fault code is determined. And then according to the corresponding relation between the fault type and a preset fault repairing program, searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library, controlling the target function module to call the target interface, executing the target fault repairing program, rapidly completing the repairing of the fault in the target function module, ensuring the normal operation of a vehicle-mounted operating system, and further improving the driving safety of the vehicle.
For a better understanding and implementation, the technical solutions of the present application are described in detail below with reference to the accompanying drawings.
Drawings
Fig. 1 is a schematic flowchart of a fault repairing method for a vehicle-mounted operating system according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data call relationship between functional modules according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating a method for repairing a failure of an onboard operating system according to another embodiment of the present application;
fig. 4 is a schematic flowchart of S104 in a fault repairing method for a vehicle-mounted operating system according to another embodiment of the present application;
FIG. 5 is a flowchart illustrating a method for repairing a failure of a vehicle-mounted operating system according to another embodiment of the present application;
FIG. 6 is a schematic structural diagram of a fault recovery apparatus of an onboard operating system according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a fault repair device of an in-vehicle operating system according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if/if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The vehicle-mounted operating system is a program system for managing and controlling vehicle-mounted hardware and vehicle-mounted software resources, is system software capable of directly running on a computer bare computer, can manage computer hardware, software and data resources, realizes a plurality of functions such as audio and video signal processing, system time management and auxiliary driving, and enables an automobile to keep efficient and safe driving.
The vehicle-mounted operating system comprises a plurality of functional modules for processing system data, the functional modules run in the vehicle-mounted operating system in a process mode, and the functional modules are matched to work to ensure the normal running of the vehicle-mounted operating system.
However, in the actual use process of the automobile, each functional module in the vehicle-mounted operating system has a certain probability of being out of order, for example: io read-write abnormity, file operation abnormity, communication blockage, thread blockage, resource preemption, null pointer, data stack overflow and the like. If the faults can not be timely repaired, the normal operation of the operating system can be influenced, so that the driving safety of the automobile is influenced.
In an alternative embodiment, the execution main body of the fault repairing method for the vehicle-mounted operating system may be a computer device on which the vehicle-mounted operating system is mounted, or may be a component in the computer device, such as a processor or a microprocessor; in another alternative embodiment, the execution subject may be another computer device on the automobile, which establishes a data connection with the computer device carrying the vehicle-mounted operating system, or a component in the other computer device; in other alternative embodiments, the execution main body may also be a remote server that establishes a network connection with the in-vehicle operating system.
In the embodiment of the present application, a computer device (hereinafter referred to as a fault recovery device) on which the in-vehicle operating system is mounted is used as an execution subject, and a fault recovery method for the in-vehicle operating system is executed.
Referring to fig. 1, a schematic flow chart of a method for repairing a fault of a vehicle-mounted operating system according to an embodiment of the present application is shown, where the method includes the following steps:
s101: when a certain preset fault occurs in the target function module, a target fault code corresponding to the preset fault is obtained.
In the embodiment of the present application, a plurality of preset faults and a fault code corresponding to each preset fault are stored in the fault repairing device.
The fault code is a string of codes for identifying preset faults, and the type of the fault code can be a character string type or a numerical value type.
The plurality of preset faults and the fault codes corresponding to each preset fault may be stored in the form of a structured file, such as a two-dimensional data relation table, or in the form of an unstructured file, such as an XML file, and the specific storage form is not limited herein.
Specifically, if the fault repairing device monitors all the functional modules, when a certain preset fault occurs in a target functional module, the fault repairing device actively captures the preset fault, and obtains a target fault code corresponding to the preset fault.
If each functional module carries out self-monitoring, when a target functional module has a certain preset fault, a fault signal is sent to the fault repairing equipment, and the fault repairing equipment responds to the fault signal to acquire a target fault code corresponding to the preset fault.
In an optional embodiment, the plurality of preset faults and the fault code corresponding to each preset fault may also be stored in an external device that establishes a data connection with the fault repairing device, and when a certain preset fault occurs in the target function module, the fault repairing device sends preset fault information to the external device and receives the target fault code corresponding to the preset fault from the external device.
S102: determining a fault type corresponding to the target fault code, and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces.
The fault code and the fault type have a many-to-one corresponding relation, the fault repairing equipment can determine the fault type corresponding to the target fault code according to the preset corresponding relation between the fault code and the fault type, and then search the target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and the preset fault repairing program.
In the embodiment of the present application, the failure types include an IO read-write failure, a file failure, a resource preemption failure, a communication failure, and the like, and different types of failures correspond to different failure recovery programs, for example: the method comprises the following steps of process restarting, thread restarting, equipment restarting, file reopening, IPC reinitialization, live database importing of backup files and the like.
The fault repairing program interface library is pre-loaded in each functional module and can provide a plurality of preset fault repairing program calling interfaces for the functional modules.
The fault repairing program is stored in the fault repairing device in the form of a section of code, and the fault repairing program can be called by the fault repairing program interface library provided for the calling interface of the functional module.
S103: and controlling the target function module to call the target interface and executing the target fault repairing program.
After the target function module obtains the target interface, the fault repairing equipment controls the target function module to call the target interface and execute the target fault repairing program.
In the embodiment of the application, different faults are preset in the vehicle-mounted operating system, the faults are classified according to fault codes corresponding to the faults, a fault repairing program interface library is preloaded in each functional module, and a plurality of calling interfaces of preset fault repairing programs are provided, so that when a certain preset fault occurs in a target functional module, a target fault code corresponding to the preset fault can be timely acquired, and the fault type corresponding to the target fault code is determined. And then according to the corresponding relation between the fault type and a preset fault repairing program, searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library, controlling the target function module to call the target interface, executing the target fault repairing program, rapidly completing the repairing of the fault in the target function module, ensuring the normal operation of a vehicle-mounted operating system, and further improving the driving safety of the vehicle.
In the vehicle-mounted operating system, a data call relationship exists between the functional modules, and a certain function of the operating system can be realized only by the cooperation of the functional modules. Specifically, please refer to fig. 2, which is a schematic structural diagram of a data call relationship between functional modules according to an embodiment of the present application, wherein fig. 2 shows a total of 6 functional modules, namely, modules 1 to Module6, according to an arrow indicating relationship, it can be understood that data of Module6 needs to be provided to modules 1 to Module5 for use, and therefore, if a fault occurs in Module6, which causes data abnormality, the modules 1 to Module5 have a higher probability of failing due to data that needs to use Module6, so as to affect a normal use of a certain function of an operating system, and in order to solve the above problem, in another embodiment of the present application, referring to fig. 3, on the basis of executing steps S101 to S103, the method further includes step S104, which is specifically as follows:
s104: and broadcasting the target fault code in the vehicle-mounted operating system through the target function module, so that other function modules except the target function module in the vehicle-mounted operating system receive the target fault code, and controlling other function modules in binding relationship with the target function module to execute the target fault repairing program together.
When a target function module fails, the fault repairing equipment controls the target function module to call a target interface to execute a target fault repairing program, and broadcasts the target fault code in the vehicle-mounted operating system through the target function module, so that other function modules in the vehicle-mounted operating system except the target function module receive the target fault code, and controls other function modules in binding relationship with the target function module to execute the target fault repairing program.
Specifically, the fault repairing device controls the target function module to encapsulate the identifier of the target function module and the target fault code, and broadcasts the encapsulated identifier of the target function module and the target fault code to other function modules in the form of a broadcast instruction, wherein the identifier of the target function module is used for determining which function module the broadcast instruction is sent by.
Therefore, after other function modules are controlled to analyze after receiving the broadcast instruction, the identification and the target fault code of the target function module are obtained, whether the target function module is in a binding relationship with the target function module is judged according to the identification of the target function module, and if the target function module is in the binding relationship with the target function module, the other function modules are controlled to execute the target fault repairing program together.
In an optional embodiment, before executing step S104, the fault repairing apparatus needs to further obtain a data call relationship between the functional modules, and then bind the functional module that calls data and the functional module that is called data according to the data call relationship.
The data call relation is the relation between the functional modules which is determined in the bottom layer design stage of the vehicle-mounted operating system. In this embodiment of the present application, the data call relationship may be stored in a form of a data call relationship diagram, where the data call relationship diagram is a directed graph, and at least one data call relationship diagram is stored in the fault repairing device.
Specifically, the fault repairing device acquires a data calling relation graph, and binds a function module calling data and a function module called data according to a connection relation between nodes in the graph.
The binding mode can be a mode of establishing a binding table with the calling relationship, and the binding table stores the identifier of the functional module of the called data and the identifier of the corresponding functional module calling the data.
In an alternative embodiment, in order to more accurately process the fault and reduce the system overhead, referring to fig. 4, step S104 includes steps S1041 to S1042, which are as follows:
s1041: and controlling the other functional modules to judge whether the fault corresponding to the target fault code is a public fault, and if so, controlling the other functional modules to execute the target fault repairing program together.
When the fault is set, the common fault and the non-common fault can be distinguished, the common fault is a fault with higher occurrence probability, is a fault which needs to be processed by all other functional modules, and an interface is preloaded in a fault repairing program interface library. And the non-public fault is a special fault, only a specific functional module is needed for processing, and an interface cannot be preloaded in a fault repairing program interface library.
And controlling other functional modules which are in binding relation with the target functional module by the fault repairing equipment to judge whether the fault corresponding to the target fault code is a public fault, if so, controlling the other functional modules to search a target interface corresponding to the target fault repairing program from a self fault repairing program interface library, and executing the target fault repairing program together.
S1042: and controlling the other function modules to judge whether the fault corresponding to the target fault code is a non-public fault, if so, controlling the non-public fault associated function module to search a target interface corresponding to the target fault repairing program from a program interface of the vehicle-mounted operating system, and calling back the target interface to execute the target fault repairing program.
The program interfaces of the vehicle-mounted operating system include all the callable interfaces of the vehicle-mounted operating system, but only some of the callable interfaces corresponding to the common fault are loaded into the fault recovery program interface library of each functional module from the program interfaces of the vehicle-mounted operating system in advance.
Therefore, if the fault corresponding to the target fault code is a non-public fault, the non-public fault correlation function module having a binding relationship with the target function module needs to be controlled to search for the target interface corresponding to the target fault repairing program from the program interfaces of the vehicle-mounted operating system, and the target interface is called back to execute the target fault repairing program.
In this embodiment, the target fault code is broadcasted in the vehicle-mounted operating system by the target function module, so that other function modules in the vehicle-mounted operating system except the target function module receive the target fault code, and control other function modules in a binding relationship with the target function module to execute the target fault repairing program together, so that when a certain function module fails, the other function modules in the binding relationship with the certain function module can also acquire fault information in time and perform corresponding processing quickly, which is more favorable for ensuring normal operation of the operating system and improving the efficiency of fault processing.
In addition, because the fault of the functional module in the vehicle-mounted operating system is usually a probabilistic fault, and there may be some random problems, which are usually problems that a rule cannot be found to recur, thereby causing quality accidents, user complaints, and the like, in order to reduce the occurrence of such a situation, it becomes difficult to recur the random fault in the process of developing the functional module and in the link of customer maintenance, so that in other embodiments of the present application, a fault repairing method for the vehicle-mounted operating system is provided, please refer to fig. 5, which includes steps S201 to S205, where steps S201 to S203 are the same as steps S101 to S103, and the specific details are as follows:
s201: when a certain preset fault occurs in the target function module, a target fault code corresponding to the preset fault is obtained.
S202: determining a fault type corresponding to the target fault code, and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces.
S203: and controlling the target function module to call the target interface and executing the target fault repairing program.
S204: and if the vehicle-mounted operating system is in a development mode, capturing the running environment information of the current vehicle-mounted operating system and the log document of the target function module.
When a certain preset fault occurs in a target function module, if the vehicle-mounted system is in a development mode, the fault repairing equipment captures current running environment information of the vehicle-mounted operating system and a log document of the target function module.
Wherein, the current operation environment information comprises: memory state, CPU state, FLASH state, partition read-write attribute, running state of each process, process CPU proportion, memory proportion and the like.
The log document of the target function module refers to records of the running process of the target function module, including an event flow, a service processing flow, a data access condition, a network access condition and the like triggered by the log document.
S205: storing the target fault, the current operating environment information and the log document of the target function module according to a preset local path; and/or outputting the target fault, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system.
And storing a preset local path in the vehicle-mounted operating system, and pointing to the target fault code, the current operating environment information and a storage area of a log document of the target function module.
The fault repairing device can store the target fault code, the current operating environment information and the log document of the target function module according to a preset local path, and then developers can better reproduce the fault by calling the information.
The fault repairing device can also directly output the target fault code, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system, and the condition is more suitable for a development mode. The serial port of the vehicle-mounted operating system refers to the serial port of computer equipment carrying the vehicle-mounted operating system.
The fault repairing device can also store the target fault, the current operating environment information and the log document of the target function module according to a preset local path, and output the target fault, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system.
In an optional embodiment, if the vehicle-mounted operating system is not in the development mode, for example, in a scene in which a user is using, when a certain preset fault occurs to the target function module, the vehicle-mounted operating system also needs to capture the running environment information of the current vehicle-mounted operating system, and store the target fault and the current running environment information according to a preset local path.
In this case, since the user is using the system, the storage area is not easily erased and written too frequently, so that the stored operating environment information is less, and only the critical memory state, the process CPU occupation ratio and the like are recorded.
In this embodiment, when a certain preset fault occurs, the target fault code, the current operating environment information, and the log file of the target function module are stored or output through a serial port, so that when a probabilistic fault occurs, the key information can be captured in time, the success rate of problem recurrence is improved, and further the occurrence of quality accidents is reduced.
Fig. 6 is a schematic structural diagram of a fault repairing apparatus of a vehicle-mounted operating system according to an embodiment of the present application. The apparatus may be implemented as all or part of a fault repair device of an onboard operating system by software, hardware, or a combination of both. The device 6 comprises a first acquisition unit 61, a second acquisition module 62 and an execution control module 63;
a first obtaining module 61, configured to obtain, when a certain preset fault occurs in a target function module, a target fault code corresponding to the preset fault;
a second obtaining module 62, configured to determine a fault type corresponding to the target fault code, and search, according to a correspondence between the fault type and a preset fault repairing program, a target interface corresponding to the target fault repairing program from a fault repairing program interface library; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces;
and the execution control module 63 is configured to control the target function module to call the target interface, and execute the target fault repairing program.
In the embodiment of the application, different faults are preset in the vehicle-mounted operating system, the faults are classified according to fault codes corresponding to the faults, a fault repairing program interface library is preloaded in each functional module, and a plurality of calling interfaces of preset fault repairing programs are provided, so that when a certain preset fault occurs in a target functional module, a target fault code corresponding to the preset fault can be timely acquired, and the fault type corresponding to the target fault code is determined. And then according to the corresponding relation between the fault type and a preset fault repairing program, searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library, controlling the target function module to call the target interface, executing the target fault repairing program, rapidly completing the repairing of the fault in the target function module, ensuring the normal operation of a vehicle-mounted operating system, and further improving the driving safety of the vehicle.
Optionally, the apparatus 6 further includes:
and the broadcasting module is used for broadcasting the target fault code in the vehicle-mounted operating system through the target function module, so that other function modules except the target function module in the vehicle-mounted operating system receive the target fault code, and controlling the other function modules in binding relationship with the target function module to execute the target fault repairing program together.
Optionally, the apparatus 6 further includes:
the third acquisition module is used for acquiring the data call relation among the functional modules;
and the binding module is used for binding the functional module for calling the data and the functional module for called data according to the data calling relation.
Optionally, the broadcasting module includes:
and the first control module is used for controlling the other functional modules to judge whether the fault corresponding to the target fault code is a common fault or not, and if so, controlling the other functional modules to execute the target fault repairing program together.
Optionally, the broadcasting module further includes:
a second control module, configured to control the other function modules to determine whether a fault corresponding to the target fault code is a non-public fault, if so, control the non-public fault associated function module to search a target interface corresponding to the target fault repairing program from program interfaces of the vehicle-mounted operating system, and call back the target interface to execute the target fault repairing program
Optionally, the apparatus 6 further includes:
the first capturing module is used for capturing the running environment information of the current vehicle-mounted operating system;
a first storage module, configured to store the target fault and the current operating environment information according to a preset local path
Optionally, the apparatus 6 further includes:
the second capturing module is used for capturing the running environment information of the current vehicle-mounted operating system and the log document of the target function module if the vehicle-mounted operating system is in a development mode;
the second storage module is used for storing the target fault, the current operating environment information and the log document of the target function module according to a preset local path;
and/or the presence of a gas in the gas,
and outputting the target fault, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system.
Fig. 7 is a schematic structural diagram of an apparatus according to an embodiment of the present application. As shown in fig. 7, the apparatus 7 may include: a processor 70, a memory 71 and a computer program 72 stored in said memory 71 and executable on said processor 70, such as: a fault recovery program of the vehicle-mounted operating system; the processor 70, when executing the computer program 72, implements the steps in the above-described method embodiments, such as the steps S101 to S103 shown in fig. 1. Alternatively, the processor 70, when executing the computer program 72, implements the functions of each module/unit in each device embodiment described above, for example, the functions of the modules 61 to 63 shown in fig. 6.
The processor 70 may include one or more processing cores, among others. The processor 70 is connected to various parts in the control device 7 by various interfaces and lines, and executes various functions of the control device 7 and processes data by operating or executing instructions, programs, code sets or instruction sets stored in the memory 71 and calling data in the memory 71, and optionally, the processor 70 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), Programmable Logic Array (PLA). The processor 70 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing contents required to be displayed by the touch display screen; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 70, but may be implemented by a single chip.
The Memory 71 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 71 includes a non-transitory computer-readable medium. The memory 71 may be used to store instructions, programs, code sets or instruction sets. The memory 71 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch instructions, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 71 may alternatively be at least one memory device located remotely from the processor 70.
An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executed by the method steps in the embodiments shown in fig. 1 and fig. 3 to fig. 5, and a specific execution process may refer to specific descriptions of the embodiments shown in fig. 1 and fig. 3 to fig. 5, which are not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc.
The present invention is not limited to the above-described embodiments, and various modifications and variations of the present invention are intended to be included within the scope of the claims and the equivalent technology of the present invention if they do not depart from the spirit and scope of the present invention.

Claims (10)

1. A fault recovery method for a vehicle-mounted operating system, wherein the vehicle-mounted operating system comprises a plurality of functional modules for processing system data, the method is characterized by comprising the following steps:
when a certain preset fault occurs in a target function module, acquiring a target fault code corresponding to the preset fault;
determining a fault type corresponding to the target fault code, and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces;
and controlling the target function module to call the target interface and executing the target fault repairing program.
2. The method for repairing a failure of an in-vehicle operation system according to claim 1, characterized by further comprising the steps of:
and broadcasting the target fault code in the vehicle-mounted operating system through the target function module, enabling other function modules except the target function module in the vehicle-mounted operating system to receive the target fault code, and controlling the other function modules in binding relationship with the target function module to execute the target fault repairing program together.
3. The method for repairing the fault of the vehicle-mounted operating system according to claim 2, wherein before the target fault code is broadcast in the vehicle-mounted operating system by the target function module, the method comprises the following steps:
acquiring a data calling relation among the functional modules;
and binding the function module of the calling data with the function module of the called data according to the data calling relation.
4. The method for repairing the fault of the vehicle-mounted operating system according to claim 2, wherein the controlling executes the target fault repairing program together with other functional modules having a binding relationship with the target functional module, and comprises the steps of:
and controlling the other functional modules to judge whether the fault corresponding to the target fault code is a public fault, and if so, controlling the other functional modules to execute the target fault repairing program together.
5. The fault recovery method for the vehicle-mounted operating system according to claim 4, characterized by further comprising the steps of:
and controlling the other function modules to judge whether the fault corresponding to the target fault code is a non-public fault, if so, controlling the non-public fault associated function module to search a target interface corresponding to the target fault repairing program from a program interface of the vehicle-mounted operating system, and calling back the target interface to execute the target fault repairing program.
6. The method for repairing the failure of the vehicle-mounted operating system according to claim 1, wherein when a predetermined failure occurs in the target function module, the method further comprises the steps of:
capturing running environment information of a current vehicle-mounted operating system;
and storing the target fault and the current operating environment information according to a preset local path.
7. The method for repairing the failure of the vehicle-mounted operating system according to claim 1, wherein when a predetermined failure occurs in the target function module, the method further comprises the steps of:
if the vehicle-mounted operating system is in a development mode, capturing running environment information of the current vehicle-mounted operating system and a log document of the target function module;
storing the target fault, the current operating environment information and the log document of the target function module according to a preset local path;
and/or the presence of a gas in the gas,
and outputting the target fault, the current operating environment information and the log document of the target function module through a serial port of the vehicle-mounted operating system.
8. A failure recovery apparatus for an in-vehicle operating system including a plurality of functional modules that process system data, comprising:
the first acquisition module is used for acquiring a target fault code corresponding to a preset fault when the target function module generates the preset fault;
the second acquisition module is used for determining a fault type corresponding to the target fault code and searching a target interface corresponding to the target fault repairing program from a fault repairing program interface library according to the corresponding relation between the fault type and a preset fault repairing program; the fault repairing program interface library is pre-loaded in each functional module and comprises a plurality of preset fault repairing program calling interfaces;
and the execution control module is used for controlling the target function module to call the target interface and executing the target fault repairing program.
9. A fail-over device of an in-vehicle operating system, characterized by comprising: processor, memory and computer program stored in the memory and executable on the processor, which when executed by the processor implements the method of fault recovery for an in-vehicle operating system of claims 1 to 7.
10. A computer-readable storage medium characterized by: the computer-readable storage medium stores a computer program which, when executed by a processor, implements the fail-over method of the in-vehicle operating system according to claims 1 to 7.
CN202011048157.3A 2020-09-29 2020-09-29 Fault repairing method, device and equipment for vehicle-mounted operating system Pending CN112181746A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011048157.3A CN112181746A (en) 2020-09-29 2020-09-29 Fault repairing method, device and equipment for vehicle-mounted operating system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011048157.3A CN112181746A (en) 2020-09-29 2020-09-29 Fault repairing method, device and equipment for vehicle-mounted operating system

Publications (1)

Publication Number Publication Date
CN112181746A true CN112181746A (en) 2021-01-05

Family

ID=73947006

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011048157.3A Pending CN112181746A (en) 2020-09-29 2020-09-29 Fault repairing method, device and equipment for vehicle-mounted operating system

Country Status (1)

Country Link
CN (1) CN112181746A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113342430A (en) * 2021-06-10 2021-09-03 深圳市元征软件开发有限公司 Fault code processing method and device, terminal equipment and readable storage medium
CN114756299A (en) * 2022-04-21 2022-07-15 国汽智控(北京)科技有限公司 Vehicle fault processing method and device, electronic device and storage medium
CN114802283A (en) * 2022-06-27 2022-07-29 宁波均胜智能汽车技术研究院有限公司 Intelligent driving fault processing system and method, intelligent vehicle and readable storage medium
CN115016969A (en) * 2022-06-06 2022-09-06 广东大舜汽车科技有限公司 Automobile electronic system repairing method and device

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113342430A (en) * 2021-06-10 2021-09-03 深圳市元征软件开发有限公司 Fault code processing method and device, terminal equipment and readable storage medium
CN114756299A (en) * 2022-04-21 2022-07-15 国汽智控(北京)科技有限公司 Vehicle fault processing method and device, electronic device and storage medium
CN115016969A (en) * 2022-06-06 2022-09-06 广东大舜汽车科技有限公司 Automobile electronic system repairing method and device
CN114802283A (en) * 2022-06-27 2022-07-29 宁波均胜智能汽车技术研究院有限公司 Intelligent driving fault processing system and method, intelligent vehicle and readable storage medium
CN114802283B (en) * 2022-06-27 2022-11-01 宁波均胜智能汽车技术研究院有限公司 Intelligent driving fault processing system and method, intelligent vehicle and readable storage medium

Similar Documents

Publication Publication Date Title
CN112181746A (en) Fault repairing method, device and equipment for vehicle-mounted operating system
CN105611330B (en) Smart television maintenance method and system, server and mobile terminal
CN108804299B (en) Application program exception handling method and device
CN108804215B (en) Task processing method and device and electronic equipment
CN114546738B (en) Universal test method, system, terminal and storage medium for server
US9519537B2 (en) Apparatus, system and method for application log data processing
CN111897724A (en) Automatic testing method and device suitable for cloud platform
CN109408361A (en) Monkey tests restored method, device, electronic equipment and computer readable storage medium
CN108509322B (en) Method for avoiding excessive return visit, electronic device and computer readable storage medium
CN111353143A (en) Sensitive authority detection method and device and storage medium
CN112148606A (en) Embedded point testing method, device, equipment and computer readable medium
CN115543827A (en) Buried point data display method and device
US11169863B2 (en) Dynamic management method for menu, server and system
CN115617780A (en) Data import method, device, equipment and storage medium
CN111061448A (en) Log information display method and device, electronic equipment and storage medium
CN110648126A (en) Payment type configuration method, device, server and storage medium
CN117056115B (en) Application program repairing method and device, storage medium and electronic equipment
CN111158995B (en) Method and system for realizing cross-system log tracking query based on skywalk and ELK platform
CN113238935A (en) Application testing method, system, device, medium, and computer program product
CN114416807A (en) Data merging method, device and system for customer account
CN114385457A (en) Application program data acquisition method, device, equipment and storage medium
CN111209197B (en) Application continuous integration test method, system, equipment and storage medium
CN113297149A (en) Method and device for monitoring data processing request
CN111475783B (en) Data detection method, system and equipment
CN108108369B (en) Method and device for processing calling error of common interface library

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination