Application server fault location method and related equipment

Abstract

The present disclosure provides an application server fault location method and related equipment, which relate to the field of communication technology. The method includes, according to the one-to-one correspondence between the service call session control function SCSCF network element and the application server AS network element, determining multiple minimum data units of the SCSCF network element and the AS network element; according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit, determining the origination failure code information of each minimum data unit; according to the origination failure code information, determining the faulty AS network element. The present disclosure can quickly and accurately locate the AS network element that has a fault.

Description

Background Art

[0002] Application Server (AS) services are connected to the IP Multimedia Subsystem (IMS) network in a serial manner in a predetermined order. AS is an important functional entity built on the IMS network, which can make full use of the various functions provided by the IMS network to provide users with supplementary services and value-added services. AS, as a transit station connected in series in the IMS network, lacks support tools for direct fault warning and positioning.

[0003] In the prior art, it takes a lot of manpower and time for maintenance personnel to analyze such network failures. In addition, there are two types of ASs: transit failure codes and origination failure codes, and there are a large number of various ASs. When a failure occurs, maintenance personnel cannot quickly and accurately locate whether it is an AS failure and the specific AS that caused the failure.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides an application server fault location method and related equipment, which at least to a certain extent overcomes the problem that the related technology cannot quickly and accurately locate the AS network element that causes the fault.

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

[0007] According to one aspect of the present disclosure, a method for locating an application server fault is provided, including: determining multiple minimum data units of a service call session control function SCSCF network element and an application server AS network element based on a one-to-one correspondence between IP addresses between the SCSCF network element and the AS network element; determining the origination failure code information of each minimum data unit based on the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit; and determining the faulty AS network element based on the origination failure code information.

[0008] In some embodiments, before obtaining business data between the service call session control function SCSCF network element and the application server AS network element, the method also includes: obtaining domain name server DNS data in the IP multimedia system IMS network; and determining the one-to-one correspondence between the IP addresses between the SCSCF network element and the AS network element based on the DNS data.

[0009] In some embodiments, the minimum data unit includes: SCSCF network element IP address; AS network element IP address; number of uplink Invites; number of various uplink failure codes; number of downlink Invites; number of various downlink failure codes; time interval; among which, the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element.

[0010] In some embodiments, the method further comprises: determining the initialization failure code information of each minimum data unit according to the difference between the number of each type of downlink failure code and the number of each type of uplink failure code in the same time interval in each minimum data unit.

[0011] In some embodiments, the method also includes: determining a suspicious AS network element set based on the originating failure code information; traversing data based on the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets; if the total number of SCSCF network elements in the suspicious AS network element set exceeds a preset threshold of the total number of SCSCF network elements with which the AS network elements have business interactions, determining a faulty AS network element.

[0012] In some embodiments, after determining the faulty AS according to the origination failure code information, the method further includes: determining information on the impact range of the AS on the service according to the total number of AS origination failure codes and the total number of uplink Invites.

[0013] In some embodiments, the uplink failure code includes a failure code transferred via an AS network element in the IMS network; the downlink failure code includes an uplink failure code and an origination failure code.

[0014] According to another aspect of the present disclosure, an application server fault locating device is also provided, including: a minimum data unit determination module, used to determine multiple minimum data units of the service call session control function SCSCF network element and the application server AS network element according to the one-to-one correspondence between the IP addresses between the SCSCF network element and the AS network element; an origination failure code information determination module, used to determine the origination failure code information of each minimum data unit according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit; a faulty AS network element determination module, used to determine the faulty AS network element according to the origination failure code information.

[0015] According to another aspect of the present disclosure, an electronic device is also provided, which includes: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned application server fault locating methods by executing the executable instructions.

[0016] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the application server fault locating method described in any one of the above is implemented.

[0017] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, any one of the above-mentioned application server fault locating methods is implemented.

