CN113704014A

CN113704014A - Log acquisition system, method, electronic device and storage medium

Info

Publication number: CN113704014A
Application number: CN202110977395.0A
Authority: CN
Inventors: 马恒彪
Original assignee: Honor Device Co Ltd
Current assignee: Shanghai Glory Smart Technology Development Co ltd
Priority date: 2021-08-24
Filing date: 2021-08-24
Publication date: 2021-11-26
Anticipated expiration: 2041-08-24
Also published as: CN113704014B

Abstract

The application provides a log obtaining system, a log obtaining method, electronic equipment and a storage medium. The method is applied to the terminal equipment. And the log acquisition module of the terminal equipment 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. And the fault management module acquires the fault log of the terminal equipment and determines the fault log matched with the fault event information as a target fault log from the fault log according to the fault event information. According to the method and the device, the logs near the abnormal problem occurrence time point can be timely acquired 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 field of data transmission technologies, and in particular, to a log obtaining system, a log obtaining method, an electronic device, and a storage medium.

Background

At present, when a user uses a terminal device, some abnormal problems such as stability and the like may occur, such as a problem of a black screen, restarting after a card is dead and the like. When a user checks or repairs an abnormal problem, the problem needs to be reproduced. And clicking to capture the log after the problem is reproduced, and uploading the log to the cloud. Due to the fact that the size and the flow of the log have certain limitations, the log near the time point of occurrence of the abnormal problem cannot be obtained in time, and the obtained log is later than the failure time point.

Disclosure of Invention

In view of the above, it is desirable to provide a log acquiring system, method, electronic device and storage medium to acquire a log around the time point of occurrence of an abnormal problem in a timely manner.

In a first aspect, the present application provides a log obtaining system, including a first device and a second device that communicate with each other, where the first device is configured to: and responding to the log capturing instruction, and sending a remote diagnosis instruction to a log acquisition module of the second equipment by the fault detection module of the first equipment, wherein the remote diagnosis instruction comprises fault event information. The second device is configured to: and responding to the remote diagnosis instruction, the log acquisition module of the second device acquires fault event information from the remote diagnosis instruction, sends the fault event information to the fault management module, and informs the fault management module to acquire a log corresponding to the fault event information. And the fault management module of the second equipment acquires the fault log of the second equipment, and determines the fault log matched with the fault event information as a target fault log from the fault log according to the fault event information. According to the technical scheme, the log collection module sends the fault event information which is received from the first device and corresponds to the abnormal problem to the fault management module, and the fault management module determines the fault log matched with the fault event information as the target fault log from the obtained fault logs according to the fault event information, so that logs near the time point when the abnormal problem occurs are obtained in time.

In one implementation, the fault management module obtains a fault log obtained by the second device performing fault log dotting in at least one service field. By the technical scheme, the fault log corresponding to the service field can be obtained by dotting aiming at least one service field.

In a possible implementation manner, the obtaining of the fault log obtained by the second device performing fault log dotting in at least one service field includes: the log dotting calling module performs fault log dotting in at least one service field to obtain dotting information of at least one service field, and sends the dotting information of at least one service field to the dotting interface module; the dotting interface module determines a fault log according to dotting information of at least one service field; and the fault management module acquires a fault log from the dotting interface module. Through the technical scheme, the fault management module acquires the fault log which is subjected to dotting aiming at the service field from the dotting interface module.

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

In one implementation, the determining, by the fault management module, a fault log matched with the fault event information as a target fault log from the fault logs according to the fault event information includes: and determining the fault log matched with the fault event identity label as a target fault log from the fault logs according to the fault event identity label, or determining the fault log matched with the application package name as the target fault log from the fault logs according to the application package name. Through the technical scheme, the fault management module can determine that the fault log matched with the fault event identity label or the fault log matched with the application package name is 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 acquisition module sends the target fault log to a log uploading channel module; and uploading the target fault log to a log server by the log uploading channel module. According to the technical scheme, 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 uploading channel, so that logs near the time point of occurrence of the abnormal problem are uploaded to the log server in time.

