CN113704014B - Log acquisition system, method, electronic device and storage medium - Google Patents

Abstract

The present application provides a log acquisition system, method, electronic device and storage medium. The method is applied in a terminal device. The log collection module of the terminal device responds to the received remote diagnosis instruction, acquires fault event information from the remote diagnosis instruction, and sends the fault event information to the fault management module. The fault management module obtains the fault log of the terminal device, and determines the fault log matching the fault event information from the fault log as the target fault log according to the fault event information. The present application can obtain logs near the time point when the abnormal problem occurs in time according to the fault event information corresponding to the abnormal problem.

Description

Log acquisition system, method, electronic device and storage medium

technical field

The present application relates to the technical field of data transmission, and in particular to a log acquisition system, method, electronic device and storage medium.

Background technique

At present, when users use terminal devices, they may encounter certain stability and other abnormal problems, such as black screen, restart after freezing and so on. When the user checks or repairs the abnormal problem, he needs to reproduce the problem. After reproducing the problem, click Capture Log and upload the log to the cloud. Due to the limitations of the log size and traffic, the logs near the time when the abnormal problem occurred cannot be obtained in time, resulting in the obtained logs being later than the fault time.

Contents of the invention

In view of the above, it is necessary to provide a log acquisition system, method, electronic device and storage medium to timely acquire logs near the time point when the abnormal problem occurs.

In the first aspect, the present application provides a log acquisition system, including a first device and a second device that communicate with each other, and the first device is configured to: respond to an instruction to capture logs, and the fault detection module of the first device will remotely diagnose The instruction is sent to the log collection module of the second device, wherein the remote diagnosis instruction includes fault event information. The second device is configured as follows: in response to the remote diagnosis command, the log acquisition module of the second device obtains the fault event information from the remote diagnosis command, sends the fault event information to the fault management module, and notifies the fault management module to obtain the fault event information corresponding to the fault event information log. The fault management module of the second device obtains the fault log of the second device, and determines from the fault log according to the fault event information that the fault log matching the fault event information is the target fault log. In the above technical solution of the present application, the log collection module sends the fault event information corresponding to the abnormal problem received from the first device to the fault management module, and the fault management module determines the fault event information from the obtained fault log according to the fault event information. The fault log with matching information is the target fault log, so as to obtain the log near the time point when the abnormal problem occurred in time.

In an implementation manner, the fault management module obtains fault logs obtained by the second device performing fault log management in at least one business domain. Through the above technical solution, at least one business field can be managed to obtain the fault log corresponding to the business field.

In a possible implementation manner, obtaining the fault log obtained by the second device performing fault log management in at least one business domain includes: the log management calling module performs fault log management in at least one business domain to obtain the management of at least one business domain information, and send the dot information of at least one business field to the dot interface module; the dot interface module determines the fault log according to the dot information of at least one business field; the fault management module obtains the fault log from the dot interface module. Through the above technical solution, the fault management module obtains the fault log for the management of the business field from the management interface module.

In an implementation manner, the fault event information includes a fault event ID tag or an application package name.

In an implementation manner, the fault management module determines from the fault log according to the fault event information that the fault log that matches the fault event information is the target fault log includes: The fault log whose label matches is the target fault log, or the fault log that matches the application package name is determined from the fault logs according to the application package name as the target fault log. Through the above technical solution, the fault management module can determine the fault log matching the fault event ID tag or the fault log matching the application package name as the target fault log.

In one implementation, the fault management module of the second device sends the target fault log to the log collection module after determining the target fault log; the log collection module sends the target fault log to the log upload channel module; the log upload channel module sends The target failure log is uploaded to the log server. Through the above technical solution, the target fault log is sent to the log collection module, and the log collection module uploads the target fault log to the log server through the log upload channel, so as to timely upload the log near the time point when the abnormal problem occurs to the log server.

In one implementation, the log collection module of the second device packs and compresses the target fault log, and sends the compressed target fault log to the log upload channel module; the log upload channel module uploads the compressed target fault log to the log server. Through the above technical solution, the target failure log can be compressed and uploaded to the log server.

In an implementation manner, the log upload channel module of the second device returns the target fault log or the compressed target fault log to the log collection module; the log collection module uploads the returned result to the fault detection module. Through the above technical solution, the log collection module can feed back the upload result of the target fault log or the compressed target fault log to the fault detection module.

In an implementation manner, the log collection module of the second device responds to the feedback instruction and generates a diagnosis shutdown instruction; the log collection module sends the diagnosis shutdown instruction to the fault detection module to notify the fault detection module to exit the remote diagnosis. Through the above technical solution, the fault detection module can quit the remote diagnosis of the log according to the diagnosis shutdown instruction sent by the log collection module.

In an implementation manner, the second device sends an instruction to capture logs to the first device in response to the user's operation.

In an implementation manner, the second device sends an instruction to capture logs to the remote diagnosis platform in response to the user's operation on the diagnosis analysis control. Through the above technical solution, the second device can respond to the user's operation of clicking the diagnostic analysis control, and send an instruction to capture logs to the first device, thereby realizing log capture.

