Fault analysis method and device, electronic equipment and medium

Abstract

The invention provides a fault analysis method and device, electronic equipment and a medium, and relates to the technical field of testing, when a call test is carried out on a mobile terminal, fault analysis is automatically carried out on a to-be-analyzed log generated in the testing process, a fault analysis result is obtained, so that the fault analysis speed is improved, the mobile terminal is tested, and therefore the fault analysis efficiency is improved. When the network fault occurs, the fault analysis result corresponding to the network fault is output and displayed, so that testers and research and development personnel can know the cause of the call fault, the testers and the research and development personnel do not need to check and maintain the fault, and the time of the testers and the research and development personnel is saved; when the mobile terminal fails, the fault analysis result corresponding to the mobile terminal is output and displayed, and the to-be-analyzed log capable of reflecting the fault of the mobile terminal is grabbed and stored to the preset position, so that research and development personnel can analyze the fault in combination with the output fault analysis result.

Description

Technical Field

[0001] The present disclosure relates to the field of testing technology, and in particular to a fault analysis method, device, electronic equipment and medium. Background Art

[0002] During the development phase of mobile terminals such as mobile phones, tablet computers, and smart watches, testers will test the call functions of mobile terminals in different locations and network environments. The mobile terminal generates logs during the test process, and the testers export the logs, and the R&D personnel perform fault analysis based on the logs. However, this method is slow to analyze fault problems. Summary of the invention

[0003] In order to overcome the problems existing in the related art, the present disclosure provides a fault analysis method, device, electronic device and medium.

[0004] According to a first aspect of an embodiment of the present disclosure, a fault analysis method is provided, the method comprising: when performing a call test on a mobile terminal through a network, obtaining a log to be analyzed generated by the mobile terminal; performing a fault analysis on the log to be analyzed to obtain a fault analysis result; if the fault analysis result represents the network fault, outputting the fault analysis result; or, if the fault analysis result represents the mobile terminal fault, outputting the fault analysis result and capturing the log to be analyzed and storing it in a preset location.

[0005] Optionally, the fault analysis result characterizes the network fault, and the fault analysis of the log to be analyzed to obtain the fault analysis result further includes: establishing a communication connection with the network; monitoring communication messages sent by the network; the fault analysis of the log to be analyzed to obtain the fault analysis result includes: when the communication message is not monitored, if an abnormal message corresponding to the network is recorded in the log to be analyzed, outputting the fault analysis result for the abnormal message; if the abnormal message corresponding to the network is not recorded in the log to be analyzed, obtaining a preset analysis result.

[0006] Optionally, the fault analysis result characterizes the fault of the mobile terminal, the mobile terminal is the called end, and the fault analysis is performed on the log to be analyzed to obtain the fault analysis result, including: when no invitation message is received, obtaining the network status recorded in the log to be analyzed; if the network status does not meet the preset network status, obtaining the fault analysis result for the network status.

[0007] Optionally, the method also includes: if the network condition meets the preset network condition, obtaining a call message from the log to be analyzed; if the call message indicates that there is a missed call, outputting a fault analysis result corresponding to the missed call; if the call message indicates that there is no missed call, obtaining the RF resource occupancy from the log to be analyzed, and obtaining the fault analysis result based on the RF resource occupancy.

[0008] Optionally, obtaining the fault analysis result according to the occupancy status of the radio frequency resources includes: if the radio frequency resources are occupied, outputting the fault analysis result corresponding to the occupation of the radio frequency resources; if the radio frequency resources are not occupied, obtaining a preset analysis result.

[0009] Optionally, the fault analysis result characterizes the mobile terminal fault, the mobile terminal is a calling terminal, and the fault analysis is performed on the log to be analyzed and the fault analysis result is output, including: when no invitation message is sent, obtaining network registration information from the log to be analyzed; and obtaining the fault analysis result based on the network registration information.

[0010] Optionally, obtaining the fault analysis result according to the network registration information includes: if the network registration information indicates that the mobile terminal is not registered with the network, obtaining a fault analysis result corresponding to the network not being registered.

[0011] Optionally, obtaining the fault analysis result according to the network registration information includes: if the network registration information indicates that the mobile terminal has registered with the network, obtaining the network status recorded in the log to be analyzed; and obtaining the fault analysis result according to the network status.

[0012] Optionally, obtaining the fault analysis result according to the network condition includes: if the network condition does not meet the preset network condition, obtaining the fault analysis result corresponding to the network condition; if the network condition meets the preset network condition, obtaining the preset analysis result.