[0018] The application server fault location method and related devices provided in the embodiments of the present disclosure determine multiple minimum data units of the SCSCF network element and the AS network element based on the one-to-one correspondence between the IP addresses of the service call session control function SCSCF network element and the application server AS network element; determine the origination failure code information of each minimum data unit based on the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit; and determine the faulty AS network element based on the origination failure code information. In the embodiments of the present disclosure, by determining the difference between the number of downlink failure codes and the number of uplink failure codes, a more accurate number of origination failure codes of the AS network element can be obtained, thereby facilitating the rapid and accurate location of the AS network element that has a fault.

[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 herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0021] Figure 1 A schematic diagram showing the logical structure of the interaction between the SCSCF network element and the AS network element in the prior art;

[0022] Figure 2 A schematic diagram showing a minimum data unit of an ISC interface in an embodiment of the present disclosure;

[0023] Figure 3 A flow chart of a method for locating a fault of an application server in an embodiment of the present disclosure is shown;

[0024] Figure 4 A flowchart showing a specific example of a method for locating a fault of an application server in an embodiment of the present disclosure is shown;

[0025] Figure 5A flowchart showing another specific example of a method for locating a fault of an application server in an embodiment of the present disclosure;

[0026] Figure 6 A flowchart showing another specific example of a method for locating a fault of an application server in an embodiment of the present disclosure;

[0027] Figure 7 A schematic diagram of analyzing an AS-originating failure code in an embodiment of the present disclosure is provided;

[0028] Figure 8 A schematic diagram of a device for locating a fault of an application server in an embodiment of the present disclosure is shown;

[0029] Fig. 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure;

[0030] Fig.10 A schematic diagram of a process for acquiring and regularizing data provided in an embodiment of the present disclosure;

[0031] Fig.11 A schematic diagram of a flow chart of a fault location analysis method provided in an embodiment of the present disclosure;

[0032] Fig.12 A structural block diagram of a computer device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0033] 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 the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0034] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0035] The specific implementation of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0036] Figure 1 FIG. 2 shows a schematic diagram of the logical structure of the interaction between the SCSCF network element and the AS network element in the prior art. Figure 1 As shown in FIG. 1 , the logical connection relationship between the SCSCF network element and the AS network element is a many-to-many relationship. Each SCSCF network element and the AS network element should have at least one IP address. According to the one-to-one correspondence between the IP addresses, a single connection data between the SCSCF network element and the AS network element is formed, that is, the minimum data unit, such as Figure 2 As shown, 1 represents a downlink Invite, 2 represents a downlink failure code, 3 represents an uplink Invite, and 4 represents an uplink failure code.

[0037] Those skilled in the art will know that Figure 1 The number of SCSCF network elements and AS network elements in the figure is only for illustration, and any number of SCSCF network elements and AS network elements may be provided according to actual needs, which is not limited in the embodiments of the present disclosure.

[0038] Figure 3 A flow chart of a method for locating a fault in an application server according to an embodiment of the present disclosure is shown as follows: Figure 3 As shown, the application server fault location method provided in the embodiment of the present disclosure includes the following steps:

[0039] S302: Determine multiple minimum data units of the service call session control function SCSCF network element and the application server AS network element according to the one-to-one correspondence between the IP addresses of the service call session control function SCSCF network element and the application server AS network element.

[0040] It should be noted that the above-mentioned minimum data unit can be a single connection data between the SCSCF network element and the AS network element.

[0041] S304: Determine the initial transmission failure code information of each minimum data unit according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit.

[0042] It should be noted that the above-mentioned uplink failure code quantity may be a field included in the minimum data unit. The above-mentioned downlink failure code quantity may be a field included in the minimum data unit. The above-mentioned initialization failure code information may be an initialization failure code of the minimum data unit.

[0043] For example, in the minimum data unit, the direction of message transmission in each single connection is constructed based on the source IP address and the destination IP address, and is divided into an upstream path and a downstream path according to the sending direction. The upstream path is the path where the source IP address is the SCSCF network element address and the destination IP address is the AS network element address, that is, the path where the SCSCF network element sends messages to the AS network element; the downstream path is the path where the source IP address is the AS network element address and the destination IP address is the SCSCF network element address, that is, the path where the AS network element sends messages to the SCSCF network element. The origination failure code existing in the minimum unit is obtained by calculating the difference between the number of downstream failure codes and the number of upstream failure codes.