In one implementation mode, a log acquisition module of the second device packs and compresses the target fault log, and sends the compressed target fault log to a log uploading channel module; and the log uploading channel module uploads the compressed target fault log to a log server. By the technical scheme, the target fault log can be compressed and then uploaded to the log server.

In one implementation mode, the log uploading channel module of the second device returns the target fault log or the compressed target fault log to the log collection module; and the log acquisition module uploads the return result to the fault detection module. Through the technical scheme, the log acquisition module can feed back the uploading result of the target fault log or the compressed target fault log to the fault detection module.

In one implementation, a log acquisition module of the second device responds to the feedback instruction to generate a diagnosis closing instruction; the log acquisition module sends a diagnosis closing instruction to the fault detection module to inform the fault detection module to quit remote diagnosis. Through the technical scheme, the fault detection module can quit remote diagnosis of the log according to the diagnosis closing instruction sent by the log acquisition module.

In one implementation, the second device sends a log capture instruction to the first device in response to a user operation.

In one implementation, the second device sends a log capture instruction to the remote diagnosis platform in response to the user operating the diagnosis analysis control. Through the technical scheme, the second equipment can respond to the operation that the user clicks the diagnosis and analysis control, and sends the log capturing instruction to the first equipment, so that the log capturing is realized.

In one implementation, a second device displays a first interface including a diagnostic analysis control; responding to the operation of clicking the diagnosis analysis control by the user, and displaying a second interface comprising the verification code field; and receiving the verification code input by the user through the verification code column, and sending a log capturing instruction to the remote diagnosis platform after the verification code passes verification. Through the technical scheme, the log capturing instruction is sent to the remote diagnosis platform after the verification of the verification code input by the user in the verification code column displayed on the second interface is passed, so that the log is captured.

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

In one implementation, the first device is further configured to: if the abnormal log dotting event corresponding to the fault event is uploaded by the second device, the acquired fault event information comprises a fault event identity label and an application package name; and if the second equipment does not upload the abnormal log dotting event corresponding to the fault event, the acquired fault event information comprises the range of the identity label of the fault event and the application package name. According to the technical scheme, when the abnormal log dotting event corresponding to the fault event is uploaded on the second device, the fault event information acquired by the first device comprises the fault event identity label and the application package name; when the second device does not upload the abnormal log dotting event corresponding to the fault event, the fault event information acquired by the first device comprises the range of the identity tag of the fault event and the application package name.

In one implementation, a fault detection module of the first device receives a log task which is input on a task interface by a user and contains fault event information through the task interface, and uses the log task as a remote diagnosis instruction. According to the technical scheme, the content of the remote diagnosis instruction can be set through the task interface.

In one implementation, the task interface includes a failure event identity tag field, an application package name field, and a failure event identity tag range field, where the failure event identity tag field is used to obtain an identity tag of a failure event, the failure event identity tag range field is used to obtain a range of the identity tag of the failure event, and the application package name field is used to obtain an application package name. According to the technical scheme, the range of the identity label of the fault event, the range of the application package name or the range of the identity label of the fault event are set and obtained through the task interface.

In a second aspect, an embodiment of the present application provides a log obtaining method, which is applied to a terminal device, and the method includes: the log acquisition module responds to the received remote diagnosis instruction and acquires fault event information from the remote diagnosis instruction; the log acquisition module sends the fault event information to the fault management module and informs the fault management module to acquire a log corresponding to the fault event information; and the fault management module acquires a fault log of the terminal equipment, and determines the fault log matched with the fault event information as a target fault log from the fault log according to the fault event information. According to the technical scheme, the log collection module sends the fault event information which is received from the first device and corresponds to the abnormal problem to the fault management module, and the fault management module determines the fault log matched with the fault event information as the target fault log from the obtained fault logs according to the fault event information, so that logs near the time point when the abnormal problem occurs are obtained in time.

In one implementation, the fault management module obtains a fault log obtained by performing fault log dotting on the terminal device in at least one service field. By the technical scheme, the fault log corresponding to the service field can be obtained by dotting aiming at least one service field.