[0013] Optionally, the network comprises an IP Multimedia Subsystem network and / or a circuit switched network.

[0014] Optionally, the log to be analyzed includes a baseband processor side log.

[0015] According to a second aspect of an embodiment of the present disclosure, a fault analysis device is provided, the device comprising: an acquisition module, used to acquire a log to be analyzed generated by a mobile terminal when a call test is performed on the mobile terminal through a network; an analysis module, used to perform a fault analysis on the log to be analyzed and obtain a fault analysis result; an output module, used to output the fault analysis result if the fault analysis result characterizes the network fault; or, if the fault analysis result characterizes the mobile terminal fault, output the fault analysis result and capture the log to be analyzed and store it in a preset location.

[0016] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to implement the steps of the method described in the first aspect when executing the instructions.

[0017] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the fault analysis method provided in the first aspect of the present disclosure are implemented.

[0018] The fault analysis method, device, electronic device and medium provided by the present invention automatically perform fault analysis on the logs to be analyzed generated during the test process when performing a call test on the mobile terminal, and obtain fault analysis results to improve the fault analysis speed. In addition, the present invention needs to test the mobile terminal. Therefore, when a network failure occurs, the fault analysis results corresponding to the network failure are output and displayed, so that the testers and R&D personnel can know the cause of the call failure. The testers and R&D personnel do not need to troubleshoot and maintain the failure, which saves the time of the testers and R&D personnel. When the mobile terminal fails, the fault analysis results corresponding to the mobile terminal are output and displayed, and the logs to be analyzed that can reflect the mobile terminal failure are captured and stored in a preset location, so that the R&D personnel can analyze the failure in combination with the output fault analysis results.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0021] Figure 1 is a schematic diagram of an application environment of a fault analysis method according to an exemplary embodiment;

[0022] Figure 2 is a flow chart of a fault analysis method according to an exemplary embodiment;

[0023] Figure 3 is a block diagram of a mobile terminal according to an exemplary embodiment;

[0024] Figure 4 is a flow chart of a fault analysis method according to another exemplary embodiment;

[0025] Figure 5 is a flow chart of a fault analysis method according to another exemplary embodiment;

[0026] Figure 6 is a block diagram of a fault analysis device according to an exemplary embodiment;

[0027] Figure 7 is a block diagram of an electronic device for a fault analysis method according to an exemplary embodiment;

[0028] Figure 8 The invention is a block diagram showing a device for applying a fault analysis method according to an exemplary embodiment. DETAILED DESCRIPTION

[0029] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0030] It should be noted that all actions of acquiring signals, information or data in the present disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the device is located and with the authorization given by the owner of the corresponding device.

[0031] During the development phase of mobile terminals such as mobile phones, tablet computers, and smart watches, testers will test the call functions of mobile terminals in different locations and network environments. The mobile terminal generates logs during the test process, and the testers export the logs. The R&D personnel then perform fault analysis based on the logs to find problems such as failure to connect and automatic hang-up during the call, so as to improve these problems. However, this method is slow to analyze fault problems.

[0032] Moreover, in the prior art, testers usually export all logs and provide them to R&D personnel. However, not all logs can reflect problems with mobile terminals. For example, a large part of the logs are network problems. Since this test is for mobile terminals, network problems do not need to be solved or improved by R&D personnel. Therefore, R&D personnel need to filter out logs that can reflect mobile terminal problems from all logs. The process of R&D personnel filtering logs consumes a lot of time, further exacerbating the problem of slow subsequent fault analysis.

[0033] In response to the above technical problems, the inventors have discovered and proposed a fault analysis method, device, electronic device and medium after long-term research. When performing a call test on a mobile terminal, the logs generated during the test process are automatically analyzed for faults, and the fault analysis results are output to improve the speed of fault analysis.

[0034] In order to better understand a fault analysis method, device, electronic device and medium provided by the embodiments of the present disclosure, the application environment applicable to the embodiments of the present disclosure is first described below.

[0035] See also Figure 1 The application environment includes a mobile terminal 100, which is a mobile terminal to be tested for a call. To this end, the mobile terminal needs to be connected to a network for subsequent testing.

