A fault handling method and a fault handling system

Abstract

The present disclosure provides a fault handling method and a fault handling system, which relate to the technical field of terminals. When a fault occurs during the testing process, the processed fault data can be automatically uploaded to the cloud-side device. The cloud-side device can visually display the uploaded processed fault data, so that R & D personnel can more intuitively and clearly understand and analyze the fault data. The method includes: the terminal device detects a fault event and generates fault data based on the fault event; the terminal device processes the fault data to obtain the processed fault data; the terminal device sends the processed fault data to the cloud-side device through the management-side device, and the cloud-side device is used to receive and display the processed fault data.

Description

Technical Field

[0001] The present disclosure relates to the technical field of terminals, and in particular, to a fault processing method and a fault processing system. Background Art

[0002] After a terminal device is manufactured on a production line, a test application can be used to test the performance of the terminal device. If a fault occurs in the terminal device during the test, the fault needs to be recorded manually. After the recording, the recording result is fed back to the corresponding R & D personnel by using emails, communication software or other communication means inside the production line. This processing method is too inefficient, and the recording result cannot be automatically uploaded. Summary of the Invention

[0003] The present disclosure provides a fault processing method and a fault processing system. When a fault occurs during the test, the processed fault data can be automatically uploaded to a cloud-side device. The cloud-side device can visually display the uploaded processed fault data, so that R & D personnel can more intuitively and clearly understand and analyze the fault data.

[0004] To achieve the above object, the present disclosure adopts the following technical solutions:

[0005] In a first aspect, the present disclosure provides a fault processing method, including: a terminal device detects a fault event and generates fault data based on the fault event; the terminal device processes the fault data to obtain processed fault data; the terminal device sends the processed fault data to a cloud-side device through a management-side device, and the cloud-side device is configured to receive and display the processed fault data. Based on this solution, the terminal device can detect a fault event in real time and generate corresponding fault data, and send the processed fault data to the cloud-side device through the management-side device, which can effectively improve the efficiency of data collection. By receiving the processed fault data by the cloud-side device, data loss can be avoided and data integrity can be ensured. The cloud-side device can also display the processed fault data, so that R & D personnel can more intuitively and clearly understand and analyze the fault data. And due to the timely feedback of the processed fault data, R & D personnel can solve the fault problem more quickly.

[0006] In combination with the first aspect, in another possible implementation, the terminal device sends the processed fault data to the cloud device through the pipe-side device, including: the terminal device receives a data export request from the pipe-side device; the data export request is used to request the terminal device to send the processed fault data to the pipe-side device, and the data export request includes the processed fault data; in response to the data export request, the terminal device sends the processed fault data to the pipe-side device, so as to send the processed fault data to the cloud device through the pipe-side device. Based on this solution, the terminal device sending the processed fault data through the pipe-side device can, to a certain extent, ensure the security of the processed fault data. Moreover, by using the pipe-side device to send the processed fault data to the cloud device, the network advantages of the pipe-side device can be utilized to optimize the efficiency and stability of data transmission.

[0007] In combination with the first aspect, in another possible implementation, the terminal device processes the fault data to obtain the processed fault data, including: the terminal device obtains a configuration file, and the configuration file includes multiple screening conditions; the terminal device screens the fault data based on the multiple screening conditions to obtain the screened fault data; the terminal device extracts information from the screened fault data to obtain the extracted fault data; the terminal device formats the extracted fault data to obtain the processed fault data. Based on this solution, the screening and information extraction of the fault data can be realized through the multiple screening conditions in the configuration file. By formatting the fault data, the data can be converted into an easy-to-read format. In this way, the processed fault data is more convenient for querying and accessing, and at the same time, the data transmission speed is effectively improved.

[0008] In combination with the first aspect, in another possible implementation, the multiple screening conditions include a first screening condition, a second screening condition, and a third screening condition. The fault data includes multiple fault logs. Screening the fault data based on the multiple screening conditions to obtain the screened fault data includes: based on the first screening condition, determining the fault logs within the fault range in the fault data; for the fault logs within the fault range in the fault data, obtaining the sorted fault data; based on the second screening condition and the sorted fault data, determining the first screened fault log, and the first screened fault log is the fault log whose number corresponding to the same fault type within a unit time is less than or equal to the first threshold; based on the third screening condition and the first screened fault log, obtaining the second screened fault log; the total number of the second screened fault logs is less than or equal to the second threshold; the screened fault data includes the second screened fault logs. Based on this solution, screening the fault data using the configuration file can effectively reduce the entry and transmission of useless data, thereby reducing the consumption of network bandwidth and saving bandwidth time at the same time.

[0009] In combination with the first aspect, in another possible implementation, for the fault logs within the fault range in the fault data, sorted fault data is obtained, including: based on the fault occurrence time of the fault logs within the fault range, the fault logs within the fault range in the fault data are sorted to obtain the sorted fault data. Based on this solution, by sorting the fault logs within the fault range in the fault data according to the fault occurrence time of the fault logs, when the sorted fault data is subsequently applied, the most recently occurred fault log can be directly selected. In this way, it is beneficial to help R & D personnel locate and solve the problems corresponding to the faults more quickly and accurately. And the most recently occurred fault log can better help R & D personnel identify potential problems of the terminal device, so that R & D personnel can timely improve and optimize the product.

[0010] In combination with the first aspect, in another possible implementation, the fault log includes production line version information, serial number, fault occurrence time, fault type, and production line station information. An exemplary description of the fault log is provided.

[0011] In combination with the first aspect, in another possible implementation, the fault log is a compressed file. Information extraction is performed on the filtered fault data to obtain the extracted fault data, including: decompressing the filtered fault data to obtain the decompressed fault data; performing information extraction on the decompressed fault data to obtain the extracted fault data. Based on this solution, the filtered fault data can be restored in a decompressed manner to make it in a readable format. In this way, the ability to process and analyze fault data can be improved, so as to more accurately identify and understand the essence of the fault. Through the information extraction method, the most important and useful information in the fault data can be identified and extracted. It helps to more precisely locate the fault, quickly find the root cause of the problem, and take targeted solutions.

[0012] In a second aspect, an embodiment of the present disclosure provides a fault processing device, which can be applied to a terminal device and is used to implement the method in the first aspect above. The functions of the fault processing device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as a detection module, a processing module, and a sending module, etc.

[0013] Among them, the detection module is configured to detect a fault event and generate fault data based on the fault event. The processing module is configured to process the fault data to obtain the processed fault data. The sending module is configured to send the processed fault data to the cloud device through the pipe side device, and the cloud device is used to receive and display the processed fault data.

[0014] In combination with the second aspect, in a possible implementation, the fault handling device further includes a receiving module. The receiving module is configured to receive a data export request from the pipe side device; the data export request is used to request the terminal device to send the processed fault data to the pipe side device, and the data export request includes the processed fault data. The sending module is further configured to, in response to the data export request, the terminal device sends the processed fault data to the pipe side device, so as to send the processed fault data to the cloud side device through the pipe side device.

[0015] In combination with the second aspect, in a possible implementation, the fault handling device further includes an acquisition module. The acquisition module is configured to acquire a configuration file, and the configuration file includes a plurality of screening conditions. The processing module is further configured to screen the fault data based on the plurality of screening conditions to obtain the screened fault data; extract information from the screened fault data to obtain the extracted fault data; and perform formatting processing on the extracted fault data to obtain the processed fault data.

[0016] In combination with the second aspect, in a possible implementation, the plurality of screening conditions include a first screening condition, a second screening condition, and a third screening condition. The fault data includes a plurality of fault logs. The screened fault data includes the screened second fault logs. The processing module is further configured to determine the fault logs within the fault range in the fault data based on the first screening condition; obtain the sorted fault data for the fault logs within the fault range in the fault data; determine the screened first fault logs based on the second screening condition and the sorted fault data, and the screened first fault logs are the fault logs for which the number of fault logs corresponding to the same fault type within a unit time is less than or equal to a first threshold; and obtain the screened second fault logs based on the third screening condition and the screened first fault logs; the total number of the screened second fault logs is less than or equal to a second threshold.

[0017] In combination with the second aspect, in a possible implementation, the processing module is further configured to obtain the sorted fault data for the fault logs within the fault range in the fault data based on the fault occurrence time of the fault logs within the fault range.

[0018] In combination with the second aspect, in a possible implementation, the fault log includes production line version information, serial number, fault occurrence time, fault type, and production line station information.

[0019] In combination with the second aspect, in a possible implementation, the fault log is a compressed file. The processing module is further configured to perform decompression processing on the screened fault data to obtain the decompressed fault data; and extract information from the decompressed fault data to obtain the extracted fault data.

[0020] In a third aspect, the present disclosure provides a fault handling system, including: a terminal device, a pipe-side device, and a cloud-side device.

[0021] Among them, the terminal device is configured to detect a fault event, generate fault data based on the fault event, process the fault data to obtain processed fault data, and receive a data export request from the pipe-side device and, in response to the data export request, send the processed fault data to the pipe-side device. The data export request is used to request the terminal device to send the processed fault data to the pipe-side device, and the data export request includes the processed fault data. The pipe-side device is configured to send a data export request to the terminal device and receive the processed fault data and send the processed fault data to the cloud-side device. The cloud-side device is configured to receive and display the processed fault data.

[0022] In combination with the third aspect, in a possible implementation, the pipe-side device is further configured to store the processed fault data and delete or update the processed fault data at a fixed period.

[0023] In a fourth aspect, the present disclosure provides a terminal device, including: a memory, a display screen, and one or more processors; the memory and the display screen are coupled to the processor. Among them, the memory is configured to store computer program code, and the computer program code includes computer instructions. When the terminal device runs, the processor is configured to execute one or more computer instructions stored in the memory so that the terminal device executes the fault handling method according to any one of the above first aspects.