[0044] S306: Determine the faulty AS network element according to the origination failure code information.

[0045] It should be noted that the above-mentioned faulty AS network element may be an AS network element where a fault occurs.

[0046] For example, the AS failure is determined according to a sudden change in the number of AS origination failure codes.

[0047] In a specific implementation, by determining the difference between the number of downlink failure codes and the number of uplink failure codes, a more accurate number of originating failure codes of the AS network element can be obtained, thereby facilitating rapid and accurate positioning of the AS network element where the fault occurs.

[0048] In one embodiment of the present disclosure, Figure 4 As shown, the application server fault location method provided in the embodiment of the present disclosure can determine the one-to-one correspondence between the IP addresses of the SCSCF network element and the AS network element through the following steps, and can accurately obtain the correspondence:

[0049] S402, obtaining domain name server DNS data in the IP multimedia system IMS network;

[0050] S404: Determine the one-to-one correspondence between the IP addresses of the SCSCF network element and the AS network element according to the DNS data.

[0051] In a specific instance, the minimum data unit includes: SCSCF network element IP address; AS network element IP address; number of uplink Invites; number of various uplink failure codes; number of downlink Invites; number of various downlink failure codes; time interval; among which, the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element.

[0052] In a specific example, the initialization failure code information of each minimum data unit is determined according to the difference between the number of each type of downlink failure code and the number of each type of uplink failure code in the same time interval in each minimum data unit.

[0053] In one embodiment of the present disclosure, Figure 5 As shown, the application server fault location method provided in the embodiment of the present disclosure can traverse data through the following steps to accurately locate the AS network element where the fault occurs:

[0054] S502, determining a suspicious AS network element set according to the origination failure code information;

[0055] S504, traverse data according to the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets;

[0056] S506: If the total number of SCSCF network elements in the suspicious AS network element set exceeds the preset threshold of the total number of SCSCF network elements with which the AS network elements have service interactions, a faulty AS network element is determined.

[0057] In one embodiment of the present disclosure, Figure 6 As shown, the application server fault location method provided in the embodiment of the present disclosure can traverse data through the following steps to accurately locate the AS network element where the fault occurs:

[0058] S602: Determine the impact range of the AS on the service based on the total number of AS-originated failure codes and the total number of uplink Invites.

[0059] In one embodiment of the present disclosure, the uplink failure code includes a failure code transferred by an AS network element in the IMS network; the downlink failure code includes an uplink failure code and an origination failure code.

[0060] For example, the uplink failure code is a failure code initiated by a network element or other unknown network element in the IMS network. These failure codes will be transferred through the AS network element; the downlink failure code is a failure code that includes the uplink failure code and the failure code initiated by this network element. Figure 7 shown.

[0061] Based on the same inventive concept, the present disclosure also provides an application server fault location device, as described in the following embodiments. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0062] Figure 8 A schematic diagram of a device for locating a fault in an application server according to an embodiment of the present disclosure is shown. Figure 8 As shown, the device includes: a minimum data unit determination module 81, an origination failure code information determination module 82, a faulty AS network element determination module 83, a corresponding relationship determination module 84 and a service impact range determination module 85.

[0063] Among them, the minimum data unit determination module 81 is used to determine multiple minimum data units of the SCSCF network element and the AS network element according to the one-to-one correspondence between the IP addresses of the service call session control function SCSCF network element and the application server AS network element;

[0064] The origination failure code information determination module 82 is used to determine the origination failure code information of each minimum data unit according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit;

[0065] The faulty AS network element determination module 83 is used to determine the faulty AS network element according to the initialization failure code information.

[0066] In one embodiment of the present disclosure, the above-mentioned application server fault locating device also includes a correspondence determination module 84 for: obtaining domain name server DNS data in the IP multimedia system IMS network; and determining the one-to-one correspondence between the IP addresses of the SCSCF network element and the AS network element based on the DNS data.