In one implementation, obtaining a fault log obtained by a terminal device performing fault log dotting in at least one service domain includes: the log dotting calling module performs fault log dotting in at least one service field to obtain dotting information of at least one service field, and sends the dotting information of the service field to the dotting interface module; the dotting interface module determines a fault log according to dotting information of at least one service field; and the fault management module acquires a fault log from the dotting interface module. Through the technical scheme, the fault management module acquires the fault log which is subjected to dotting aiming at the service field from the dotting interface module.

In one implementation, the fault management module determines, from the fault log according to the fault event identity tag, that the fault log matched with the fault event identity tag is a target fault log, or determines, from the fault log according to the application package name, that the fault log matched with the application package name is the target fault log. Through the technical scheme, the fault management module can determine that the fault log matched with the fault event identity label or the fault log matched with the application package name is the target fault log.

In one implementation, the method further comprises: the fault management module sends the target fault log to the log acquisition module after determining the target fault log; the log acquisition module sends the target fault log to a log uploading channel module; and uploading the target fault log to a log server by the log uploading channel module. According to the technical scheme, 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 uploading channel, so that logs near the time point of occurrence of the abnormal problem are uploaded to the log server in time.

In one implementation, the method further comprises: the log acquisition module packs and compresses the target fault log and sends the compressed target fault log to the log uploading channel module; and the log uploading channel module uploads the compressed target fault log to a log server. By the technical scheme, the target fault log can be compressed and then uploaded to the log server.

In one implementation, the method further comprises: the log uploading channel module returns the target fault log or the compressed target fault log to the log acquisition module; and the log acquisition module uploads the return result to the fault detection module. Through the technical scheme, the log acquisition module can feed back the uploading result of the target fault log or the compressed target fault log to the fault detection module.

In one implementation, the method further comprises: the log acquisition module responds to the feedback instruction and generates a diagnosis closing instruction; the log acquisition module sends a diagnosis closing instruction to the fault detection module to inform the fault detection module to quit remote diagnosis. Through the technical scheme, the fault detection module can quit remote diagnosis of the log according to the diagnosis closing instruction sent by the log acquisition module.

In one implementation, the method further comprises: and responding to the operation of the user, and sending a log grabbing instruction to the remote diagnosis platform.

In one implementation, the sending the instruction to grab the log to the remote diagnosis platform in response to the operation of the user includes: and responding to the operation of the user on the diagnosis analysis control, and sending a log capturing instruction to the remote diagnosis platform. Through the technical scheme, the second equipment can respond to the operation that the user clicks the diagnosis analysis control of the applet and sends the log capturing instruction to the first equipment, so that the log capturing is realized.

In one implementation, the sending the instruction for grabbing the log to the remote diagnosis platform in response to the operation of the diagnosis analysis control by the user comprises: displaying a first interface, wherein a diagnosis analysis control is displayed on the first interface; responding to the operation of clicking the diagnosis analysis control by the user, displaying a second interface, and displaying the verification code column on the second interface; and receiving the verification code input by the user through the verification code column, and sending a log capturing instruction to the remote diagnosis platform after the verification code passes verification. Through the technical scheme, the log capturing instruction is sent to the remote diagnosis platform after the verification of the verification code input by the user in the verification code column displayed on the second interface is passed, so that the log is captured.

In one implementation, the method further comprises: and responding to the operation that the user clicks the log content viewing control on the second interface, and displaying a third interface, wherein the log content is displayed on the third interface. Through the technical scheme, the log content can be displayed on the third interface for the user to view by clicking the log content viewing control on the second interface.

In one implementation, the method further comprises: the fault management module saves the target fault log in a log service directory. Through the technical scheme, the target fault log can be stored.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory; wherein the processor is coupled to the memory; a memory for storing program instructions; and the processor is used for reading the program instructions stored in the memory so as to realize the log acquisition method.

In a fourth aspect, embodiments of the present application provide a computer storage medium storing program instructions that, when executed on an electronic device, cause the electronic device to perform a log obtaining method as described above.

In addition, the technical effects brought by the third to fourth aspects can be referred to the description related to the methods designed in the above methods, and are not repeated herein.

Drawings

Fig. 1 is a block diagram of a software structure of an electronic device according to an embodiment of the present application.

