Equipment exception recovery method and device, terminal equipment and storage medium

Abstract

The invention is suitable for the technical field of equipment management, and provides an equipment exception recovery method and device, terminal equipment and a storage medium, and the method comprises the steps: obtaining multiple pieces of feature data corresponding to diagnostic equipment under the condition that the working state of the diagnostic equipment is abnormal; determining an abnormal object of the diagnosis equipment according to the feature data; and sending the first instruction to the diagnosis equipment, so that the diagnosis equipment recovers the abnormal object according to the first instruction. According to the method, the abnormality can be recovered and tracked in time when the diagnosis equipment is abnormal, so that the performance of the diagnosis application is improved, and the use experience of a user is improved.

Description

Technical Field

[0001] The present application belongs to the technical field of device exception handling, and in particular relates to a device exception recovery method, apparatus, terminal device, and storage medium. Background Art

[0002] Modern vehicles are highly intelligent, comprised of numerous complex electronic systems and mechanical components. Diagnostic equipment communicates with the vehicle's onboard diagnostic system, rapidly reading and analyzing various fault codes and real-time data. This equipment can pinpoint the specific cause of a malfunction, providing maintenance personnel with clear repair instructions, significantly reducing troubleshooting time and improving maintenance efficiency.

[0003] When using diagnostic equipment, users may encounter changes to the device's Internet Protocol (IP) address, impacting diagnostic communications for a specific IP address. They may also encounter occasional anomalies in the configuration file corresponding to the diagnostic application, impacting functionality. Related technologies rely on third-party tools to assist in modifying and restoring the IP address, or require users to reinstall the device or directly send a replacement configuration file. However, these methods are limited, require frequent user interaction, and are difficult to analyze, severely impacting application performance and resulting in a poor user experience. Summary of the Invention

[0004] The embodiments of the present application provide a method, apparatus, terminal device and computer-readable storage medium for recovering device abnormalities, which can promptly recover and track the cause of the abnormality when an abnormality occurs in the diagnostic device, improve the performance of the diagnostic application, and enhance the user experience.

[0005] In a first aspect, an embodiment of the present application provides a method for recovering from a device abnormality, comprising:

[0006] When the working state of the diagnostic device is abnormal, obtaining multiple characteristic data corresponding to the diagnostic device;

[0007] Determine the abnormal object where the diagnostic equipment has an abnormality based on the characteristic data;

[0008] Perform abnormal recovery on the abnormal object to restore the diagnostic equipment to normal working state.

[0009] In an embodiment of the present application, by obtaining multiple characteristic data of the diagnostic device, the working status of the diagnostic device can be comprehensively and meticulously reflected, and these data cover all aspects of the operation of the diagnostic device. Based on the analysis of the characteristic data, the specific object where the abnormality occurs can be accurately found. After the abnormal object is identified, special abnormality recovery measures can be taken for the object. This targeted processing method can quickly solve the problem and reduce equipment downtime. And compared with traditional methods, when an abnormality occurs in the diagnostic device, there is no need to rely on third-party tools to promptly identify the abnormal object and perform abnormal recovery in a timely manner. This method can effectively recover the abnormality of the diagnostic device, improve the application performance of the diagnostic device and improve the user experience.

[0010] In a possible implementation of the first aspect, determining, based on the characteristic data, an abnormal object in which the diagnostic device is abnormal includes:

[0011] When the characteristic data is the first identification data corresponding to the current diagnostic device, comparing the first identification data with the preset identification data;

[0012] If the first identification data is different from the preset identification data, it is determined that the abnormal object of the abnormality of the diagnostic device is the abnormality of the identification data.

[0013] In an embodiment of the present application, the first identification data is compared with the preset identification data, which can quickly identify the problem among many potential abnormal factors. When it is found that the first identification data is different from the preset identification data, the abnormal object is directly determined to be an identification data abnormality. There is no need to check other complex functions and components of the device one by one, which greatly shortens the time to discover the problem.

[0014] In a possible implementation of the first aspect, sending a first instruction to a diagnostic device so that the diagnostic device recovers the abnormal object according to the first instruction includes:

[0015] When it is determined that the abnormal object of the diagnostic device is abnormal identification data, the first instruction is used to instruct the diagnostic device to modify the current first identification data to preset identification data.