[0067] In one embodiment of the present disclosure, the minimum data unit in the above-mentioned minimum data unit determination module 81 includes: SCSCF network element IP address; AS network element IP address; number of uplink Invites; number of various uplink failure codes; number of downlink Invites; number of various downlink failure codes; time interval; among which, the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element.

[0068] In one embodiment of the present disclosure, the above-mentioned initialization failure code information determination module 82 is used to determine the initialization failure code information of each minimum data unit according to the difference between the number of each type of downlink failure code and the number of each type of uplink failure code in the same time interval in each minimum data unit.

[0069] In one embodiment of the present disclosure, the above-mentioned faulty AS network element determination module 83 is used to: determine a suspicious AS network element set based on the originating failure code information; traverse data based on the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets; if the total number of SCSCF network elements in the suspicious AS network element set exceeds the preset threshold of the total number of SCSCF network elements with which the AS network elements have business interactions, determine the faulty AS network element.

[0070] In one embodiment of the present disclosure, the application server fault locating device further includes a service impact range determination module 85 for determining information on the impact range of the AS on the service based on the total number of failure codes initiated by the AS and the total number of uplink Invites.

[0071] In one embodiment of the present disclosure, the uplink failure code in the above-mentioned origination failure code information determination module 82 includes a failure code transferred by an AS network element in the IMS network; the downlink failure code includes an uplink failure code and an origination failure code.

[0072] It should be noted that the above-mentioned minimum data unit determination module 81, the initialization failure code information determination module 82, and the faulty AS network element determination module 73 correspond to S302 to S306 in the method embodiment, and the examples and application scenarios implemented by the above-mentioned modules and corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned method embodiment. It should be noted that the above-mentioned modules as part of the device can be executed in a computer system such as a set of computer executable instructions.

[0073] In one embodiment of the present disclosure, the first step is to form the basic data and service data of the monitoring object in the present disclosure. The basic data comes from the SRV record and A record in the DNS data in the IMS network, which dynamically forms the correspondence between the host name and IP address of the SCSCF network element and the correspondence between the host name and IP address of the AS network element.

[0074] The source of service data can be signaling XDR (External Data Representation) or the statistical file measured by IP of SCSCF network element in IMS network. The service data between SCSCF network element and AS network element is filtered out according to the basic data.

[0075] This disclosure requires the regularization of business data, refer to Figure 1 The logical connection relationship between the SCSCF network element and the AS network element is a many-to-many relationship. Each SCSCF network element and AS network element should have at least one IP address. According to the one-to-one correspondence between the IP addresses, a single connection data between the SCSCF network element and the AS network element is formed, that is, the minimum data unit. Figure 2 . In the minimum data unit, the direction of message transmission in each single connection is constructed based on the source IP address and the destination IP address, and is divided into an upstream path and a downstream path according to the sending direction. The upstream path has the source IP address of the SCSCF network element address and the destination IP address of the AS network element address, that is, the path for the SCSCF to send messages to the AS; the downstream path has the source IP address of the AS network element address and the destination IP address of the SCSCF network element address, that is, the path for the AS to send messages to the SCSCF. The fields in this minimum data unit include the SCSCF network element IP address, the AS network element IP address, the number of upstream Invites, the number of various upstream failure codes, the number of downstream Invites, the number of various downstream failure codes, and the time interval.

[0076] The second step is to form the method of analyzing the number of initial failure codes for the monitored object disclosed in the present invention.

[0077] The number of uplink failure codes and downlink failure codes are further classified: the uplink failure code is the failure code initiated by a network element or other unknown network element in the IMS network, and these failure codes will be transferred through the AS network element; the downlink failure code is a combination of the uplink failure code and the failure code initiated by this network element, refer to Figure 3 For each minimum data unit in the same time period, the origination failure codes existing in the minimum unit are obtained by calculating the difference between the number of each type of downlink failure codes and the number of each type of uplink failure codes.

