Fault location method, device, computer readable medium and electronic device

Abstract

The embodiments of the present application provide a fault location method, device, computer-readable medium and electronic device, the fault location method comprising: monitoring the operation log of the network element, if the operation log is monitored to contain abnormal information, determining the target network request for processing the abnormality according to the abnormal information; obtaining the identification information of the terminal that initiates the target network request from the abnormal information; obtaining the target link tracking information obtained by tracking the processing process of the target network request with the identification information as the tracking identifier; determining the target network element passed through during the processing of the target network request from the target link tracking information, and obtaining the operation log of the target network element; locating the cause of the abnormal processing of the target network request according to the obtained operation log. The technical solution of the embodiment of the present application can confirm the network element through which the network request for processing the abnormality passes through through the target link tracking information, avoiding obtaining the operation log from each network element one by one to locate the cause of the abnormal processing.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a fault location method, device, computer-readable medium and electronic device. Background Art

[0002] In the related technology, the network elements deployed in the network operate independently. If an abnormality occurs in a network element when processing a network request initiated by a terminal, it is necessary to obtain the operation logs of each network element in the network and locate the cause of the abnormality based on the obtained operation logs. Since there are many network elements deployed in the network, the data is also large, which leads to a long time to locate and process the cause of the abnormality. Summary of the invention

[0003] To solve the above technical problems, the embodiments of the present application provide a fault location method, device, computer-readable medium and electronic device, so as to shorten the time spent in locating and processing the cause of the abnormality.

[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0005] According to one aspect of an embodiment of the present application, a fault locating method is provided, comprising: monitoring an operation log of a network element, and if it is detected that the operation log contains abnormal information, determining a target network request for processing the abnormality based on the abnormal information; obtaining identification information of a terminal that initiates the target network request from the abnormal information; obtaining target link tracking information obtained by tracking the processing of the target network request using the identification information as a tracking identifier; determining a target network element passed through during the processing of the target network request from the target link tracking information, and obtaining the operation log of the target network element; and locating the cause of the abnormal processing of the target network request based on the obtained operation log.

[0006] According to one aspect of an embodiment of the present application, a fault locating device is provided, including: a monitoring module, configured to monitor an operation log of a network element, and if abnormal information is detected in the operation log, determining a target network request for processing the abnormality according to the abnormal information; a first data processing module, configured to obtain identification information of a terminal that initiates the target network request from the abnormal information; a second data processing module, configured to obtain target link tracking information obtained by tracking the processing process of the target network request using the identification information as a tracking identifier; a third data processing module, configured to determine a target network element passed through during the processing of the target network request from the target link tracking information, and obtain the operation log of the target network element; a fault identification module, configured to locate the cause of the abnormal processing of the target network request according to the obtained operation log.

[0007] In some embodiments of the present application, based on the aforementioned scheme, the second data processing module is further configured to: obtain the target network request before obtaining the target link tracking information obtained by tracking the processing process of the target network request using the identification information as the tracking identifier; obtain the identification information of the terminal that initiates the target network request from the target network request; track the processing process of the target network request using the identification information as the tracking identifier to obtain the target link tracking information.

[0008] In some embodiments of the present application, based on the aforementioned scheme, the second data processing module is configured to: obtain multiple link tracking information obtained by tracking multiple network requests initiated by the terminal with the identification information as the tracking identifier; the link tracking information includes the network elements passed during the processing of the network request and the corresponding receiving time of the network elements, wherein the receiving time is the time when the network element receives the data corresponding to the network request; obtain the target timestamp from the exception information, wherein the target timestamp is the time when the network element to which the exception information belongs receives the data corresponding to the target network request; determine the link tracking information whose receiving time matches the target timestamp from the multiple link tracking information, and use the determined link tracking information as the target link tracking information.

[0009] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module is configured to: obtain the standard processing flow corresponding to the target network request; compare the standard processing flow with the abnormal processing flow corresponding to the target link tracking information, and generate a comparison result; locate the cause of the abnormal processing of the target network request according to the operation log and the comparison result.

[0010] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module is configured to: determine the base station that communicates with the terminal from the target network element; obtain the information of the terminal and the information of the base station, and locate the cause of the abnormal processing of the target network request based on the operation log, the information of the terminal and the information of the base station.

[0011] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module is configured to: filter out a first data processing record containing the tracking identifier from the acquired operation log; and locate the cause of the abnormal processing of the target network request based on the first data processing record.