[0024] In a fifth aspect, the present disclosure provides a computer storage medium, including computer instructions, which when running on a terminal device, cause the terminal device to execute the fault handling method according to any one of the first aspects.

[0025] In a sixth aspect, the present disclosure provides a computer program product, which when running on a terminal device, causes the terminal device to execute the fault handling method according to any one of the first aspects.

[0026] In a seventh aspect, a device (for example, the device may be a chip system) is provided. The device includes a processor configured to support a first device to implement the functions involved in the above first aspect. In a possible design, the device further includes a memory configured to store necessary program instructions and data for the first device. When the device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0027] It should be understood that the beneficial effects of the above second to seventh aspects can be referred to the relevant descriptions in the above first aspect and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 Schematic diagram of the architecture of a fault handling system provided by an embodiment of the present disclosure.

[0029] Figure 2 Schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present disclosure.

[0030] Figure 3 Block diagram of the software structure of a terminal device provided by an embodiment of the present disclosure.

[0031] Figure 4 Interaction diagram of a fault handling system provided by an embodiment of the present disclosure.

[0032] Figure 5 One of the schematic flowcharts of a fault handling method provided by an embodiment of the present disclosure.

[0033] Figure 6 Schematic diagram of a station process provided by an embodiment of the present disclosure.

[0034] Figure 7 Schematic diagram of the execution logic of a terminal device, a tube-side device, and a cloud-side device provided by an embodiment of the present disclosure.

[0035] Figure 8 Another schematic flowchart of a fault handling method provided by an embodiment of the present disclosure.

[0036] Figure 9 Schematic diagram of the structure of a fault handling device provided by an embodiment of the present disclosure.

[0037] Figure 10 Schematic diagram of the structure of a fault handling system provided by an embodiment of the present disclosure. Detailed implementation manners

[0038] The following will describe the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Among them, in the description of the present disclosure, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the present disclosure is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. These three situations, where A and B can be singular or plural. Also, in the description of the present disclosure, unless otherwise specified, "a plurality of" means two or more than two. "At least one (item)" or its similar expression below refers to any combination of these items, including any combination of a single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple. Additionally, for the convenience of clearly describing the technical solutions of the embodiments of the present disclosure, in the embodiments of the present disclosure, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. Those skilled in the art can understand that the terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. do not necessarily limit being different. At the same time, in the embodiments of the present disclosure, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present disclosure should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific way for easy understanding.

[0039] In addition, the network architecture and service scenarios described in the embodiments of the present disclosure are for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present disclosure are equally applicable to similar technical problems.

[0040] The following will describe the implementation manners of this embodiment in detail with reference to the drawings.

[0041] As Figure 1As shown in the figure, it is a schematic architecture diagram of a fault handling system provided by an embodiment of the present application. The fault handling system may include a terminal device, a pipe-side device, and a cloud-side device. Among them, the terminal device may include at least one electronic device. For example, the terminal device includes mobile phone 01. The pipe-side device may also include at least one server. For example, the pipe-side device includes server 02. The cloud-side device may include at least one server. For example, the cloud-side device includes server 03. The terminal device and the pipe-side device communicate with each other through wired or wireless communication means. The pipe-side device and the cloud-side device communicate with each other through wired or wireless communication means, and the specific connection process can be determined by the user. The deployment locations of the pipe-side device and the cloud-side device are different. The deployment location of the pipe-side device is close to the terminal device, and the deployment location of the cloud-side device is far from the terminal device.

[0042] In some examples, the terminal device may also be referred to as a client device. Among them, the terminal device may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., which can install and run application programs. The present application does not impose special restrictions on the specific form of the terminal device. The pipe-side device may also be referred to as a pipe-side server. The pipe-side device may be a server within an enterprise. The cloud-side device may also be referred to as a cloud-side server. The cloud-side device may be a physical server or a server cluster of an accelerator. The cloud-side device may also be referred to as a computing node or a cloud-side computing cluster.

[0043] In the embodiment of the present application, Figure 1 taking the terminal device shown (such as mobile phone 01) as the electronic device 200 as an example, the structure of the terminal device provided by the embodiment of the present application is illustrated. As Figure 2As shown, the electronic device 200 may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.

[0044] Among them, the above-mentioned sensor module 280 may include sensors such as a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, and a bone conduction sensor.

[0045] It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200. In other embodiments, the electronic device 200 may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0046] The processor 210 may include one or more processing units. For example, the processor 210 may include an application processor (AP), a modulation and demodulation processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0047] The controller may be the nerve center and command center of the electronic device 200. The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

[0048] A memory can also be set in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can save the instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0049] In some embodiments, the processor 210 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0050] It can be understood that the interface connection relationship between the modules illustrated in this embodiment is only for illustrative purposes and does not constitute a structural limitation on the electronic device 200. In some other embodiments, the electronic device 200 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0051] The charging management module 240 is configured to receive a charging input from a charger. The charger can be a wireless charger or a wired charger. While charging the battery 242, the charging management module 240 can also supply power to the electronic device through the power management module 241.

[0052] The power management module 241 is used to connect the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives the inputs from the battery 242 and / or the charging management module 240 and supplies power to the processor 210, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260, etc. In some embodiments, the power management module 241 and the charging management module 240 may also be provided in the same device.

[0053] The wireless communication function of the electronic device 200 can be implemented by antenna 1, antenna 2, the mobile communication module 250, the wireless communication module 260, the modulation and demodulation processor, and the baseband processor, etc. In some embodiments, antenna 1 of the electronic device 200 is coupled to the mobile communication module 250, and antenna 2 is coupled to the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technologies.

[0054] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 200 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, antenna 1 can be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0055] The mobile communication module 250 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc. applied to the electronic device 200. The mobile communication module 250 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 250 can receive electromagnetic waves through antenna 1, and perform filtering, amplification and other processing on the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation.

[0056] The mobile communication module 250 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves through antenna 1 and radiate it out. In some embodiments, at least some functional modules of the mobile communication module 250 can be disposed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 can be disposed in the same device.

[0057] The wireless communication module 260 can provide solutions for wireless communications including WLAN (such as (wireless fidelity, Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied to the electronic device 200.

[0058] The wireless communication module 260 may be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 260 may also receive the signals to be sent from the processor 210, perform frequency modulation on them, amplify them, and convert them into electromagnetic waves through the antenna 2 for radiation.

[0059] The electronic device 200 realizes the display function through the GPU, the display screen 294, the application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 294 and the application processor. The GPU is used to execute mathematical and geometric calculations for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or change the display information.

[0060] The display screen 294 is used to display images, videos, etc. The display screen 294 includes a display panel.

[0061] The electronic device 200 can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294, the application processor, etc. The ISP is used to process the data fed back by the camera 293. The camera 293 is used to capture static images or videos. In some embodiments, the electronic device 200 may include one or N cameras 293, where N is a positive integer greater than 1.

[0062] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to achieve the data storage function. For example, files such as music and videos are saved in the external memory card.

[0063] The internal memory 221 can be used to store computer-executable program codes, and the executable program codes include instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by running the instructions stored in the internal memory 221. For example, in the embodiments of the present application, the processor 210 can execute the instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.

[0064] Among them, the storage program area can store the operating system, application programs required for at least one function (such as the sound playback function, image playback function, etc.), and so on. The storage data area can store the data created during the use of the electronic device 200 (such as audio data, phone book, etc.), and so on. In addition, the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0065] The electronic device 200 can implement audio functions through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the headphone jack 270D, and the application processor, etc. Such as music playback, recording, etc.

[0066] The keys 290 include a power-on key, volume keys, etc. The keys 290 can be mechanical keys or touch keys. The motor 291 can generate a vibration prompt. The motor 291 can be used for incoming call vibration prompts and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging state, the change in battery power, and can also be used to indicate messages, missed calls, notifications, etc. The SIM card interface 295 is used to connect the SIM card. The SIM card can be in contact with and separated from the electronic device 200 by inserting or removing it from the SIM card interface 295. The electronic device 200 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.

[0067] The software system of the above-mentioned electronic device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiments of the present invention, taking the system of the layered architecture as an example, the software structure of the electronic device is exemplarily described.

[0068] Figure 3 is the software structure block diagram of the electronic device provided by the embodiments of the present application.

[0069] The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely the application layer, the application framework layer, the Android runtime and the system library (which can also be called the Native layer), and the kernel layer.

[0070] The application layer may include a series of application packages. Such as Figure 3As shown, the application package may include applications such as camera, gallery, calendar, phone, map, navigation, WLAN, Bluetooth, music, video, short message, etc. The application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application framework layer includes some predefined functions. It can be understood that the application layer may include multiple applications, and the types of these multiple applications may be the same or different.

[0071] As Figure 3 shown, the application framework layer may include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0072] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0073] The content provider is used to store and obtain data, and make these data accessible to applications.

[0074] The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build applications. The display interface can be composed of one or more views. For example, the display interface including a short message notification icon may include a view for displaying text and a view for displaying pictures.

[0075] The phone manager is used to provide the communication function of the terminal device. For example, the management of call status (including answering, hanging up, etc.).

[0076] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0077] The notification manager enables applications to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short stay without user interaction. For example, the notification manager is used to inform that the download is completed, message reminder, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as the notification of a background-running application, and can also be a notification that appears on the screen in the form of a dialogue window. For example, prompt text information in the status bar, emit a prompt sound, the terminal device vibrates, the indicator light flashes, etc.

[0078] The Android runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system.

[0079] The core library consists of two parts: one is the functional functions that the Java language needs to call, and the other is the core library.

[0080] The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files in the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as management of object life cycles, stack management, thread management, security and exception management, and garbage collection.