[0078] The third step is to form a method for sensing AS failure according to a sudden change in the number of AS origination failure codes in the present disclosure.

[0079] This method is to call and analyze the number of origination failure codes according to time periods, and traverse each minimum data unit of business data line by line to find abnormal points.

[0080] Each minimum data unit is used as a monitoring object. The number of uplink Invite of the monitoring object is not 0. If the number of uplink Invite is 0, the monitoring object has no call service.

[0081] For the monitoring object, the present disclosure compares the number of a certain type of origination failure code in the current period with the peak number of origination failure codes in the same period and position in history, and determines whether it is abnormal according to the following rules.

[0082] The rule judgment formula is:

[0083] (The current number of origination failure codes > the peak value of origination failure codes in the same period of the previous M days + K) and (the current number of origination failure codes > (the total number of invite messages * N%));

[0084] Wherein, K is the discrete threshold value, and N is the weight value of the failure code's influence on the call Invite. If the above two items are true, the minimum data unit is included in the current suspicious data unit set.

[0085] Further, the suspicious data units are verified for accuracy.

[0086] In the IMS network, the number of AS network elements originating failure codes is relatively high. There are two situations: one is caused by problems with the AS network element. The main phenomenon is that all SCSCF network elements connected to the AS network element will be affected; the other is that business behavior leads to a sudden increase in occasional failure codes. The main phenomenon is that a small number of SCSCF network elements connected to the AS network element will be affected.

[0087] Based on the above phenomenon, the verification method disclosed in the present invention is formed, which traverses the suspicious data unit set to obtain the AS network element IP address list, and uses each IP as an index to perform cyclic determination until the end.

[0088] The loop judgment method is: traverse the suspicious data unit set and calculate the total number of affected SCSCFs, define the value as variable Sum1, and traverse the minimum data unit whose uplink Invite number is not 0 in the service data of the same period and calculate the total number of all SCSCFs connected to the AS network element, and define the value as variable Sum2. When Sum1 / Sum2>0.5, the IP address of the AS network element is inserted into the abnormal data set, and the judgment ends, otherwise the judgment ends directly.

[0089] Finally, an abnormal data set for this period is formed. When there is data in the abnormal data set, there is an abnormal AS.

[0090] The present disclosure makes up for the deficiencies in the IMS network's ability to locate and analyze failure code problems, simplifies the method for finding faulty ASs, and the method can be implemented by machines, allowing machines to replace a large amount of manpower, and proactively perform maintenance monitoring on such problems, thereby improving the speed and accuracy of finding problems, thereby improving user experience.

[0091] Fig. 9 The present disclosure is shown to be implemented by an electronic device, referring to Fig. 9 , this embodiment is implemented through modules.

[0092] like Fig. 9 As shown, a preferred embodiment thereof is composed of a data acquisition module 910, a data analysis engine 920, and a storage module 930. The data acquisition module 910 acquires and forms basic data and business data, the basic data being the host name and IP address of the SCSCF and the host name and IP address of the AS, and the business data being the statistics of various types of interaction information between the SCSCF and the AS in units of IP addresses; the analysis engine 920 performs machine analysis on the business data to generate analysis results; the data storage module 930 provides a storage medium for the basic data, business data, and analysis results.

[0093] The service implementation of this embodiment is as follows:

[0094] First, basic data is obtained, which requires the use of a data acquisition module 910 and a data storage module 930;

[0095] The data acquisition module 910 connects with the IMS network DNS network element to obtain DNS data, and according to the basic data requirements of this embodiment, stores the DNS data of the SCSCF network element and the AS network element into the data storage module 920 to form basic data, which constitutes two types of data as follows:

[0096] The first type of data is the Pool name of the SCSCF network element, the host names of all SCSCFs in each Pool and their corresponding IP addresses.

[0097] An example of SCSCF basic data is shown in Table 1 below:

[0098] Table 1