[0016] In an embodiment of the present application, when an abnormal identification data occurs in the diagnostic device, the first identification data is modified to the preset identification data using the first instruction. This operation can quickly restore the normal operation of the device, ensure the accuracy of data communication and enhance the stability of the system, which is of great significance to the efficient operation of the diagnostic device.

[0017] In a possible implementation of the first aspect, determining, based on the characteristic data, an abnormal object in which the diagnostic device is abnormal includes:

[0018] Determine whether the characteristic data contains configuration information corresponding to the diagnostic device; wherein the configuration information is the configuration parameters of the diagnostic device during the diagnostic function;

[0019] If the characteristic data does not completely include the configuration information corresponding to the diagnostic device, it is determined that the abnormal object of the abnormality of the diagnostic device is an information configuration abnormality.

[0020] In the embodiments of this application, the configuration information of the diagnostic device is directly related to the proper functioning of its diagnostic functions. By determining whether the characteristic data contains complete configuration information, if it is found that it does not, the abnormal object is accurately located as an information configuration anomaly. This avoids blindly troubleshooting when a device problem occurs, greatly narrowing the scope of the problem search.

[0021] In a possible implementation of the first aspect, sending a first instruction to a diagnostic device so that the diagnostic device recovers the abnormal object according to the first instruction includes:

[0022] When it is determined that the abnormal object causing the abnormality of the diagnostic device is an information configuration abnormality, the first instruction is used to instruct the diagnostic device to replace the configuration information with the configuration information corresponding to the received preset configuration file; wherein the preset configuration file is the configuration file corresponding to the diagnostic device in normal working state.

[0023] In the embodiments of the present application, if the configuration information of the diagnostic device is missing or abnormal, it will directly affect its normal operation. The first instruction calls the configuration information corresponding to the preset configuration file to replace it, which can quickly restore the configuration state of the device, allowing the device to continue to perform diagnostic work efficiently and reducing the downtime of the device caused by configuration problems.

[0024] In a possible implementation of the first aspect, the method further includes:

[0025] After determining the abnormal object in which the diagnostic device is abnormal, obtaining first log information corresponding to the diagnostic device; wherein the first log information includes an operation record of the diagnostic device during the diagnosis process;

[0026] Analyze the first log information to determine the cause of the abnormality of the abnormal object;

[0027] The version corresponding to the diagnostic device is updated according to the cause of the abnormality of the abnormal object.

[0028] In the embodiment of the present application, by obtaining logs, analyzing causes and performing version updates, a series of operations can accurately solve problems, continuously optimize device performance, prevent potential failures, and improve the reliability and stability of diagnostic equipment.

[0029] In a possible implementation of the first aspect, when no abnormality occurs in the working state of the diagnostic device, the method further includes:

[0030] Obtaining second log information corresponding to the diagnostic device; wherein the second log information includes an operation record of the diagnostic device during a historical diagnostic process;

[0031] Delete the second log information;

[0032] Record the operation record of the diagnostic device during this diagnostic process and generate third log information.

[0033] In an embodiment of the present application, the historical second log information is deleted and the third log information focused on the current diagnosis is recorded to ensure the accuracy and timeliness of the log data. The environment and requirements of the diagnostic work are constantly changing, and the historical log may not reflect the current actual situation. The newly generated third log information can accurately record the latest operations of the current diagnosis, provide a reliable basis for subsequent analysis and decision-making, and improve the quality and reliability of the diagnostic work.

[0034] In a second aspect, an embodiment of the present application provides a device abnormality recovery apparatus, comprising:

[0035] A data acquisition module, used for acquiring a plurality of characteristic data corresponding to the diagnostic device when an abnormality occurs in the working state of the diagnostic device;

[0036] An abnormality determination module, used to determine the abnormal object of the diagnostic device based on the characteristic data;

[0037] The abnormality recovery module is used to send a first instruction to the diagnostic device, so that the diagnostic device recovers the abnormal object according to the first instruction.

[0038] In a third aspect, an embodiment of the present application provides a terminal device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a device abnormality recovery method as described in any one of the first aspects above is implemented.

[0039] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the device abnormality recovery method as described in any one of the first aspects above.

[0040] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, enables the terminal device to execute any one of the device abnormality recovery methods in the first aspect above.

[0041] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0043] Figure 1 This is a flow chart of a method for recovering from an abnormality in a device provided in an embodiment of the present application;