[0036] Please continue reading Figure 1, one way for the mobile terminal to connect to the network may be that the mobile terminal 100 establishes a communication connection with the server 210, wherein the server 210 may be a traditional server or a cloud server, which is not specifically limited here. A test program (such as an APP, a WeChat applet, a voice program, etc.) may be installed on the mobile terminal 100, and a corresponding test program may also be installed on the server 210, and the tester establishes a communication connection between the mobile terminal 100 and the server 210 based on the test program. The tester may perform a communication test by inputting text information, voice information, image information, or video information based on the test program on the mobile terminal 100. After the mobile terminal 100 receives the above information output by the tester, the information may be sent to the server 210, and the test program on the server 210 responds to the above information to realize the interaction between the mobile terminal 100 and the server 210, so as to complete the call test. Specifically, the test program of the server 210 may interact with the tester based on a virtual robot. For example, the test program of the server 210 is based on the above information input by the tester, and answers based on the virtual robot. Among them, a virtual robot is a software program based on visual graphics, which can present a robot form that simulates biological behavior or thoughts to the user after being executed. A virtual robot can be a robot that simulates a real person, such as a robot that looks like a real person based on the user's own or other people's form, or a robot with an animation effect, such as a robot in the form of an animal or a cartoon character.

[0037] Please continue reading Figure 1 , another way for the mobile terminal to connect to the network may be that the mobile terminal 100 establishes a communication connection with the base station 220. And, the base station 220 establishes a communication connection with another mobile terminal 300. A test program may be installed on both the mobile terminal 100 and the mobile terminal 300. The tester may perform a communication test by inputting text information, voice information, image information or video information based on the test program on the mobile terminal 100. After receiving the above information output by the tester, the mobile terminal 100 may send the information to the base station 220, and the base station 220 sends the information to the mobile terminal 300. The tester of the mobile terminal 300 replies to the information sent by the base station, and the reply information may be in the form of text information, voice information, image information or video information. The mobile terminal 300 sends the reply information of the tester to the mobile terminal 100 through the base station 200, so as to realize the interaction between the mobile terminal 100 and the mobile terminal 300, so as to complete the call test. Among them, when the mobile terminal 100 initiates a call session, the mobile terminal 300 receives the call. Alternatively, when the mobile terminal 300 initiates a call session, the mobile terminal 100 receives the call.

[0038] The above application environment is only an example for the convenience of understanding. It should be understood that the embodiments of the present disclosure are not limited to the above application environment.

[0039] The fault analysis method, device, electronic device and medium provided in the embodiments of the present disclosure will be described in detail below through specific embodiments.

[0040] See also Figure 2 , Figure 2 is a flowchart of a fault analysis method shown in an exemplary embodiment of the present disclosure, and the fault analysis method can be applied to mobile terminals, Figure 6 The fault analysis device 400 shown, Figure 7 The electronic device 800 shown, Figure 8 The device 1900 and the computer readable storage medium shown in the figure. In this embodiment, the application to a mobile terminal is taken as an example, wherein the mobile terminal includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a desktop computer, a wearable electronic device, etc. Figure 2 The process shown is described in detail, and the fault analysis method may specifically include the following steps:

[0041] Step S110: when a call test is performed on a mobile terminal through a network, a log to be analyzed generated by the mobile terminal is obtained.

[0042] The mobile terminal is placed in a network environment, and a call test is performed on the mobile terminal by making and answering calls. During the test, the mobile terminal generates a log to be analyzed. The log to be analyzed can record all events, errors, or activities during the call test.

[0043] The network environment in which the mobile terminal is located may be a single network environment, for example, the environment includes an IMS (IP Multimedia Subsystem) network or a CS (Circuit Switched Domain) network. The network environment in which the mobile terminal is located may be an environment formed by a combination of multiple networks, for example, the environment includes an IMS network and a CS network.

[0044] In one embodiment, a storage location of the log is preset, and after the log is generated, it is automatically stored in the storage location. The mobile terminal reads the log to be analyzed from the storage location in real time. The method of reading the log to be analyzed in real time can quickly and timely obtain the generated log to be analyzed, which is convenient for subsequent rapid analysis of the log and improves the speed of fault analysis.

[0045] In another embodiment, a storage location of the log is preset, and after the log is generated, it is automatically stored in the storage location. The mobile terminal reads the log to be analyzed from the storage location according to a preset period. Compared with the real-time reading method, this embodiment can reduce the data flow and computing load of the mobile terminal.

[0046] Step S120: Perform fault analysis on the log to be analyzed to obtain a fault analysis result.

[0047] Automatically perform fault analysis on the logs to be analyzed and obtain fault analysis results.