[0012] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module is configured to: obtain the target reception time corresponding to the target network element from the target link tracking information, wherein the target reception time is the time when the target network element receives the data corresponding to the target network request; filter out the second data processing record corresponding to the reception time from the first data processing record; and locate the cause of the abnormal processing of the target network request based on the second data processing record.

[0013] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the fault location method described in the above embodiment.

[0014] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the fault location method as described in the above embodiments.

[0015] In the technical solution of the embodiment of the present application, the operation log of the network element is monitored, and if it is monitored that the operation log contains abnormal information, the target network request for processing the exception is determined according to the abnormal information; the identification information of the terminal that initiates the target network request is obtained from the abnormal information; the target link tracking information obtained by tracking the processing process of the target network request with the identification information as the tracking identifier; the target network element passed through during the processing of the target network request is determined from the target link tracking information, and the operation log of the target network element is obtained; the cause of the abnormal processing of the target network request is located according to the obtained operation log, so that when it is monitored that the operation log contains abnormal information, the target network element passed through during the processing of the target network request is quickly confirmed through the target link tracking information, avoiding obtaining the operation log from each network element one by one, thereby improving the efficiency of locating the cause of the abnormal processing of the target network request, and by tracking the processing process of the network request with the identification information of the terminal as the tracking identifier, there is no need to generate an additional tracking identifier, thereby saving resources, and facilitating the determination of the terminal that initiates the target network request for processing the exception.

[0016] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0018] Figure 1 A flow chart of a fault location method according to an embodiment of the present application is shown;

[0019] Figure 2 A flow chart of a fault location method according to another embodiment of the present application is shown;

[0020] Figure 3 Shows Figure 1 A flowchart of step S120 in the illustrated embodiment in an exemplary embodiment;

[0021] Figure 4 Shows Figure 1 A flowchart of step S130 in the illustrated embodiment in an exemplary embodiment;

[0022] Figure 5 Shows Figure 1 A flowchart of step S140 in the illustrated embodiment in an exemplary embodiment;

[0023] Figure 6 Shows Figure 1 A flowchart of step S140 in the illustrated embodiment in an exemplary embodiment;

[0024] Figure 7 Shows Figure 6 A flowchart of step S510 in the illustrated embodiment in an exemplary embodiment;

[0025] Figure 8 A block diagram of a fault location device according to an embodiment of the present application is shown;

[0026] Fig. 9 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0027] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0028] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0029] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0030] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0031] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0032] The technical solution of the embodiment of the present application proposes a fault location method. Figure 1 As shown, the fault location method can be executed by a fault location device deployed in the network, and the fault location device can be any network element constituting the network; the fault location method at least includes steps S100 to S140, which are described in detail as follows:

[0033] In step S100, the operation log of the network element is monitored. If it is detected that the operation log contains abnormal information, a target network request for processing the abnormality is determined according to the abnormal information.

[0034] It should be noted that a network element is a device deployed in a network, and its types include but are not limited to base stations, terminals, gateways, routers, etc. Among them, networks include but are not limited to 5G (5th Generation Mobile Communication Technology, fifth generation mobile communication technology), 4G (4th Generation Mobile Communication Technology, fourth generation mobile communication technology) and other networks.

[0035] Secondly, the operation log is a log generated by the network element during operation. The operation log records the processing information of the network element on various data. When an exception occurs during data processing, the network element will generate exception information and record it in the operation log. For example, when the network element has a process interruption, data processing timeout, or processing without response, exception information will be generated and recorded in the operation log.

[0036] A network request is a request initiated by a terminal to a network, and its types include but are not limited to a registration request, a call request, a location update request, etc.

[0037] In an embodiment of the present application, in order to determine whether an abnormality occurs during network request processing, the operation log of the network element can be monitored. If abnormal information is detected in the operation log, the target network request associated with the abnormal information can be determined based on the abnormal information.

[0038] The method of determining the target network request associated with the abnormal information according to the abnormal information can be flexibly set according to actual needs. In one embodiment, the abnormal information includes identification information of the target network request to which it belongs. After obtaining the abnormal information, the abnormal information can be parsed to obtain the identification information of the target network request to determine the target network request.

[0039] In step S110, identification information of the terminal that initiates the target network request is obtained from the exception information.

[0040] It should be noted that after establishing a connection with the network, the terminal can initiate a network request to the network element; the terminal includes but is not limited to electronic devices such as smart phones, tablets, laptops, computers, and vehicle-mounted terminals; the identification information is a unique identifier corresponding to different terminals, and the identification information includes but is not limited to SUPI (Subscription Permanent Identifier), IMSI (International Mobile Subscriber Identity), etc.