In one implementation, the second device displays the first interface including the diagnostic analysis control; in response to the user's operation of clicking the diagnostic analysis control, displays the second interface including the verification code field; and receives the user input through the verification code field The verification code, and after the verification code is verified, send the instruction of grabbing logs to the remote diagnosis platform. Through the above technical solution, after the verification code entered by the user in the verification code field displayed on the second interface is verified, an instruction to capture logs is sent to the remote diagnosis platform, thereby realizing log capture.

In an implementation manner, the second device further displays a third interface in response to the user's operation of clicking the view log content control on the second interface, where the log content is displayed on the third interface. Through the above technical solution, by clicking the view log content control on the second interface, the log content can be displayed on the third interface for the user to view.

In one implementation, the first device is further configured to: if the second device has uploaded an abnormal log management event corresponding to the fault event, the obtained fault event information includes the fault event identity tag and the application package name; if the second device No exception log management event corresponding to the fault event has been uploaded, and the obtained fault event information includes the scope of the identity tag of the fault event and the name of the application package. Through the above technical solution, when the second device has uploaded the abnormal log management event corresponding to the fault event, the fault event information obtained by the first device includes the fault event identity tag and the application package name; When the corresponding exception log is logged, the fault event information acquired by the first device includes the scope of the identity tag of the fault event and the name of the application package.

In an implementation manner, the fault detection module of the first device receives a log task including fault event information input by a user on the task interface through the task interface, and uses the log task as a remote diagnosis instruction. The above technical solution can set the content of the remote diagnosis instruction through the task interface.

In one implementation, the task interface includes a failure event identity label field, an application package name field, and a failure event identity label range field. The failure event identity label field is used to obtain the identity label of the failure event. The failure event identity label The scope field is used to obtain the scope of the identity label of the fault event, and the application package name field is used to obtain the application package name. In the above technical solution, the identity tag of the fault event, the application package name, or the range of the identity tag of the fault event are set and acquired through the task interface.

In the second aspect, the embodiment of the present application provides a log acquisition method, which is applied in a terminal device. The method includes: the log acquisition module responds to the received remote diagnosis instruction, and obtains fault event information from the remote diagnosis instruction; the log acquisition module will Send the fault event information to the fault management module, and notify the fault management module to obtain the log corresponding to the fault event information; The failure log is the target failure log. In the above technical solution of the present application, the log collection module sends the fault event information corresponding to the abnormal problem received from the first device to the fault management module, and the fault management module determines the fault event information from the obtained fault log according to the fault event information. The fault log with matching information is the target fault log, so as to obtain the log near the time point when the abnormal problem occurred in time.

In an implementation manner, the fault management module acquires fault logs obtained by terminal equipment in at least one business domain through fault log management. Through the above technical solution, at least one business field can be managed to obtain the fault log corresponding to the business field.

In an implementation manner, obtaining the fault log obtained by the terminal device in at least one business domain through fault log management includes: the log management calling module performs fault log management in at least one business domain to obtain the management information of at least one business domain, and Send the dotting information of the group of business domains to the dotting interface module; the dotting interface module determines the fault log according to the dot information of at least one business field; the fault management module obtains the fault log from the dotting interface module. Through the above technical solution, the fault management module obtains the fault log for the management of the business field from the management interface module.

In an implementation manner, the fault event information includes a fault event ID tag or an application package name.

In one implementation, the fault management module determines from the fault logs the fault log matching the fault event identity tag as the target fault log according to the fault event identity tag, or determines the The fault log whose name matches the target fault log. Through the above technical solution, the fault management module can determine the fault log matching the fault event ID tag or the fault log matching the application package name as the target fault log.

In one implementation, the method further includes: the fault management module sends the target fault log to the log collection module after determining the target fault log; the log collection module sends the target fault log to the log upload channel module; the log upload channel The module uploads the target failure log to the log server. Through the above technical solution, the target fault log is sent to the log collection module, and the log collection module uploads the target fault log to the log server through the log upload channel, so as to timely upload the log near the time point when the abnormal problem occurs to the log server.

In one implementation, the method further includes: the log collection module packs and compresses the target fault log, and sends the compressed target fault log to the log upload channel module; the log upload channel module compresses the compressed target fault log Upload to the log server. Through the above technical solution, the target failure log can be compressed and uploaded to the log server.

In an implementation manner, the method further includes: the log upload channel module returns the target fault log or the compressed target fault log to the log collection module; the log collection module uploads the returned result to the fault detection module. Through the above technical solution, the log collection module can feed back the upload result of the target fault log or the compressed target fault log to the fault detection module.

In an implementation manner, the method further includes: the log collection module responds to the feedback instruction and generates a diagnosis shutdown instruction; the log collection module sends the diagnosis shutdown instruction to the fault detection module to notify the fault detection module to exit the remote diagnosis. Through the above technical solution, the fault detection module can quit the remote diagnosis of the log according to the diagnosis shutdown instruction sent by the log collection module.

In an implementation manner, the method further includes: in response to the user's operation, sending an instruction of grabbing logs to the remote diagnosis platform.

In an implementation manner, in response to the user's operation, sending the instruction of capturing logs to the remote diagnosis platform includes: in response to the user's operation on the diagnostic analysis control, sending the instruction of capturing logs to the remote diagnosis platform. Through the above technical solution, the second device can respond to the user's operation of clicking the diagnostic analysis control of the applet, and send an instruction to capture logs to the first device, thereby realizing the capture of logs.