[0048] In one implementation, automatic fault analysis of the log to be analyzed may be performed in the following manner: presetting a fault event, reading the event recorded in the log to be analyzed, and obtaining a corresponding fault analysis result if the recorded event matches the fault event.

[0049] Step S130: if the fault analysis result represents the network fault, output the fault analysis result; or, if the fault analysis result represents the mobile terminal fault, output the fault analysis result and capture the log to be analyzed and store it in a preset location.

[0050] In one embodiment, the mobile terminal includes a display screen, and the fault analysis result is output and displayed on the display screen.

[0051] Optionally, in the case where the fault analysis result characterizes the fault of the mobile terminal, the fault analysis result and the log to be analyzed are bound, and the fault analysis result and the log to be analyzed can be output on the display screen at the same time for analysis by the R&D personnel. Alternatively, the fault analysis result can be output separately on the display screen, and when the R&D personnel clicks on the control on the display screen, or clicks on the fault analysis result displayed on the display screen, the log to be analyzed bound to the fault analysis result is displayed on the display screen, so that the R&D personnel can analyze and view the fault in combination with the fault analysis result and the log to be analyzed.

[0052] The fault analysis method provided in this embodiment automatically performs fault analysis on the logs to be analyzed generated during the test process when performing a call test on the mobile terminal, and obtains fault analysis results to improve the speed of fault analysis. In addition, this embodiment tests the mobile terminal, so when a network failure occurs, the fault analysis results corresponding to the network failure are output and displayed, so that the testers and R&D personnel can know the cause of the call failure. The testers and R&D personnel do not need to troubleshoot and maintain the failure, which saves the time of the testers and R&D personnel. When the mobile terminal fails, the fault analysis results corresponding to the mobile terminal are output and displayed, and the logs to be analyzed that can reflect the mobile terminal failure are captured and stored in a preset location, so that the R&D personnel can analyze the failure in combination with the output fault analysis results.

[0053] When the mobile terminal is used as the MT (Mobile Termination Call, called party) or MO (Mobile Origination Call, calling party), during the test of the mobile terminal, the factors that cause the call problem may be network factors, so the network factors can be analyzed for faults. In one embodiment, the mobile terminal establishes a communication connection with the network and monitors the communication messages sent by the network, wherein the communication messages can be Figure 1 The message sent by the test program of the server 210 may also be Figure 1 The message replied by another mobile terminal forwarded by the base station 220 in the communication message. When the communication message is monitored, it means that the mobile terminal can communicate normally, there is no fault or abnormality, and there is no need to perform fault analysis on the log to be analyzed. Or, when the communication message is not monitored, if the abnormal message corresponding to the network is recorded in the log to be analyzed, the fault analysis result for the abnormal message is obtained. Among them, the abnormal message may include the abnormal status code corresponding to the network, etc. For example, the mobile terminal is connected to the IMS network, and its corresponding abnormal status code includes the status code of the client request error, such as status code 400Bad Request, which indicates that the request is invalid, which may be due to incorrect request parameters or incorrect format; status code 401Unauthorized, which indicates that it is not authorized, and identity authentication or valid credentials are required; status code 404Not Found, which indicates that the resource is not found and the requested resource does not exist. Its corresponding abnormal status code also includes a status code indicating that an error occurred in the server when processing the request, such as status code 5001Internal Server Error, which indicates an internal error in the server, which may be due to a code error or a server configuration problem. The abnormal message may also include a cancel message, which indicates that the connection with the mobile terminal is canceled due to factors such as network busyness or failure. When the communication message is not monitored, if the abnormal message corresponding to the network is not recorded in the log to be analyzed, the preset analysis result is obtained. For example, the preset analysis result may be "unknown problem", and the text "unknown problem" is output on the display screen. Optionally, when outputting the preset analysis result, it can be combined with the log to be analyzed, for example, the text "call connection failure caused by unknown problem" is output on the display screen.