[0041] In the embodiment of the present application, in order to determine the terminal that initiates the target network request for processing the exception, the identification information of the terminal that initiates the target network request can be obtained from the exception information.

[0042] Among them, the method of obtaining the identification information of the terminal that initiates the target network request from the exception information can be flexibly set as needed. In one embodiment, after determining the target network request to process the exception, the identification information of the terminal can be directly obtained from the target network request. That is, before the terminal initiates a network request to the network element, the terminal adds the identification information matching the terminal to the network request, and then sends the network request to the network element. In this way, when the network element receives the target network request and processes the exception, the identification information of the terminal that initiates the target network request can be directly obtained from the target network request.

[0043] In another embodiment, the exception information includes identification information of the terminal that initiates the target network request, and therefore, the identification information can be directly obtained from the exception information.

[0044] In step S120, target link tracking information is obtained by tracking the processing process of the target network request using the identification information as the tracking identification.

[0045] Link tracking information is information obtained by tracking the processing of network requests. It should be understood that the network is usually divided into multiple different network elements according to business functions, and then different network elements are combined to provide rich business functions. The processing of a network request may pass through multiple network elements. In order to locate the cause of the abnormality after the network request is processed abnormally, the processing of the network request can be tracked to obtain link tracking information.

[0046] The link tracking information may include, but is not limited to, the network elements passed through during the processing of the network request, the time when each network element receives the data corresponding to the network request, the processing result of the data corresponding to the network request, etc. For example, assuming that the processing process of a certain network request is: after receiving the network request, network element A performs operation a and sends a call instruction to network element B to call network element B to perform operation b; then the link tracking information may include the time when network element A receives the network request and the time when network element B receives the call instruction.

[0047] Among them, in order to facilitate viewing of link tracking information, after obtaining the link tracking information, a tree view, a process view, etc. can be generated based on the process of tracking the processing process of the network request in the link tracking information.

[0048] It should be noted that a network element may process data corresponding to network requests initiated by multiple terminals. In order to distinguish the processing processes of network requests initiated by multiple terminals, the network element may generate a tracking identifier corresponding to the terminal.

[0049] In an embodiment of the present application, the identification information of the terminal that initiates the network request can be directly obtained from the network request, and the obtained identification information can be used as a tracking identifier. The network requests initiated by multiple terminals can be distinguished through the uniqueness of the identification information, so that the network element does not need to generate a tracking identifier corresponding to the terminal, thereby reducing the waste of resources.

[0050] In order to determine the processing process of the target network request, the target link tracking information can be obtained. The specific method of obtaining the target link tracking information can be flexibly set according to needs. In one embodiment, after obtaining the identification information of the terminal that initiates the target network request, the link tracking information corresponding to the identification information can be searched from the database to obtain the target link tracking information. That is to say, before step S130, the identification information of the terminal that initiates the network request can also be used as the tracking identifier to track the processing process of different network requests, obtain the link tracking information corresponding to different network requests, and store it in the database. In this way, after obtaining the identification information of the terminal that initiates the target network request from the abnormal information, the target link tracking information of the target network request can be directly obtained from the database.

[0051] In another implementation, after the identification information of the terminal that initiates the target network request is obtained, the obtained identification information can be used as a tracking identifier to track the processing process of the network request, thereby obtaining the target link tracking information.

[0052] In step S130, the target network element passed through during the processing of the target network request is determined from the target link tracking information, and the operation log of the target network element is obtained.

[0053] The target network element is the network element through which the processing process of the target network request passes.

[0054] The target link tracking information includes the network elements passed through during the processing of the target network request. Therefore, after obtaining the target link tracking information, the network elements passed through during the processing of the target network request can be directly obtained from the target link tracking information to determine the target network element. In this way, the operation log of the target network element can be obtained.

[0055] In step S140, the cause of the abnormal processing of the target network request is located according to the acquired operation log.

[0056] It should be noted that when it is monitored that the operation log of any network element contains abnormal processing of a network request, the cause of the abnormal processing of the network request may be caused by other network elements different from this network element that the network request passes through during the processing. Therefore, in one embodiment of the present application, after obtaining the operation log of the target network element through which the target network request passes, the cause of the abnormal processing of the target network request can be located based on the obtained operation log.

[0057] The method of locating the cause of the abnormal processing of the target network request can be flexibly set as needed. In one embodiment, after obtaining the operation log in the target network element, the abnormal information can be filtered out from the operation log, and the abnormal information corresponding to the identification information can be filtered out from the abnormal information based on the identification information in the target network request, and then the abnormal information associated with the target network request is determined based on the target network request, so as to locate the cause of the abnormal processing of the target network request.