[0044] Figure 2 This is a schematic diagram of the process for determining abnormal objects provided by the embodiment of the present application. Figure 1 ;

[0045] Figure 3 This is a schematic diagram of the process for determining abnormal objects provided by the embodiment of the present application. Figure 2 ;

[0046] Figure 4 This is a flowchart of anomaly tracking provided by an embodiment of the present application;

[0047] Figure 5 This is a structural block diagram of an abnormal device recovery device provided in an embodiment of the present application;

[0048] Figure 6 It is a structural diagram of the terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0050] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0051] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0052] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0053] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0054] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized.

[0055] Modern vehicles are highly intelligent, comprised of numerous complex electronic systems and mechanical components. Diagnostic equipment communicates with the vehicle's onboard diagnostic system, rapidly reading and analyzing various fault codes and real-time data. This equipment can pinpoint the specific cause of a malfunction, providing maintenance personnel with clear repair instructions, significantly reducing troubleshooting time and improving maintenance efficiency.

[0056] When using diagnostic equipment, users may encounter changes to the device's Internet Protocol (IP) address, impacting diagnostic communications for a specific IP address. They may also encounter occasional anomalies in the configuration file corresponding to the diagnostic application, impacting functionality. Related technologies rely on third-party tools to assist in modifying and restoring the IP address, or require users to reinstall the device or directly send a replacement configuration file. However, these methods are limited, require frequent user interaction, and are difficult to analyze, severely impacting application performance and resulting in a poor user experience.

[0057] To address the issues encountered in related technologies, this application provides a device exception recovery method. When a diagnostic device exception occurs, the method promptly resolves the exception, allowing users to continue using the diagnostic device normally. It also effectively tracks application execution and provides feedback on historical application function usage when an exception occurs, facilitating exception tracking. The method has a clear structure and is easy to understand and maintain.

[0058] See also Figure 1 , is a flow chart of a device abnormality recovery method provided in an embodiment of the present application. As an example and not a limitation, the method may include the following steps:

[0059] S101 , when a working state of a diagnostic device is abnormal, obtaining a plurality of characteristic data corresponding to the diagnostic device.

[0060] In the embodiments of the present application, during operation, the diagnostic device may not be in normal working state due to various reasons. For example, when a user is using the diagnostic device in a car diagnostic scenario, the diagnostic device may not be able to establish a connection with the vehicle's Electronic Control Unit (ECU), or an error message may appear when reading the vehicle's fault code, or the display screen of the diagnostic device itself may display an abnormal display, etc. These are all manifestations of abnormal working state of the diagnostic device. An abnormality analysis can be performed based on the abnormal situation reported by the user, and targeted solutions can be provided to solve the error.

[0061] To accurately determine the cause of an anomaly and implement effective solutions, it's necessary to collect multiple data points related to the anomaly of the diagnostic equipment, known as feature data. This data can reflect the anomaly from different perspectives, providing a basis for subsequent analysis and resolution.

[0062] Among them, feature data includes various types of information related to abnormal situations. For example, based on abnormal situations reported by users, relevant feature data can be obtained for the abnormal situations. For example, the IP information of the device is one of the important feature data. Because diagnostic equipment relies on IP addresses to communicate with other devices, if the IP is modified, it may cause communication abnormalities and affect the diagnostic work. Configuration file configuration items are also key feature data. The functions of diagnostic equipment rely on the parameter settings in the configuration file. If there are errors or abnormalities in the configuration items, it will directly lead to problems with the device function. In addition, the device's operation log, diagnostic operation records, communication data with other devices, etc. may all become feature data, reflecting the status and behavior of the device when it is abnormal from different aspects.

[0063] S102: Determine the abnormal object of the diagnostic device according to the characteristic data.

[0064] In the embodiment of the present application, after the diagnostic device experiences an abnormality, multiple characteristic data related to the abnormality are obtained. This collected data is used to determine whether the abnormal part or component of the diagnostic device (the abnormal object) is the abnormality reported by the user. Alternatively, the user can accurately identify which part or component of the diagnostic device has a problem.

[0065] In one embodiment, see Figure 2 , is a schematic diagram of the process of determining abnormal objects provided by the embodiment of the present application Figure 1 , step S102 includes:

[0066] S201 : When the characteristic data is first identification data corresponding to the current diagnostic device, the first identification data is compared with preset identification data.