In one implementation, in response to the user's operation on the diagnostic analysis control, sending an instruction to grab logs to the remote diagnosis platform includes: displaying the first interface, on which the diagnostic analysis control is displayed; responding to the user's operation of clicking the diagnostic analysis control , displaying the second interface, the verification code field is displayed on the second interface; and the verification code input by the user is received through the verification code field, and an instruction to capture logs is sent to the remote diagnosis platform after the verification code is verified. Through the above technical solution, after the verification code entered by the user in the verification code field displayed on the second interface is verified, an instruction to capture logs is sent to the remote diagnosis platform, thereby realizing log capture.

In an implementation manner, the method further includes: displaying a third interface in response to the user's operation of clicking the view log content control on the second interface, where the log content is displayed on the third interface. Through the above technical solution, by clicking the view log content control on the second interface, the log content can be displayed on the third interface for the user to view.

In an implementation manner, the method further includes: the fault management module saves the target fault log in a log service directory. Through the above technical solution, the target fault log can be saved.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory; wherein the processor is coupled to the memory; the memory is used to store program instructions; the processor is used to read the program instructions stored in the memory, To achieve the above log acquisition method.

In a fourth aspect, the embodiment of the present application provides a computer storage medium, the computer storage medium stores program instructions, and when the program instructions are run on the electronic device, the electronic device executes the log acquisition method as described above.

In addition, for the technical effects brought about by the third aspect to the fourth aspect, please refer to the descriptions related to the methods of each design in the above method part, and will not be repeated here.

Description of drawings

FIG. 1 is a block diagram of a software structure of an electronic device in an embodiment of the present application.

FIG. 2 is an architecture diagram of a log acquisition system in an embodiment of the present application.

Fig. 3 is a flow chart of a log acquisition method in an embodiment of the present application.

4a-4d are diagrams of application scenarios in which a terminal device sends an instruction to capture a log to a remote diagnosis platform in another embodiment of the present application.

FIG. 5 is an application scene diagram showing a diagnostic analysis sub-interface in an embodiment of the present application.

Fig. 6 is a schematic diagram of a task interface in an embodiment of the present invention.

FIG. 7 is a schematic diagram of a hardware structure of an electronic device in an embodiment of the present invention.

Detailed ways

Hereinafter, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features. Thus, a feature defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of some embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in some embodiments of the present application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field of this application. The terms used in the description of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. It should be understood that unless otherwise stated in this application, "/" means or. For example, A/B can mean either A or B. "And/or" in some embodiments of the present application is only an association relationship describing associated objects, indicating that there may be three relationships. For example, A and/or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. "At least one" means one or more. "A plurality" means two or more than two. For example, at least one of a, b or c can represent: a, b, c, a and b, a and c, b and c, a, b and c seven situations.

This application provides a log acquisition method. The log acquisition method is applied in the electronic device 100 . Referring to FIG. 1 , it is a block diagram showing a software structure of an electronic device 100 in an embodiment of the present application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system of the electronic device 100 is divided into four layers, from top to bottom are application program layer, application program framework layer, Android runtime (Android runtime) and system library, and kernel layer.

The application layer can include a series of applications. As shown in FIG. 1, applications may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown, the application program framework layer may include window manager, content provider, view system, phone manager, resource manager, notification manager and so on.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data, and make these data accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the download completion, message reminder, etc. The notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is issued, the smart terminal vibrates, and the indicator light flashes, etc.

Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

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

The media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, G.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.

2D graphics engine is a drawing engine for 2D drawing.

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

Referring to FIG. 2 , it is an architecture diagram of a log acquisition system in an embodiment of the present application. The log acquisition system 10 includes a remote diagnosis platform 20 , a terminal device 30 and a log server 40 . The remote diagnosis platform 20 communicates with the terminal device 30 , and the terminal device 30 communicates with the log server 40 . The remote diagnosis platform 20 is used to add fault event information and send the fault event information to the terminal device 30 . The terminal device 30 is used to search for a fault log matching the fault event information, and send the fault log to the log server 40 . In the above embodiments provided in the present application, the remote diagnosis platform may be referred to as a first device, and the terminal device 30 may be referred to as a second device.

In this embodiment, the remote diagnosis platform 20 includes a fault detection module 201 . The terminal device 30 includes a log collection module 301 , a fault management module 302 , a log upload channel module 303 , a log dot calling module 304 , and a dot interface module 305 . It should be noted that the modules in this application include software modules or hardware modules. In this embodiment, the log collection module 301 is connected to the fault management module 302 and the log upload channel module 303 respectively. The log dot calling module 304 is connected with the dot interface module 305 . The dot interface module 305 is connected with the fault management module 302 . As follows, the function of each module in the log acquisition system including 10 will be introduced in conjunction with the flow of each step of the log acquisition method in FIG. 3 .

Please refer to FIG. 3 , which is a flow chart of a log acquisition method in an embodiment of the present application. The method includes the following steps.

Step S301 , in response to the instruction of grabbing logs, the fault detection module 201 of the remote diagnosis platform 20 sends the remote diagnosis instruction to the log collection module 301 of the terminal device 30 , wherein the remote diagnosis instruction includes fault event information.