[0058] In the technical solution of the aforementioned embodiment, after determining the target network request for processing exceptions through the exception information in the operation log, the identification information of the terminal that initiates the target network request is obtained from the exception information, and based on the identification information, the processing process of the target network request is tracked using the identification information as a tracking identifier to obtain the target link tracking information, and then the target network element passed by the target network request during the reprocessing process is determined through the target link tracking information, thereby excluding the network element that the target network request for processing exceptions has not passed, avoiding obtaining the operation log from each network element one by one, improving the efficiency of locating the cause of the processing exception of the target network request, narrowing the scope of locating the cause of the processing exception, and thereby shortening the time for handling the fault, and using the identification information as a tracking identifier, there is no need to additionally generate a tracking identifier to track the processing process of the network request, thereby reducing the waste of resources.

[0059] See also Figure 2 , Figure 2 FIG. 1 is a flow chart of a fault location method according to another exemplary embodiment. Figure 2 As shown, in Figure 1 Before step S120 in the illustrated embodiment, the method may further include steps S200 to S220, which are described in detail as follows:

[0060] Step S200, obtaining a target network request.

[0061] In this embodiment, before step S120, a target network request may be obtained first, wherein the target network request may be obtained from network elements such as AMF (Access and Mobility Management Function) and MME (Mobility Management Entity).

[0062] Step S210: Acquire identification information of a terminal that initiates the target network request from the target network request.

[0063] In one embodiment of the present application, in order to obtain the identification information of the terminal that initiates the target network request from the target network request, in one embodiment, before obtaining the network request, the terminal can add the identification information of the terminal to the network request when initiating the network request. Therefore, the identification information of the terminal that initiates the target network request can be directly obtained by parsing the target network request.

[0064] In another embodiment, before obtaining the network request, when the network element receives the network request sent by the terminal, the network element may send a request to the terminal for obtaining the identification information of the terminal. After receiving the identification information returned by the terminal, the network element adds the identification information of the terminal to the network request. Therefore, the identification information of the terminal that initiates the target network request can be directly obtained by parsing the target network request.

[0065] Step S220: Track the processing process of the target network request using the identification information as the tracking identification to obtain target link tracking information.

[0066] In one embodiment of the present application, after the identification information of the terminal is acquired, the processing process of the network request can be tracked according to the identification information as a tracking identifier to obtain link tracking information.

[0067] Through the above implementation, after obtaining the network request, the identification information obtained by parsing the network request can be used as a tracking identifier, and the processing process of the network request can be tracked to obtain link tracking information. Moreover, after obtaining the link tracking information, the link tracking information can also be stored, so that after an abnormality occurs in the target network request, the target link tracking information can be directly obtained from the corresponding storage location, thereby improving the speed of information acquisition, and avoiding the situation where the tracking identifier disappears and the target link tracking information cannot be obtained after tracking occurs after an abnormality occurs in the target network request.

[0068] See also Figure 3 , Figure 3 yes Figure 1 The step S120 in the embodiment shown is a flow chart in an exemplary embodiment. Figure 3 As shown, the process of obtaining the target link tracking information obtained by tracking the processing process of the target network request using the identification information as the tracking identification may include steps S121 to S123, which are described in detail as follows:

[0069] Step S121, obtaining multiple link tracking information obtained by tracking multiple network requests initiated by the terminal respectively using the identification information as the tracking identification; the link tracking information includes the network elements passed during the processing of the network request and the corresponding receiving time of the network elements.

[0070] Firstly, it should be noted that the receiving time corresponding to the network element is the time when the network element receives the data corresponding to the network request.

[0071] The same terminal can initiate multiple network requests to a network element. Therefore, by tracking the processing of the network request using the terminal's identification information as the tracking identifier, multiple link tracking information may be obtained, each of which corresponds to a network request.

[0072] In an embodiment of the present application, after a network request initiated by a terminal is obtained, identification information of the terminal that initiated the network request is obtained from the network request, and the network request initiated by the terminal is tracked using the identification information as a tracking identifier. Thus, the multiple link tracking information obtained include both target link tracking information for processing abnormal target network requests and link tracking information for remaining network requests initiated by the terminal.

[0073] Step S122, obtaining a target timestamp from the exception information.

[0074] It should be noted that the target timestamp is the time when the network element to which the abnormal information belongs receives the data corresponding to the target network request for processing the abnormality.

[0075] In an embodiment of the present application, when the operation log is monitored to contain abnormal information, the target timestamp can be directly obtained from the abnormal information. That is, when the network element generates abnormal information, the time when the network element receives the data corresponding to the target network request can be used as the target timestamp, and the target timestamp can be added to the abnormal information.