[0067] In the embodiments of the present application, the first identification data is specific identity or status identification information of the current diagnostic device. It can be the device's IP address, a specific software version number, etc., which uniquely represents a certain attribute of the current device. The preset identification data is standard identification information that the diagnostic device should possess under normal circumstances. It is typically stored in a system database, configuration file, or device management center. For example, the IP address corresponding to the diagnostic device in normal working state.

[0068] When the system detects that the characteristic data it receives is the first identification data, it automatically initiates a comparison process. The system compares the first identification data with the preset identification data field by field and byte by byte. If the first identification data is the device's IP address, the preset identification data contains the device's correct IP address, and the system accurately compares the two addresses for complete consistency. If the first identification data is a software version number, the system also compares the major version number, minor version number, revision number, and other components according to the version number format specifications to ensure consistency.

[0069] S202: If the first identification data is different from the preset identification data, it is determined that the abnormal object of the abnormality of the diagnostic device is the abnormality of the identification data.

[0070] In an embodiment of the present application, comparison can be used to quickly determine whether the basic properties of the diagnostic device are normal. If the first identification data is inconsistent with the preset identification data, it indicates that an identification data anomaly has occurred in the device. For example, an inconsistent IP address may mean that the device has been replaced or tampered with; an abnormal software version number may cause unstable device functions, requiring a version update or repair operation. This comparison method provides a key basis for subsequent further abnormality investigation and processing, helps to promptly discover potential problems, and ensures the reliability and accuracy of the diagnostic equipment. If the two are completely consistent, it means that the basic identity or status information of the device is correct, no abnormality is found at the identification level, and it is necessary to analyze whether other components have abnormalities.

[0071] In the above method, the first identification data is compared with the preset identification data, which can quickly identify the problem among many potential abnormal factors. When it is found that the first identification data is different from the preset identification data, the abnormal object is directly determined to be an identification data abnormality. There is no need to check other complex functions and components of the device one by one, which greatly shortens the time to discover the problem.

[0072] In another embodiment, see Figure 3 , is a schematic diagram of the process of determining abnormal objects provided by the embodiment of the present application Figure 2 , step S102 includes:

[0073] S301, determining whether the characteristic data contains configuration information corresponding to the diagnostic device; wherein the configuration information is the configuration parameters of the diagnostic device during the diagnostic function.

[0074] In the embodiments of the present application, configuration parameters play a core role when the diagnostic device performs diagnostic functions. Taking automotive diagnostic equipment as an example, its configuration information may include communication protocol parameters (such as the baud rate and data frame format of protocols such as CAN and LIN). These parameters determine the communication method and data transmission speed between the diagnostic equipment and the electronic control units (ECUs) of the vehicle. It also includes diagnostic function parameters, such as the fault code reading range, the execution conditions of specific test functions, etc., which control the specific content and process of the diagnostic operation. Accurate configuration information is the basis for the normal operation of the diagnostic equipment and the acquisition of accurate diagnostic results.

[0075] After acquiring the diagnostic device's signature data, the system parses and filters it according to pre-set rules and formats. Because configuration information typically has a specific data structure and identifiers, the system identifies it based on these characteristics. The system may use file format parsing (such as parsing an INI configuration file) to determine whether the signature data contains complete or partial configuration information.

[0076] S302: If the characteristic data does not completely include the configuration information corresponding to the diagnostic device, it is determined that the abnormal object of the abnormality of the diagnostic device is an information configuration abnormality.

[0077] In an embodiment of the present application, if the characteristic data does not contain the configuration information corresponding to the diagnostic device, or the configuration information contained is incomplete or contains errors, then the diagnostic device is very likely to fail to work properly, or an erroneous result will appear during the diagnostic process, that is, it is determined to be an information configuration anomaly. This requires further investigation of the reasons for the missing or incorrect configuration information, such as configuration file damage, system update resulting in configuration loss, etc., and timely repair and reconfiguration. On the contrary, if the characteristic data contains complete and correct configuration information, this indicates that the configuration of the diagnostic device is in a normal state, which provides a guarantee for the smooth execution of the diagnostic function. In the subsequent diagnostic process, accurate diagnostic operations can be performed based on this configuration information.

[0078] In this method, the configuration information of the diagnostic device is directly related to the proper functioning of its diagnostic functions. By determining whether the signature data contains complete configuration information, if it is found to be incomplete, the anomaly is accurately identified as an information configuration anomaly. This avoids blind troubleshooting when a device problem occurs, significantly narrowing the scope of the problem search.