In this implementation, the terminal device 30 sends an instruction to capture logs to the remote diagnosis platform 20 in response to the user's operation. The remote diagnosis platform 20 is used to create a log task containing fault event information, and send the log task to the terminal device 30 . For example, referring to FIGS. 4a-4d , it shows an application scenario diagram in which the terminal device 30 sends an instruction to capture logs to the remote diagnosis platform 20 in an embodiment of the present application. In this embodiment, referring to FIG. 4 a , the detection application interface 32 is displayed after clicking on the applet displayed on the terminal device 30 , for example, the applet is the smart detection applet of the Honor mobile phone. It should be noted that the application icon of the applet is displayed on the application interface of the terminal device 30 , and the user can open the detection application interface 32 of the applet by clicking the application icon of the applet on the application interface of the terminal device 30 . In this embodiment, the terminal device 30 sends an instruction to capture logs to the remote diagnosis platform 20 in response to the user's operation on the detection application interface 32 . Specifically, when it is detected that the user clicks on the operation of the diagnostic analysis control 321 on the detection application interface 32, the terminal device 30 displays the diagnostic analysis interface 320 (refer to FIG. 4b ). The diagnostic analysis interface 320 displays a verification code field 322 . The user obtains the verification code by sending the mobile phone number to the background system, or by calling the service hotline to contact the customer service personnel to obtain the verification code. It should be noted that the background system is a system for managing or controlling the terminal device 30 to perform log capture. For example, the background system may be a server connected to the terminal device 30 in communication, or the background system and the log server 40 may be the same device. In this embodiment, the verification code is a character string composed of numbers and letters, and is used for security verification of this log capture. In this embodiment, after the user enters the obtained verification code in the verification code field 322, the terminal device 30 responds to the verification code, verifies the verification code, and sends a capture to the remote diagnosis platform 20 after the verification is passed. log instructions, and display the diagnostic analysis sub-interface 323 (refer to FIG. 4 c ) for users to view captured logs or exit log diagnostics. Referring to FIG. 5 , it is an application scene diagram showing a diagnostic analysis sub-interface 323 in an embodiment of the present application. In this embodiment, after the verification code is verified, the terminal device 30 also receives a notification message 31 sent by the background system and displays the notification message in the pull-down menu of the terminal device 30 . When it is detected that the user clicks the notification message 31 in the pull-down menu bar of the terminal device 30 , the terminal device 30 displays the diagnosis analysis sub-interface 323 . The diagnostic analysis sub-interface 323 includes a view log content control 324 , a feedback control 325 , an exit control 326 and a problem description window control 327 . In response to the user's operation of clicking the view log content control 324, the terminal device 30 displays the matched log content for the user to view (refer to FIG. 4d ). It should be noted that the log content shown in FIG. 4d may be displayed after the user clicks the view log content control 324 on the diagnostic analysis sub-interface 323, or after the user clicks the diagnostic analysis control 321 on the detection application interface 32. or it is displayed after the verification code input by the user in the verification code field 322 of the diagnostic analysis sub-interface 323 is verified. In this embodiment, the terminal device 30 closes the log diagnosis in response to the user's operation of clicking the feedback control 325 . In response to the user's operation of clicking the exit control 326, the terminal device 30 exits the log diagnosis. The terminal device 30 receives the user's description of the fault event through the problem description window control 327 .

In this embodiment, the fault detection module 201 of the remote diagnosis platform 20 sends the remote diagnosis command carrying fault event information to the log collection module 301 of the terminal device 30 in response to the log capture command sent by the terminal device 30 . It should be noted that the fault detection module 201 receives the log task including fault event information input by the staff on the remote diagnosis platform 20 side on the task interface 50 through a task interface, and uses the log task as a remote diagnosis command. Specifically, the fault detection module 201 displays the task interface 50 in response to the command to capture logs sent by the terminal device 30 . Referring to FIG. 6 , it is a schematic diagram of a task interface 50 in an embodiment of the present application. The task interface 50 includes a task name field, a timeout duration field, a fault event ID tag (ID) field, a fault event ID tag range field, an application package name field, and a fault type field. It should be noted that the task name column is used to obtain the name of the log task. In this embodiment, the system of the fault detection module 201 automatically assigns and enters the task name into the task name column. The timeout period field is used to obtain the timeout period of the failure event of the log task. The Fault Event ID Tag field is used to get the ID tag of the fault event. The Fault Event ID Tag Range field is used to get the range of the fault event ID tag. The application package name field is used to obtain the application package name of the log task. The failure type field is used to obtain the type of failure event. It should be noted that the types of fault events include, but are not limited to, application categories (such as system/third-party applications, communication and social networking, multimedia, etc.), reliability categories (such as crashes, restarts, upgrades, etc.), performance categories (such as freezing, Slow start, etc.), power consumption (such as battery life, heating, charging, etc.), communication (such as calls, text messages, signals, data, etc.), short-range categories (such as WiFi, Bluetooth, GPS, NFC, etc.), device categories ( Such as sensing, fingerprint, screen, infrared, etc.).