[0054] In the call test of the mobile terminal, it is usually a process of making a call through the mobile terminal to test the communication quality and function of the mobile terminal. In the process of testing the mobile terminal, at least one aspect of the content such as call quality, signal strength, connectivity with the network, and functional testing may be involved. Among them, the content tested by the functional test may be call transfer, hands-free call, mute, etc. As follows, in one embodiment, when the mobile terminal is used as the MT end, the method of performing fault analysis may include analyzing the mobile terminal fault including analyzing the network status. Exemplarily, the invitation message is a message sent by the MO end to request the MT end to establish a communication connection. When the MT end does not receive the invite message, the network status recorded in the log to be analyzed is obtained, wherein the network status includes RSIP (Received Signal Strength Indication, received signal strength), network speed, bandwidth, throughput and other parameters. If the network status does not meet the preset network status, it means that the network quality is poor, and the fault analysis result for the network status is obtained. For example, the network status includes the network speed. If the network speed is lower than the preset network speed, it is determined that the network status does not meet the preset network status, and the fault analysis result for the network speed is obtained. The fault analysis results can be output in combination with the logs to be analyzed, for example, the text "poor network quality leads to missed invitation information" is displayed on the display screen. R&D personnel can adjust the parameters of the antenna or RF module of the mobile terminal according to the displayed text, or modify the call-related applications on the mobile terminal.

[0055] Optionally, poor network quality may also lead to problems such as missed call messages and call interruptions. In the case of poor network quality, the mobile terminal fault analysis may also include analyzing call (paging) messages. For example, if the network condition meets the preset network condition, the call message is obtained from the log to be analyzed. It can be understood that the log to be analyzed records call messages, which may be MO calls, paging requests, paging errors, missed calls, etc. Among them, missed calls can be detected by counting the number of calls of the MO in the call message and the actual number of calls of the MT. If the two numbers are inconsistent, it indicates that there is a missed call. On the contrary, if the two numbers are consistent, it indicates that there is no missed call. If the call message indicates that there is a missed call, the fault analysis result corresponding to the missed call is obtained, for example, the text "paging was missed during the called period, resulting in the failure of the called party" is output on the display screen.

[0056] Optionally, the cause of missed calls may be the allocation of RF resources, silence or shutdown, etc. If multiple SIM (Subscriber Identity Module) cards are installed on the mobile terminal, and multiple SIM cards share the RF (Radio Frequency) module of the mobile terminal, in this case, the occupancy of RF resources can also be considered. For example, if the call message indicates that there is no missed call, the occupancy of the radio frequency RF resources is obtained from the log to be analyzed, and the fault analysis result is obtained based on the occupancy of the radio frequency RF resources. Exemplarily, if the RF resources are occupied, the fault analysis result corresponding to the occupation of the RF resources is output, for example, the text "Another card on the MT side occupies the RF resources, resulting in a call failure" is output on the display screen; if the RF resources are not occupied, a preset analysis result is obtained, for example, the text "Unknown problem" is output on the display screen.

[0057] In this implementation, a fault analysis is first performed on the network status, then on the call message, and then on the RF resources, gradually analyzing from large fault problems to small fault problems. This makes it easier and faster to obtain fault analysis results, making it easier for R&D personnel to improve the mobile terminal based on the fault analysis results.

[0058] It should be noted that the method of fault analysis of the log to be analyzed is not limited to the above implementation mode, where fault analysis is performed in sequence from network status, call message, and RF resource occupation status. For example, other analysis orders may be used, such as performing fault analysis in sequence from call message, RF resource, and network status. Furthermore, the log to be analyzed is not limited to the analysis of call message, RF resource, and network status. According to the content of the log to be analyzed, fault analysis in other aspects such as call interruption, network registration information, etc. may also be performed.

[0059] In another embodiment, when the mobile terminal is used as the MO end, the analysis of the log to be analyzed may include analyzing the network registration information, for example, when the invitation message is not sent, the network registration information is obtained from the log to be analyzed, such as obtaining the registration information of the IMS network and / or the CS network. The fault analysis result is obtained according to the network registration information. If the network registration information indicates that the mobile terminal is not registered with the network, the fault analysis result corresponding to the network unregistration is obtained, for example, the text "IMS domain and CS domain are not registered, and calls cannot be made" is output on the display screen. Or, if the network registration information indicates that the mobile terminal has registered with the network, the network status recorded in the log to be analyzed is obtained, and the fault analysis result is output according to the network status. If the network status does not meet the preset network status, indicating that the network quality is poor, the fault analysis result corresponding to the network status is output, for example, the text "poor network environment quality may cause the MO end to fail to initiate a call" is output on the display screen. On the contrary, if the network status meets the preset network status, the preset analysis result is output, for example, the text "unknown problem causes the MO end to be unable to initiate a call" is output on the display screen.