Fig. 2 is an architecture diagram of a log obtaining system according to an embodiment of the present application.

Fig. 3 is a flowchart of a log obtaining method in an embodiment of the present application.

Fig. 4a to 4d are application scenario diagrams of a terminal device sending a log capture instruction to a remote diagnosis platform according to another embodiment of the present application.

Fig. 5 is an application scenario diagram showing a diagnostic analysis sub-interface according to an embodiment of the present application.

FIG. 6 is a diagram illustrating a task interface according to an embodiment of the invention.

Fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.

Detailed Description

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of some embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or illustrations. Any embodiment or design described as "exemplary" or "e.g.," in some embodiments of the present application is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It should be understood that in this application, "/" means "or" means "unless otherwise indicated. For example, A/B may represent A or B. In some embodiments of the present application, "and/or" is only one kind of association relation describing an associated object, and means that there may be three kinds of relations. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. "at least one" means one or more. "plurality" means two or more than two. For example, at least one of a, b, or c, may represent: a, b, c, a and b, a and c, b and c, a, b and c.

The application provides a log obtaining method. The log obtaining method is applied to the electronic device 100. Referring to fig. 1, a block diagram of a software structure of an electronic device 100 according to an embodiment of the present application is shown. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system of the electronic device 100 is divided into four layers, which are an application layer, an application framework layer, an Android runtime (Android runtime) and system library layer, and a kernel layer from top to bottom.

The application layer may include a series of applications. As shown in fig. 1, the applications may include camera, gallery, calendar, phone, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.

As shown, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short 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. Such as management of call status (including on, off, etc.).

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

The notification manager enables applications to display notification information in a status bar, can be used to convey notification-type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the intelligent terminal vibrates, and the indicator light flickers.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

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

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, g.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

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

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Referring to fig. 2, an architecture diagram of a log acquisition system in an embodiment of the present application is shown. The log obtaining system 10 includes a remote diagnosis platform 20, a terminal device 30, and a log server 40. The remote diagnosis platform 20 is connected with the terminal device 30 in a communication mode, and the terminal device 30 is connected with the log server 40 in a communication mode. The remote diagnosis platform 20 is used for adding fault event information and sending the fault event information to the terminal device 30. The terminal device 30 is configured 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 herein, 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 diagnostic 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 uploading channel module 303, a log dotting calling module 304, and a dotting interface module 305. The modules in the present 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 uploading channel module 303 respectively. The log dotting calling module 304 is connected with the dotting interface module 305. Dotting interface module 305 is connected to fault management module 302. The functions of the respective modules in the log obtaining system including 10 will be described below with reference to the flow of the respective steps of the log obtaining method of fig. 3.

Referring to fig. 3, a flowchart of a log obtaining method according to an embodiment of the present application is shown. The method comprises the following steps.

In step S301, in response to the instruction to capture the log, 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, where the remote diagnosis instruction includes the fault event information.