[0081] The system library can include multiple functional modules. For example: surface manager, Media Libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0082] The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

[0083] The media library supports the playback and recording of multiple common audio and video formats, as well as static image files, etc. The media library can support multiple audio and video coding formats.

[0084] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc.

[0085] The 2D graphics engine is a graphics engine for 2D drawing.

[0086] The kernel layer is the layer between the hardware and the software. The kernel layer at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0087] The methods in the following embodiments can all be implemented in a terminal device having the above hardware structure or software structure.

[0088] In some examples, in order to implement a fault handling method provided in an embodiment of the present application, based on the software structure block diagram of the terminal device shown in Figure 3 as shown in Figure 4 the application layer of the terminal device further includes an automatic test application (i.e., Autotest APP), a man-machine interface application (i.e., MMI APP), and an aging application, etc.

[0089] Among them, the automatic test application is used to test the functions supported by the terminal device. The human-machine interface application is used to provide an interface between the user and the terminal device, enabling the user to interact with the terminal device through the screen, buttons, touchpad, etc. of the terminal device. The aging application is a software tool used to test and simulate the aging problems that may occur during the use of the terminal device. Its main function is to simulate the terminal device during long-term use and evaluate the stability, reliability, and performance of the terminal device under various conditions. During the aging test process, the aging application can also detect whether the terminal device or system has an anomaly or fault that matches the keyword, and interrupt the test in a timely manner when an anomaly or fault occurs to avoid further damage or problems.

[0090] The native layer of the terminal device also includes a data monitor daemon (DMD), a Hiview service, and a Factory monitor daemon (FMD). Among them, DMD is used to perform fault printing and generate a fault print file. The fault print file can also be called a DMD file. Usually, the DMD application is in a commercial way. The Hiview service can be used to generate fault data during the test process; it can also be used to collect production data and perform packet processing and adaptation processing on the collected production data. Exemplarily, the fault data can be used in the terminal device and the network management device in the form of a hiview file.

[0091] FMD is used to process and convert the fault data. For example, FMD encapsulates the calibration parameters of various devices into a specific format and saves them in a relevant file. FMD converts the event information to adapt to a specific transmission or storage method, thereby ensuring the integrity and readability of the event information. FMD controls the upload process and speed of the data to ensure the integrity and accuracy of the uploaded data. Usually, after processing and converting the fault information, FMD can generate a formatted file. The formatted file can be the processed fault data. The formatted file can be recognized by the network management device.

[0092] Such as Figure 4As shown, the tube-side device may include multiple functional modules, such as: a trigger module, a data export module, a conversion module, a generation module, and an upload module. Among them, the data export module is used to send a data export request to the terminal device to export the processed fault data through the data export request. The trigger module is used to trigger the formatted conversion of the processed fault data. The conversion module is used to perform a formatted conversion on the processed fault data to obtain a converted file. For example, performing a formatted conversion on the processed fault data may be to convert and splice the field information in the processed fault data to obtain a converted file, and the converted file may be called a resul file. The generation module is used to generate a database file according to the converted file. For example, the file format of the database file is an mdb file. The upload module is used to upload the database file to the cloud-side device.

[0093] As Figure 4 shown, the cloud-side device may include multiple functional modules, such as: a database, a data analysis system, a data lake, and a display module. Among them, the database is used to receive the database file and store and manage the database file. Exemplarily, the database in the cloud-side device may be a Hummer database. The data analysis system is used to perform data analysis and mining on the database file according to the database file in the database and display the data analysis and mining results. Exemplarily, the data analysis system in the cloud-side device may be a Hummer data analysis system. The data lake (which can also be called the system data base) is a platform for storing and processing a large amount of data. The data lake may have multiple data processing functions, such as: data extraction, data conversion, data loading, and data query, etc. The database may upload the database file to the data lake when receiving the database file. The database may also periodically upload the database file to the data lake.

[0094] The display module can be used to display the manufacturing hardware fault analysis website and the R & D website. Specifically, the manufacturing hardware fault analysis website can extract the database file from the data lake and parse the database file to obtain a parsed file. Then, various functions are implemented using the parsed file. For example, functions such as fault expansion service, station status analysis, station time analysis, station result distribution analysis, and test item and time matrix analysis are implemented. The manufacturing hardware fault analysis website can also display other data related to hardware faults. In addition, the manufacturing hardware fault analysis website has also added a filtering and isolation mechanism. In this way, the accuracy and reliability of the data can be improved, and invalid or interfering data can be filtered out. To ensure the independence and isolation of data between different users and protect the security and privacy of the data.

[0095] The R & D website can also extract database files from the data lake, parse the database files, and obtain the parsed files. Then, various functions can be implemented using the parsed files. For example, functions such as data summarization, data analysis, interface display, and algorithm and threshold correction can be implemented. The interface display function can be used to display the faults occurring at the workstations on the production line. R & D personnel can quickly determine the cause of the fault based on the faults displayed on the interface.

[0096] Next, based on Figure 4 the interactive schematic diagram of the fault handling system shown, in combination with Figure 5 the fault handling method provided by the embodiments of the present disclosure will be schematically described. This method can be applied to the above-mentioned fault handling system. Taking the terminal device in the fault handling system as a mobile phone as an example, as Figure 5 shown, this data processing method can include the following steps 501 - step 519.

[0097] Step 501, when the test application in the mobile phone detects a fault, view the service (Hiview service) to generate fault data.

[0098] Among them, the fault data is used to record the faults that occur in the mobile phone during the test. The fault data includes multiple fault logs. One fault log corresponds to one fault information.

[0099] In some examples, each of the multiple fault logs can be a compressed file. One fault log can include multiple log information.

[0100] Exemplarily, the log information includes production line version information, serial number, fault occurrence time, fault point, and production line workstation information, etc. Among them, the production line version information refers to the version information of the mobile phone on the production line. The production line version information can be used to indicate on which production line and which batch the mobile phone was tested. The fault point is used to characterize the specific location or module where the problem occurred during the production line workstation test of the mobile phone. The fault point can be a certain function, a certain component, a certain algorithm, etc. in the software, or a certain chip, a certain sensor, etc. in the hardware. The fault point can also be represented in the form of a fault type. The production line workstation information is used to characterize at which workstation the fault occurred.

[0101] To facilitate R & D personnel in quickly understanding the key information of each fault log, the key information of each fault log can be displayed on the name of the compressed file corresponding to the fault log. Exemplarily, the name of the compressed file corresponding to the fault log may include: the model and network mode information of the mobile phone, the production line version information, the encrypted serial number (SN), the fault occurrence time, the fault type, and the production line station information, etc. For example, the model and network mode information of the mobile phone are Honor Magic Vs2 and TD-LTE. The production line version information is FMN-AN00-BD 1.0.0.19. The encrypted SN is Q972tghNQ2+R51JE4z29HVPlrzegOXCRq4yrMb4tMQ0=. The fault occurrence time is 20230810160754. The fault type is 901000002. The production line station information is RT.

[0102] When a production line produces an electronic product, the performance of the electronic product is usually tested, and only the electronic products that pass the performance test can enter the trading market for users to choose.

[0103] Generally, when producing electronic products, the production line will include multiple station processes. Exemplarily, the electronic product is a mobile phone, as Figure 6 shown, the station processes corresponding to the production line of the mobile phone at least include: Download Barcode Calibration (DBC), Calibration Board Test (CBT), Man-Machine interface (MMI), RUNIN_OFFLINE (RT), automated man-machine interface test, Customer information Write (CW), and Mobile Check (MC), etc.

[0104] Among them, the DBC station is used to execute the loading of the burning software and the functional test of the baseband circuit. The CBT is used to calibrate various radio frequency indicators of the mobile phone single board (such as transmit power, frequency error, phase error, power ramp, modulation spectrum, etc.), and perform tests after calibration. The MMI is used to check functions such as the product's TPLCD, camera, audio, and sensor on the human-computer interaction interface. The RT is used to apply corresponding stresses to the product to convert potentially defective products into obvious defective products. Defects triggered are eliminated through functional inspection, thereby reducing the defect ratio of the product and ensuring the quality of a large number of products shipped. The automated MMI test can be achieved through the 9100 device. The CW is used to write customer information. The MC is used to perform checks on the consistency of the physical number, country information, operator information, software version, battery power, etc., and perform a factory reset on the mobile phone.

[0105] When manufacturing a mobile phone based on the above station processes, each station process may malfunction. Therefore, after manufacturing the mobile phone, as Figure 7 shown, the test application can issue test instructions to test multiple functions supported by the mobile phone using the test instructions, thereby ensuring the performance of the mobile phone.

[0106] Exemplarily, the multiple functions supported by the mobile phone can include stability, performance, power consumption and heat, communication, devices, application services, log engine, Wireless Fidelity (wifi), Global Positioning System (GPS), fingerprint, Bluetooth, file system, Near Field Communication (NFC), and audio, etc.

[0107] When testing the multiple functions supported by the above mobile phone, Figure 7 the View Service (Hiview Service) can generate fault data. This fault data may involve data in multiple aspects, such as log package data, device dot data, device capacitance value data, fault website data, dump data, and captured script data, etc. The Hiview Service can also have other functions, such as format conversion, parameter collection, instruction export, output of other solutions, etc.

[0108] In addition, as Figure 7 shown, the mobile phone also includes an acquisition module, which is used to acquire production data generated during the production process.

[0109] In some examples, when a test application in a mobile phone conducts a stability test on the mobile phone, if the mobile phone malfunctions, the mobile phone will display a data dump interface. When the R & D personnel find that the mobile phone displays the dump interface, they will perform a restart operation on the mobile phone.