[0060] In this embodiment, fault analysis is performed step by step on the logs to be analyzed on the MO side from network registration information to network status, and the fault analysis results are automatically output, which improves the speed of fault analysis and facilitates R&D personnel to improve the mobile terminal based on the fault analysis results.

[0061] It should be noted that the method of analyzing the fault of the log to be analyzed is not limited to the above implementation mode. It is also possible to first analyze the network status recorded in the log to be analyzed, and then analyze the network registration information.

[0062] When conducting a call test on a mobile terminal, a large part of the logs are network problems. Since this test is for mobile terminals, the problems that occur in the network do not need to be solved or improved by R&D personnel. Therefore, R&D personnel need to filter out logs that can reflect mobile terminal problems from all logs. In order to facilitate R&D personnel to directly view logs that can reflect mobile terminal problems, the method also includes: capturing the logs to be analyzed and storing them in a preset location. The generated logs are automatically stored in the storage location. In order to facilitate R&D personnel to make further judgments through the logs, the logs that can reflect the problems of the mobile terminal are captured and stored separately in the preset location.

[0063] In this implementation, logs that can reflect mobile terminal problems are stored in a preset location, and R&D personnel can directly obtain the logs from the preset location to facilitate improvements to the mobile terminal. There is no need to filter out logs reflecting mobile terminal problems one by one from a large number of logs, which effectively improves the speed and accuracy of R&D personnel in locating problems.

[0064] Optionally, the fault analysis result can also be bound to the log to be analyzed that represents the fault and the fault analysis result, and then the bound fault analysis result and the log to be analyzed can be output to a display screen for display. When R&D personnel analyze mobile terminal faults based on the log to be analyzed, the automatically generated fault analysis results can serve as a reference, provide further operational guidance to the R&D personnel, and improve the speed of locating faults.

[0065] The mobile terminal includes an AP (Application Processor), on which the operating system and applications on the mobile terminal run. The mobile terminal also includes a BP (Baseband Processor), on which the RF control software responsible for communication runs. Figure 3 The mobile terminal includes an application processor 10 and a baseband processor 14. The wireless interface layer 13 is used to provide a communication interface. The application processor 10 and the baseband processor 14 communicate through the wireless interface layer 13. The mobile terminal also includes a display interface 11 and a mobile phone control program 12. The mobile phone control program 12 runs on the application processor 10. Since the present disclosure performs a call test on the mobile terminal and the baseband processor 14 is responsible for communication, the log to be analyzed in the present disclosure includes the baseband processor BP side log. By performing fault analysis on the BP side log, the fault of the mobile terminal in the call test can be known.

[0066] Optionally, see Figure 4 The present disclosure provides a fault analysis method, comprising the following steps:

[0067] Step S201, the control program analyzes the MT BP side log in real time.

[0068] Step S202: Whether an invite message is received.

[0069] If an invite message is received, the process proceeds to step S210; if not, the process proceeds to step S203.

[0070] Step S203: Whether the network quality is poor.

[0071] If yes, the process goes to step S204, if no, the process goes to step S205.

[0072] Step S204: The interface prompts “Poor network quality may result in missed invite messages” and captures BP logs.

[0073] Step S205: Check whether paging is missed.

[0074] If yes, the process goes to step S206, if no, the process goes to step S207.

[0075] Step S206: The interface displays a prompt "The called device missed paging, resulting in call failure", and captures the BP log.

[0076] Step S207: Check whether the RF resources are occupied.

[0077] If yes, the process goes to step S208, if no, the process goes to step S209.

[0078] Step S208: The display interface prompts "Another card of MT occupies RF resources, resulting in call failure", and captures BP logs.

[0079] Step S209: The interface prompts "Unknown problem leads to missed invite message" and captures the BP log.

[0080] Step S210: Establish a call connection, and monitor the network side's reply message during the process.

[0081] Step S211: Whether the network sends an abnormal message.

[0082] If yes, the process goes to step S213, if no, the process goes to step S212.

[0083] Step S212: The interface prompts "An unknown problem caused the call connection to fail" and captures the BP log.

[0084] Step S213: The interface prompts "Network side is abnormal, so the call is released actively", and the BP log is not captured.

[0085] The specific contents of steps S201 to S213 refer to the above embodiments and will not be described again here.

[0086] Optionally, see Figure 5 The present disclosure provides a fault analysis method, comprising the following steps:

[0087] Step S301, the control program analyzes the MO end BP side log in real time.

[0088] Step S302: whether to report an invite message.