In this embodiment, the terminal device 30 sends a log capture instruction to the remote diagnosis platform 20 in response to an operation by the user. The remote diagnosis platform 20 is configured to create a log task including fault event information, and send the log task to the terminal device 30. For example, referring to fig. 4a to 4d, there are shown application scenarios in which the terminal device 30 sends a log capture instruction to the remote diagnosis platform 20 according to an embodiment of the present application. In this embodiment, referring to fig. 4a, after clicking an applet displayed on the terminal device 30, a detection application interface 32 is displayed, for example, the applet is an intelligent detection applet of a glory mobile phone. It should be noted that the app icon of the applet is displayed on the app interface of the terminal device 30, and the user may open the detection app interface 32 of the applet by clicking the app icon of the applet on the app interface of the terminal device 30. In this embodiment, the terminal device 30 sends a log capture instruction to the remote diagnosis platform 20 in response to the operation of the user on the detection application interface 32. Specifically, when the operation of clicking the diagnostic analysis control 321 on the detection application interface 32 by the user is detected, the terminal device 30 displays the diagnostic analysis interface 320 (refer to fig. 4 b). The diagnostic analysis interface 320 displays a captcha field 322. The user obtains the verification code by sending a mobile phone number to the background system or contacting a customer service person by dialing a service hotline. 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 communicatively connected to the terminal device 30, or the background system may be the same device as the log server 40. In this embodiment, the verification code is a character string composed of numbers and letters, and is used to perform security verification on the capturing of the current log. In this embodiment, after the user inputs the acquired verification code in the verification code field 322, the terminal device 30 responds to the verification code, verifies the verification code, sends a log capturing instruction to the remote diagnosis platform 20 after the verification is passed, and displays a diagnosis analysis sub-interface 323 (refer to fig. 4c) for the user to view the captured log or exit the diagnosis of the log. Referring to fig. 5, an application scenario diagram showing a diagnostic analysis sub-interface 323 in an embodiment of the present application is shown. In this embodiment, after the verification of the verification code passes, the terminal device 30 further receives a notification message 31 sent by the background system and displays the notification message in a 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 diagnostic 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. The terminal device 30 responds to the operation of the user clicking the view log content control 324, and displays the matched log content for the user to view (refer to fig. 4 d). It should be noted that the log content displayed in fig. 4d may be displayed after the user clicks the view log content control 324 on the diagnosis and analysis sub-interface 323, or displayed after the user clicks the diagnosis and analysis control 321 on the detection application interface 32, or displayed after the verification of the verification code input in the verification code field 322 of the diagnosis and analysis sub-interface 323 passes. In this embodiment, the terminal device 30 closes the log diagnosis in response to the user clicking the feedback control 325. The terminal device 30 responds to the operation that the user clicks the exit control 326, and exits the diagnosis of the log. Terminal device 30 receives the user's description of the failure event through issue description window control 327.

In this embodiment, the fault detection module 201 of the remote diagnosis platform 20 responds to the log capturing instruction sent by the terminal device 30, and sends the remote diagnosis instruction carrying the fault event information to the log collection module 301 of the terminal device 30. It should be noted that the fault detection module 201 receives, through a task interface, a log task that includes fault event information and is input on the task interface 50 by a worker on the remote diagnosis platform 20 side, and uses the log task as a remote diagnosis instruction. Specifically, the fault detection module 201 displays the task interface 50 in response to the log capturing instruction sent by the terminal device 30. Referring to FIG. 6, a schematic diagram of a task interface 50 in one embodiment of the present application is shown. The task interface 50 includes a task name field, a timeout duration field, a fault event identification tag (ID) field, a fault event identification tag range field, an application package name field, and a fault type field. It should be noted that the task name field is used to obtain the name of the log task. In this embodiment, the system of the fault detection module 201 automatically allocates and enters the task name into the task name field. The timeout duration field is used for acquiring the timeout duration of the fault event of the log task. The failure event identity tag field is used for acquiring the identity tag of the failure event. The failure event identity tag range field is used to obtain the range of the identity tag of the failure event. The application package name field is used for acquiring the application package name of the log task. The fault type field is used to obtain the type of fault event. It should be noted that the types of the failure event include, but are not limited to, an application class (e.g., system/third-party application, social communication, multimedia, etc.), a reliability class (e.g., crash, restart, upgrade, etc.), a performance class (e.g., stuck, slow start, etc.), a power consumption class (e.g., cruising, heating, charging, etc.), a communication class (e.g., talking, short message, signal, data, etc.), a short-distance class (e.g., WiFi, bluetooth, GPS, NFC, etc.), and a device class (e.g., sensing, fingerprint, screen, infrared, etc.).

It should be noted that, before acquiring the instruction to capture the log, the remote diagnosis platform 20 may determine the fault event information according to whether the terminal device 30 uploads the abnormal log dotting event corresponding to the fault event. If the abnormal log dotting event corresponding to the fault event is uploaded by the terminal device 30, the fault event information acquired by the remote diagnosis platform 20 through the task interface 50 includes a fault event identity tag and an application package name. If the terminal device 30 does not upload the abnormal log dotting event corresponding to the fault event, the fault event information acquired by the remote diagnosis platform 20 through the task interface 50 includes: range of identity tag of failure event, application package name.