[0110] When using a test application to conduct a stability test on a mobile phone, if the mobile phone malfunctions, the malfunction generally occurs in multiple scenarios. For example, restart scenarios, application scenarios, resource scenarios, black screen and frozen screen scenarios, and non-booting scenarios, etc.

[0111] In different scenarios, fault logs of different fault types can be represented by different digital codes. Exemplarily, the restart scenario involves multiple different types of fault logs, and multiple different types of fault logs can be represented by digital codes such as 901000000, 901000001, 901000002, 901000003, 901000004, 901000005, 901000006, 901000007, 901000008, 901000009, and 901000010.

[0112] Among them, the fault type of the fault log corresponding to 901000000 is the Android SystemServer process error restart (i.e., Android Vmreboot). The fault type of the fault log corresponding to 901000001 is the Android SystemServer blocked restart (i.e., Vm Watchdog), the fault type of the fault log corresponding to 901000002 is the whole machine crashing (including hungtask120s, etc.) (i.e., Panic), the fault type of the fault log corresponding to 901000003 is the driver layer watchdog reset (i.e., HwWatchdog), the fault type of the fault log corresponding to 901000004 is the unrecognized fault (i.e., Unknown Fault), the fault type of the fault log corresponding to 901000005 is the hardware exception (i.e., Hardware Fault), the fault type of the fault log corresponding to 901000006 is the bootloader exception (i.e., Bootloader Crash), the fault type of the fault log corresponding to 901000007 is the lpm3 exception (i.e., Lpm3 Exception), the fault type of the fault log corresponding to 901000008 is the security subsystem whole machine restart (i.e., Trustzone Rebootsys), the fault type of the fault log corresponding to 901000009 is the modem subsystem whole machine restart (i.e., Modem Rebootsys), and the fault type of the fault log corresponding to 901000010 is the Press10s restart (i.e., Press10s Reset).

[0113] The application scenario also involves multiple different types of faults, and multiple different types of faults can be represented by digital codes such as 901001000, 901001001, and 901001002.

[0114] Among them, the fault type of the fault log corresponding to 901001000 is that the pre-loaded application is unresponsive (i.e., Pre-loaded Application ANR). The fault type of the fault log corresponding to 901001001 is that the pre-loaded application crashes (i.e., Pre-loaded Application Crash). The fault type of the fault log corresponding to 901001002 is that the pre-loaded program process Tombstone (i.e., Pre-loaded Application Tomestone).

[0115] The resource scenario also involves multiple different types of faults, and multiple different types of faults can be represented by digital codes such as 901003000, 901003001, and 901003023.

[0116] Among them, the fault type of the fault log corresponding to 901003000 is process thread leakage (i.e., Thread Limit). The fault type of the fault log corresponding to 901003001 is process file handle leakage (i.e., File Handler Limit). The fault type of the fault log corresponding to 901003023 is memory growth exceeding the limit (i.e., Memory Increase).

[0117] The black screen and frozen screen scenario also involves multiple different types of faults, and multiple different types of faults can be represented by digital codes such as 901004000, 901004003, and 901004005.

[0118] Among them, the fault type of the fault log corresponding to 901004000 is system frozen screen fault (i.e., System HungFault). The fault type of the fault log corresponding to 901004003 is service stuck (i.e., Service Die). The fault type of the fault log corresponding to 901004005 is application stuck detection (i.e., App Freeze).

[0119] The fault involved in the non-booting scenario is 901005000. The fault type of the fault log corresponding to 901005000 is non-booting fault (i.e., Boot Fail Error).

[0120] It is understandable that the above-mentioned fault types are only examples, and the faults involved in the mobile phone are not limited to the above-mentioned faults. Specifically, it shall be subject to the actual application, and the present disclosure does not make any restrictions thereon.

[0121] In some examples, the mobile phone can receive a function test instruction sent by the device on the tube side. The mobile phone can respond to the function test instruction and call a test application to test multiple functions in the mobile phone. During the process of the test application testing the mobile phone, the Hiview service will generate fault data.

[0122] In some examples, during the process of the test application in the mobile phone testing the mobile phone, the Hiview service detects a fault event and generates fault data based on the fault event. Wherein, the fault event refers to a fault or unexpected situation that occurs during the process of the test application testing the mobile phone.

[0123] In some examples, when the test application detects the occurrence of a fault, the process of the Hiview service generating fault data may include: the test application obtains the performance information of the mobile phone and tests the mobile phone based on the performance information of the mobile phone. During the test process, the test application can generate log information based on the entire test process and write the log information into the system log. The log information includes the fault events that occur during the test process.

[0124] The Hiview service includes a monitoring API. The Hiview service can use the monitoring API to monitor the operations of the test application and the log information generated by the test application. When the Hiview service monitors a fault event in the log information, the Hiview service can register a callback function, use the callback function to receive the log information written by the test application, and generate fault data based on the log information.

[0125] For example, during the test process, when the test application detects that the mobile phone has a stability problem, the mobile phone will display a dump interface. The test application will generate log information based on the stability problem and write the log information into the system log. When the R & D personnel find that the mobile phone displays a dump interface, the R & D personnel will perform a restart operation on the mobile phone. Since the monitoring API is included in the Hiview service, the Hiview service can use the monitoring API to monitor the operations of the test application and the mobile phone. When the Hiview service monitors that the mobile phone displays a dump interface, the mobile phone performs a restart operation, and the test application writes log information into the system log, the Hiview service will generate fault data according to the log information written by the test application.

[0126] It should be noted that the size of the fault data generated by the Hiview service is related to the size of the memory (buffer) storing the log information in the system log. The larger the memory for storing the log information, the more fault data generated by the Hiview service. The smaller the memory for storing the log information, the less fault data generated by the Hiview service.

[0127] Step 502: The in-pipe device sends a first notification to the instruction processing module in the mobile phone.

[0128] Among them, the first notification can also be called a data export request, which is used to request the terminal device to send the processed fault data to the in-pipe device. The data export request includes the processed fault data.

[0129] In some examples, when the test application in the mobile phone conducts a stability test on the mobile phone, if the mobile phone fails, the R & D personnel will perform a restart operation on the mobile phone and connect the mobile phone to the in-pipe device. After the connection between the mobile phone and the in-pipe device is successful, the in-pipe device can send a first notification to the instruction processing module in the mobile phone to notify the instruction processing module to export the processed fault data in the mobile phone. Exemplarily, the in-pipe device can be equipped at the aging (Burn In, BI) station in the production line. During the test, if the mobile phone fails, the R & D personnel can take the mobile phone to the BI station and connect the mobile phone to the in-pipe device (for example, Figure 7 the server shown) in the BI station.

[0130] Step 504: The instruction processing module in the mobile phone receives the first notification.

[0131] Step 505: In response to the first notification, the instruction processing module in the mobile phone obtains the configuration file and sends a second notification to the Hiview service.

[0132] Among them, the second notification is used to request to obtain the fault data.

[0133] After receiving the first notification, the instruction processing module in the mobile phone can obtain the configuration file and send a second notification to the Hiview service to obtain the fault data generated by the Hiview service. Then, the processed fault data can be generated using the configuration file and the fault data, and the processed fault data can be sent to the in-pipe device.

[0134] In some examples, the instruction processing module in the mobile phone can obtain the configuration file through multiple ways, for example, the instruction processing module obtains the configuration file from a preset address. Specifically, the configuration file can be a software version that comes with the mobile phone operating system. The configuration file is part of the software version. During the software version production stage, the configuration file is included in the software version. When the software version is installed on the mobile phone, the configuration file is also stored in a specific directory of the mobile phone. The configuration file may include settings and screening rules related to the processed fault data.

[0135] The configuration file includes multiple screening rules. The multiple screening rules may include a first screening rule, a second screening rule and a third screening rule. The first screening rule is used to limit the fault range, and the fault range includes at least one fault type. The second screening rule is used to limit the number of fault logs corresponding to the same fault type within a unit time. The third screening rule is used to limit the number of all fault logs within the fault range.

[0136] Exemplarily, the second screening rule is specifically used to limit the number of fault logs corresponding to the same fault type within a unit time to be less than or equal to the first threshold. The third screening rule is specifically used to limit the total number of all fault logs within the fault range to be less than or equal to the second threshold.

[0137] For example, the fault range defined by the first screening rule includes the fault log corresponding to the fault type 901000000, the fault log corresponding to the fault type 901000001, and the fault log corresponding to the fault type 901000002.

[0138] The unit time can be 1 minute. The second screening rule defines that within a unit time, the number of fault logs corresponding to fault type 901000000 is less than or equal to 5. Within a unit time, the number of fault logs corresponding to fault type 901000001 is less than or equal to 3. Within a unit time, the number of fault logs corresponding to fault type 901000002 is less than or equal to 1.

[0139] The third screening rule is limited to the fault range, and the total number of fault logs corresponding to fault type 901000000, fault logs corresponding to fault type 901000001, and fault logs corresponding to fault type 901000002 is less than or equal to 10.

[0140] It is understandable that the above-mentioned first screening rule, second screening rule and third screening rule are only examples. In different usage scenarios, the first screening rule, second screening rule and third screening rule may correspond to other contents, and the present disclosure does not limit this.

[0141] Step 505: The hiview service in the mobile phone receives the second notification.

[0142] Step 506: In response to the second notification, the hiview service in the mobile phone sends the fault data to the instruction processing module in the mobile phone.

[0143] After receiving the second notification, the hiview service in the mobile phone can, in response to the second notification, send the fault data to the instruction processing module in the mobile phone, so that the instruction processing module generates processed fault data based on the fault data.

[0144] Step 507: The instruction processing module in the mobile phone receives the fault data.

[0145] Step 508: The instruction processing module in the mobile phone determines whether the fault logs in the fault data are within the fault range based on the first screening condition in the configuration file.