[0076] Step S123, determining the link tracking information whose receiving time matches the target timestamp from the multiple link tracking information, and using the determined link tracking information as the target link tracking information.

[0077] In an embodiment of the present application, after obtaining the target timestamp, the link tracking information matching the target timestamp can be directly determined from the multiple receiving times contained in the multiple link tracking information, and the determined link tracking information can be used as the target link tracking information.

[0078] Through the above implementation, when multiple network requests are initiated by the same terminal, the identification information of the terminal is used to track the multiple network requests initiated respectively, and multiple link tracking information is obtained. When the target network request is processed abnormally, the reception time of the network element receiving the data corresponding to the target network request, that is, the target timestamp, is obtained by parsing the abnormal information of the target network request. By comparing the target timestamp with the reception time corresponding to the network element contained in the multiple link tracking information, the link tracking information whose reception time matches the target timestamp can be determined from the multiple link tracking information, and the determined link tracking information is used as the target link tracking information, thereby obtaining the target link tracking information of the target network request. For example, assuming that network element A includes exception information, the target timestamp in the exception information is T1, and the terminal identification information is used as the tracking identifier, three link tracking information corresponding to the tracking identifier are obtained, among which the first link tracking information includes the BCD network element, the second link tracking information includes the ABC network element, and the corresponding receiving time of the A network element is T1; the third link tracking information includes the ACE network element, and the corresponding receiving time of the A network element is T2; since the second link tracking information includes the A network element, and the receiving time of the A network element matches the target timestamp, the second link tracking information is used as the target link tracking information.

[0079] See also Figure 4 , Figure 4 yes Figure 1 The step S140 in the illustrated embodiment is a flow chart in an exemplary embodiment. Figure 4 As shown, the process of locating the cause of the abnormal processing of the target network request according to the acquired operation log may include steps S300 to S320, which are described in detail as follows:

[0080] Step S300, obtaining a standard processing flow corresponding to a target network request.

[0081] In an embodiment of the present application, a standard process library is pre-set, and the standard process library contains standard processing processes for different network requests, that is, normal processing processes.

[0082] After obtaining the target network request, the processing flow corresponding to the target network request can be obtained from the standard flow library, and the obtained processing flow can be used as the standard processing flow.

[0083] Step S310 , comparing the standard processing flow with the abnormal processing flow corresponding to the target link tracking information, and generating a comparison result.

[0084] It should be noted that the exception handling process is obtained based on the target network elements that the target network request passes through during the processing and the time when the target network element receives the data corresponding to the target network request.

[0085] In an embodiment of the present application, after obtaining the target network request, the processing flow corresponding to the target network request is obtained from the standard flow library, and the obtained processing flow is used as the standard processing flow. The standard processing flow is then compared with the exception processing flow for the target network request obtained from the target link tracking information, thereby obtaining a difference processing flow between the exception processing flow and the standard processing flow, and the difference processing flow is used as the comparison result.

[0086] The difference processing flow is a processing flow in which the processing flow of the network element for the network request in the abnormal processing flow is different from the processing flow of the network element for the network request in the standard processing flow;

[0087] Step S320: locate the cause of the abnormal processing of the target network request according to the operation log and the comparison result.

[0088] In an embodiment of the present application, after obtaining the comparison result between the exception processing flow and the standard processing flow, the cause of the processing exception of the target network request is located in combination with the operation log.

[0089] In the above implementation, after obtaining the comparison results of the exception handling process and the standard processing process, the operation log of the network element corresponding to the difference processing process is obtained according to the difference processing process in the comparison results to locate the cause of the exception processing, thereby narrowing the scope of locating the cause of the exception processing of the target network request and improving the efficiency of searching the operation log.

[0090] See also Figure 5 , Figure 5 yes Figure 1 The step S140 in the illustrated embodiment is a flow chart in an exemplary embodiment. Figure 5 As shown, the process of locating the cause of the abnormal processing of the target network request according to the acquired operation log may include steps S400 to S410, which are described in detail as follows:

[0091] Step S400: determining a base station for communication with the terminal from the target network element.

[0092] It should be noted that the base station is the infrastructure in the network and is the interface device for terminals to access the network; base stations are set up in different areas so that terminals in the area can access the network through the base stations in the area.