It should be noted that the remote diagnosis platform 20 can determine the fault event information according to whether the terminal device 30 has uploaded an abnormal log event corresponding to the fault event before obtaining the command to grab the log. If the terminal device 30 has uploaded an abnormal log management event corresponding to the fault event, the fault event information acquired by the remote diagnosis platform 20 through the task interface 50 includes the fault event identity tag and the application package name. If the terminal device 30 has not uploaded an abnormal log management event corresponding to the fault event, the fault event information obtained by the remote diagnosis platform 20 through the task interface 50 includes: the scope of the identity tag of the fault event, and the application package name.

Step S302, in response to the remote diagnosis instruction, the log collection module 301 turns on the diagnosis switch, and obtains fault event information from the remote diagnosis instruction.

In step S303, the log collection module 301 sends the fault event information to the fault management module 302, and notifies the fault management module 302 to obtain logs corresponding to the fault event information.

In step S304, the fault management module 301 obtains the fault log of the terminal device 30, and determines from the fault logs according to the fault event information that the fault log matching the fault event information is the target fault log.

In this embodiment, after the log collection module 301 turns on the diagnosis switch, it obtains the fault event identity tag and application package name from the remote diagnosis command, or obtains the range of the fault event identity tag and the application package name from the remote diagnosis command. The log collection module 301 sends the fault event tag or the application package name to the fault management module 302, and notifies the fault management module 302 to obtain the log corresponding to the fault event tag or the process log corresponding to the application package name. The fault management module 302 acquires the fault logs obtained by the terminal device 30 in a group of business domains through fault log management, and determines from the fault logs the fault log that matches the fault event identity tag as the target fault log according to the fault event identity tag , or determine the fault log matching the application package name from the fault logs according to the application package name as the target fault log.

In this embodiment, the fault management module 302 acquires the fault logs obtained by the terminal device 30 in a group of business fields through fault log management, including: the log management module 304 performs fault log management in the group of business fields to obtain the fault logs of the group of business fields Dot information, and the dot information of this group of business fields is sent to the dot interface module 305; The dot interface module 305 determines the failure log according to the dot information of this group of business fields; the fault management module 302 obtains the fault from the dot interface module 305 log. After obtaining the fault log, the fault management module 302 processes the fault log through the remote diagnosis plug-in to obtain the target fault log. Specifically, the remote diagnosis plug-in determines the fault log that matches the fault event identity tag from the fault log according to the fault event identity tag, or determines the fault log that matches the application package name from the fault log according to the application package name. Fault log.

In this embodiment, the business domain includes, but is not limited to, the stability domain and the performance domain. The stability field includes at least one of ANR, crash, tombstone, and watching. The performance domain includes at least one of startup time, interface switching, and response time.

In step S305, the fault management module 302 saves the target fault log.

In this embodiment, the fault management module 302 saves the target fault log in a specified file directory of the terminal device 30 , for example, saves the target fault log in a log service (LogService) directory of the terminal device 30 .

Step S306 , the fault management module 302 sends the target fault log to the log collection module 301 .

In step S307, the log collection module 301 packs and compresses the target fault log.

In step S308, the log collection module 301 responds to the feedback instruction, turns off the diagnosis switch and generates a diagnosis turn-off instruction.

Referring to FIG. 4C , when it is detected that the user clicks the feedback control 325 on the diagnostic analysis sub-interface 323 of the terminal device 30 , the log collection module 301 generates a feedback instruction. The log collection module 301 turns off the diagnosis switch according to the feedback instruction, and generates a diagnosis turn-off instruction.

In step S309, the log collection module 301 sends a diagnosis shutdown command to the fault detection module 201 to notify the fault detection module 201 to exit the remote diagnosis.

Step S310 , the log collection module 301 sends the target fault log or the compressed target fault log to the log upload channel module 303 .

Step S311 , the log upload channel module 303 uploads the target fault log or the compressed target fault log to the log server 40 , and returns the upload result to the log collection module 301 .

Step S312 , the log collection module 301 uploads the returned result to the fault detection module 201 .

Referring to FIG. 7 , it is a schematic diagram of a hardware structure of an electronic device 100 in an embodiment of the present application. The electronic device 100 includes a remote diagnosis platform 20 , a terminal device 30 or a combination of terminal devices 30 of the remote diagnosis platform 20 . For example, the electronic device 100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, and a cell phone, a personal Digital assistant (personal digital assistant, PDA), augmented reality (augmented reality, AR) equipment, virtual reality (virtual reality, VR) equipment, artificial intelligence (artificial intelligence, AI) equipment, wearable equipment, vehicle equipment, smart home Devices and/or smart city devices, some embodiments of the present application do not specifically limit the specific type of the electronic device 100 .

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and A subscriber identification module (subscriber identification module, SIM) card interface 195 and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.