[0146] After the instruction processing module in the mobile phone obtains the fault data from the hiview service, it can screen out the fault logs corresponding to other fault types that are not within the fault range based on the first screening rule in the configuration file, so that the fault types corresponding to the screened fault logs are all within the fault range.

[0147] In some examples, determining whether the fault logs in the fault data are within the fault range can be: first, determine at least one fault type included in the fault range. Then, compare the fault type corresponding to each fault log in the fault data with the at least one fault type within the fault range. If the fault type corresponding to the fault log is the same as the at least one fault type within the fault range, it is considered that the fault log is within the fault range. If the fault type corresponding to the fault log is not the same as any of the at least one fault type within the fault range, it is considered that the fault log is not within the fault range.

[0148] For example, the at least one fault type included in the fault range is 901000000, 901000001, and 901000002. The fault data includes multiple fault logs. The multiple fault logs are respectively fault log 1, fault log 2, fault log 3, fault log 4, fault log 5, fault log 6, fault log 7, fault log 8, fault log 9, fault log 10, fault log 11, fault log 12, fault log 13, fault log 14, and fault log 15. Among them, the fault types corresponding to fault log 1, fault log 2, fault log 4, fault log 5, fault log 7, fault log 10, and fault log 11 are 901000000. The fault types corresponding to fault log 3, fault log 6, and fault log 12 are 901000001. The fault types corresponding to fault log 8, fault log 9, fault log 13, and fault log 14 are 901000002. The fault type corresponding to fault log 15 is 901005000.

[0149] After determining the types of faults within the fault range and the types of faults corresponding to multiple fault logs, each fault log's corresponding fault type in the multiple fault logs is then compared with the fault types within the fault range. Finally, based on the comparison results between each fault log's corresponding fault type and the fault types within the fault range, it is determined whether the fault logs in the fault data are within the fault range. Through comparison, it can be seen that fault log 1, fault log 2, fault log 3, fault log 4, fault log 5, fault log 6, fault log 7, fault log 8, fault log 9, fault log 10, fault log 11, fault log 12, fault log 13, and fault log 14 are within the fault range, while fault log 15 is not within the fault range.

[0150] Step 509: When it is determined that there are no fault logs within the fault range in the fault data, the process ends.

[0151] When it is determined that none of the fault logs in the fault data are within the fault range, it means that the fault data does not need to be uploaded to the pipe-side device, so the process ends.

[0152] Step 510: When it is determined that there are fault logs within the fault range in the fault data, the instruction processing module in the mobile phone sorts the fault logs within the fault range to obtain the sorted fault data.

[0153] When it is determined that there are fault logs within the fault range in the fault data, since the fault logs need to be further filtered according to the second filtering rule and the third filtering rule later, the fault logs within the fault range can be sorted to facilitate filtering the sorted fault data using the second filtering rule and the third filtering rule later, thereby improving the filtering efficiency.

[0154] In some examples, the instruction processing module in the mobile phone sorts the fault logs within the fault range to obtain the sorted fault data, which can be: the instruction processing module sorts the fault logs within the fault range according to the fault occurrence time of each fault log in the fault data to obtain the sorted fault data.

[0155] Since the instruction processing module sorts the fault logs within the fault range according to the fault occurrence time, when subsequently screening the fault logs within the fault range using the second and third screening rules, the most recently occurred fault logs can be screened based on the sorted fault data. This helps the R & D personnel to more quickly and accurately locate and solve the problems corresponding to the faults. Moreover, the most recently occurred fault logs can better help the R & D personnel identify potential problems of the terminal device, enabling the R & D personnel to improve and optimize the product in a timely manner.

[0156] For example, the fault logs within the fault range are Fault Log 1, Fault Log 2, Fault Log 3, Fault Log 4, Fault Log 5, Fault Log 6, Fault Log 7, Fault Log 8, Fault Log 9, Fault Log 10, Fault Log 11, Fault Log 12, Fault Log 13, and Fault Log 14 respectively.

[0157] Among them, the fault occurrence time of Fault Log 1 is 9:01:10, the fault occurrence time of Fault Log 2 is 9:01:35, the fault occurrence time of Fault Log 3 is 9:01:24, the fault occurrence time of Fault Log 4 is 9:01:44, the fault occurrence time of Fault Log 5 is 8:59:00, the fault occurrence time of Fault Log 6 is 9:02:11, the fault occurrence time of Fault Log 7 is 8:59:05, the fault occurrence time of Fault Log 8 is 9:04:20, the fault occurrence time of Fault Log 9 is 9:01:07, the fault occurrence time of Fault Log 10 is 9:02:12, the fault occurrence time of Fault Log 11 is 8:59:15, the fault occurrence time of Fault Log 12 is 9:05:22, the fault occurrence time of Fault Log 13 is 8:59:23, and the fault occurrence time of Fault Log 14 is 9:01:01.

[0158] Based on the chronological order of the fault occurrence times of multiple fault logs in the fault data, the above multiple fault logs are sorted. The sorted fault data is: Fault Log 5, Fault Log 7, Fault Log 11, Fault Log 13, Fault Log 14, Fault Log 9, Fault Log 1, Fault Log 3, Fault Log 2, Fault Log 4, Fault Log 6, Fault Log 10, Fault Log 8, Fault Log 12.

[0159] Step 511: The instruction processing module in the mobile phone screens the sorted fault data based on the sorted fault data and the second screening rule in the configuration file to obtain the first screened fault data.

[0160] After obtaining the sorted fault data, the instruction processing module in the mobile phone can screen the sorted fault data based on the second screening rule in the configuration file to obtain the first screened fault data.

[0161] In some examples, since the second screening rule is used to limit that the number of fault logs corresponding to the same fault type within a unit time is less than or equal to the first threshold. Therefore, when screening the sorted fault data based on the second screening rule, at least one fault log corresponding to the same fault type can be determined first. Then, based on the fault occurrence times of the at least one fault log, the total number of the at least one fault log within a unit time can be determined. Next, compare the total number of the at least one fault log within a unit time with the first threshold. If the total number of the at least one fault log within a unit time is less than or equal to the first threshold, the first screened fault data includes the at least one fault log. If the total number of the at least one fault log within a unit time is greater than the first threshold, according to the sorted fault data, the first screened fault data includes the fault logs ranked later among the at least one fault log, and the total number of the fault logs ranked later among the at least one fault log is equal to the first threshold.

[0162] For example, when screening the sorted fault data based on the second screening rule, at least one fault log corresponding to the same fault type can be determined first. Combining with step 508, the at least one fault log corresponding to the fault type 901000000 is: fault log 1, fault log 2, fault log 4, fault log 5, fault log 7, fault log 10, and fault log 11. The at least one fault log corresponding to the fault type 901000001 is: fault log 3, fault log 6, and fault log 12. The at least one fault log corresponding to the fault type 901000002 is: fault log 8, fault log 9, fault log 13, and fault log 14.

[0163] For the at least one fault log corresponding to the fault type 901000000, based on the fault occurrence times of fault log 1, fault log 2, fault log 4, fault log 5, fault log 7, fault log 10, and fault log 11, combining with step 510, the fault occurrence time of fault log 1 is 9:01:10, the fault occurrence time of fault log 2 is 9:01:35, the fault occurrence time of fault log 4 is 9:01:44, the fault occurrence time of fault log 5 is 8:59:00, the fault occurrence time of fault log 7 is 8:59:05, the fault occurrence time of fault log 10 is 9:02:12, and the fault occurrence time of fault log 11 is 8:59:15. Therefore, within a unit time (i.e., 1 minute), that is, the total number of fault logs within 9:01 is 3. The total number of fault logs within 8:59 is 3. The total number of fault logs within 9:02 is 1.

[0164] Combined with step 504, it can be seen that within a unit of time, the number of fault logs corresponding to the fault type 901000000 is less than or equal to 5. Since the total number of at least one fault log within a unit of time is less than 5, the first filtered fault data includes fault log 1, fault log 2, fault log 4, fault log 5, fault log 7, fault log 10, and fault log 11.

[0165] For at least one fault log corresponding to the fault type 901000001, based on the fault occurrence times of fault log 3, fault log 6, and fault log 12, combined with step 510, it can be seen that the fault occurrence time of fault log 3 is 9:01:24, the fault occurrence time of fault log 6 is 9:02:11, the fault occurrence time of fault log 4 is 9:01:44, the fault occurrence time of fault log 5 is 8:59:00, and the fault occurrence time of fault log 12 is 9:05:22. Therefore, within a unit of time, that is, within 9:01, the total number of fault logs is 1. Within 9:02, the total number of fault logs is 1. Within 9:05, the total number of fault logs is 1.

[0166] Combined with step 504, it can be seen that within a unit of time, the number of fault logs corresponding to the fault type 901000001 is less than or equal to 3. Since the total number of at least one fault log within a unit of time is less than 3, the first filtered fault data includes fault log 3, fault log 6, and fault log 12.

[0167] For at least one fault log corresponding to the fault type 901000002, based on the fault occurrence times of fault log 8, fault log 9, fault log 13, and fault log 14, combined with step 510, it can be seen that the fault occurrence time of fault log 8 is 9:04:20, the fault occurrence time of fault log 9 is 9:01:07, the fault occurrence time of fault log 13 is 8:59:23, and the fault occurrence time of fault log 14 is 9:01:01. Therefore, within a unit of time, that is, within 8:59, the total number of fault logs is 1. Within 9:01, the total number of fault logs is 2. Within 9:04, the total number of fault logs is 1.