[0079] S103: Send a first instruction to the diagnostic device, so that the diagnostic device recovers the abnormal object according to the first instruction.

[0080] In the embodiments of the present application, after an abnormality occurs in the diagnostic device and the abnormal object is identified, "sending a first instruction to the diagnostic device to cause the diagnostic device to restore the abnormal object according to the first instruction" is a key operation to resolve the abnormality and restore normal operation of the device. The first instruction is a control command specifically designed based on the abnormality of the diagnostic device and the abnormal object that needs to be restored.

[0081] Among them, the instruction sender (which can be the remote management system of the diagnostic equipment, the host computer software, etc.) sends the first instruction through the communication link connected to the diagnostic equipment. The communication link can be a wired connection (such as USB, Ethernet, etc.) or a wireless connection (such as Wi-Fi, Bluetooth, etc.). The sender encapsulates the first instruction according to a specific communication protocol to ensure the accuracy and integrity of the instruction during the transmission process. The instruction is packaged into a data frame that conforms to the Ethernet protocol and sent to the diagnostic equipment through the network interface. After receiving the first instruction, the diagnostic equipment will parse the instruction. It will extract the operation requirements and related parameters in the instruction, and perform corresponding recovery operations on the abnormal object based on this information.

[0082] In one embodiment, step S103 includes:

[0083] When it is determined that the abnormal object of the diagnostic device is abnormal identification data, the first instruction is used to instruct the diagnostic device to modify the current first identification data to preset identification data.

[0084] In an embodiment of the present application, when the IP address of the diagnostic device is modified, resulting in a communication anomaly, the first instruction may include the correct IP address information (preset identification data) and an operation instruction for modifying the IP address. If the first instruction requires modifying the IP address, upon receiving the first instruction, the diagnostic device parses the first instruction, extracts the operation requirements and related parameters in the instruction, and then updates its own network configuration parameters according to the new IP address information in the instruction, completing the IP address correction.

[0085] In the above method, when the identification data of the diagnostic device is abnormal, the first instruction is used to modify the first identification data to the preset identification data. This operation can quickly restore the normal operation of the device, ensure the accuracy of data communication and enhance the stability of the system, which is of great significance to the efficient operation of the diagnostic device.

[0086] In another embodiment, step S103 includes:

[0087] When it is determined that the abnormal object causing the abnormality of the diagnostic device is an information configuration abnormality, the first instruction is used to instruct the diagnostic device to replace the configuration information with the configuration information corresponding to the received preset configuration file; wherein the preset configuration file is the configuration file corresponding to the diagnostic device in normal working state.

[0088] In this embodiment of the present application, when the diagnostic device is determined to have an abnormality due to an information configuration anomaly, that is, an error in a configuration item in the ini configuration file that affects a specific function, the first instruction will include the correct parameters for that configuration item (preset configuration file) and the operation requirements for modifying the configuration. This instruction is the core control signal for abnormality recovery and carries the key information for restoring the diagnostic device to normal operation.

[0089] After receiving the first instruction, the diagnostic device will parse the preset configuration file, then locate the corresponding position in the configuration file, and replace the erroneous configuration content with the correct parameters in the instruction, thereby restoring the normal state of the abnormal object and enabling the diagnostic device to work normally again.

[0090] In the above method, if the diagnostic device's configuration information is missing or abnormal, it will directly affect its normal operation. However, the first instruction calls the configuration information corresponding to the preset configuration file to replace it, which can quickly restore the device's configuration state, allowing the device to continue to perform diagnostic work efficiently and reducing device downtime caused by configuration issues.

[0091] In one embodiment, see Figure 4 , is a flowchart of the exception tracking provided by the embodiment of the present application, such as Figure 4 As shown, the device exception recovery method also includes exception tracking, specifically:

[0092] S401 , after determining the abnormal object of the diagnostic device, obtaining first log information corresponding to the diagnostic device; wherein the first log information includes an operation record of the diagnostic device during the diagnosis process.

[0093] In the embodiments of the present application, once the abnormal object causing the diagnostic device anomaly has been identified, the approximate scope of the problem has been determined. Obtaining the first log information at this point is to further explore the cause of the anomaly from the perspective of the device's operation records. For example, if the abnormal object is a functional module of the diagnostic device, reviewing the module's operation records during the diagnostic process can help identify the specific operation within the module that caused the anomaly.