[0093] In an embodiment of the present application, the base station communicating with the terminal can be directly determined from the target network element. That is, when the base station generates a data processing record when processing the corresponding data in the received network request, the identification information of the terminal that initiated the network request is added to the data processing record. Therefore, the network elements passed through during the network request processing in the link tracking information include the base station communicating with the terminal. Therefore, after determining the target network request for processing abnormality, the base station that receives the target network request for processing abnormality initiated by the terminal can be determined through the target network element contained in the target link tracking information.

[0094] Step S410, obtaining terminal information and base station information, and locating the cause of the abnormal processing of the target network request based on the operation log, the terminal information and the base station information.

[0095] In order to further improve the efficiency of locating the cause of the abnormal processing of the target network request, in this embodiment, a terminal database is pre-set, and the terminal database includes but is not limited to the location information of the terminal, the identification information of the terminal, and the operator information of the terminal.

[0096] The method of obtaining terminal information is to obtain identification information from the target network request, determine the terminal that initiates the target network request in the terminal database based on the identification information, and retrieve other information of the terminal in the terminal database from the terminal database.

[0097] Through the above implementation, when locating the cause of abnormal network request processing, the information of the terminal with the same identification information and the information of the base station that establishes communication with the terminal can be obtained from the terminal database, so as to locate the cause of the abnormal processing in the operation log.

[0098] See also Figure 6 , Figure 6 yes Figure 1 The step S140 in the illustrated embodiment is a flow chart in an exemplary embodiment. Figure 6 As shown, the process of locating the cause of the abnormal processing of the target network request according to the acquired operation log may include steps S500 to S510, which are described in detail as follows:

[0099] Step S500: Filter out a first data processing record containing a tracking identifier from the acquired operation log.

[0100] It should be noted that the operation log of the network element includes data processing records for processing different data. The network element processes data of network requests initiated by multiple terminals, so the operation log of the network element includes data processing records for processing data of network requests initiated by multiple terminals.

[0101] In order to distinguish network requests initiated by multiple terminals, the data processing record may include identification information of the terminal.

[0102] In an embodiment of the present application, in order to filter out the data processing record corresponding to the target network request from the operation log, the first data processing record containing the tracking identifier can be filtered out from the acquired operation log. The first data processing record is a data processing record of the network request initiated by the network element to the target terminal, and the target terminal is the terminal that initiates the target network request with abnormal processing.

[0103] Step S510: locate the cause of the abnormal processing of the target network request based on the first data processing record.

[0104] In an embodiment of the present application, after obtaining the first data processing record, the data processing record corresponding to the target network request in the operation log is determined, thereby locating the cause of the abnormal processing of the target network request based on the first data processing record, narrowing the scope of locating the cause of the abnormal processing, and further improving the accuracy of locating the cause of the abnormal processing of the target network request.

[0105] See also Figure 7 , Figure 7 yes Figure 6 The step S510 in the illustrated embodiment is a flow chart in an exemplary embodiment. Figure 7 As shown, the process of locating the cause of the abnormal processing of the target network request based on the first data processing record may include steps S511 to S513, which are described in detail as follows:

[0106] Step S511, obtaining the target receiving time corresponding to the target network element from the target link tracking information.

[0107] It should be noted that the target receiving time is the time when the target network element receives the data corresponding to the target network request.

[0108] The processing process of different network requests of the same terminal may go through the same network element. Therefore, when the operation log is filtered based on the identification information of the terminal, the data processing records corresponding to different network requests of the same terminal may be filtered out, that is, the first data processing record may include data processing records of other network requests initiated by the terminal corresponding to the target network request.

[0109] In order to filter out the data processing record corresponding to the target network request from the first data processing record, in this embodiment, the target receiving time corresponding to the target network element can be firstly obtained from the target link tracking information.

[0110] Step S512: Filter out the second data processing record corresponding to the target receiving time from the first data processing record.

[0111] In order to further improve the accuracy of locating the cause of abnormal processing of the target network request, in an embodiment of the present application, after obtaining the time when the target network element receives the data corresponding to the target network request, the second data processing record corresponding to the target reception time can be filtered out from the first data processing record.

[0112] For example, it is assumed that the target link tracking information includes network elements a1 and a2, wherein the target receiving times corresponding to network elements a1 and a2 are t1 and t2 respectively; the first data processing record includes 5 data processing records, which are recorded as b1, b2, b3, b4, and b5 respectively, wherein the times included in b1, b2, b3, b4, and b5 are t1, t3, t1, t2, and t5 respectively, b1 and b2 are data processing records of network element a1, and b3, b4, and b5 are data processing records of network element a2. Therefore, the data processing record that matches the target receiving time t1 of network element a1 is screened out from the data processing records b1 and b2 of network element a1, namely b1; the data processing record that matches the target receiving time t2 of network element a2 is screened out from the data processing records b3, b4, and b5 of network element a2, namely b4, thereby obtaining the second data processing records, namely b1 and b4.