[0168] Combined with step 504, it can be seen that within a unit of time, the number of fault logs corresponding to the fault type 901000002 is less than or equal to 1. Since the total number of fault logs at 9:01 is 2 which is greater than 1, according to the sorted fault data in step 510, among the fault logs 9 and 14 corresponding to 9:01, the fault log 9 is ranked later. Combining with the fact that within a unit of time, the number of fault logs corresponding to the fault type 901000002 is less than or equal to 1, the first filtered fault data includes the fault log 9. In addition, since the total number of fault logs at 8:59 and the total number of fault logs at 9:04 are both equal to 1, the first filtered fault data also includes the fault log 8 and the fault log 13.

[0169] Therefore, the first filtered fault data includes: fault log 1, fault log 2, fault log 4, fault log 5, fault log 7, fault log 10, fault log 11, fault log 3, fault log 6, fault log 12, fault log 9, fault log 8 and fault log 13.

[0170] Step 512: The instruction processing module in the mobile phone filters the first filtered fault data based on the third filtering rule in the configuration file to obtain the second filtered fault data.

[0171] After obtaining the sorted fault data, the instruction processing module in the mobile phone can filter the first filtered fault data based on the third filtering rule in the configuration file to obtain the second filtered fault data.

[0172] In some examples, since the third filtering rule is used to limit that the total number of all fault logs within the fault range is less than or equal to the second threshold. Therefore, when filtering the first filtered fault data based on the third filtering rule, the total number of the first filtered fault data can be determined first. Then compare the total number of the first filtered fault data with the second threshold. If the total number of the first filtered fault data is less than or equal to the second threshold, the second filtered fault data is the first filtered fault data. If the total number of the first filtered fault data is greater than the second threshold, according to the sorted fault data, the second filtered fault data is the fault logs ranked later in the first filtered fault data, and the total number of the fault logs ranked later in the first filtered fault data is equal to the second threshold.

[0173] For example, as can be seen from step 511, the total number of the first filtered fault data is 13. As can be seen from step 504, the third filtering rule defines that within the fault range, the total number of the fault logs corresponding to the fault type 901000000, the fault logs corresponding to the fault type 901000001, and the fault logs corresponding to the fault type 901000002 is less than or equal to 10. By comparing the total number of the first filtered fault data with the second threshold, it can be seen that the total number 13 of the first filtered fault data is greater than the second threshold 10.

[0174] According to the sorted fault data in step 510, since the second filtered fault data includes the fault logs at the later positions in the first filtered fault data, and the total number of the fault logs at the later positions in the first filtered fault data is equal to the second threshold, the second filtered fault data is: fault log 13, fault log 9, fault log 1, fault log 3, fault log 2, fault log 4, fault log 6, fault log 10, fault log 8, and fault log 12.

[0175] Therefore, the present disclosure can use the first filtering rule, the second filtering rule, and the third filtering rule in the configuration file to filter the fault data, so as to obtain the filtered fault data. Filtering the fault data by using the configuration file can effectively reduce the entry and transmission of useless data, thereby reducing the consumption of network bandwidth and saving bandwidth time at the same time.

[0176] In step 513, the instruction processing module in the mobile phone performs decompression processing on the second filtered fault data to obtain the decompressed fault data.

[0177] In some examples, as can be seen from step 501, the fault data generated by the hiview service includes multiple fault logs, and each fault log in the multiple fault logs can be a compressed file. And the name of each compressed file includes information such as the model and network mode information of the mobile phone, the production line version information, the encrypted serial number (SN), the fault occurrence time, the fault type, and the production line station information. Therefore, when the instruction processing module obtains the fault data from the hiview service, the instruction processing module can execute the above steps 508, 510, 511, and 512 only according to the name of the compressed file corresponding to the fault data. Therefore, after obtaining the second filtered fault data, the second filtered fault data can be decompressed to obtain the decompressed fault data.

[0178] By using the decompression method to restore the filtered fault data, the filtered fault data can be changed into a readable format. This helps to improve the ability to process and analyze the fault data, enabling R & D personnel to more accurately identify and understand the essence of the fault.

[0179] Step 514: The instruction processing module in the mobile phone extracts information from the decompressed fault data to obtain the extracted fault data.

[0180] After the instruction processing module in the mobile phone obtains the decompressed fault data, it can extract information from the decompressed fault data to obtain the extracted fault data. In the example, the information in the extracted fault data may include at least one of the mobile phone model and network mode information, production line version, fault type, and production line station information, etc. The present disclosure does not limit the information in the extracted fault data and can be flexibly set according to actual usage requirements.

[0181] Through the information extraction method, the most important and useful information in the fault data can be identified and extracted. It helps to more accurately locate the fault, quickly find the root cause of the problem, and take targeted solutions.

[0182] Step 515: The instruction processing module in the mobile phone formats the extracted fault data to obtain the processed fault data.

[0183] After obtaining the extracted fault data, in order to improve the data transmission efficiency, the instruction processing module in the mobile phone can perform formatting processing on the extracted fault data to obtain the processed fault data.

[0184] Exemplarily, the formatting processing can be compression processing. Through compression processing, the amount of data transmitted can also be reduced, thereby reducing the network load. In the case of limited network environment bandwidth and relatively serious network congestion, it can improve network performance and response speed and reduce transmission delay. It should be noted that the formatting processing is related to the specific application scenario, and the present disclosure does not limit this.

[0185] Step 516: The instruction processing module in the mobile phone sends the processed fault data to the pipe side device.

[0186] After obtaining the processed fault data, the instruction processing module in the mobile phone can upload the processed fault data to the pipe side device to facilitate the pipe side device to timely upload the processed fault data to the cloud side device.

[0187] In some examples, after obtaining the processed fault data, the instruction processing module in the mobile phone can respond to the data export request sent by the pipe side device and upload the processed fault data to the pipe side device.

[0188] Step 517: The pipe side device receives the processed fault data.

[0189] After the pipe-side device receives the processed fault data, the pipe-side device performs some data processing operations on the processed fault data to give full play to the role of the processed fault data.

[0190] Exemplarily, the pipe-side device includes at least one server. This server can also be called a log transfer server. The data processing operations performed by this server on the processed fault data include: saving the processed fault data, automatically migrating the processed fault data, and maintaining and managing the processed fault data.

[0191] Among them, the automatic migration of the processed fault data means that the pipe-side device can upload the saved processed fault data to the cloud-side device. The maintenance and management of the processed fault data means that the pipe-side device can perform daily maintenance and management on the processed fault data. For example, regularly deleting the processed fault data, timely updating the processed fault data, etc. It can be understood that the data processing operations performed by the pipe-side device can also include other operations, which are subject to actual use, and the present disclosure does not limit this.

[0192] As Figure 7 shown, this server can also include a function test module, a fault information module, and a fault processing module.

[0193] Among them, the function test module is used to obtain the function test data of the terminal device, and the function test data at least includes the function test result. The fault information module is used to extract the fault log in the fault data. The fault information module is also used to calibrate the parameters in the fault data. The fault processing module is used to process the fault data. For example, the fault processing module exports the fault data from the terminal device, the fault processing module packs the fault data, the fault processing module triggers the capture behavior, and the fault processing module triggers the dumping of the terminal device information. In a computer, dumping generally refers to exporting and saving data as a file or in a static form, that is, saving dynamic (volatile) data as static data (persistent data).

[0194] Step 518: The pipe-side device sends the processed fault data to the cloud-side device.

[0195] After the pipe-side device finishes performing the data processing operations on the processed fault data, the pipe-side device can upload the processed fault data to the cloud-side device in various ways. Exemplarily, as Figure 7 shown, the pipe-side device can upload the processed fault data to the cloud-side device through the firewall, thereby ensuring the transmission security of the processed fault data.

[0196] Step 519: The cloud-side device receives and displays the processed fault data.

[0197] After receiving the processed fault data uploaded by the pipe-side device, the cloud-side device can display the processed fault data. Thus, R & D personnel can quickly understand the current faults occurring in the mobile phone and handle the faults accordingly.

[0198] In some examples, the cloud-side device may include a display module. As Figure 7 shown, the cloud-side device can display the processed fault data on the manufacturing hardware fault analysis website and the R & D website through the display module. The manufacturing hardware fault analysis website can have functions such as Process Capability Index (CPK) analysis, device fault analysis, and aging test duration statistics. Through these functions, it can assist R & D personnel to better understand the faults occurring in the mobile phone, thus facilitating the quick resolution of the faults.

[0199] The R & D website can have functions such as interface display, data aggregation, data analysis, and algorithm and threshold correction.

[0200] Among them, the data aggregation function can be used to aggregate the processed fault data. Data analysis can be used to analyze the processed fault data. Interface display can be used to display the fault log data.

[0201] Exemplarily, through the data aggregation function and the data analysis function, the processed fault data can be processed to obtain the fault log data. Then, the fault log data can be displayed in the form of graphs or images through the interface display function. In this way, R & D personnel can more intuitively and clearly understand and analyze these data. For example, the interface display function can display the fault occurrence time, fault type, and production line station information, etc. in the fault log data.

[0202] In this way, R & D personnel can quickly locate the fault, understand the cause of the fault, and thus find a solution faster.

[0203] In addition, the interface display function can also have a filtering function. R & D personnel can filter out the required data according to certain conditions to better understand and analyze the faults. For example, through the fault type label, the display of a certain fault type can be opened or closed, or custom filtering labels can be defined. In this way, the positioning range can be narrowed down layer by layer, so as to quickly find the root cause of the problem. In short, through the form of interface display (i.e., visual display), it greatly facilitates the viewing of fault log data by R & D personnel, which is of great help in improving work efficiency and accuracy.

[0204] The algorithm and threshold correction may include algorithm correction and threshold correction. Among them, algorithm correction refers to improving the original algorithm to make it more efficient, accurate, faster or more adaptable to specific application scenarios. This may include improving the mathematical model of the algorithm, adding new feature extraction methods, optimizing the parameter settings of the algorithm, etc.