[0099] SCSCFPOOL ID SCSCF SEVERNAME SCSCF IP SCSCFPOOL1 SCSCSF11 1.1.1.1 SCSCFPOOL1 SCSCSF12 1.1.1.2 SCSCFPOOL1 SCSCSF12 1.1.1.3 SCSCFPOOL2 SCSCSF21 1.1.2.1 SCSCFPOOL1 SCSCSF22 1.1.2.2

[0100] The second type of data is the pool name of the AS network element, the host names of all SCSCFs in each pool and their corresponding IP addresses.

[0101] An example of AS basic data is shown in Table 2 below:

[0102] Table 2

[0103] ASPOOL ID AS SEVERNAME AS IP ASFPOOL1 AS11 2.1.1.1 ASFPOOL1 AS12 2.1.1.2 ASFPOOL2 AS21 2.1.2.1 ASFPOOL3 AS31 2.1.3.1

[0104] Furthermore, to obtain and form business data, a data acquisition module 910 and a data storage module 930 are required;

[0105] The data acquisition module 910 is connected to the signaling monitoring system to periodically acquire the signaling XDR data, and according to the business data requirements of this embodiment, classifies and counts the XDR data according to the rules of this method to form business data and store it in the data storage module 930.

[0106] The data structure is shown in Table 3 below:

[0107] Table 3

[0108]

[0109] Reference Fig.10 , the method for forming business data in the data acquisition module 910 includes S1001, S1002 and S1003, wherein:

[0110] S1001. Periodically obtain the ISC interface type XDR file.

[0111] Obtain the ISC interface type XDR file of the information measurement system and temporarily store it locally for subsequent data cleaning and organization.

[0112] S1002. Filter data according to source and destination IP addresses to form statistics of uplink data and downlink data.

[0113] The obtained ISC interface XDR file is used to extract the source and destination IP addresses for classification and counting. Combined with the basic data, the SCSCF is used as the source IP address and each AS is used as the target IP address for group counting and counting to obtain various data in the upstream path, including the number of upstream Invites and the number of various upstream failure codes. At the same time, the same AS is used as the source IP address and the same SCSCF IP is used as the target IP address as the various data in the downstream path, including the number of Invites and the number of various downstream failure codes, and then the date and time interval of the cycle are added to form business data.

[0114] S1003, put into storage and notify the analysis module.

[0115] The data acquisition module 910 stores the generated business data in the data storage module 930, and notifies the business analysis engine 920 after the storage is completed, notifying the parameters including the date and time period.

[0116] Further, the business data is analyzed using the analysis engine 920 and the data storage module 930. Fig.11 The method for analyzing business data includes S1101, S1102, S1103 and S1104, wherein:

[0117] S1101. Listen for notification.

[0118] The analysis engine 920 listens to the notification of the data acquisition module 910, and triggers the analysis process of the business data upon receipt.

[0119] S1102: Analyze the number of failure codes issued by the AS according to the business data, and determine whether the AS is abnormal according to a sudden change in the number of a certain type of failure code.

[0120] First, the service data in the current time period is traversed line by line. The number of uplink Invite of the monitored object is not 0. If the number of uplink Invite is 0, the monitored object has no call service. The difference between the number of various downlink failure codes and the number of various uplink failure codes is calculated to obtain whether there is an AS-originated failure code number.

[0121] Formula for obtaining the number of origination failure codes: Let the AS origination failure code be y n , the number of various downlink failure codes x n , the number of various uplink failure codes x′ n , get y n =x n -x′ n , that is, the number of origination failure codes.

[0122] Furthermore, for the monitoring object, the present disclosure compares the number of a certain type of origination failure code in the current period with the peak number of origination failure codes in the same period and location in history, and determines whether it is abnormal according to the following rules. The judgment formula is:

[0123] (The current number of origination failure codes > the peak value of origination failure codes in the same period of the previous M days + K) and (the current number of origination failure codes > (the total number of Invite messages * N%)), where K is the discrete threshold value and N is the proportion of the failure code's impact on the Invite call.

[0124] If the above two items are true, the minimum data unit is included in the current suspicious data unit set.