[0113] Step S513: locate the cause of the abnormal processing of the target network request based on the second data processing record.

[0114] In an embodiment of the present application, after acquiring the second data processing record, the cause of the abnormal processing of the target network request is located based on the second data processing record, which further narrows the scope of locating the cause of the abnormal processing and improves the efficiency of locating the cause of the abnormal processing.

[0115] The following describes an apparatus embodiment of the present application, which can be used to execute the fault location method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned embodiment of the fault location method of the present application.

[0116] Figure 8 FIG. 8 is a block diagram of a fault location device 800 according to an embodiment of the present application.

[0117] Reference Figure 8As shown, according to an embodiment of the present application, a fault location device 800 includes: a monitoring module 810, configured to monitor the operation log of the network element, and if it is detected that the operation log contains abnormal information, the target network request for processing the abnormality is determined according to the abnormal information; a first data processing module 820, configured to obtain the identification information of the terminal that initiates the target network request from the abnormal information; a second data processing module 830, configured to obtain target link tracking information obtained by tracking the processing process of the target network request with the identification information as the tracking identifier; a third data processing module 840, configured to determine the target network element passed through during the processing of the target network request from the target link tracking information, and obtain the operation log of the target network element; a fault identification module 850, configured to locate the cause of the abnormal processing of the target network request according to the obtained operation log.

[0118] In some embodiments of the present application, based on the aforementioned scheme, the second data processing module 830 is further configured to: obtain the target network request before obtaining the target link tracking information obtained by tracking the processing process of the target network request using the identification information as the tracking identifier; obtain the identification information of the terminal that initiates the target network request from the target network request; track the processing process of the target network request using the identification information as the tracking identifier to obtain the target link tracking information.

[0119] In some embodiments of the present application, based on the aforementioned scheme, the second data processing module 830 is configured to: obtain multiple link tracking information obtained by tracking multiple network requests initiated by the terminal with identification information as tracking identifier; the link tracking information includes the network elements passed during the processing of the network request and the corresponding receiving time of the network elements, wherein the receiving time is the time when the network element receives the data corresponding to the network request; obtain the target timestamp from the exception information, wherein the target timestamp is the time when the network element to which the exception information belongs receives the data corresponding to the target network request; determine the link tracking information whose receiving time matches the target timestamp from the multiple link tracking information, and use the determined link tracking information as the target link tracking information.

[0120] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module 850 is configured to: obtain the standard processing flow corresponding to the target network request; compare the standard processing flow with the abnormal processing flow corresponding to the target link tracking information, and generate a comparison result; locate the cause of the abnormal processing of the target network request based on the operation log and the comparison result.

[0121] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module 850 is configured to: determine the base station that communicates with the terminal from the target network element; obtain the terminal information and the base station information, and locate the cause of the abnormal processing of the target network request based on the operation log, the terminal information and the base station information.

[0122] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module 850 is configured to: filter out a first data processing record containing a tracking identifier from the acquired operation log; and locate the cause of the abnormal processing of the target network request based on the first data processing record.

[0123] In some embodiments of the present application, based on the aforementioned scheme, the fault identification module 850 is configured to: obtain the target reception time corresponding to the target network element from the target link tracking information, wherein the target reception time is the time when the target network element receives the data corresponding to the target network request; filter out the second data processing record corresponding to the reception time from the first data processing record; and locate the cause of the abnormal processing of the target network request based on the second data processing record.

[0124] It should be noted that the fault location device 800 provided in the above embodiment and the fault location method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here.

[0125] Fig. 9 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.

[0126] It should be noted that Fig. 9 The computer system 900 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0127] like Fig. 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 902 or the program loaded from the storage part 908 to the random access memory (RAM) 903, such as executing the method described in the above embodiment. In the RAM 903, various programs and data required for system operation are also stored. The CPU 901, ROM 902 and RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0128] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

[0129] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 909, and / or installed from a removable medium 911. When the computer program is executed by a central processing unit (CPU) 901, various functions defined in the system of the present application are executed.

[0130] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0131] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0132] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0133] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.

[0134] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0135] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0136] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0137] It should be understood that the present application is not limited to the precise 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 application is limited only by the appended claims.

Claims