It can be understood that, the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor (ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (serial data line, SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flashlight, the camera 193 and the like through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to realize the touch function of the electronic device 100 .

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 . In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls through the Bluetooth headset.

The PCM interface can also be used for audio communication, sampling, quantizing and encoding the analog signal. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 . For example: the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to realize the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . The MIPI interface includes a camera serial interface (camera serial interface, CSI), a display serial interface (displayserial interface, DSI), and the like. In some embodiments, the processor 110 communicates with the camera 193 through the CSI interface to realize the shooting function of the electronic device 100 . The processor 110 communicates with the display screen 194 through the DSI interface to realize the display function of the electronic device 100 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193 , the display screen 194 , the wireless communication module 160 , the audio module 170 , the sensor module 180 and so on. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface conforming to the USB standard specification, specifically, it may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100 , and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones and play audio through them. This interface can also be used to connect other electronic devices 100, such as AR devices.

It can be understood that the interface connection relationship between the modules shown in the embodiment of the present invention is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 140 is configured to receive a charging input from a charger. Wherein, the charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 is charging the battery 142 , it can also supply power to the electronic device 100 through the power management module 141 .

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives the input from the battery 142 and/or the charging management module 140 to provide power for the processor 110 , the internal memory 121 , the display screen 194 , the camera 193 , and the wireless communication module 160 . The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be disposed in the processor 110 . In some other embodiments, the power management module 141 and the charging management module 140 may also be set in the same device.

The wireless communication function of the electronic device 100 can be realized by the antenna 1 , the antenna 2 , the mobile communication module 150 , the wireless communication module 160 , a modem processor, a baseband processor, and the like.

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

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.

A modem processor may include a modulator and a demodulator. Wherein, the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is passed to the application processor after being processed by the baseband processor. The application processor outputs sound signals through audio equipment (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (wireless fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (codedivision multiple access, CDMA), wideband code Wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM , and/or IR technology, etc. The GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou satellite navigation system (beidounavigation satellite system, BDS), a quasi-zenith satellite system (quasi- zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

The electronic device 100 realizes the display function through the GPU, the display screen 194 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos and the like. The display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light emitting diode). AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diodes (quantum dot light emitting diodes, QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194 , where N is a positive integer greater than 1.

The electronic device 100 can realize the shooting function through the ISP, the camera 193 , the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used for processing the data fed back by the camera 193 . For example, when taking a picture, open the shutter, the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be located in the camera 193 .

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a complementary metal-oxide-semiconductor (complementary metal-oxide-semiconductor, CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other image signals. In some embodiments, the electronic device 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in various encoding formats, for example: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor. By referring to the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process input information and continuously learn by itself. Applications such as intelligent cognition of the electronic device 100 can be realized through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The internal memory 121 may include one or more random access memories (random access memory, RAM) and one or more non-volatile memories (non-volatile memory, NVM).

Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (synchronous dynamic random access memory, SDRAM), double data rate synchronous Dynamic random access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, such as the fifth generation DDR SDRAM is generally called DDR5 SDRAM), etc.;

Non-volatile memory may include magnetic disk storage devices, flash memory (flash memory).

According to the operating principle, flash memory can include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. According to the potential order of storage cells, it can include single-level storage cells (single-level cell, SLC), multi-level storage cells (multi-level cell, MLC), triple-level cell (TLC), quad-level cell (QLC), etc., can include universal flash storage (English: universal flash storage, UFS), An embedded multimedia memory card (embedded multi media Card, eMMC), etc.

The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of an operating system or other running programs, and can also be used to store user and application data.

The non-volatile memory can also store executable programs and store user and application data, etc., and can be loaded into random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 can be used to connect an external non-volatile memory, so as to expand the storage capacity of the electronic device 100 . The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and video are stored in an external non-volatile memory.

The internal memory 121 or the external memory interface 120 is used to store one or more computer programs. One or more computer programs are configured to be executed by the processor 110 . The one or more computer programs include multiple instructions. When the multiple instructions are executed by the processor 110 , the method for acquiring logs executed on the electronic device 100 in the above-mentioned embodiments can be implemented, so as to implement the log acquisition function of the electronic device 100 .

The electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be set in the processor 110 , or some functional modules of the audio module 170 may be set in the processor 110 .

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals. Electronic device 100 can listen to music through speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the receiver 170B can be placed close to the human ear to receive the voice.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can put his mouth close to the microphone 170C to make a sound, and input the sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 may be provided with two microphones 170C, which may also implement a noise reduction function in addition to collecting sound signals. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions, etc.

The earphone interface 170D is used for connecting wired earphones. The earphone interface 170D may be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may be comprised of at least two parallel plates with conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view short messages is executed. When a touch operation whose intensity is greater than or equal to the first pressure threshold acts on the icon of the short message application, the instruction of creating a new short message is executed.

The gyro sensor 180B can be used to determine the motion posture of the electronic device 100 . In some embodiments, the angular velocity of the electronic device 100 around three axes (ie, x, y and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyro sensor 180B detects the shaking angle of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and allows the lens to counteract the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude based on the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

The magnetic sensor 180D includes a Hall sensor. The electronic device 100 may use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a clamshell machine, the electronic device 100 can detect opening and closing of the clamshell according to the magnetic sensor 180D. Furthermore, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, features such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device 100, and can be applied to applications such as horizontal and vertical screen switching, pedometers, etc.

The distance sensor 180F is used to measure the distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may use the distance sensor 180F for distance measurement to achieve fast focusing.

Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diodes may be infrared light emitting diodes. The electronic device 100 emits infrared light through the light emitting diode. Electronic device 100 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it may be determined that there is an object near the electronic device 100 . When insufficient reflected light is detected, the electronic device 100 may determine that there is no object near the electronic device 100 . The electronic device 100 can use the proximity light sensor 180G to detect that the user is holding the electronic device 100 close to the ear to make a call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode, automatic unlock and lock screen in pocket mode.

The ambient light sensor 180L is used for sensing ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket, so as to prevent accidental touch.

The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access to application locks, take pictures with fingerprints, answer incoming calls with fingerprints, and the like.

The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to implement a temperature treatment strategy. For example, when the temperature reported by the temperature sensor 180J exceeds the threshold, the electronic device 100 may reduce the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the electronic device 100 from being shut down abnormally due to the low temperature. In some other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

The touch sensor 180K is also called "touch device". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a “touch screen”. The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 , which is different from the position of the display screen 194 .

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the human pulse and receive the blood pressure beating signal. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone, combined into a bone conduction earphone. The audio module 170 can analyze the voice signal based on the vibration signal of the vibrating bone mass of the vocal part acquired by the bone conduction sensor 180M, so as to realize the voice function. The application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.

The keys 190 include a power key, a volume key and the like. The key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 can receive key input and generate key signal input related to user settings and function control of the electronic device 100 .

The motor 191 can generate a vibrating reminder. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects for touch operations acting on different areas of the display screen 194 . Different application scenarios (for example: time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 195 is used for connecting a SIM card. The SIM card can be connected and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The electronic device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card and so on. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calling and data communication. In some embodiments, the electronic device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .

This embodiment also provides a computer program product, which, when running on a computer, causes the computer to execute the above related steps, so as to realize the log acquisition method in the above embodiment.

In addition, some embodiments of the present application also provide a device, which may specifically be a chip, a component or a module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, The processor may execute the computer-executable instructions stored in the memory, so that the chip executes the log acquisition method in each method embodiment above.

Wherein, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is all used to execute the corresponding method provided above, therefore, the beneficial effects it can achieve can refer to the corresponding method provided above The beneficial effects in the method will not be repeated here.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated according to needs It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the 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 it can be integrated into another device, or some features can be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of some embodiments of the present application are essentially or part of the contribution to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the software products are stored in a The storage medium includes several instructions for enabling a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods in various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of some embodiments of the present application and not to limit them. Although some embodiments of the present application have been described in detail with reference to preferred embodiments, those of ordinary skill in the art should It is understood that the technical solutions of some implementation examples of the present application may be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of some embodiments of the present application.

Claims (26)

1. A log acquisition system, comprising a first device and a second device, the first device and the second device are connected in communication, characterized in that: The first device is configured to: In response to the instruction of grabbing logs, the fault detection module of the first device sends a remote diagnosis instruction to the log collection module of the second device, wherein the remote diagnosis instruction includes fault event information, if the second device uploads The abnormal log management event corresponding to the fault event, the fault event information includes the fault event identity tag, the application package name, if the second device has not uploaded the abnormal log management event corresponding to the fault event, the fault event The event information includes the scope of the identity label of the fault event and the name of the application package; The second device is configured to: Responding to the remote diagnosis instruction, acquiring fault event information from the remote diagnosis instruction; The log collection module sends the fault event information to the fault management module, and notifies the fault management module to obtain a log corresponding to the fault event information; The fault management module acquires the fault log of the second device, and determines from the fault log according to the fault event information that the fault log matching the fault event information is the target fault log, including: according to the The fault event identity tag and the application package name determine from the fault log that the fault log matching the fault event identity tag and the application package name is the target fault log; or according to the fault event identity tag The scope and the application package name determine from the fault logs that the fault log matching the scope of the identity tag of the fault event and the application package name is the target fault log. 2. The log acquisition system according to claim 1, wherein the fault management module acquiring the fault log of the second device comprises: Obtaining fault logs obtained by the second device performing fault log management in at least one business domain. 3. The log acquisition system according to claim 2, wherein said acquisition of the fault log obtained by the second device in at least one business field through fault log management includes: The log management calling module performs fault log management in the at least one business domain to obtain the management information of the at least one business domain, and sends the management information of the at least one business domain to the management interface module; The point management interface module determines the fault log according to the point management information of the at least one business field; The fault management module acquires fault logs from the dotting interface module. 4. The log acquisition system according to claim 1, wherein the second device is further configured to: The fault management module sends the target fault log to the log collection module after determining the target fault log; The log collection module sends the target failure log to the log upload channel module; The log upload channel module uploads the target fault log to a log server. 5. The log acquisition system according to claim 4, wherein the second device is further configured to: The log collection module packs and compresses the target fault log, and sends the compressed target fault log to the log upload channel module; The log upload channel module uploads the compressed target fault log to the log server. 6. The log acquisition system according to claim 5, wherein the second device is further configured to: The log upload channel module returns the target fault log or the compressed target fault log to the log collection module; The log collection module uploads the returned result to the fault detection module. 7. The log acquisition system according to claim 4, wherein the second device is further configured to: The log collection module responds to the feedback instruction and generates a diagnosis shutdown instruction; The log collection module sends the diagnosis closing instruction to the fault detection module to notify the fault detection module to exit the remote diagnosis. 8. The log acquisition system according to claim 1, wherein the second device is further configured to: In response to the user's operation, sending the instruction of grabbing logs to the first device. 9. The log acquisition system according to claim 8, wherein the second device responds to the user's operation, and sending the instruction for grabbing the log to the first device includes: In response to the user's operation on the diagnosis and analysis control, the instruction of grabbing the log is sent to the remote diagnosis platform. 10. The log acquisition system according to claim 9, wherein, in response to the user's operation on the diagnostic analysis control, sending the command to grab the log to the remote diagnostic platform includes: displaying a first interface, where diagnostic analysis controls are displayed on the first interface; In response to the user's operation of clicking the diagnostic analysis control, a second interface is displayed, and a verification code field is displayed on the second interface; and The verification code input by the user is received through the verification code field, and the instruction of grabbing logs is sent to the remote diagnosis platform after the verification code is verified. 11. The log acquisition system according to claim 10, wherein the second device is further configured to: In response to the user's operation of clicking the view log content control on the second interface, a third interface is displayed, wherein the log content is displayed on the third interface. 12. The log acquisition system according to claim 1, wherein the first device is further configured to: The fault detection module receives a log task including fault event information input by a user on the task interface through the task interface, and uses the log task as the remote diagnosis instruction. 13. The log acquisition system according to claim 12, wherein the task interface includes a failure event identity label field, an application package name field, and a failure event identity label range field, and the failure event identity label field The bit is used to obtain the identity tag of the fault event, the fault event identity tag range field is used to obtain the range of the fault event identity tag, and the application package name field is used to obtain the application package name. 14. A log acquisition method applied in a terminal device, characterized in that the method comprises: The log acquisition module responds to the received remote diagnosis instruction, and obtains fault event information from the remote diagnosis instruction, wherein if the second device has uploaded an abnormal log event corresponding to the fault event, the fault event information includes the fault event identity tag, Application package name, if the second device has not uploaded an abnormal log management event corresponding to the fault event, the fault event information includes the scope of the identity tag of the fault event and the application package name; The log collection module sends the fault event information to the fault management module, and notifies the fault management module to obtain a log corresponding to the fault event information; The fault management module obtains the fault log of the terminal device, and determines from the fault log according to the fault event information that the fault log matching the fault event information is the target fault log, including: according to the fault event information The event identity tag and the application package name determine from the fault log that the fault log matching the fault event identity tag and the application package name is the target fault log; or according to the scope of the fault event identity tag The application package name determines from the fault logs the fault log that matches the scope of the identity tag of the fault event and the application package name as the target fault log. 15. The log obtaining method according to claim 14, wherein the fault management module obtaining the fault log of the terminal device comprises: Obtaining fault logs obtained by performing fault log management in at least one business field of the terminal device. 16. The log acquisition method according to claim 15, wherein said acquisition of the fault log obtained by the terminal device in at least one business field through fault log management comprises: The log management calling module performs fault log management in the at least one business domain to obtain the management information of the at least one business domain, and sends the management information of the at least one business domain to the management interface module; The point management interface module determines the fault log according to the point management information of the at least one business field; The fault management module acquires fault logs from the dotting interface module. 17. The log acquisition method according to claim 14, wherein the method further comprises: The fault management module sends the target fault log to the log collection module after determining the target fault log; The log collection module sends the target failure log to the log upload channel module; The log upload channel module uploads the target fault log to a log server. 18. The log acquisition method according to claim 17, wherein the method further comprises: The log collection module packs and compresses the target fault log, and sends the compressed target fault log to the log upload channel module; The log upload channel module uploads the compressed target fault log to the log server. 19. The log acquisition method according to claim 18, wherein the method further comprises: The log upload channel module returns the target fault log or the compressed target fault log to the log collection module; The log collection module uploads the returned result to the fault detection module. 20. The log acquisition method according to claim 14, wherein the method further comprises: The log collection module responds to the feedback instruction and generates a diagnosis shutdown instruction; The log collection module sends the diagnosis closing instruction to the fault detection module to notify the fault detection module to exit the remote diagnosis. 21. The log acquisition method according to claim 14, wherein the method further comprises: In response to the user's operation, an instruction to capture logs is sent to the remote diagnosis platform. 22. The log acquisition method according to claim 21, wherein the response to the user's operation, sending an instruction to grab logs to the remote diagnosis platform comprises: In response to the user's operation on the diagnosis and analysis control, the instruction of grabbing the log is sent to the remote diagnosis platform. 23. The log acquisition method according to claim 22, wherein, in response to the user's operation on the diagnostic analysis control, sending the command to grab the log to the remote diagnostic platform includes: displaying a first interface, where diagnostic analysis controls are displayed on the first interface; In response to the user's operation of clicking the diagnostic analysis control, a second interface is displayed, and a verification code field is displayed on the second interface; and The verification code input by the user is received through the verification code field, and the instruction of grabbing logs is sent to the remote diagnosis platform after the verification code is verified. 24. The log acquisition method according to claim 23, wherein the method further comprises: In response to the user's operation of clicking the view log content control on the second interface, a third interface is displayed, wherein the log content is displayed on the third interface. 25. An electronic device, comprising a processor and a memory; wherein the processor is coupled to the memory; The memory is used to store program instructions; The processor is configured to read the program instructions stored in the memory, so as to realize the log acquisition method according to any one of claims 14 to 24. 26. A computer-readable storage medium, characterized in that, the computer-readable storage medium stores program instructions, and when the program instructions are run on the electronic device, the electronic device executes any one of claims 14-24. One of the described log acquisition methods.

Images