[0094] The first log information primarily covers the diagnostic equipment's operational records during the diagnostic process. These records contain rich details, such as the start time of the diagnostic task, the various functions called during execution, the read and write operations of different vehicle system data, and communication interaction records with external devices (such as the vehicle control unit). Each operation record details the time the operation occurred, the type of operation, the data involved, and the results of the operation.

[0095] S402: Analyze the first log information to determine the cause of the abnormality of the abnormal object.

[0096] In an embodiment of the present application, after obtaining the first log information, the technician can perform a detailed analysis of the first log information. The first log information contains the operation record of the diagnostic device during the diagnostic process, and the information is complex. First, it is necessary to extract and organize the logs, sort out the operations in chronological order, and classify different types of operations, such as data reading operations, instruction sending operations, device communication operations, etc. At the same time, mark the results of the operation, such as success, failure, or error code and other key information for subsequent analysis.

[0097] Specifically, analysis can be based on error codes. For example, a communication error code might indicate a communication problem between the device and an external system (such as a vehicle control unit); an out-of-memory error code might indicate that the device ran out of resources during operation. Exception analysis can also be performed based on operation results. For example, if a data read operation returns a null value or illogical data, it could indicate a faulty data transmission line, an external device failure, or an error in the data parsing algorithm.

[0098] S403: Update the version of the diagnostic device according to the cause of the abnormality of the abnormal object.

[0099] In an embodiment of the present application, after determining the cause of the abnormal object's abnormality by analyzing the first log information, updating the corresponding version of the diagnostic device based on the cause is an effective means to solve the problem and improve device performance.

[0100] Specifically, different anomaly causes may correspond to different version issues. If the anomaly is due to a software algorithm vulnerability, resulting in inaccurate data processing results, a software update may be necessary to fix the algorithm. This means updating the software version corresponding to the diagnostic device to fix the cause of the anomaly.

[0101] The above method, through a series of operations such as obtaining logs, analyzing causes, and updating versions, can accurately solve problems, continuously optimize device performance, prevent potential failures, and improve the reliability and stability of diagnostic equipment.

[0102] It should be noted that if the technician does not specifically analyze the cause of the abnormality of the abnormal object during the analysis of the first log, the abnormality can be allowed to exist. However, when an abnormality occurs in the diagnostic device, the device abnormality recovery method provided in this application can be used to recover the abnormality in a timely manner without affecting the user's use of the diagnostic device.

[0103] In one embodiment, when the working state of the diagnostic device is normal, the method further includes:

[0104] Obtaining second log information corresponding to the diagnostic device; wherein the second log information includes an operation record of the diagnostic device in a historical diagnostic process; deleting the second log information; recording the operation record of the diagnostic device in this diagnostic process, and generating third log information.

[0105] In an embodiment of the present application, after the diagnostic device is judged and analyzed, no abnormality is found in the working state of the diagnostic device. At this time, it is necessary to reinitialize the log information (second log information) corresponding to the diagnostic device, that is, to delete the second log information. This operation is mainly to avoid the log file from being too large and affecting the performance of the device, and to ensure the rational use of storage resources. If not cleaned up in time, a large number of historical logs will occupy the device storage space, resulting in a shortage of storage resources and may also reduce the speed of the device reading and writing new logs. After deleting the old logs, space can be made for the new logs, ensuring the efficient operation of the device storage system.

[0106] The second log information includes the operation records of the device during the historical diagnosis process, such as the start and end time of each diagnostic task, the diagnosed vehicle information, the called diagnostic function module, the data transmission record, etc.

[0107] After deleting the second log, a third log is generated, recording the diagnostic device's operations during the current diagnostic process. This log details all device operations during the diagnostic process, including communication details with the vehicle control unit, the process of acquiring and processing data, and the steps involved in generating diagnostic results. It not only provides a complete picture of the diagnostic process, supporting the results, but also preserves critical data for subsequent analysis of potential issues.

[0108] In this method, deleting the historical second log information and generating a third log information focused on the current diagnosis ensures the accuracy and timeliness of the log data. Diagnostic environments and requirements are constantly changing, and historical logs may not reflect current conditions. The newly generated third log information accurately records the latest diagnostic operations, providing a reliable basis for subsequent analysis and decision-making, thereby improving the quality and reliability of diagnostic work.