[0205] Threshold correction refers to adjusting the threshold or threshold value set in the website. These threshold values are usually used to control the threshold of certain functions or decisions. By correcting these threshold values, the behavior, results, access rights, etc. of the website can be adjusted and optimized. For example, threshold correction can be used to adjust the security level of the system, the strictness of filtering text or image content, etc.

[0206] When using the solution of the present disclosure to test the performance of the terminal device using a test application, if a failure occurs, the Hiview service in the terminal device can generate failure data. Then, the instruction processing module processes the failure data to obtain the processed failure data, and finally sends the processed failure data to the cloud-side device through the pipe-side device. In this way, the data collection efficiency can be effectively improved. By receiving the processed failure data through the cloud-side device, data loss can be avoided and data integrity can be ensured. The cloud-side device can also display the processed failure data, so that R & D personnel can more intuitively and clearly understand and analyze the failure data. And due to the timely feedback of the processed failure data, R & D personnel can solve the failure problem more quickly.

[0207] Therefore, by using the failure handling method provided by the present disclosure, the failure data can be screened and actively reported to the cloud-side device for display, so as to assist R & D personnel in quickly understanding the failures occurring in the terminal device.

[0208] In addition, in the above embodiments, the application scenario of the mobile phone having stability problems is used as an example for illustration. It can be understood that the above failure handling method can also be applied to application scenarios of other problems such as communication problems, power consumption problems, performance problems, etc. The embodiments of the present disclosure do not make any restrictions on this.

[0209] The following combines the attached Figure 8 to illustrate the failure handling method provided by the embodiments of the present disclosure. As Figure 8 shown, the failure handling method may include the following steps 801-step 803.

[0210] Step 801: The terminal device detects a failure event and generates failure data based on the failure event.

[0211] In the embodiments of the present disclosure, the terminal device detecting a failure event and generating failure data based on the failure event can refer to the above Figure 5Step 501 in the illustrated embodiment will not be elaborated in the embodiments of the present disclosure.

[0212] Step 802: The terminal device processes the fault data to obtain the processed fault data.

[0213] For the terminal device in the embodiments of the present disclosure to process the fault data to obtain the processed fault data, reference can be made to Step 501 in the above Figure 5 illustrated embodiment, which will not be elaborated in the embodiments of the present disclosure.

[0214] In some examples, for the terminal device to process the fault data to obtain the processed fault data, it includes: the terminal device obtains a configuration file, and the configuration file includes multiple screening conditions; the terminal device screens the fault data based on the multiple screening conditions to obtain the screened fault data; the terminal device extracts information from the screened fault data to obtain the extracted fault data; the terminal device performs formatting processing on the extracted fault data to obtain the processed fault data.

[0215] For the terminal device in the embodiments of the present disclosure to obtain a configuration file, where the configuration file includes multiple screening conditions; the terminal device screens the fault data based on the multiple screening conditions to obtain the screened fault data; the terminal device extracts information from the screened fault data to obtain the extracted fault data; the terminal device performs formatting processing on the extracted fault data to obtain the processed fault data, reference can be made to Figure 5 Steps 508 - 515 in the above illustrated embodiment, which will not be elaborated in the embodiments of the present disclosure.

[0216] In some examples, the multiple screening conditions include a first screening condition, a second screening condition, and a third screening condition, and the fault data includes multiple fault logs; screening the fault data based on the multiple screening conditions to obtain the screened fault data includes: based on the first screening condition, determining the fault logs within the fault range in the fault data; for the fault logs within the fault range in the fault data, obtaining the sorted fault data; based on the second screening condition and the sorted fault data, determining the first screened fault log, and the first screened fault log is the fault log for which the number of fault logs corresponding to the same fault type within a unit time is less than or equal to the first threshold; based on the third screening condition and the first screened fault log, obtaining the second screened fault log; the total number of the second screened fault logs is less than or equal to the second threshold; the screened fault data includes the second screened fault logs.

[0217] In the embodiments of the present disclosure, based on the first screening condition, fault logs within the fault range in the fault data are determined; for the fault logs within the fault range in the fault data, sorted fault data is obtained; based on the second screening condition and the sorted fault data, the first screened fault logs are determined, and the first screened fault logs are fault logs in which the number of fault logs corresponding to the same fault type within a unit time is less than or equal to the first threshold; based on the third screening condition and the first screened fault logs, the second screened fault logs are obtained; the total number of the second screened fault logs is less than or equal to the second threshold; the screened fault data includes the second screened fault logs, which can refer to steps 508 - 512 in the embodiment shown above. Figure 5 The steps 508 - 512 in the embodiment shown above are not elaborated herein again in the embodiments of the present disclosure.

[0218] In some examples, the fault logs include production line version information, serial number, fault occurrence time, fault type, and production line station information.

[0219] In some examples, for the fault logs within the fault range in the fault data, obtaining sorted fault data includes: based on the fault occurrence time of the fault logs within the fault range, sorted fault data is obtained for the fault logs within the fault range in the fault data.

[0220] In the embodiments of the present disclosure, based on the fault occurrence time of the fault logs within the fault range, obtaining sorted fault data for the fault logs within the fault range in the fault data can refer to step 510 in the embodiment shown above. The embodiments of the present disclosure are not elaborated herein again. Figure 5 The steps 510 in the embodiment shown above are not elaborated herein again in the embodiments of the present disclosure.

[0221] In some examples, the fault log is a compressed file; for the screened fault data, extracting the extracted fault data includes: performing decompression processing on the screened fault data to obtain the decompressed fault data; performing information extraction on the decompressed fault data to obtain the extracted fault data.

[0222] In the embodiments of the present disclosure, performing decompression processing on the screened fault data to obtain the decompressed fault data; performing information extraction on the decompressed fault data to obtain the extracted fault data can refer to steps 513 - 514 in the embodiment shown above. The embodiments of the present disclosure are not elaborated herein again. Figure 5 The steps 513 - 514 in the embodiment shown above are not elaborated herein again in the embodiments of the present disclosure.

[0223] Step 803: The terminal device sends the processed fault data to the cloud device through the pipe-side device, and the cloud device is used to receive and display the processed fault data.

[0224] In the embodiments of the present disclosure, the terminal device sends the processed fault data to the cloud device through the pipe-side device, and the cloud device is used to receive and display the processed fault data. For the steps 516-step 519 in the embodiments shown above, the embodiments of the present disclosure will not be elaborated herein. Figure 5 For the steps 516-step 519 in the embodiments shown above, the embodiments of the present disclosure will not be elaborated herein.

[0225] In some examples, the terminal device sends the processed fault data to the cloud device through the pipe-side device, including: the terminal device receives a data export request from the pipe-side device; the data export request is used to request the terminal device to send the processed fault data to the pipe-side device, and the data export request includes the processed fault data; in response to the data export request, the terminal device sends the processed fault data to the pipe-side device, so as to send the processed fault data to the cloud device through the pipe-side device.

[0226] The terminal device in the embodiments of the present disclosure receives a data export request from the pipe-side device; the data export request is used to request the terminal device to send the processed fault data to the pipe-side device, and the data export request includes the processed fault data; in response to the data export request, the terminal device sends the processed fault data to the pipe-side device, so as to send the processed fault data to the cloud device through the pipe-side device. For the steps 502-step 519 in the embodiments shown above, the embodiments of the present disclosure will not be elaborated herein. Figure 5 For the steps 502-step 519 in the embodiments shown above, the embodiments of the present disclosure will not be elaborated herein.

[0227] Corresponding to the method in the foregoing embodiments, the embodiments of the present disclosure further provide a fault processing device. The fault processing device can be applied to a terminal device and is used to implement the method in the foregoing embodiments. The functions of the fault processing device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0228] For example, Figure 9 shows a schematic structural diagram of a fault processing device 900, as Figure 9 shown, the fault processing device 900 may include: a detection module 901, a processing module 902, and a sending module 903.

[0229] Among them, the detection module 901 is configured to detect a fault event and generate fault data based on the fault event. The processing module 902 is configured to process the fault data to obtain the processed fault data. The sending module 903 is configured to send the processed fault data to the cloud device through the pipe-side device, and the cloud device is used to receive and display the processed fault data.

[0230] In a possible implementation, the fault handling device 900 further includes a receiving module 904. The receiving module 904 is configured to receive a data export request from the pipe side device; the data export request is used to request the terminal device to send the processed fault data to the pipe side device, and the data export request includes the processed fault data. The sending module 903 is further configured to, in response to the data export request, the terminal device sends the processed fault data to the pipe side device, so as to send the processed fault data to the cloud side device through the pipe side device.

[0231] In a possible implementation, the fault handling device 900 further includes an obtaining module 905. The obtaining module 905 is configured to obtain a configuration file, and the configuration file includes a plurality of screening conditions. The processing module 902 is further configured to screen the fault data based on the plurality of screening conditions to obtain the screened fault data; extract information from the screened fault data to obtain the extracted fault data; and perform formatting processing on the extracted fault data to obtain the processed fault data.

[0232] In a possible implementation, the plurality of screening conditions include a first screening condition, a second screening condition, and a third screening condition, and the fault data includes a plurality of fault logs; the screened fault data includes the screened second fault logs. The processing module 902 is further configured to determine the fault logs within the fault range in the fault data based on the first screening condition; obtain the sorted fault data for the fault logs within the fault range in the fault data; determine the screened first fault logs based on the second screening condition and the sorted fault data, and the screened first fault logs are the fault logs whose number corresponding to the same fault type within a unit time is less than or equal to a first threshold; and obtain the screened second fault logs based on the third screening condition and the screened first fault logs; the total number of the screened second fault logs is less than or equal to a second threshold;