[0089] If yes, the process goes to step S308, if no, the process goes to step S303.

[0090] Step S303: Whether the IMS and CS are registered.

[0091] If yes, the process goes to step S303, if no, the process goes to step S305.

[0092] Step S304: The interface prompts “IMS domain and CS domain are not registered, calls cannot be made”, and the BP log is captured.

[0093] Step S305: Whether the network quality is poor.

[0094] If yes, the process goes to step S306, if no, the process goes to step S307.

[0095] Step S306: The interface prompts "Poor network quality may cause MO call failure" and captures the BP log.

[0096] Step S307: The display interface prompts "An unknown problem causes the MO end to be unable to initiate a call" and captures the BP log.

[0097] Step S308: Establish a call connection, and monitor the network side's reply message during the process.

[0098] Step S309: Whether the network sends an abnormal message.

[0099] If yes, the process goes to step S311, if no, the process goes to step S310.

[0100] Step S310: The interface prompts "Unknown problem caused the call connection to fail" and captures the BP log.

[0101] Step S311: The display interface prompts "Network side abnormality, so the call is released actively", and the BP log is not captured.

[0102] The specific contents of steps S301 to S311 refer to the above embodiments and will not be described again here.

[0103] Based on the same inventive concept, the present disclosure also provides a fault analysis device, see Figure 6 , the fault analysis device 400 comprises:

[0104] The acquisition module 410 is used to acquire the log to be analyzed generated by the mobile terminal when performing a call test on the mobile terminal;

[0105] The analysis module 420 is used to perform fault analysis on the log to be analyzed and output the fault analysis result;

[0106] The output module 430 is used to output the fault analysis result if the fault analysis result represents the network fault; or, if the fault analysis result represents the mobile terminal fault, output the fault analysis result and capture the log to be analyzed and store it in a preset location.

[0107] Regarding the fault analysis device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0108] The present disclosure also provides a computer-readable storage medium having computer program instructions stored thereon, and the program instructions, when executed by a processor, implement the steps of the fault analysis method provided by the present disclosure.

[0109] Figure 7 8 is a block diagram of an electronic device for a fault analysis method according to an exemplary embodiment. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a message transceiver device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc. The electronic device may be the above-mentioned mobile terminal, or may be a server connected to the mobile terminal, and the server is used to execute the above-mentioned fault analysis method.

[0110] Reference Figure 7 , the electronic device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output interface 812 , a sensor component 814 , and a communication component 816 .

[0111] The processing component 802 generally controls the overall operation of the electronic device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0112] The memory 804 is configured to store various types of data to support operations on the electronic device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0113] The power supply component 806 provides power to the various components of the electronic device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 800.

[0114] The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the electronic device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0115] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the electronic device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0116] The input / output interface 812 provides an interface between the processing component 802 and the peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0117] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the electronic device 800. For example, the sensor assembly 814 can detect the open / closed state of the electronic device 800, the relative positioning of the components, such as the display and keypad of the electronic device 800, and the sensor assembly 814 can also detect the position change of the electronic device 800 or a component of the electronic device 800, the presence or absence of contact between the user and the electronic device 800, the orientation or acceleration / deceleration of the electronic device 800, and the temperature change of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0118] The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0119] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0120] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by a processor 820 of an electronic device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0121] In addition to being an independent electronic device, the above-mentioned device can also be a part of an independent electronic device. For example, in one embodiment, the device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be an IC or a collection of multiple ICs; the chip can include but is not limited to the following types: GPU (Graphics Processing Unit), CPU (Central Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), SOC (System on Chip, SoC), etc. The above-mentioned integrated circuit or chip can be used to execute executable instructions (or codes) to implement the above-mentioned method. The executable instructions can be stored in the integrated circuit or chip, or can be obtained from other devices or equipment, such as the integrated circuit or chip including a processor, a memory, and an interface for communicating with other devices. The executable instruction may be stored in the memory, and the above method may be implemented when the executable instruction is executed by the processor; alternatively, the integrated circuit or chip may receive the executable instruction through the interface and transmit it to the processor for execution, so as to implement the above method.

[0122] In another exemplary embodiment, a computer program product is also provided. The computer program product includes a computer program executable by a programmable device, and the computer program has a code portion for executing the above method when executed by the programmable device.

[0123] Figure 8 1 is a block diagram of a device 1900 for a fault analysis method according to an exemplary embodiment. For example, the device 1900 may be provided as a server and connected to the mobile terminal. Figure 8 , the apparatus 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions executable by the processing component 1922, such as an application. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above-mentioned fault analysis method.