[0109] This application provides a method for recovering and tracking device anomalies. When a diagnostic device is used to report an anomaly, this method captures multiple characteristic data from the device, comprehensively and meticulously reflecting the device's operating status. This data covers all aspects of the device's operation. Analysis based on the characteristic data can accurately pinpoint the specific object where the anomaly occurred.

[0110] Once the anomaly is identified, specific recovery measures can be implemented for that object. This targeted approach quickly resolves the problem and reduces equipment downtime. Furthermore, compared to traditional methods, this approach eliminates the need to rely on third-party tools when diagnostic equipment anomalies occur, enabling prompt identification and recovery. This approach effectively recovers from anomalies, improving diagnostic equipment performance and enhancing the user experience.

[0111] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0112] Corresponding to the abnormal device recovery method in the above embodiment, Figure 5 This is a structural block diagram of the abnormal device recovery device provided in an embodiment of the present application. For the sake of convenience, only the parts related to the embodiment of the present application are shown.

[0113] Reference Figure 5 , the device 5 comprises:

[0114] The data acquisition module 51 is used to acquire a plurality of characteristic data corresponding to the diagnostic device when an abnormality occurs in the working state of the diagnostic device;

[0115] An abnormality determination module 52 is used to determine the abnormal object of the diagnostic device according to the characteristic data;

[0116] The abnormality recovery module 53 is configured to send a first instruction to the diagnostic device, so that the diagnostic device recovers the abnormal object according to the first instruction.

[0117] Optionally, the abnormality determination module 52 is further configured to:

[0118] When the characteristic data is the first identification data corresponding to the current diagnostic device, comparing the first identification data with the preset identification data;

[0119] If the first identification data is different from the preset identification data, it is determined that the abnormal object of the abnormality of the diagnostic device is the abnormality of the identification data.

[0120] Optionally, the abnormality determination module 52 is further configured to:

[0121] Determine whether the characteristic data contains configuration information corresponding to the diagnostic device; wherein the configuration information is the configuration parameters of the diagnostic device during the diagnostic function;

[0122] If the characteristic data does not completely include the configuration information corresponding to the diagnostic device, it is determined that the abnormal object of the abnormality of the diagnostic device is an information configuration abnormality.

[0123] Optionally, the abnormality recovery module 53 is further configured to:

[0124] When it is determined that the abnormal object of the diagnostic device is abnormal identification data, the first instruction is used to instruct the diagnostic device to modify the current first identification data to preset identification data.

[0125] Optionally, the abnormality recovery module 53 is further configured to:

[0126] When it is determined that the abnormal object causing the abnormality of the diagnostic device is an information configuration abnormality, the first instruction is used to instruct the diagnostic device to replace the configuration information with the configuration information corresponding to the received preset configuration file; wherein the preset configuration file is the configuration file corresponding to the diagnostic device in normal working state.

[0127] The abnormal device recovery device 5 also includes:

[0128] The abnormality tracking module 54 is used to obtain first log information corresponding to the diagnostic device after determining the abnormal object in which the diagnostic device has an abnormality; wherein the first log information includes an operation record of the diagnostic device during the diagnosis process;

[0129] Analyze the first log information to determine the cause of the abnormality of the abnormal object;

[0130] The version corresponding to the diagnostic device is updated according to the cause of the abnormality of the abnormal object.

[0131] The exception tracking module 54 is also used to:

[0132] When the working state of the diagnostic device is normal, obtaining second log information corresponding to the diagnostic device; wherein the second log information includes an operation record of the diagnostic device in a historical diagnostic process;

[0133] Delete the second log information;

[0134] Record the operation record of the diagnostic device during this diagnostic process and generate third log information.

[0135] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment section and will not be repeated here.

[0136] in addition, Figure 5 The abnormal device recovery device shown can be a software unit, a hardware unit, or a combination of software and hardware units built into an existing terminal device, or can be integrated into the terminal device as an independent hang-up, or can exist as an independent terminal device.

[0137] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0138] Figure 6 This is a schematic diagram of the structure of the terminal device provided in the embodiment of the present application. Figure 6 As shown, the terminal device 6 of this embodiment includes: at least one processor 60 ( Figure 6Only one is shown in the figure) a processor, a memory 61, and a computer program 62 stored in the memory 61 and executable on at least one processor 60. When the processor 60 executes the computer program 62, the steps in any of the above-mentioned embodiments of the abnormal device recovery method are implemented.