[0233] In a possible implementation, the processing module 902 is further configured to obtain the sorted fault data for the fault logs within the fault range in the fault data based on the fault occurrence time of the fault logs within the fault range.

[0234] In a possible implementation, the fault log includes production line version information, serial number, fault occurrence time, fault type, and production line station information.

[0235] In a possible implementation, the fault log is a compressed file; the processing module 902 is further configured to decompress the screened fault data to obtain the decompressed fault data; and extract information from the decompressed fault data to obtain the extracted fault data.

[0236] For example,Figure 10 shows a schematic structural diagram of a fault handling system, as Figure 10 shown. The fault handling system may include a terminal device 1001, a pipe side device 1002, and a cloud side device 1003.

[0237] Among them, the terminal device 1001 is used to detect a fault event, generate fault data based on the fault event, process the fault data to obtain processed fault data, and receive a data export request from the pipe side device and, in response to the data export request, send the processed fault data to the pipe side device. The data export request is used to request the terminal device to send the processed fault data to the pipe side device, and the data export request includes the processed fault data.

[0238] The pipe side device 1002 is used to send a data export request to the terminal device and receive the processed fault data and send the processed fault data to the cloud side device.

[0239] The cloud side device 1003 is used to receive and display the processed fault data.

[0240] In a possible implementation, the pipe side device 1002 is further used to store the processed fault data and delete or update the processed fault data at fixed intervals.

[0241] It should be understood that the division of units or modules (hereinafter all referred to as units) in the above device is only a logical function division. In actual implementation, they can be fully or partially integrated into a physical entity, or physically separated. And the units in the device can all be implemented in the form of software called by a processing element; they can also all be implemented in hardware form; or some units can be implemented in the form of software called by a processing element, and some units can be implemented in hardware form.

[0242] For example, each unit can be a separately established processing element, or can be integrated in a certain chip of the device. In addition, it can also be stored in a memory in the form of a program and called and executed by a certain processing element of the device to perform the function of the unit. In addition, these units can be fully or partially integrated together or can be independently implemented. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through the integrated logic circuit of the hardware in the processor element or in the form of software called by the processing element.

[0243] In one example, the units in the above device can be one or more integrated circuits configured to implement the above method, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.

[0244] For another example, when the units in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a CPU or other processors that can call programs. For another example, these units can be integrated together and implemented in the form of a system-on-chip (SOC).

[0245] In one implementation, the units in the above device that implement the corresponding steps in the above method can be implemented in the form of a processing element scheduler. For example, the device can include a processing element and a storage element. The processing element calls the program stored in the storage element to execute the method of the above method embodiment. The storage element can be a storage element on the same chip as the processing element, that is, an on-chip storage element.

[0246] In another implementation, the program for executing the above method can be stored in a storage element on a different chip from the processing element, that is, an off-chip storage element. At this time, the processing element calls or loads the program from the off-chip storage element onto the on-chip storage element to call and execute the method of the above method embodiment.

[0247] For example, an embodiment of the present disclosure can also provide a device, such as a terminal device, which may include: a processor and a memory for storing executable instructions of the processor. When the processor is configured to execute the above instructions, the terminal device implements the fault handling method as described in the foregoing embodiments. The memory can be located inside the terminal device or outside the terminal device. And the processor includes one or more.

[0248] In yet another implementation, the units in the device that implement the various steps in the above method can be configured as one or more processing elements, and these processing elements can be provided on the corresponding terminal device as described above. Here, the processing element can be an integrated circuit, such as: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.

[0249] For example, an embodiment of the present disclosure also provides a chip, which can be applied to the above terminal device. The chip includes one or more interface circuits and one or more processors; the interface circuits and the processors are interconnected by lines; the processors receive and execute computer instructions from the memory of the terminal device through the interface circuits to implement the method in the above method embodiment.

[0250] An embodiment of the present disclosure also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a terminal device, the terminal device can implement the fault handling method as described above.

[0251] The embodiments of the present disclosure also provide a computer program product, including computer instructions for running on the terminal device as described above. When the computer instructions run on the terminal device, the terminal device can implement the fault handling method as described above. Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In practical applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0252] In several embodiments provided by the present disclosure, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in electrical, mechanical or other forms.

[0253] The unit described as a separated component may or may not be physically separated. The component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0254] In addition, each functional unit in various embodiments of the present disclosure can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0255] 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 readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present disclosure, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product, such as: a program. This software product is stored in a program product, such as a computer-readable storage medium, including several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods in various embodiments of the present disclosure. And the foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks or optical discs that can store program codes.

[0256] For example, an embodiment of the present disclosure may further provide a computer-readable storage medium storing computer program instructions. When the computer program instructions are executed by a terminal device, the terminal device is caused to implement the fault handling method in the foregoing method embodiment.

[0257] The above is only the specific implementation manner of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any change or replacement within the technical scope disclosed by the present disclosure should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A fault handling method, characterized in that, The method includes: After a test application in a terminal device detects a fault event corresponding to the self-function of the terminal device, the test application calls the view Hiview service to generate fault data corresponding to the fault event; An instruction processing module in the terminal device responds to a first notification, obtains a configuration file, and sends a second notification to the Hiview service to request to obtain the fault data from the Hiview service. Wherein, the first notification is sent by a management-side device to the instruction processing module, the second notification is used to request to obtain the fault data, the configuration file includes multiple screening rules, the multiple screening rules include a first screening rule, a second screening rule, and a third screening rule, and the fault data includes multiple fault logs; After obtaining the fault data, the instruction processing module determines the fault logs within the fault range in the fault data based on the first screening rule; The instruction processing module sorts the fault logs within the fault range in the fault data to obtain sorted fault logs; The instruction processing module determines a first screened fault log based on the second screening rule and the sorted fault logs. The first screened fault log is a fault log for which the number of fault logs corresponding to the same fault type within a unit time is less than or equal to a first threshold; The instruction processing module obtains a second screened fault log based on the third screening rule and the first screened fault log, so as to determine the second screened fault log as the screened fault data, wherein the total number of the second screened fault logs is less than or equal to a second threshold; The instruction processing module extracts information from the screened fault data to obtain extracted fault data; The instruction processing module formats the extracted fault data based on the production monitoring daemon process FMD to obtain processed fault data; the instruction processing module sends the processed fault data to a cloud-side device through the management-side device, and the cloud-side device is used to receive and display the processed fault data.

2. The method according to claim 1, characterized in that, The instruction processing module sending the processed fault data to the cloud-side device through the management-side device includes: The instruction processing module receives a data export request from the management-side device; the data export request is used to request the instruction processing module to send the processed fault data to the management-side device, and the data export request includes the processed fault data; In response to the data export request, the instruction processing module sends the processed fault data to the management-side device, so as to send the processed fault data to the cloud-side device through the management-side device.

3. The method according to claim 1, characterized in that, The instruction processing module sorting the fault logs within the fault range in the fault data to obtain sorted fault logs includes: The instruction processing module sorts the fault logs within the fault range in the fault data based on the fault occurrence time of the fault logs within the fault range to obtain sorted fault logs.

4. The method according to claim 3, characterized in that, The fault log includes production line version information, serial number, fault occurrence time, fault type, and production line station information.

5. The method according to claim 1, characterized in that, The fault log is a compressed file; The instruction processing module extracts information from the filtered fault data to obtain the extracted fault data, including: The instruction processing module performs decompression processing on the filtered fault data to obtain the decompressed fault data; The instruction processing module extracts information from the decompressed fault data to obtain the extracted fault data.

6. A fault handling system, characterized in that, It includes a terminal device, a pipe-side device, and a cloud-side device; the terminal device is configured to: after detecting a fault event corresponding to its own function of the terminal device based on a test application, call and view the Hiview service through the test application to generate fault data corresponding to the fault event; respond to a first notification based on an instruction processing module to obtain a configuration file through the instruction processing module, and send a second notification to the Hiview service through the instruction processing module, so that the instruction processing module requests and obtains the fault data from the Hiview service, where the first notification is sent by the pipe-side device to the instruction processing module, the second notification is used to request and obtain the fault data, the configuration file includes multiple filtering rules, the multiple filtering rules include a first filtering rule, a second filtering rule, and a third filtering rule, the fault data includes multiple fault logs; after the instruction processing module obtains the fault data, based on the first filtering rule, determine the fault logs within the fault range in the fault data; sort the fault logs within the fault range in the fault data based on the instruction processing module to obtain the sorted fault logs; based on the instruction processing module, based on the second filtering rule and the sorted fault logs, determine the first filtered fault log, and the first filtered fault log is the fault log whose number corresponding to the same fault type within a unit time is less than or equal to a first threshold; based on the instruction processing module, based on the third filtering rule and the first filtered fault log, obtain the second filtered fault log, so as to determine the second filtered fault log as the filtered fault data, where the total number of the second filtered fault logs is less than or equal to a second threshold; based on the instruction processing module, extract information from the filtered fault data to obtain the extracted fault data; based on the instruction processing module, call the production monitoring daemon process FMD to format the extracted fault data to obtain the processed fault data; The pipe-side device is configured to: send a data export request to the terminal device, so that the terminal device responds to the data export request and sends the processed fault data to the pipe-side device; The pipe-side device is further configured to: after receiving the processed fault data, send the processed fault data to the cloud-side device; The cloud-side device is configured to: receive and display the processed fault data.

7. The fault handling system according to claim 6, characterized in that, The tube-side device is further configured to: store the processed fault data, and delete or update the processed fault data at fixed intervals.

8. A computer-readable storage medium, on which computer program instructions are stored; characterized in that, When the computer program instructions are executed by a fault processing system, the fault processing system implements a fault processing method according to any one of claims 1 to 5.

Images