[0125] Step S1103: Verify the determination result according to the relationship between the SCSCF and the AS.

[0126] In the analysis engine 920, the suspicious data set is verified, and the data is traversed through the IP addresses of the AS network elements to obtain the IP addresses of all SCSCF network elements. When the total number of SCSCF network elements in the suspicious set exceeds K% of the total number of SCSCFs with business interactions in the AS, where K is the threshold, the suspicious set is judged to be a fault set. If it is lower than the threshold, it is discarded.

[0127] Step S1104: generate analysis results.

[0128] In the analysis engine 920, the AS, SCSCF and failure code of the fault set are added to the analysis result, and the scope of the AS's impact on the service is calculated by the algorithm. The formula is: AS's impact on the service = (total number of AS-originating failure codes / total number of uplink Invites) × 100%. The final analysis result is stored in the data storage module 930.

[0129] The present disclosure uses a difference algorithm of traffic (number of failure codes) flow direction (the direction in which the failure codes are sent) to calculate the difference between the number of various downlink failure codes and the number of various uplink failure codes to obtain the number of AS-originating failure codes. The number of AS-originating failure codes is calculated by this unified algorithm. This helps to quickly and accurately locate the AS network element that has a fault.

[0130] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0131] Refer to the following Fig.12 1200 according to this embodiment of the present disclosure is described. Fig.12 The electronic device 1200 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0132] like Fig.12 As shown, the electronic device 1200 is in the form of a general computing device. The components of the electronic device 1200 may include but are not limited to: at least one processing unit 1210, at least one storage unit 1220, and a bus 1230 connecting different system components (including the storage unit 1220 and the processing unit 1210).

[0133] The storage unit stores program codes, which can be executed by the processing unit 1210, so that the processing unit 1210 executes the steps described in the above “exemplary method” section of this specification according to various exemplary embodiments of the present disclosure.

[0134] For example, the processing unit 1210 can execute the following steps of the above method embodiment: determine multiple minimum data units of the SCSCF network element and the AS network element based on the one-to-one correspondence between the IP addresses of the service call session control function SCSCF network element and the application server AS network element; determine the originating failure code information of each minimum data unit based on the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit; determine the faulty AS network element based on the originating failure code information.

[0135] For example, the processing unit 1210 may execute the following steps of the above method embodiment: obtaining domain name server DNS data in the IP multimedia system IMS network; and determining a one-to-one correspondence between IP addresses of the SCSCF network element and the AS network element according to the DNS data.

[0136] For example, the minimum data unit in the steps of the above method embodiment executed by the processing unit 1210 includes: SCSCF network element IP address; AS network element IP address; number of uplink Invites; number of various uplink failure codes; number of downlink Invites; number of various downlink failure codes; time interval; among which, the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element.

[0137] For example, the processing unit 1210 may execute the following steps of the above method embodiment: determine the initialization failure code information of each minimum data unit according to the difference between the number of each type of downlink failure code and the number of each type of uplink failure code in the same time interval in each minimum data unit.

[0138] For example, the processing unit 1210 can execute the following steps of the above-mentioned method embodiment: determine the suspicious AS network element set according to the originating failure code information; traverse the data according to the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets; if the total number of SCSCF network elements in the suspicious AS network element set exceeds the preset threshold of the total number of SCSCF network elements with which the AS network elements have business interactions, determine the faulty AS network element.

[0139] For example, the processing unit 1210 may execute the following steps of the above method embodiment: determine information on the impact range of the AS on the service according to the total number of failure codes initiated by the AS and the total number of uplink Invites.

[0140] For example, the uplink failure code in the steps of the above method embodiment executed by the processing unit 1210 includes a failure code transferred by an AS network element in the IMS network; the downlink failure code includes an uplink failure code and an origination failure code.

[0141] The storage unit 1220 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 12201 and / or a cache storage unit 12202 , and may further include a read-only storage unit (ROM) 12203 .