[0139] The terminal device can be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that Figure 6 It is only an example of the terminal device 6 and does not constitute a limitation on the terminal device 6. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0140] The processor 60 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

[0141] In some embodiments, the memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or memory of the terminal device 6. In other embodiments, the memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 6. Furthermore, the memory 61 may include both an internal storage unit of the terminal device 6 and an external storage device. The memory 61 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of a computer program. The memory 61 may also be used to temporarily store data that has been output or is about to be output.

[0142] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0143] An embodiment of the present application provides a computer program product. When the computer program product is run on a terminal device, the terminal device can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0144] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, a computer-readable medium cannot be an electric carrier signal or a telecommunication signal.

[0145] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0146] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0147] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal devices and methods can be implemented in other ways. For example, the device / terminal device embodiments described above are merely illustrative. For example, the division of modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0148] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0149] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A device abnormality recovery method, characterized in that: The method comprises: When an abnormality occurs in the working state of the diagnostic device, obtaining a plurality of characteristic data corresponding to the diagnostic device; determining an abnormal object where the diagnostic device has an abnormality according to the characteristic data; A first instruction is sent to the diagnostic device, so that the diagnostic device recovers the abnormal object according to the first instruction.

2. The device abnormality recovery method according to claim 1, characterized in that: The determining, based on the characteristic data, the abnormal object where the diagnostic device is abnormal, includes: When the characteristic data is the first identification data corresponding to the current diagnostic device, comparing the first identification data with preset identification data; If the first identification data is different from the preset identification data, it is determined that the abnormal object of the abnormality of the diagnostic device is the abnormality of the identification data.

3. The device abnormality recovery method according to claim 2, characterized in that: The sending a first instruction to the diagnostic device so that the diagnostic device recovers the abnormal object according to the first instruction includes: When it is determined that the abnormal object of the abnormality of the diagnostic device is abnormal identification data, the first instruction is used to instruct the diagnostic device to modify the current first identification data to the preset identification data.

4. The device abnormality recovery method according to claim 1, characterized in that: The determining, based on the characteristic data, the abnormal object where the diagnostic device is abnormal, includes: Determining whether the characteristic data contains configuration information corresponding to the diagnostic device; wherein the configuration information is a configuration parameter of the diagnostic device during the diagnostic function; If the characteristic data does not include the configuration information corresponding to the diagnostic device, it is determined that the abnormal object of the abnormality of the diagnostic device is an information configuration abnormality.

5. The device abnormality recovery method according to claim 4, characterized in that: The sending a first instruction to the diagnostic device so that the diagnostic device recovers the abnormal object according to the first instruction includes: When it is determined that the abnormal object causing the abnormality of the diagnostic device is an information configuration abnormality, the first instruction is used to instruct the diagnostic device to replace the configuration information with configuration information corresponding to the received preset configuration file; wherein, the preset configuration file is the configuration file corresponding to the diagnostic device in normal working state.

6. The device abnormality recovery method according to claim 1, characterized in that: The method further comprises: After determining the abnormal object in which the diagnostic device is abnormal, obtaining first log information corresponding to the diagnostic device; wherein the first log information includes an operation record of the diagnostic device during the diagnosis process; Analyze the first log information to determine the cause of the abnormality of the abnormal object; The version corresponding to the diagnostic device is updated according to the cause of the abnormality of the abnormal object.

7. The device abnormality recovery method according to claim 6, characterized in that: The method further comprises: When the working state of the diagnostic device is normal, obtaining second log information corresponding to the diagnostic device; wherein the second log information includes an operation record of the diagnostic device in a historical diagnostic process; Deleting the second log information; The operation record of the diagnostic device during the current diagnostic process is recorded to generate third log information.

8. A device abnormality recovery device, characterized in that: include: A data acquisition module, configured to acquire a plurality of characteristic data corresponding to the diagnostic device when an abnormality occurs in the working state of the diagnostic device; an abnormality determination module, configured to determine an abnormal object where the diagnostic device has an abnormality based on the characteristic data; The abnormality recovery module is used to send a first instruction to the diagnostic device, so that the diagnostic device recovers the abnormal object according to the first instruction.

9. A terminal device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images