Step S302, in response to the remote diagnosis instruction, the log collection module 301 turns on the diagnosis switch, and obtains the 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 a log 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 log according to the fault event information, that the fault log matched with the fault event information is the target fault log.

In this embodiment, after the log collection module 301 turns on the diagnosis switch, the fault event identity tag and the application package name are obtained from the remote diagnosis instruction, or the range of the fault event identity tag and the application package name are obtained from the remote diagnosis instruction. The log collection module 301 sends the fault event label or the application package name to the fault management module 302, and notifies the fault management module 302 to obtain a log corresponding to the fault event label or a process log corresponding to the application package name. The fault management module 302 obtains a fault log obtained by dotting the fault log in a group of service fields by the terminal device 30, and determines the fault log matched with the fault event identity tag as a target fault log from the fault log according to the fault event identity tag, or determines the fault log matched with the application package name as the target fault log from the fault log according to the application package name.

In this embodiment, the acquiring, by the fault management module 302, the fault log obtained by the terminal device 30 performing fault log dotting in a group of service fields includes: the log dotting calling module 304 performs fault log dotting in the group of service fields to obtain dotting information of the group of service fields, and sends the dotting information of the group of service fields to the dotting interface module 305; the dotting interface module 305 determines a fault log according to the dotting information of the group of service fields; the fault management module 302 obtains a fault log from the dotting interface module 305. After obtaining the fault log, the fault management module 302 processes the fault log through the remote diagnosis plug-in to obtain a target fault log. Specifically, the remote diagnosis plug-in determines a fault log matched with the fault event identity label from the fault log according to the fault event identity label, or determines a fault log matched with the application package name from the fault log according to the application package name.

In this embodiment, the business fields include, but are not limited to, a stability field and a performance field. The stability field comprises at least one of ANR, crash, tombstone and kitchen. The performance field comprises at least one of starting time length, interface switching and response time length.

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.

In 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 diagnostic switch, and generates a diagnostic 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 closing instruction to the fault detection module 201 to notify the fault detection module 201 to exit remote diagnosis.

In step S310, the log collection module 301 sends the target fault log or the compressed target fault log to the log uploading channel module 303.

In step S311, the log uploading channel module 303 uploads the target fault log or the compressed target fault log to the log server 40, and returns an uploading result to the log collecting module 301.

In step S312, the log collection module 301 uploads the return result to the failure detection module 201.