[0142] The storage unit 1220 may also include a program / utility 12204 having a set (at least one) of program modules 12205, such program modules 12205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0143] Bus 1230 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0144] The electronic device 1200 may also communicate with one or more external devices 1240 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1200, and / or communicate with any device that enables the electronic device 1200 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1250. Furthermore, the electronic device 1200 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 1260. As shown, the network adapter 1260 communicates with other modules of the electronic device 1200 via a bus 1230. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0145] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure 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, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0146] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer program product, which includes: a computer program, which implements the above-mentioned application server fault locating method when executed by a processor.

[0147] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the above method of the present disclosure is stored thereon. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Exemplary Method” section of this specification.

[0148] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), 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 foregoing.

[0149] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code 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. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0150] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0151] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0152] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, 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 multiple modules or units to be embodied.

[0153] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0154] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure 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, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0155] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which 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 intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A method for locating an application server fault, characterized in that: include: According to the one-to-one correspondence between the IP addresses of the service call session control function SCSCF network element and the application server AS network element, multiple minimum data units of the SCSCF network element and the AS network element are determined; Determine the initialization failure code information of each minimum data unit according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit; Determine the faulty AS network element according to the origination failure code information; The minimum data unit includes: SCSCF network element IP address; AS network element IP address; the number of uplink Invite; the number of various uplink failure codes; the number of downlink Invite; the number of various downlink failure codes; the time interval; the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element; Determining the faulty AS network element based on the initial failure code information includes: determining a suspicious AS network element set based on the initial failure code information; traversing data based on the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets; if the total number of SCSCF network elements in the suspicious AS network element set exceeds a preset threshold of the total number of SCSCF network elements with which the AS network elements have business interactions, determining the faulty AS network element.

2. The method for locating an application server fault according to claim 1, characterized in that: Before acquiring the service data between the service call session control function SCSCF network element and the application server AS network element, the method further includes: Obtaining DNS data from the IP multimedia system IMS network; According to the DNS data, a one-to-one correspondence between the IP addresses of the SCSCF network element and the AS network element is determined.

3. The method for locating an application server fault according to claim 1, characterized in that: The method further comprises: The initial transmission failure code information of each minimum data unit is determined according to the difference between the number of each type of downlink failure code and the number of each type of uplink failure code in the same time interval in each minimum data unit.

4. The method for locating an application server fault according to claim 1, characterized in that: After determining the fault AS according to the initialization failure code information, the method further includes: The impact range of the AS on the service is determined based on the total number of AS-originated failure codes and the total number of uplink Invite messages.

5. The application server fault location method according to claim 1, characterized in that: The uplink failure code includes a failure code transferred via an AS network element in the IMS network; the downlink failure code includes an uplink failure code and an origination failure code.

6. An application server fault location device, characterized in that: include: A minimum data unit determination module, configured to determine multiple minimum data units of a service call session control function SCSCF network element and an application server AS network element according to a one-to-one correspondence between IP addresses of the SCSCF network element and the AS network element; The origination failure code information determination module is used to determine the origination failure code information of each minimum data unit according to the difference between the number of uplink failure codes and the number of downlink failure codes of each minimum data unit, wherein the minimum data unit includes: SCSCF network element IP address; AS network element IP address; the number of uplink Invites; the number of various uplink failure codes; the number of downlink Invites; the number of various downlink failure codes; the time interval; wherein the uplink represents the path for the SCSCF network element to send messages to the AS network element; the downlink represents the path for the AS network element to send messages to the SCSCF network element; A faulty AS network element determination module, used to determine the faulty AS network element according to the initialization failure code information; The faulty AS network element determination module is also used to determine a suspicious AS network element set based on the initial failure code information; traverse data based on the IP addresses of the AS network elements in the suspicious AS network element set to determine the total number of SCSCF network elements in all suspicious AS network element sets; if the total number of SCSCF network elements in the suspicious AS network element set exceeds a preset threshold of the total number of SCSCF network elements with which the AS network elements have business interactions, determine the faulty AS network element.

7. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the application server fault locating method according to any one of claims 1 to 5 by executing the executable instructions.

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

Images