[0124] The device 1900 may also include a power supply component 1926 configured to perform power management of the device 1900, a wired or wireless network interface 1950 configured to connect the device 1900 to a network, and an input / output interface 1958. The device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server 2000. TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM or similar.

[0125] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the present disclosure. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0126] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A fault analysis method, characterized in that: The method comprises: When a call test is performed on a mobile terminal through a network, obtaining a log to be analyzed generated by the mobile terminal; Performing fault analysis on the log to be analyzed to obtain a fault analysis result; If the fault analysis result indicates the network fault, output the fault analysis result; Or, if the fault analysis result indicates a fault of the mobile terminal, the fault analysis result is output, and the log to be analyzed is captured and stored in a preset location.

2. The method according to claim 1, characterized in that The fault analysis result represents the network fault, and the performing fault analysis on the log to be analyzed, before obtaining the fault analysis result, further includes: Establishing a communication connection with the network; monitoring communication messages sent by the network; The performing fault analysis on the log to be analyzed to obtain the fault analysis result includes: When the communication message is not monitored, if an abnormal message corresponding to the network is recorded in the log to be analyzed, outputting a fault analysis result for the abnormal message; If the abnormal message corresponding to the network is not recorded in the log to be analyzed, a preset analysis result is obtained.

3. The method according to claim 1, characterized in that The fault analysis result represents the fault of the mobile terminal, the mobile terminal is a called terminal, and the fault analysis is performed on the log to be analyzed to obtain the fault analysis result, including: When no invitation message is received, obtaining the network status recorded in the log to be analyzed; If the network condition does not meet the preset network condition, a fault analysis result for the network condition is obtained.

4. The method according to claim 3, characterized in that: The method further comprises: If the network condition meets the preset network condition, obtaining a call message from the log to be analyzed; If the call message indicates that there is a missed call, outputting a fault analysis result corresponding to the missed call; If the call message indicates that there is no missed call, the radio frequency resource occupancy status is obtained from the log to be analyzed, and the fault analysis result is obtained according to the radio frequency resource occupancy status.

5. The method according to claim 4, characterized in that The obtaining the fault analysis result according to the radio frequency resource occupancy condition includes: If the radio frequency resource is occupied, outputting a fault analysis result corresponding to the occupation of the radio frequency resource; If the radio frequency resource is not occupied, a preset analysis result is obtained.

6. The method according to claim 1, characterized in that The fault analysis result represents the fault of the mobile terminal, the mobile terminal is a calling terminal, and the fault analysis is performed on the log to be analyzed to obtain the fault analysis result, including: When no invitation message is sent, obtaining network registration information from the log to be analyzed; The fault analysis result is obtained according to the network registration information.

7. The method according to claim 6, characterized in that The obtaining the fault analysis result according to the network registration information includes: If the network registration information indicates that the mobile terminal is not registered with the network, a fault analysis result corresponding to the network not being registered is obtained.

8. The method according to claim 6, characterized in that The obtaining the fault analysis result according to the network registration information includes: If the network registration information indicates that the mobile terminal has registered with the network, obtaining the network status recorded in the log to be analyzed; The fault analysis result is obtained according to the network status.

9. The method according to claim 8, characterized in that The obtaining the fault analysis result according to the network status includes: If the network condition does not meet the preset network condition, obtaining a fault analysis result corresponding to the network condition; If the network condition meets the preset network condition, a preset analysis result is obtained.

10. The method according to any one of claims 2 to 9, characterized in that: The network includes an IP Multimedia Subsystem network and / or a circuit switched network.

11. The method according to any one of claims 1 to 9, characterized in that: The logs to be analyzed include baseband processor side logs.

12. A fault analysis device, characterized in that: The device comprises: An acquisition module, used for acquiring the log to be analyzed generated by the mobile terminal when performing a call test on the mobile terminal through the network; An analysis module is used to perform fault analysis on the log to be analyzed and obtain a fault analysis result; The output module is used to output the fault analysis result if the fault analysis result represents the network fault; or, if the fault analysis result represents the mobile terminal fault, output the fault analysis result and capture the log to be analyzed and store it in a preset location.

13. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the steps of the method described in any one of claims 1 to 11 when executing the instructions.

14. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the program instructions are executed by a processor, the steps of the method described in any one of claims 1 to 11 are implemented.

Images