Referring to fig. 7, a hardware structure diagram of an electronic device 100 according to an embodiment of the present application is shown. The electronic device 100 includes the remote diagnosis platform 20, the terminal device 30, or a combination of the 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, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR) device, a Virtual Reality (VR) device, an Artificial Intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, and/or a city device, and some embodiments of the present application do not particularly 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 (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a 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, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may 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 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

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

The UART interface is a universal serial data bus used for asynchronous communications. The bus may 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 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

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

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices 100, such as AR devices and the like.

It should be understood that the connection relationship between the modules according to the embodiment of the present invention is only illustrative, and is not limited to the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via 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. The charging management module 140 may also supply power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented 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.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may 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 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. 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, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 100 implements display functions via 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 an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

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 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The internal memory 121 may include one or more Random Access Memories (RAMs) and one or more non-volatile memories (NVMs).

The random access memory may include static random-access memory (SRAM), dynamic random-access memory (DRAM), synchronous dynamic random-access memory (SDRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM), such as fifth generation DDR SDRAM generally referred to as DDR5 SDRAM, and the like;

the nonvolatile memory may include a magnetic disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operation principle, may include single-level cells (SLC), multi-level cells (MLC), three-level cells (TLC), four-level cells (QLC), etc. according to the level order of the memory cells, and may include universal FLASH memory (UFS), embedded multimedia memory cards (eMMC), etc. according to the storage specification.

The random access memory may be read and written directly by the processor 110, may be used to store executable programs (e.g., machine instructions) of an operating system or other programs in operation, and may also be used to store data for users and applications, etc.

The nonvolatile memory may also store executable programs, data of users and applications, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 may be used to connect an external nonvolatile memory to extend the storage capability of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are saved in an external nonvolatile 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 a plurality of instructions, and when executed by the processor 110, can implement the log obtaining method executed on the electronic device 100 in the above embodiments to implement the log obtaining function of the electronic device 100.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a 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 disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be an open mobile electronic device 100 platform (OMTP) standard interface of 3.5mm, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects a shake angle of the electronic device 100, calculates a distance to be compensated for by the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for identifying the posture of the electronic equipment 100, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can 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 are no objects near the electronic device 100. The electronic device 100 can utilize the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to achieve the purpose of saving power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

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

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass. The bone conduction sensor 180M may also contact the human pulse to receive the blood pressure pulsation signal. In some embodiments, the bone conduction sensor 180M may also be disposed in a headset, integrated into a bone conduction headset. The audio module 170 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 180M, so as to implement a voice function. The application processor can analyze 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-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The present embodiment also provides a computer program product, which when running on a computer, causes the computer to execute the above related steps to implement the log obtaining method in the above embodiments.

In addition, some embodiments of the present application also provide an apparatus, which may be embodied as a chip, a component, or a module, and may include a processor and a memory connected to each other; the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored in the memory, so that the chip can execute the log obtaining method in the above-mentioned method embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the electronic device, the computer storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the module or unit is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of some embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of some embodiments of the present application and not for limiting, and although some embodiments of the present application are described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions can be made on the technical solutions of some embodiments of the present application without departing from the spirit and scope of the technical solutions of some embodiments of the present application.

Claims

1. A log obtaining system comprises a first device and a second device, wherein the first device and the second device are connected in communication, and the log obtaining system is characterized in that:

the first device is configured to:

responding to a log grabbing instruction, and sending a remote diagnosis instruction to a log acquisition module of the second equipment by a fault detection module of the first equipment, wherein the remote diagnosis instruction comprises fault event information;

the second device is configured to:

responding to the remote diagnosis instruction, and acquiring fault event information from the remote diagnosis instruction;

the log acquisition module sends the fault event information to a fault management module and informs the fault management module to acquire a log corresponding to the fault event information;

and the fault management module acquires the fault log of the second equipment, and determines the fault log matched with the fault event information as a target fault log from the fault log according to the fault event information.

2. The log acquisition system of claim 1, wherein the fault management module to acquire the fault log of the second device comprises:

and acquiring a fault log obtained by the second device performing fault log dotting in at least one service field.

3. The log obtaining system of claim 2, wherein the obtaining the fault log obtained by the second device performing fault log dotting in at least one business domain comprises:

the log dotting calling module performs fault log dotting in the at least one service field to obtain dotting information of the at least one service field, and sends the dotting information of the at least one service field to the dotting interface module;

the dotting interface module determines a fault log according to the dotting information of the at least one service field;

and the fault management module acquires a fault log from the dotting interface module.

4. The log acquisition system as in claim 1, wherein the failure event information comprises a failure event identity tag or an application package name.

5. The log obtaining system according to claim 4, wherein the determining, by the fault management module, from the fault logs according to the fault event information that the fault log matching the fault event information is a target fault log comprises:

and determining a fault log matched with the fault event identity label as a target fault log from the fault log according to the fault event identity label, or determining a fault log matched with the application packet name as a target fault log from the fault log according to the application packet name.

6. The log acquisition system of claim 1, wherein the second device is further configured to:

the fault management module sends a target fault log to a log acquisition module after determining the target fault log;

the log acquisition module sends the target fault log to a log uploading channel module;

and the log uploading channel module uploads the target fault log to a log server.

7. The log acquisition system of claim 6, wherein the second device is further configured to:

the log acquisition module packs and compresses the target fault log and sends the compressed target fault log to a log uploading channel module;

and the log uploading channel module uploads the compressed target fault log to the log server.

8. The log acquisition system of claim 7, wherein the second device is further configured to:

the log uploading channel module returns the target fault log or the compressed target fault log to a log acquisition module;

and the log acquisition module uploads the return result to the fault detection module.

9. The log acquisition system of claim 6, wherein the second device is further configured to:

the log acquisition module responds to the feedback instruction and generates a diagnosis closing instruction;

and the log acquisition module sends the diagnosis closing instruction to the fault detection module so as to inform the fault detection module to quit remote diagnosis.

10. The log acquisition system of claim 1, wherein the second device is further configured to:

and responding to the operation of a user, and sending the log grabbing instruction to the first equipment.

11. The log acquisition system as claimed in claim 10, wherein said second device sending said instruction to grab the log to said first device in response to a user operation comprises:

and responding to the operation of the user on the diagnosis analysis control, and sending the log grabbing instruction to a remote diagnosis platform.

12. The log acquisition system as in claim 11, wherein sending the log scraping instructions to a remote diagnostic platform in response to user operation of a diagnostic analysis control comprises:

displaying a first interface on which a diagnostic analysis control is displayed;

responding to the operation of clicking the diagnosis analysis control by a user, and displaying a second interface on which a verification code column is displayed; and

and receiving a verification code input by a user through the verification code column, and sending the log capturing instruction to a remote diagnosis platform after the verification code passes verification.

13. The log acquisition system of claim 12, wherein the second device is further configured to:

and responding to the operation that the user clicks the log content viewing control on the second interface, and displaying a third interface, wherein the log content is displayed on the third interface.

14. The log acquisition system of claim 1, wherein the first device is further configured to:

if the abnormal log dotting event corresponding to the fault event is uploaded by the second device, the obtained fault event information comprises a fault event identity label and an application package name;

and if the second equipment does not upload the abnormal log dotting event corresponding to the fault event, the acquired fault event information comprises the range of the identity label of the fault event and the application package name.

15. The log acquisition system of claim 14, wherein the first device is further configured to:

and the fault detection module receives a log task which is input on the task interface by a user and contains fault event information through a task interface, and takes the log task as the remote diagnosis instruction.

16. The log retrieval system of claim 15, wherein the task interface comprises a failure event identity tag field for retrieving an identity tag of a failure event, an application package name field for retrieving an application package name, and a failure event identity tag scope field for retrieving a scope of an identity tag of a failure event.

17. A log obtaining method is applied to terminal equipment, and is characterized by comprising the following steps:

the log acquisition module responds to the received remote diagnosis instruction and acquires fault event information from the remote diagnosis instruction;

and the fault management module acquires the fault log of the terminal equipment, and determines the fault log matched with the fault event information as a target fault log from the fault log according to the fault event information.

18. The log obtaining method according to claim 17, wherein the obtaining of the fault log of the terminal device by the fault management module includes:

and acquiring a fault log obtained by the terminal equipment by performing fault log dotting in at least one service field.

19. The log obtaining method of claim 18, wherein the obtaining the fault log obtained by the terminal device performing fault log dotting in at least one service domain comprises:

20. The log retrieval method of claim 17, wherein the failure event information comprises a failure event identity tag or an application package name.

21. The log obtaining method according to claim 20, wherein the determining, by the fault management module, the fault log that matches the fault event information from the fault logs as a target fault log according to the fault event information includes:

22. The log acquisition method as in claim 17, wherein the method further comprises:

23. The log acquisition method as in claim 22, wherein the method further comprises:

24. The log acquisition method as in claim 23, wherein the method further comprises:

25. The log acquisition method as in claim 17, wherein the method further comprises:

26. The log acquisition method as in claim 17, wherein the method further comprises:

and responding to the operation of the user, and sending a log grabbing instruction to the remote diagnosis platform.

27. The log retrieval method of claim 26, wherein said sending a log grab instruction to the remote diagnostic platform in response to a user action comprises:

28. The log acquisition method of claim 27, wherein said sending the log scraping instructions to a remote diagnostic platform in response to user operation of a diagnostic analysis control comprises:

29. The log acquisition method as in claim 28, wherein the method further comprises:

30. An electronic device comprising a processor, a memory; wherein the processor is coupled with the memory;

the memory to store program instructions;

the processor, configured to read the program instructions stored in the memory to implement the log obtaining method according to any one of claims 17 to 29.

31. A computer-readable storage medium storing program instructions that, when run on an electronic device, cause the electronic device to perform the log obtaining method according to any one of claims 17 to 29.