1. A fault location method, characterized in that: The method comprises: Monitor the operation log of the network element, and if it is detected that the operation log contains abnormal information, determine the target network request for processing the abnormality according to the abnormal information; the operation log is a log generated by the network element during operation; the operation log records the processing information of the network element on various data; Acquire identification information of a terminal that initiates the target network request from the abnormal information; before the terminal initiates the network request, add identification information matching the terminal to the target network request; Acquire target link tracking information obtained by tracking the processing process of the target network request using the identification information as a tracking identifier; Determine the target network element passed through during the processing of the target network request from the target link tracking information, and obtain the operation log of the target network element; Locate the cause of the abnormal processing of the target network request according to the acquired operation log; the cause of the abnormal processing of the network request is caused by other network elements different from the monitored network elements passed by the target network request during the processing; The locating the cause of the abnormal processing of the target network request according to the acquired operation log includes: filtering out a first data processing record containing the tracking identifier from the acquired operation log; the first data processing record is a data processing record of a network request initiated by a network element to a target terminal, and the target terminal is a terminal that initiates the target network request with abnormal processing; and locating the cause of the abnormal processing of the target network request based on the first data processing record.

2. The method according to claim 1, characterized in that: Before obtaining the target link tracking information obtained by tracking the processing process of the target network request using the identification information as the tracking identifier, the method further includes: Obtaining the target network request; Acquire identification information of a terminal that initiates the target network request from the target network request; The processing process of the target network request is tracked using the identification information as a tracking identification to obtain the target link tracking information.

3. The method according to claim 1, characterized in that The obtaining of target link tracking information obtained by tracking the processing process of the target network request using the identification information as a tracking identifier includes: Acquire multiple pieces of link tracking information obtained by tracking multiple network requests initiated by the terminal respectively using the identification information as the tracking identification; the link tracking information includes network elements passed through during the processing of the network request and the corresponding receiving time of the network element, wherein the receiving time is the time when the network element receives the data corresponding to the network request; Acquire a target timestamp from the exception information, wherein the target timestamp is the time when the network element to which the exception information belongs receives data corresponding to the target network request; The link tracking information whose receiving time matches the target timestamp is determined from the multiple link tracking information, and the determined link tracking information is used as the target link tracking information.

4. The method according to claim 1, characterized in that The locating the cause of the abnormal processing of the target network request according to the acquired operation log includes: Obtaining a standard processing flow corresponding to the target network request; Compare the standard processing flow with the abnormal processing flow corresponding to the target link tracking information, and generate a comparison result; The cause of the abnormal processing of the target network request is located according to the operation log and the comparison result.

5. The method according to claim 1, characterized in that The locating the cause of the abnormal processing of the target network request according to the acquired operation log includes: Determining a base station for communicating with the terminal from the target network element; The information of the terminal and the information of the base station are obtained, and the cause of the abnormal processing of the target network request is located based on the operation log, the information of the terminal and the information of the base station.

6. The method according to claim 1, characterized in that The locating the cause of the abnormal processing of the target network request based on the first data processing record includes: Acquire a target receiving time corresponding to the target network element from the target link tracking information, wherein the target receiving time is the time when the target network element receives the data corresponding to the target network request; Filtering out a second data processing record corresponding to the receiving time from the first data processing record; The cause of the abnormal processing of the target network request is located based on the second data processing record.

7. A fault location device, characterized in that: include: A monitoring module is configured to monitor the operation log of the network element, and if it is detected that the operation log contains abnormal information, determine the target network request to process the abnormality according to the abnormal information; the operation log is a log generated by the network element during operation; the operation log records the processing information of the network element on various data; a first data processing module configured to obtain identification information of a terminal that initiates the target network request from the abnormal information; before the terminal initiates the network request, add identification information matching the terminal to the target network request; A second data processing module is configured to obtain target link tracking information obtained by tracking the processing process of the target network request using the identification information as a tracking identifier; A third data processing module is configured to determine the target network element passed through during the processing of the target network request from the target link tracking information, and obtain the operation log of the target network element; A fault identification module, configured to locate the cause of the abnormal processing of the target network request according to the acquired operation log; The reason for the abnormal processing of the network request is that the target network request passes through other network elements different from the monitored network elements during the processing; The locating the cause of the abnormal processing of the target network request according to the acquired operation log includes: filtering out a first data processing record containing the tracking identifier from the acquired operation log; The first data processing record is a data processing record of a network request initiated by a network element to a target terminal, where the target terminal is a terminal that initiates a target network request with a processing exception; and the cause of the processing exception of the target network request is located based on the first data processing record.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the fault location method according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: include: one or more processors; A storage device, used to store one or more programs, when the one or more programs are executed by the one or more processors, enables the one or more processors to implement the fault location method according to any one of claims 1 to 6.

Images